Merge pull request #478 from vatpac-technology/coordination

Coordination Rules Refresh & Other Changes

Author: mattk04

docs/aerodromes/classc/Adelaide.md

@@ -104,26 +104,20 @@ Shall be assigned the **Radar SID**.
 
 ## Coordination
 ### Auto Release
-'Next' coordination is **not** required to AD TCU 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
+[Next](../../controller-skills/coordination.md#next) coordination is **not** required to AD TCU for aircraft that are:   
 
-All other aircraft require a 'Next' call to AD TCU.
+  - Departing from a runway nominated on the ATIS; and  
+  - Assigned the standard assignable level; and  
+  - Assigned a **Procedural** SID
 
-!!! phraseology
-    <span class="hotline">**AD ADC** -> **AD TCU**</span>: "Next, RXA4362, Runway 23"  
-    <span class="hotline">**AD TCU** -> **AD ADC**</span>: "RXA4362, Track Extended Centreline, Unrestricted"  
-    <span class="hotline">**AD ADC** -> **AD TCU**</span>: "Track Extended Centreline, RXA4362"  
-    
-    **AD ADC**: "RXA4362, Track Extended Centreline 222 degrees, Runway 23, Cleared for Takeoff"  
-    **RXA4362**: "Track Extended Centreline 222 degrees, Runway 23, Cleared for Takeoff, RXA4362"
-
-The AD TCU controller can suspend/resume Auto Release at any time, with the concurrence of **AD ADC**.
+All other aircraft require a Next call to AD TCU.
 
 The Standard Assignable level from AD ADC to AD TCU is:  
-For Jets: `A050`  
-For Non-Jets: The lower of `A040` or the `RFL`
+
+| Aircraft | Level |
+| -------- | ----- |
+| Jets | `A050` |
+| Non-Jets | The lower of `A040` and `RFL` |
 
 ### Departures Controller
 When **AAE** 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

docs/aerodromes/classc/Amberley.md

@@ -167,16 +167,14 @@ Circuits are flown at `A010`, in the same circuit direction as the duty runway.
 
 ## Coordination
 ### AMB TCU
-'Next' coordination is required from AMB ADC to AMB TCU for all aircraft.
-
-!!! phraseology
-    <span class="hotline">**AMB ADC** -> **AMB TCU**</span>: "Next, STAL56, runway 33"  
-    <span class="hotline">**AMB TCU** -> **AMB ADC**</span>: "STAL56, unrestricted"  
-    <span class="hotline">**AMB ADC** -> **AMB TCU**</span>: "STAL56"  
+[Next](../../controller-skills/coordination.md#next) coordination is required from AMB ADC to AMB TCU for all aircraft.
 
 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.
+
+| Assigned Departure | Level |
+| ------------------ | ----- |
+| Procedural SID | The lower of `F180` and `RFL` |
+| Coded Departure | `F190` |
 
 ## Charts
 !!! abstract "Reference"

docs/aerodromes/classc/Brisbane.md

@@ -198,30 +198,23 @@ Both taxiway **H2** and **F4** are inside the maneuvering area and treated like
 
 ## Coordination
 ### Auto Release
-'Next' coordination is **not** required to BN TCU for aircraft that are:
+[Next](../../controller-skills/coordination.md#next) coordination is **not** required to BN TCU for aircraft that are:
 
 - Departing from a runway nominated on the ATIS (except during SODPROPS^); and  
 - Assigned the standard assignable level; and  
 - Assigned a **Procedural** SID; or
 - Assigned the **Radar** SID with a [Standard Assignable Heading](#standard-assignable-departure-headings)
 
-^Auto Release is not available during SODPROPS runway mode. All aircraft must be coordinated from BN ADC to BN TCU.
+^*Auto Release is not available during SODPROPS runway mode. All aircraft must be coordinated from BN ADC to BN TCU.*
 
 All other aircraft require a 'Next' call to BN TCU.
 
-!!! phraseology
-    <span class="hotline">**BN ADC** -> **BN TCU**</span>: "Next, QLK404D, Runway 19L"  
-    <span class="hotline">**BN TCU** -> **BN ADC**</span>: "QLK404D, heading 160, unrestricted"  
-    <span class="hotline">**BN ADC** -> **BN TCU**</span>: "Heading 160, QLK404D"   
-
-    **BN ADC**: "QLK404D, Assigned heading Left 160, Runway 19L, Cleared for Takeoff"  
-    **QLK404D**: "Left heading 160, Runway 19L, Cleared for Takeoff, QLK404D"
-
-The BN TCU controller can suspend/resume Auto Release at any time, with the concurrence of **BN ADC**.
-
 The Standard Assignable level from BN ADC to BN TCU is:  
-For Jets: `A060`  
-For Non-Jets: The lower of `A040` or the `RFL`
+
+| Aircraft | Level |
+| -------- | ----- |
+| Jets | `A060` |
+| 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.

docs/aerodromes/classc/Cairns.md

@@ -154,42 +154,30 @@ The ATIS approach expectation shall be `EXPECT INSTRUMENT APPROACH` when:
 Taxiways A2 and A between A2 and A3 are not available to aircraft above 7,000 kilograms. Taxiway A4 is not available to aircraft above 90,000 kilograms. Taxiway Y is not available to aircraft above 10,000 kilograms.
 
 ## Coordination
-
 ### CS TCU
 #### Auto Release
-'Next' coordination is **not** required 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
+[Next](../../controller-skills/coordination.md#next) coordination is **not** required for aircraft that are:   
 
-All other aircraft require a 'Next' call to CS TCU.
+  - Departing from a runway nominated on the ATIS; and  
+  - Assigned the standard assignable level; and  
+  - Assigned a **Procedural** SID
 
-!!! phraseology
-    <span class="hotline">**CS ADC** -> **CS TCU**</span>: "Next, HND151"  
-    <span class="hotline">**CS TCU** -> **CS ADC**</span>: "HND151, Heading 030, unrestricted"  
-    <span class="hotline">**CS ADC** -> **CS TCU**</span>: "Heading 030, HND151"   
+All other aircraft require a 'Next' call to CS TCU.
 
-    **CS ADC**: "HND151, Assigned heading Left 030, Runway 15, Cleared for Takeoff"  
-    **HND151**: "Left heading 030, Runway 15, Cleared for Takeoff, HNT151"
+The Standard Assignable level from CS ADC to CS TCU is:
 
-The Standard Assignable level from CS ADC to CS TCU is the lower of `A060` or the `RFL`.
+| Aircraft | Level |
+| -------- | ----- |
+| All | The lower of `A060` and `RFL` |
 
 #### Arrivals
 Aircraft tracking via a visual right base to runway 33 will be coordinated by CS TCU (see [Runway 33](#runway-33)). All other arriving aircraft do not require coordination.
 
 #### ACD to CS TCU
-The controller assuming responsibility of **CS ACD** shall give heads-up coordination to the relevant CS TCU controller prior to the issue of the following clearances:  
-a) VFR Departures  
-b) Aircraft using a runway not on the ATIS
+The controller assuming responsibility of **CS ACD** shall give [heads-up](../../controller-skills/coordination.md#airways-clearance) coordination to the relevant CS TCU controller prior to the issue of the following clearances:  
 
-!!! phraseology
-    <span class="coldline">**CS ACD** -> **CS TCU**</span>: "ABC, Requesting clearance for a Northbound VFR Coastal departure at A035"  
-    <span class="coldline">**CS TCU** -> **CS ACD**</span>: "ABC, Cleared for a Northbound VFR Coastal departure, A035"  
-    <span class="coldline">**CS ACD** -> **CS TCU**</span>: "Cleared for a Northbound VFR Coastal departure, A035, ABC"   
-    
-    **CS ACD**: "ABC, Cleared for a Northbound VFR Coastal departure, A035, Squawk 3601"  
-    **ABC**: "Cleared for a Northbound VFR Coastal departure, A035, 3601, ABC"  
+- VFR departures into CS TCU CTA  
+- Aircraft using a runway not on the ATIS 
 
 ### CS FLW
-FLW must advise ADC of any sequence changes within 36 Miles CS.  
-All requests for non-duty runway arrivals must be approved by ADC.
+FLW must advise ADC of any sequence changes within 36 Miles CS. All requests for non-duty runway arrivals must be approved by ADC.

docs/aerodromes/classc/Canberra.md

@@ -99,26 +99,20 @@ Helicopters arriving to the pads will generally be coordinated by the TMA contro
 
 ## Coordination
 ### Auto Release
-'Next' coordination is not required to CB TCU 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
+[Next](../../controller-skills/coordination.md#next) coordination is not required to CB TCU for aircraft that are:   
+  
+  - Departing from a runway nominated on the ATIS; and  
+  - Assigned the standard assignable level; and  
+  - Assigned a **Procedural** SID
 
 All other aircraft require a 'Next' call to CB TCU.
 
-!!! phraseology
-    <span class="hotline">**CB ADC** -> **CB TCU**</span>: "Next, XEB, runway 35"  
-    <span class="hotline">**CB TCU** -> **CB ADC**</span>: "XEB, heading 010, Unrestricted"  
-    <span class="hotline">**CB ADC** -> **CB TCU**</span>: "Heading 010, XEB"
-
-    **CB ADC**: "XEB, Assigned heading Right 010, Runway 35, Cleared for Takeoff"  
-    **XEB**: "Right heading 010, Runway 35, Cleared for Takeoff, XEB"
-
-The CB TCU controller can suspend/resume Auto Release at any time, with the concurrence of **CB ADC**.
-
 The Standard Assignable level from CB ADC to CB TCU is:  
-For IFR aircraft: `A100`  
-For VFR aircraft: The lower of `A040` or the `RFL`
+
+| Flight Rules | Level |
+| ------------ | ----- |
+| IFR | `A100` |
+| VFR | The lower of `A040` and `RFL` |
 
 ### Runway Change
 Any Runway change must be prior coordinated to **CB TCU**.

docs/aerodromes/classc/Curtin.md

@@ -25,17 +25,16 @@ CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`.
 
 ## Coordination
 ### CIN TCU
-'Next' coordination is required from CIN ADC to CIN TCU for all aircraft.
+[Next](../../controller-skills/coordination.md#next) coordination is required from CIN ADC to CIN TCU for all aircraft.
 
-!!! phraseology
-    <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 Standard Assignable Level from  **CIN ADC** to **CIN TCU** is the Lower of `F190` or the `RFL`.
+| Aircraft | Level |
+| -------- | ----- |
+| All | The lower of `F190` and `RFL` |
 
 ### TRT(ASH)
-When CIN TCU is offline, coordination is not required between CIN ADC and TRT(ASH). Aircraft entering TRT(ASH) airspace shall be handed off, and instructed to contact TRT(ASH) for onwards clearance.
+When CIN TCU is offline, coordination is not required between CIN ADC and TRT(ASH). Aircraft entering TRT(ASH) airspace shall be handed off and instructed to contact TRT(ASH) for onwards clearance.
 
 ## Charts
 !!! abstract "Reference"

docs/aerodromes/classc/Darwin.md

@@ -87,17 +87,16 @@ For non-RNAV approved IFR aircraft with a wake turbulence category of light, iss
 VFR aircraft that will operate only in ADCs airspace shall be assigned SSR code 0100  
 
 Circuit altitude will depend on the type of aircraft. Assign circuit altitudes for the following aircraft types:  
-a) MIL Jet: `A020`  
-b) Jet: `A015`  
-c) Non-jet: `A010`  
-d) Helo: `A010`  
 
-### VFR Departures
-VFR aircraft are required to track via one of the published VFR Routes.  
-
-VFR routes shall be assigned based on the destination radial from Darwin.  
+| Aircraft | Altitude |
+| ----- | ---- |
+| Military Jet | `A020` |
+| Other Jet | `A015` |
+| Non-Jet | `A010` |
+| Helicopter | `A010` | 
 
-Assign VFR routes in accordance with the following radial chart:  
+### VFR Departures
+VFR aircraft are required to track via one of the published VFR Routes (as shown on the Darwin VTC). VFR routes shall be assigned based on the destination radial from Darwin, as per below:  
 
 |Outbound Radial |Assigned VFR Route|
 |---|---|
@@ -109,19 +108,16 @@ Assign VFR routes in accordance with the following radial chart:
 |225 – 359| Direct|
 
 !!! tip
-    If a VFR aircraft has not planned via a VFR route as above, use the phraseology: “ABC, cleared amended route VFR route 1, maintain A020, squawk 4512”
+    If a VFR aircraft has not planned via a VFR route as above, use the phraseology: “*ABC, cleared amended route VFR route 1, climb to A020, squawk 4512*”
 
 ## Coordination
 ### DN TCU
-Auto-Release is **not available** at YPDN. All Departures will be coordinated when ready for departure.
-
-!!! phraseology
-    <span class="hotline">**DN ADC** -> **DN TCU**</span>: "Next, EOC, runway 18"  
-    <span class="hotline">**DN TCU** -> **DN ADC**</span>: "EOC, Track Extended Centreline, unrestricted"  
-    <span class="hotline">**DN ADC** -> **DN TCU**</span>: "Track Extended Centreline, EOC"  
+[Next](../../controller-skills/coordination.md#next) coordination is required from DN ADC to DN TCU for all aircraft.
 
-The Standard Assignable level from **DN ADC** to **DN TCU** is:
+The Standard Assignable Level from  **DN ADC** to **DN TCU** is:
 
-- For IFR aircraft assigned a Procedural SID: the lower of `F180` or the `RFL`.  
-- For IFR aircraft **not** assigned a Procedural SID: the lower of `A030` or the `RFL`.  
-- For VFR aircraft: the lower of `A020` or the `RFL`.
+| Aircraft | Level |
+| -------- | ----- |
+| IFR aircraft assigned a **Procedural** SID | The lower of `F180` and `RFL` |
+| IFR aircraft **not** assigned a **Procedural** SID | The lower of `A030` and `RFL` |
+| VFR aircraft | The lower of `A020` and `RFL` |