Scherger SOP Updates

docs/aerodromes/classc/Scherger.md

@@ -16,37 +16,113 @@
     YBSG is a [military aerodrome](../../../controller-skills/military/#military-aerodromes) and procedures can differ significantly to those at a civil aerodrome. Ensure you are familiar with the [military controller skills](../../../controller-skills/military) necessary to provide a quality service.
 
 ## Airspace
-SG ADC owns the Class C airspace within the SG CTR from `SFC` to `A015` with a **5nm radius** around YBSG.
+**SG ADC** is not responsible for any airspace by default.
+
+### Restricted Area Activations
+There are no [restricted areas or MOAs](../../../controller-skills/sua) activated by default when SG ADC is online.
+
+## Manoeuvring Area
+### Recommended Taxi Routes
+Except when the traffic situation warrants, taxi clearances shall conform to the following diagram:
+
+=== "Runway 12"
+	<figure markdown>
+	![Standard Taxi Routes for RWY 12](img/ybsgstdtaxi_12.png){ width="500" }
+	  <figcaption>Standard Taxi Routes for RWY 12</figcaption>
+	</figure>
+
+=== "Runway 30"
+	<figure markdown>
+	![Standard Taxi Routes for RWY 30](img/ybsgstdtaxi_30.png){ width="500" }
+	  <figcaption>Standard Taxi Routes for RWY 30</figcaption>
+	</figure>
+
+## Local Procedures
+### Initial and Pitch 
+The [intial points](../../../controller-skills/military/#initial-and-pitch) are aligned with Taxiway A at the following locations.
+
+| RWY  | Initial Point | Altitude |
+| ---- | ------------- | --------------------------- |
+| 12   | Bend in Mission River at 4.5 TAC SGR | `A025` |
+| 30   | Intersection of Marmoss Creek and easterly estuary | `A025` |
+
+### Military Gates
+There are numerous [military gates](../../../controller-skills/military/#military-gates) established throughout the SG TMA to facilitate entry and exit to adjoining SUA.
+
+<figure markdown>
+![SG SUA Gates](../../terminal/img/sg_mil_gates.png){ width="700" }
+  <figcaption>SG SUA Gates</figcaption>
+</figure>
+
+Pilots should include the desired departure gate when requesting clearance.
+
+!!! phraseology
+    *FBED14 plans to enter the M610A MOA via the Gate 10 for military training and airwork.*  
+    **FBED14**: "Scherger Ground, FBED14 for Gate 10, `F180` for M610A, request clearance."  
+    **SG SMC**: "FBED14, Scherger Ground. cleared Gate 10 direct, climb to `F180`, squawk 6001, departure frequency 124.2."   
+
+If the pilot **does not** nominate a gate, or nominates a gate that does not provide access to their intended SUA, SG SMC should clear the aircraft to depart via the **appropriate gate**.
+
+| Intended SUA    | TCU Exit Gate       |
+| --------------- | ------------------- |
+| N/A (Deps East) | Gate 2, 4, and 6    |
+| M601A           | Gate 8, 10, and 12  |
+
+!!! tip
+    [Coordination requirements](#smc-to-sg-tcu) exist between SMC and TCU when aircraft are requesting clearance to operate in an SUA that has not been activated. Controllers performing the role of SMC should ensure they coordinate with TCU before providing clearance.
+
+## Helicopter Operations
+### Helipads
+There are two helipads at YBSG, both located south of Taxiway A2.
+
+Both helipads are outside of the manoeuvring area so no takeoff or landing clearances should be issued. Instead, helicopters should be instructed to report airborne or report on the ground.
+
+!!! phraseology 
+    **SG ADC**: "RHWK11, Pad 1, report on the ground" 
 
 ## Runway Modes
 ### Circuits
+The circuit height is `A015`.
+
+#### Circuit Direction
 | Runway | Direction |
 | ------ | ----------|
-| 30     | Right  |
-| 12     | Left |
+| 30     | Right     |
+| 12     | Left      |
+
+## ATIS
+#### Operational Info
+The Operational Information field should be updated to reflect the activation of either [TRA Scherger or SG MIL CTR](../../../terminal/scherger/#sg-mil-ctr).
+
+| Activated SUA | OPR INFO Field |
+| ------------- | -------------- |
+| TRA Scherger  | `T R A SCHERGER ACTIVE` |
+| SG MIL CTR    | `SCHERGER MILITARY CONTROL ZONE ACTIVE` |
 
 ## Coordination
 ### Auto Release
-[Next](../../controller-skills/coordination.md#next) coordination is required from SG ADC to SG TCU for all aircraft.
+[Next](../../../controller-skills/coordination/#next) coordination is required from SG ADC to SG TCU for all aircraft.
 
 The Standard Assignable Level from **SG ADC** to **SG TCU** is:
 
-| Aircraft | Level |
-| ------- | ------- |
-| All | The lower of `F240` and `RFL` |
-
-SG TCU shall perform [Heads Up](../../controller-skills/coordination.md#heads-up) coordination for all aircraft inbound to YBWP.
+| Aircraft | Level   |
+| -------- | ------- |
+| All      | The lower of `F190` and `RFL` |
 
 ### Departures Controller
-When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the Advisory frequency shall be issued.
+When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the advisory frequency shall be issued.
+
+| Runway | Via  | Departure Frequency |
+| ------ | ---- | ------------------- |
+| All    | All  | 124.2 (SGA)         |
 
-| Runway | Via | Departure Frequency |
-| ------ | ---- | -------------------- |
-| All | All | 124.2 (SGA) |
+### SMC to SG TCU
+The controller assuming responsibility of **SMC** shall give [heads-up](../../../controller-skills/coordination/#airways-clearance) coordination to SGA (or the enroute controller responsible for the SG TCU) prior to the issue of a clearance to an aircraft intending to operate in an SUA that **has not** been activated. 
 
-### 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.
+!!! phraseology
+    <span class="hotline">**SG SMC** -> **SGA**</span>: "FBED13 requests clearance to M610A”  
+    <span class="hotline">**SGA** -> **SG SMC**</span>: "FBED13, clearance approved."  
 
 ## 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}
+    In addition to the civilian `ERSA` and `AIP` publications, [the RAAF AIP website](https://ais-af.airforce.gov.au/australian-aip){target=new} contains the necessary charts (available in the TERMA) and description of procedures (in each airports' FIHA).

docs/enroute/brisbane/ISA.md

@@ -32,19 +32,42 @@ ISA is responsible for **ARA**, **STR**, and **WEG** when they are offline.
 
 ### Reclassifications
 === "SG CTR"
-	When **SG TCU** is offline, SG MIL CTR and associated restricted airspace reverts to Class G, and is administered by ARA.
-
-	!!! tip
-        Consider publishing a pre-formatted **ATIS Zulu** for the aerodrome, to inform pilots about the airspace reclassification.
+	The restricted airspace around YPWR is classified as Class G by default, and is only reclassified as controlled airspace when **SGA** is online. When **SGA** is offline, the area remains Class G, and is administered by ARA.
 
 ## Departure and Arrival Procedures
 
 ### YBSG
 ARA is responsibile for facilitating operations in and out of YBSG.
 
-<!-- ## Special Use Airspace 
-### Restricted Areas
--->
+## Local Procedures
+### Special Use Airspace
+There are multiple volumes of [SUA](../../../controller-skills/sua) within ISA airspace, mostly associated with military operations in and out of YBSG.
+
+<figure markdown>
+![Notable SUA in ISA Airspace](../img/isa_sua.png){ width="700" }
+  <figcaption>Notable SUA in ISA Airspace</figcaption>
+</figure>
+
+SG TCU must [give heads up coordination](../../../terminal/scherger/#sua-in-enroute-airspace) with the relevant enroute controllers **prior** to any departures intending to operate in a currently inactive SUA.
+
+!!! phraseology
+    <span class="hotline">**SGA** -> **ARA**</span>: "On the ground YBSG, FBED14, requests activation of M610A `F125-F245`, from 0300 until 0500.”  
+    <span class="hotline">**ARA** -> **SGA**</span>: "FBED14, expect activation of M610A `F125-F245` at 0300 until 0500."   
+    <span class="hotline">**SGA** -> **ARA**</span>: "FBED14."   
+
+Non-participating aircraft intending to transit an activated SUA should be rerouted, where possible, [subject to the VATSIM Code of Conduct](../../../sua/#ad-hoc-activations).
+
+#### M610A Scherger
+The M610A Scherger [MOA](../../../controller-skills/sua/#military-operating-areas) is located over western coast of North Queensland and the Gulf of Carpentaria, `F125-F245`, located entirely in ARA airspace. 
+
+The MOAs directly adjoin the SG TMA and when SGA is online aircraft will be transferred directly to/from the MOAs. When [WAL is offline](#reclassifications), aircraft will contact ARA for transit through the surrounding civilian airspace.
+
+Aircraft will generally enter and exit the MOA via the appropriate [military gate](../../../terminal/scherger/#military-gates).
+
+#### Townsville SUA
+There are two SUA associated with military operations at Townsville which clip ISA airspace: the R738G-H Townsville (Land) restricted areas.
+
+TLA (or KEN(KEN, TBP) on their behalf) will coordinate the activation these SUA prior to any activity.
 
 ## STAR Clearance Expectation
 ### Handoff
@@ -62,20 +85,23 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio
 
 ### SG TCU
 #### Airspace
-The limits of the SG TCU are `SFC` to `F245` within 40 NM of the YBSG ARP. This may be amended by NOTAM.
+The limits of the SG TCU are `SFC` to `F245` within 40 NM of the YBSG ARP.
 
 #### Arrivals/Overfliers
-The Standard assignable level from ARA to SG TCU is `F130`, tracking via WP VOR.
+Voiceless for all aircraft:
+
+- With ADES **YBSG**; and
+- Tracking via **WP VOR**; and
+- Assigned `F130`.
 
-All other aircraft must be voice coordinated to SG TCU prior to **20nm** from the boundary.
+All other aircraft coming from ARA CTA must be **Heads-up** Coordinated to SGA prior to **20nm** from the boundary.
 
 #### Departures
-The Standard Assignable level from SG TCU to ARA is `F240`, and tracking via their planned route.
+Voiceless for all aircraft:
 
-#### SG ADC
-When SG TCU is offline, coordination is not required between ISA(ARA) and SG ADC. Aircraft entering SG ADC airspace shall be handed off, and instructed to contact SG ADC for onwards clearance.
+- Assigned the lower of `F240` or the `RFL`.
 
-SG ADC owns the Class C airspace within the SG CTR from `SFC` to `A015`.
+All other aircraft going into ARA CTA will be **Heads-up** Coordinated by SGA prior to the boundary.
 
 ### ISA Internal
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.