Merge pull request #255 from vatpac-technology/alex-dev

AIRAC 2406, other small fixes

docs/aerodromes/classc/Adelaide.md

@@ -83,10 +83,10 @@ This allows aircraft on the Victor STAR from the west to join a visual right bas
 Between the hours of 1330-2030 UTC (1230-1930 UTC HDS), AD ADC may elect to simulate Curfew operations, ie: **Runway 05 for arrivals, Runway 23 for departures**. When this is in operation, the ATIS shall include `CURFEW IN OPERATION UNTIL (time) ZULU`.
 
 ## SID Selection
-Jet Aircraft planned via **PANKI**, **BENDO**, **GILES**, **HAWKY**, **ORBUN**. or **SEDAN**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID.
+Jet Aircraft planned via **AVDEN**, **BENDO**, **GILES**, **AREPA**, **ORBUN**. or **UPROT**, shall be assigned the **Procedural SID** that terminates at the appropriate waypoint. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID.
 
 !!! example
-    Jet Aircraft planned via PANKI, assigned runway 23, shall be given the PANKI SID.
+    Jet Aircraft planned via AVDEN, assigned runway 23, shall be given the AVDEN SID.
 
 a) Non-Jet Aircraft; or  
 b) Aircraft using Runway 12/30; or  
@@ -125,14 +125,14 @@ When **AAE** is online, the AD TCU airspace is split down the 05/23 Runway Centr
 | Tracking via            | Departure Runway      | Departures Controller        |
 | ------------------ | -------------- | ---------------- |
 | VILAD   | 05/23/12   | AAE         |
-| SEDAN    | 05/23/12   | AAE         |
-| PANKI    | 05/23/12   | AAE         |
+| UPROT    | 05/23/12   | AAE         |
+| AVDEN    | 05/23/12   | AAE         |
 | BENDO     | 05/23/12 | AAE          | 
 | ALBUT    | 05/23/12  | AAE          | 
 | EEMUE    | 05/23/30  | AAW          | 
 | GILES   | 05/23/30  | AAW          | 
 | YORKE    | 05/23/30  | AAW          | 
-| HAWKY    | 05/23/30  | AAW          | 
+| AREPA    | 05/23/30  | AAW          | 
 | HOLIT    | 05/23/30  | AAW          | 
 | ORBUN    | 05/23/30  | AAW          | 
 | All   | 12  | AAE          | 

docs/aerodromes/classc/Perth.md

@@ -28,8 +28,8 @@ With the Southwest Plan active, all departures shall be assigned runway 21. Arri
 | JULIM | 21 |
 | SAPKO | 21 |
 | IPMOR | 21 |
-| BEVLY | 24 (or 21 if operationally required) |
-| GRENE | 24 |
+| KABLI | 24 (or 21 if operationally required) |
+| LAVEX | 24 |
 | SOLUS | 24 |
 
 The ATIS shall notify `EXPECT ILS APCH`.

docs/aerodromes/classd/Camden.md

@@ -104,10 +104,10 @@ CN ADC must advise SY TCU when the aircraft has called 'Ready'. In response to a
 
 !!! example
     <span class="hotline">**CN ADC** -> **SRI**</span>: "Ready, MHQ, Runway 06"  
-    <span class="hotline">**SRI** -> **CN ADC**</span>: "MHQ, traffic is MEH, an IFR AC50, tracking SHL RAKSO SBKWI, A035, estimate RAKSO time 35" (or "No Reported IFR Traffic")  
-    <span class="hotline">**CN ADC** -> **SRI**</span>: "Traffic is MEH tracking SHL RAKSO SBKWI A035, RAKSO at 35"  
+    <span class="hotline">**SRI** -> **CN ADC**</span>: "MHQ, traffic is MEH, an IFR AC50, tracking SHL RAKSO SB2WI, A035, estimate RAKSO time 35" (or "No Reported IFR Traffic")  
+    <span class="hotline">**CN ADC** -> **SRI**</span>: "Traffic is MEH tracking SHL RAKSO SB2WI A035, RAKSO at 35"  
 
-    **CN ADC:** "MHQ, traffic is MEH, IFR AC50 tracking SHL RAKSO SBKWI at A035, estimating RAKSO at time 35, runway 06, cleared for takeoff"  
+    **CN ADC:** "MHQ, traffic is MEH, IFR AC50 tracking SHL RAKSO SB2WI at A035, estimating RAKSO at time 35, runway 06, cleared for takeoff"  
     **MHQ:** "Runway 06, cleared for takeoff, MHQ"
 
     **CN ADC:** "MHQ, contact Sydney Centre on 124.55"  

docs/aerodromes/classd/Jandakot.md

@@ -27,7 +27,7 @@ JT ADC is responsible for the Class D airspace in the JT CTR `SFC` to `A015`.
 </figure>
 
 ## Fixed-Wing Operations
-### VFR Inbound Procedures
+### VFR Arrivals
 VFR aircraft will report inbound at BOAT, POWR, OAKF or RUSS at `A015`. JT ADC will instruct aircraft to maintain `A015` or remain outside the control zone (workload permitting). Aircraft will then report again at ADWD when inbound from BOAT or POWR, or FDL when inbound from OAKF or RUSS. They should then be instructed to join the circuit as below:
 
 | VFR Approach Point | RWYs 06  | RWYs 24 | RWY 12 | RWY 30 |
@@ -40,7 +40,7 @@ All aircraft will arrive on runway 06L/24R or 12/30.
 !!! note
     Circuit joining instructions given without an assigned altitude imply clearance to conduct the visual approach. There is no need to clear these aircraft for a visual approach.
 
-### VFR Outbound Procedures
+### VFR Departures
 VFR aircraft should report ready to **JT ADC** with their departure intentions.  A takeoff clearance constitutes a clearance to depart the zone by extending the pilot's requested leg of the circuit.  Aircraft departing the zone into class G airspace will transfer to area frequency upon leaving the zone, **no explicit frequency transfer is given to these aircraft**.
 
 Aircraft departing a leg of the circuit will climb to and maintain the following levels until clear of the zone:  
@@ -50,6 +50,18 @@ VFR aircraft will depart via set outbound departure routes. Aircraft will track
 
 Departures via FREM and YGB will depart on runway 06L/24R. Runway 06R/24L is used for circuit traffic and departures via SHOP.
 
+### IFR Arrivals
+**PH TCU** will coordinate all IFR arrivals in accordance with coordination procedures.
+
+### IFR Departures
+All IFR Departures must be assigned the most appropriate SID in accordance with the aircraft's direction of flight.
+
+| Direction | SID   |
+| -------| ----- |
+| South/West    | TONEG  |
+| North/North-west    | ISPET |
+| East/North-east    | SCARP |
+
 ### Circuits
 The circuit direction changes depending on tower opening hours and runway being used.
 
@@ -64,19 +76,13 @@ The circuit direction changes depending on tower opening hours and runway being
 
 Circuits to be flown at `A010`
 
-## IFR Inbound Procedures
-Aircraft arriving from the Perth Class C in VMC will track via CNB. These aircraft will contract **JT ADC** approaching CNB and will be issued circuit joining instructions.  
-Aircraft in IMC will track inbound via an instrument approach.  
-**PH TCU** will coordinate all IFR arrivals in accordance with coordination procedures.
-
 ## Helicopter Operations
 ### General
 Unless otherwise depicted in the `ERSA FAC YPJT`, all helicopters must comply with fixed wing procedures.
 
 ### Circuits
 Circuits are conducted within the lateral confines of the fixed-wing circuit at `A008`, in the same direction as the current runway config.  The termination point of the circuit is the Main Pad.
 
-
 ## ATIS
 ### Runway Nomination
 The ATIS must indicate the current runway config and nominate what each parallel runway is being used for.  The northern runway (06L/24R) is primarily used for VFR arrivals and departures, the southern runway (06R/24L) for circuit training and departures via `SHOP`, and the cross runway (12/30) for arrivals/departures when weather is unsuitable for parallel rwunay operations.  

docs/controller-skills/annotations.md

@@ -21,6 +21,7 @@ Here is a complete list of standard annotations controllers should be entering i
 | Amended route | When assigned a route that differs to that planned | AR |
 | Assigned Heading | H(heading) | H350 |
 | Track Extended Centreline | | TEC |
+| Maintain runway heading | Surveillance environment only | MR |
 
 ## Requests, Requirements and Restrictions
 | Information | Meaning and Usage | Example |
@@ -64,35 +65,41 @@ Here is a complete list of standard annotations controllers should be entering i
 | Cruise and descent speed | (speed on cruise)/(speed on descent) | M80/300 |
 | Mach reduction on cruise | MR(difference) | MR04 |
 | Mach reduction on cruise and descent speed | MR(difference)/(descent speed) | MR04/240 |
-| Descend at minimum speed | | MIN |
-| Descend at maximum speed | Also cancels STAR speed restrictions | MX |
-| Cancel speed restrictions (250K below 10,000ft AMSL) | | CSR |
+| Maintain minimum speed | | MIN |
+| Maintain maximum speed | Also cancels all speed restrictions | MX |
+| Cancel all speed restrictions | | CSR |
 
-## Sequencing
+## Sequencing/Flow
 | Information | Meaning and Usage | Example |
 | ----------- | ----------------- | ------- |
-| Feeder fix time | F(time) | F37 |
-| Estimated landing time | L(time) | L58 |
+| Feeder fix time, and 250kts from FF | F(time) | F37 |
+| 250kts from FF | F | F |
+| Issued instruction | (instruction)< | F< |
+| Projected landing time | L(time) | L06 |
+| Projected landing time with delay | L(time)/(time after delay) | L06/09 |
+| Stream to Follow (10nm / 2mins) | F/(Callsign) | F/QFA462 |
 | Hold at position | H/(position) | H/SHARK |
 | Hold at position with stack departure time | H/(position)/(time) | H/CANTY/33 |
+| Descend at minimum speed | | MIN |
+| Descend at maximum speed | Also cancels all speed restrictions | MX |
+| Cancel all speed restrictions  | | CSR |
 
 ## Miscellaneous
 | Information | Meaning and Usage | Example |
 | ----------- | ----------------- | ------- |
 | Surveillance Information Service | Aircraft receiving service (Flight Following) | SIS |
 | Coordinated Item | C(information) | C380 |
-| Information/instruction in yet to be issued | Record information on reciept from other unit followed by a period.<br />Remove period once action is completed | MX. |
+| Information/instruction in yet to be issued | Outstanding instruction/action, followed by a period.<br />Remove period once action is completed | MX. |
 | Clearance issued to an aircraft prior to 10 NM from the lateral CTA boundary | | > |
 | No IFR Traffic | | NIT |
 | Cancel SARWATCH | IFR aircraft cancelled SARWATCH prior to circuit area or destination ETA | CSW |
 | QNH issued (en route traffic is altimeter setting region) | Q(final 2-digit value) | Q15 |
-| No level restrictions on STAR | | NHR |
+| Cancel SID/STAR level restrictions | | NHR |
 | No STAR (or cancel STAR) | | NS |
 | Aircraft has reported Visual | | V |
 | Aircraft has reported Runway in Sight | | R |
 
 ## Less commonly used
-
 | Information | Meaning and Usage | Example |
 | ----------- | ----------------- | ------- |
 | Not before | NB(time) | NB1035 |
@@ -105,15 +112,13 @@ Here is a complete list of standard annotations controllers should be entering i
 | Sight and follow | S+F/(callsign) | S+F/VOZ882 |
 | Calculated time of passing | TP(time) | TP0835 |
 | At | | @ |
-| Information is checked and correct | An aircraft has acknowledged information; or<br />Action has been taken or requirement has been met<br /><(information) | <F42 |
 | VFR-on-top | | VT |
 | Arriving at procedural tower aerodrome | Include estimate for destination navaid, track in, assigned level (if not standard assignable) and sequence number. <br /> L(time) (track) (level) (number) | L49 038 120 3 |
 | Hold at normal position with stack departure time | H/(time) | H/06 |
 | LAHSO approved | | LA |
 | Passive LAHSO only | | PL |
 | Negative LAHSO | | XX |
 | Hold at normal position | | H |
-| Stream to follow |  F/(preceding aircraft) | F/QLK41D |
 | Stream to follow by distance | F/(preceding aircraft)+(distance) | F/TFD+18 |
 | Visual departure | | VSD |
 | Expected approach time | EAT(time) | EAT23 |
@@ -125,7 +130,6 @@ Here is a complete list of standard annotations controllers should be entering i
 | Climb straight ahead | Non-surveillance environment | CSA |
 | Left turn | L(heading) | L240 |
 | Right turn | R(heading) | R020 |
-| Maintain runway heading | Surveillance environment only | MR |
 | Aircraft level | Two- or three-figure group <br />Record levels of 1000ft or higher as multiples of 100ft<br />Record levels less than 1000ft as a two-didget group beginning with zero. | FL177<br />A01 (100ft) |
 | Above Ground Level | (level)AGL | 200AGL |
 | Maintain initial level | Departure Instructions <br /> M(level) | M80 |

docs/enroute/Brisbane Centre/TRT.md

@@ -23,7 +23,7 @@ TRT is responsible for **KIY** when they are offline.
 
 ### Reclassifications
 #### BRM CTR
-When **BRM ADC** is offline, BRM CTR (Class D/E `SFC` to `A055`) reverts to Class G, and is administered by KIY. Alternatively, KIY may provide a [top-down procedural service](../../../aerodromes/Karratha) if they wish.
+When **BRM ADC** is offline, BRM CTR (Class D/E `SFC` to `A055`) reverts to Class G, and is administered by KIY. Alternatively, KIY may provide a [top-down procedural service](../../../aerodromes/Broome) if they wish.
 
 ## Sector Responsibilities
 TRT is responsible for sequencing, issuing STAR Clearances, and issuing descent for aircraft bound for YPDN.  

docs/enroute/Melbourne Centre/ASP.md

@@ -34,6 +34,17 @@ When **AS ADC** is offline, AS CTR (Class D and C `SFC` to `F125`) within 80 DME
 !!! Warning
     ML-ASP_CTR is only permitted to extend to adjacent **YMMM** sectors.
 
+## Surveillance Coverage
+Limited surveillance coverage exists in the FOR sector greater than **250nm** from ADSB stations. [Procedural Standards](../../../separation-standards/procedural/) must be implemented **prior** to losing surveillance coverage
+
+The **Orange** shaded areas will have limited surveillance coverage **Below F330**.  
+The **Red** shaded areas will have limited surveillance coverage at **All Levels**.
+
+<figure markdown>
+![Forest Surveillance Coverage](../assets/aspsurv.png){ width="700" }
+  <figcaption>Forest Surveillance Coverage</figcaption>
+</figure>
+
 ## STAR Clearance Expectation
 ### Handoff
 Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff:
@@ -43,7 +54,7 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR
 | FOR, WRA, BKE | TBD(AUG) | YPAD, YPED | Jets only |
 | BKE | TBD | YPAD, YPED | |
 | ESP | PIY(HYD) | YPPH, YPEA | Jets only |
-| BKE | YWE(KAT) | YSSY | |
+| BKE | YWE(KAT, GTH) | YSSY | |
 
 ## Coordination
 ### Enroute

docs/enroute/Melbourne Centre/ELW.md

@@ -59,6 +59,7 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR
 | ELW | BLA | YSCB | |
 | SNO | HUO | YMHB | |
 | BLA | ELW | YMML | Non-Jets only |
+| SNO | YWE(WON) | YMML | |
 
 ### First Contact
 Aircraft being transferred from the following sectors shall be given STAR Clearance on first contact:

docs/enroute/Melbourne Centre/PIY.md

@@ -24,47 +24,60 @@
 
 ## 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](#perth-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 Non-jets bound for YPPH and YPEA. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment.
 
 For aircraft overflying the PH TCU place `O/FLY` in the LABEL DATA field.
 
 ### Leeman (LEA)
-LEA is responsible for assigning and issuing STAR clearance to aircraft inbound to Perth via `IPMOR`. See [Perth Runway Modes](#perth-runway-modes) for runway assignment.
+LEA is responsible for assigning and issuing STAR clearance to aircraft inbound to Perth via `IPMOR`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment.
 
 !!! note
     Controllers should be aware that VHF coverage near the LEA/IND border may be limited. Controllers should strive to issue HF frequencies and transfer of communications instruction prior to 160 NM PH DME.
 
 ### Grove (GVE)
-GVE is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `JULIM` and `SAPKO`.  See [Perth Runway Modes](#perth-runway-modes) for runway assignment.
+GVE is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `JULIM` and `SAPKO`.  See [Perth Runway Modes](#ypph-runway-modes) for runway assignment.
 
 ### Hyden (HYD)
-HYD is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `BEVLY`, `DAYLR` and `GRENE`. See [Perth Runway Modes](#perth-runway-modes) for runway assignment.
+HYD is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `KABLI`/`MALUP`, `DAYLR` and `LAVEX`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment.
 
 ### Cross (CRS) / Geraldton (GEL)
 Just keeping them separated!
 
 ### Jarrah (JAR)
-JAR is responsible for assigning and issuing arrival clearance to aircraft inbound to Perth via `SOLUS`. See [Perth Runway Modes](#perth-runway-modes) for runway assignment.
+JAR is responsible for assigning and issuing arrival clearance to aircraft inbound to Perth via `SOLUS`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment.
 
 !!! note
     Controllers should be aware there may be limited ADS-B coverage around Albany (YABA). Expect some areas of Class E airspace to be outside surveillance coverage. [Procedural Standards](../../../separation-standards/procedural) may need to be used in these cases.
 
-### Perth Runway Modes
-#### Southwest Plan
+## YPPH Runway Modes
+### Southwest Plan
 With the Southwest Plan active, arrivals shall be processed to either runway 21 or 24 based on their feeder fix, as per the table below:
 
 | Feeder Fix | Assigned Runway |
 | --- | --- |
 | JULIM | 21 |
 | SAPKO | 21 |
 | IPMOR | 21 |
-| BEVLY | 24 (or 21 if operationally required) |
-| GRENE | 24 |
+| KABLI | 24 (or 21 if operationally required) |
+| LAVEX | 24 |
 | SOLUS | 24 |
 
-#### Northeast Plan
+### 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*:
+
+| Feeder Fix | 03/06 | 21/24 |
+| ------------------- | ----- | ----- |
+| WOORA | Golf | WOORA PH JT (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.
+
 ## STAR Clearance Expectation
 
 ### Handoff

docs/enroute/Melbourne Centre/YWE.md

@@ -37,7 +37,7 @@ MUN is responsible for issuing STAR Clearances for aircraft arriving at YMML. MU
 OXL is responsible for issuing STAR Clearances for aircraft arriving at YMML. OXL will also initiate sequencing as required for aircraft arriving at YMML.
 
 ### Griffith (GTH)
-Just keeping them separated!
+GTH is responsible for issuing STAR Clearances for YSSY.
 
 ### Katoomba (KAT)
 KAT is responsible for issuing STAR Clearances for YSCB and YSSY.
@@ -52,6 +52,7 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR
 | GTH | OXL | YMML, YMAV | |
 | OXL | ELW(BLA) | YSCB | |
 | GTH | BIK(GUN) | YSSY | |
+| OXL | GTH | YSSY | |
 | WON | HUO | YMHB | |
 
 ### First Contact
@@ -61,8 +62,9 @@ Aircraft being transferred from the following sectors shall be given STAR Cleara
 | ---- | -------- | --------- | --------- |
 | TBD | MUN | YMML, YMAV | |
 | ASP(BKE), GTH | OXL | YMML, YMAV | |
-| HUO | WON | YMML | 
-| ASP(BKE) | KAT | YSSY | |
+| HUO, ELW(SNO) | WON | YMML | 
+| ASP(BKE) | GTH, KAT | YSSY | |
+| OXL | GTH | YSSY | |
 | ARL(MDE) | KAT | YSCB | |
 
 ## Coordination