vatpac-technology · Slep-wt · Dec 26, 2023 · Dec 27, 2023 · Dec 27, 2023 · Dec 27, 2023
diff --git a/docs/aerodromes/Amberley.md b/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.
diff --git a/docs/aerodromes/Curtin.md b/docs/aerodromes/Curtin.md
@@ -0,0 +1,37 @@
+---
+  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 ADC / CIN TCU
+
+'Next' coordination is required from CIN ADC to CIN TCU for all aircraft.
+
+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}
+
diff --git a/docs/aerodromes/Learmonth.md b/docs/aerodromes/Learmonth.md
@@ -0,0 +1,32 @@
+---
+  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 |
+| ------ | ----------|
+| 29     | Right  |
+| 11     | Left |
+
+## Coordination
+### LM ADC / LM TCU
+
+'Next' coordination is required from LM ADC to LM TCU for all aircraft.
+
+The Standard Assignable Level from  **LM ADC** to **LM TCU** is the Lower of `F130` or the `RFL`.
+
diff --git a/docs/aerodromes/Scherger.md b/docs/aerodromes/Scherger.md
@@ -0,0 +1,36 @@
+---
+  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 |
+| ------ | ----------|
+| 29     | Right  |
+| 11     | Left |
+
+## Coordination
+### SG ADC / SG TCU
+
+'Next' coordination is required from SG ADC to SG TCU for all aircraft.
+
+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}
+
diff --git a/docs/aerodromes/Woomera.md b/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
+### WR ADC / ASP(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">**ASP(WRA)** -> **WR ADC**</span>: "Via WRA DCT, PSDN100”  
+    <span class="hotline">**WR ADC** -> **ASP(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}
+
diff --git a/docs/enroute/Brisbane Centre/INL.md b/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.
diff --git a/docs/pacific/New-Caledonia/TCU.md b/docs/pacific/New-Caledonia/TCU.md
@@ -8,7 +8,11 @@
 
 | Name               | ID      | Callsign       | Frequency        | Login Identifier              |
 | ------------------ | --------------| -------------- | ---------------- | --------------------------------------|
-| Tontouta Approach South|NWWWA| Tontouta Approach  | 128.300         | NWWW_APP          |
+| **Tontouta Approach South**|**NWWWA**| **Tontouta Approach**  | **128.300**         | **NWWW_APP**          |
+| Tontouta Approach (TMA 1.1)†|NWWWT| Tontouta Approach  | 119.700         | NWWW-T_APP          |
+
+
+† *Non-standard positions* may only be used in accordance with [VATPAC Ratings and Controller Positions Policy](https://vatpac.org/publications/policies){target=new}
 
 ## Airspace
 

diff --git a/docs/terminal/amberleyoakey.md b/docs/terminal/amberleyoakey.md
@@ -2,33 +2,30 @@
   title: Amberley / Oakey TCU
 ---
 
---8<-- "includes/abbreviations.md"
-
-
 --8<-- "includes/abbreviations.md"
 
 ## Positions
 
 | Name               | Callsign       | Frequency        | Login Identifier              |
 | ------------------ | -------------- | ---------------- | --------------------------------------|
-| Amberley TCU   | Amberley Approach   | 126.200        | AM_APP                                   |
+| Amberley TCU   | Amberley Approach   | 126.200        | AMB_APP                                   |
 | Oakey TCU   | Oakey Approach | 125.400        | OK_APP                                   |
 
-AM APP is expected to extend to OK APP when they are offline. No frequency cross coupling is required. 
+AMB APP is expected to extend to OK APP when they are offline. No frequency cross coupling is required. 
 
 
 ## Airspace
-### AM TCU
+### AMB TCU
 #### Restricted Areas
-By default, AM APP owns all of the R625 Restricted Areas, as detailed below:
+By default, AMB APP owns all of the R625 Restricted Areas, as detailed below:
 
 - R625A (`A015`-`A085`)  
 - R625B (`A025`-`A085`)  
 - R625C (`A045`-`A085`)  
 - R625D (`A085`-`F210`)  
 
 ### Optional, as required
-AM APP can negotiate further airspace releases from surrounding ENR sectors to facilitate planned military operations of the following Restricted Areas:
+AMB APP can negotiate further airspace releases from surrounding ENR sectors to facilitate planned military operations of the following Restricted Areas:
 
 - R650A (`A050`-`A100`)  
 - R650B (`A050`-`F600`)  
@@ -43,12 +40,12 @@ AM APP can negotiate further airspace releases from surrounding ENR sectors to f
 #### Diagram
 
 <figure markdown>
-![AM TCU Airspace Diagram](img/amtcu.png){ width="952" }
-  <figcaption>AM TCU Airspace Diagram</figcaption>
+![AMB TCU Airspace Diagram](img/amtcu.png){ width="952" }
+  <figcaption>AMB TCU Airspace Diagram</figcaption>
 </figure>
 
-### AM ADC
-AM ADC owns the Class C airspace in the AM CTR within 10nm of the YAMB ARP from `SFC` to `A015`. 
+### AMB ADC
+AMB ADC owns the Class C airspace in the AM CTR within 10nm of the YAMB ARP from `SFC` to `A015`. 
 
 ### OK TCU
 #### Restricted Areas
@@ -79,7 +76,7 @@ Aircraft will make a visual departure in the circuit direction and fly overhead
 
 !!! example
     WOLF03 was assiged the BYRON7 departure with their intial 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 |
@@ -92,7 +89,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}
 
 !!! note
-    AM ACD will record the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route with all necessary tracking points.
+    AMB ACD will record the name of the coded departure in the Global Ops Field of the FDR and amend the flight plan route with all necessary tracking points.
 
 ## Charts
 !!! note
@@ -101,35 +98,35 @@ Aircraft will make a visual departure in the circuit direction and fly overhead
 ## Coordination
 ### AM/OK ADC
 
-'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"  
 
 ### INL / BN TCU
 #### Departures
-All aircraft from AM/OK TCU to INL(All) and BN TCU require Heads-up coordination prior to the boundary, however, as soon as practical (when is the aircraft becomes airborne) is prefered.
+All aircraft from AMB/OK TCU to INL(All) and BN TCU require Heads-up coordination prior to the boundary, however, as soon as practical (when is the aircraft becomes airborne) is prefered.
 
-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.
 
 The Standard Assignable from **OK ADC** to **OK TCU** is the lower of `F120` or `RFL`.
 
 !!! example
-    <span class="hotline">**AM TCU** -> **BN TCU**</span>: "via BN, DRGN02"  
-    <span class="hotline">**BN TCU** -> **AM TCU**</span>: "DRGN02, `F180`"  
+    <span class="hotline">**AMB TCU** -> **BN TCU**</span>: "via BN, DRGN02"  
+    <span class="hotline">**BN TCU** -> **AMB TCU**</span>: "DRGN02, `F180`"  
 
 !!! example
     BUCK03 is assigned the BYRON 7 coded departure. 
-    <span class="hotline">**AM TCU** -> **NSA**</span>: "via COWIE, BUCK3."  
-    <span class="hotline">**NSA** -> **AM TCU**</span>: "BUCK03, `F190`"  
+    <span class="hotline">**AMB TCU** -> **NSA**</span>: "via COWIE, BUCK3."  
+    <span class="hotline">**NSA** -> **AMB TCU**</span>: "BUCK03, `F190`"  
 
 #### Arrivals/Overlfies
-All aircraft transiting from GOL/DOS/BUR to **AM TCU** and **OK TCU** must be heads-up coordinated prior to **20nm** from the boundary and aircraft from **BN TCU** to **AM TCU** only prior to the boundary. Operations within **AM TCU** are fairly ad-hoc, so there are no standard assignable levels. GOL/DOS/BUR and **AM TCU**/**OK TCU** controller must agree on a suitable level during coordination.
+All aircraft transiting from GOL/DOS/BUR to **AMB TCU** and **OK TCU** must be heads-up coordinated prior to **20nm** from the boundary and aircraft from **BN TCU** to **AMB TCU** only prior to the boundary. Operations within **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels. GOL/DOS/BUR and **AMB TCU**/**OK TCU** controller must agree on a suitable level during coordination.
 
 !!! example
-    <span class="hotline">**GOL** -> **AM TCU**</span>: "via HUUGO, PUMA11, will be assigned A090"  
-    <span class="hotline">**AM TCU** -> **GOL**</span>: "PUMA11, A090"  
+    <span class="hotline">**GOL** -> **AMB TCU**</span>: "via HUUGO, PUMA11, will be assigned A090"  
+    <span class="hotline">**AMB TCU** -> **GOL**</span>: "PUMA11, A090"