Metro D Dual ADCs

docs/aerodromes/classc/Goldy.md

@@ -34,7 +34,7 @@ Radar SID aircraft shall be cleared subject to the following conditions for nois
 |  **North**   |   Left turn and then over water until `A030`    | Right turn and then over water until `A030` |
 |  **East**   |   Left turn and then over water until `A030`      | Right turn and then over water until `A030` |
 |  **South** Jets   |   Minor right turn then over water until 5 DME   |    Over water until south of KCFF (CG130/7 NM) and `A050`    |
-|  **South** Non-Jets  |    Left turn and then over water until `A030`     | Right turn and then over water until `A030`  |
+|  **South** Non-Jets  |    Left turn and then over water until `A030`     | Right turn and then over water until `A030`  | 
 
 ## Arrivals
 Arriving aircraft that are operating at or below `A015` may contact ADC for inbound clearance. These aircraft shall be assigned a discrete SSR code but shall not be radar identified.  

docs/aerodromes/classd/Archerfield.md

@@ -7,10 +7,26 @@
 ## Positions
 | Name               | Callsign       | Frequency        | Login ID                         |
 | ------------------ | -------------- | ---------------- | ---------------------------------------- |
-| **Archerfield ADC**  | **Archer Tower**  | **118.100**        | **AF_TWR**                        |
+| **Archerfield ADC South**  | **Archer Tower**  | **118.100**        | **AF_TWR**                        |
+| <span class="indented">Archerfield ADC North :material-information-outline:{ title="Non-standard position"}  | Archer Tower  | 123.600        | AF-N_TWR                        |
 | **Archerfield SMC**   | **Archer Ground**  | **129.300**         | **AF_GND**                       |
 | **Archerfield ATIS**        |                | **120.900**          | **YBAF_ATIS**                                |
 
+!!! abstract "Non-Standard Positions"
+    :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}.  
+    Approval must be sought from the **bolded parent position** prior to opening a Non-Standard Position, unless [NOTAMs](https://vatpac.org/publications/notam){target=new} indicate otherwise (eg, for events).
+
+### Dual ADC Operations
+When Archerfield ADC North is online, responsibility for the **Runway**, **Circuit**, and **Airspace** is divided between the two ADC controllers.
+
+ADC South takes responsibility for the South/East Runway, Circuit and Airspace (Runway **10R, 28L, 04R, 22L**).
+
+ADC North takes responsibility for the North/West Runway, Circuit and Airspace (Runway **10L, 28R, 04L, 22R**).
+
+ADC North is **not permitted** online when *Single Runway* Operations are in use.
+
+Refer to the [ATIS section](#dual-adc-operations_2) for information on ATIS formatting when ADC North is online.
+
 ## Airspace
 AF ADC is responsible for the Class D airspace in the AF CTR `SFC` to `A015`.
 
@@ -21,7 +37,11 @@ AF ADC is responsible for the Class D airspace in the AF CTR `SFC` to `A015`.
 
 Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information.
 
-## VFR Arrival Procedures
+### Dual ADC Operations
+Airspace Ownership when ADC North is online, is split down the middle of the two active extended centrelines.
+
+## VFR Procedures
+### Arrivals
 VFR aircraft should track via a VFR inbound point at `A015` and be instructed as below:
 
 | VFR Approach Point | RWYs 04  | RWYs 22 | RWYs 10  | RWYs 28 | 
@@ -34,7 +54,7 @@ VFR aircraft should track via a VFR inbound point at `A015` and be instructed as
 !!! note
     Aircraft joining downwind are instructed to maintain `A015` for separation with aircraft departing the zone at `A010`.  Once inbound aircraft are clear of the departure track, they should be *"cleared visual approach"*.
 
-## VFR Departure Procedures
+### Departures
 
 | Planned Departure Tracks | "Intentions"   | Tracking Requirement | 
 | ---------------      | ---------      | ----------           | 
@@ -137,14 +157,30 @@ Helicopters inbound from the south via PKR for either the northen or central hel
 ## ATIS
 ### Runway Nomination
 
-The ATIS must indicate the current runway config and nominate what each runway is being used for.  This should be reflected on the ATIS as below:
+| Priority | Runway Mode |
+| ------ | ------ |
+| =1     | 10L & 10R |
+| =1     | 28L & 28R |
+| =2     | 04L & 04R |
+| =2     | 22L & 22R |
+| 3      | Any Single Runway Operations |
+
+The ATIS must indicate the current runway config and nominate what each runway is being used for. This should be reflected on the ATIS as below:
 
 | Runway | RWY Field  |
 | ----------------| --------- |
 | Single RWY      | `ALL OPERATIONS RWY (Number)` |
-| RWY 10/28       | `RWY 10L/28R FOR ARRIVALS AND DEPARTURES NORTH; RWY 10R/28L FOR ARRIVALS AND DEPARTURES SOUTH` |
-| RWY 04          | `RWY 04L FOR ARRIVALS AND DEPARTURES NORTH AND WEST; RWY 04R FOR ARRIVALS AND DEPARTURES SOUTH AND EAST` |
-| RWY 22          | `RWY 22. EASTERN DEPARTURES NOT AVAILABLE. RWY 22R FOR ARRIVALS AND DEPARTURES NORTH AND WEST; RWY 22L FOR ARRIVALS SOUTH AND EAST AND DEPARTURES SOUTH` |
+| RWY 10/28       | `RWY 10L/28R FOR ARRS AND DEPS NORTH. RWY 10R/28L FOR ARRS AND DEPS SOUTH` |
+| RWY 04          | `RWY 04L FOR ARRS AND DEPS NORTH AND WEST. RWY 04R FOR ARRS AND DEPS SOUTH AND EAST` |
+| RWY 22          | `RWY 22. EASTERN DEPS NAVBL. RWY 22R FOR ARRS AND DEPS NORTH AND WEST. RWY 22L FOR ARRS SOUTH AND EAST AND DEPS SOUTH` |
+
+#### Dual ADC Operations
+
+| Runway | RWY Field  |
+| ----------------| --------- |
+| RWY 10/28       | `RWY 10L/28R FOR ARRS AND DEPS NORTH, FREQ 123.6. RWY 10R/28L FOR ARRS AND DEPS SOUTH, FREQ 118.1` |
+| RWY 04          | `RWY 04L FOR ARRS AND DEPS NORTH AND WEST, FREQ 123.6. RWY 04R FOR ARRS AND DEPS SOUTH AND EAST, FREQ 118.1` |
+| RWY 22          | `EASTERN DEPS NAVBL. RWY 22R FOR ARRS AND DEPS NORTH AND WEST, FREQ 123.6. RWY 22L FOR ARRS SOUTH AND EAST AND DEPS SOUTH, FREQ 118.1` |
 
 ### Approach Expectation
 The APCH field should include `EXP INST APCH` when:   
@@ -172,11 +208,19 @@ BN TCU will heads-up coordinate arrivals/overfliers from Class C to AF ADC.
 IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to AF ADC, unless AF ADC nominates a restriction.  
 VFR aircraft require a level readback.
 
-
 !!! phraseology
     <span class="hotline">**BN TCU** -> **AF ADC**</span>: "via TVT for the visual approach, UJE"  
     <span class="hotline">**AF ADC** -> **BN TCU**</span>: "UJE, visual approach"
 
-
 !!! tip
-    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.
+    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.
+
+#### ADC North Online
+When ADC North is online, BN TCU may not be familiar with which controller owns what airspace. Best practice is to receive the coordination no matter what, and if it was meant for the other ADC controller, relay the coordination to them internally.
+
+### AF ADC Internal
+AF ADC must heads-up coordinate **all aircraft** transiting from one ADC controller to the other.
+
+!!! phraseology
+    <span class="hotline">**AF ADC S** -> **AF ADC N**</span>: "via TAR, TQC for an overhead join"  
+    <span class="hotline">**AF ADC N** -> **AF ADC S**</span>: "TQC, A015"

docs/aerodromes/classd/Bankstown.md

@@ -7,10 +7,26 @@
 ## Positions
 | Name               | Callsign       | Frequency        | Login ID                         |
 | ------------------ | -------------- | ---------------- | ---------------------------------------- |
-| **Bankstown ADC**  | **Bankstown Tower**  | **132.800**         | **BK_TWR**                        |
+| **Bankstown ADC North**  | **Bankstown Tower**  | **132.800**         | **BK_TWR**                        |
+| <span class="indented">Bankstown ADC (Circuit) :material-information-outline:{ title="Non-standard position"}  | Bankstown Tower  | 123.600        | BK-C_TWR                        |
 | **Bankstown SMC**   | **Bankstown Ground**   | **119.900**         | **BK_GND**                       |
 | **Bankstown ATIS**        |                | **120.900**          | **YSBK_ATIS**                                |
 
+!!! abstract "Non-Standard Positions"
+    :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}.  
+    Approval must be sought from the **bolded parent position** prior to opening a Non-Standard Position, unless [NOTAMs](https://vatpac.org/publications/notam){target=new} indicate otherwise (eg, for events).
+
+### Dual ADC Operations
+When Bankstown ADC (Circuit) is online, responsibility for the **Runway**, **Circuit**, and **Airspace** is divided between the two ADC controllers.
+
+ADC North takes responsibility for the Northern Runways, Circuit and Airspace (Runway **11L/29R**, **11C/29C**), and Southern Airspace at **at A015**.
+
+ADC (Circuit) takes responsibility for the Southern Runway, Circuit and Airspace (Runway **11R/29L**), **not above A010**
+
+ADC (Circuit) is **not permitted** online when *Single Runway* Operations are in use.
+
+Refer to the [ATIS section](#runway-nomination) for information on ATIS formatting when ADC (Circuit) is online.
+
 ## Airspace
 BK ADC is responsible for the Class D airspace in the BK CTR `SFC` to `A015`.
 
@@ -57,6 +73,36 @@ The circuit direction changes depending on time of day and runway being used.
 
 Circuits to be flown at `A010`
 
+## Adjacent Runways
+### Proximity
+There is 106 metres between the centrelines of Runway **11R/29L** & **11C/29C**, and 106 metres between the centrelines of Runway **11C/29C** & **11L/29R**.
+Due to the close proximity in critical stages of flight, there are additional considerations (below).
+
+### Dependent Runway Operations (Departures Only)
+At Bankstown, all Runways are considered Independent unless a Multi-Engined OR Jet aircraft departs from an adjacent Runway. 
+In this instance, runways are treated as dependent *for departures ONLY*. Controllers should apply the same Runway standard across all dependant Runways. Arriving aircraft are exempt from this clause.
+
+Definitions;
+Independent: Runways can operate simultaneously without restriction.
+Dependent: Runways are operated with restrictions, often one at a time.
+
+Example A; A King Air (Multi-Engine) is ready to depart Runway 29R. A Cherokee is departing Runway 29L. Runways are not adjacent, and are therefore independent of each other.
+Example B; A Citation (Jet) is ready Runway 11C. Both Runways 11L & 11R are adjacent, and a Runway Separation Standard should be applied across ALL three Runways. Note: Arriving Aircraft are exempt.
+Example C; A PC12 (Single Engine) is ready Runway 29C. There aircraft is a single-engined aircraft and the Runways are treated independently from one another.
+Example D; A Seminole (Multi-Engine) is cleared a Touch & Go on Runway 11R. Any aircraft departing from the adjacent Runway (11C) must have a Runway separation standard applied.
+
+### Opposite Bases (Arrivals Only)
+DO NOT allow aircraft to turn final simultaneously AND in close proximity.
+Controllers should allow at least one aircraft to become established on final prior to the second commencing their turn to final, and MUST pass mutual traffic.
+
+!!! phraseology
+    **BK ADC:** "FWC, Traffic is a King Air, late right base assigned the middle runway"
+
+### Holding Aircraft Between Runways
+As per YSBK ERSA, all aircraft should remain on Tower frequency when between Runways.
+The largest aircraft that can safely hold between Runways is a BE20 (King Air). All larger aircraft are considered to be occupying the runway behind until clear of all active Runways. 
+All helicopters are considered to be larger than a King Air for the purpose of this clause.
+
 ## Helicopter Operations
 ### General
 These procedures apply during hours of daylight only. During hours of darkness, all helicopters must revert to fixed-wing operations.  
@@ -69,6 +115,7 @@ Three helicopter reporting points help keep helicopters segregated from other tr
 CWST: Michels Patisserie located 1.2nm west of CNTH on the water pipeline  
 CNTH: Northern end of Regents Park Railway Station, roughly 300 metres north of the water pipeline  
 CSTH: Intersection of two creeks enclosing a sewage treatment works 2.1nm south of the aerodrome reference point
+
 ### Inbound Procedures
 Helicopters should track inbound at `A007` via one of the normal inbound points (PSP or TWRN) or via *Olympic Park* and report to **BK ADC** at that point. In response, **BK ADC** should instruct the aircraft to track as below:
 
@@ -84,6 +131,7 @@ Helicopters should track inbound at `A007` via one of the normal inbound points
     Example:  
     *"LOI, traffic is a helicopter overflying the aerodrome to the north at A005, runway left, cleared touch and go"*  
     *"YZD, traffic is a Cherokee turning final for runway left, overfly midfield at A005, join downwind main pad"*
+
 ### Outbound Procedures
 Helicopters should track outbound via one of the helicopter reporting points at `A007`. Departures to the north must track via CWST when RWY 29s are in use and CNTH when RWY 11s are in use.
 
@@ -99,6 +147,7 @@ Helicopters shall report ready to **BK ADC** with their departure intentions. In
     Example:  
     *"XEL, traffic is a helicopter overflying the aerodrome to the south at A005, runway left, cleared touch and go"*  
     *"YZD, traffic is a Cherokee turning final for runway left, depart Choppers South, main pad, cleared for takeoff"*
+
 ### Circuits
 Circuits are conducted within the lateral confines of the fixed-wing circuit at `A007`, in the same direction as the current runway config. The termination point of the circuit is the Main Pad.
 
@@ -110,7 +159,10 @@ Circuits are conducted within the lateral confines of the fixed-wing circuit at
 The ATIS must indicate the current runway config and nominate what each parallel runway is being used for. The northern runway (11L/29R) is primarily used for VFR arrivals and departures, the southern runway (11R/29L) for circuit training, and the centre runway for IFR arrivals/departures and VFR overflow.  
 
 This should be reflected on the ATIS as below:  
-`RWY 11L FOR ARRIVALS AND DEPARTURES; RWY 11R FOR CIRCUIT TRAINING; RWY 11C IN USE`
+
+- Single ADC: `RWY 11L/29R FOR ARRS AND DEPS. RWY 11R/29L FOR CCT TRAINING. RWY 11C/29C IN USE`
+- Dual ADC: `RWY 11L/29R FOR ARRS AND DEPS, FREQ 132.8. RWY 11R/29L FOR CCT TRAINING, FREQ 123.6. RWY 11C/29C IN USE`
+
 ### Operational Info
 When the crosswind component exceeds 15 knots, the OPR INFO field must include:  
 `CROSSWIND ALERT – DO NOT PASS THROUGH FINAL FOR YOUR ASSIGNED RUNWAY`
@@ -137,4 +189,20 @@ VFR aircraft require a level readback.
     <span class="hotline">**BK ADC** -> **SY TCU**</span>: "UJN, A010"
 
 !!! tip
-    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.
+    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.
+
+#### ADC (Circuit) Online
+When ADC (Circuit) is online, SY TCU may not be familiar with which controller owns what airspace. Best practice is to receive the coordination no matter what, and if it was meant for the other ADC controller, relay the coordination to them internally.
+
+### BK ADC Internal
+BK ADC must heads-up coordinate **all aircraft** transiting from one ADC controller to the other.
+
+!!! phraseology
+    <span class="hotline">**BK ADC C** -> **BK ADC N**</span>: "via TWRN, EWY for an overhead join"  
+    <span class="hotline">**BK ADC N** -> **BK ADC C**</span>: "EWY, A015"
+
+BK ADC must coordinate **all helicopter traffic** via CSTH. Coordination must take place prior to Take-Off clearance bring issued (departures) OR before issuing a clearance beyond CSTH (arrivals). When responding to coordination, ADC2 should pass aircraft type and position of any aircraft likely to affect the crossing midfield at A005.
+
+!!! phraseology
+    <span class="hotline">**BK ADC N** -> **BK ADC C**</span>: "Choppers South Inbound/Outbound"  
+    <span class="hotline">**BK ADC C** -> **BK ADC N**</span>: "Roger, Traffic is a Cherokee late downwind"