From 748f56eccd15f94090098e788756767936052d50 Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Fri, 13 Dec 2024 22:44:24 +1100 Subject: [PATCH 01/14] YPEA Procedures Initial Procedures --- docs/aerodromes/classc/Pearce.md | 64 +++++++++++++++++++++++++++++++- 1 file changed, 63 insertions(+), 1 deletion(-) diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index 607f48171..4b63ed1d5 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -4,7 +4,69 @@ --8<-- "includes/abbreviations.md" -Reserved. +## Positions +| Name | Callsign | Frequency | Login ID | +| ------------------ | -------------- | ---------------- | --------------------------------------| +| **Pearce ADC** | **Pearce Tower** | **118.300** | **PE_TWR** | +| **Pearce SMC** | **Pearce Ground** | **127.250** | **PE_GND** | +| **Pearce ACD** | **Pearce Delivery** | **134.100** | **PE_DEL** | +| Pearce ATIS | | 136.400 | YPEA_ATIS | + +## Airsapce + +PE ADC owns the Class C airspace **in the PE CTR** within 5nm of the YPEA ARP from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches. + +### Sid Selection +Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. +Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. + +!!! Note + Due to Civil Traffic Arriving from the North, the GUNOK SID will have an altitude assignment of A030. + + ### Level Assignment +The Standard Assignable Level from **PE ADC** to **PE TCU** is: +a) The Lower of `F130` or `RFL` for Aircraft assigned via Procedural or RNAV SID. +b) `F130` for Aircraft assigned a Coded Departure. + +#### Miscellaneous + +### Circuit Operations +The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of 1600 while both 2FTS and RSAF PC21s are assigned 1200ft. + +!!! Note + 36L/18R is unsuitable for HAWK Aircraft + +### Circuit Direction +| Runway | Direction | +| ------ | ----------| +| 5 | Left | +| 18L | Right | +| 18R | Right | +| 23 | Right | +| 36L | Left | +| 36R | Left | + +### Initial and Pitch Procedures + +| Runway | Direction Initial | Inital Altitude +| ------ | ------------------|----------------| +| 5 | Any | 1000 +| 18L | Left/Straight | 1500 | Right | 1000 +| 18R | Left/Straight | 1500 | Right | 1000 +| 23 | Any | 1500 +| 36L | Left | 1000 | Right | 1500 +| 36R | Left | 1000 | Right | 1500 + +## Coordination +### PE TCU + +'Next' coordination is required from PE ADC to PE TCU for all aircraft. + +!!! example + **PE ADC** -> **PE TCU**: "Next, ASY01, runway 33" + **PE TCU** -> **PE ADC**: "ASY01, Assigned Heading Right 030, unrestricted" + **PE ADC** -> **PE TCU**: "Assigned Heading Heading Right 030, ASY01" +## Charts !!! note 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} \ No newline at end of file From 214b67fb4c4781064611be3f445846abadf1daf3 Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Wed, 18 Dec 2024 07:14:30 +1100 Subject: [PATCH 02/14] Fixed Formatting --- docs/aerodromes/classc/Pearce.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index 4b63ed1d5..b9c6103c5 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -17,7 +17,7 @@ PE ADC owns the Class C airspace **in the PE CTR** within 5nm of the YPEA ARP from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches. -### Sid Selection +### SID Selection Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. @@ -32,7 +32,7 @@ b) `F130` for Aircraft assigned a Coded Departure. #### Miscellaneous ### Circuit Operations -The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of 1600 while both 2FTS and RSAF PC21s are assigned 1200ft. +The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A035'. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of A016 while both 2FTS and RSAF PC21s are assigned A012. !!! Note 36L/18R is unsuitable for HAWK Aircraft @@ -51,12 +51,12 @@ The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SF | Runway | Direction Initial | Inital Altitude | ------ | ------------------|----------------| -| 5 | Any | 1000 -| 18L | Left/Straight | 1500 | Right | 1000 -| 18R | Left/Straight | 1500 | Right | 1000 -| 23 | Any | 1500 -| 36L | Left | 1000 | Right | 1500 -| 36R | Left | 1000 | Right | 1500 +| 5 | Any | A010 +| 18L | Left/Straight | A015 | Right | A010 +| 18R | Left/Straight | A015 | Right | A010 +| 23 | Any | A015 +| 36L | Left | A010 | Right | A015 +| 36R | Left | A010 | Right | A015 ## Coordination ### PE TCU @@ -64,7 +64,7 @@ The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SF 'Next' coordination is required from PE ADC to PE TCU for all aircraft. !!! example - **PE ADC** -> **PE TCU**: "Next, ASY01, runway 33" + **PE ADC** -> **PE TCU**: "Next, ASY01, runway 36R" **PE TCU** -> **PE ADC**: "ASY01, Assigned Heading Right 030, unrestricted" **PE ADC** -> **PE TCU**: "Assigned Heading Heading Right 030, ASY01" ## Charts From 3f4eceff48aed67be81b7e1460cece561bccc71d Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Wed, 18 Dec 2024 08:53:20 +1100 Subject: [PATCH 03/14] Fixed typos --- docs/aerodromes/classc/Pearce.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index 4b63ed1d5..569a50244 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -17,7 +17,7 @@ PE ADC owns the Class C airspace **in the PE CTR** within 5nm of the YPEA ARP from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches. -### Sid Selection +### SID Selection Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. @@ -32,7 +32,7 @@ b) `F130` for Aircraft assigned a Coded Departure. #### Miscellaneous ### Circuit Operations -The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of 1600 while both 2FTS and RSAF PC21s are assigned 1200ft. +The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of A016 while both 2FTS and RSAF PC21s are assigned A012. !!! Note 36L/18R is unsuitable for HAWK Aircraft @@ -51,12 +51,12 @@ The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SF | Runway | Direction Initial | Inital Altitude | ------ | ------------------|----------------| -| 5 | Any | 1000 -| 18L | Left/Straight | 1500 | Right | 1000 -| 18R | Left/Straight | 1500 | Right | 1000 -| 23 | Any | 1500 -| 36L | Left | 1000 | Right | 1500 -| 36R | Left | 1000 | Right | 1500 +| 5 | Any | A010 +| 18L | Left/Straight | A015 | Right | A010 +| 18R | Left/Straight | A015 | Right | A010 +| 23 | Any | A015 +| 36L | Left | A010 | Right | A015 +| 36R | Left | A010 | Right | A015 ## Coordination ### PE TCU @@ -64,7 +64,7 @@ The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SF 'Next' coordination is required from PE ADC to PE TCU for all aircraft. !!! example - **PE ADC** -> **PE TCU**: "Next, ASY01, runway 33" + **PE ADC** -> **PE TCU**: "Next, ASY01, runway 36L" **PE TCU** -> **PE ADC**: "ASY01, Assigned Heading Right 030, unrestricted" **PE ADC** -> **PE TCU**: "Assigned Heading Heading Right 030, ASY01" ## Charts From d1749cb4e8e1b4469934fda1fbc754a274cba10d Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Sun, 22 Dec 2024 09:09:40 +1100 Subject: [PATCH 04/14] Fixed Typo --- docs/aerodromes/classc/Pearce.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index 569a50244..63d58b6b9 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -29,7 +29,7 @@ The Standard Assignable Level from **PE ADC** to **PE TCU** is: a) The Lower of `F130` or `RFL` for Aircraft assigned via Procedural or RNAV SID. b) `F130` for Aircraft assigned a Coded Departure. -#### Miscellaneous +## Miscellaneous ### Circuit Operations The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of A016 while both 2FTS and RSAF PC21s are assigned A012. From 3d81b6a65ce80717629aabf35c17f713badb3f01 Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Sun, 22 Dec 2024 09:28:56 +1100 Subject: [PATCH 05/14] SID Tweaks Per Tylers Comments --- docs/aerodromes/classc/Pearce.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index 63d58b6b9..c0da3c5f5 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -18,10 +18,11 @@ PE ADC owns the Class C airspace **in the PE CTR** within 5nm of the YPEA ARP from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches. ### SID Selection -Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. -Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. +vatSys does not have SIDs built-in for YPEA. Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. as long as ATC is familiar with the chart, and the pilot is able. Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. !!! Note + A Radar SID is preferred, however a Procedural SID may be issued on request. + Due to Civil Traffic Arriving from the North, the GUNOK SID will have an altitude assignment of A030. ### Level Assignment From 5e41a9d0f351b60ce315c906ac0fc21dc8721cbc Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Mon, 23 Dec 2024 02:59:37 +1100 Subject: [PATCH 06/14] pea adc fixes, reference admonition --- docs/aerodromes/classc/Amberley.md | 2 +- docs/aerodromes/classc/Curtin.md | 2 +- docs/aerodromes/classc/Darwin.md | 2 +- docs/aerodromes/classc/Edinburgh.md | 2 +- docs/aerodromes/classc/Gingin.md | 2 +- docs/aerodromes/classc/Learmonth.md | 2 +- docs/aerodromes/classc/Oakey.md | 2 +- docs/aerodromes/classc/Pearce.md | 55 +++++++++++++-------------- docs/aerodromes/classc/Richmond.md | 4 +- docs/aerodromes/classc/Scherger.md | 2 +- docs/aerodromes/classc/Tindal.md | 2 +- docs/aerodromes/classc/Townsville.md | 4 +- docs/aerodromes/classc/Williamtown.md | 2 +- docs/aerodromes/procedural/Woomera.md | 2 +- docs/terminal/amberleyoakey.md | 2 +- docs/terminal/curtin.md | 2 +- docs/terminal/darwin.md | 2 +- docs/terminal/learmonth.md | 2 +- docs/terminal/pearce.md | 2 +- docs/terminal/scherger.md | 2 +- docs/terminal/tindal.md | 6 +-- docs/terminal/townsville.md | 2 +- docs/terminal/williamtown.md | 2 +- 23 files changed, 53 insertions(+), 54 deletions(-) diff --git a/docs/aerodromes/classc/Amberley.md b/docs/aerodromes/classc/Amberley.md index 43abb533a..212bdac6e 100644 --- a/docs/aerodromes/classc/Amberley.md +++ b/docs/aerodromes/classc/Amberley.md @@ -57,7 +57,7 @@ Aircraft will depart the circuit visually and track overhead YAMB to begin track Runways 15/33 are the primary runways at YAMB. ## Charts -!!! note +!!! 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} ## Miscellaneous diff --git a/docs/aerodromes/classc/Curtin.md b/docs/aerodromes/classc/Curtin.md index dcb91159f..21bca726b 100644 --- a/docs/aerodromes/classc/Curtin.md +++ b/docs/aerodromes/classc/Curtin.md @@ -38,5 +38,5 @@ The Standard Assignable Level from **CIN ADC** to **CIN TCU** is the Lower of ` When CIN TCU is offline, coordination is not required between CIN ADC and TRT(ASH). Aircraft entering TRT(ASH) airspace shall be handed off, and instructed to contact TRT(ASH) for onwards clearance. ## Charts -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Darwin.md b/docs/aerodromes/classc/Darwin.md index 0e31e4057..951404b16 100644 --- a/docs/aerodromes/classc/Darwin.md +++ b/docs/aerodromes/classc/Darwin.md @@ -52,7 +52,7 @@ For non-RNAV approved IFR aircraft with a wake turbulence category of medium or For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or Radar SID ## Charts -!!! note +!!! 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} ## Miscellaneous diff --git a/docs/aerodromes/classc/Edinburgh.md b/docs/aerodromes/classc/Edinburgh.md index a66597426..ccb33584a 100644 --- a/docs/aerodromes/classc/Edinburgh.md +++ b/docs/aerodromes/classc/Edinburgh.md @@ -6,5 +6,5 @@ Reserved. -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Gingin.md b/docs/aerodromes/classc/Gingin.md index 411bc76da..62cfa7b45 100644 --- a/docs/aerodromes/classc/Gingin.md +++ b/docs/aerodromes/classc/Gingin.md @@ -6,5 +6,5 @@ Reserved. -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Learmonth.md b/docs/aerodromes/classc/Learmonth.md index 2493037af..fa7dc142b 100644 --- a/docs/aerodromes/classc/Learmonth.md +++ b/docs/aerodromes/classc/Learmonth.md @@ -37,5 +37,5 @@ The Standard Assignable Level from **LM ADC** to **LM TCU** is the Lower of `F2 When LM TCU is offline, coordination is not required between LM ADC and OLW. Aircraft entering OLW airspace shall be handed off, and instructed to contact OLW for onwards clearance. ## Charts -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Oakey.md b/docs/aerodromes/classc/Oakey.md index f2ad68473..1c41db8bd 100644 --- a/docs/aerodromes/classc/Oakey.md +++ b/docs/aerodromes/classc/Oakey.md @@ -16,7 +16,7 @@ OK ADC owns the airspace within 5 DME of the OK VOR from `SFC` to `A025`. This airspace is designed to facilitate circuit traffic. ## Charts -!!! note +!!! 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} ## Miscellaneous diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index c0da3c5f5..75d67b449 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -14,34 +14,27 @@ | Pearce ATIS | | 136.400 | YPEA_ATIS | ## Airsapce - -PE ADC owns the Class C airspace **in the PE CTR** within 5nm of the YPEA ARP from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches. +PE ADC owns the airspace within the Pearce CIRA (**5nm** Radius of YPEA ARP, located entirely within **R155A**) from `SFC` to `A035`. This airspace is primarily used for military circuits and initial and pitch approaches. ### SID Selection -vatSys does not have SIDs built-in for YPEA. Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. as long as ATC is familiar with the chart, and the pilot is able. Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. - -!!! Note - A Radar SID is preferred, however a Procedural SID may be issued on request. - - Due to Civil Traffic Arriving from the North, the GUNOK SID will have an altitude assignment of A030. +All aircraft shall be assigned the **Radar** SID by default. - ### Level Assignment -The Standard Assignable Level from **PE ADC** to **PE TCU** is: -a) The Lower of `F130` or `RFL` for Aircraft assigned via Procedural or RNAV SID. -b) `F130` for Aircraft assigned a Coded Departure. +vatSys does not have Procedural SIDs built-in for YPEA. As long as ATC is familiar with the chart, and the pilot is able, aircraft may be assigned **Procedural SIDs** *on pilot request*. ## Miscellaneous - ### Circuit Operations -The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A032`. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of A016 while both 2FTS and RSAF PC21s are assigned A012. +Aircraft can be instructed to extend outside of this airspace by ATC for traffic management, following coordination with the appropriate sectors. + +HAWKs have circuit altitude of `A016`, while both 2FTS and RSAF PC21s are assigned `A012`. -!!! Note - 36L/18R is unsuitable for HAWK Aircraft +!!! note + 36L/18R is unsuitable for HAWK Aircraft ### Circuit Direction + | Runway | Direction | | ------ | ----------| -| 5 | Left | +| 05 | Left | | 18L | Right | | 18R | Right | | 23 | Right | @@ -52,22 +45,28 @@ The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SF | Runway | Direction Initial | Inital Altitude | ------ | ------------------|----------------| -| 5 | Any | A010 -| 18L | Left/Straight | A015 | Right | A010 -| 18R | Left/Straight | A015 | Right | A010 -| 23 | Any | A015 -| 36L | Left | A010 | Right | A015 -| 36R | Left | A010 | Right | A015 +| 05 | Any | A010 | +| 18L | Left/Straight
Right | A015
A010 | +| 18R | Left/Straight
Right | A015
A010 | +| 23 | Any | A015 | +| 36L | Left
Right | A010
A015 | +| 36R | Left
Right | A010
A015 | ## Coordination ### PE TCU - 'Next' coordination is required from PE ADC to PE TCU for all aircraft. -!!! example +!!! phraseology **PE ADC** -> **PE TCU**: "Next, ASY01, runway 36L" - **PE TCU** -> **PE ADC**: "ASY01, Assigned Heading Right 030, unrestricted" - **PE ADC** -> **PE TCU**: "Assigned Heading Heading Right 030, ASY01" + **PE TCU** -> **PE ADC**: "ASY01, Heading 030, unrestricted" + **PE ADC** -> **PE TCU**: "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 + ## Charts -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Richmond.md b/docs/aerodromes/classc/Richmond.md index f332e46a2..b9e5b22a4 100644 --- a/docs/aerodromes/classc/Richmond.md +++ b/docs/aerodromes/classc/Richmond.md @@ -21,8 +21,8 @@ Control authority of the **R470** Restricted Area when active is as follows: - SY TCU (SDN) `A015`-`A045` ## Charts -!!! note - 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} +!!! 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} ## Aerodrome ### SID Selection diff --git a/docs/aerodromes/classc/Scherger.md b/docs/aerodromes/classc/Scherger.md index c81dde374..a7de73c34 100644 --- a/docs/aerodromes/classc/Scherger.md +++ b/docs/aerodromes/classc/Scherger.md @@ -36,5 +36,5 @@ The Standard Assignable Level from **SG ADC** to **SG TCU** is the lower of `F2 When SG TCU is offline, coordination is not required between SG ADC and ISA(ARA). Aircraft entering ISA(ARA) airspace shall be handed off, and instructed to contact ISA(ARA) for onwards clearance. ## Charts -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Tindal.md b/docs/aerodromes/classc/Tindal.md index a0acefba7..3a940ec20 100644 --- a/docs/aerodromes/classc/Tindal.md +++ b/docs/aerodromes/classc/Tindal.md @@ -93,5 +93,5 @@ The Standard Assignable level from TN ADC to TN TCU is the lower of `F180` or th When TN TCU is offline, coordination is not required between TN ADC and TRT(TRS). Aircraft entering TRT(TRS) airspace shall be handed off, and instructed to contact TRT(TRS) for onwards clearance. ## Charts -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/aerodromes/classc/Townsville.md b/docs/aerodromes/classc/Townsville.md index acc1330ae..980a69902 100644 --- a/docs/aerodromes/classc/Townsville.md +++ b/docs/aerodromes/classc/Townsville.md @@ -13,7 +13,7 @@ | **Townsville ACD** | **Townsville Delivery** | **128.100** | **TL_DEL** | | Townsville ATIS | | 133.500 | YBTL_ATIS | -!!! note +!!! 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} ## Airspace @@ -29,7 +29,7 @@ For non-RNAV approved IFR aircaft with a wake turbulence category of medium or g For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or RADAR SID ## Charts -!!! note +!!! 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} ## Miscellaneous diff --git a/docs/aerodromes/classc/Williamtown.md b/docs/aerodromes/classc/Williamtown.md index 7f4bc6f02..697960f4d 100644 --- a/docs/aerodromes/classc/Williamtown.md +++ b/docs/aerodromes/classc/Williamtown.md @@ -22,7 +22,7 @@ WLM ADC owns the airspace within the WLM MIL CTR A (`SFC`-`A050`). This may be a ## Charts -!!! note +!!! 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} ## Coordination diff --git a/docs/aerodromes/procedural/Woomera.md b/docs/aerodromes/procedural/Woomera.md index 323a7e6d2..2ec08a470 100644 --- a/docs/aerodromes/procedural/Woomera.md +++ b/docs/aerodromes/procedural/Woomera.md @@ -24,5 +24,5 @@ Surveillance coverage can be expected to be available at all levels in the WR CT Coordination is not required between WR ADC and ASP(WRA). Aircraft entering ASP(WRA) airspace shall be handed off, and instructed to contact ASP(WRA) for onwards clearance. ## Charts -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/terminal/amberleyoakey.md b/docs/terminal/amberleyoakey.md index af71c618f..5ad5b18cf 100644 --- a/docs/terminal/amberleyoakey.md +++ b/docs/terminal/amberleyoakey.md @@ -92,7 +92,7 @@ Aircraft will make a visual departure in the circuit direction and fly overhead Charts for the Coded Departures may be in YAMB AD2 Supplements 6.2.25.11 available here: [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new} ## Charts -!!! note +!!! 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} ## Coordination diff --git a/docs/terminal/curtin.md b/docs/terminal/curtin.md index 644271988..6e0ba4512 100644 --- a/docs/terminal/curtin.md +++ b/docs/terminal/curtin.md @@ -51,5 +51,5 @@ Any aircraft not meeting the above criteria must be prior coordinated to ENR. #### Arrivals The Standard assignable level from ASH to CIN TCU is `F130`, and tracking via CIN VOR. All other aircraft must be prior coordinated. -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/terminal/darwin.md b/docs/terminal/darwin.md index 64d12e5ad..f79fc1b17 100644 --- a/docs/terminal/darwin.md +++ b/docs/terminal/darwin.md @@ -51,7 +51,7 @@ e) Runway 11 and Runway 18; f) Runway 11 only. ## Charts -!!! note +!!! 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} ## Miscellaneous diff --git a/docs/terminal/learmonth.md b/docs/terminal/learmonth.md index 8a4db8dc4..24e315e27 100644 --- a/docs/terminal/learmonth.md +++ b/docs/terminal/learmonth.md @@ -52,6 +52,6 @@ Any aircraft not meeting the above criteria must be prior coordinated to ENR. #### Arrivals The Standard assignable level from OLW to LM TCU is `F130`, and tracking via LM VOR. All other aircraft must be prior coordinated. -!!! note +!!! 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} diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 2ca695cfb..d12ce26af 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -6,5 +6,5 @@ Reserved. -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/terminal/scherger.md b/docs/terminal/scherger.md index c4afe3d83..7569e5eca 100644 --- a/docs/terminal/scherger.md +++ b/docs/terminal/scherger.md @@ -52,5 +52,5 @@ Any aircraft not meeting the above criteria must be prior coordinated to ENR. #### Arrivals The Standard assignable level from ARA to SG TCU is `F130`, and tracking via WP VOR. All other aircraft must be prior coordinated. -!!! note +!!! 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} \ No newline at end of file diff --git a/docs/terminal/tindal.md b/docs/terminal/tindal.md index 7aa5cccbc..8ff90b453 100644 --- a/docs/terminal/tindal.md +++ b/docs/terminal/tindal.md @@ -24,7 +24,7 @@ All of which are reclassified as **Class C** when active, and TN APP has Control TN APP may increase the upper limit of the Restricted Areas and their airspace. This must be either published by NOTAM, or negotiated with TRT(TRS) if online. ## Charts -!!! note +!!! 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} ## Arrival/Departure Gates @@ -94,7 +94,7 @@ All other aircraft coming from TRT(TRS) CTA will be **Heads-up** Coordinated to !!! phraseology **TN ADC** -> **TN TCU**: "Next, ASY01, runway 32" - **TN TCU** -> **TN ADC**: "ASY01, Assigned Heading Right 030, unrestricted" - **TN ADC** -> **TN TCU**: "Assigned Heading Heading Right 030, ASY01" + **TN TCU** -> **TN ADC**: "ASY01, Heading 030, unrestricted" + **TN ADC** -> **TN TCU**: "Heading 030, ASY01" The Standard Assignable level from TN ADC to TN TCU is the lower of `F180` or the `RFL`. \ No newline at end of file diff --git a/docs/terminal/townsville.md b/docs/terminal/townsville.md index 372ec80fc..e87ff0f5e 100644 --- a/docs/terminal/townsville.md +++ b/docs/terminal/townsville.md @@ -23,7 +23,7 @@ TL TCU owns the Class C and G airspace within 36 DME TL from `SFC` to `F180` TL ADC owns the Class C airspace in the TL CTR (Extends to 7NM from the thresholds of Runway 01/19) from `SFC` to `A015`. This airspace is designed to facilitate Helicopter Traffic and Ciruit Traffic. ## Charts -!!! note +!!! 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} ## Coordination diff --git a/docs/terminal/williamtown.md b/docs/terminal/williamtown.md index 909267afa..c1168d6a6 100644 --- a/docs/terminal/williamtown.md +++ b/docs/terminal/williamtown.md @@ -37,7 +37,7 @@ When WLM ADC is online, they own the airspace within the WLM MIL CTR A (`SFC`-`A ## Charts -!!! note +!!! 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} ## Coordination From 3f78bad8c4ad3ebf30c05aa83d9fda9149709568 Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Mon, 23 Dec 2024 11:28:15 +1100 Subject: [PATCH 07/14] Pearce TCU positions --- docs/terminal/pearce.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index d12ce26af..6fc774283 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -4,7 +4,15 @@ --8<-- "includes/abbreviations.md" -Reserved. +## Positions + +| Name | Callsign | Frequency | Login ID | +| **Pearce TCU** | **Pearce Appraoch** | **130.200** | **PE_APP** | + +## Airspace + + + !!! 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} \ No newline at end of file From 9162ef886fc35645f061a7317acc2770984644ff Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Mon, 23 Dec 2024 11:59:47 +1100 Subject: [PATCH 08/14] Pearce Position updated --- docs/terminal/pearce.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 6fc774283..7815609c9 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -7,7 +7,8 @@ ## Positions | Name | Callsign | Frequency | Login ID | -| **Pearce TCU** | **Pearce Appraoch** | **130.200** | **PE_APP** | +| **Pearce Approach** | **Pearce Approach** | **130.200** | **PE_APP** | +| **Pearce Departures** | **Peaarce Departures** | **123.300** | **PE_DEP** | ## Airspace From 4ab7ac30060cc651db520792a3ccaecc998148c4 Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Mon, 23 Dec 2024 12:27:44 +1100 Subject: [PATCH 09/14] Airspace --- docs/terminal/pearce.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 7815609c9..9cd002e14 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -11,7 +11,7 @@ | **Pearce Departures** | **Peaarce Departures** | **123.300** | **PE_DEP** | ## Airspace - +The PEA TMA's lateral boundaries are defined by a 20-nautical mile arc within R155A/M166 and the southern boundary of R153. Vertically, it extends from the 'SFC' to 'A050' feet within R155A/M166 and to NOTOAM within R153. From c2e48e08c691683bbc7a33327a09415f15bdf098 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Mon, 23 Dec 2024 13:23:15 +1100 Subject: [PATCH 10/14] revert ypea ad --- docs/aerodromes/classc/Pearce.md | 43 ++++++++++++++------------------ 1 file changed, 19 insertions(+), 24 deletions(-) diff --git a/docs/aerodromes/classc/Pearce.md b/docs/aerodromes/classc/Pearce.md index 593bff6f3..75d67b449 100644 --- a/docs/aerodromes/classc/Pearce.md +++ b/docs/aerodromes/classc/Pearce.md @@ -19,23 +19,11 @@ PE ADC owns the airspace within the Pearce CIRA (**5nm** Radius of YPEA ARP, loc ### SID Selection All aircraft shall be assigned the **Radar** SID by default. -### SID Selection -Aircraft planned via **WAMAL**, **GUNOK**, **ALKIMOS**, **MULLALOO**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. -Aircraft who are not planned via those points or who are negative RNAV may be assigned a RADAR SID or a visual departure. - -!!! Note - Due to Civil Traffic Arriving from the North, the GUNOK SID will have an altitude assignment of A030. - - ### Level Assignment -The Standard Assignable Level from **PE ADC** to **PE TCU** is: -a) The Lower of `F130` or `RFL` for Aircraft assigned via Procedural or RNAV SID. -b) `F130` for Aircraft assigned a Coded Departure. - -#### Miscellaneous +vatSys does not have Procedural SIDs built-in for YPEA. As long as ATC is familiar with the chart, and the pilot is able, aircraft may be assigned **Procedural SIDs** *on pilot request*. ## Miscellaneous ### Circuit Operations -The Circuit Area Airspace is allocated to be within 5nm of the YPEA ARP from `SFC` to `A035'. Aircraft can be instructed to extend outside of this airspace by ATC for traffic management. Hawks have circuit altitude of A016 while both 2FTS and RSAF PC21s are assigned A012. +Aircraft can be instructed to extend outside of this airspace by ATC for traffic management, following coordination with the appropriate sectors. HAWKs have circuit altitude of `A016`, while both 2FTS and RSAF PC21s are assigned `A012`. @@ -57,21 +45,28 @@ HAWKs have circuit altitude of `A016`, while both 2FTS and RSAF PC21s are assign | Runway | Direction Initial | Inital Altitude | ------ | ------------------|----------------| -| 5 | Any | A010 -| 18L | Left/Straight | A015 | Right | A010 -| 18R | Left/Straight | A015 | Right | A010 -| 23 | Any | A015 -| 36L | Left | A010 | Right | A015 -| 36R | Left | A010 | Right | A015 +| 05 | Any | A010 | +| 18L | Left/Straight
Right | A015
A010 | +| 18R | Left/Straight
Right | A015
A010 | +| 23 | Any | A015 | +| 36L | Left
Right | A010
A015 | +| 36R | Left
Right | A010
A015 | ## Coordination ### PE TCU 'Next' coordination is required from PE ADC to PE TCU for all aircraft. -!!! example - **PE ADC** -> **PE TCU**: "Next, ASY01, runway 36R" - **PE TCU** -> **PE ADC**: "ASY01, Assigned Heading Right 030, unrestricted" - **PE ADC** -> **PE TCU**: "Assigned Heading Heading Right 030, ASY01" +!!! phraseology + **PE ADC** -> **PE TCU**: "Next, ASY01, runway 36L" + **PE TCU** -> **PE ADC**: "ASY01, Heading 030, unrestricted" + **PE ADC** -> **PE TCU**: "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 + ## 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} \ No newline at end of file From 552037755a6a61ebfdd07da705bc1b54c30f44e7 Mon Sep 17 00:00:00 2001 From: ST6-Bravo Date: Mon, 23 Dec 2024 16:43:40 +1100 Subject: [PATCH 11/14] Airspace releases --- docs/terminal/pearce.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 9cd002e14..3204a618c 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -13,6 +13,17 @@ ## Airspace The PEA TMA's lateral boundaries are defined by a 20-nautical mile arc within R155A/M166 and the southern boundary of R153. Vertically, it extends from the 'SFC' to 'A050' feet within R155A/M166 and to NOTOAM within R153. +## Coordination +### PIY +#### Airspace +Any airspace releases from the default setup must be coordinated and agreed upon with PIY. It is also good practice to remind them of any airspace releases that may be active due to NOTAMs. + +## Merlo Release +Merlo Airspace is released to Pearce TMA when duty runways are RWY 36L/R. PEA TMA takes other the PTH airspace that lies within 9-10 TAC above R153, for 'SFC' to 'A040'. If Merlo Release is inactive, instrument approaches will be delayed or denied. + +## Gnangara Release +Gnangara Airspace is released to Pearace TMA when duty runways are RWY 36L/R or RWY 5 and Merlo Release is unaviliable. PEA TMA takes other the PTH airspace between 9-11 DME of Perth from 'SFC' to 'A010.' + !!! abstract "Reference" From 6e0ac85b079ba3df09d9e8a3f84aecead1610cc1 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Mon, 23 Dec 2024 19:03:57 +1100 Subject: [PATCH 12/14] pe tcu, enr, stars --- docs/enroute/Melbourne Centre/PIY.md | 46 +++++++++++++++++++++++++--- docs/terminal/pearce.md | 41 +++++++++++++++++++------ 2 files changed, 73 insertions(+), 14 deletions(-) diff --git a/docs/enroute/Melbourne Centre/PIY.md b/docs/enroute/Melbourne Centre/PIY.md index 17a654b80..2ee14e1d6 100644 --- a/docs/enroute/Melbourne Centre/PIY.md +++ b/docs/enroute/Melbourne Centre/PIY.md @@ -80,21 +80,21 @@ With the Southwest Plan active, arrivals shall be processed to either runway 21 ### Northeast Plan With the Northeast Plan active (runways 03 and 06 in use), all arrivals shall be processed to runway 03. -## YPJT Arrivals -To facilitate smooth movement of traffic in the Perth TCU, IFR Arrivals to YPJT shall be assigned a STAR in accordance with the *YPPH Runway Mode*: +## YPJT/YPEA Arrivals +To facilitate smooth movement of traffic in the Perth TCU, IFR Arrivals to YPJT and YPEA shall be assigned a STAR in accordance with the *YPPH Runway Mode*: | Feeder Fix | 03/06 | 21/24 | | ------------------- | ----- | ----- | -| WOORA | Golf | WOORA PH JT (No STAR) | +| JULIM | Golf (via WOORA) | **YPJT**: JULIM WOORA PH JT (No STAR)
**YPEA**: JULIM PEA (No STAR) | +| SAPKO | Golf (via WOORA) | **YPJT**: SAPKO WOORA PH JT (No STAR)
**YPEA**: SAPKO PEA (No STAR) | | LAVEX | Golf | Romeo | | KABLI (Jet) | Golf | Romeo | | MALUP (Non-Jet) | Whiskey | Romeo (via KABLI) | !!! note - Assigning a STAR to YPJT Arrivals still does not meet [voiceless coordination requirements](#arrivalsoverfliers) to PH TCU. All YPJT Arrivals must be **heads-up coordinated**, including those assigned a STAR. + Assigning a STAR to YPJT Arrivals still does not meet [voiceless coordination requirements](#arrivalsoverfliers) to PH TCU or PE TCU. All YPJT/YPEA Arrivals must be **heads-up coordinated**, including those assigned a STAR. ## STAR Clearance Expectation - ### Handoff Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff: @@ -162,3 +162,39 @@ Aircraft must have their identification terminated and be instructed to make a p !!! phraseology **PIY**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" + +### PE TCU +#### Airspace +The PE TCU is responsible for the airspace within **20 TACAN** of PEA (that is continained within **Pearce SUA**), `SFC` to `A050`. By default, PE TCU does not border any HYD CTA. + +This is all reclassified to **Class C** when PE TCU is online. + +!!! abstract "Reference" + A helpful diagram can be found in [Pearce FIHA AD2 Supp](https://ais-af.airforce.gov.au/australian-aip){target=new}, Section 2.2.2. + +Additional airspace releases may be NOTAM'd, or coordinated between PE TCU, PH TCU and HYD, to facilitate Military Operations. + +!!! phraseology + **PE TCU** -> **PH TCU**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with HYD" + **PH TCU** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with HYD" + + **PE TCU** -> **HYD**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PH TCU" + **HYD** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PH TCU" + +#### Departures +Voiceless for all aircraft: + +- Tracking via **AVNEX**; and +- Assigned the lower of `F180` or the `RFL` + +All other aircraft going to HYD CTA will be **Heads-up** Coordinated by PE TCU, if coming from CTA (ie, only if PE TCU has assumed more airspace than the default setup). + +#### Arrivals/Overfliers +If PE TCU has assumed additional airspace from the default, and as such, PE TCU CTA borders HYD CTA, then: + +Voiceless for all aircraft: + +- Tracking from **JULIM** or **SAPKO** DCT **PEA**; and +- Assigned `A090` + +All other arrivals/overfliers coming from HYD CTA must be **Heads-up** Coordinated to PE TCU prior to **20nm** from the boundary. \ No newline at end of file diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 3204a618c..1c4fd9519 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -7,24 +7,47 @@ ## Positions | Name | Callsign | Frequency | Login ID | +| ------------------ | --------------| -------------- | ---------------- | | **Pearce Approach** | **Pearce Approach** | **130.200** | **PE_APP** | -| **Pearce Departures** | **Peaarce Departures** | **123.300** | **PE_DEP** | ## Airspace -The PEA TMA's lateral boundaries are defined by a 20-nautical mile arc within R155A/M166 and the southern boundary of R153. Vertically, it extends from the 'SFC' to 'A050' feet within R155A/M166 and to NOTOAM within R153. +The PE TCU is responsible for the airspace within **20 TACAN** of PEA (that is continained within **Pearce SUA**), `SFC` to `A050`. By default, PE TCU does not border any HYD CTA. + +This is all reclassified to **Class C** when PE TCU is online. + +!!! abstract "Reference" + A helpful diagram can be found in [Pearce FIHA AD2 Supp](https://ais-af.airforce.gov.au/australian-aip){target=new}, Section 2.2.2. + +### Additional Releases +Additional airspace releases may be NOTAM'd, or coordinated between PE TCU, PH TCU and HYD, to facilitate Military Operations. + +!!! phraseology + **PE TCU** -> **PH TCU**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with HYD" + **PH TCU** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with HYD" + + **PE TCU** -> **HYD**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PH TCU" + **HYD** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PH TCU" ## Coordination -### PIY -#### Airspace -Any airspace releases from the default setup must be coordinated and agreed upon with PIY. It is also good practice to remind them of any airspace releases that may be active due to NOTAMs. +### HYD +#### Departures +Voiceless for all aircraft: + +- Tracking via **AVNEX**; and +- Assigned the lower of `F180` or the `RFL` + +All other aircraft going to HYD CTA must be **Heads-up** Coordinated by PE TCU, if coming from CTA (ie, only if PE TCU has assumed more airspace than the default setup). -## Merlo Release -Merlo Airspace is released to Pearce TMA when duty runways are RWY 36L/R. PEA TMA takes other the PTH airspace that lies within 9-10 TAC above R153, for 'SFC' to 'A040'. If Merlo Release is inactive, instrument approaches will be delayed or denied. +#### Arrivals/Overfliers +If PE TCU has assumed additional airspace from the default, and as such, PE TCU CTA borders HYD CTA, then: -## Gnangara Release -Gnangara Airspace is released to Pearace TMA when duty runways are RWY 36L/R or RWY 5 and Merlo Release is unaviliable. PEA TMA takes other the PTH airspace between 9-11 DME of Perth from 'SFC' to 'A010.' +Voiceless for all aircraft: +- Tracking from **JULIM** or **SAPKO** DCT **PEA**; and +- Assigned `A090` +All other arrivals/overfliers coming from HYD CTA will be **Heads-up** Coordinated to PE TCU prior to **20nm** from the boundary. +## 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} \ No newline at end of file From 2ea19998423c5a840a2715203f002062a52a2dab Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Tue, 24 Dec 2024 19:54:22 +1100 Subject: [PATCH 13/14] pea/ph tcu coord --- docs/enroute/Melbourne Centre/PIY.md | 8 ++++---- docs/terminal/pearce.md | 13 ++++++++++--- docs/terminal/perth.md | 8 ++++++-- 3 files changed, 20 insertions(+), 9 deletions(-) diff --git a/docs/enroute/Melbourne Centre/PIY.md b/docs/enroute/Melbourne Centre/PIY.md index 2ee14e1d6..0a8214734 100644 --- a/docs/enroute/Melbourne Centre/PIY.md +++ b/docs/enroute/Melbourne Centre/PIY.md @@ -36,7 +36,7 @@ The CPDLC Station Code is `YPIY`. ## Sector Responsibilities ### Pingelly (PIY) -PIY will provide final sequencing actions to ensure aircraft comply with their FF times prior to entering the Perth TCU. PIY is also responsible for issuing STAR Clearances for aircraft bound for YPJT, and Non-jets bound for YPPH and YPEA. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. +PIY will provide final sequencing actions to ensure aircraft comply with their FF times prior to entering the Perth TCU. PIY is also responsible for issuing STAR Clearances for aircraft bound for YPJT and YPEA, and Non-jets bound for YPPH. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. For aircraft overflying the PH TCU place `O/FLY` in the LABEL DATA field. @@ -187,14 +187,14 @@ Voiceless for all aircraft: - Tracking via **AVNEX**; and - Assigned the lower of `F180` or the `RFL` -All other aircraft going to HYD CTA will be **Heads-up** Coordinated by PE TCU, if coming from CTA (ie, only if PE TCU has assumed more airspace than the default setup). +All other aircraft going to PIY CTA will be **Heads-up** Coordinated by PE TCU, if coming from CTA (ie, only if PE TCU has assumed more airspace than the default setup). #### Arrivals/Overfliers -If PE TCU has assumed additional airspace from the default, and as such, PE TCU CTA borders HYD CTA, then: +If PE TCU has assumed additional airspace from the default, and as such, PE TCU CTA borders PIY CTA, then: Voiceless for all aircraft: - Tracking from **JULIM** or **SAPKO** DCT **PEA**; and - Assigned `A090` -All other arrivals/overfliers coming from HYD CTA must be **Heads-up** Coordinated to PE TCU prior to **20nm** from the boundary. \ No newline at end of file +All other arrivals/overfliers coming from PIY CTA must be **Heads-up** Coordinated to PE TCU prior to **20nm** from the boundary. \ No newline at end of file diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 1c4fd9519..25f635b86 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -29,17 +29,17 @@ Additional airspace releases may be NOTAM'd, or coordinated between PE TCU, PH T **HYD** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PH TCU" ## Coordination -### HYD +### PIY #### Departures Voiceless for all aircraft: - Tracking via **AVNEX**; and - Assigned the lower of `F180` or the `RFL` -All other aircraft going to HYD CTA must be **Heads-up** Coordinated by PE TCU, if coming from CTA (ie, only if PE TCU has assumed more airspace than the default setup). +All other aircraft going to PIY CTA must be **Heads-up** Coordinated by PE TCU, if coming from CTA (ie, only if PE TCU has assumed more airspace than the default setup). #### Arrivals/Overfliers -If PE TCU has assumed additional airspace from the default, and as such, PE TCU CTA borders HYD CTA, then: +If PE TCU has assumed additional airspace from the default, and as such, PE TCU CTA borders PIY CTA, then: Voiceless for all aircraft: @@ -48,6 +48,13 @@ Voiceless for all aircraft: All other arrivals/overfliers coming from HYD CTA will be **Heads-up** Coordinated to PE TCU prior to **20nm** from the boundary. +### PH TCU +**All aircraft** transiting between PE TCU and PH TCU must be heads-up coordinated prior to the boundary. + +!!! phraseology + **PE TCU** -> **PH TCU**: "Airborne YPEA, PHNX11" + **PH TCU** -> **PE TCU**: "PHNX11, F180" + ## 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} \ No newline at end of file diff --git a/docs/terminal/perth.md b/docs/terminal/perth.md index 461822455..58f326638 100644 --- a/docs/terminal/perth.md +++ b/docs/terminal/perth.md @@ -203,6 +203,10 @@ VFR aircraft require a level readback. **PH TCU** -> **JT ADC**: "via RNAV-Z RWY 06L, FD416, circling to land RWY 24R" **JT ADC** -> **PH TCU**: "FD416, RNAV-Z RWY 06L with a circle to land RWY 24R" -### PEA ADC -Reserved. +### PE TCU +**All aircraft** transiting between PE TCU and PH TCU must be heads-up coordinated prior to the boundary. +!!! phraseology + **PH TCU** -> **PE TCU**: "via PH, VIPR22, Requesting DCT PEA for ILS-Z 18L" + **PE TCU** -> **PH TCU**: "VIPR22, DCT PEA, A035" + **PH TCU** -> **PE TCU**: "A035, VIPR22" \ No newline at end of file From 6776142a1dbc14b73e1d28d62cb21e52d5e28bc8 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Tue, 24 Dec 2024 19:58:31 +1100 Subject: [PATCH 14/14] PIY HYD fix --- docs/terminal/pearce.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/terminal/pearce.md b/docs/terminal/pearce.md index 25f635b86..d9757a344 100644 --- a/docs/terminal/pearce.md +++ b/docs/terminal/pearce.md @@ -11,7 +11,7 @@ | **Pearce Approach** | **Pearce Approach** | **130.200** | **PE_APP** | ## Airspace -The PE TCU is responsible for the airspace within **20 TACAN** of PEA (that is continained within **Pearce SUA**), `SFC` to `A050`. By default, PE TCU does not border any HYD CTA. +The PE TCU is responsible for the airspace within **20 TACAN** of PEA (that is continained within **Pearce SUA**), `SFC` to `A050`. By default, PE TCU does not border any PIY CTA. This is all reclassified to **Class C** when PE TCU is online. @@ -19,14 +19,14 @@ This is all reclassified to **Class C** when PE TCU is online. A helpful diagram can be found in [Pearce FIHA AD2 Supp](https://ais-af.airforce.gov.au/australian-aip){target=new}, Section 2.2.2. ### Additional Releases -Additional airspace releases may be NOTAM'd, or coordinated between PE TCU, PH TCU and HYD, to facilitate Military Operations. +Additional airspace releases may be NOTAM'd, or coordinated between PE TCU, PH TCU and PIY, to facilitate Military Operations. !!! phraseology - **PE TCU** -> **PH TCU**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with HYD" - **PH TCU** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with HYD" + **PE TCU** -> **PH TCU**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PIY" + **PH TCU** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PIY" - **PE TCU** -> **HYD**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PH TCU" - **HYD** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PH TCU" + **PE TCU** -> **PIY**: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PH TCU" + **PIY** -> **PE TCU**: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PH TCU" ## Coordination ### PIY