vatpac-technology · tylerthetiletiler · May 2, 2024 · May 2, 2024 · May 2, 2024 · May 2, 2024
@@ -131,11 +131,11 @@ The ATIS shall always have `EXP INST APCH` as the approach type. Visual Approach
 ## Coordination
 ### Auto Release
 'Next' coordination is **not** required to BN TCU for aircraft that are:   
-  a) Departing from a runway nominated on the ATIS (except during SODPROPS*); and  
+  a) Departing from a runway nominated on the ATIS (except during SODPROPS^); and  
   b) Assigned the standard assignable level; and  
   c) Assigned a **Procedural** SID  
 
-*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.
 

@@ -48,7 +48,7 @@ Jet Aircraft planned via **MNG**, **NONIX**, **DOSEL**, **CORRS**, **KEPPA**, **
 During the 16A27D Runway Mode, some aircraft may operationally require Runway 16 for departure.  
 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 planned via **MNG**, **NONIX**, **DOSEL**, **KEPPA**, or **NEVIS**, using Runway 16 for departure **Off Mode**, shall be assigned the **ISPEG** SID.
+Jet aircraft via **MNG**, **NONIX**, **DOSEL**, **KEPPA**, **NEVIS** or **ESDIG**, using Runway 16 for departure **Off Mode**, shall be assigned the **ISPEG** SID.
 
 !!! 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.
@@ -137,12 +137,19 @@ Remember to pass traffic information to both aircraft.
 !!! 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:   
-    a) Departing from a runway nominated on the ATIS; and  
-    b) Assigned `A050`; and  
-    c) Assigned a **Procedural** SID; or  
-    d) Assigned the **ISPEG** SID for **Off Mode** Runway 16 departures; or  
-    e) Assigned the **ML (RADAR) SID** and a [Standard Assignable Heading](#standard-assignable-departure-headings)
+'Next' coordination is **not** required for aircraft that are:  
+
+- Assigned a **Procedural** SID  
+    - Departing from a runway nominated on the ATIS; and  
+    - Assigned `A050`  
+- Assigned the **ML (RADAR)** SID  
+    - Departing from a runway nominated on the ATIS; and  
+    - Assigned `A050`; and  
+    - Assigned a [Standard Assignable Heading](#standard-assignable-departure-headings)  
+- Assigned the **ISPEG** SID  
+    - Departing from Runway 16 during the 16A27D Runway Mode; and  
+    - Assigned `A050`; and  
+    - Tracking via **MNG**, **NONIX**, **DOSEL**, **KEPPA**, **NEVIS** or **ESDIG**
 
 All other aircraft require a 'Next' call to ML TCU.
 

@@ -66,7 +66,7 @@ VFR aircraft will not be coordinated, and will need to receive their airways cle
     Remember that IFR aircraft are only separated from other IFR or SVFR aircraft in class D. You should *generally* be able to issue a clearance for an approach and use other separation methods (visual separation, holding a departure on the ground) if separation is required with these aircraft.
 
 #### Runway Change
-Any Runway change must be prior coordinated to the relevant [TCU Controller](#TCU-Controller).
+Any Runway change must be prior coordinated to the relevant [TCU Controller](#tcu-controller).
 
 #### TCU Controller
 When **MDN** and/or **MDS** are online, the relevant TCU controller is whoever is responsible for **MDS**.

@@ -4,6 +4,9 @@ title: Airwork / Special Operations
 
 --8<-- "includes/abbreviations.md"
 
+<details open markdown="1">
+<summary>Airwork</summary>
+
 ## Airwork
 Airwork is essentially defined as an aerial operation that doesn't involve simply going from A to B. They can complicate things from an air traffic control perspective, because it's not necessarily as clear exactly what the aircraft is about to do just from looking at their label. In order to facilitate separation and the orderly flow of traffic whilst Airwork is taking place, there are a few procedures to follow.
 
@@ -16,6 +19,8 @@ Airwork can be conducted in any defined area specified by the pilot or ATC. This
     **KIY**: "PPB, No Reported IFR Traffic"  
     **PPB**: "PPB"
 
+</details>
+
 <details markdown="1">
 <summary>Remarks</summary>
 

@@ -177,6 +177,7 @@ If due to weather, overflying aircraft, runway config changes, etc. Auto Release
 **Voiceless** for aircraft landing at main airport (eg YMML in ML TCU), assigned a STAR, and standard assignable level.  
 
 Heads-up coordinate all other aircraft by **20nm** to boundary.
+
 ### TCU -> ENR
 **Voiceless** for aircraft assigned lower of standard assignable level or RFL, and tracking via a Procedural SID terminus.
 

@@ -4,8 +4,13 @@ title: Milk Run Monday
 
 --8<-- "includes/abbreviations.md"
 
+<details open markdown="1">
+<summary>Milk Run</summary>
+
 Milk Run Monday is a very busy event, that tests the limits of controllers at it's busiest. It is important to understand some processes that makes the event run as smooth as possible for all pilot and controllers involved. The information on this page is extracted from various Local Instructions and Controller Skills pages, collated to give all of the most relevant information to controlling the Milk Run event.
 
+</details>
+
 <details markdown="1">
 <summary>ACD</summary>
 
@@ -15,7 +20,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) 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.
+A Reminder that [Off Mode Departures from Runway 16](../../aerodromes/classc/Melbourne/#off-mode-departures) to the North East and 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.
 
 </details>
 

@@ -4,7 +4,12 @@ title: vatSys Setup
 
 --8<-- "includes/abbreviations.md"
 
-Although much of the detailed setup is up to personal preference, the following setttings are **strongly** recommended to help best execute the appropriate role.
+<details open markdown="1">
+<summary>Setup</summary>
+
+Although much of the detailed setup is up to personal preference, the following settings are **strongly** recommended to help best execute the appropriate role.
+
+</details>
 
 <details markdown="1">
 <summary>Enroute</summary>

@@ -114,17 +114,25 @@ Aircraft being transferred from the following sectors shall be given STAR Cleara
 #### Airspace
 SY TCU is responsible for the airspace within a 45nm radius of TESAT, `SFC` to `F285`.
 
-Refer to [Sydney TCU Airspace Division](../../terminal/sydney/#airspace-division) for information on airspace divisions when **SAS**, **SDN**, **SDS** and/or **SRI** are online.
+Refer to [Sydney TCU Airspace Division](../../../terminal/sydney/#airspace-division) for information on airspace divisions when **SAS**, **SDN**, **SDS** and/or **SRI** are online.
 
 #### Arrivals/Overfliers
-The Standard Assignable level from ARL(All) to SY TCU is:  
-`A100` for aircraft tracking via BOREE or MARLN, and assigned the relevant STAR  
-`A090` for aircraft tracking via MEPIL, and assigned the MEPIL STAR  
+Voiceless for all aircraft:
 
-All other aircraft must be voice coordinated to SY TCU prior to **20nm** from the boundary.
+- With ADES **YSSY**; and  
+- Assigned a STAR; and  
+- Tracking via **MARLN** or **BOREE**, assigned `A100`; or  
+- Tracking via **MEPIL**, assigned `A090`
+
+All other aircraft coming from ARL CTA must be **Heads-up** Coordinated to SY TCU prior to **20nm** from the boundary.
 
 #### Departures
-The Standard Assignable level from SY TCU to ARL(All) is the lower of `F280` or the `RFL`, and tracking via a SID terminus.
+Voiceless for all aircraft:
+
+- Tracking via a Procedural SID terminus; and  
+- Assigned the lower of `F280` or the `RFL`
+
+All other aircraft going to ARL CTA will be **Heads-up** Coordinated by SY TCU.
 
 ### Enroute
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
@@ -133,6 +141,7 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
 
 That being said, due to their small sizes and frequent random-track traffic, it is *advised* that ARL(All) gives **Heads-up Coordination** in the following scenarios:   
+
 - MNN to ARL for all aircraft  
 - ARL to MNN for all aircraft  
 - CNK to MLD for all aircraft  
@@ -142,6 +151,8 @@ That being said, due to their small sizes and frequent random-track traffic, it
 #### Airspace
 TW ADC is responsible for the Class D airspace in the TW CTR `SFC` to `A045`, as well as the Class C airspace between `A045` and `A065`.
 
+Refer to [Reclassifications](#tw-ctr) for operations when TW ADC is offline.
+
 #### Departures
 Departures from YSTW in to ARL/MDE Class C will be coordinated when ready for departure.
 
@@ -165,6 +176,8 @@ The Standard Assignable level from ARL/MDE to **TW ADC** is `A080`, any other le
 #### Airspace
 CFS ADC is responsible for the Class D airspace in the CFS CTR `SFC` to `A045`.
 
+Refer to [Reclassifications](#cfs-ctr) for operations when CFS ADC is offline.
+
 #### Departures
 Departures from YCFS in to MNN Class C will be coordinated when ready for departure.
 
@@ -188,17 +201,28 @@ The Standard Assignable level from MNN to **CFS ADC** is `A080`, any other level
 #### Airspace
 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.
 
-Refer to [Airspace](#airspace) for operations when WLM TCU is offline.
+Refer to [Reclassifications](#wlm-ctr) for operations when WLM TCU is offline.
 
 #### Departures
-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.
+Voiceless for all aircraft:
+
+- Tracking via a Procedural SID terminus; and  
+- Assigned the lower of `F120` or the `RFL`
+
+All other aircraft going to ARL CTA will be **Heads-up** Coordinated by WLM TCU.
 
 !!! example
     <span class="hotline">**WLM TCU** -> **MLD**</span>: "QJE1597, request DCT OMGAB"  
     <span class="hotline">**MLD** -> **WLM TCU**</span>: "QJE1597, concur DCT OMGAB"  
 
 #### 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.
+Voiceless for all aircraft:
+
+- With ADES **YWLM**; and  
+- Assigned a STAR; and  
+- Assigned `A090`
+
+All other aircraft coming from ARL CTA must be **Heads-up** Coordinated to WLM TCU prior to **20nm** from the boundary.
 
 !!! example
     <span class="hotline">**CNK** -> **WLM TCU**</span>: "QFA1968, request DCT UPTEB"  

@@ -38,7 +38,7 @@ When **CFS ADC** is offline, CFS CTR (Class D `SFC` to `A045`) reverts to Class
 Due to the low ceiling of CTA, when CFS ADC is offline, INL shall instruct aircraft departing into CTA to report lined up on the runway and issue an airways clearance (traffic pending) at that time.
 
 #### RK CTR
-Whilst the **RKA** controller is expected to provide a [top-down service](../../../aerodromes/Rockhampton) to YBRK when **RK ADC** is offline, this is not expected of a GOL controller when both **RKA** and **RK ADC** are offline. If electing not to provide a top-down service to YBRK, the RK CTR Class D is reclassified to Class G `SFC` to `A007`, and Class E `A007` to `A045`.
+Whilst the **RKA** controller is expected to provide a [top-down service](../../../aerodromes/Rockhampton) to YBRK when **RK ADC** is offline, this is not expected of a KPL controller when both **RKA** and **RK ADC** are offline. If electing not to provide a top-down service to YBRK, the RK CTR Class D is reclassified to Class G `SFC` to `A007`, and Class E `A007` to `A045`.
 
 ## Sector Responsibilities
 
@@ -55,6 +55,14 @@ NSA is responsible for facilitating YBSU traffic, including operating the Class
 ### Keppel (KPL)
 KPL is responsible for issuing STAR Clearances (Jets only) and initial descent for aircraft bound for YBSU, YBBN and YBCG.
 
+### Sequencing in to YBBN
+Aircraft assigned the **same runway** inbound via:  
+
+- BLAKA and GOMOL  
+- SMOKA and MORBI
+
+Must be considered to be on the **same STAR** for sequencing purposes. That is, they must be at least **2 minutes **apart at their respective Feeder fixes.
+
 ## STAR Clearance Expectation
 ### Handoff
 Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff:
@@ -80,33 +88,77 @@ Aircraft being transferred from the following sectors shall be given STAR Cleara
 | INL | GOL | YBSU | |
 | NSA | KPL | YBRK, YBMK | |
 
+## STAR Assignment
+### PROPS
+When operating a PROPS Runway Mode, Aircraft shall be assigned the appropriate 'ALPHA' STAR (or other STAR on pilot request), with the following runway selection:
+
+| FF | Runway |
+| ---- | -------- |
+| BLAKA | 01R/19L |
+| GOMOL | 01R/19L |
+| UGTUG | 01R/**19R** |
+| TEBOT | 01R/**19R** |
+| MORBI | 01L/19R |
+| SMOKA | 01L/19R |
+| WOODY | 01L/19R |
+| ENLIP | 01L/**19L** |
+| Other aircraft: |
+| From the NORTH and WEST | 01L/19R |
+| From the SOUTH and EAST | 01R/19L |
+
+These standard runway assignments may be modified strategically by the BAS or BFL controller.
+
+!!! example
+    If during an event, the vast majority of traffic is coming from **BLAKA** and **GOMOL** feeder fixes, BAS/BFL may elect to assign 19L to **BLAKA** arrivals and 19R to **GOMOL** arrivals, to keep them strategically spearated in the TCU.
+
+    <span class="hotline">**BFL** -> **INL**</span>: "All arrivals via GOMOL to be assigned 19R until further notice"  
+    <span class="hotline">**INL** -> **BFL**</span>: "Roger, Arrivals via GOMOL to be assigned 19R" 
+
+### SODPROPS
+When operating the SODPROPS Runway Mode, aircraft via **ENLIP**, **BLAKA**, **GOMOL** and **UGTUG**, shall be assigned the **ISPON** STAR with the appropriate transition. Aircraft via other Feeder fixes may be assigned the standard STAR.
+
 ## Coordination
 ### BN TCU
 #### Airspace
 The Vertical limits of the BN TCU are `SFC` to `F180`, except in BAC airspace, where it is `SFC` to `A075` in the North West, and `SFC` to `F125` in the South East.
 
-Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/operations/#airspace-division) for information on airspace divisions when **BAS**, **BDN** and/or **BDS** are online.
+Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BAS**, **BDN** and/or **BDS** are online.
 
 #### Arrivals/Overfliers
-The Standard assignable level from INL(All) to BN TCU is:  
-`A090` for YBBN arrivals, and assigned a STAR  
-`F130` for YBCG arrivals via BERNI, and assigned a STAR  
+Voiceless for all aircraft:
+
+- With ADES **YBBN** or **YBCG**; and  
+- Assigned a STAR; and  
+- Assigned `A090` for **YBBN** arrivals; or  
+- Assigned `F130` for **YBCG** arrivals
 
-All other aircraft must be voice coordinated to BN TCU prior to **20nm** from the boundary.
+Additionally, Voiceless coordination may be used for **YBCG** arrivals tracking via **BN** and assigned `F190`.
+
+All other aircraft coming from INL CTA must be **Heads-up** Coordinated to BN TCU prior to **20nm** from the boundary.
 
 #### Departures
-The Standard Assignable level for YBBN departures from BN TCU to **INL(All)** is the lower of `F180` or the `RFL`.  
-The Standard Assignable level for YBCG departures from BN TCU to **GOL/SDY** is the lower of `F120` or the `RFL`, and tracking via APAGI.  
-The Standard Assignable level for YBCG departures from BN TCU to **NSA/BUR/DOS** is the lower of `F180` or the `RFL`.  
-The Standard Assignable level for YBSU arrivals from BN TCU to **NSA** is `F130`, and tracking via ITIDE.  
+Voiceless for aircraft:
+
+- With ADEP **YBBN**  
+    - Tracking via a Procedural SID terminus; and  
+    - Assigned the lower of `F180` or the `RFL`  
+- With ADEP **YBCG**  
+    - Tracking via **APAGI** and assigned the lower of `F120` or the `RFL`; or  
+    - Tracking via **BN** and assigned the lower of `F180` or the `RFL`  
+- With ADES **YBSU**  
+    - Assigned the **ITIDE** STAR; and  
+    - Assigned `F130`
+
+All other aircraft going to INL CTA will be **Heads-up** Coordinated by BN TCU.
 
 ### Enroute
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
 
 ### INL Internal
 As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **20nm** to boundary.
 
-That being said, it is *advised* that INL(All) give **Heads-up Coordination** to the relevant sector prior to **20nm** from the boundary in the following scenarios:  
+That being said, it is *advised* that INL(All) give **Heads-up Coordination** to the relevant sector prior to **20nm** from the boundary in the following scenarios:
+
 - INL to DOS for all aircraft  
 - DOS to BUR, NSA, GOL and INL for all aircraft  
 - SDY to NSA, GOL and INL for all aircraft  
@@ -115,6 +167,8 @@ That being said, it is *advised* that INL(All) give **Heads-up Coordination** to
 #### Airspace
 SU ADC is responsible for the Class D airspace in the SU CTR `SFC` to `A045`.
 
+Refer to [Reclassifications](#su-ctr) for operations when SU ADC is offline.
+
 #### Departures
 Departures from YBSU in to NSA Class C will be coordinated when ready for departure.
 
@@ -139,18 +193,31 @@ The Standard Assignable level from NSA to **SU ADC** is `A060`, any other level
 #### Airspace
 RKA is responsible for the airspace within the 'RK keyhole' `SFC` to `F150`.
 
+Refer to [Reclassifications](#rk-ctr) for operations when RKA is offline.
+
 #### Arrivals/Overfliers
-The Standard assignable level from KPL to **RKA** is `A070`, and assigned the ABVAS STAR or DADBO STAR.
+Voiceless for all aircraft:
 
-All other aircraft must be voice coordinated to **RKA** prior to **20nm** from the boundary.
+- With ADES **YBRK**; and  
+- Assigned the **ABVAS** or **DADBO** STAR; and  
+- Assigned `A070`
+
+All other aircraft coming from KPL CTA must be **Heads-up** Coordinated to RKA prior to **20nm** from the boundary.
 
 #### Departures
-The Standard Assignable level from **RKA** to KPL is `F150`, and tracking via BUDGI or TARES.
+Voiceless for all aircraft:
+
+- Tracking via **BUDGI** or **TARES**; and  
+- Assigned the lower of `F150` or the `RFL`
+
+All other aircraft going to KPL CTA will be **Heads-up** Coordinated by RKA.
 
 ### CFS ADC
 #### Airspace
 CFS ADC is responsible for the Class D airspace in the CFS CTR `SFC` to `A045`.
 
+Refer to [Reclassifications](#cfs-ctr) for operations when CFS ADC is offline.
+
 #### Departures
 Departures from YCFS in to INL Class C will be coordinated when ready for departure.