Merge pull request #284 from Augzer/melbournedarwin

YPDN IFR Level Assignment and YMML off mode Departure Changes.

docs/aerodromes/classc/Darwin.md

@@ -75,6 +75,10 @@ d) Helo: `A010`
 
 All departures from 18/36 require departure coordination with **DN TCU**
 
+### IFR Level Assignment
+The Standard Assignable level from **DN ADC** to **DN TCU** is the lower of `F180` or the `RFL`.  
+If the aircraft is **not** planned via an RNAV SID and has a light wake turbulance cateogry, they are to be assigned the lower of `A030` or the `RFL`.
+
 ### VFR Departures
 `A020` or the planned level; whichever is lower, to all VFR aircraft.  
 
@@ -113,7 +117,3 @@ Tower may depart aircraft that conform with the above conditions within the auto
 !!! tip
     Tower shall provide visual separation between aircraft in the auto-release wedge and subsequent departures until the preceding departure has been maneuvered by TCU
 
-### IFR Level Assignment
-Issue `F180` or `RFL`; whichever is lower, to aircraft cleared via an RNAV SID or aircraft with a wake turbulence category of medium or greater.  
-Issue `F180` or `RFL`; whichever is lower, to jet aircraft not cleared via an RNAV SID regardless of wake turbulence category.  
-Issue `A030` or `RFL`; whichever is lower, to aircraft not cleared via an RNAV SID with a wake turbulence category of light.  

docs/aerodromes/classc/Melbourne.md

@@ -49,6 +49,15 @@ During the 16A27D Runway Mode, some aircraft may operationally require Runway 16
 Aircraft departing Runway 16 and assigned the Standard Assignable Heading would conflict with departures from Runway 27, so the **ISPEG** SID must be used instead.
 
 Jet aircraft via **MNG**, **NONIX**, **DOSEL**, **KEPPA**, **NEVIS** or **ESDIG**, using Runway 16 for departure **Off Mode**, shall be assigned the **ISPEG** SID.
+Aircraft not planned via these waypoints should be assigned the sid that terminates on their first waypoint unless they are unable a procedural departure.
+
+<figure markdown>
+![ISPEG1 SID](img/ISPEG1SID.png){ width="700" }
+  <figcaption>Runway 16 and 27 departure conflicts visualised with the ISPEG1 SID</figcaption>
+</figure>
+
+!!! note
+    The ISPEG1 SID does not resolve all conflicts. Departures via SUNTI and CORRS need to be handled tactically by ML TCU.
 
 !!! definition
     **Off Mode:** Aircraft departing from a runway not prescribed as active for departures on the ATIS. For example, a heavy aircraft that operationally requires Runway 16 for departure during the 16A/27D Mode.

docs/terminal/darwin.md

@@ -122,6 +122,10 @@ DN ADC owns the airspace within the DN CTR `SFC`–`A010`.
 
 All departures from 18/36 require departure coordination with **DN TCU**
 
+#### IFR Departures
+The Standard Assignable level from **DN ADC** to **DN TCU** is the lower of `F180` or the `RFL`.  
+If the aircraft is **not** planned via an RNAV SID and has a light wake turbulance cateogry, they are to be assigned the lower of `A030` or the `RFL`.
+
 #### VFR Departures
 `A020` or the planned level; whichever is lower, to all VFR aircraft.  
 
@@ -159,13 +163,7 @@ Tower may depart aircraft that conform with the above conditions within the auto
 
 !!! tip
     Tower shall provide visual separation between aircraft in the auto-release wedge and subsequent departures until the preceding departure has been maneuvered by TCU
-
-#### IFR Level Assignment
-Issue `F180` or `RFL`; whichever is lower, to aircraft cleared via an RNAV SID or aircraft with a wake turbulence category of medium or greater.  
-Issue `F180` or `RFL`; whichever is lower, to jet aircraft not cleared via an RNAV SID regardless of wake turbulence category.  
-Issue `A030` or `RFL`; whichever is lower, to aircraft not cleared via an RNAV SID with a wake turbulence category of light.  
-
-
+
 ### DN TCU Internal
 Heads-up coordination is not required between DAW and DAE for: