TCU Position Restructuring and Departure Frequencies

docs/aerodromes/classc/Adelaide.md

@@ -126,28 +126,21 @@ The Operational Information field should be updated based on the runway mode in
 
 All other aircraft require a Next call to AD TCU.
 
-The Standard Assignable level from AD ADC to AD TCU is:  
+The Standard Assignable level from AD ADC to AD TCU is:
 
 | Aircraft | Level |
-| -------- | ----- |
+| ------------ | ----- |
 | Jets | `A050` |
 | Non-Jets | The lower of `A040` and `RFL` |
 
 ### Departures Controller
-When **AAW** is online, the AD TCU airspace is split down the 05/23 Runway Centreline. As such, departing aircraft shall be instructed to contact the departures controller corresponding to the direction of turn of the aircraft after departure
-
-| Tracking via            | Departure Runway      | Departures Controller        |
-| ------------------ | -------------- | ---------------- |
-| VILAD   | 05/23/12   | AAE         |
-| UPROT    | 05/23/12   | AAE         |
-| AVDEN    | 05/23/12   | AAE         |
-| BENDO     | 05/23/12 | AAE          | 
-| ALBUT    | 05/23/12  | AAE          | 
-| EEMUE    | 05/23/30  | AAW          | 
-| GILES   | 05/23/30  | AAW          | 
-| YORKE    | 05/23/30  | AAW          | 
-| AREPA    | 05/23/30  | AAW          | 
-| HOLIT    | 05/23/30  | AAW          | 
-| ORBUN    | 05/23/30  | AAW          | 
-| All   | 12  | AAE          | 
-| All   | 30  | AAW          | 
+When **AAW** is online, the AD TCU is [split down the runway 05/23 centreline](../../terminal/adelaide#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel.
+
+| Runway | Via  | Departure Controller |
+| ------ | ---- | -------------------- |
+| 05 | AREPA<br>GILES<br>ORBUN<br>West | AAW |
+| 05 | AVDEN<br>BENDO<br>UPROT<br>East | AAE |
+| 12 | All | AAE |
+| 23 | AREPA<br>GILES<br>ORBUN<br>West | AAW |
+| 23 | AVDEN<br>BENDO<br>UPROT<br>East | AAE |
+| 30 | All | AAW |

docs/aerodromes/classc/Brisbane.md

@@ -240,13 +240,34 @@ The Standard Assignable level from BN ADC to BN TCU is:
 | Non-Jets | The lower of `A040` and `RFL` |
 
 ### Departures Controller
-Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BDN** and/or **BDS** are online.
+When both **BDN** and **BDS** are online, the BN TCU is [split down the runway 01R/19L centreline](../../terminal/brisbane#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel.
+
+=== "01 PROPS"
+
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 01L | All | BDN |
+    | 01R | All | BDS |
+
+=== "19 PROPS"
+
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 19L | BIXAD<br>WACKO | BDN |
+    | 19L | All others | BDS|
+    | 19R | All | BDN |
+
+=== "SODPROPS"
+
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 01R | All | BDS |
 
 ### Standard Assignable Departure Headings
 Aircraft that have been cleared the **BN (RADAR) SID** must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required (excluding during SODPROPS) to the BN TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below:
 
-| Runway | Assigned Heading 
-| ----------------- | -------------- |
+| Runway | Assigned Heading |
+| ------ | -------------- |
 | 01L | H340 |
 | 01R | H120 |
 | 19L | H110 |

docs/aerodromes/classc/Canberra.md

@@ -163,5 +163,14 @@ The Standard Assignable level from CB ADC to CB TCU is:
 | IFR | `A100` |
 | VFR | The lower of `A040` and `RFL` |
 
-### Runway Change
-Any Runway change must be prior coordinated to **CB TCU**.
+### Departures Controller
+When **CBW** is online, the CB TCU is [split down the runway 17/35 centreline](../../terminal/Canberra#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel.
+
+| Runway | Via  | Departure Controller |
+| ------ | ---- | -------------------- |
+| 12 | All | AAE |
+| 17 | DUBUS<br>HOWLY<br>NONUP<br>TANTA<br>WG VOR<br>West | AAW |
+| 17 | AKMIR<br>AVBEG<br>CULIN<br>East | AAE |
+| 30 | All | CBW |
+| 35 | AVBEG<br>DUBUS<br>HOWLY<br>NONUP<br>TANTA<br>WG VOR<br>West | AAW |
+| 35 | AKMIR<br>CULIN<br>East | AAE |

docs/aerodromes/classc/Melbourne.md

@@ -268,7 +268,31 @@ The following Standard Assignable Headings may be used for aircraft assigned the
 Any runway change must be prior coordinated to **MAE** and **EN ADC**.
 
 ### Departures Controller
-Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online.
+When both **MDS** and **MDN** are online, the ML TCU is [divided according to the runway mode in use](../../terminal/melbourne#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel.
+
+=== "09"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 09 | Tracking NW, N, or NE | MDN |
+    | 09 | Tracking SW, S, or SE | MDS |
+
+=== "16"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 16 | MNG<br>NONIX<br>DOSEL<br>KEPPA<br>PEDNI<br>Tracking NW, N, or NE | MDN |
+    | 16 | CORRS<br>CRENA<br>ESDIG<br>ISPEG<br>SUNTI<br>Tracking SW, S, or SE | MDS |
+
+=== "27"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 27 | MNG<br>NONIX<br>DOSEL<br>KEPPA<br>PEDNI<br>Tracking NW, N, or NE | MDN |
+    | 27 | CORRS<br>CRENA<br>ESDIG<br>SUNTI<br>Tracking SW, S, or SE | MDS |
+
+=== "34"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 34 | CORRS<br>MNG<br>NONIX<br>DOSEL<br>KEPPA<br>PEDNI<br>SUNTI<br>Tracking NW, N, or NE | MDN |
+    | 34 | CRENA<br>ESDIG<br>Tracking SW, S, or SE | MDS |
 
 ### EN ADC
 EN ADC is responsible for separation with all YMML traffic, and will coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with YMML traffic.

docs/aerodromes/classc/Sydney.md

@@ -497,7 +497,35 @@ The Standard Assignable level from SY ADC to SY TCU is:
 | Non-Jets | The lower of `A030` and `RFL` |
 
 ### Departures Controller
-Refer to [Sydney TCU Airspace Division](../../../terminal/sydney/#airspace-division) for information on airspace divisions when **SDN** and/or **SDS** are online.
+When both **SDS** and **SDN** are online, the SY TCU is [divided according to the runway mode in use](../../terminal/sydney#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure, SID, and direction of travel.
+
+=== "07"
+    | Runway |  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 07 | FISHA SID, OLSEM Transition<br>Tracking N, or NE | SDN |
+    | 07 | FISHA SID, WOL Transition<br>Tracking S, W, or SW | SDS |
+
+=== "16s"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 16L | ABBEY SID, WOL Transition<br>Tracking S or SW | SDS |
+	| 16L | KEVIN SID<br>Tracking SE, E, NE, or N | SDN |
+    | 16R | All | SDS |
+
+=== "25"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 25 | Tracking N, or NE | SDN |
+    | 25 | Tracking S, W, or SW  | SDS |
+
+=== "34s"
+    | Runway | Via  | Departure Controller |
+    | ------ | ---- | -------------------- |
+    | 34L | RIC SID<br>Tracking N, or NE | SDN |
+    | 34L | KADOM SID<br>WOL SID<br>Tracking S, W, or SW | SDS |
+    | 34R | OLSEM SID<br>Tracking N, or NE | SDN |
+    | 34R | MARUB SID, WOL Trans<br>Tracking S, W, or SW | SDS |
+
 
 ### Standard Assignable Departure Headings
 Aircraft that have been cleared the **SY (RADAR) SID** must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required to the SY TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below:

docs/terminal/adelaide.md

@@ -9,8 +9,9 @@
 | Name                          | ID      | Callsign                | Frequency   | Login ID      |
 | ----------------------------- | ------- | ----------------------- | ----------- | ------------- |
 | **Adelaide Approach East**    | **AAE** | **Adelaide Approach**   | **118.200** | **AD_APP**    |
-| <span class="indented">Adelaide Approach West :material-information-outline:{ title="Non-standard position"}  | AAW | Adelaide Approach  | 124.200  | AD-W_APP |
-| <span class="indented">Adelaide Flow :material-information-outline:{ title="Non-standard position"}           | AFL |                    |          | AD_FMP   |
+| <span class="indented">Adelaide Approach West :material-information-outline:{ title="Non-standard position"}  | AAW | Adelaide Approach  | 124.200 | AD-W_APP |
+| <span class="indented">Adelaide Radar :material-information-outline:{ title="Non-standard position"}          | AAR | Adelaide Approach  | 130.450 | AD-R_DEP |
+| <span class="indented">Adelaide Flow :material-information-outline:{ title="Non-standard position"}           | AFL |                    |         | AD_FMP   |
 
 !!! abstract "Non-Standard Positions"
     :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}.  
@@ -37,6 +38,9 @@ ED CTR reverts to Class G when **ED ADC** is offline, and is administered by the
   <figcaption>AD TCU Structure</figcaption>
 </figure>
 
+#### Adelaide Radar (AAR)
+AAR is responsible for the provision of FIS in Class G airspace within the AD TMA. It is a role normally performed by the controller responsible for **AAE**. The position is designed to reduce the workload of other TMA positions by identifing and issuing clearance (where available) to aircraft OCTA, then transferring them to the relevant TMA controller.
+
 ## Local Procedures 
 ### Scenic Coastal Flights
 VFR aircraft may transit the control zone tracking coastal north or southbound, generally at `A005`. **AD TCU** is responsible for ensuring these aircraft remain separated from aircraft arriving/departing at YPAD and may delegate this responsibility to **AD ADC**.  

docs/terminal/brisbane.md

@@ -13,6 +13,7 @@
 | <span class="indented">Brisbane Departures North :material-information-outline:{ title="Non-standard position"} | BDN | Brisbane Departures | 133.450 | BN_DEP   |
 | <span class="indented">Brisbane Departures South :material-information-outline:{ title="Non-standard position"} | BDS | Brisbane Departures | 118.450 | BN-S_DEP |
 | <span class="indented">Gold Coast Approach :material-information-outline:{ title="Non-standard position"}       | BAC | Brisbane Approach   | 123.500 | BN-C_APP |
+| <span class="indented">Brisbane Radar :material-information-outline:{ title="Non-standard position"}            | SHN | Brisbane Centre     | 119.500 | BN-R_DEP |
 | <span class="indented">Brisbane Flow :material-information-outline:{ title="Non-standard position"}             | BFL |                     |         | BN_FMP   |
 
 !!! abstract "Non-Standard Positions"
@@ -59,6 +60,9 @@ The divisions of the airspace between **BAN**, **BAS**, **BDS**, **BDN**, and **
 	![SODPROPS TCU Structure](img/bnsodprops.png){ width="700" }
 	  <figcaption>SODPROPS TCU Structure</figcaption>
 	</figure>
+
+#### Brisbane Radar (SHN)
+SHN is responsible for the provision of FIS in Class G airspace within the BN TMA. The position is designed to reduce the workload of other TMA positions by identifing and issuing clearance (where available) to aircraft OCTA, then transferring them to the relevant TMA controller.
 
 #### Airspace Structural Arrangements
 Pursuant to Section 2 of the [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}, **"North"**/**"West"** positions shall assume the airspace of corresponding **"South"**/**"East"** positions when the latter are inactive (e.g. **BAN** assumes **BAS** airspace), and vice versa.