YWLM ops, other misc changes

docs/aerodromes/Launceston.md

@@ -28,9 +28,9 @@ Refer to [Class D Tower Skills](../../controller-skills/classdtwr) for more info
 ## SID Selection
 Aircraft planned via **MIKIS**, **TASUM**, or **VEKLO** shall be assigned the relevant Procedural SID.
 
-Aircraft planned via **IRSOM**, **ONAGI**, **VIMAP**, **NUNPA**, **MOTRA**, or **MORGO** shall be assigned the relevant **ALPHA** Procedural SID.
+Aircraft planned via **IRSOM** **MORGO**, **ONAGI**, **VIMAP**, **NUNPA**, or **MOTRA**, departing Runway 32L, shall be assigned the relevant **ALPHA** Procedural SID.
 
-Aircraft planned via **ONAGI**, **VIMAP**, **NUNPA**, or **MOTRA** may be assigned the relevant **BRAVO** Procedural SID *on pilot request*.
+Aircraft planned via **ONAGI**, **VIMAP**, **NUNPA**, or **MOTRA**, departing Runway 14R, shall be assigned the relevant **BRAVO** Procedural SID.
 
 **Non-Jet** Aircraft planned via **IRSOM**, **ONAGI**, or **MORGO** may be assigned the relevant **CHARLIE** Procedural SID *on pilot request*.
 
@@ -76,6 +76,7 @@ b) Aircraft using a runway not on the ATIS
 The Standard Assignable level from LT ADC to LTA is:  
 For Jets: `A080`  
 For Non-Jets: The lower of `A045` or the `RFL`.
+
 ### Arrivals/Overfliers
 LTA will heads-up coordinate arrivals/overfliers from Class C to LT ADC.  
 IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to LT ADC, unless LT ADC nominates a restriction.  

docs/controller-skills/annotations.md

@@ -26,6 +26,7 @@ Here is a complete list of standard annotations controllers should be entering i
 | Place-brearing-distance locations | Position expressed as a bearing and distance from a datum.<br />(place)(bearing)(distance) | SY335045<br />*ie: SY DME, R335, 45 NM* |
 | Amended route | When assigned a route that differs to that planned | AR |
 | Assigned Heading | H(heading) | H350 |
+| Track Extended Centreline | | TEC |
 
 ## Requests, Requirements and Restrictions
 | Information | Meaning and Usage | Example |
@@ -93,6 +94,8 @@ Here is a complete list of standard annotations controllers should be entering i
 | QNH issued (en route traffic is altimeter setting region) | Q(final 2-digit value) | Q15 |
 | No level restrictions on STAR | | NHR |
 | No STAR (or cancel STAR) | | NS |
+| Aircraft has reported Visual | | V |
+| Aircraft has reported Runway in Sight | | R |
 
 ## Less commonly used
 

docs/enroute/Brisbane Centre/ARL.md

@@ -20,6 +20,8 @@ When **TW ADC** is offline, TW CTR (Class D and C `SFC` to `A085`) reverts to Cl
 
 When **CFS ADC** is offline, CFS CTR (Class D `SFC` to `A045`) reverts to Class G, and is administered by MNN and INL. MNN is **not permitted** to provide a [top-down procedural service](../../../aerodromes/Coffs), only INL can do this, and they must coordinate with MNN if they are doing so.
 
+When **WLM TCU** is offline, WLM MIL CTR (Class C `SFC` to `A065`) reverts to Class G, and WLM MIL CTR (Class C `A065` to `F125`) reverts to Class E. This airspace is administered by the appropriate ARL subsector. Alternatively, ARL(MLD) may provide a [top-down service](../../../military/williamtown) if they wish.  
+
 <figure markdown>
 ![Armidale Airspace](../assets/arl.png){ width="700" }
   <figcaption>Armidale Airspace</figcaption>
@@ -55,6 +57,9 @@ OCN is responsible for sequencing, issuing STAR Clearances, and issuing descent
 
 Refer to the [Sequencing into YSSY](#sequencing-into-yssy) notes below for runway selection notes.
 
+### YWLM Operations
+All ARL subsectors are responsible for assigning STARs to aircraft inbound to YWLM, and the STAR shall be issued by the first ARL subsector to take jurisdiction of the aircraft.
+
 ### Sequencing into YSSY
 Sequencing arrivals from the north/east into YSSY is a joint responsibility of the subsectors of ARL. Initial sequencing actions for aircraft from the north should be performed by ARL and MNN, with fine tuning and any holding required issued by CNK. 
 
@@ -180,36 +185,23 @@ Any aircraft that will enter CFS ADC airspace, and not landing at YCFS, must be
 
 ### WLM TCU
 #### Airspace
-By default, **WLM TCU** (when online) owns the airspace within the **R578A-G** restricted areas, unless stated otherwise by ad-hoc release or NOTAM. It is the responsibility of the **WLM TCU** controller to inform ARL(All) of what airspace they are assuming.
+By default, **WLM TCU** (when online) owns the airspace within the WLM MIL CTR `SFC` to `F125`, unless stated otherwise by ad-hoc release or NOTAM. It is the responsibility of the **WLM TCU** controller to inform ARL(All) of what airspace they are assuming.
 
-When WLM TCU is offline, **ARL** administers the Class E airspace (generally **A085** and above, or **A045** and above in some airspace steps) and the military Class C airspace is reclassified as Class G.
+Refer to [Airspace](#airspace) for operations when WLM TCU is offline.
 
 #### Departures
-Departures from **WLM TCU** in to ARL(All) Class C will be heads-up coordinated.
+Voiceless coordination is in place from WLM TCU to ARL(All) for aircraft assigned the lower of `F120` or the `RFL`, and tracking via a Procedural SID terminus.
 
 !!! example
-    <span class="hotline">**WLM TCU** -> **MNN**</span>: "Departed YWLM, WGTL33, will be assigned F120"  
-    <span class="hotline">**MNN** -> **WLM TCU**</span>: "WGTL33, F120"  
+    <span class="hotline">**WLM TCU** -> **MLD**</span>: "QJE1597, request DCT OMGAB"  
+    <span class="hotline">**MLD** -> **WLM TCU**</span>: "QJE1597, concur DCT OMGAB"  
 
 #### Arrivals/Overfliers
-All aircraft transiting from ARL(All) to **WLM TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **WLM TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the ARL(All) and **WLM TCU** controller agree on.
+The Standard assignable level from ARL(All) to WLM TCU is `A090`, and assigned a STAR. All other aircraft must be prior coordinated.
 
 !!! example
-    <span class="hotline">**MNN** -> **WLM TCU**</span>: "via SANAD, JST458, will be assigned F130"  
-    <span class="hotline">**WLM TCU** -> **MNN**</span>: "JST458, F130"  
-
-!!! tip
-    To keep it simple and safe, coordinate departures at the Lowest Assignable level over the TCU (eg, with standard WLM TCU configuration, `F130`). You may coordinate other levels with WLM TCU if required for separation purposes.
-
-#### R574 Release
-To put it bluntly, the R574 Restricted Area is quite large.
-
-<figure markdown>
-![R574 Restricted Area](../../military/img/r574.png){ width="700" }
-  <figcaption>R574 Restricted Area</figcaption>
-</figure>
-
-It also occupies a lot of airspace that would commonly be used by YSSY arrivals and departures. If YWLM military operations are taking ownership of this airspace, it is good practice to negotiate an airspace release, whether that be a lateral or vertical portion of airspace (or a combination), to enable them to facilitate YSSY arrivals and departures with minimal impact.
+    <span class="hotline">**CNK** -> **WLM TCU**</span>: "QFA1968, request DCT UPTEB"  
+    <span class="hotline">**WLM TCU** -> **CNK**</span>: "QFA1968, concur DCT UPTEB"  
 
 ### TSN/HWE (Oceanic)
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-oceanic), Heads-up coordinate prior to **15 mins** to boundary.

docs/military/townsville.md

@@ -24,16 +24,16 @@ TL TCU owns the Class C and G airspace within 36 DME TL from `SFC` to `F180`
 </figure>
 
 ### ADC
-TL ADC owns the Class C arispace in the TL CTR (Extends to 7NM of the thresholds of 01 and 19.) from `SFC` to `A015`. This airsapce is designed to facilitate Helicopter Traffic and Ciruit Traffic.
+TL ADC owns the Class C airspace in the TL CTR (Extends to 7NM from the thresholds of Runway 01/19) from `SFC` to `A015`. This airsapce is designed to facilitate Helicopter Traffic and Ciruit Traffic.
 
 ## Aerodrome
 ### Runway Operations
-Runways 01 and 19 are the primary runways at Townsville. 
-Runway 07 is often used in conjunction with 01 for VFR arrivals and Helicopter Traffic. 
+Runway 01/19 are the primary runways at Townsville. 
+Runway 07/25 is often used in conjunction with 01 for VFR arrivals and Helicopter Traffic. 
 
 ### NON-RNAV Departures
 For non-RNAV approved IFR aircaft with a wake turbulence category of medium or greater, issue a RADAR SID.
-For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or Radar SID
+For non-RNAV approved IFR aircraft with a wake turbulence category of light, issue a visual departure or RADAR SID
 
 ## Charts
 !!! note
@@ -69,7 +69,6 @@ The Standard assignable level from TBP to TL TCU is `A100`, and assigned a STAR.
 
 ### TL ADC
 #### Auto Release  
-
 'Next' coordination is **not** required from TL ADC to TL TCU for aircraft that are:  
 a) Departing from a runway nominated in the ATIS; and  
 b) Assigned the standard assignable level;  
@@ -80,4 +79,4 @@ c) Assigned a **Procedural** SID
     <span class="hotline">**TL TCU** -> **TL ADC**</span>: "DNGO05, Assigned Heading Left 150, unrestricted"  
     <span class="hotline">**TL ADC** -> **TL TCU**</span>: "Assigned Heading Left 150, DNGO05"  
 
-    The Standard Assignable level from TL ADC to TL TCU is the lower of `F180` or the RFL.
+The Standard Assignable level from TL ADC to TL TCU is the lower of `F180` or the RFL.

docs/military/williamtown.md

@@ -16,100 +16,64 @@
 
 ## Airspace
 ### Default
-By default, WLM APP owns all of the R578 Restricted Areas, detailed below:
-
-- R578A (`A050`-`F125`)  
-- R578B (`SFC`-`F125`)  
-- R578C (`A045`-`F125`)  
-- R578D (`A025`-`F125`)  
-- R578E (`SFC`-`A100`)  
-- R578F (`A045`-`A085`)  
-- R578G (`A035`-`A085`)
+By default, WLM TCU owns the airspace within the WLM MIL CTR `SFC` to `F125`. This may be amended by NOTAM.
 
 #### Diagram
 <figure markdown>
-![Default WLM TCU Upper Limits](img/wlmapp.png){ width="700" }
-  <figcaption>Default WLM TCU Upper Limits</figcaption>
+![WLM TCU Airspace](img/wlmtcu.png){ width="700" }
+  <figcaption>WLM TCU Airspace</figcaption>
 </figure>
 
-### Optional, as required
-WLM APP can negotiate further airspace releases from surrounding ENR sectors of the following Restricted Areas:
-
-- R580 (`A045`-`F125`)  
-- R583A (`SFC`-`F125`)  
-- R583B (`SFC`-`A100`)  
-- R587A (`F125`-`F600`)  
-- R587B (`F125`-`F600`)  
-- R596 (`SFC`-`F120`)
-
 !!! note
     It is the responsibility of the WLM TCU controller to negotiate any airspace releases with ARL(All).
 
-### Classification
-All airspace owned by WLM TCU when online is reclassified to **Class C**.
-
 ### Tower
-When WLM ADC is online, the airspace below the R578A restricted area is owned by WLM ADC (`SFC`-`A050`), and is **Class C**.
+When WLM ADC is online, they own the within the WLM MIL CTR A (`SFC`-`A050`). This may be amended/released as required between WLM ADC and WLM TCU.
 
 <figure markdown>
-![WLM ADC Airspace](img/wlmtwr.png){ width="700" }
+![WLM ADC Airspace](img/wlmadc.png){ width="700" }
   <figcaption>WLM ADC Airspace</figcaption>
 </figure>
 
-### Surveillance
-WLM ADC is permitted to use Surveillance standards for separation. Surveillance coverage can be expected to be available at all levels in the WLM ADC airspace.  
-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.
-
 ## 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}
 
 ## Coordination
-### WLM TCU / ARL(All)
+### ARL(All)
 
 #### Airspace
-Due to the variable nature of the WLM TCU airspace, WLM APP shall coordinate to the relevant ENR exactly what airspace is being released, upon either ARL(All) or WLM APP logging on.
+Any airspace releases from the default setup must be coordinated and agreed upon with ARL. It is also good practice to remind them of any airspace releases that may be active due to NOTAMs.
 
 #### Departures
-Due to the nature of WLM TCU operations, and the proximity to busy YSSY airspace, all departures shall be heads-up coordinated to ARL(All) prior to **10nm** from the boundary. Practically, this will need to be completed as soon as possible, ie, as soon as the aircraft becomes identified on departure.
+Voiceless coordination is in place from WLM TCU to ARL(All) for aircraft assigned the lower of `F120` or the `RFL`, and tracking via a Procedural SID terminus.
 
-!!! example
-    <span class="coldline">**WLM TCU** -> **MNN**</span>: "via OMBUP, UTY1105, will be assigned F120"  
-    <span class="coldline">**MNN** -> **WLM TCU**</span>: "UTY1105, F120"  
-#### Arrivals/Overfliers
-All aircraft transiting from CNK/MND/MNN to **WLM TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **WLM TCU** are fairly ad-hoc, so there are no standard assignable levels, simply whatever the CNK/MND/MNN and **WLM TCU** controller agree on.
+Any aircraft not meeting the above criteria must be prior coordinated to ARL(All).
 
 !!! example
-    <span class="coldline">**MNN** -> **WLM TCU**</span>: "via SANAD, JST458, will be assigned F130"  
-    <span class="coldline">**WLM TCU** -> **MNN**</span>: "JST458, F130"  
+    <span class="hotline">**WLM TCU** -> **MLD**</span>: "QJE1597, request DCT OMGAB"  
+    <span class="hotline">**MLD** -> **WLM TCU**</span>: "QJE1597, concur DCT OMGAB"  
 
-!!! tip
-    To keep it simple and safe, coordinate departures at the Highest Assignable level within your airspace (eg, with standard WLM TCU configuration, F120 to the East, A090 to the North West, A080 to the South West). You may coordinate other levels with ARL(All) if required for separation purposes.
+#### Arrivals/Overfliers
+The Standard assignable level from ARL(All) to WLM TCU is `A090`, and assigned a STAR. All other aircraft must be prior coordinated.
 
-### WLM TCU / WLM ADC
-### Departures
-A 'Next' call is made for all aircraft when they are next to depart. WLM ADC must inform WLM TCU if the aircraft does not depart within **2 minutes** of the next call.
+### TCU/ADC
+#### Departures
+'Next' coordination is **not** required from WLM ADC to WLM TCU for aircraft that are:  
+a) Departing from a runway nominated in the ATIS; and  
+b) Assigned the standard assignable level;  
+c) Assigned a **Procedural** SID  
 
 !!! example
-    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "Next, JST471"  
-    <span class="hotline">**WLM TCU** -> **WLM ADC**</span>: "JST471"
-
-The Standard Assignable level from WLM ADC to WLM TCU is the lower of `A050` or the `RFL`, and assigned a SID. Any other aircraft must be heads-up coordinated in full.
+    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "Next, MVP"  
+    <span class="hotline">**WLM TCU** -> **WLM ADC**</span>: "MVP, Left Heading 010, Unrestricted"  
+    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "Left Heading 010, MVP"  
 
-!!! example
-    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "Next, DPOT27"  
-    <span class="hotline">**WLM TCU** -> **WLM ADC**</span>: "DPOT27, A080"  
-    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "A080, DPOT27"
+The Standard Assignable level from WLM ADC to WLM TCU is the lower of `F120` or the `RFL`.
 
-### Arrivals/Overfliers
-WLM TCU must heads-up coordinate all arrivals and overfliers to WLM ADC prior to handoff. Practically, this needs to be done as soon as possible, ie, as soon as WLM TCU receives coordination on the aircraft.
+#### Arrivals/Overfliers
+Voiceless coordination is in place from WLM TCU to WLM ADC for arrivals cleared for an approach on to a runway nominated on the ATIS. All other aircraft and all overfliers must be heads-up coordinated as soon as practical.
 
 !!! example
     <span class="hotline">**WLM TCU** -> **WLM ADC**</span>: "via WLM, ZULU, Close formation of 5, do you have any restrictions or requirements?”  
-    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "ZULU, no frequency requirements, A040"  
-
-Aircraft with ADES YWLM shall be cleared for the approach prior to handoff.
-
-!!! example
-    <span class="hotline">**WLM TCU** -> **WLM ADC**</span>: "via BLAFF for the ILS RWY 12, VOZ1593”  
-    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "VOZ1593"  
+    <span class="hotline">**WLM ADC** -> **WLM TCU**</span>: "ZULU, no restrictions or requirements, A040"  

docs/terminal/adelaide.md

@@ -91,7 +91,7 @@ The Standard assignable level from TBD/AUG to AD TCU is `A090`, and assigned a S
 
 ### AD ADC
 #### Auto Release
-'Next' coordination is **not** required to from AD ADC for aircraft that are:   
+'Next' coordination is **not** required from AD ADC for aircraft that are:   
   a) Departing from a runway nominated on the ATIS; and  
   b) Assigned the standard assignable level; and  
   c) Assigned a **Procedural** SID

docs/terminal/cairns.md

@@ -111,7 +111,7 @@ The following speeds apply from the Feeder Fix:
 
 ### CS ADC
 #### Departures
-'Next' coordination is **not** required for aircraft that are:   
+'Next' coordination is **not** required from CS ADC for aircraft that are:   
   a) Departing from a runway nominated on the ATIS; and  
   b) Assigned the standard assignable level; and  
   c) Assigned a **Procedural** SID

docs/terminal/canberra.md

@@ -39,7 +39,7 @@ The Standard assignable level from ENR to CB TCU is `F130`. All other levels mus
 
 ### CB ADC
 #### Auto Release
-'Next' coordination is **not** required to CB TCU for aircraft that are:   
+'Next' coordination is **not** required from CB ADC for aircraft that are:   
   a) Departing from a runway nominated on the ATIS; and  
   b) Assigned the standard assignable level; and  
   c) Assigned a **Procedural** SID

docs/terminal/coral.md

@@ -44,9 +44,10 @@ The Standard assignable level from KEN(SWY) to MKA is `A070`, and assigned a STA
 
 ### MK/RK ADC
 #### Auto Release
-"Next" Coordination to TCU is required for all departures not assigned a SID.
-
-"Next" Coordination is a procedure where the **ADC** controller gives a heads-up to the TCU controller about an impending departure not on a SID. The TCU controller will respond by assigning a visual heading to the aircraft, for the **ADC** controller to pass on with their takeoff clearance.
+'Next' coordination is **not** required from MK/RK ADC for aircraft that are:   
+  a) Departing from a runway nominated on the ATIS; and  
+  b) Assigned the standard assignable level; and  
+  c) Assigned a **Procedural** SID
 
 !!! example
     <span class="hotline">**MK ADC** -> **MKA**</span>: "Next, ABC, runway 14"  
@@ -55,11 +56,9 @@ The Standard assignable level from KEN(SWY) to MKA is `A070`, and assigned a STA
 
 The TCU controller can suspend/resume Auto Release at any time, with the concurrence of **ADC**.
 
-!!! Note
-    "Next" Coordination to TCU is not required for aircraft assigned a **Procedural SID** and the Standard Assignable Level.
-
 The Standard Assignable level from MK/RK ADC to MKA/RKA is the lower of `A060` or the `RFL`.
 
+#### MK/RK SMC
 The controller assuming responsibility of **SMC** shall give heads-up coordination to TCU controller prior to the issue of the following clearances:  
 
 - VFR Departures  

docs/terminal/melbourne.md

@@ -206,7 +206,7 @@ The Standard assignable level from ENR to ML TCU is `A090`. All other levels mus
 !!! important
     Melbourne utilises auto release for all **Procedural** SIDs and the **ML (RADAR)** SID provided aircraft are assigned the Standard Assignable Level and a [Standard Assignable Heading](#standard-assignable-departure-headings).
 
-'Next' coordination is **not** required for aircraft that are:   
+'Next' coordination is **not** required from ML ADC for aircraft that are:   
     a) Departing from a runway nominated on the ATIS; and  
     b) Assigned `A050`; and  
     c) Assigned a **Procedural** SID; or