diff --git a/docs/aerodromes/classc/Goldy.md b/docs/aerodromes/classc/Goldy.md index 8545be243..5a4ab54d8 100644 --- a/docs/aerodromes/classc/Goldy.md +++ b/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. diff --git a/docs/aerodromes/classd/Archerfield.md b/docs/aerodromes/classd/Archerfield.md index 1230e2b75..3979ecf03 100644 --- a/docs/aerodromes/classd/Archerfield.md +++ b/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** | +| 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 **BN TCU** -> **AF ADC**: "via TVT for the visual approach, UJE" **AF ADC** -> **BN TCU**: "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. \ No newline at end of file + 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 + **AF ADC S** -> **AF ADC N**: "via TAR, TQC for an overhead join" + **AF ADC N** -> **AF ADC S**: "TQC, A015" \ No newline at end of file diff --git a/docs/aerodromes/classd/Bankstown.md b/docs/aerodromes/classd/Bankstown.md index 0bcb48661..1e8a65016 100644 --- a/docs/aerodromes/classd/Bankstown.md +++ b/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** | +| 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. **BK ADC** -> **SY TCU**: "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. \ No newline at end of file + 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 + **BK ADC C** -> **BK ADC N**: "via TWRN, EWY for an overhead join" + **BK ADC N** -> **BK ADC C**: "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 + **BK ADC N** -> **BK ADC C**: "Choppers South Inbound/Outbound" + **BK ADC C** -> **BK ADC N**: "Roger, Traffic is a Cherokee late downwind" \ No newline at end of file diff --git a/docs/aerodromes/classd/Jandakot.md b/docs/aerodromes/classd/Jandakot.md index 0fedf1c66..dfc26d8fe 100644 --- a/docs/aerodromes/classd/Jandakot.md +++ b/docs/aerodromes/classd/Jandakot.md @@ -8,10 +8,26 @@ | Name | Callsign | Frequency | Login ID | | ------------------ | -------------- | ---------------- | ---------------------------------------- | -| **Jandakot ADC** | **Jandakot Tower** | **118.100** | **JT_TWR** | +| **Jandakot ADC West** | **Jandakot Tower** | **118.100** | **JT_TWR** | +| Jandakot ADC (Circuit) :material-information-outline:{ title="Non-standard position"} | Jandakot Tower | 119.400 | JT-C_TWR | | **Jandakot SMC** | **Jandakot Ground** | **124.300** | **JT_GND** | | **Jandakot ATIS** | | **128.650** | **YPJT_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 Jandakot ADC (Circuit) is online, responsibility for the **Runway**, **Circuit**, and **Airspace** is divided between the two ADC controllers. + +ADC West takes responsibility for the North-West Runway, Circuit and Airspace (Runway **06L/24R**), and the entire **JT CTR** at `A015`. + +ADC (Circuit) takes responsibility for the South-East Runway, Circuit and Airspace (Runway **06R/24L**) at or below `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 East is online. + ## Airspace JT ADC is responsible for the Class D airspace in the JT CTR `SFC` to `A015`. @@ -20,8 +36,14 @@ JT ADC is responsible for the Class D airspace in the JT CTR `SFC` to `A015`.
JT ADC Airspace
-## Fixed-Wing Operations -### VFR Arrivals +### Dual ADC Operations +Airspace Ownership when ADC East is online, is: + +- At `A015`; owned entirely by ADC West +- At or below `A010`; split between ADC Circuit/West down the middle of the **06L/24R** and **06R/24L** extended centrelines. + +## VFR Operations +### Arrivals VFR aircraft will report inbound at BOAT, POWR, OAKF or RUSS at `A015`. JT ADC will instruct aircraft to maintain `A015` or remain outside the control zone (workload permitting). Aircraft will then report again at ADWD when inbound from BOAT or POWR, or FDL when inbound from OAKF or RUSS. They should then be instructed to join the circuit as below: | VFR Approach Point | RWYs 06 | RWYs 24 | RWY 12 | RWY 30 | @@ -34,7 +56,7 @@ All aircraft will arrive on runway 06L/24R or 12/30. !!! note Circuit joining instructions given without an assigned altitude imply clearance to conduct the visual approach. There is no need to clear these aircraft for a visual approach. -### VFR Departures +### Departures VFR aircraft should report ready to **JT ADC** with their departure intentions. A takeoff clearance constitutes a clearance to depart the zone by extending the pilot's requested leg of the circuit. Aircraft departing the zone into class G airspace will transfer to area frequency upon leaving the zone, **no explicit frequency transfer is given to these aircraft**. Aircraft departing a leg of the circuit will climb to and maintain the following levels until clear of the zone: @@ -44,10 +66,11 @@ VFR aircraft will depart via set outbound departure routes. Aircraft will track Departures via FREM and YGB will depart on runway 06L/24R. Runway 06R/24L is used for circuit traffic and departures via SHOP. -### IFR Arrivals +## IFR Operations +### Arrivals **PH TCU** will coordinate all IFR arrivals in accordance with coordination procedures. -### IFR Departures +### Departures All IFR Departures must be assigned the most appropriate SID in accordance with the aircraft's direction of flight. | Direction | SID | @@ -56,17 +79,17 @@ All IFR Departures must be assigned the most appropriate SID in accordance with | North/North-west | ISPET | | East/North-east | SCARP | -### Circuits +## Circuits The circuit direction changes depending on tower opening hours and runway being used. -| Runway | Tower Open | Tower Closed | -| -------| ----- | ----- | -| 06L | Left | Right | -| 06R | Right | - | -| 24L | Left | - | -| 24R | Right | Left | -| 12 | Left | Left | -| 30 | Left | Left | +| Runway | Direction | +| -------| ----- | +| 06L | Left | +| 06R | Right | +| 24L | Left | +| 24R | Right | +| 12 | Left | +| 30 | Left | Circuits to be flown at `A010` @@ -79,16 +102,19 @@ Circuits are conducted within the lateral confines of the fixed-wing circuit at ## ATIS ### Runway Nomination -The ATIS must indicate the current runway config and nominate what each parallel runway is being used for. The northern runway (06L/24R) is primarily used for VFR arrivals and departures, the southern runway (06R/24L) for circuit training and departures via `SHOP`, and the cross runway (12/30) for arrivals/departures when weather is unsuitable for parallel rwunay operations. +The ATIS must indicate the current runway config and nominate what each parallel runway is being used for. The northern runway (**06L/24R**) is primarily used for VFR arrivals and departures, the southern runway (**06R/24L**) for circuit training and departures via `SHOP`. The cross runway (**12/30**) for all arrivals/departures when weather is unsuitable for parallel runway operations. This should be reflected on the ATIS as below: -`RWY 06R FOR CIRCUITS AND DEPARTURES VIA ARMADALE SHOPS; RWY 06L FOR ARRIVALS AND ALL OTHER DEPARTURES` -`RWY 24L FOR CIRCUITS AND DEPARTURES VIA ARMADALE SHOPS; RWY 24R FOR ARRIVALS AND ALL OTHER DEPARTURES` -When PH RWY 03 is in operation, the ATIS should include: -`DUE PERTH DUTY RUNWAY 03, CAUTION WAKE TURBULANCE` +- Single ADC: `RWY 06R/24L FOR CCTS AND DEPS VIA ARMADALE SHOPS. RWY 06L/24R FOR ARRS AND ALL OTHER DEPS` +- Dual ADC: `RWY 06R/24L FOR CCTS AND DEPS VIA ARMADALE SHOPS, FREQ 119.4. RWY 06L/24R FOR ARRS AND ALL OTHER DEPS, FREQ 118.1` + +### Operational Info +When PH RWY 03 is in operation, the ATIS OPR INFO shall include: +`DUE YPPH DUTY RWY 03, CAUTION WAKE TURB` + ## Coordination -### Next Call +### Departures [Next](../../controller-skills/coordination.md#next) coordination is required from JT ADC to PH TCU for all aircraft **entering PH TCU CTA**. The Standard Assignable level from **JT ADC** to **PH TCU** is: @@ -107,4 +133,14 @@ VFR aircraft require a level readback. **JT ADC** -> **PH TCU**: "FD416, RNAV-Z RWY 06L with a circle to land RWY 24R" !!! 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. \ No newline at end of file + 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, PH 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. + +### JT ADC Internal +JT ADC must heads-up coordinate **all aircraft** transiting from one ADC controller to the other. + +!!! phraseology + **JT ADC C** -> **JT ADC W**: "via FDL, TBN for an overfly" + **JT ADC W** -> **JT ADC C**: "TBN, A015" \ No newline at end of file diff --git a/docs/aerodromes/classd/Moorabbin.md b/docs/aerodromes/classd/Moorabbin.md index b2a904445..19466a977 100644 --- a/docs/aerodromes/classd/Moorabbin.md +++ b/docs/aerodromes/classd/Moorabbin.md @@ -8,10 +8,26 @@ | Name | Callsign | Frequency | Login ID | |--------------------|----------------------|-------------|--------------| -| **Moorabbin ADC** | **Moorabbin Tower** | **118.100** | **MB_TWR** | +| **Moorabbin ADC East** | **Moorabbin Tower** | **118.100** | **MB_TWR** | +| Moorabbin ADC West :material-information-outline:{ title="Non-standard position"} | Moorabbin Tower | 123.000 | MB-W_TWR | | **Moorabbin SMC** | **Moorabbin Ground** | **134.250** | **MB_GND** | | **Moorabbin ATIS** | | **120.900** | **YMMB_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 Moorabbin ADC West is online, responsibility for the **Runway**, **Circuit**, and **Airspace** is divided between the two ADC controllers. + +ADC East takes responsibility for the East Runway, Circuit and Airspace (Runway **17L/35R** and **13L/31R**). + +ADC West takes responsibility for the West Runway, Circuit and Airspace (Runway **17R/35L** and **13R/31L**). + +ADC West 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 West is online. + ## Airspace MB ADC is responsible for the Class D airspace in the MB CTR from `SFC` to `A025`. @@ -22,6 +38,9 @@ MB ADC is responsible for the Class D airspace in the MB CTR from `SFC` to `A025 Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information. +### Dual ADC Operations +Airspace Ownership when ADC West is online, is split down the middle of the two active extended centrelines. + ## Runway Modes Preferred runway modes are as follows (in order of preference): @@ -123,6 +142,20 @@ Circuit operations are conducted parallel to the duty runway and inside the fixe #### Night Circuits Night operations must comply with fixed wing operations. +## ATIS +### Runway Nomination + +| Priority | Runway Mode | +| ------ | ------ | +| =1 | 17L & 17R | +| =1 | 35L & 35R | +| =2 | 13L & 13R | +| =2 | 31L & 31R | +| 3 | Single Runway Operations (13/17/31/35) | +| 4 | Single Runway Operations (04/22) | + +When 2 ADC controllers are online, the ATIS shall be formatted: `RWY 13L/17L/31R/35R FOR ARRS AND DEPS EAST, FREQ 118.1. RWY 13R/17R/31L/35L FOR ARRS AND DEPS WEST, FREQ 123.0` + ## Coordination ### Departures [Next](../../controller-skills/coordination.md#next) coordination is required from MB ADC to ML TCU for all aircraft **entering ML TCU CTA**. @@ -150,4 +183,14 @@ ML TCU will heads-up coordinate arrivals/overfliers from their Class C to MB ADC **MB ADC** -> **MDS**: "PLE, NDB-A" !!! tip - Remember that IFR aircraft are only separated from other IFR or SVFR aircraft in class D. Use other separation methods, such as holding a departure on the ground, if separation is required with these aircraft. \ No newline at end of file + Remember that IFR aircraft are only separated from other IFR or SVFR aircraft in class D. Use other separation methods, such as holding a departure on the ground, if separation is required with these aircraft. + +#### ADC West Online +When ADC West is online, ML 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. + +### MB ADC Internal +MB ADC must heads-up coordinate **all aircraft** transiting from one ADC controller to the other. + +!!! phraseology + **MB ADC W** -> **MB ADC E**: "via CARR, EWX for an overfly" + **MB ADC E** -> **MB ADC W**: "EWX, A015" \ No newline at end of file diff --git a/docs/aerodromes/classd/Parafield.md b/docs/aerodromes/classd/Parafield.md index d362b4837..2d3e7f7dc 100644 --- a/docs/aerodromes/classd/Parafield.md +++ b/docs/aerodromes/classd/Parafield.md @@ -7,10 +7,26 @@ ## Positions | Name | Callsign | Frequency | Login ID | | ------------------ | -------------- | ---------------- | ---------------------------------------- | -| **Parafield ADC** | **Parafield Tower** | **118.700** | **PF_TWR** | +| **Parafield ADC East** | **Parafield Tower** | **118.700** | **PF_TWR** | +| Parafield ADC West :material-information-outline:{ title="Non-standard position"} | Parafield Tower | 124.600 | PF-W_TWR | | **Parafield SMC** | **Parafield Ground** | **119.900** | **PF_GND** | | **Parafield ATIS** | | **120.900** | **YPPF_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 Parafield ADC West is online, responsibility for the **Runway**, **Circuit**, and **Airspace** is divided between the two ADC controllers. + +ADC East takes responsibility for the South/East Runway, Circuit and Airspace (Runway **08R/26L** and **03R/21L**). + +ADC West takes responsibility for the North/West Runway, Circuit and Airspace (Runway **08L/26R** and **03L/21R**). + +ADC West 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 West is online. + ## Airspace PF ADC is responsible for the Class D airspace in the PF CTR `SFC` to `A015`. @@ -19,6 +35,9 @@ PF ADC is responsible for the Class D airspace in the PF CTR `SFC` to `A015`.
PF ADC Airspace
+### Dual ADC Operations +Airspace Ownership when ADC West is online, is split down the middle of the two active extended centrelines. + ## Circuits Circuits to be flown at `A010` @@ -33,32 +52,42 @@ Circuits to be flown at `A010` | 26L | Left | - | | 26R | Right | - | -## VFR Inbound Procedures +## VFR Operations +### Arrivals | VFR Approach Point | RWYs 03 | RWYs 21 | RWYs 08 | RWYs 26 | | ----------------| --------- | ---------- | ----- | ----- | | OHB | Join base (or downwind) RWY 03L | Join base (or downwind) RWY 21R | Join final RWY 08L| Join downwind RWY 26R | | DMW | Join downwind RWY 03R | Join 3NM final RWY 21L| Join downwind RWY 08L | Join final RWY 26R | -!!! note - Visually monitor all aircraft to ensure tracking South of Bolivar Strobe, to ensure aircraft remain outside of Edinburgh CTR. +!!! warning "Important" + Visually monitor all aircraft to ensure tracking South of **Bolivar Strobe** (located at the Southern tip of the EDN CTR), to ensure aircraft remain outside of EDN CTR.
- ![Bolivar](img/bolivar.png){ width="700" } + ![Bolivar](img/bolivar.png){ width="400" }
+## IFR Operations +### Departures +IFR Departures from YPPF shall be assigned **PF RADAR** SID when Runway 03/21 is in use. + ## ATIS -### Operational Info -ATIS broadcast **BY DAY** shall follow the format: -`RWY 21R (OR 03L) FOR ARRS & DEPS WEST, RWY 21L (OR 03R) ARRS & DEPS EAST` -OR -`RWY 26R (OR 08L) FOR ARRS & DEPS, RWY 26L (OR 08R) FOR CCT TRAINING` - -ATIS broadcast **BY NIGHT** shall follow the format: -`RWY 21R (OR 03L) FOR ALL OPERATIONS` +### Runway Nomination + +| Priority | Runway Mode | +| ------ | ------ | +| =1 | 03L & 03R | +| =1 | 21L & 21R | +| =2 | 08L & 08R | +| =2 | 26L & 26R | +| 3 | Any Single Runway Operations | + +When 2 ADC controllers are online, the ATIS shall be formatted: `RWY 03R/08R/21L/26L FOR ARRS AND DEPS EAST, FREQ 118.7. RWY 03L/08L/21R/26R FOR ARRS AND DEPS WEST, FREQ 124.6` + +By Night, Only Runway **03L/21R** may be used. ### Approach Expectation The APCH field should include `EXP INST APCH` when: - the ceiling is at or below `A020`; or - - visibility is less than 5000m + - visibility is less than **5000m** ## Coordination ### Departures @@ -75,10 +104,26 @@ AD TCU will heads-up coordinate arrivals/overfliers from Class C to PF ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to PF ADC, unless PF ADC nominates a restriction. VFR aircraft require a level readback. - !!! phraseology **AAW** -> **PF ADC**: "via PAL, YTS" **PF ADC** -> **AAW**: "YTS, 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. \ No newline at end of file + 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. + +## Taxi Routes +Taxiway Bravo crosses through the Undershoots of Runway 26L and 26R. As per YPPF Aerodrome Chart, a `Clearance is Required` to taxi through these areas, using the same phraseology as normal Runway Crossings. + +!!! phraseology + **PF SMC:** "USP, On Bravo cross the undershoots of Runway 26L and 26R. Taxi to Holding Point B1, Runway 03L." + **USP:** "On Bravo cross undershoots of Runway 26L & 26R. Taxi to Holding Point B1 Runway 03L, USP." + +#### ADC West Online +When ADC West is online, AD 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. + +### PF ADC Internal +PF ADC must heads-up coordinate **all aircraft** transiting from one ADC controller to the other. + +!!! phraseology + **PF ADC W** -> **PF ADC E**: "via OHB, YNM for an overhead join" + **PF ADC E** -> **PF ADC W**: "YNM, A015" \ No newline at end of file diff --git a/docs/aerodromes/classd/img/bolivar.png b/docs/aerodromes/classd/img/bolivar.png index df0c68558..a0ed719ec 100644 Binary files a/docs/aerodromes/classd/img/bolivar.png and b/docs/aerodromes/classd/img/bolivar.png differ diff --git a/docs/aerodromes/procedural/Tamworth.md b/docs/aerodromes/procedural/Tamworth.md index e895e423b..8da67bae0 100644 --- a/docs/aerodromes/procedural/Tamworth.md +++ b/docs/aerodromes/procedural/Tamworth.md @@ -9,9 +9,25 @@ | Name | Callsign | Frequency | Login ID | | ---- | -------- | --------- | ---------------- | | **Tamworth ADC** | **Tamworth Tower** | **119.400** | **TW_TWR** | +| Tamworth ADC South :material-information-outline:{ title="Non-standard position"} | Tamworth Tower | 118.250 | TW-S_TWR | | **Tamworth SMC** | **Tamworth Ground** | **121.900** | **TW_GND** | | **Tamworth ATIS** | | **123.800** | **YSTW_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 Tamworth ADC South is online, responsibility for the **Runway**, **Circuit**, and **Airspace** is divided between the two ADC controllers. + +ADC North takes responsibility for the North Runway, Circuit and Airspace (Runway **12L/30R**). + +ADC South takes responsibility for the South Runway, Circuit and Airspace (Runway **12R/30L**). + +ADC South 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 2 is online. + ## Airspace
![TW ADC Airspace](img/YSTW_airspace.png){ width="800" } @@ -22,6 +38,14 @@ TW ADC is responsible for the Class D airspace in the TW CTR, as well as the Cla Refer to [Class D Tower Separation Standards](../../../separation-standards/classd) for more information. +### Dual ADC Operations +When ADC South is Online, they are responsible for the airspace between the **TW** 160 Radial, West through to the 295 Radial. + +
+![TW Dual ADC Airspace](img/twadcown.png){ width="600" } +
TW Dual ADC Airspace
+
+ ## Surveillance Surveillance coverage can be expected to be not available below `A034` in the TW CTR. Although TW ADC is **not permitted** to use surveillance for separation, ARL/MDE may assist by establishing surveillance separation standards via coordination @@ -58,6 +82,10 @@ The positions in each table header below are procedurally separated from each ot | LLC West of **GWT** | | | | LLC North of
**DGN - NEM - Tamworth City
- MAL via Manilla Rd** | | | +The [geographic feature separation standard](../../separation-standards/visual.md#geographic-features) may also be useful to efficiently process aircraft. + +The **Oxley** and **New England** Highways are good references for this standard. + ## Runway Modes Equal preference is shared between runways 12L/R and 30L/R. @@ -79,9 +107,12 @@ In the absense of day VMC, dependent parallel runway operations may be conducted Circuits are to be flown in the direction coinciding with the Runway designator (Left/Right) at `A024`. ## ATIS +### Runway Nomination +When 2 ADC controllers are online, the ATIS shall be formatted: `RWY 12R/30L FOR CCTS AND ARRS AND DEPS SOUTH WEST, FREQ 118.25. RWY 12L/30R FOR ALL OTHER ARRS AND DEPS, FREQ 119.4` + ### Operational Info When parallel runway operations are in use, the ATIS OPR INFO field shall include: -`SIMUL PARL RWY OPS IN USE. EXP TRAFFIC ON FINAL AND OPP BASE OF THE PARL RWY` +`SIMUL PARL RWY OPS IN USE. EXP TFC ON FINAL AND OPP BASE OF THE PARL RWY` ## Coordination ### Departures @@ -100,4 +131,14 @@ ARL/MDE will heads-up coordinate all arrivals/overfliers to TW ADC **MDE** -> **TW ADC**: "Via MOR DCT for the VOR-A, FD272” **TW ADC** -> **MDE**: "FD272, VOR-A" -The Standard Assignable level from ARL/MDE to TW ADC is `A080`, any other level must be prior coordinated. \ No newline at end of file +The Standard Assignable level from ARL/MDE to TW ADC is `A080`, any other level must be prior coordinated. + +#### ADC 2 Online +When ADC 2 is online, ARL/MDE 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. + +### TW ADC Internal +TW ADC must heads-up coordinate **all aircraft** transiting from one ADC controller to the other. + +!!! phraseology + **TW ADC S** -> **TW ADC**: "via GWT, SPP for an overfly" + **TW ADC** -> **TW ADC S**: "SPP, A035" \ No newline at end of file diff --git a/docs/aerodromes/procedural/img/twadcown.png b/docs/aerodromes/procedural/img/twadcown.png new file mode 100644 index 000000000..e7ad66af3 Binary files /dev/null and b/docs/aerodromes/procedural/img/twadcown.png differ diff --git a/docs/controller-skills/hoto.md b/docs/controller-skills/hoto.md index 44ffa5934..849114bb2 100644 --- a/docs/controller-skills/hoto.md +++ b/docs/controller-skills/hoto.md @@ -37,9 +37,9 @@ Anything else they need to know? ## Example !!! example "**Runway** 16 for arrivals, 27 for departures at YMML. Runway 34L and 34R at YSSY. Runway 35 at YSCB. Runway 25 at YMAY. - **Airspace**, We're controlling ELW, extending to BIK, providing top-down at YMML, YSSY and YSCB. AY TWR is online, and YWE is online, extending to ARL and HUO. Airspace releases all normal. + **Airspace**, We're controlling ELW, extending to GUN, providing top-down at YMML, YSSY and YSCB. AY TWR is online, and MUN is online, extending to ARL and HUO. Airspace releases all normal. **Weather** is mostly normal, Area QNHs are high, except for a small part to the east of Area 30. **Frequencies** active are 123.75 and 129.8. - **Traffic**, QFA428 is taxiing 34L at YSSY, WOL2 departure for YMML. No other calls on the ground at YSSY, YSCB or YMML. VOZ831 is on climb, coordination to YWE is done. LPD has clearance to leave controlled airspace descending. QJE1721 and UAL19 are both estimating LIZZI at the same time, will need some sequencing. JST528 and BNZ192 are coming in from the north, haven't yet assessed if they're in conflict. + **Traffic**, QFA428 is taxiing 34L at YSSY, WOL2 departure for YMML. No other calls on the ground at YSSY, YSCB or YMML. VOZ831 is on climb, coordination to MUN is done. LPD has clearance to leave controlled airspace descending. QJE1721 and UAL19 are both estimating LIZZI at the same time, will need some sequencing. JST528 and BNZ192 are coming in from the north, haven't yet assessed if they're in conflict. No other **outstanding instructions** other than frequency transfers and handoffs. Any questions?" \ No newline at end of file diff --git a/docs/enroute/Brisbane Centre/TRT.md b/docs/enroute/Brisbane Centre/TRT.md index 1c588956f..5021c8aa6 100644 --- a/docs/enroute/Brisbane Centre/TRT.md +++ b/docs/enroute/Brisbane Centre/TRT.md @@ -80,7 +80,7 @@ Aircraft being transferred from the following sectors shall be given STAR Cleara !!! warning "Important" Due to its operational complexity, LAHSO **must be authorised by a member of the VATPAC ATS or Events Staff Team or a C3-rated controller**. -In accordance with the authorisation requirements above, YPDN may utilise LAHSO during exceptionally busy events. Detailed procedures exist to ensure that controllers are aware of their responsibilities when performing LAHSO. See [Controller Skills](../controller-skills/runwaymanagement.md#lahso) for more information. +In accordance with the authorisation requirements above, YPDN may utilise LAHSO during exceptionally busy events. Detailed procedures exist to ensure that controllers are aware of their responsibilities when performing LAHSO. See [Controller Skills](../../../controller-skills/runwaymanagement/#lahso) for more information. ## Coordination diff --git a/docs/terminal/coral.md b/docs/terminal/coral.md index 88b157883..ed1160db4 100644 --- a/docs/terminal/coral.md +++ b/docs/terminal/coral.md @@ -63,6 +63,11 @@ Voiceless for all aircraft: All other aircraft coming from SWY/KPL CTA will be **Heads-up** Coordinated to MKA/RKA. ### MK/RK ADC +#### Airspace +MK ADC is responsible for the Class D airspace in the MK CTR `SFC` to `A010`. + +RK ADC is responsible for the Class D airspace in the RK CTR `SFC` to `A010`. + #### Auto Release [Next](../controller-skills/coordination.md#next) coordination is **not** required to MKA/RKA for aircraft that are: @@ -77,6 +82,15 @@ The Standard Assignable level from **MK/RK ADC** to **MKA/RKA** is: | ------ | ----- | | All | The lower of `A060` and `RFL` | +!!! phraseology + **MK ADC** -> **MKA**: "Next, ABC, runway 14" + **MKA** -> **MK ADC**: "ABC, Heading 150 Visual, unrestricted" + **MK ADC** -> **MKA**: "Heading 150 Visual unrestricted, ABC" + +The TCU controller can suspend/resume Auto Release at any time, with the concurrence of **ADC**. + +The Standard Assignable level from MK/RK ADC to MKA/RKA is the lower of `A060` or the `RFL`. + #### MK/RK SMC The controller assuming responsibility of **SMC** shall give [Heads-up](../controller-skills/coordination.md#heads-up) coordination to TCU controller prior to the issue of the following clearances: diff --git a/docs/terminal/nowra.md b/docs/terminal/nowra.md index d30bac10b..0bdc1e2e2 100644 --- a/docs/terminal/nowra.md +++ b/docs/terminal/nowra.md @@ -10,7 +10,7 @@ | **Nowra TMA** | **NWA** | **Nowra Approach** | **123.500** | **NW_APP** | ## Airspace -NW TCU owns the airspace within R421, `SFC` to `F125`. Where traffic levels (primarily preplanned military operations) warrant, NW TCU may request a release of R420F from `F125` to `F300` from BIK(WOL), if online. +NW TCU owns the airspace within R421, `SFC` to `F125`. Where traffic levels (primarily preplanned military operations) warrant, NW TCU may request a release of R420F from `F125` to `F300` from WOL, if online.
![NW TMA](img/nwtcu.png){ width="700" } @@ -28,7 +28,7 @@ Where it is deemed operationally beneficial to activate R420F, this should be re **WOL** -> **NW TCU**: "R420F released to you F125 to F300" **NW TCU** -> **WOL**: "R420F released F125 to F300" -As per [Coordination](#enroute), with R420F active, all transiting aircraft will be coordinated by BIK(WOL). Where possible, facilitate the transit of these aircraft. In exceptional circumstances where the level of military aircraft movements prohibit transiting civil aircraft, inform BIK(WOL) that no transiting aircraft can be accommodated, and that they will need to be rerouted to remain clear of the TCU. +As per [Coordination](#enroute), with R420F active, all transiting aircraft will be coordinated by WOL. Where possible, facilitate the transit of these aircraft. In exceptional circumstances where the level of military aircraft movements prohibit transiting civil aircraft, inform WOL that no transiting aircraft can be accommodated, and that they will need to be rerouted to remain clear of the TCU. !!! warning "Important" Activating R420F increases the workload of the overlying enroute controller by altering the airspace normally available to them for civil aircraft. Only activate this airspace if operationally necessary, primarily for preplanned military exercises. @@ -52,7 +52,7 @@ Voiceless for aircraft: - Tracking via a published airway; and - Assigned the lower of `F120` or the `RFL` -All other aircraft going to BIK(WOL) CTA must be **Heads-up** Coordinated by NW TCU prior to the boundary. +All other aircraft going to WOL CTA must be **Heads-up** Coordinated by NW TCU prior to the boundary. #### Arrivals Voiceless for aircraft: @@ -61,7 +61,7 @@ Voiceless for aircraft: - Tracking direct to the NWA TACAN or YSNW; and - Assigned `F130` -All other aircraft coming from BIK(WOL) CTA will be **Heads-up** Coordinated to NW TCU. +All other aircraft coming from WOL CTA will be **Heads-up** Coordinated to NW TCU. ### NW ADC #### Airspace @@ -76,4 +76,9 @@ The Standard Assignable level from **NW ADC** to **NW TCU** is: | -------- | ----- | | All | The lower of `F120` and `RFL` | +!!! phraseology + **NW ADC** -> **NW TCU**: "Next, BUCK03, runway 08" + **NW TCU** -> **NW ADC**: "BUCK03, Assigned Heading Left 030, unrestricted" + **NW ADC** -> **NW TCU**: "Assigned Heading Heading Left 030, BUCK03" + Helicopters departing from helicopter spots will be treated as if departing from the duty runway. \ No newline at end of file