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

Military pages & more

docs/aerodromes/Albury.md

@@ -20,8 +20,14 @@
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
 ## Surveillance
-AY ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the AY CTR.  
-For simulation purposes, visual separation is assumed to exist below the cloud base, and within 5nm of the aerodrome. Visual separation can still be used to separate from aircraft on an instrument approach, below the cloud base.
+Surveillance coverage can be expected to be available at all levels in the AY CTR. Although AY ADC is **not permitted** to use surveillance for separation, ELW(BLA) may assist by establishing surveillance separation standards via coordination
+
+!!! example
+    <span class="hotline">**AY ADC** -> **BLA**</span>: "Can you advise when QLK206D is 5nm clear of DSB?"  
+    <span class="hotline">**BLA** -> **AY ADC**</span>: "Wilco"  
+
+    <span class="hotline">**BLA** -> **AY ADC**</span>: "QLK206D 5nm clear of DSB"  
+    <span class="hotline">**AY ADC** -> **BLA**</span>: "QLK206D 5nm clear of DSB, thanks"
 
 ## Coordination
 ### Departures

docs/aerodromes/Alice.md

@@ -21,8 +21,8 @@ AS ADC is responsible for the Class D airspace `SFC` to `A045`, as well as the C
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
 ## Surveillance
-AS TWR is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the AS CTR.  
-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.
+Surveillance coverage can be expected to be available at all levels in the AS CTR. Although AS ADC is **not permitted** to use surveillance for separation, ASP may assist by establishing surveillance separation standards via coordination
+
 ## Coordination
 ### Departures
 Departures from YBAS in to ASP Class C will be coordinated when ready for departure.

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/Broome.md

@@ -20,8 +20,8 @@
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
 ## Surveillance
-BRM ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the BRM CTR.  
-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.
+Surveillance coverage can be expected to be available at all levels in the BRM CTR. Although BRM ADC is **not permitted** to use surveillance for separation, TRT(KIY) may assist by establishing surveillance separation standards via coordination
+
 ## Coordination
 ### Departures
 A 'next' call is made for all aircraft when they are next to depart. BRM ADC must inform TRT(KIY) if the aircraft does not depart within **2 minutes** of the next call.

docs/aerodromes/Coffs.md

@@ -19,17 +19,7 @@
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
 ## Surveillance
-CFS ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be not available below `A028` in the CFS CTR.  
-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.
-
-CFS ADC must establish a [Procedural Standard](../../controller-skills/classdtwr/#standards) prior to losing surveillance identification of an aircraft.
-
-!!! caution
-    A procedural and/or visual standard **must** be put in place for all aircraft below `A028`.
-## Instrument Approaches
-Only one aircraft is permitted to conduct an instrument approach at any time, due to limited surveillance coverage. CFS ADC must ensure that all aircraft are procedurally separated from any portion of an instrument approach and missed approach that is conducted below `A028`.  
-
-If required, CFS ADC can pass amended tracking/level instructions to an aircraft for a missed approach for separation purposes, as long as the aircraft can be issued **uninterrupted climb** to the LSALT/MSA once identified.
+Surveillance coverage can be expected to be not available below `A028` in the CFS CTR. Although CFS ADC is **not permitted** to use surveillance for separation, ARL(MNN) or INL may assist by establishing surveillance separation standards via coordination
 
 ## Coordination
 ### Departures

docs/aerodromes/Curtin.md

@@ -0,0 +1,46 @@
+---
+  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 `A035`.
+
+## Surveillance
+Surveillance coverage can be expected to be available at all levels in the CIN CTR. Although CIN ADC is **not permitted** to use surveillance for separation, CIN TCU or TRT(KIY) may assist by establishing surveillance separation standards via coordination
+
+## 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">**CIN ADC** -> **CIN TCU**</span>: "Next, ASY404, runway 29"  
+    <span class="hotline">**CIN TCU** -> **CIN ADC**</span>: "ASY404, unrestricted"  
+    <span class="hotline">**CIN ADC** -> **CIN TCU**</span>: "ASY404"  
+
+The Standard Assignable Level from  **CIN ADC** to **CIN TCU** is the Lower of `F190` or the `RFL`.
+
+### TRT(KIY)
+When CIN TCU is offline, coordination is not required between CIN ADC and TRT(KIY). Aircraft entering TRT(KIY) airspace shall be handed off, and instructed to contact TRT(KIY) for onwards clearance.
+
+## 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/Hammo.md

@@ -23,18 +23,7 @@ HM ADC is responsible for the Class D airspace in the HM CTR, `SFC` to `A045`.
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
 ## Surveillance
-HM ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be not available below `A031` in the HM CTR.  
-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.
-
-HM ADC must establish a [Procedural Standard](../../controller-skills/classdtwr/#standards) prior to losing surveillance identification of an aircraft.
-
-!!! caution
-    A procedural and/or visual standard **must** be put in place for all aircraft below `A031`.
-
-## Instrument Approaches
-Only one aircraft is permitted to conduct an instrument approach at any time, due to limited surveillance coverage. HM ADC must ensure that all aircraft are procedurally separated from any portion of an instrument approach and missed approach that is conducted below `A031`.  
-
-If required, HM ADC can pass amended tracking/level instructions to an aircraft for a missed approach for separation purposes, as long as the aircraft can be issued **uninterrupted climb** to the LSALT/MSA once identified.
+Surveillance coverage can be expected to be not available below `A031` in the HM CTR. Although HM ADC is **not permitted** to use surveillance for separation, KEN(SWY) may assist by establishing surveillance separation standards via coordination
 
 ## Coordination
 ### Departures

docs/aerodromes/Karratha.md

@@ -21,8 +21,8 @@
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
 ## Surveillance
-KA ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the KA CTR.  
-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.
+Surveillance coverage can be expected to be available at all levels in the KA CTR. Although KA ADC is **not permitted** to use surveillance for separation, OLW may assist by establishing surveillance separation standards via coordination
+
 ## Coordination
 ### Departures
 A 'next' call is made for all aircraft when they are next to depart. KA ADC must inform OLW if the aircraft does not depart within **2 minutes** of the next call.

docs/aerodromes/Learmonth.md

@@ -0,0 +1,44 @@
+---
+  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 `A025`.
+
+## Surveillance
+Surveillance coverage can be expected to be available at all levels in the LM CTR. Although LM ADC is **not permitted** to use surveillance for separation, LM TCU or OLW may assist by establishing surveillance separation standards via coordination
+
+## 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`.
+
+### OLW
+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
+    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/Mackay.md

@@ -20,9 +20,6 @@ MK ADC is responsible for the Class D airspace in the MK CTR `SFC` to `A010`.
 
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
-## Surveillance
-MK ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the MK CTR.  
-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
 ### Departures
 A 'next' call is made for all aircraft when they are next to depart. MK ADC must inform KEN(SWY) if the aircraft does not depart within **2 minutes** of the next call.

docs/aerodromes/Melbourne.md

@@ -34,17 +34,17 @@ ML ADC is not responsible for any airspace by default.
 Due to the close proximity of the airspace to the arrival and departure paths at YMML, controllers should be aware of surrounding traffic before issuing a clearance to helicopters.
 
 !!! example
-    **HEMS3:** "Melbourne Tower, HEMS3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance"  
-    **ML ADC:** "HEMS3, cleared to YMEN, track Sunbury Corridor, not above A020"  
-    **HEMS3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HEMS3"
+    **HM3:** "Melbourne Tower, HM3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance"  
+    **ML ADC:** "HM3, cleared to YMEN, track Sunbury Corridor, not above A020"  
+    **HM3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HM3"
 
 If necessary, consider issuing a clearance limit for separation or instruct helicopters to report sighting and to maintain own separation with other aircraft.  Alternatively, tower controllers can simulate visual separation provided no risk of collision exists and both aircraft remain in sight of the controller at all times. 
 
 !!! example
-    **ML ADC:** "HEMS3, report sighting a Jetstar A320, 4nm final runway 16"  
-    **HEMS3:** "Traffic sighted, HEMS3"  
-    **ML ADC:** "HEMS3, pass behind that aircraft, maintain own separation, caution wake turbulence"  
-    **HEMS3:** "Pass behind the A320, maintain own separation, HEMS3"
+    **ML ADC:** "HM3, report sighting a Jetstar A320, 4nm final runway 16"  
+    **HM3:** "Traffic sighted, HM3"  
+    **ML ADC:** "HM3, pass behind that aircraft, maintain own separation, caution wake turbulence"  
+    **HM3:** "Pass behind the A320, maintain own separation, HM3"
 
 Remember to pass traffic information to both aircraft.
 

docs/aerodromes/Rockhampton.md

@@ -21,9 +21,6 @@ RK ADC is responsible for the Class D airspace in the RK CTR `SFC` to `A010`.
 
 Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more information.
 
-## Surveillance
-RK ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the RK CTR.  
-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
 ### Departures
 A 'next' call is made for all aircraft when they are next to depart. RK ADC must inform rka if the aircraft does not depart within **2 minutes** of the next call.

docs/aerodromes/Scherger.md

@@ -0,0 +1,43 @@
+---
+  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 `A040`.
+
+## Surveillance
+Surveillance coverage can be expected to be available at all levels in the SG CTR. Although SG ADC is **not permitted** to use surveillance for separation, SG TCU or ISA(ARA) may assist by establishing surveillance separation standards via coordination
+
+## 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, unrestricted"  
+    <span class="hotline">**SG ADC** -> **SG TCU**</span>: "ASY219"  
+
+The Standard Assignable Level from  **SG ADC** to **SG TCU** is the lower of `F240` or the `RFL`.
+
+### ISA(ARA)
+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
+    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}