Skip to content

Commit

Permalink
Merge pull request #405 from ST6-Bravo/YGIG
Browse files Browse the repository at this point in the history
YGIG Procedures
  • Loading branch information
tylerthetiletiler authored Jan 21, 2025
2 parents 4c35de1 + 9f556c3 commit 464a122
Show file tree
Hide file tree
Showing 2 changed files with 60 additions and 1 deletion.
37 changes: 36 additions & 1 deletion docs/aerodromes/classc/Gingin.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,42 @@

--8<-- "includes/abbreviations.md"

Reserved.
## Positions

| Name | Callsign | Frequency | Login ID |
| ------------------ | -------------- | ---------------- | --------------------------------------|
| **Gingin ADC** | **Gingin Tower** | **118.500** | **GIG_TWR** |

## Airspace
GIG ADC owns the airspace within the GIG CIRA, which is defined as within **5nm** of the YGIG ARP, *excluding* the area south of **12 TACAN PEA**, from `SFC` to `A035`.

This airspace is primarily used for military circuits and initial and pitch approaches.

Refer to the [YPEA FIHA AD2 Supp](https://ais-af.airforce.gov.au/australian-aip){target=new} for a diagram.

## Miscellaneous
### Circuit Operations
The CIRA airspace is allocated to be within 5nm of the YGIG ARP from `SFC` to `A035` exculding the area within 12TAC Pearce. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management.

The Circuit altitude is `A016` for Jets, and `A012` for Non-Jets.

### Circuit Direction
The Ciruits are preferred to be to the south of the field.

### Initial and Pitch Procedures
The intial points for Gingin are RWY 08 is the corner of the pine plantation and RWY 26 is the paddock divided by the creek. The intial altitude is `A015`.

## Coordination
### PE TCU
'Next' coordination is required from GIG ADC to PE TCU for all aircraft.

!!! example
<span class="hotline">**GIG ADC** -> **PE TCU**</span>: "Next, VIPR01, Runway 08"
<span class="hotline">**PE TCU** -> **GIG ADC**</span>: "VIPR01, Assigned Heading Right 030, unrestricted"
<span class="hotline">**PE ADC** -> **PE TCU**</span>: "Right Heading 030, VIPR01"

The Standard Assignable Level from **GIG ADC** to **PE TCU** is the lower of `A050` or the `RFL`.

## Charts
!!! abstract "Reference"
Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}
24 changes: 24 additions & 0 deletions docs/terminal/pearce.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,30 @@ All other arrivals/overfliers coming from HYD CTA will be **Heads-up** Coordinat
<span class="hotline">**PE TCU** -> **PH TCU**</span>: "Airborne YPEA, PHNX11"
<span class="hotline">**PH TCU** -> **PE TCU**</span>: "PHNX11, F180"

### PE ADC
'Next' coordination is required from PE ADC to PE TCU for all aircraft.

!!! phraseology
<span class="hotline">**PE ADC** -> **PE TCU**</span>: "Next, ASY01, runway 36L"
<span class="hotline">**PE TCU** -> **PE ADC**</span>: "ASY01, Heading 030, unrestricted"
<span class="hotline">**PE ADC** -> **PE TCU**</span>: "Heading 030, ASY01"

The Standard Assignable Level from **PE ADC** to **PE TCU** is:

- `F130` for aircraft assigned a Procedural SID; except
- `A030` for aircraft assigned the **GUNOK** SID; or
- The lower of `F130` or `RFL` for all other aircraft

### GIG ADC
'Next' coordination is required from GIG ADC to PE TCU for all aircraft.

!!! example
<span class="hotline">**GIG ADC** -> **PE TCU**</span>: "Next, VIPR01, Runway 08"
<span class="hotline">**PE TCU** -> **GIG ADC**</span>: "VIPR01, Assigned Heading Right 030, unrestricted"
<span class="hotline">**PE ADC** -> **PE TCU**</span>: "Right Heading 030, VIPR01"

The Standard Assignable Level from **GIG ADC** to **PE TCU** is the lower of `A050` or the `RFL`.

## Charts
!!! abstract "Reference"
Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new}

0 comments on commit 464a122

Please sign in to comment.