AIRAC 2313 | 28DEC23

docs/aerodromes/Amberley.md

@@ -8,16 +8,16 @@
 
 | Name               | Callsign       | Frequency        | Login Identifier              |
 | ------------------ | -------------- | ---------------- | --------------------------------------|
-| Amberley ADC    | Amberley Tower  | 118.300         | AM_TWR        |
-| Amberley SMC    | Amberley Ground  | 129.350      | AM_GND        |
-| Amberley ACD    | Amberley Delivery  | 134.600         | AM_DEL       |
+| Amberley ADC    | Amberley Tower  | 118.300         | AMB_TWR        |
+| Amberley SMC    | Amberley Ground  | 129.350      | AMB_GND        |
+| Amberley ACD    | Amberley Delivery  | 134.600         | AMB_DEL       |
 | Amberley ATIS    |   | 123.300         | YAMB_ATIS       |
 
 
 
 ## Airspace
 
-AM ADC owns the Class C airspace **in the AM CTR** within 10nm of the YAMB ARP from `SFC` to `A015`. This airspace is primarily used for military circuits and initial and pitch approaches.
+AMB ADC owns the Class C airspace **in the AMB CTR** within 10nm of the YAMB ARP from `SFC` to `A015`. This airspace is primarily used for military circuits and initial and pitch approaches.
 
 
 ## YAMB Aerodrome
@@ -33,11 +33,11 @@ Aircraft will depart the circuit visually and track overhead YAMB to begin track
 
 !!! example
     CRNG21 plans to enter R637 via the gate MOSSI for Military Training.
-    **AM ADC**: "CRNG21, cleared to YAMB via MOSSI, flight planned route. Runway 15, Northern 1 Departure. Climb to `F190`. Squawk 3601, Departure Frequency 126.20"  
+    **AMB ADC**: "CRNG21, cleared to YAMB via MOSSI, flight planned route. Runway 15, Northern 1 Departure. Climb to `F190`. Squawk 3601, Departure Frequency 126.20"  
 
 !!! example
     WOLF03 was assiged the BYRON7 departure with their initial clearance. 
-    **AM ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff"  
+    **AMB ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff"  
     **WOLF03**: "Make left turn, reach `F190` by COWIE, cleared for takeoff, WOLF03"  
 
 | Departure | Initial Constraint | Route |
@@ -50,7 +50,7 @@ Aircraft will depart the circuit visually and track overhead YAMB to begin track
     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}
 
 !!! note
-    Since the Coded Departures are not SIDs, AM ACD needs to write the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route to include all relevant tracking points.
+    Since the Coded Departures are not SIDs, AMB ACD needs to write the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route to include all relevant tracking points.
 
 
 ### Runway Operations
@@ -73,16 +73,16 @@ The Circuit Area Airspace is allocated to be within 5nm of the YAMB ARP from `SF
 | 22     | Left |
 
 ## Coordination
-### AM TCU
+### AMB TCU
 
-'Next' coordination is required from AM ADC to AM TCU for all aircraft.
+'Next' coordination is required from AMB ADC to AMB TCU for all aircraft.
 
 !!! example
-    <span class="hotline">**AM ADC** -> **AM TCU**</span>: "Next, ASY01, runway 33"  
-    <span class="hotline">**AM TCU** -> **AM ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"  
-    <span class="hotline">**AM ADC** -> **AM TCU**</span>: "Assigned Heading Heading Right 030, ASY01"  
+    <span class="hotline">**AMB ADC** -> **AMB TCU**</span>: "Next, ASY01, runway 33"  
+    <span class="hotline">**AMB TCU** -> **AMB ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"  
+    <span class="hotline">**AMB ADC** -> **AMB TCU**</span>: "Assigned Heading Heading Right 030, ASY01"  
 
 ### Level Assignment
-The Standard Assignable Level from  **AM ADC** to **AM TCU** is:  
+The Standard Assignable Level from  **AMB ADC** to **AMB TCU** is:  
 a) The Lower of `F180` or `RFL` for Aircraft assigned via Procedural or RNAV SID.  
 b) `F190` for Aircraft assigned a Coded Departure.

docs/aerodromes/Curtin.md

@@ -0,0 +1,43 @@
+---
+  title: Curtin (YCIN)
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Positions
+
+| Name               | Callsign       | Frequency        | Login Identifier              |
+| ------------------ | -------------- | ---------------- | --------------------------------------|
+| Curtin ADC    | Curtin Tower  | 118.300         | CIN_TWR        |
+| Curtin SMC    | Curtin Ground  | 126.200      | CIN_GND        |
+| Curtin ACD    | Curtin Delivery  | 136.800         | CIN_DEL       |
+| Curtin ATIS    |   | 134.800         | YCIN_ATIS       |
+
+## Airspace
+
+CIN ADC owns the Class C airspace **within the CIN CTR** from `SFC` to `A015`.
+
+### Circuit Direction
+
+| Runway | Direction |
+| ------ | ----------|
+| 29     | Left  |
+| 11     | Right |
+
+## Coordination
+### CIN TCU
+
+'Next' coordination is required from CIN ADC to CIN TCU for all aircraft.
+
+!!! example
+    <span class="hotline">**SG ADC** -> **SG TCU**</span>: "Next, ASY404, runway 29"  
+    <span class="hotline">**SG TCU** -> **SG ADC**</span>: "ASY404, Left heading 260, unrestricted"
+    <span class="hotline">**SG ADC** -> **SG TCU**</span>: "Left heading 260, ASY404"  
+
+
+The Standard Assignable Level from  **CIN ADC** to **CIN TCU** is the Lower of `F190` or the `RFL`.
+
+## 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}
+

docs/aerodromes/Learmonth.md

@@ -0,0 +1,37 @@
+---
+  title: Learmonth (YPLM)
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Positions
+
+| Name               | Callsign       | Frequency        | Login Identifier              |
+| ------------------ | -------------- | ---------------- | --------------------------------------|
+| Learmonth ADC    | Learmonth Tower  | 118.300         | LM_TWR        |
+| Learmonth SMC    | Learmonth Ground  | 126.200      | LM_GND        |
+| Learmonth ATIS    |   | 123.300         | YPLM_ATIS       |
+
+## Airspace
+
+LM ADC owns the Class C airspace **within the LM CTR** from `SFC` to `A015`.
+
+### Circuit Direction
+
+| Runway | Direction |
+| ------ | ----------|
+| 36     | Right  |
+| 18     | Left |
+
+## Coordination
+### LM TCU
+
+'Next' coordination is required from LM ADC to LM TCU for all aircraft.
+
+!!! example
+    <span class="hotline">**LM ADC** -> **LM TCU**</span>: "Next, QFA1601, runway 36"  
+    <span class="hotline">**LM TCU** -> **LM ADC**</span>: "QFA1601, Right heading 060 Visual, unrestricted"
+    <span class="hotline">**LM ADC** -> **LM TCU**</span>: "Right heading 060 Visual, QFA1601"  
+
+The Standard Assignable Level from  **LM ADC** to **LM TCU** is the Lower of `F270` or the `RFL`.
+

docs/aerodromes/Scherger.md

@@ -0,0 +1,41 @@
+---
+  title: Scherger (YBSG)
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Positions
+
+| Name               | Callsign       | Frequency        | Login Identifier              |
+| ------------------ | -------------- | ---------------- | --------------------------------------|
+| Scherger ADC    | Scherger Tower  | 118.300         | SG_TWR        |
+| Scherger SMC    | Scherger Ground  | 126.200      | SG_GND        |
+| Scherger ATIS    |   | 134.800         | YBSG_ATIS       |
+
+## Airspace
+
+SG ADC owns the Class C airspace **within the SG CTR** from `SFC` to `A015`.
+
+### Circuit Direction
+
+| Runway | Direction |
+| ------ | ----------|
+| 30     | Right  |
+| 12     | Left |
+
+## Coordination
+### SG TCU
+
+'Next' coordination is required from SG ADC to SG TCU for all aircraft.
+
+!!! example
+    <span class="hotline">**SG ADC** -> **SG TCU**</span>: "Next, ASY219, runway 30"  
+    <span class="hotline">**SG TCU** -> **SG ADC**</span>: "ASY219, Left heading 270 Visual, unrestricted"
+    <span class="hotline">**SG ADC** -> **SG TCU**</span>: "Left heading 270 Visual, ASY219"  
+
+The Standard Assignable Level from  **SG ADC** to **SG TCU** is the Lower of `F240` or the `RFL`.
+
+## 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}
+

docs/aerodromes/Woomera.md

@@ -0,0 +1,44 @@
+---
+  title: Woomera (YPWR)
+---
+
+--8<-- "includes/abbreviations.md"
+
+## Positions
+
+| Name               | Callsign       | Frequency        | Login Identifier              |
+| ------------------ | -------------- | ---------------- | --------------------------------------|
+| Woomera ADC    | Woomera Tower  | 118.300         | WR_TWR        |
+| Woomera ATIS    |   | 118.100         | YPWR_ATIS       |
+
+## Airspace
+
+By default, WR ADC owns the **R222F** Restricted Area. This airspace has vertical limits of `SFC` to `F125`. When WR ADC is active, this airspace is classfied as Class D.
+
+Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
+
+## Surveillance
+
+WR TWR is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels within R222F.  
+For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base.
+
+## Coordination
+### WRA
+
+A 'next' call is made for all aircraft when they are next to depart. WR ADC must inform ASP(WRA) if the aircraft does not depart within **2 minutes** of the next call.
+
+The Standard Assignable Level from  **WR ADC** to **ASP(WRA)** is the Lower of `F130` or the `RFL`.
+
+### Arrivals/Overfliers
+ASP(WRA) will heads-up coordinate all arrivals/overfliers to WR ADC
+
+!!! example
+    <span class="hotline">**WRA** -> **WR ADC**</span>: "Via WRA DCT, PSDN100”  
+    <span class="hotline">**WR ADC** -> **WRA**</span>: "PSDN100"  
+
+The Standard Assignable level from ASP(WRA) to WR ADC is `F120`, any other level must be prior coordinated.
+
+## 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}
+

docs/enroute/Brisbane Centre/INL.md

@@ -176,24 +176,24 @@ Any aircraft that will enter CFS ADC airspace, and not landing at YCFS, must be
     <span class="hotline">**INL** -> **CFS ADC**</span>: "via CFS, XFC, Overflier"  
     <span class="hotline">**CFS ADC** -> **INL**</span>: "XFC, A040"
 
-### OK TCU / AM TCU
+### OK TCU / AMB TCU
 #### Airspace
-By default, **OK TCU** owns the airspace within the **R654A-D** restricted areas, and **AM TCU** owns the airspace within the **R625A-D** restricted areas, unless stated otherwise by ad-hoc release or NOTAM.
+By default, **OK TCU** owns the airspace within the **R654A-D** restricted areas, and **AMB TCU** owns the airspace within the **R625A-D** restricted areas, unless stated otherwise by ad-hoc release or NOTAM.
 
 #### Departures
-All aircraft from AM/OK TCU to INL(All) require Heads-up coordination prior to the boundary. Expect this coordination to be completed a short time after the aircraft becomes airborne (pending controller workload).
+All aircraft from AMB/OK TCU to INL(All) require Heads-up coordination prior to the boundary. Expect this coordination to be completed a short time after the aircraft becomes airborne (pending controller workload).
 
 !!! example 
-    <span class="hotline">**AM TCU** -> **NSA**</span>: "via COWIE, BUCK03."  
-    <span class="hotline">**NSA** -> **AM TCU**</span>: "BUCK03, `F190`"  
+    <span class="hotline">**AMB TCU** -> **NSA**</span>: "via COWIE, BUCK03."  
+    <span class="hotline">**NSA** -> **AMB TCU**</span>: "BUCK03, `F190`"  
 
 #### Arrivals/Overfliers
-All aircraft transiting from INL(All) to **OK TCU** and **AM TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **OK TCU** and **AM TCU** are fairly ad-hoc, so there are no standard assignable levels. ENR and TCU controllers should coordinate to determine the most suitable level.
+All aircraft transiting from INL(All) to **OK TCU** and **AMB TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **OK TCU** and **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels. ENR and TCU controllers should coordinate to determine the most suitable level.
 
 !!! example
-    <span class="hotline">**GOL** -> **AM TCU**</span>: "via HUUGO, STAL13, what level can I assign?"  
-    <span class="hotline">**AM TCU** -> **GOL**</span>: "STAL13, `A090`"  
-    <span class="hotline">**GOL** -> **AM TCU**</span>: "`A090`, STAL13"   
+    <span class="hotline">**GOL** -> **AMB TCU**</span>: "via HUUGO, STAL13, what level can I assign?"  
+    <span class="hotline">**AMB TCU** -> **GOL**</span>: "STAL13, `A090`"  
+    <span class="hotline">**GOL** -> **AMB TCU**</span>: "`A090`, STAL13"   
 
 ### TSN(FLD/HWE) (Oceanic)
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary.

docs/enroute/Brisbane Centre/ISA.md

@@ -32,6 +32,7 @@ ISA is responsible for **ARA**, **STR**, **WEG**, and **CVN** when they are offl
 
 ## Sector Responsibilities
 ISA and its subsectors are purely Classes A, E and G of airspace. [Standard separation procedures](../../../separation-standards) apply.
+ARA is responsible for sequencing and issuing descent to aircraft bound for YBSG.
 
 ## STAR Clearance Expectation
 ### Handoff
@@ -50,6 +51,14 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR
 ### Enroute
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
 
+### SG TCU
+
+The Standard assignable level from ARA to SG TCU is `F130`, tracking via WP VOR.
+
+All other aircraft must be voice coordinated to SG TCU prior to **20nm** from the boundary.
+
+The Standard Assignable level from SG TCU to ARA is `F240`, and tracking via their planned route.
+
 ### ISA Internal
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
 ### TSN(COL) (Oceanic)

docs/enroute/Brisbane Centre/TRT.md

@@ -23,6 +23,7 @@ TRT is responsible for **KIY** when they are offline.
 ## Sector Responsibilities
 TRT is responsible for sequencing, issuing STAR Clearances, and issuing descent for aircraft bound for YPDN.  
 KIY is responsible for issuing descent and ascertaining arrival intentions for aircraft bound for YBRM.
+KIY is also responsible for sequencing and issuing descent to aircraft bound for YCIN.
 
 ## STAR Clearance Expectation
 ### Handoff
@@ -82,6 +83,14 @@ Any aircraft that will enter BRM ADC airspace, and not landing at YBRM, must be
     <span class="hotline">**KIY** -> **BRM ADC**</span>: "via CIN, NQC"  
     <span class="hotline">**BRM ADC** -> **SWY**</span>: "NQC, A045"
 
+### CIN TCU
+
+The Standard assignable level from TRT(KIY) to CIN TCU is `F130`, tracking via CIN VOR or DBY NDB.
+
+All other aircraft must be voice coordinated to CIN TCU prior to **20nm** from the boundary.
+
+The Standard Assignable level from CIN TCU to TRT(KIY) is `F190`, and tracking via their planned route.
+
 ### IND(INE) (Oceanic)
 As per [Standard Coordination Procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary.
 ### International (WAAF)

docs/enroute/Melbourne Centre/ASP.md

@@ -28,6 +28,8 @@
 
 When **AS ADC** is offline, AS CTR (Class D and C `SFC` to `F125`) within 80 DME AS reverts to Class G, and AS CTR (Class C `F125` to `F245`) within 80 DME AS reverts to Class E, and both are administered by ASP. Alternatively, ASP may provide a [top-down procedural service](../../../aerodromes/Alice) if they wish.
 
+When **WR ADC** is offline, R222F (`SFC` to `F125`) reverts to Class G, and is administered by WRA. Alternatively, WRA may provide a [top-down procedural service](../../../aerodromes/Woomera) if they wish.
+
 ## Extending
 !!! Warning
     As per [VATPAC Ratings and Controller Positions Policy](https://cdn.vatpac.org/documents/policy/Controller+Positions+and+Ratings+Policy+v5.2.pdf), ML-ASP_CTR is only permitted to extend to adjacent **YMMM** sectors.
@@ -76,5 +78,32 @@ Any aircraft that will enter AS ADC airspace, and not landing at YBAS, must be H
     <span class="hotline">**ASP** -> **AS ADC**</span>: "via AS, JDS"  
     <span class="hotline">**AS ADC** -> **ASP**</span>: "JDS, A060"
 
+### WR ADC
+
+Departures from YPWR in to WRA Class E will be coordinated when ready for departure.
+
+!!! example
+    <span class="hotline">**WR ADC** -> **WRA**</span>: "Next, ASY404"  
+    <span class="hotline">**WRA** -> **WR ADC**</span>: "ASY404, Unrestricted"  
+    <span class="hotline">**WR ADC** -> **WRA**</span>: "Unrestricted, ASY404" 
+
+The Standard Assignable level from **WR ADC** to ASP is the lower of `F130` or the `RFL`, any other level must be prior coordinated.
+
+#### Arrivals
+YPWR arrivals shall be heads-up coordinated to **WR ADC** from WRA prior to **5 mins** from the boundary.
+
+!!! example
+    <span class="hotline">**WRA** -> **WR ADC**</span>: "Via WR, ASY219”  
+    <span class="hotline">**WR ADC** -> **WRA**</span>: "ASY219"  
+
+The Standard Assignable level from ASP to **WR ADC** is `F120`, any other level must be prior coordinated.
+
+#### Overfliers
+Any aircraft that will enter WR ADC airspace, and not landing at YPWR, must be Heads-up coordinated prior to **5 mins** from the boundary.
+
+!!! example
+    <span class="hotline">**WRA** -> **WR ADC**</span>: "via WR, XZA"  
+    <span class="hotline">**WR ADC** -> **WRA**</span>: "XZA, A060"
+
 ### IND(INS) (Oceanic)
 As per [Standard Coordination Procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary.

docs/enroute/Melbourne Centre/OLW.md

@@ -27,10 +27,11 @@ OLW is responsible for **POT**, **PAR**, **NEW**, **MEK**, **MTK** and **MZI** w
 
 ### Reclassifications
 #### KA CTR
-When **KA ADC** is offline, KA CTR (Class D `SFC` to `A055`) reverts to Class G, and is administered by OLW. Alternatively, OLW may provide a [top-down approach service](../../../terminal/canberra) if they wish.
+When **KA ADC** is offline, KA CTR (Class D `SFC` to `A055`) reverts to Class G, and is administered by OLW. Alternatively, OLW may provide a [top-down procedural service](../../../aerodromes/Karratha) if they wish.
 
 ## Sector Responsibilities
 OLW is responsible for issuing descent and ascertaining arrival intentions for aircraft bound for YPKA.
+OLW is also responsible for sequencing and issuing descent to aircraft bound for YPLM.
 
 ## STAR Clearance Expectation
 ### Handoff
@@ -74,5 +75,13 @@ Any aircraft that will enter KA ADC airspace, and not landing at YPKA, must be H
     <span class="hotline">**OLW** -> **KA ADC**</span>: "via BORAT, QQK"  
     <span class="hotline">**KA ADC** -> **OLW**</span>: "QQK, A030"
 
+### LM TCU
+
+The Standard assignable level from OLW to LM TCU is `F130`, tracking via LM VOR.
+
+All other aircraft must be voice coordinated to LM TCU prior to **20nm** from the boundary.
+
+The Standard Assignable level from LM TCU to OLW is `F240`, and tracking via their planned route.
+
 ### IND,INE (Oceanic)
 As per [Standard Coordination Procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary.