Merge pull request #313 from vatpac-technology/moorabbin

Coordinator Procedures Update & Metro D Clearance Clarification

docs/aerodromes/classc/Melbourne.md

@@ -138,13 +138,10 @@ During busy events, such as [Milk Run Monday](../../../controller-skills/milkrun
 ### Pushback Requests on ACD
 To mitigate this, pushback requests may be done on **ACD** frequency, to balance the workload. A few steps must be followed to properly execute this procedure.
 
+To commence the procedure:
+
 1. **SMC** and **ACD** coordinate to implement the procedure, due to high **SMC** workload.
 2. **SMC** coordinates with **ADC** in order to have the [ATIS](#acd-pushback-requests) updated.
-3. When **ACD** has finished issuing an airways clearance, they will **remind** pilots to *"Contact me when ready for pushback"*.
-4. When a pilot requests pushback, **ACD** will instruct them to **Monitor** *(not contact)* Ground on 121.7, and advise their position in the queue.
-5. **ACD** will move the strip in to the **Queue** section of the **Cleared** bay^ in [OzStrips](../../../client/towerstrips/), to denote they are awaiting pushback approval†.
-6. Eventually, **SMC** will have adequate space on the aprons, taxiways, and holding point, as well as time to make assessments.
-7. **SMC** will scan the [Cleared Queue bay](../../../client/towerstrips/#stripboard) for the next aircraft in line, and call them to approve their pushback.
 
 !!! example
     <span class="hotline">**ML SMC** -> **ML ACD**</span>: "It's getting quite busy. Happy to implement Pushback requests on your frequency?"  
@@ -154,31 +151,56 @@ To mitigate this, pushback requests may be done on **ACD** frequency, to balance
     <span class="hotline">**ML SMC** -> **ML ADC**</span>: "Can we please get `ALL DEPARTURES MUST REQUEST PUSH BACK ON 127.2` on the ATIS?"  
     <span class="hotline">**ML ADC** -> **ML SMC**</span>: "Wilco"  
 
-    **QFA401:** "Melbourne Delivery, QFA401, Request Clearance"  
-    **ML ACD:** "QFA401, Melbourne Delivery. Cleared to..."  
-    **QFA401:** "Cleared to... we are bay B27, QFA401"  
-    **ML ACD:** "QFA401, Contact me when ready for pushback"  
-    ...  
-    **QFA401:** "Request Pushback"  
-    **ML ACD:** "QFA401, Monitor Ground 121.7, Number 5. They will call you when pushback is available"  
-    **QFA401:** "Monitor 121.7, QFA401"  
-    *ML SMC will move QFA401's strip to the* ***Cleared Queue*** *bay*  
-    *QFA401 will change frequency, but* ***not contact*** *ML SMC*  
-    ...  
-    **ML SMC:** "QFA401, Melbourne Ground, push approved"  
+To operate with pushback requests on ACD:
 
-#### Queue Management
-Remember that the **bottom** aircraft represents the **front** of the queue.
+1. When **ACD** has finished issuing an airways clearance, they will **remind** pilots to *"Contact me when ready for pushback"*.
+2. When a pilot requests pushback, **ACD** will assess their priority based on apron congestion and number of aircraft in the queue (see [Queue Management](#queue-management)).  
+3. **ACD** will either instruct them to **monitor** *(not contact)* SMC, or remain on the ACD frequency if a delay is required.  
+4. If an aircraft is instructed to monitor SMC, **ACD** will move the strip to the **Queue** section of the **Cleared** bay in [OzStrips](../../../client/towerstrips/), to denote they are awaiting pushback approval.  
+5. When **SMC** has adequate space on the aprons, taxiways, and holding point, they will issue pushback/taxi to the next aircraft in line by scanning the [Cleared Queue bay](../../../client/towerstrips/#stripboard).
 
-^ Additionally, the strips must remain in the strip bay of their **current state**, even if they are in a queue. For example, if they have received an airways clearance and are in the queue for pushback, they must remain in the **Cleared** bay, **not** the Pushback bay.
+The decision whether or not to send an aircraft to SMC or hold them on the Coordinator frequency should be made in accordance with the [Queue Management](#queue-management) techniques.
+
+!!! important
+    If SMC needs to reduce the pushback rate due to congestion at the holding points or excessive workload, **ACD** should be informed without delay, and instructed to hold all departures on their frequency. This will stop aircraft being told to monitor the SMC frequency. Remember to cancel this requirement when congestion eases.
+
+!!! example
+    **VOZ543:** "Melbourne Delivery, VOZ543, PDC read back"  
+    **ML ACD:** "VOZ543, go ahead the read back"  
+    **VOZ543:** "DOSEL1 departure, squawk 1336, bay E8, VOZ543"  
+    **ML ACD:** "VOZ543, contact me when ready for pushback"  
+    **VOZ543:** "Wilco, VOZ543"  
+    ...   
+    **VOZ543:** "Melbourne Delivery, VOZ543, bay E8, request pushback"  
+    **ML ACD:** "VOZ543, monitor ground 121.7"  
+    **VOZ543:** "Monitor 121.7, VOZ543"  
+    ...   
+    **ML SMC:** "VOZ543, Melbourne Ground, pushback approved."
+
+If a delay is required prior to transferring an aircraft to SMC, provide an estimated delay value to the pilot or advise them of their position in the queue.
+
+!!! tip
+    Remember that the **bottom** aircraft represents the **front** of the queue.
+
+!!! example
+    **VOZ543:** "Melbourne Delivery, VOZ543, bay E8, request pushback"  
+    **ML ACD:** "VOZ543, estimated delay 10 minutes, remain this frequency."
+
+#### Queue Management
+To reduce SMC workload, ACD should not allow more than **three** aircraft to be awaiting pushback or taxi on the SMC frequency. When three aircraft are already queued on the SMC frequency, any additional aircraft should be told to remain on the ACD frequency and informed of their position in the queue or approximate delay (if known). It may be helpful to cock these strips and move them to the bottom of the bay, creating a queue of aircraft waiting for frequency transfer.
 
 <figure markdown>
-![Cleared Queue Bay](img/clrqbay.png){ width="500" }
-  <figcaption>Cleared Queue Bay</figcaption>
+![Coordinator Ops with OzStrips](img/coordinator-ozstrips.png){ width="700" }
+  <figcaption>Coordinator Ops with OzStrips<br><small>Three aircraft are monitoring SMC (below the Queue bar), and QLK150D and VOZ845 have both requested push/taxi but are being held on the Coordinator frequency. QLK150D is closer to the bottom, so will be next to be told to monitor SMC.</small></figcaption>
 </figure>
 
+When SMC moves an aircraft from the **Cleared Queue** to the **Pushback bay**, Coordinator should instruct the next aircraft in line to monitor the SMC frequency.
+
+!!! important
+    Strips must remain in the strip bay of their **current state**, even if they are in a queue. For example, if they have received an airways clearance and are in the queue for pushback, they must remain in the **Cleared** bay, **not** the Pushback bay.
+
 #### COBT Slot Times
-† Aircraft that are compliant with their booked slot time should be moved to the **front** of the queue
+During busy events, VATPAC may utilise prebooked slots to manage traffic congestion. Aircraft which are compliant with their booked slot time should be prioritised over aircraft who are non-compliant or do not have a slot.
 
 <figure markdown>
 ![COBT Slot Time](img/slottime.png){ width="200" }

docs/aerodromes/classc/Sydney.md

@@ -289,65 +289,60 @@ Climb Gradient Requirements apply to all Procedural SIDs. It is the pilot's resp
 When Independent Visual Approaches are run during PROPS, the APCH field must also include `DO NOT PASS THRU ASSIGNED RWY CL`.
 
 ### Operational Info
+The Operational Information field should be updated based on the runway mode and approach type in use, as per the table below:
 
-> For the following approach types:
-> 
-> - `EXP INSTR APCH`
-> 
-> - `EXP INSTR APCH THEN INDEP VISUAL APCH WHEN VISUAL`
-> 
-> the ATIS OPR INFO shall include `INDEP PARL DEPS IN PROG`.
-> 
-> !!! Note
-    This permits independent departures (two simultaneous departures on parallel runways) but NOT independent approaches (two simultaneous arrivals on parallel runways without perscribed separation minima).
+| Condition | OPR INFO Field |
+| ---------- | -------------- |
+| `EXP INSTR APCH`, or<br>`EXP INSTR APCH THEN INDEP VISUAL APCH WHEN VISUAL` | `INDEP PARL DEPS IN PROG` |
+| `EXP INDEP VISUAL APCH` | `INDEP PARL APPROACHES AND DEPS IN PROG` |
+| SODROPS | `SIMUL OPP DIR PARL RWY OPS IN PROG` |
 
-⠀  
+!!! Note
+    `INDEP PARL DEPS IN PROG` permits independent departures (two simultaneous departures on parallel runways) but NOT independent approaches (two simultaneous arrivals on parallel runways without perscribed separation minima).  
 
-> For the following approach type,
-> 
-> - `EXP INDEP VISUAL APCH`
-> 
-> the ATIS OPR INFO shall include `INDEP PARL APPROACHES AND DEPS IN PROG`.
+When [Coordinator](#sydney-coordinator) is online, the ATIS OPR INFO shall include `WHEN READY FOR PUSH BACK OR TAXI CTC COORDINATOR 127.6`.
 
-⠀  
-
-> When SODPROPS are in operation, the ATIS OPR INFO shall include `SIMUL OPP DIR PARL RWY OPS IN PROG`.
-
-⠀  
-
-> When [Coordinator](#sydney-coordinator) is online, the ATIS OPR INFO shall include `WHEN READY FOR PUSH BACK OR TAXI CTC COORDINATOR 127.6`.
-> 
-> When [Coordinator](#sydney-coordinator) is online and start approval is required, the ATIS OPR INFO shall include `START APPROVAL RQ. WHEN READY FOR PUSH BACK OR ENGINE START, CTC SYDNEY COORDINATOR ON FREQ 127.6, FOR START TIME`.
+When [Coordinator](#sydney-coordinator) is online and start approval is required, the ATIS OPR INFO shall include `START APPROVAL RQ. WHEN READY FOR PUSH BACK OR ENGINE START, CTC SYDNEY COORDINATOR ON FREQ 127.6, FOR START TIME`.
 
 !!! example
     <figure markdown>
         ![IVAs on the ATIS](img/yssy_atis_example.png)
     </figure>
 
 ## Sydney Coordinator
-Sydney Coordinator is activated to reduce frequency congestion on SMC and ensure compliance with pre-determined slot times. The position is rarely used on VATSIM and is only beneficial with the large amounts of traffic seen during annual events like WorldFlight. When Coordinator is online, all departures are first directed to them prior to monitoring SMC.
+Sydney Coordinator is activated to reduce frequency congestion on SMC and ensure compliance with pre-determined slot times. The position is only beneficial with large amounts of traffic and when performed carefully and deliberately. When Coordinator is online, all departures are first directed to them prior to monitoring SMC, thus reducing one radio call per aircraft on the SMC frequency.
 
 !!! important
     Sydney Coordinator is a non-standard position which may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}.
 
 !!! tip
-    The responsibilities of Sydney Coordinator may also be delegated to **ACD** when there is high SMC workload however no seperate Coordinator controller available (as per NOTAM YSSY 220).
+    The responsibilities of Sydney Coordinator may be delegated to **ACD** when there is high SMC workload but no seperate Coordinator controller available. This should be reflected in the ATIS accordingly.
 
-A few steps must be followed during the operation of coordinator:
+To open Coordinator:
 
 1. **SMC** and **COORD** coordinate to implement the procedure.
 2. **SMC** coordinates with **ADC** in order to have the [ATIS](#operational-info) updated to include `WHEN READY FOR PUSH BACK OR TAXI CTC COORDINATOR 127.6`.
-3. When **ACD** has finished issuing an airways clearance, they will **handoff** pilots to Coordinator *"contact Coordinator 127.6 for pushback"* OR **remind** pilots to *"contact me when ready for pushback"* (during combined ACD and COORD).
-4. When a pilot requests pushback, **COORD** will assess their priority based on apron congestion and number of aircraft at the holding point.
-5. **COORD** will either instruct them to **Monitor** *(not contact)* SMC, or remain on the Coordinator frequency for a pushback delay (as per the below phraseology).
-6. Once the aircraft is monitoring SMC, **COORD** will move the strip to the **Queue** section of the **Cleared** bay^ in [OzStrips](../../../client/towerstrips/), to denote they are awaiting pushback approval†.
-7. Eventually, **SMC** will have adequate space on the aprons, taxiways, and holding point, as well as time to make assessments.
-8. **SMC** will scan the [Cleared Queue bay](../../../client/towerstrips/#stripboard) for the next aircraft in line, and call them to approve their pushback.
+
+To operate with Coordinator open:  
+
+1. When **ACD** has finished issuing an airways clearance, they will **handoff** pilots to Coordinator using *"contact Coordinator 127.6 for pushback"* OR **remind** pilots to *"contact me when ready for pushback"* (during combined ACD and COORD).  
+2. When a pilot requests pushback, **COORD** will assess their priority based on apron congestion and number of aircraft in the queue (see [Queue Management](#queue-management)).  
+3. **COORD** will either instruct them to **monitor** *(not contact)* SMC, or remain on the Coordinator frequency if a delay is required.  
+4. If an aircraft is instructed to monitor SMC, **COORD** will move the strip to the **Queue** section of the **Cleared** bay in [OzStrips](../../../client/towerstrips/), to denote they are awaiting pushback approval.  
+5. When **SMC** has adequate space on the aprons, taxiways, and holding point, they will issue pushback/taxi to the next aircraft in line by scanning the [Cleared Queue bay](../../../client/towerstrips/#stripboard).
+
+The decision whether or not to send an aircraft to SMC or hold them on the Coordinator frequency should be made in accordance with the [Queue Management](#queue-management) techniques.
+
+!!! tip
+    Remember that the **bottom** aircraft represents the **front** of the queue.
+
+!!! important
+    If SMC needs to reduce the pushback rate due to congestion at the holding points or excessive workload, **Coordinator** should be informed without delay, and instructed to hold all departures on their frequency. This will stop aircraft being told to monitor the SMC frequency. Remember to cancel this requirement when congestion eases.
 
 !!! example
     **VOZ543:** "Sydney Delivery, VOZ543, PDC read back"  
     **SY ACD:** "VOZ543, go ahead the read back"  
-    **VOZ543:** "OLSEM1 departure, squawk 1336, bay 33, VOZ543"  
+    **VOZ543:** "Runway 34R, OLSEM1 departure, squawk 1336, bay 33, VOZ543"  
     **SY ACD:** "VOZ543, contact Coordinator 127.6 for pushback"  
     **VOZ543:** "127.6 for push, VOZ543"  
     ...   
@@ -357,30 +352,33 @@ A few steps must be followed during the operation of coordinator:
     ...   
     **SY SMC:** "VOZ543, Sydney Ground, pushback approved."
 
-!!! note
-    If a delay is required prior to transferring an aircraft to SMC, provide an estimated delay value to the pilot.
+
+If a delay is required prior to transferring an aircraft to SMC, provide an estimated delay value to the pilot or advise them of their position in the queue.
 
 !!! example
     **VOZ543:** "Sydney Coordinator, VOZ543, bay 33, request pushback"  
     **SY COORD:** "VOZ543, estimated delay 10 minutes, remain this frequency."
 
-#### Start Approval
-When delays for taxi are excessive (e.g. 15–30 minutes), it may be necessary to include the following ATIS OPR INFO: `START APPROVAL RQ. WHEN READY FOR PUSH BACK OR ENGINE START, CTC SYDNEY COORDINATOR ON FREQ 127.6, FOR START TIME`.
-
-This will ensure aircraft don't start their engines before a 30 minute wait, thereby burning considerable fuel and potentially disrupting the latter parts of the flight (e.g. the aircraft may not have enough fuel for lengthy en-route sequencing or holds).
-
 #### Queue Management
-Remember that the **bottom** aircraft represents the **front** of the queue.
-
-^ Additionally, the strips must remain in the strip bay of their **current state**, even if they are in a queue. For example, if they have received an airways clearance and are in the queue for pushback, they must remain in the **Cleared** bay, **not** the Pushback bay.
+To reduce SMC workload, Coordinator should not allow more than **three** aircraft to be awaiting pushback or taxi on the SMC frequency. When three aircraft are already queued on the SMC frequency, any additional aircraft should be told to remain on the Coordinator frequency and informed of their position in the queue or approximate delay (if known). It may be helpful to cock these strips and move them to the bottom of the bay, creating a queue of aircraft waiting for frequency transfer.
 
 <figure markdown>
-![Cleared Queue Bay](img/clrqbay.png){ width="500" }
-  <figcaption>Cleared Queue Bay</figcaption>
+![Coordinator Ops with OzStrips](img/coordinator-ozstrips.png){ width="700" }
+  <figcaption>Coordinator Ops with OzStrips<br><small>Three aircraft are monitoring SMC (below the Queue bar), and QLK150D and VOZ845 have both requested push/taxi but are being held on the Coordinator frequency. QLK150D is closer to the bottom, so will be next to be told to monitor SMC.</small></figcaption>
 </figure>
 
+When SMC moves an aircraft from the **Cleared Queue** to the **Pushback bay**, Coordinator should instruct the next aircraft in line to monitor the SMC frequency.
+
+!!! important
+    Strips must remain in the strip bay of their **current state**, even if they are in a queue. For example, if they have received an airways clearance and are in the queue for pushback, they must remain in the **Cleared** bay, **not** the Pushback bay.
+
+#### Start Approval
+When delays for taxi are excessive (e.g. 15–30 minutes), it may be necessary to include the following ATIS OPR INFO: `START APPROVAL RQ. WHEN READY FOR PUSH BACK OR ENGINE START, CTC SYDNEY COORDINATOR ON FREQ 127.6, FOR START TIME`. This will ensure aircraft don't end up burning considerable amounts of fuel and potentially disrupting the latter parts of the flight (with insufficient fuel for lengthy en-route sequencing or holds).
+
+With start approvals in operation, aircraft who do not require pushback will contact Coordinator prior to starting. Coordinator should issue an estimated start time to the aircraft, and contact them when they reach the front of the queue to provide start approval. Aircraft are still expected to report ready to taxi to Coordinator, who will follow the procedure above and tell them to monitor the SMC frequency.
+
 #### COBT Slot Times
-† Aircraft that are compliant with their booked slot time should be moved to the **front** of the queue
+During busy events, VATPAC may utilise prebooked slots to manage traffic congestion. Aircraft which are compliant with their booked slot time should be prioritised over aircraft who are non-compliant or do not have a slot.
 
 <figure markdown>
 ![COBT Slot Time](img/slottime.png){ width="200" }

docs/aerodromes/classd/Bankstown.md

@@ -40,6 +40,9 @@ Aircraft departing a leg of the circuit will climb to and maintain the following
 RWY 29 direction: `A010`  
 RWY 11 direction: `A015`
 
+## Departures into CTA
+Aircraft planned into the overlying Class C airspace shall be issued an airways clearance by **BK ADC** and assigned `A030`. These aircraft must be Next coordinated to the relevant TCU controller, who will assess the current traffic picture and provide a release when able. During times of peak TMA traffic, there may be extensive delays for departure and pilots may elect to depart directly into class G. See [Departure Coordination](#departures) for coordination requirements.
+
 ### Circuits
 The circuit direction changes depending on time of day and runway being used.
 
@@ -117,13 +120,13 @@ When the crosswind component exceeds 15 knots, the OPR INFO field must include:
 ### Departures
 When the aircraft is ready for departure, Tower will coordinate with the relevant Class C sector above them for permission to release the aircraft into their CTA.
 
+The Standard Assignable level from BK ADC to SY TCU is `A030`, any other level must be prior coordinated.
+
 !!! example
     <span class="hotline">**BK ADC** -> **SY TCU**</span>: "Next, UJN, runway 29C"  
     <span class="hotline">**SY TCU** -> **BK ADC**</span>: "UJN, unrestricted"  
     <span class="hotline">**BK ADC** -> **SY TCU**</span>: "UJN"
 
-The Standard Assignable level from BK ADC to SY TCU is `A030`, any other level must be prior coordinated.
-
 Aircraft shall be instructed to contact SY TCU passing `A015`.
 
 ### Arrivals/Overfliers