Merge pull request #402 from ST6-Bravo/YPEA

YPEA Procedures

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}

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

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}

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}

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}

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

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 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
+All aircraft shall be assigned the **Radar** SID by default.
+
+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 
+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
+
+### Circuit Direction
+
+| Runway | Direction |
+| ------ | ----------|
+| 05      | Left  |
+| 18L    | Right |
+| 18R    | Right |
+| 23     | Right |
+| 36L    | Left  |
+| 36R    | Left  |
+
+### Initial and Pitch Procedures 
+
+| Runway | Direction Initial | Inital Altitude
+| ------ | ------------------|----------------|
+| 05     | Any | A010 |
+| 18L    | Left/Straight<br>Right | A015<br>A010 |
+| 18R    | Left/Straight<br>Right | A015<br>A010 |
+| 23     | Any | A015 |
+| 36L    | Left<br>Right | A010<br>A015 |
+| 36R    | Left<br>Right | A010<br>A015 |
+
+## Coordination
+### PE TCU
+'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
+
+## 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}

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

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}

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}

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

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
 </figure>
 
 ## 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

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}

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.
 
@@ -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)<br>**YPEA**: JULIM PEA (No STAR) |
+| SAPKO | Golf (via WOORA) | **YPJT**: SAPKO WOORA PH JT (No STAR)<br>**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
+    <span class="hotline">**PE TCU** -> **PH TCU**</span>: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with HYD"   
+    <span class="hotline">**PH TCU** -> **PE TCU**</span>: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with HYD"  
+
+    <span class="hotline">**PE TCU** -> **HYD**</span>: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PH TCU"   
+    <span class="hotline">**HYD** -> **PE TCU**</span>: "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 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 PIY CTA, then:
+
+Voiceless for all aircraft:
+
+- Tracking from **JULIM** or **SAPKO** DCT **PEA**; and 
+- Assigned `A090`
+
+All other arrivals/overfliers coming from PIY CTA must be **Heads-up** Coordinated to PE TCU prior to **20nm** from the boundary.

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}

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

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}
 

docs/terminal/pearce.md

@@ -4,7 +4,57 @@
 
 --8<-- "includes/abbreviations.md"
 
-Reserved.
+## Positions
 
-!!! note
+| Name               | Callsign       | Frequency        | Login ID              |
+| ------------------ | --------------| -------------- | ---------------- |
+| **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 PIY 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 PIY, to facilitate Military Operations.
+
+!!! phraseology
+    <span class="hotline">**PE TCU** -> **PH TCU**</span>: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PIY"   
+    <span class="hotline">**PH TCU** -> **PE TCU**</span>: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PIY"  
+
+    <span class="hotline">**PE TCU** -> **PIY**</span>: "Request release of R155 Alpha and Bravo, SFC to F180, for Military Operations. My onwards with PH TCU"   
+    <span class="hotline">**PIY** -> **PE TCU**</span>: "R155 Alpha and Bravo, SFC to F180, Released to you. Your onwards with PH TCU"  
+
+## Coordination
+### PIY
+#### Departures
+Voiceless for all aircraft:
+
+- Tracking via **AVNEX**; and  
+- Assigned the lower of `F180` or the `RFL`
+
+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 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 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
+    <span class="hotline">**PE TCU** -> **PH TCU**</span>: "Airborne YPEA, PHNX11"   
+    <span class="hotline">**PH TCU** -> **PE TCU**</span>: "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}

docs/terminal/perth.md

@@ -203,6 +203,10 @@ VFR aircraft require a level readback.
     <span class="hotline">**PH TCU** -> **JT ADC**</span>: "via RNAV-Z RWY 06L, FD416, circling to land RWY 24R"  
     <span class="hotline">**JT ADC** -> **PH TCU**</span>: "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
+    <span class="hotline">**PH TCU** -> **PE TCU**</span>: "via PH, VIPR22, Requesting DCT PEA for ILS-Z 18L"   
+    <span class="hotline">**PE TCU** -> **PH TCU**</span>: "VIPR22, DCT PEA, A035"  
+    <span class="hotline">**PH TCU** -> **PE TCU**</span>: "A035, VIPR22"   

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}

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
     <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Next, ASY01, runway 32"  
-    <span class="hotline">**TN TCU** -> **TN ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"  
-    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Assigned Heading Heading Right 030, ASY01"  
+    <span class="hotline">**TN TCU** -> **TN ADC**</span>: "ASY01, Heading 030, unrestricted"  
+    <span class="hotline">**TN ADC** -> **TN TCU**</span>: "Heading 030, ASY01"  
 
 The Standard Assignable level from TN ADC to TN TCU is the lower of `F180` or the `RFL`.