vatpac-technology · chrisg06 · Apr 6, 2024 · Apr 5, 2024 · Apr 5, 2024 · Apr 6, 2024
diff --git a/docs/aerodromes/classc/Essendon.md b/docs/aerodromes/classc/Essendon.md
@@ -12,19 +12,17 @@
 | Essendon ATIS     |                  | 119.800         | YMEN_ATIS                                |
 
 ## Airspace
-EN ADC is responsible for the Class C airspace in the "Coffin" `SFC` to `A015`, and in the "South East Quadrant" `SFC` to `A020`.
+EN ADC is responsible for the Class C airspace shown below, `SFC` to `A020`.
 
 <figure markdown>
-![EN ADC Airspace](img/ENTWR.png){ width="500" }
-</figure>
-
-<figure markdown>
-![EN ADC ML Airspace](img/MLTCUairspace.png){ width="500" }
+![EN ADC Airspace](img/enadc.png){ width="700" }
 </figure>
 
 ## Runway Selection
 Consideration of the Melbourne duty runway(s) should be made when nominating runways. The effect of Melbourne traffic on a runway selection takes priority over compliance with DAP Noise Abatement Procedures.
 
+The 26A17D runway mode is most optimal for facilitating separation with YMML traffic.
+
 ## Departures
 IFR flights shall be cleared via:  
     a) When cloud base and visibility exceeds `A020` and 5 KM, visual departure;  
@@ -75,16 +73,16 @@ VFR arrivals from Class G shall be cleared (at not above `A015`) via:
 Circuits are to be flown at `A015`
 
 ## Separation
+EN ADC is responsible for **all separation** with YMML Traffic, including arrivals to RWY34 via the MONTY-SHEED track, and all potential arrivals, departures, and missed approach paths.  
+Some important points to note are that:  
+- Aircraft operating on or south of the 08/26 Centreline are separated with YMML 09/27 Traffic at all times  
+- Aircraft operating on or east of the 17/35 Centreline are **only** visually separated with YMML 16/34 Traffic in **Day VMC**  
+- Aircraft conducting the ILS 26 Published Missed Approach are **only** visually separated with YMML 16/34 Traffic in **Day VMC**
 
-### Separation with SHEED Track
-By day only, ML TCU may require EN ADC to separate aircraft from the MONTY – SHEED track for RWY 34 ML during the Next call. EN ADC shall separate by restricting the departure to `A015` until clear of the MONTY – SHEED track.
+EN ADC must assume that **any runway** at YMML may be used for arrival, departure, or a missed approach, **at any time**.  
+When the cloud base is below **A020**, or the Visibility is below **5000m**, all aircraft operating within **3nm** of the 09/27 or 16/34 extended centreline must be [boundary coordinated](../../../controller-skills/coordination/#boundary) to ML ADC, as prescribed in [Coordination](#ml-adc)
 
-### Additional EN ADC separation requirements
-EN TWR shall separate traffic in EN airspace with:  
-a) ML RWY 27 Arrivals and ML RWY 09 Departures on or north of ML RWY 09 / 27 centreline;  
-b) ML RWY 34 arrivals and ML RWY 16 Departures on or west of ML RWY 16 / 34 centreline;  
-c) ML RWY 34 arrivals from overhead EN;  
-d) EN arrivals from ML TCU inbound via Arrival Gates or as coordinated.  
+If ML ADC nominates a restriction, and EN ADC determines they **cannot** maintain visual or lateral separation with the YMML traffic, EN ADC must delay the aircraft in their airspace until the separation can be assured. 
 
 ## Miscellaneous
 Traffic in EN ADC airspace shall squawk 0100 unless a discrete code is required.
@@ -95,7 +93,7 @@ EN ADC is responsible for facilitating aircraft requesting city orbits. They sha
 `A022` by night
 
 !!! example
-    **EOG**: "Essendon Tower, EOG, approaching Williamstown, A015, Requesting 1 left-hand city orbit, in receipt of L"  
+    **EOG**: "Essendon Tower, EOG, approaching WMS, A015, Requesting 1 left-hand city orbit, in receipt of L"  
     **EN ADC**: "EOG, Essendon Tower, cleared 1 left-hand city orbit A015"  
     **EOG**: "Cleared 1 left-hand city orbit A015, EOG"  
     *When orbit is complete and aircraft is leaving CTA laterally:*  
@@ -140,6 +138,9 @@ When “The Coffin” is released, ML TCU is required to coordinate any use of R
 Any Runway change must be prior coordinated to **ML TCU**
 
 ### ML ADC
-EN ADC must advise ML ADC when “The Coffin” is activated or deactivated.
+EN ADC is responsible for separation with all YMML traffic, and must coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with the 09/27 or 16/34 Extended Centrelines at YMML.
 
-EN ADC must advise ML ADC, for traffic awareness, when an ad hoc airspace release to EN ADC will cause an aircraft to pass within 3 NM of any runway at ML.
+!!! example 
+    <span class="hotline">**EN ADC** -> **ML ADC**</span>: "Boundary Ident, OXG, Published Missed Approach from the ILS 26"  
+    <span class="hotline">**ML ADC** -> **EN ADC**</span>: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation"  
+    <span class="hotline">**EN ADC** -> **ML ADC**</span>: "My separation with QFA451, OXG"
diff --git a/docs/aerodromes/classc/Melbourne.md b/docs/aerodromes/classc/Melbourne.md
@@ -23,35 +23,6 @@ Except when the traffic situation warrants, taxi clearances shall conform to the
 ## Airspace
 ML ADC is not responsible for any airspace by default.
 
-### Sunbury Corridor
-**ML ADC** may request a release of the Sunbury Corridor from ML TCU, to facilitate movements of Day VFR Helicopters.
-
-<figure markdown>
-![Melbourne TCU Airspace Administration](img/MLTCUairspace.png){ width="500" }
-  <figcaption>Melbourne TCU Airspace Administration</figcaption>
-</figure>
-
-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
-    **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:** "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.
-
-!!! example
-    **ML ADC:** "JST515, traffic is a helicopter, 2nm northwest of the field, tracking for Essendon and maintaining own separation with you, runway 16, cleared to land"  
-    **JST515:** "Runway 16, cleared to land, JST515"
-
 ## Runway Modes
 If winds are too great, single runway operations may be necessary (eg, Runway 16 for Arrivals and Departures). However, pending wind limitations (Crosswind <20kts, Tailwind <5kts), the following runway modes are to be used
 
@@ -125,6 +96,42 @@ Whilst this is used to reduce frequency congestion on SMC in the real world, coo
 
 In light of this, the use of this operational info should be avoided.
 
+## Miscellaneous
+### Sunbury Corridor
+Day VFR Helicopters may request clearance via the **Sunbury Corridor**. It is defined as the corridor 1nm either side of a track from SWT - PWLC - 16/27 Intersection at YMML.
+
+<figure markdown>
+![Sunbury Corridor](img/sunburycorridor.png){ width="700" }
+  <figcaption>Sunbury Corridor</figcaption>
+</figure>
+
+Boundary Coordination must be completed to ML TCU for clearances in this airspace
+
+!!! example
+    <span class="hotline">**ML ADC** -> **ML TCU**</span>: "For Ident, HM3, Sunbury Corridor, not above A020"  
+    <span class="hotline">**ML TCU** -> **ML ADC**</span>: "HM3, No Restrictions"  
+
+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
+    **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:** "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.
+
+!!! example
+    **ML ADC:** "JST515, traffic is a helicopter, 2nm northwest of the field, tracking for Essendon and maintaining own separation with you, runway 16, cleared to land"  
+    **JST515:** "Runway 16, cleared to land, JST515"
+
 ## Coordination
 ### Auto Release
 !!! important
@@ -171,4 +178,12 @@ 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.
+Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online.
+
+### 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.
+
+!!! example 
+    <span class="hotline">**EN ADC** -> **ML ADC**</span>: "Boundary Ident, OXG, Published Missed Approach from the ILS 26"  
+    <span class="hotline">**ML ADC** -> **EN ADC**</span>: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation"  
+    <span class="hotline">**EN ADC** -> **ML ADC**</span>: "My separation with QFA451, OXG"
diff --git a/docs/aerodromes/classc/img/enadc.png b/docs/aerodromes/classc/img/enadc.png
diff --git a/docs/aerodromes/classc/img/sunburycorridor.png b/docs/aerodromes/classc/img/sunburycorridor.png
diff --git a/docs/controller-skills/milkrun.md b/docs/controller-skills/milkrun.md
@@ -12,7 +12,7 @@ The job of the ACD controller during Milk Run is a fairly straight-forward one,
 Ensure that all flight plans are correct, nothing like `DOSEL DCT RIVET`, `GPS DIRECT`, or anything else unusual like that, just stick to the pre-approved Jet and Non-Jet routes. This helps reduce workload on Enroute controllers down the line.
 
 ### 16 Off Mode Departures at YMML
-A Reminder that [Off Mode Departures from Runway 16](../../aerodromes/classc/Melbourne/#off-mode-departures) during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not.
+A Reminder that [Off Mode Departures from Runway 16](../../aerodromes/classc/Melbourne/#off-mode-departures) to the North East and North West during the 16A27D Runway Mode must be assigned the **ISPEG** SID, **NOT** the DOSEL SID. The **ISPEG** SID deconflicts concurrent 16 and 27 departures, whereas the DOSEL SID does not.
 
 ## SMC
 ### Standard Taxi Routes

diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md
@@ -34,6 +34,30 @@ See also: [CG ADC Offline](#cg-adc-offline).
 ### Airspace Structural Arrangements
 Pursuant to Section 3 of the [VATPAC Air Traffic Services Policy](https://cdn.vatpac.org/documents/policy/Controller+Positions+and+Ratings+Policy+v5.2.pdf), **“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.
 
+### Airspace Division
+The divisions of the airspace between **BAN**, **BAS**, **BDS**, **BDN**, and **BAC** change based on the Runway Mode.
+
+!!! note
+    The following diagrams do not include non BN TCU areas of responsibility such as AF CTR or CG ADC
+
+#### 01 PROPS
+<figure markdown>
+![01 PROPS TCU Structure](img/bn01props.png){ width="700" }
+  <figcaption>01 PROPS TCU Structure</figcaption>
+</figure>
+
+#### 19 PROPS
+<figure markdown>
+![19 PROPS TCU Structure](img/bn19props.png){ width="700" }
+  <figcaption>19 PROPS TCU Structure</figcaption>
+</figure>
+
+#### SODPROPS
+<figure markdown>
+![SODPROPS TCU Structure](img/bnsodprops.png){ width="700" }
+  <figcaption>SODPROPS TCU Structure</figcaption>
+</figure>
+
 ## Parallel Runway Operations
 Refer to [Parallel Runway Separation Standards](../../separation-standards/parallelapps) for more information
 ### Runway Selection
@@ -80,30 +104,6 @@ Due to the low level of CTA (`A035`) in the CG CTR when **CG ADC** is offline, i
     **BN TCU**: "JST446, Cleared to YSSY via APAGI, Flight Planned Route. Climb to A060"  
     **JST446**: "Cleared to YSSY via APAGI, Flight Planned Route. Climb to A060, JST446"
 
-## Airspace Division
-The divisions of the airspace between **BAN**, **BAS**, **BDS**, **BDN**, and **BAC** change based on the Runway Mode.
-
-!!! note
-    The following diagrams do not include non BN TCU areas of responsibility such as AF CTR or CG ADC
-
-### 01 PROPS
-<figure markdown>
-![01 PROPS TCU Structure](img/bn01props.png){ width="700" }
-  <figcaption>01 PROPS TCU Structure</figcaption>
-</figure>
-
-### 19 PROPS
-<figure markdown>
-![19 PROPS TCU Structure](img/bn19props.png){ width="700" }
-  <figcaption>19 PROPS TCU Structure</figcaption>
-</figure>
-
-### SODPROPS
-<figure markdown>
-![SODPROPS TCU Structure](img/bnsodprops.png){ width="700" }
-  <figcaption>SODPROPS TCU Structure</figcaption>
-</figure>
-
 ## Coordination
 ### Enroute
 #### Departures

diff --git a/docs/terminal/coral.md b/docs/terminal/coral.md
@@ -24,6 +24,7 @@ MKA may extend to RKA and vice versa, callsigns remain the same. See [Controller
     <figure markdown>
     ![Coral Combined Airspace](img/coraltcusetup.png){ width="1000" }
     </figure>
+
 ## Coordination
 
 ### Enroute

diff --git a/docs/terminal/darwin.md b/docs/terminal/darwin.md
@@ -21,6 +21,7 @@ DN TCU is also responsible for Active Restricted Area R264 A-K and R230 A-F
 
 DAW may request DN TCU (`SFC`–`F240`) from TRT to facilitate military transits to/from R264 A-K and R230 A-F  
 
+### Airspace Division
 When both DN TCU positions are opened, DN TCU is split east and west along the runway 18/36 extended centreline. DAW owns the airspace to the west of the line and DAE owns the airspace to the east of the line  
 
 <figure markdown>
@@ -29,7 +30,6 @@ When both DN TCU positions are opened, DN TCU is split east and west along the r
 </figure>
 
 ### ADC
-
 ADC owns the airspace within the DN CTR (`SFC`–`A010`). This airspace is designed to facilitate the processing of helicopter scenic flights and low-level helicopter circuits.  
 The CTR extends 7NM from the thresholds of runways 11 and 29 but does not including the Robertson Barracks transit zone.  
 

diff --git a/docs/terminal/img/16PROPS.png b/docs/terminal/img/16PROPS.png
diff --git a/docs/terminal/img/enadc.png b/docs/terminal/img/enadc.png
diff --git a/docs/terminal/melbourne.md b/docs/terminal/melbourne.md
@@ -17,18 +17,6 @@
 
 ## Airspace
 The Vertical limits of the ML TCU are `SFC` to `F245`.  
-ML TCU is responsible for the Melbourne TCU, except:    
-a) The Sunbury Corridor, when **ML ADC** is online  
-b) The South East Quadrant, when **EN ADC** is online  
-c) The Coffin, when **EN ADC** is online, and the airspace has been released to **EN ADC**  
-
-<figure markdown>
-![Melbourne TCU Airspace Administration](img/MLTCUairspace.png){ width="500" }
-  <figcaption>Melbourne TCU Airspace Administration</figcaption>
-</figure>
-
-!!! note
-    The released airspace of the Sunbury Corridor and South East Quadrant is only from the lower level of CTA. ML TCU still owns the Class G airspace beneath it.
 
 ### Reclassifications
 #### MB CTR
@@ -41,6 +29,42 @@ AV CTR Class D `SFC` to `A007` reverts to Class G and `A007` to `A025` to Class
 
 See also: [AV ADC Offline](#av-adc-offline).
 
+### Airspace Division
+The divisions of the airspace between **MAE**, **MDN**, and **MDS** change based on the Runway Mode.
+
+!!! note
+    The following diagrams do not include non ML TCU areas of responsibility such as MB CTR or AV ADC
+
+#### 09
+<figure markdown>
+![09 TCU Structure](img/ML09annotated.png){ width="700" }
+  <figcaption>09 TCU Structure</figcaption>
+</figure>
+
+#### 09A16D
+<figure markdown>
+![09A16D TCU Structure](img/ML09A16Dannotated.png){ width="700" }
+  <figcaption>09A16D TCU Structure</figcaption>
+</figure>
+
+#### 16 / 16A27D
+<figure markdown>
+![16 / 16A27D TCU Structure](img/ML16annotated.png){ width="700" }
+  <figcaption>16 / 16A27D TCU Structure</figcaption>
+</figure>
+
+#### 27 / 27AD34D
+<figure markdown>
+![27 / 27AD34D TCU Structure](img/ML27annotated.png){ width="700" }
+  <figcaption>27 / 27AD34D TCU Structure</figcaption>
+</figure>
+
+#### 34
+<figure markdown>
+![34 TCU Structure](img/ML34annotated.png){ width="700" }
+  <figcaption>34 TCU Structure</figcaption>
+</figure>
+
 ## Departure Procedures
 ### ML (RADAR) SID
 The **ML (RADAR) SID** is used for all non-jet IFR departures (and certain jet aircraft) from YMML.  Unlike at other aerodromes, **ML ADC** does *not* need to coordinate these departures with a 'Next' call, provided they are assigned the standard assignable level and a [Standard Assignable Heading](#standard-assignable-headings).
@@ -158,42 +182,6 @@ Due to the low level of CTA surrounding YMMB, it is best practice to give airway
     **ML TCU:** "AAC, cleared to YBLT via SAMIG, flight planned route, climb to A040"  
     **AAC:** "Cleared to YBLT via SAMIG, flight planned route, climb to A040, AAC"
 
-## Airspace Division
-The divisions of the airspace between **MAE**, **MDN**, and **MDS** change based on the Runway Mode.
-
-!!! note
-    The following diagrams do not include non ML TCU areas of responsibility such as MB CTR or AV ADC
-
-### 09
-<figure markdown>
-![09 TCU Structure](img/ML09annotated.png){ width="700" }
-  <figcaption>09 TCU Structure</figcaption>
-</figure>
-
-### 09A16D
-<figure markdown>
-![09A16D TCU Structure](img/ML09A16Dannotated.png){ width="700" }
-  <figcaption>09A16D TCU Structure</figcaption>
-</figure>
-
-### 16 / 16A27D
-<figure markdown>
-![16 / 16A27D TCU Structure](img/ML16annotated.png){ width="700" }
-  <figcaption>16 / 16A27D TCU Structure</figcaption>
-</figure>
-
-### 27 / 27AD34D
-<figure markdown>
-![27 / 27AD34D TCU Structure](img/ML27annotated.png){ width="700" }
-  <figcaption>27 / 27AD34D TCU Structure</figcaption>
-</figure>
-
-### 34
-<figure markdown>
-![34 TCU Structure](img/ML34annotated.png){ width="700" }
-  <figcaption>34 TCU Structure</figcaption>
-</figure>
-
 ## Coordination
 
 ### Enroute
@@ -242,7 +230,12 @@ The following Standard Assignable Headings may be used for aircraft assigned the
 
 ### EN ADC
 #### Airspace
-EN ADC is responsible for the Class C airspace in the "Coffin" `SFC` to `A015`, and in the "South East Quadrant" `SFC` to `A020`.
+EN ADC is responsible for the Class C airspace shown below, `SFC` to `A020`.
+
+<figure markdown>
+![EN ADC Airspace](img/enadc.png){ width="700" }
+  <figcaption>EN ADC Airspace</figcaption>
+</figure>
 
 #### Start Clearance
 When an aircraft requests start clearance, the EN SMC controller shall coordinate with ML TCU to obtain the start clearance.