From 9b23ff4da5548c00133586910393bda28f5fc105 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Fri, 13 Dec 2024 17:57:58 +1100 Subject: [PATCH 1/3] admonitions --- docs/aerodromes/classc/Adelaide.md | 8 +- docs/aerodromes/classc/Amberley.md | 6 +- docs/aerodromes/classc/Brisbane.md | 4 +- docs/aerodromes/classc/Cairns.md | 18 +- docs/aerodromes/classc/Canberra.md | 10 +- docs/aerodromes/classc/Curtin.md | 2 +- docs/aerodromes/classc/Darwin.md | 2 +- docs/aerodromes/classc/EastSale.md | 6 +- docs/aerodromes/classc/Essendon.md | 8 +- docs/aerodromes/classc/Goldy.md | 2 +- docs/aerodromes/classc/Learmonth.md | 2 +- docs/aerodromes/classc/Melbourne.md | 28 +-- docs/aerodromes/classc/Nowra.md | 6 +- docs/aerodromes/classc/Oakey.md | 2 +- docs/aerodromes/classc/Perth.md | 6 +- docs/aerodromes/classc/Scherger.md | 2 +- docs/aerodromes/classc/Sydney.md | 38 ++-- docs/aerodromes/classc/Townsville.md | 2 +- docs/aerodromes/classc/Williamtown.md | 4 +- docs/aerodromes/classd/Archerfield.md | 6 +- docs/aerodromes/classd/Avalon.md | 4 +- docs/aerodromes/classd/Bankstown.md | 8 +- docs/aerodromes/classd/Camden.md | 10 +- docs/aerodromes/classd/Hobart.md | 16 +- docs/aerodromes/classd/Jandakot.md | 4 +- docs/aerodromes/classd/Launceston.md | 4 +- docs/aerodromes/classd/Mackay.md | 4 +- docs/aerodromes/classd/Moorabbin.md | 8 +- docs/aerodromes/classd/Parafield.md | 4 +- docs/aerodromes/classd/Rockhampton.md | 4 +- docs/aerodromes/procedural/Albury.md | 4 +- docs/aerodromes/procedural/Alice.md | 4 +- docs/aerodromes/procedural/Broome.md | 4 +- docs/aerodromes/procedural/Coffs.md | 4 +- docs/aerodromes/procedural/Hammo.md | 4 +- docs/aerodromes/procedural/Karratha.md | 4 +- docs/aerodromes/procedural/Sunshinecoast.md | 6 +- docs/aerodromes/procedural/Tamworth.md | 4 +- docs/assets/headset.svg | 4 + docs/assist-us/best-practices.md | 6 +- docs/assist-us/setup.md | 2 +- docs/assist-us/tips.md | 2 +- docs/client/towerstrips.md | 4 +- docs/controller-skills/airwork.md | 40 ++--- docs/controller-skills/circuitoperations.md | 20 +-- docs/controller-skills/coordination.md | 22 +-- docs/controller-skills/lsalt.md | 8 +- docs/controller-skills/military.md | 6 +- docs/controller-skills/runwaymanagement.md | 8 +- docs/controller-skills/sequencing.md | 4 +- docs/enroute/Brisbane Centre/ARL.md | 18 +- docs/enroute/Brisbane Centre/INL.md | 18 +- docs/enroute/Brisbane Centre/ISA.md | 6 +- docs/enroute/Brisbane Centre/KEN.md | 6 +- docs/enroute/Brisbane Centre/TRT.md | 10 +- docs/enroute/Melbourne Centre/ASP.md | 8 +- docs/enroute/Melbourne Centre/BIK.md | 8 +- docs/enroute/Melbourne Centre/ELW.md | 6 +- docs/enroute/Melbourne Centre/HUO.md | 4 +- docs/enroute/Melbourne Centre/HYD.md | 163 ++++++++++++++++++ docs/enroute/Melbourne Centre/OLW.md | 6 +- docs/enroute/Melbourne Centre/PIY.md | 2 +- docs/enroute/Melbourne Centre/YWE.md | 2 +- docs/events/milkrun/aerodrome.md | 4 +- docs/events/milkrun/enroute.md | 6 +- docs/events/milkrun/terminal.md | 2 +- docs/events/milkrun/workload.md | 2 +- .../events/worldflight/Aerodromes/adelaide.md | 6 +- .../events/worldflight/Aerodromes/brisbane.md | 2 +- docs/events/worldflight/Aerodromes/darwin.md | 8 +- docs/events/worldflight/Aerodromes/perth.md | 10 +- .../worldflight/Aerodromes/portmoresby.md | 4 +- .../worldflight/Aerodromes/sydneyarr.md | 4 +- .../worldflight/Aerodromes/sydneydep.md | 14 +- docs/events/worldflight/Enroute/aypyybbn.md | 2 +- docs/events/worldflight/Enroute/ybbnyssy.md | 2 +- docs/events/worldflight/Enroute/ypadypph.md | 2 +- docs/events/worldflight/Enroute/ypphwiii.md | 4 +- docs/events/worldflight/Enroute/yssyypad.md | 2 +- .../worldflight/Terminal Areas/adelaide.md | 2 +- .../worldflight/Terminal Areas/brisbane.md | 4 +- .../worldflight/Terminal Areas/perth.md | 2 +- .../worldflight/Terminal Areas/sydneyarr.md | 4 +- docs/oceanic/Positions/IND.md | 4 +- docs/oceanic/Positions/TSN.md | 10 +- docs/oceanic/index.md | 2 +- docs/oceanic/procedures.md | 10 +- docs/pacific/New-Caledonia/Magenta.md | 4 +- docs/separation-standards/assurance.md | 10 +- docs/separation-standards/classd.md | 2 +- docs/separation-standards/procedural.md | 6 +- docs/separation-standards/visual.md | 2 +- docs/stylesheets/admonitions.css | 20 +++ docs/terminal/adelaide.md | 20 +-- docs/terminal/amberleyoakey.md | 10 +- docs/terminal/brisbane.md | 22 +-- docs/terminal/cairns.md | 10 +- docs/terminal/canberra.md | 8 +- docs/terminal/coral.md | 6 +- docs/terminal/curtin.md | 4 +- docs/terminal/darwin.md | 6 +- docs/terminal/eastsale.md | 8 +- docs/terminal/learmonth.md | 4 +- docs/terminal/melbourne.md | 36 ++-- docs/terminal/nowra.md | 6 +- docs/terminal/perth.md | 18 +- docs/terminal/scherger.md | 4 +- docs/terminal/sydney.md | 52 +++--- docs/terminal/tassie.md | 6 +- docs/terminal/townsville.md | 4 +- docs/terminal/williamtown.md | 6 +- 111 files changed, 609 insertions(+), 422 deletions(-) create mode 100644 docs/assets/headset.svg create mode 100644 docs/enroute/Melbourne Centre/HYD.md diff --git a/docs/aerodromes/classc/Adelaide.md b/docs/aerodromes/classc/Adelaide.md index 264ddf5cd..9bc00b2af 100644 --- a/docs/aerodromes/classc/Adelaide.md +++ b/docs/aerodromes/classc/Adelaide.md @@ -44,21 +44,21 @@ The TCU controller will coordinate these aircraft with ADC prior to issuing airw
Clearance Limits (red) and Approach/Departure Path (green)
-!!! example +!!! phraseology *CNY is a VFR Cessna 172 tracking coastal northbound, approaching PNL. They have contacted AD TCU for clearance.* **TCU** -> **ADC**: "South of PNL, CNY, for coastal northbound, 500ft, clearance limit BTJ" **ADC** -> **TCU**: "CNY" If a delay is expected at the clearance limit, instruct the aircraft to hold there. -!!! example +!!! phraseology **CNY:** "Adelaide Tower, CNY, maintaining not above 500ft" **AD ADC:** "CNY, Adelaide Tower, hold at the clearance limit, expect onwards clearance in 5 minutes due inbound traffic" **CNY:** "Hold at the clearance limit, CNY" Once the conflict is no longer a threat (or if no holding was required in the first place), cancel the clearance limit and issue onwards clearance tracking coastal north/southbound at the desired level. -!!! example +!!! phraseology **AD ADC:** "CNY, cancel clearance limit, track coastal offshore northbound, not above 500ft" **CNY:** "Cancel clearance limit, track coastal offshore northbound, not above 500ft, CNY" @@ -111,7 +111,7 @@ Shall be assigned the **Radar SID**. All other aircraft require a 'Next' call to AD TCU. -!!! example +!!! phraseology **AD ADC** -> **AD TCU**: "Next, RXA4362, Runway 23" **AD TCU** -> **AD ADC**: "RXA4362, Track Extended Centreline, Unrestricted" **AD ADC** -> **AD TCU**: "Track Extended Centreline, RXA4362" diff --git a/docs/aerodromes/classc/Amberley.md b/docs/aerodromes/classc/Amberley.md index 866dc9961..43abb533a 100644 --- a/docs/aerodromes/classc/Amberley.md +++ b/docs/aerodromes/classc/Amberley.md @@ -31,11 +31,11 @@ Visual Departures are commonly requested by high performance military jets and o Aircraft will depart the circuit visually and track overhead YAMB to begin tracking for their initial waypoint. -!!! example +!!! phraseology CRNG21 plans to enter R637 via the gate MOSSI for Military Training. **AMB ADC**: "CRNG21, cleared to YAMB via MOSSI, flight planned route. Runway 15, Northern 1 Departure. Climb to `F190`. Squawk 3601, Departure Frequency 126.20" -!!! example +!!! phraseology WOLF03 was assiged the BYRON7 departure with their initial clearance. **AMB ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff" **WOLF03**: "Make left turn, reach `F190` by COWIE, cleared for takeoff, WOLF03" @@ -77,7 +77,7 @@ The Circuit Area Airspace is allocated to be within 5nm of the YAMB ARP from `SF 'Next' coordination is required from AMB ADC to AMB TCU for all aircraft. -!!! example +!!! phraseology **AMB ADC** -> **AMB TCU**: "Next, ASY01, runway 33" **AMB TCU** -> **AMB ADC**: "ASY01, Assigned Heading Right 030, unrestricted" **AMB ADC** -> **AMB TCU**: "Assigned Heading Heading Right 030, ASY01" diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index 5b308dc3b..2d2989463 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -70,7 +70,7 @@ Winds must always be considered for Runway modes (Crosswind <20kts, Tailwind <5k When using the SODPROPS mode, pass traffic information to aircraft that are departing and landing at the same time -!!! example +!!! phraseology **BN ADC:** "ABC, Traffic is DEF, a 737, on short final for the opposite direction parallel runway. Runway 01R, Cleared for Takeoff" **ABC:** "Cleared for Takeoff Runway 01R, ABC" **BN ADC:** "DEF, Traffic is ABC, an A320, departing from the opposite direction parallel runway to the South-West. Runway 19R, Cleared to Land" @@ -134,7 +134,7 @@ The ATIS shall always have `EXP INST APCH` as the approach type. Visual Approach All other aircraft require a 'Next' call to BN TCU. -!!! example +!!! phraseology **BN ADC** -> **BN TCU**: "Next, QLK404D, Runway 19L" **BN TCU** -> **BN ADC**: "QLK404D, heading 160, unrestricted" **BN ADC** -> **BN TCU**: "Heading 160, QLK404D" diff --git a/docs/aerodromes/classc/Cairns.md b/docs/aerodromes/classc/Cairns.md index 4a2e5c615..462b70624 100644 --- a/docs/aerodromes/classc/Cairns.md +++ b/docs/aerodromes/classc/Cairns.md @@ -15,7 +15,7 @@ ## Airspace CS ADC is responsible for the Class C airspace within the CS CTR `SFC` to `A010`. -!!! important +!!! warning "Important" CS ADC is responsible for issuing visual approach clearances to some aircraft tracking for runway 33 in CTA, as well as initial airways clearances for VFR aircraft entering the CTR from class G. See [Runway 33 Arrival Procedures](#runway-33) for more information.
@@ -46,7 +46,7 @@ When visual approaches are in use, expect light & medium category aircraft (B737 ADC must assess any potential conflicts with aircraft in the CTR and clear the inbound aircraft for a visual approach when able. Given the limited airspace available, it is crucial that ADC maintains separation assurance between inbound aircraft and those operating in the CTR, to avoid a delay in issuing the visual approach clearance. -!!! example +!!! phraseology **TCU** -> **ADC**: "Via right base, RXA5418, will be assigned A020 visual" **ADC** -> **TCU**: "A020 visual, RXA5418" @@ -82,7 +82,7 @@ Prior to issuing clearance to these helicopters, ensure that no conflict exists Arriving helicopters should be cleared direct to The Pier, not above `A005` and instructed to report on the ground. -!!! example +!!! phraseology *YZM is a VFR R44 tracking from Upolo Cay to False Cape, inbound to The Pier.* **VH-YZM**: "Cairns Tower, helicopter YZM, 5nm northeast of False Cape, A005, for The Pier, received Hotel" **CS ADC**: "YZM, Cairns Tower, cleared direct to The Pier, not above A005, report on the ground" @@ -93,7 +93,7 @@ Arriving helicopters should be cleared direct to The Pier, not above `A005` and Departing helicopters should be cleared direct to their nominated tracking point not above `A005`, and instructed to report airborne. -!!! example +!!! phraseology *VTB is a VFR Bell 505 on The Pier, intending to track to Cairns Airport for a landing on the southern pads. A 737 is about to depart from runway 15.* **VH-VTB**: "Cairns Tower, helicopter VTB, at The Pier, for the southern pads, received India" **CS ADC**: "VTB, Cairns Tower, short delay for clearance" @@ -112,20 +112,20 @@ Departing helicopters should be cleared direct to their nominated tracking point ### Western VFR Corridor The Western VFR Corridor conflicts with the extended centreline to the north of the aerodrome. Clearances for aircraft entering the CTR must use clear and unambiguous phraseology to eliminate any potential for confusion by the pilot. -!!! Example +!!! phraseology **NDR**: "Cairns Tower, NDR, EDT, A015, for the Western VFR Corridor, Request Clearance" **CS ADC**: "NDR, enter the CTR tracking via the Western VFR corridor at A015. Remain on the corridor until advised." If a clearance limit is associated with the clearance, then it must be reiterated to the pilot to remain “on or west of the VFR Corridor”. -!!! Example +!!! phraseology **NDR**: "Cairns Tower, NDR, EDT, A015, for the Western VFR Corridor, Request Clearance" **CS ADC**: "NDR, enter the CTR tracking via the Western VFR Corridor at A015. Clearance limit is ADI, Remain on or west of the Western VFR Corridor at all times." ### Inbound Aircraft planning to enter the CS CTR between *Mt Gorton*, CGF and Upolo Cay at `A005`, must contact CS ADC for airways clearance. -!!! Example +!!! phraseology **NDR**: "Cairns Tower, NDR, Cape Grafton, A005, Inbound, Information Alpha, Request Clearance" **CS ADC**: "NDR, enter the CTR tracking for a Right Base runway 33, maintain A005." @@ -164,7 +164,7 @@ Taxiways A2 and A between A2 and A3 are not available to aircraft above 7,000 ki All other aircraft require a 'Next' call to CS TCU. -!!! example +!!! phraseology **CS ADC** -> **CS TCU**: "Next, HND151" **CS TCU** -> **CS ADC**: "HND151, Heading 030, unrestricted" **CS ADC** -> **CS TCU**: "Heading 030, HND151" @@ -182,7 +182,7 @@ The controller assuming responsibility of **CS ACD** shall give heads-up coordin a) VFR Departures b) Aircraft using a runway not on the ATIS -!!! example +!!! phraseology **CS ACD** -> **CS TCU**: "ABC, Requesting clearance for a Northbound VFR Coastal departure at A035" **CS TCU** -> **CS ACD**: "ABC, Cleared for a Northbound VFR Coastal departure, A035" **CS ACD** -> **CS TCU**: "Cleared for a Northbound VFR Coastal departure, A035, ABC" diff --git a/docs/aerodromes/classc/Canberra.md b/docs/aerodromes/classc/Canberra.md index ffe577e21..87d7bc21e 100644 --- a/docs/aerodromes/classc/Canberra.md +++ b/docs/aerodromes/classc/Canberra.md @@ -39,7 +39,7 @@ VFR aircraft that will operate only in ADCs airspace shall be assigned SSR code Aircraft operating in the circuit area are to remain on the ADC frequency. The phrasing of the airways clearance is: -!!! example +!!! phraseology “ABC, cleared to operate in the circuit area, not above A030, squawk 0040”. The circuit direction is not specified in the airways clearance, but with a take-off or touch-and-go clearance. @@ -67,13 +67,13 @@ Helicopters departing the pads require an airways clearance to do so, either tak Departing aircraft should **not** be issued a takeoff clearance (as the helipads are outside the manoeuvring area). Instead, instruct aircraft to 'report airborne'. -!!! example +!!! phraseology *RSCU201 is a VFR AW139 helicopter intending to depart Southcare Base (YXSB) to the northwest at `A035` (below the base of the Class C steps).* **RSCU201**: "Canberra Tower, helicopter RSCU201, Southcase Base, for departure to the northwest, A035, received Juliet, ready" **CB ADC**: "RSCU201, Canberra Tower, transit approved not above A035, report OCTA" **RSCU201**: "Transit approved, not above A035, RSCU201" -!!! example +!!! phraseology *RSCU209 is an IFR AW139 helicopter intending to depart Canberra Hospital (YXCB) for Bankstown (YSBK) at `A090` (inside Class C CTA).* **RSCU209**: "Canberra Tower, helicopter RSCU209, on the pad at Canberra Hospital, for Bankstown, received Juliet, ready" **CB ADC**: "RSCU209, Canberra Tower, report sighting a Jetstar A320 on a 3nm final runway 35 and advise able to maintain own separation with that aircraft" @@ -87,7 +87,7 @@ Departing aircraft should **not** be issued a takeoff clearance (as the helipads #### Arriving Aircraft Helicopters arriving to the pads will generally be coordinated by the TMA controller and should be cleared via a visual approach (when available) and instructed to report on the ground. Do **not** issue a landing clearance to these aircraft (as the helipads are outside the manoeuvring area). It may be necessary to instruct these helicopters to track via amended visual points or sight and pass other aircraft. -!!! example +!!! phraseology **RSCU203**: "Canberra Tower, gday, RSCU203" **CB ADC**: "RSCU203, Canberra Tower, report sighting a Qantas 737 lining up on runway 17 and advise able to maintain own separation with that aircraft" **RSCU203**: "Traffic sighted and affirm, RSCU203" @@ -106,7 +106,7 @@ Helicopters arriving to the pads will generally be coordinated by the TMA contro All other aircraft require a 'Next' call to CB TCU. -!!! example +!!! phraseology **CB ADC** -> **CB TCU**: "Next, XEB, runway 35" **CB TCU** -> **CB ADC**: "XEB, heading 010, Unrestricted" **CB ADC** -> **CB TCU**: "Heading 010, XEB" diff --git a/docs/aerodromes/classc/Curtin.md b/docs/aerodromes/classc/Curtin.md index 09c244d58..dcb91159f 100644 --- a/docs/aerodromes/classc/Curtin.md +++ b/docs/aerodromes/classc/Curtin.md @@ -27,7 +27,7 @@ CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`. ### CIN TCU 'Next' coordination is required from CIN ADC to CIN TCU for all aircraft. -!!! example +!!! phraseology **CIN ADC** -> **CIN TCU**: "Next, ASY404, runway 29" **CIN TCU** -> **CIN ADC**: "ASY404, unrestricted" **CIN ADC** -> **CIN TCU**: "ASY404" diff --git a/docs/aerodromes/classc/Darwin.md b/docs/aerodromes/classc/Darwin.md index e73aa3e2d..0e31e4057 100644 --- a/docs/aerodromes/classc/Darwin.md +++ b/docs/aerodromes/classc/Darwin.md @@ -88,7 +88,7 @@ Assign VFR routes in accordance with the following radial chart: ### DN TCU Auto-Release is **not available** at YPDN. All Departures will be coordinated when ready for departure. -!!! example +!!! phraseology **DN ADC** -> **DN TCU**: "Next, EOC, runway 18" **DN TCU** -> **DN ADC**: "EOC, Track Extended Centreline, unrestricted" **DN ADC** -> **DN TCU**: "Track Extended Centreline, EOC" diff --git a/docs/aerodromes/classc/EastSale.md b/docs/aerodromes/classc/EastSale.md index a25ab2b2c..92cb15965 100644 --- a/docs/aerodromes/classc/EastSale.md +++ b/docs/aerodromes/classc/EastSale.md @@ -127,7 +127,7 @@ Lanes are defined by GNSS waypoints situated at 12, 35, and 50 NM from YMES AD. Aircraft departing ESL military airspace may be instructed to track via a lane at or below `F160`. -!!! example +!!! phraseology **BRCT21** is departing East Sale via the Eastern Lane at FL110 to Orbost (YORB). The departure clearance would be issued as follows: **ES SMC** -> **BRCT21**: "BRCT21 CLEARED TO YORB, VIA EASTERN LANE, FPR, FL110, SQUAWK 1234, DEPARTURES 123.3" @@ -142,14 +142,14 @@ Aircraft departing ESL military airspace may be instructed to track via a lane a ### Auto Release Auto release is not utilised at East Sale. 'Next' coordination is required from ES ADC to ES TCU for all aircraft. -!!! example +!!! phraseology **ES ADC** -> **ES TCU**: "Next, ASY01, runway 09" **ES TCU** -> **ES ADC**: "ASY01, Assigned Heading Left 030, unrestricted" **ES ADC** -> **ES TCU**: "Left Heading 030, ASY01" Helicopters departing from helicopter spots will be treated as if departing from the duty runway. -!!! example +!!! phraseology *PSDN14 is a VFR helicopter departing from the threshold of RWY04 (in the direction of runway 27)* **ES ADC** -> **ES TCU**: "Next, PSDN14, runway 27" **ES TCU** -> **ES ADC**: "PSDN14, right turn, unrestricted" diff --git a/docs/aerodromes/classc/Essendon.md b/docs/aerodromes/classc/Essendon.md index 447ce4ea4..8fb44d956 100644 --- a/docs/aerodromes/classc/Essendon.md +++ b/docs/aerodromes/classc/Essendon.md @@ -92,7 +92,7 @@ EN ADC is responsible for facilitating aircraft requesting city orbits. They sha `A015` by day `A022` by night -!!! example +!!! phraseology **EOG**: "Essendon Tower, EOG, approaching WMS, A015, Requesting 1 left-hand city orbit, in receipt of L" **EN ADC**: "EOG, Essendon Tower, cleared 1 left-hand city orbit A015" **EOG**: "Cleared 1 left-hand city orbit A015, EOG" @@ -113,7 +113,7 @@ Essendon departures that will not enter ML TCU Class C airspace are not required All aircraft departing into Class C must be coordinated to ML TCU with a "Next" Call -!!! example +!!! phraseology **EN ADC** -> **ML TCU**: "Next, FD318" **ML TCU** -> **EN ADC**: "FD318, heading 330, unrestricted" **EN ADC** -> **ML TCU**: "Heading 330, FD318" @@ -125,7 +125,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from Class C to EN ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to EN ADC, unless EN ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **ML TCU** -> **EN ADC**: "via KAO, KHU" **EN ADC** -> **ML TCU**: "KHU, A015" @@ -140,7 +140,7 @@ Any Runway change must be prior coordinated to **ML TCU** ### ML ADC EN ADC is responsible for separation with all YMML traffic, and must coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with the 09/27 or 16/34 Extended Centrelines at YMML. -!!! example +!!! phraseology **EN ADC** -> **ML ADC**: "Boundary Ident, OXG, Published Missed Approach from the ILS 26" **ML ADC** -> **EN ADC**: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation" **EN ADC** -> **ML ADC**: "My separation with QFA451, OXG" \ No newline at end of file diff --git a/docs/aerodromes/classc/Goldy.md b/docs/aerodromes/classc/Goldy.md index 12b9906b7..ca93e35b9 100644 --- a/docs/aerodromes/classc/Goldy.md +++ b/docs/aerodromes/classc/Goldy.md @@ -88,7 +88,7 @@ Circuits from the Western Grass are to be made in the same direction as the duty All other aircraft require a 'Next' call to CG TCU. -!!! example +!!! phraseology **CG ADC** -> **BAC**: "Next, CBN, runway 14" **BAC** -> **CG ADC**: "CBN, heading 030, unrestricted" **CG ADC** -> **BAC**: "Heading 030, CBN" diff --git a/docs/aerodromes/classc/Learmonth.md b/docs/aerodromes/classc/Learmonth.md index 04bb5aeef..2493037af 100644 --- a/docs/aerodromes/classc/Learmonth.md +++ b/docs/aerodromes/classc/Learmonth.md @@ -26,7 +26,7 @@ LM ADC owns the Class C airspace within the LM CTR from `SFC` to `A015`. ### LM TCU 'Next' coordination is required from LM ADC to LM TCU for all aircraft. -!!! example +!!! phraseology **LM ADC** -> **LM TCU**: "Next, QFA1601, runway 36" **LM TCU** -> **LM ADC**: "QFA1601, Right heading 060 Visual, unrestricted" **LM ADC** -> **LM TCU**: "Right heading 060 Visual, QFA1601" diff --git a/docs/aerodromes/classc/Melbourne.md b/docs/aerodromes/classc/Melbourne.md index f46020832..08ee61479 100644 --- a/docs/aerodromes/classc/Melbourne.md +++ b/docs/aerodromes/classc/Melbourne.md @@ -32,7 +32,7 @@ If winds are too great, single runway operations may be necessary (eg, Runway 16 | 16A/27D | 16 | 27 | | 09A/16D | 09 | 16 | -!!! information +!!! info When utilising the 27AD/34D runway mode, Heavy Aircraft may require Runway 34 for departure due to the shorter length of Runway 27. Assigning Runway 34 to aircraft from the southern apron can also improve aerodrome efficiency due to the reduced taxi distance. !!! note @@ -45,7 +45,7 @@ Jet Aircraft planned via **MNG**, **NONIX**, **DOSEL**, **CORRS**, **KEPPA**, ** Jet Aircraft planned via DOSEL, assigned runway 27, shall be given the DOSEL SID. #### Off Mode Departures -!!! definition +!!! info "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. For jet aircraft departing Runway 16 **Off Mode** via **MNG**, **NONIX**, **DOSEL**, **KEPPA**, **NEVIS**, or **ESDIG**, the **ISPEG SID** must be assigned. **Off Mode** departures to the south-east shall be assigned the relevant **Procedural SID**. @@ -107,20 +107,20 @@ Day VFR Helicopters may request clearance via the **Sunbury Corridor**. It is de Boundary Coordination must be completed to ML TCU for clearances in this airspace -!!! example +!!! phraseology **ML ADC** -> **ML TCU**: "For Ident, HM3, Sunbury Corridor, not above A020" **ML TCU** -> **ML ADC**: "HM3, No Restrictions" Due to the close proximity of the airspace to the arrival and departure paths at YMML, controllers should be aware of surrounding traffic before issuing a clearance to helicopters. -!!! example +!!! phraseology **HM3:** "Melbourne Tower, HM3, approaching SWT, A020, for YMEN via the Sunbury Corridor, request clearance" **ML ADC:** "HM3, cleared to YMEN, track Sunbury Corridor, not above A020" **HM3:** "Cleared to YMEN, track Sunbury Corridor, not above A020, HM3" If necessary, consider issuing a clearance limit for separation or instruct helicopters to report sighting and to maintain own separation with other aircraft. Alternatively, tower controllers can simulate visual separation provided no risk of collision exists and both aircraft remain in sight of the controller at all times. -!!! example +!!! phraseology **ML ADC:** "HM3, report sighting a Jetstar A320, 4nm final runway 16" **HM3:** "Traffic sighted, HM3" **ML ADC:** "HM3, pass behind that aircraft, maintain own separation, caution wake turbulence" @@ -128,7 +128,7 @@ If necessary, consider issuing a clearance limit for separation or instruct heli Remember to pass traffic information to both aircraft. -!!! example +!!! phraseology **ML ADC:** "JST515, traffic is a helicopter, 2nm northwest of the field, tracking for Essendon and maintaining own separation with you, runway 16, cleared to land" **JST515:** "Runway 16, cleared to land, JST515" @@ -144,7 +144,7 @@ To commence the procedure: 2. **SMC** coordinates with **ADC** in order to have the [ATIS](#acd-pushback-requests) updated. 3. **ACD** places the `MONITOR GROUND` bar in the **Cleared Bay** in [OzStrips](../../client/towerstrips.md#coordinator). -!!! example +!!! phraseology **ML SMC** -> **ML ACD**: "It's getting quite busy. Happy to implement Pushback requests on your frequency?" **ML ACD** -> **ML SMC**: "Understood, affirm" **ML SMC** -> **ML ACD**: "Thanks, I'll talk to Tower" @@ -162,10 +162,10 @@ To operate with pushback requests on ACD: The decision whether or not to send an aircraft to SMC or hold them on the ACD frequency should be made in accordance with the [Queue Management](#queue-management) techniques. -!!! important +!!! warning "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 +!!! phraseology **VOZ543:** "Melbourne Delivery, VOZ543, PDC read back" **ML ACD:** "VOZ543, go ahead the read back" **VOZ543:** "DOSEL1 departure, squawk 1336, bay E8, VOZ543" @@ -183,7 +183,7 @@ If a delay is required prior to transferring an aircraft to SMC, provide an esti !!! tip Remember that the **bottom** aircraft represents the **front** of the queue. -!!! example +!!! phraseology **VOZ543:** "Melbourne Delivery, VOZ543, bay E8, request pushback" **ML ACD:** "VOZ543, estimated delay 10 minutes, remain this frequency." @@ -197,7 +197,7 @@ To reduce SMC workload, ACD should not allow more than **three** aircraft to be When SMC moves an aircraft from below the **Monitor Ground** bar to the **Pushback Bay**, ACD should instruct the next aircraft in line to monitor the SMC frequency (and move the strip appropriately). -!!! important +!!! warning "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 @@ -210,7 +210,7 @@ During busy events, VATPAC may utilise prebooked slots to manage traffic congest ## Coordination ### Auto Release -!!! important +!!! warning "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: @@ -229,7 +229,7 @@ During busy events, VATPAC may utilise prebooked slots to manage traffic congest All other aircraft require a 'Next' call to ML TCU. -!!! example +!!! phraseology **ML ADC** -> **ML TCU**: "Next, JIA, runway 34" **ML TCU** -> **ML ADC**: "JIA, Track Extended Centreline, Unrestricted" **ML ADC** -> **ML TCU**: "Track Extended Centreline, JIA" @@ -266,7 +266,7 @@ Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace ### EN ADC EN ADC is responsible for separation with all YMML traffic, and will coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with YMML traffic. -!!! example +!!! phraseology **EN ADC** -> **ML ADC**: "Boundary Ident, OXG, Published Missed Approach from the ILS 26" **ML ADC** -> **EN ADC**: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation" **EN ADC** -> **ML ADC**: "My separation with QFA451, OXG" \ No newline at end of file diff --git a/docs/aerodromes/classc/Nowra.md b/docs/aerodromes/classc/Nowra.md index 075562432..b09e2b150 100644 --- a/docs/aerodromes/classc/Nowra.md +++ b/docs/aerodromes/classc/Nowra.md @@ -70,7 +70,7 @@ The following pre-defined helicopter spots can be used for this purpose. These s | Runway 03 | Spot 6 (B3), Spot 5 (B3) | Spot 4 (B4), Spot 3 (B4) | | Runway 21 | Spot 4 (B4), Spot 3 (B4) | Spot 6 (B3), Spot 5 (B3) | -!!! example +!!! phraseology **NW ADC**: "TAIP52, spot 2, cleared to land" **TAIP52**: "Spot 2, cleared to land, TAIP52" @@ -81,14 +81,14 @@ Aerodrome and instrument approach charts are available in the AIP, or otherwise ### Auto Release Auto release is not utilised at Nowra. 'Next' coordination is required from NW ADC to NW TCU for all aircraft. -!!! example +!!! phraseology **NW ADC** -> **NW TCU**: "Next, ASY01, runway 08" **NW TCU** -> **NW ADC**: "ASY01, Assigned Heading Left 030, unrestricted" **NW ADC** -> **NW TCU**: "Assigned Heading Heading Left 030, ASY01" Helicopters departing from helicopter spots will be treated as if departing from the duty runway. -!!! example +!!! phraseology *PSDN14 is a VFR helicopter departing from spot 2 (in the direction of runway 08)* **NW ADC** -> **NW TCU**: "Next, PSDN14, runway 08" **NW TCU** -> **NW ADC**: "PSDN14, right turn, unrestricted" diff --git a/docs/aerodromes/classc/Oakey.md b/docs/aerodromes/classc/Oakey.md index 33cabcf26..f2ad68473 100644 --- a/docs/aerodromes/classc/Oakey.md +++ b/docs/aerodromes/classc/Oakey.md @@ -40,7 +40,7 @@ The standard circuit direction is to the north of the field. ### OK TCU 'Next' coordination is required from OK ADC to OK TCU for all aircraft not remaining in the circuit. -!!! example +!!! phraseology **OK ADC** -> **OK TCU**: "Next, MRCH01, runway 32" **OK TCU** -> **OK ADC**: "MRCH01, Make Right Turn, unrestricted" **OK ADC** -> **OK TCU**: "Make Right Turn, MRCH01" diff --git a/docs/aerodromes/classc/Perth.md b/docs/aerodromes/classc/Perth.md index 54dff2982..edc279288 100644 --- a/docs/aerodromes/classc/Perth.md +++ b/docs/aerodromes/classc/Perth.md @@ -54,7 +54,7 @@ All circuits are to be conducted to the east of Runway 03/21 (right-hand circuit ## Helicopter Operations There are no helipad facilities at YPPH. Helicopters should be issued an airways clearance in accordance with the fixed-wing operation applicable to their flight rules (i.e. SID for IFR helicopters, VFR departure via appropriate VFR route if necessary for VFR helicopters). Helicopters should be cleared to takeoff/land from runways or taxiways, as deemed appropriate by ADC. The point of takeoff/landing must be specified by ADC. -!!! example +!!! phraseology **PH ADC:** "YOE, taxiway Romeo, cleared to land" **PH ADC:** "HWD, runway 21, cleared for takeoff" @@ -71,7 +71,7 @@ When traffic permits, VFR scenic flights over Perth are cleared via VICTOR 65 ro All other aircraft require a 'Next' call to PH TCU. -!!! example +!!! phraseology **PH ADC** -> **PH TCU**: "Next, ABC, runway 03" **PH TCU** -> **PH ADC**: "ABC, Heading 010, unrestricted" **PH ADC** -> **PH TCU**: "Heading 010, ABC" @@ -91,7 +91,7 @@ The controller assuming responsibility of ACD shall give heads-up coordination t a) VFR Departures b) Aircraft using a runway not on the ATIS -!!! example +!!! phraseology **ABC**: "Perth Delivery, ABC, request Victor 65" **PH ACD**: "ABC, Perth Delivery, standby" diff --git a/docs/aerodromes/classc/Scherger.md b/docs/aerodromes/classc/Scherger.md index ac71c26f7..c81dde374 100644 --- a/docs/aerodromes/classc/Scherger.md +++ b/docs/aerodromes/classc/Scherger.md @@ -25,7 +25,7 @@ SG ADC owns the Class C airspace within the SG CTR from `SFC` to `A015`. ### SG TCU 'Next' coordination is required from SG ADC to SG TCU for all aircraft. -!!! example +!!! phraseology **SG ADC** -> **SG TCU**: "Next, ASY219, runway 30" **SG TCU** -> **SG ADC**: "ASY219, unrestricted" **SG ADC** -> **SG TCU**: "ASY219" diff --git a/docs/aerodromes/classc/Sydney.md b/docs/aerodromes/classc/Sydney.md index b351362d6..541905377 100644 --- a/docs/aerodromes/classc/Sydney.md +++ b/docs/aerodromes/classc/Sydney.md @@ -36,19 +36,19 @@ SY ACD will issue airways clearance for a Helicopter Route through a coded clear !!! tip You can find details of each Helicopter Route (including applicable clearance limits) in the `ERSA FAC YSSY`. -!!! example +!!! phraseology **YOE:** "Sydney Delivery, helicopter YOE, for the Harbour Bridge 5 outbound, request clearance" **SY ACD:** "YOE, Delivery, cleared Harbour Bridge 5 outbound, squawk 0215, departure frequency 123.0" **YOE:** "Cleared Harbour Bridge 5 outbound, squawk 0215, departure frequency 123.0, YOE" Most helicopters will be capable of departing from their company helipad. If reposition is required to Helipad 1 (the primary helipad), this must be approved by **SY ADC**. -!!! example +!!! phraseology **YOE:** "Sydney Tower, helicopter YOE, Hotel 7, request reposition Hotel 1" **SY ADC:** "YOE, reposition approved" **YOE:** "Reposition approved, YOE" Helipad 1 is controlled by **SY ADC** and treated like a runway (takeoff clearances required). All other pads are outside Tower's jurisdiction and do not require a takeoff/landing clearance, however, approval must still be sought for helicopters to become airborne in the SY CTR. This approval is communicated in the form of a requirement to *'report airborne'*. -!!! example +!!! phraseology **HWD:** "Sydney Tower, helicopter HWD, Hotel 7, for the Harbour Bridge 5 outbound, ready" **SY ADC:** "HWD, Sydney Tower, report airborne" **HWD:** "HWD" @@ -58,7 +58,7 @@ Helipad 1 is controlled by **SY ADC** and treated like a runway (takeoff clearan **HWD:** "Departures, HWD" Helicopter operations should be accommodated without unduly delaying fixed wing traffic to/from the aerodrome. Where possible, visually separate helicopters and fixed wing aircraft, and when necessary, delegate responsibility for separation to the helicopter. -!!! example +!!! phraseology **SY ADC:** "HSZ, traffic is a 737 shortly rolling on runway 34R, report in sight" **HSZ:** "Traffic sighted, HSZ" **SY ADC:** "HSZ, maintain own separation, caution wake turbulence, report airborne" @@ -69,7 +69,7 @@ VFR helicopters are generally processed via by one of Sydney's Helicopter Routes SY TCU will clear helicopters for all inbound Helicopter Routes, with the exception of the `CAPE BANKS 5 INBOUND` and `WANDA 5 INBOUND`. Tower controllers should assess the current traffic situation and issue clearances for these aircraft when available. Each procedure is delivered as a coded clearance, which includes automatic altitude assignment, tracking, and a clearance limit designed to separate helicopters from fixed-wing aircraft. -!!! example +!!! phraseology **YZD:** "Sydney Tower, helicopter YZD, JIBN, A005, received Tango, request Cape Banks 5 Inbound" **SY ADC:** "YZD, Sydney Tower, cleared Cape Banks 5 Inbound, report at the Container Terminal" **YZD:** "Cleared Cape Banks 5 Inbound, YZD" @@ -82,7 +82,7 @@ SY TCU will clear helicopters for all inbound Helicopter Routes, with the except You can find details of each Helicopter Route (including applicable clearance limits) in the `YSSY ERSA FAC`. During times of peak fixed wing traffic, instruct helicopters to hold at their designated clearance limit on their Helicopter Route and maintain own separation on approach to the heliport. -!!! example +!!! phraseology **SY ADC:** "YOE, hold at the clearance limit, traffic is a 717 on a 4nm final to runway 25, report in sight" **YOE:** "Hold at the clearance limit, traffic sighted, YOE" **SY ADC:** "YOE, pass behind that aircraft, maintain own separation, caution wake turbulence, cleared visual approach, report on the ground" @@ -124,7 +124,7 @@ When both ADC and SMC are online, SMC shall issue aircraft departing on runway 1 | Runway 16L | Holding point `B10` | | Runway 34R | Taxiway `S` | -!!! example +!!! phraseology **SY SMC:** "VOZ853, taxi Charlie, cross runway 25, hold short Sierra" **VOZ853:** "Taxi Charlie, cross runway 25, hold short Sierra, VOZ853" @@ -133,13 +133,13 @@ When both ADC and SMC are online, SMC shall issue aircraft departing on runway 1 Aircraft landing on runway 16L/34R are expected to vacate the runway and taxi via the standard taxi routes to join taxiway Lima. If pilots are unfamiliar with local procedures, they should be instructed by **ADC** to taxi accordingly. Where possible, outbound aircraft should give way to inbound aircraft to avoid creating congestion at the runway exits. -!!! example +!!! phraseology **SY ADC**: "JAL52, taxi Tango, Lima, on Lima contact Ground 121.7" ### Transferring Between SMCs When both SMC positions are online and an aircraft is to be passed from one to the other (e.g. an aircraft taxis from the domestic terminal for runway 34L), they should be instructed to hold short of runway 16R/34L and to contact the next SMC frequency. -!!! example +!!! phraseology **SMC East**: "JST412, cross runway 25, taxi Lima, hold short runway 34L, on Lima contact ground 126.5" **JST412**: "Cross runway 25, taxi Lima, hold short runway 34L, contact ground 126.5, JST412" @@ -182,7 +182,7 @@ Winds must always be considered for Runway modes (Crosswind <20kts, Tailwind <5k ### SODPROPS When using the SODPROPS mode, pass traffic information to aircraft that are departing and landing at the same time. -!!! example +!!! phraseology **SY ADC:** "JST521, traffic is a 737 on a 3nm final for the opposite direction parallel runway, runway 16L, cleared for takeoff" **JST521:** "Runway 16L, cleared for takeoff, JST521" **SY ADC:** "VOZ954, traffic is an A320 departing from the opposite direction parallel runway to the southeast, runway 34L, cleared to land" @@ -284,7 +284,7 @@ Climb Gradient Requirements apply to all Procedural SIDs. It is the pilot's resp | Between 2000FT & 3000FT| >5000M | `EXP INSTR APCH THEN INDEP VISUAL APCH WHEN VISUAL`| | Below 2000FT **or** | <5000M | `EXP INSTR APCH` | -!!! Important +!!! warning "Important" Independent Visual Approaches (IVAs) may only be run during Parallel Runway Operations (PROPS). During single runway operations, regular visual approaches (blank ATIS 'APCH' field) should be used instead. When Independent Visual Approaches are run during PROPS, the APCH field must also include `DO NOT PASS THRU ASSIGNED RWY CL`. @@ -314,7 +314,7 @@ When [Coordinator](#sydney-coordinator) is online and start approval is required ## Sydney Coordinator 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 +!!! warning "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 @@ -339,10 +339,10 @@ The decision whether or not to send an aircraft to SMC or hold them on the Coord !!! tip Remember that the **bottom** aircraft represents the **front** of the queue. -!!! important +!!! warning "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 +!!! phraseology **VOZ543:** "Sydney Delivery, VOZ543, PDC read back" **SY ACD:** "VOZ543, go ahead the read back" **VOZ543:** "Runway 34R, OLSEM1 departure, squawk 1336, bay 33, VOZ543" @@ -358,7 +358,7 @@ The decision whether or not to send an aircraft to SMC or hold them on the Coord 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 +!!! phraseology **VOZ543:** "Sydney Coordinator, VOZ543, bay 33, request pushback" **SY COORD:** "VOZ543, estimated delay 10 minutes, remain this frequency." @@ -372,7 +372,7 @@ To reduce SMC workload, ACD should not allow more than **three** aircraft to be When SMC moves an aircraft from below the **Monitor Ground** bar to the **Pushback Bay**, Coordinator should instruct the next aircraft in line to monitor the SMC frequency (and move the strip appropriately). -!!! important +!!! warning "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 @@ -390,7 +390,7 @@ During busy events, VATPAC may utilise prebooked slots to manage traffic congest ## Coordination ### Auto Release -!!! important +!!! warning "Important" YSSY utilises auto release for all **Procedural** SIDs (except **ABBEY** SID during SODPROPS), and the **SY (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: @@ -408,7 +408,7 @@ All other aircraft require a 'Next' call to SY TCU. d) Jets departing 16L via WOL e) All aircraft during the Curfew Runway Mode -!!! example +!!! phraseology **SY ADC** -> **SY TCU**: "Next, MHQ, Runway 34R" **SY TCU** -> **SY ADC**: "MHQ, heading 030, unrestricted" **SY ADC** -> **SY TCU**: "Heading 030, MHQ" @@ -449,7 +449,7 @@ The controller assuming responsibility of **SY ACD** shall give heads-up coordin a) VFR Departures b) Aircraft using a runway not on the ATIS -!!! example +!!! phraseology **TEK:** "Sydney Delivery, TEK, for YSHL via CUL, A025, request clearance" **SY ACD:** "TEK, Sydney Delivery, standby" diff --git a/docs/aerodromes/classc/Townsville.md b/docs/aerodromes/classc/Townsville.md index 2701c108a..acc1330ae 100644 --- a/docs/aerodromes/classc/Townsville.md +++ b/docs/aerodromes/classc/Townsville.md @@ -55,7 +55,7 @@ a) Departing from a runway nominated in the ATIS; and b) Assigned the standard assignable level; c) Assigned a **Procedural** SID -!!! example +!!! phraseology **TL ADC** -> **TL TCU**: "Next, DNGO05, runway 19" **TL TCU** -> **TL ADC**: "DNGO05, Assigned Heading Left 150, unrestricted" **TL ADC** -> **TL TCU**: "Assigned Heading Left 150, DNGO05" diff --git a/docs/aerodromes/classc/Williamtown.md b/docs/aerodromes/classc/Williamtown.md index 47c728516..7f4bc6f02 100644 --- a/docs/aerodromes/classc/Williamtown.md +++ b/docs/aerodromes/classc/Williamtown.md @@ -32,7 +32,7 @@ a) Departing from a runway nominated in the ATIS; and b) Assigned the standard assignable level; c) Assigned a **Procedural** SID -!!! example +!!! phraseology **WLM ADC** -> **WLM TCU**: "Next, MVP" **WLM TCU** -> **WLM ADC**: "MVP, Left Heading 010, Unrestricted" **WLM ADC** -> **WLM TCU**: "Left Heading 010, MVP" @@ -42,6 +42,6 @@ The Standard Assignable level from WLM ADC to WLM TCU is the lower of `F120` or ### Arrivals/Overfliers Voiceless coordination is in place from WLM TCU to WLM ADC for arrivals cleared for an approach on to a runway nominated on the ATIS. All other aircraft and all overfliers must be heads-up coordinated as soon as practical. -!!! example +!!! phraseology **WLM TCU** -> **WLM ADC**: "via WLM, ZULU, Close formation of 5, do you have any restrictions or requirements?” **WLM ADC** -> **WLM TCU**: "ZULU, no restrictions or requirements, A040" \ No newline at end of file diff --git a/docs/aerodromes/classd/Archerfield.md b/docs/aerodromes/classd/Archerfield.md index 7d320df61..5d2ebd7cd 100644 --- a/docs/aerodromes/classd/Archerfield.md +++ b/docs/aerodromes/classd/Archerfield.md @@ -48,7 +48,7 @@ VFR departures will depart the control zone at `A010`. Aircraft should advise planned Departure Procedure to **AF SMC** with TAXI call and **AF ADC** with READY call. -!!! example +!!! phraseology **VPF:** "Archer Ground, Cherokee VPF is on the Main Apron, solo, Western Departure, received information Alpha, request taxi" **VPF:** "Archer Tower, Cherokee VPF is B8, runway 10 Left for Western Departure, ready" @@ -91,7 +91,7 @@ The APCH field should include `EXP INST APCH` when: ### Departures When aircraft planned via a CTA departure are ready for takeoff and expected to depart imminently, **AF ADC** shall seek release of the aircraft through a 'Next' call. -!!! example +!!! phraseology **AF ADC** -> **BN TCU**: "Next, XMM, Runway 10L" **BN TCU** -> **AF ADC**: "XMM, Unrestricted" **AF ADC** -> **BN TCU**: "XMM" @@ -104,7 +104,7 @@ IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) VFR aircraft require a level readback. -!!! example +!!! phraseology **BN TCU** -> **AF ADC**: "via TVT for the visual approach, UJE" **AF ADC** -> **BN TCU**: "UJE, visual approach" diff --git a/docs/aerodromes/classd/Avalon.md b/docs/aerodromes/classd/Avalon.md index e04842ff1..0154ca52f 100644 --- a/docs/aerodromes/classd/Avalon.md +++ b/docs/aerodromes/classd/Avalon.md @@ -47,7 +47,7 @@ All other IFR aircraft shall be assigned the **Radar SID**. All other aircraft require a 'Next' call to ML TCU. -!!! example +!!! phraseology **AV ADC** -> **MDS**: "Next, UJI, Runway 18" **MDS** -> **AV ADC**: "UJI, heading 030, unrestricted" **AV ADC** -> **MDS**: "Heading 030, UJI" @@ -59,7 +59,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from CTA to AV ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to AV ADC, unless AV ADC nominates a restriction. VFR aircraft will not be coordinated, and will need to receive their airways clearance from AV ADC. -!!! example +!!! phraseology **MDS** -> **AV ADC**: "via TEMPL for the ILS-Y 18, JST631" **AV ADC** -> **MDS**: "JST631, ILS-Y 18" diff --git a/docs/aerodromes/classd/Bankstown.md b/docs/aerodromes/classd/Bankstown.md index d6fa96141..0dfeed2db 100644 --- a/docs/aerodromes/classd/Bankstown.md +++ b/docs/aerodromes/classd/Bankstown.md @@ -89,7 +89,7 @@ Helicopters should track outbound via one of the helicopter reporting points at Helicopters shall report ready to **BK ADC** with their departure intentions. In response, **BK ADC** will clear the aircraft for takeoff and instruct them to track via the appropriate exit gate. -!!! example +!!! phraseology **YZD:** "Bankstown Tower, helicopter YZD, main pad, for Choppers North departure, ready" **BK ADC:** "YZD, Bankstown Tower, depart Choppers North, main pad, cleared for takeoff" @@ -102,7 +102,7 @@ Helicopters shall report ready to **BK ADC** with their departure intentions. In ### 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. -!!! example +!!! phraseology **BK ADC:** "SUA, main pad, cleared stop and go" ## ATIS @@ -122,7 +122,7 @@ When the aircraft is ready for departure, Tower will coordinate with the relevan The Standard Assignable level from BK ADC to SY TCU is `A030`, any other level must be prior coordinated. -!!! example +!!! phraseology **BK ADC** -> **SY TCU**: "Next, UJN, runway 29C" **SY TCU** -> **BK ADC**: "UJN, unrestricted" **BK ADC** -> **SY TCU**: "UJN" @@ -134,7 +134,7 @@ SY TCU will heads-up coordinate arrivals/overfliers from Class C to BK ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to BK ADC, unless BK ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **SY TCU** -> **BK ADC**: "via GRB, UJN" **BK ADC** -> **SY TCU**: "UJN, A010" diff --git a/docs/aerodromes/classd/Camden.md b/docs/aerodromes/classd/Camden.md index f1b3b4f68..f33bcf7a7 100644 --- a/docs/aerodromes/classd/Camden.md +++ b/docs/aerodromes/classd/Camden.md @@ -31,7 +31,7 @@ Departing IFR aircraft will receive a frequency transfer. ### Depart On Climb Some aircraft may request to leave the CTR on climb above `A013`. If there is no reported traffic above the zone and no conflicting traffic at `A018`, aircraft may be cleared to depart on climb. -!!! example +!!! phraseology **CN ADC:** "PCN, runway 06, cleared for takeoff" **PCN:** "Runway 06, cleared for takeoff, PCN" @@ -54,7 +54,7 @@ VFR aircraft should track via one of the VFR inbound points and be instructed as When Aircraft are clear of conflicting traffic below, aircraft may *"cleared visual approach"*. When an aircraft reports at their specified report point (or on downwind), issue the aircraft its sequence in the circuit. -!!! example +!!! phraseology *"XEM, number 3 Runway 06, follow the C172 on base"* ### Instrument Approaches @@ -83,7 +83,7 @@ The circuit direction changes depending on time of day and runway being used. Circuits are flown at `A013` (High Performance Aircraft: `A018`) When an aircraft reports on downwind, indicate their position in the sequence (and give a follow instruction if the sequence has changed since the last circuit). -!!! example +!!! phraseology **JKA:** "JKA, downwind, touch and go" **CN ADC:** "JKA, number 2" @@ -96,7 +96,7 @@ When there is more than SCT cloud on the YSCN METAR area below `A035`, the APCH ### Departures CN ADC must advise SY TCU when the aircraft has called 'Ready'. In response to a ready call, SY TCU will issue a traffic statement. -!!! example +!!! phraseology **CN ADC** -> **SRI**: "Ready, MHQ, Runway 06" **SRI** -> **CN ADC**: "MHQ, traffic is MEH, an IFR AC50, tracking SHL RAKSO SB2WI, A035, estimate RAKSO time 35" (or "No Reported IFR Traffic") **CN ADC** -> **SRI**: "Traffic is MEH tracking SHL RAKSO SB2WI A035, RAKSO at 35" @@ -115,7 +115,7 @@ SY TCU will coordinate inbound IFR aircraft. CN ADC is responsible for issuing a SY TCU will **NOT** clear the aircraft for the approach. -!!! example +!!! phraseology **SRI** -> **CN ADC**: “via RNP W, HRP” **CN ADC** -> **SRI**: “HRP” diff --git a/docs/aerodromes/classd/Hobart.md b/docs/aerodromes/classd/Hobart.md index 9a44bb3a7..d25c3b4ff 100644 --- a/docs/aerodromes/classd/Hobart.md +++ b/docs/aerodromes/classd/Hobart.md @@ -44,20 +44,20 @@ All IFR Aircraft departing Cambridge shall be assigned a **Visual Departure** or !!! note Both VFR and IFR aircraft require a clearance to operate in Class D airspace (even if this is an implied clearance to depart a leg of the circuit). The examples below show an IFR aircraft departing. -!!! Example +!!! phraseology **NDR:** "Hobart Ground, NDR, for Devonport, Request Clearance" **HB SMC:** "NDR, Cleared to Devonport via KANLI flight plan route, KANLI3 Departure, Climb via SID A045, Squawk 4432" When ready to taxi and prior to leaving the apron aircraft must contact **HB ADC**, advising intended runway for departure and receipt of YMHB ATIS, to obtain traffic information. -!!! Example +!!! phraseology **NDR:** "Hobart Tower, NDR, taxiing Cambridge Runway 32, received Hobart Information D" **HB ADC:** "NDR, No reported IFR traffic, report ready" **NDR:** "Wilco, NDR" Takeoff clearances are not given. Aircraft will remain clear of the active runway and report ready to HB ADC. Aircraft must not enter an active runway or become airborne until departure instructions have been issued. -!!! Example +!!! phraseology **NDR:** "NDR, Ready" **HB ADC:** "NDR, track via the KANLI3 departure, report airborne" **NDR:** "Track via the KANLI3 departure, wilco, NDR" @@ -68,7 +68,7 @@ Inbound VFR aircraft should be instructed to join a leg of the circuit and clear As a landing clearance is not given, aircraft should instead be informed of any traffic operating on the aerodrome and instructed to report clear of the runway. -!!! example +!!! phraseology *UJA is an IFR Aero Commander who has been cleared the YMHB RNAV-Z RWY 30 approach by HB APP and handed off to HB ADC.* **UJA:** "Hobart Tower, UJA" **HB ADC:** "UJA, Hobart Tower, report visual" @@ -78,7 +78,7 @@ As a landing clearance is not given, aircraft should instead be informed of any **HB ADC:** "UJA, track for final runway 30, no reported traffic, report clear of the runway" **UJA:** "Track for final runway 30, wilco, UJA" -!!! example +!!! phraseology *KLR is a VFR Cherokee who is tracking inbound on the Victor East VFR route.* **HB ADC:** "KLR, enter the control zone tracking via the Victor East, A015, clearance limit Sorell" **KLR:** "Enter control zone tracking via the Victor East, A015, clearance limit Sorell, KLR" @@ -112,7 +112,7 @@ As a landing clearance is not given, aircraft should instead be informed of any Clearances for aircraft entering the CTR must be worded so as to leave no possibility for misinterpretation by the pilot. -!!! Example +!!! phraseology **NDR:** "Hobart Tower, NDR, CPA, A015, on the Victor Northwest, received Romeo, request clearance" **HB ADC:** "NDR, enter the CTR tracking via the Victor Northwest at A015." @@ -126,7 +126,7 @@ Clearances for aircraft entering the CTR must be worded so as to leave no possib All other aircraft require a 'Next' call to HBA. -!!! example +!!! phraseology **HB ADC** -> **HBA**: "Next, ABC, runway 12" **HBA** -> **HB ADC**: "ABC, Heading 150 Visual, unrestricted" **HB ADC** -> **HBA**: "Heading 150 Visual, ABC" @@ -152,6 +152,6 @@ HBA will heads-up coordinate arrivals/overfliers from Class C to HB ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to HB ADC, unless HB ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **HBA** -> **HB ADC**: "via BAVUR for the RNAV-W RWY 12, QJE1551" **HB ADC** -> **HBA**: "QJE1551, RNP-W RWY 12" diff --git a/docs/aerodromes/classd/Jandakot.md b/docs/aerodromes/classd/Jandakot.md index dd270d728..ff1ddbffc 100644 --- a/docs/aerodromes/classd/Jandakot.md +++ b/docs/aerodromes/classd/Jandakot.md @@ -91,7 +91,7 @@ When PH RWY 03 is in operation, the ATIS should include: ### Next Call When the aircraft is ready for departure, JT ADC will coordinate with the relevant PH TCU controller above them for permission to release the aircraft into their CTA. -!!! example +!!! phraseology **JT ADC** -> **PH TCU**: "Next, FD420, runway 24R" **PH TCU** -> **JT ADC**: "FD420, Unrestricted" **JT ADC** -> **PH TCU**: "FD420" @@ -103,7 +103,7 @@ PH TCU will heads-up coordinate arrivals/overfliers from Class C to JT ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to JT ADC, unless JT ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **PH TCU** -> **JT ADC**: "via RNAV-Z RWY 06L, FD416, circling to land RWY 24R" **JT ADC** -> **PH TCU**: "FD416, RNAV-Z RWY 06L with a circle to land RWY 24R" diff --git a/docs/aerodromes/classd/Launceston.md b/docs/aerodromes/classd/Launceston.md index 757dad6dc..d38d3a6e0 100644 --- a/docs/aerodromes/classd/Launceston.md +++ b/docs/aerodromes/classd/Launceston.md @@ -54,7 +54,7 @@ YMLT ATIS identifiers range from `A` to `M`, as YMHB uses `N` through `Y`. All other aircraft require a 'Next' call to LTA. -!!! example +!!! phraseology **LT ADC** -> **LTA**: "Next, ABC, runway 14L" **LTA** -> **LT ADC**: "ABC, Heading 150 Visual, unrestricted" **LT ADC** -> **LTA**: "Heading 150 Visual, ABC" @@ -77,6 +77,6 @@ LTA will heads-up coordinate arrivals/overfliers from LTA CTA to LT ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to LT ADC, unless LT ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **LTA** -> **LT ADC**: "via IRSOM for the DGA, TFW" **LT ADC** -> **LTA**: "TFW, DGA" diff --git a/docs/aerodromes/classd/Mackay.md b/docs/aerodromes/classd/Mackay.md index 1ea58dfc9..62b00c291 100644 --- a/docs/aerodromes/classd/Mackay.md +++ b/docs/aerodromes/classd/Mackay.md @@ -29,7 +29,7 @@ Refer to [Class D Tower Separation Standards](../../../separation-standards/clas c) Assigned a **Procedural** SID; or d) Not entering MKA CTA -!!! example +!!! phraseology **MK ADC** -> **MKA**: "Next, ABC, runway 14" **MKA** -> **MK ADC**: "ABC, Heading 150 Visual, unrestricted" **MK ADC** -> **MKA**: "Heading 150 Visual unrestricted, ABC" @@ -49,6 +49,6 @@ MKA will heads-up coordinate arrivals/overfliers from Class C to MK ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to MK ADC, unless MK ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **MKA** -> **MK ADC**: "Via BAVAM for the RNP RWY 32, VOZ1164” **MK ADC** -> **MKA**: "VOZ1164, RNP RWY 32" \ No newline at end of file diff --git a/docs/aerodromes/classd/Moorabbin.md b/docs/aerodromes/classd/Moorabbin.md index 5c199d9d7..c628d8fc0 100644 --- a/docs/aerodromes/classd/Moorabbin.md +++ b/docs/aerodromes/classd/Moorabbin.md @@ -64,19 +64,19 @@ Autorelease is not in effect at YMMB and all departures into the overlying Class The standard assignable level for departures into CTA is `A050` or `RFL` if lower. -!!! example +!!! phraseology **MB ADC** -> **MDS**: "Next, SGE" **MDS** -> **MB ADC**: "SGE, unrestricted" Aircraft departing directly into Class C airspace should be instructed to report passing A025 and transferred to the TCU at that point. -!!! example +!!! phraseology **SGE**: "SGE, A025" **MB ADC**: "SGE, contact Melbourne Departures on 129.4" Aircraft who will transit Class G airspace on climb into CTA will be **cleared to leave and re-enter controlled airspace** on climb to their assigned level. -!!! example +!!! phraseology **MB ADC**: "SGE, cleared to leave and re-enter controlled airspace climbing to A050, no reported IFR traffic. Contact Melbourne Departures on 129.4" **SGE**: "Cleared to leave and re-enter controlled airspace climbing to A050, Departures 129.4, SGE" @@ -85,7 +85,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from Class C to MB ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to MB ADC, unless MB ADC nominates a restriction. VFR aircraft will not be coordinated, and will need to receive their airways clearance from MB ADC. -!!! example +!!! phraseology **MDS** -> **MB ADC**: "To the west, PLE, for the NDB-A" **MB ADC** -> **MDS**: "PLE, NDB-A" diff --git a/docs/aerodromes/classd/Parafield.md b/docs/aerodromes/classd/Parafield.md index 2d5134432..1970a40a7 100644 --- a/docs/aerodromes/classd/Parafield.md +++ b/docs/aerodromes/classd/Parafield.md @@ -64,7 +64,7 @@ The APCH field should include `EXP INST APCH` when: ### Departures When the aircraft is ready for departure, PF ADC will coordinate with the relevant Class C sector above them for permission to release the aircraft into their CTA. -!!! example +!!! phraseology **PF ADC** -> **AAW**: "Next, XMM, 03L" **AAW** -> **PF ADC**: "XMM, Heading 020, unrestricted" **PF ADC** -> **AAW**: "Heading 020, XMM" @@ -76,7 +76,7 @@ IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) VFR aircraft require a level readback. -!!! example +!!! phraseology **AAW** -> **PF ADC**: "via PAL, YTS" **PF ADC** -> **AAW**: "YTS, A010" diff --git a/docs/aerodromes/classd/Rockhampton.md b/docs/aerodromes/classd/Rockhampton.md index 49bf1664f..04e6ab812 100644 --- a/docs/aerodromes/classd/Rockhampton.md +++ b/docs/aerodromes/classd/Rockhampton.md @@ -30,7 +30,7 @@ Refer to [Class D Tower Separation Standards](../../../separation-standards/clas c) Assigned a **Procedural** SID; or d) Not entering RKA CTA -!!! example +!!! phraseology **RK ADC** -> **RKA**: "Next, VJE" **RKA** -> **RK ADC**: "VJE, Track Extended Centreline, Unrestricted" **RK ADC** -> **RKA**: "Track Extended Centreline, VJE" @@ -50,6 +50,6 @@ RKA will heads-up coordinate arrivals/overfliers from Class C to RK ADC. IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to RK ADC, unless RK ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **RKA** -> **RK ADC**: "Via SARUS for the visual approach, VJN” **RK ADC** -> **RKA**: "VJN, visual approach" \ No newline at end of file diff --git a/docs/aerodromes/procedural/Albury.md b/docs/aerodromes/procedural/Albury.md index 07c28970e..fc79ae60f 100644 --- a/docs/aerodromes/procedural/Albury.md +++ b/docs/aerodromes/procedural/Albury.md @@ -28,7 +28,7 @@ Surveillance coverage can be expected to be available at all levels in the AY CT ### Departures A 'Next' call is made for all aircraft entering ELW(BLA) CTA when they are next to depart. AY ADC must inform ELW(BLA) if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **AY ADC** -> **BLA**: "Next, AM324" **BLA** -> **AY ADC**: "AM324, Unrestricted" **AY ADC** -> **BLA**: "AM324" @@ -38,7 +38,7 @@ The Standard Assignable level from AY TWR to ELW(BLA) is the lower of `A070` or ### Arrivals/Overfliers ELW(BLA) will heads-up coordinate all arrivals/overfliers to AY ADC -!!! example +!!! phraseology **BLA** -> **AY ADC**: "Via ARRAN1 Arrival, RXA6783” **AY ADC** -> **BLA**: "RXA6783" diff --git a/docs/aerodromes/procedural/Alice.md b/docs/aerodromes/procedural/Alice.md index 01f0ce81f..97b8b3321 100644 --- a/docs/aerodromes/procedural/Alice.md +++ b/docs/aerodromes/procedural/Alice.md @@ -27,7 +27,7 @@ Surveillance coverage can be expected to be available at all levels in the AS CT ### Departures Departures from YBAS in to ASP Class C will be coordinated when ready for departure. -!!! example +!!! phraseology **AS ADC** -> **ASP**: "Next, QFA797" **ASP** -> **AS ADC**: "QFA797, Unrestricted" **AS ADC** -> **ASP**: "QFA797" @@ -37,7 +37,7 @@ The Standard Assignable level from AS ADC to ASP is the lower of `A070` or the ` ### Arrivals/Overfliers ASP will heads-up coordinate all arrivals/overfliers to AS ADC -!!! example +!!! phraseology **ASP** -> **AS ADC**: "Via SADEL, QFA1956” **AS ADC** -> **ASP**: "QFA1956" diff --git a/docs/aerodromes/procedural/Broome.md b/docs/aerodromes/procedural/Broome.md index 3b1b6f81b..9ff7bb0a5 100644 --- a/docs/aerodromes/procedural/Broome.md +++ b/docs/aerodromes/procedural/Broome.md @@ -28,7 +28,7 @@ Surveillance coverage can be expected to be available at all levels in the BRM C ### Departures A 'next' call is made for all aircraft entering TRT(ASH) CTA when they are next to depart. BRM ADC must inform TRT(ASH) if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **BRM ADC** -> **ASH**: "Next, NWK1653" **ASH** -> **BRM ADC**: "NWK1653, Unrestricted" **BRM ADC** -> **ASH**: "NWK1653" @@ -38,7 +38,7 @@ The Standard Assignable level from BRM ADC to TRT(ASH) is the lower of `A050` or ### Arrivals/Overfliers TRT(ASH) will heads-up coordinate all arrivals/overfliers to BRM ADC -!!! example +!!! phraseology **ASH** -> **BRM ADC**: "Via CIN, ANO332” **BRM ADC** -> **ASH**: "ANO332" diff --git a/docs/aerodromes/procedural/Coffs.md b/docs/aerodromes/procedural/Coffs.md index 03a1e4c33..a324a40e3 100644 --- a/docs/aerodromes/procedural/Coffs.md +++ b/docs/aerodromes/procedural/Coffs.md @@ -27,7 +27,7 @@ Surveillance coverage can be expected to be not available below `A028` in the CF ### Departures A 'next' call is made for all aircraft entering INL/ARL(MNN) CTA when they are next to depart. CFS ADC must inform INL/ARL(MNN) if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **CFS ADC** -> **MNN**: "Next, QJE1573" **MNN** -> **CFS ADC**: "QJE1573, Unrestricted" **CFS ADC** -> **MNN**: "QJE1573" @@ -37,7 +37,7 @@ The Standard Assignable level from CFS ADC to INL/ARL(MNN) is the lower of `A070 ### Arrivals/Overfliers INL/ARL(MNN) will heads-up coordinate all arrivals/overfliers to CFS ADC. -!!! example +!!! phraseology **INL** -> **CFS ADC**: "Via KADSI, RXA6416” **CFS ADC** -> **INL**: "RXA6416" diff --git a/docs/aerodromes/procedural/Hammo.md b/docs/aerodromes/procedural/Hammo.md index e423e7bfd..ea7bf8d19 100644 --- a/docs/aerodromes/procedural/Hammo.md +++ b/docs/aerodromes/procedural/Hammo.md @@ -29,7 +29,7 @@ Surveillance coverage can be expected to be not available below `A031` in the HM ### Departures A 'next' call is made for all aircraft entering KEN(SWY) CTA when they are next to depart. HM ADC must inform KEN(SWY) if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **HM ADC** -> **SWY**: "Next, QFA797" **SWY** -> **HM ADC**: "QFA797, Unrestricted" **HM ADC** -> **SWY**: "QFA797" @@ -39,7 +39,7 @@ The Standard Assignable level from HM ADC to KEN(SWY) is the lower of `A050` or ### Arrivals/Overfliers KEN(SWY) will heads-up coordinate all arrivals/overfliers to HM ADC -!!! example +!!! phraseology **SWY** -> **HM ADC**: "Via OPOSI for the RNP-U RWY 32, JST848” **HM ADC** -> **SWY**: "JST848" diff --git a/docs/aerodromes/procedural/Karratha.md b/docs/aerodromes/procedural/Karratha.md index 05530dd5f..daadbddd5 100644 --- a/docs/aerodromes/procedural/Karratha.md +++ b/docs/aerodromes/procedural/Karratha.md @@ -37,7 +37,7 @@ Surveillance coverage can be expected to be available at all levels in the KA CT ### Departures A 'next' call is made for all aircraft entering OLW CTA when they are next to depart. KA ADC must inform OLW if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **KA ADC** -> **OLW**: "Next, NWK694" **OLW** -> **KA ADC**: "NWK694, Unrestricted" **KA ADC** -> **OLW**: "NWK694" @@ -47,7 +47,7 @@ The Standard Assignable level from KA ADC to OLW is the lower of `A050` or the ` ### Arrivals/Overfliers OLW will heads-up coordinate all arrivals/overfliers to KA ADC -!!! example +!!! phraseology **OLW** -> **KA ADC**: "Via PD, KPG, Overflier” **KA ADC** -> **OLW**: "KPG, A040" diff --git a/docs/aerodromes/procedural/Sunshinecoast.md b/docs/aerodromes/procedural/Sunshinecoast.md index ba623551d..365f34c5e 100644 --- a/docs/aerodromes/procedural/Sunshinecoast.md +++ b/docs/aerodromes/procedural/Sunshinecoast.md @@ -35,7 +35,7 @@ All other aircraft may be assigned a visual departure, or a standard IFR departu ### Departures A 'next' call is made for all aircraft entering INL(NSA/BUR) CTA when they are next to depart. SU ADC must inform INL(NSA/BUR) if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **SU ADC** -> **NSA**: "Next, BNZ133, runway 31" **NSA** -> **SU ADC**: "BNZ133, unrestricted" **SU ADC** -> **NSA**: "BNZ133" @@ -44,13 +44,13 @@ The Standard Assignable level from SU ADC to INL(NSA/BUR) is the lower of `A040` Where operationally possible, INL(NSA/BUR) will assign a higher level to high performance aircraft during next coordination. This level assignment should be communicated to the aircraft during the takeoff clearance or when they provide a departure report after takeoff. -!!! example +!!! phraseology **SU ADC**: "VOZ924, climb to FL120, runway 31, cleared for takeoff" ### Arrivals/Overfliers NSA will heads-up coordinate arrivals/overfliers from Class C to SU ADC. Aircraft will be cleared for the coordinated approach prior to handoff to SU ADC, unless SU ADC nominates a restriction. -!!! example +!!! phraseology **NSA** -> **SU ADC**: "Via ITIDE2W Arrival, QJE1756” **SU ADC** -> **NSA**: "QJE1756" diff --git a/docs/aerodromes/procedural/Tamworth.md b/docs/aerodromes/procedural/Tamworth.md index 39cc260e3..86c2a39da 100644 --- a/docs/aerodromes/procedural/Tamworth.md +++ b/docs/aerodromes/procedural/Tamworth.md @@ -75,7 +75,7 @@ Circuits are to be flown in the direction coinciding with the Runway designator ### Departures A 'next' call is made for all aircraft entering ARL/MDE CTA when they are next to depart. TW ADC must inform ARL/MDE if the aircraft does not depart within **2 minutes** of the next call. -!!! example +!!! phraseology **TW ADC** -> **ARL**: "Next, QLK5D" **ARL** -> **TW ADC**: "QLK5D, Unrestricted" **TW ADC** -> **ARL**: "QLK5D" @@ -85,7 +85,7 @@ The Standard Assignable level from TW ADC to ARL/MDE is the lower of `A070` or t ### Arrivals/Overfliers ARL/MDE will heads-up coordinate all arrivals/overfliers to TW ADC -!!! example +!!! phraseology **MDE** -> **TW ADC**: "Via MOR DCT for the VOR-A, FD272” **TW ADC** -> **MDE**: "FD272, VOR-A" diff --git a/docs/assets/headset.svg b/docs/assets/headset.svg new file mode 100644 index 000000000..8f6410bbc --- /dev/null +++ b/docs/assets/headset.svg @@ -0,0 +1,4 @@ + + + + diff --git a/docs/assist-us/best-practices.md b/docs/assist-us/best-practices.md index 08472b2a8..4c1132d8c 100644 --- a/docs/assist-us/best-practices.md +++ b/docs/assist-us/best-practices.md @@ -25,7 +25,7 @@ All links that navigate a user away from the SOPs site should have `{target=new} [External Link](https://vatpac.org){target=new} ``` -!!! warning +!!! warning "Important" All external links should use the `https` protocol. ## Sector Names @@ -50,7 +50,7 @@ Radio calls should take the following format: **STATION NAME**: "Message" ``` -!!! example +!!! phraseology **VOZ1545**: "VOZ1545, request descent" **HUO**: "VOZ1545, descend to FL130" @@ -73,7 +73,7 @@ As a general rule of thumb, hotlines should be used in all circumstances, except - Oceanic coordination - Airways clearance requests from ACD to overlying TCU/ENR position (e.g. Sydney Delivery requesting clearance to YSBK on behalf of an aircraft) -!!! example +!!! phraseology **NW TCU** -> **WOL**: "Taxi, PSDN18 for YMCO via URBOB, Requesting F130" **WOL** -> **NW TCU**: "PSDN18, F130" **NW TCU** -> **WOL**: "F130, PSDN18" diff --git a/docs/assist-us/setup.md b/docs/assist-us/setup.md index c751dcc6a..13f183f7c 100644 --- a/docs/assist-us/setup.md +++ b/docs/assist-us/setup.md @@ -6,7 +6,7 @@ We'll kick off by setting up your local development environment. -!!! important +!!! warning "Important" If you have any questions about setting up your development environment for these SOPs, or you get stuck - feel free to reach out to the Operations Team. ## Requirements diff --git a/docs/assist-us/tips.md b/docs/assist-us/tips.md index f17bcc7f0..39afa45a3 100644 --- a/docs/assist-us/tips.md +++ b/docs/assist-us/tips.md @@ -22,7 +22,7 @@ Links that navigate a user through the SOPs site can follow the normal Markdown [External Link](https://vatpac.org){target=new} ``` -!!! warning +!!! warning "Important" All external links should use the `https` protocol. ### Buttons diff --git a/docs/client/towerstrips.md b/docs/client/towerstrips.md index 7a2341317..70efa7591 100644 --- a/docs/client/towerstrips.md +++ b/docs/client/towerstrips.md @@ -8,7 +8,7 @@ In the real world, aerodrome controllers use strips to provide a visual represen Within vatSys, this can be emulated using the [OzStrips plugin](https://maxrumsey.xyz/OzStrips/){target=new}. Strip state is shared between controllers operating at the same aerodrome. -!!! important +!!! warning "Important" OzStrips can be an incredibly useful tool to reduce controller workload and improve the level of service offered to pilots, but it's use is not compulsory. Controllers should revert to the default vatSys strip bays if the use of OzStrips is becoming a hinderance to themselves or surrounding controllers. ## Setup @@ -275,5 +275,5 @@ Aircraft at the bottom of the queue are first in line. When an aircraft is in a queue, make sure the strip's bay location represents its current state. -!!! Example +!!! example An aircraft in a queue for an airways clearance, would remain in the *Preactive* bay, below the queue bar, not in the *Cleared* bay. \ No newline at end of file diff --git a/docs/controller-skills/airwork.md b/docs/controller-skills/airwork.md index e997c6e6f..1a9d811a5 100644 --- a/docs/controller-skills/airwork.md +++ b/docs/controller-skills/airwork.md @@ -12,7 +12,7 @@ Airwork is essentially defined as an aerial operation that doesn't involve simpl Airwork can be conducted in any defined area specified by the pilot or ATC. This can be a radius from a fix (eg within a 20nm Radius of YBMK), a Survey Area (eg Operating within [Map 420 Survey Area](#survey-map-example)), a defined polygon (eg Operating within an area between BNA-IDNER-VEGAH-TUCAB), a visual topographical feature (eg Operating within the Port Phillip Bay area), or any other area specified by Pilot or ATC. -!!! example +!!! phraseology **PPB**: "PPB, with Airwork Details" **KIY**: "PPB" **PPB**: "PPB, will be conducting Airwork within a 20nm radius of YPKU, not above A040, for the next 20 minutes. Will call Ops Normal time 30" @@ -64,7 +64,7 @@ A pilot intending to conduct Aerial Survey Operations as per Map 420 #### Ops Normal time If an aircraft is to be conducting airwork that does not require them to talk to ATC for an extended period (30 mins or more), an "Ops Normal" time should be agreed upon. This is a time that the aircraft confirms they will "check-in" with ATC by, to confirm that they're still alive essentially. If the pilot does not volnteer an Ops Normal time, provide them with one that is on an even hour or half hour, anywhere from 30 mins to 60 mins from the current time. -!!! example +!!! phraseology Time is 0648Z **OBF**: "OBF will be conducting Airwork within a 20nm radius of YBLT Not above A050 for the next 60 minutes" **YWE**: "OBF, No Reported IFR Traffic, Call Ops Normal time 30." @@ -113,7 +113,7 @@ SAR Operations are conducted more or less as a standard airwork procedure. Handl SAR Operations are most commonly flown in a circular area (eg Radius from a Fix, or Radius from a Lat/Long), or a Straight line pattern (eg, back and forth on a line between 2 Fixes, or 2 Lat/Longs). -!!! example +!!! phraseology **DDU**: "DDU, Requesting Traffic for Search and Rescue operations for the next 90 minutes, within a 10nm Radius of 23 52 South, 136 01 East, Not above A060" **ASP**: "DDU, No Reported IFR Traffic. Call Ops Normal time on the hour" **DDU**: "Ops Normal on the hour, DDU" @@ -130,7 +130,7 @@ A Practice Instrument Approach is simply an aircraft conducting an Instrument Ap VFR aircraft are still allowed to do Instrument Approaches #### Initial Call -!!! example +!!! phraseology **YNJ**: "Adelaide Approach, YNJ, Requesting Practice YPPF VOR-A Approach" **AAE**: "YNJ, Adelaide Approach, Standby" @@ -160,7 +160,7 @@ Then we continue our assessment. Assess for: A Sector Entry is a procedure pilots use to commence an approach. The type of turn made prior to the commencement of the approach differs based on which direction the aircraft is joing from. That is all we really need to know as a controller. No need to overcomplicate things as a controller, simply ask the following: -!!! example +!!! phraseology **AAE**: "YNJ, Will you be requiring a Sector Entry or Hold for the Approach?" **YNJ**: "Affirm will require a Sector Entry, but no hold, YNJ" **AAE**: "YNJ" @@ -171,16 +171,16 @@ Label Data, Block Levels, and Text-on-Screen are all useful for Practice Instrum #### Coordination Conduct Coordination to any affected adjacent units as required -!!! example +!!! phraseology **AAE** -> **AAW**: "via AD, YNJ, for a Practice VOR-A approach at YPPF, with your concurrence, I'll clear them for the approach, and will call you overhead AD. Your coord with AD ADC" **AAW** -> **AAE**: "YNJ calls me overhead AD with approach clearance, concurred. My onwards with AD ADC" -!!! example +!!! phraseology **AAW** -> **AD ADC**: "Cancel Auto Release temporarily, I've got an aircraft doing the VOR-A for YPPF" **AD ADC** -> **AAW**: "Copied, Auto Release cancelled" #### Clearance (if required) -!!! example +!!! phraseology **AAE**: "YNJ, Cleared VOR-A Approach, make Sector Entry. At the minima, Fly Published Missed Approach" **YNJ**: "Cleared VOR-A Approach, make Sector Entry. At the minima, Fly Published Missed Approach, YNJ" @@ -206,7 +206,7 @@ Aerial Survey Work involves flying in a pattern similar to that shown above. Pil The numbers signify "Runs" that the survey aircraft can be cleared for. It is important to note, that the pilot may require to do these runs in a particular order and direction, and at a particular altitude. They also may have some flexibility. Ask the pilot questions if you need more information about how much freedom you have to move them where you want for separation purposes #### Initial Call -!!! example +!!! phraseology **MZI**: "Melbourne Centre, MZI, Conquest, POB 1, IFR, Taxis Runway 36 at YMNG for Survey Operations" **ELW**: "MZI, Melbourne Centre, Squawk 3601, No Reported IFR Traffic" **MZI**: "Squawk 3601, MZI" @@ -224,20 +224,20 @@ Dropping Text-on-Screen of the letter "X" at the vertices of the rough area in w #### Coordination In this example, lets say the aircraft is intending to operate at F168. Boundary Coordination to ML TCU is not technically required, however, they have a voiceless coordination to you for aircraft assigned the DOSEL and NONIX SID, Climbing to F240. This would place YMML departures directly in conflict with the survey aircraft. A negotation should be made to assure separation between departures and the survey aircraft. -!!! example +!!! phraseology **ELW** -> **MDN**: "For Ident, MZI, conducting Survey work between DOSEL and BOGES at F168. All departures via NONIX and DOSEL to have restriction to reach F180 by 30 miles ML, or assigned level at or below F150, until advised" **MDN** -> **ELW**: "Copied all departures to be assigned restriction to reach F180 by 30 miles ML, or F150 or lower, reference MZI" #### Clearance (if required) Start by clearing the aircraft to where they need to go -!!! example +!!! phraseology **ELW**: "MZI, Cleared directly to the start of Run 1, Climb to F168" **MZI**: "Cleared directly to the start of Run 1, Climb to F168, MZI" Then when ready, clear the aircraft for the survey work -!!! example +!!! phraseology **ELW**: "MZI, Cleared for Runs 1 through 4, Report at the completion of each run" **MZI**: "Cleared for Runs 1 through 4, Wilco, MZI" @@ -261,7 +261,7 @@ There are lots of different variables at play when considering how to handle par #### Initial Call The exact nature of Parachute Operations can vary significantly at different drop zones around the country, so it's very important to ascertain the pilot's exact intentions prior to them entering controlled airspace. -!!! example +!!! phraseology **DJV**: "Sydney Departures, Caravan, DJV, Airborne YSHL for Parachute Operations overhead Flagstaff Point, Requesting F140" **SDS**: "DJV, Sydney Departures, Standby" @@ -269,7 +269,7 @@ The exact nature of Parachute Operations can vary significantly at different dro The aircraft may or may not have filed a flightplan. Search in the Preactive window or Flight Plan Window for their callsign. If you find a flight plan, activate it, and pass the aircraft their squawk code. If there is no flight plan, simply create a Quicktag for the aircraft, and assign them the displayed code. -!!! example +!!! phraseology **SDS**: "DJV, Sydney Departures, Squawk 3601" **DJV**: "Squawk 3601, DJV" @@ -301,14 +301,14 @@ Many drop zones around the country have associated Danger Areas, that can be see #### Coordination Conduct Coordination to any affected adjacent units as required -!!! example +!!! phraseology **SDS** -> **SAS**: "For Ident, DJV, conducting Parachute Operations at Flagstaff Point, do you have any restrictions or requirements?" **SAS** -> **SDS**: "DJV, no restrictions, no requirements" #### Clearance (if required) Best practice is to clear the aircraft to operate within a reasonably sized radius area of the drop zone, 5nm for example. If the pilot has special requests to add to the clearance, it is their responsibility to communicate it to you. -!!! example +!!! phraseology **SDS**: "DJV, Cleared to operate within a 5nm radius of Flagstaff Point, Climb to F140. Report Ready for Drop and Descent" **DJV**: "Cleared to operate within a 5nm radius of Flagstaff Point, Climb to F140, Wilco, DJV" @@ -317,25 +317,25 @@ Ensure you maintain separation assurance with other aircraft in the area. There #### Broadcasts Throughout the Parachute operations, you can expect the PJE aircraft to make multiple broadcasts on your frequency to traffic in the area. Unless the aircraft addresses you directly (eg *"Sydney Departures and traffic in the Wollongong area"*), there is no need to respond to these traffic broadcasts -!!! example +!!! phraseology **DJV**: "Traffic in the Wollongong city area, DJV is a Caravan, 5 minutes to Parachute drop from flight levels overhead Flagstaff Point, expect 6 canopies, Traffic Wollongong city area" #### Drop and Descent -!!! example +!!! phraseology **DJV**: "DJV, Broadcasts complete, Request Drop and Descent" You are required to separate all aircraft from a **2nm Radius** of the Drop Zone (ie, the appropriate radar standard, 3nm for TCU, 5nm for Enroute, **Plus** 2nm Radius of the Drop Zone), once a drop clearance has been given. This is because you are no longer just separating from the aircraft, but the Parachutes themselves as well. Your responsibility for separating from the Parachutes terminates once the pilot reports the chutes are OCTA. Once again, when giving drop and descent clearance, consider giving an interim level, or a heading, if required for separation. -!!! example +!!! phraseology **SDS**: "DJV, Cleared to Drop and leave controlled airspace descending, not below the chutes, tracking DCT YSHL, No Reported IFR Traffic. Report chutes OCTA." **DJV**: "Cleared to Drop and leave controlled airspace descending, not below the chutes, tracking DCT YSHL, Wilco, DJV." !!! note *"Not below the chutes"* is so that you can separate from the last level vacated by the aircraft. If you do not instruct the aircraft to descend not below the chutes, then you would need to separate all the way from the drop height (in this case, F140) until the chutes are reported as OCTA. -!!! example +!!! phraseology **DJV**: "DJV, Chutes and aircraft OCTA." **SDS**: "DJV, Identification terminated, Frequency change approved" **DJV**: "DJV" diff --git a/docs/controller-skills/circuitoperations.md b/docs/controller-skills/circuitoperations.md index 0387f80a0..fb2737a8a 100644 --- a/docs/controller-skills/circuitoperations.md +++ b/docs/controller-skills/circuitoperations.md @@ -13,7 +13,7 @@ at any aerodrome, including major Class C aerodromes. At a Class C aerodrome, provide an explicit clearance to operate in the circuit area, alongside an altitude and a discrete squawk code. -!!! example +!!! phraseology *ABC is a VFR aircraft on the ground at Canberra that intends to conduct circuit training.* **ABC:** "Canberra Ground, ABC, request clearance for circuits" **CB SMC:** "ABC, Canberra Ground, cleared to operate in the circuit area not above A030, squawk 0040" @@ -23,7 +23,7 @@ area, alongside an altitude and a discrete squawk code. At a Class D aerodrome, a clearance to take-off is a clearance to operate within a Class D control zone, so an explicit airways clearance is not given. -!!! example +!!! phraseology *ABC is a VFR aircraft on the ground at Archerfield that intends to conduct circuit training.* **ABC:** "Archer Ground, ABC, Cessna 172, information F, on the Eastern Apron, request taxi, for circuits" **AF SMC:** "ABC, Archer Ground, taxi to holding point B1, runway 28R" @@ -35,7 +35,7 @@ a Class D control zone, so an explicit airways clearance is not given. For aircraft that are already airborne, provide circuit joining instructions on first contact. -!!! example +!!! phraseology *DEF is a VFR aircraft inbound to Canberra that intends to conduct circuit training.* **DEF:** "Canberra Tower, DEF, overhead Hoskinstown, A040, information L, for circuits" **CB ADC:** "DEF, Canberra Tower, join downwind runway 12, not above A030, squawk 2311" @@ -58,7 +58,7 @@ Circuit directions are usually provided in ERSA, but if any doubt exists or a non-standard circuit is in use, provide the circuit direction with the take-off clearance. -!!! example +!!! phraseology **AF ADC:** "ABC, runway 28R, cleared for take-off, make left circuit" **ABC:** "Runway 28R, cleared for take-off, make left , ABC" @@ -73,7 +73,7 @@ different requests a pilot may make at this point: 3. a **full-stop landing**, where the aircraft makes a normal landing and exits the runway; or 4. the **option**, which is the pilot asking for the option to make either of the above three manouvers at their own discretion, without any further clearance. -!!! example +!!! phraseology **ABC:** "ABC, downwind, touch and go" **AF ADC:** "ABC, cleared touch and go" **ABC:** "Cleared touch and go, ABC" @@ -82,7 +82,7 @@ different requests a pilot may make at this point: Depending on the traffic situation, you may approve the pilots request, or else require that they make a full-stop landing. -!!! example +!!! phraseology **ABC:** "ABC, downwind, request the option" **AF ADC:** "ABC, make full stop due to traffic, cleared to land" **ABC:** "Cleared to land, ABC" @@ -98,7 +98,7 @@ aircraft arriving at the aerodrome from elsewhere. **ADC** are not permitted to vector aircraft, but there are a number of other tools available to help segregate aircraft within the circuit. -!!! warning +!!! warning "Important" The use of these tools in no way diminishes the responsibility of VFR aircraft to see and avoid, nor does it relieve the controller of the responsibility to pass traffic information where applicable. @@ -111,7 +111,7 @@ A straightforward way of accomplishing this with minimal added workload is to instruct the aircraft to "follow" the leading aircraft. In order to do this, the following aircraft **must** report having the leading aircraft in sight. -!!! example +!!! phraseology *ABC is downwind on runway 16L at Sydney while QFA1254 is established on a 3 mile final for the same runway.* **ABC:** "ABC, downwind, touch and go" **SY ADC:** "ABC, traffc is a 737 on a 3nm final, runway 16L, report sighting" @@ -128,7 +128,7 @@ following aircraft **must** report having the leading aircraft in sight. An **ADC** may issue an instruction for a pilot to make a complete 360 degree orbit, either left or right, to delay the aircraft in place. -!!! example +!!! phraseology *DEF, a Cessna 172, is on a left downwind on runway 30 at Canberra, while UEM, a Baron, is joining left base.* **DEF:** "DEF, downwind, full-stop" **CB ADC:** "DEF, make one right hand orbit" @@ -153,7 +153,7 @@ different performances for better traffic flow. You may approve a pilot request for a change of runway for an aircraft established on final. -!!! example +!!! phraseology *ABC is on a right downwind on runway 16R at Sydney. QLK1834 is on a 7 mile final for the same runway.* **ABC:** "ABC, downwind, touch and go" **SY ADC:** "ABC, change of runway, runway 16L, cleared touch and go, make left circuit" diff --git a/docs/controller-skills/coordination.md b/docs/controller-skills/coordination.md index d0d9e17b8..62d5b90f0 100644 --- a/docs/controller-skills/coordination.md +++ b/docs/controller-skills/coordination.md @@ -25,7 +25,7 @@ Coordination notes are included for most positions, using the following format: As a receiving controller, answer a coordination call by stating the name of **your** position. If you are busy at the time, finish your current radio call and then state your position to indicate that you are ready to receive the message. -!!! example +!!! phraseology *BIK calls SAN with a hotline to discuss an arrival* **BIK** -> **SAN**: \***DING**\* **SAN** -> **BIK**: "Sydney Approach" @@ -42,7 +42,7 @@ Heads-up Coordination is the act of giving the next sector a "heads-up" about an Controlling Sector -> Receiving Sector: "(Position), (Callsign)" Receiving Sector -> Controlling Sector: "(Callsign), (Level)" -!!! example +!!! phraseology **ELW** -> **BIK**: "via CB, VOZ1234" **BIK** -> **ELW**: "VOZ1234, F350" @@ -50,7 +50,7 @@ If the level that will be assigned at transfer of jurisdiction is different from Once this coordination is completed, the aircraft's level and route is **locked in**. Any further changes must be recoordinated. -!!! example +!!! phraseology **ELW** -> **BIK**: "VOZ1234, requesting DCT RIVET" **BIK** -> **ELW**: "VOZ1234, concur DCT RIVET" @@ -72,13 +72,13 @@ Boundary coordination must be completed so they are aware of the aircraft, and c Controlling Sector -> Boundary Sector: "For Ident, (Position), (Callsign), (Details as required)" Boundary Sector -> Controlling Sector: "(Callsign), (Restriction)" -!!! example +!!! phraseology **BIK** -> **CBE**: "For Ident, overhead CB, QFA12, do you have any restrictions on descent?" **CBE** -> **BIK**: "QFA12, No restrictions on descent" The Boundary Sector may omit the restriction and readback the callsign only. This will be taken as the Boundary Sector having **no vertical or lateral restrictions**. -!!! example +!!! phraseology **INL** -> **BAS**: "For Ident, West of BLAKA, ABC" **BAS** -> **INL**: "ABC" @@ -111,7 +111,7 @@ Source: [Annotations](../../controller-skills/annotations) | **NRR** | No Restrictions or Requirements | **Any and all** lateral and level changes approved, and No Frequency Requirements | *Offering NFR* -!!! example +!!! phraseology *ABC tracking MNG W663 VINOP* **ELW** -> **YWE**: "via MNG, ABC, if you have no restrictions or requirements, my onwards with OXL" **YWE** -> **ELW**: "ABC, I have no restrictions or requirements, your onwards with OXL" @@ -121,7 +121,7 @@ Source: [Annotations](../../controller-skills/annotations) ELW will handoff the aircraft directly to OXL *Initiating NFR* -!!! example +!!! phraseology *DEF tracking EML-LEMER-RK* **SWY** -> **CVN**: "via LEMER, DEF, I have no vertical restrictions or frequency requirements, your onwards with KPL" **CVN** -> **SWY**: "DEF, my onwards with KPL" @@ -163,7 +163,7 @@ Voice coordinate 'Next' call **within 2 minutes of takeoff** unless overridden b If Auto Release is suspended by the TCU controller, respond by advising of any aircraft with a takeoff clearance. -!!! example +!!! phraseology **TCU** -> **ADC**: "Cancel auto release until time 45" **ADC** -> **TCU**: "Cancel auto release until time 45, QLK108D released" **TCU** -> **ADC**: "QLK108D" @@ -232,7 +232,7 @@ Coordination to **International** units shall be done in the following format: - Level - *"On climb"*/*"On descent*" (if applicable) -!!! example +!!! phraseology **IND** -> **FIMM CTR**: "Estimate, QFA63, IBMAT time 33, F360" **FIMM CTR** -> **IND**: "QFA63, F360" @@ -242,13 +242,13 @@ For any aircraft transiting **to or from** Uncontrolled airspace (ie: Class G, V ## Handoffs Receiving a handoff means you are permitted to turn an aircraft **45 degrees left or right**, and **climb/descend it to any level** without coordination. Do not handoff an aircraft to another sector if a turn of 45 degrees or a change of level would cause a conflict with any of your own aircraft. Or alternatively, you can nominate a restriction prior to handoff. -!!! example +!!! phraseology **YWE** -> **TBD**: "ABC, my restriction is DEF, calls you now" **TBD** -> **YWE**: "ABC, restriction is DEF, calls me now" Upon receipt of a handoff, once the aircraft is established **half the applicable lateral standard** (2.5nm for ENR, 1.5nm for ADC/TCU) within your airspace, you are free to turn the aircraft as much as you like. If you need to turn them more than 45 degrees earlier than that, simply ask! -!!! example +!!! phraseology **KPL** -> **RKA**: "ZYX, do you have any restrictions?" **RKA** -> **KPL**: "ZYX, no restrictions" KPL will place *"RKA NR"* in the label until 2.5nm clear of their airspace, to record that the coordination has been completed. diff --git a/docs/controller-skills/lsalt.md b/docs/controller-skills/lsalt.md index 25fa34299..3a602a7bd 100644 --- a/docs/controller-skills/lsalt.md +++ b/docs/controller-skills/lsalt.md @@ -27,7 +27,7 @@ An IFR aircraft is permitted below LSALT when: - They are using a "Pilot-Calculated" LSALT - They are in the course of a normal departure/approach procedure -!!! information +!!! info Pilots can calculate their own LSALT from numerous different sources, such as aerodrome 25nm and 10nm MSAs, VOR/NDB/DR tracking tolerance splays, and others. Bottom line is, if a pilot says they are using a Pilot-Calculated LSALT, they have taken full responsibility for their own separation with terrain. ## Radar Terrain Clearance Chart (RTCC) @@ -43,14 +43,14 @@ Aircraft can be cleared within CTA down to the level shown on the RTCC, and this ## Visual Once an aircraft has reported visual, LSALTs are no longer a factor. However, if clearing an aircraft to an altitude that is below Grid LSALT, Route LSALT, or MSA, the controller must append the word **"Visual"** to the clearance. This also applies to any assigned headings, or route clearances, when the aircraft is cleared to a level below LSALT. -!!! example +!!! phraseology **MAE**: "AM328, Report in-flight conditions" **AM328**: "AM328, visual" **MAE**: "AM328, Descend to A040 visual" **AM328**: "Descend to A040 visual, AM328" ## Examples -!!! example +!!! phraseology **ABC**: "Melbourne Centre, PA44, ABC, POB 2, IFR, Taxiing YSWG for YMCO, Runway 23" **BLA**: "ABC, Melbourne Centre, Squawk 3601, No reported IFR Traffic" **ABC**: "3601, ABC" @@ -59,7 +59,7 @@ Once an aircraft has reported visual, LSALTs are no longer a factor. However, if **BLA**: "ABC, no additional reported IFR traffic, expect that" **ABC**: "ABC" -!!! example +!!! phraseology **DEF**: "Brisbane Centre, PC12, DEF, POB 6, IFR, Taxiing YBUD for YROM, Runway 32" **KPL**: "DEF, Brisbane Centre, Squawk 3601, No reported IFR Traffic" **DEF**: "3601, DEF" diff --git a/docs/controller-skills/military.md b/docs/controller-skills/military.md index e9dbea479..b4b5a5526 100644 --- a/docs/controller-skills/military.md +++ b/docs/controller-skills/military.md @@ -30,10 +30,10 @@ It is the pilots responsibility to remain clear of Restricted Areas, however, th #### OCTA Outside controlled airspace, it is the responsibility of the controller to provide Safety Alerts on aircraft that will shortly enter, or have already entered, active restricted areas. -!!! example +!!! phraseology **CBW**: "Safety Alert, VFR aircraft overhead Cotter tracking southbound 2500, you will shortly be entering R430 restricted area, clearance not available, suggest immediate left turn to avoid" -!!! example +!!! phraseology **CNK**: "VFR aircraft overhead YCNK 3500 tracking westbound, confirm you will be remaining clear of the R564 restricted area?" To which they will almost always reply with either *"Affirm"* or *"Huh?"* @@ -57,7 +57,7 @@ Some Restricted Areas will be activated by NOTAM, most commonly for use by RAAF ### Aircraft operating inside Restricted Area Military aircraft are permitted to operate within their designated Restricted Area as per the relevant NOTAM. Even if this Restricted Area is inside your airspace, you have no control authority over it. -!!! example +!!! phraseology **ARA**: "DRGN379, shortly entering R604 Restricted Area, identification and control services terminated, frequency change approved. Contact me prior to leaving for airways clearance" **DRGN379**: "Wilco, DRGN379" diff --git a/docs/controller-skills/runwaymanagement.md b/docs/controller-skills/runwaymanagement.md index 49fc86fc7..f13e8bcd3 100644 --- a/docs/controller-skills/runwaymanagement.md +++ b/docs/controller-skills/runwaymanagement.md @@ -59,7 +59,7 @@ If the cloud base or visibility does not allow for visual approaches, an instrum ## Runway Changes Whilst runway changes have minimal impact on aerodrome controllers, they can drastically increase the workload for TMA controllers and have large flow on effects for enroute controllers. All runway changes should (where possible) be carefully planned and communicated, to ensure all surrounding sectors are aware of the impending change. -!!! important +!!! warning "Important" Runway changes involve all types of controllers (from Delivery to Enroute), so a large amount of coordination is required. All coordination should be done on a **point-to-point** basis, so remember to pass on any relevant details to any controllers above/around you as necessary. E.g. ADC talks to TMA, then TMA talks to ENR, then ENR talks to any subsectors/surrounding sectors as required. @@ -69,7 +69,7 @@ The aerodrome controller in charge of the ATIS should frequently check the METAR Discuss the event with the overlying TMA controller/s and nominate a time from which the new runway configuration will be used. It can be helpful to identify the last arrival who will use the current runway mode, so that both Tower and Approach have a definite change point. Once this coordination has been completed, update the ATIS and include an expectation of a runway change in the `OPR INFO` field. This should include the expected time of change and the new runway mode to be used. The TMA controller should coordinate with Enroute, who will amend any STAR clearances for aircraft projected to land after the nominated time. -!!! example +!!! phraseology **SY ADC** -> **SAN**: "The tailwind component is starting to increase a bit and the TAF indicates the wind's going to keep swinging around. Thoughts on changing to runway 34s from time 30?" **SAN** -> **SY ADC**: "There's a gap in the sequence in about 20 minutes, lets make it time 45. Last arrival in the runway 16 direction will be QFA553." **SY ADC** -> **SAN**: "Copy, changing to 34s at time 45, last arrival runway 16s QFA553." @@ -126,7 +126,7 @@ There is often confusion about how to handle helicopter operations at a controll ### Runways & Manoeuvring Area The aerodrome controllers 'own' the pavement on all runways and any taxiways or other areas defined as the 'manoeuvring area'. Aircraft require explicit takeoff and landing clearances to operate from these areas. -!!! example +!!! phraseology **SY ADC**: "RSCU209, runway 16L, cleared to land" **AD ADC**: "YOE, taxiway A2, cleared for takeoff" @@ -134,7 +134,7 @@ The aerodrome controllers 'own' the pavement on all runways and any taxiways or ### Other Locations Areas outside of the manoeuvring area are beyond the jurisdiction of the aerodrome controllers. However, since these aerodromes exist in a CTR (with controlled airspace down to the surface), a clearance is required to operate in the airspace itself. ATC is not able to issue explicit takeoff and landing clearances (as they don't own the ground on which the aircraft wishes to takeoff/land), so issue a requirement to report airborne or on the ground. -!!! example +!!! phraseology **SY ADC**: "HSZ, hotel 6, report on the ground" **SY ADC**: "HWD, report airborne" \ No newline at end of file diff --git a/docs/controller-skills/sequencing.md b/docs/controller-skills/sequencing.md index c74945b76..3b2e70af5 100644 --- a/docs/controller-skills/sequencing.md +++ b/docs/controller-skills/sequencing.md @@ -143,7 +143,7 @@ Holding is the final delaying action, useful for when a delay of 6 minutes or mo Typically 1 standard holding pattern takes 6 minutes. -!!! example +!!! phraseology **YWE:** "BNZ135, hold at APPLE, maintain FL200." **BNZ135:** "Hold at APPLE, maintain FL200, BNZ135" ... @@ -152,7 +152,7 @@ Typically 1 standard holding pattern takes 6 minutes. Although the phraseology *"Hold at (waypoint)"* is standardised from the AIP `AIP GEN 3.4`, it could mean pilots who are not familiar with published holding patterns do not fly the hold you were expecting them to. In this case, use specific instructions which gives more detail about the holding pattern. This is also applicable to holding at fixes where there is no published hold. -!!! example +!!! phraseology **ELW:** "VOZ888, hold at NABBA, inbound track 224 degrees, left hand pattern, outbound time 2 minutes, maintain FL200." **VOZ888:** "Hold at NABBA, inbound track 224 degrees, left hand pattern, outbound time 2 minutes, maintain FL200,VOZ888" ... diff --git a/docs/enroute/Brisbane Centre/ARL.md b/docs/enroute/Brisbane Centre/ARL.md index ab742bac7..ef17c29b5 100644 --- a/docs/enroute/Brisbane Centre/ARL.md +++ b/docs/enroute/Brisbane Centre/ARL.md @@ -88,7 +88,7 @@ Sequencing arrivals from the north/east into YSSY is a joint responsibility of t Aircraft from the north/east shall be assigned **runway 16L/34R** during PROPS. However, some situations may warrant the use of the main runway (16R/34L), such as heavy aircraft operationally requiring the longer runway or large volumes of traffic requiring the use of both runways to minimise delay. In this case, coordination must be conducted with Melbourne Centre or Sydney Flow (if operating) to ensure that the sequence is built in an efficient and orderly way. -!!! example +!!! phraseology **ARL** -> **BIK**: "North of Sydney, CPA21, with your concurrence will be assigned runway 34L due operational requirement" **BIK** -> **ARL**: "Concur, CPA21 runway 34L, required landing time 43 due sequence from the west" **ARL** -> **BIK**: "Runway 34L, landing time 43, CPA21" @@ -103,7 +103,7 @@ Non-jet aircraft for YSSY shall be assigned the **MEPIL** STAR. In this case, coordination should be conducted to ensure that both controllers agree and no additional conflicts are created as a result (particularly with aircraft inbound from the south/west). -!!! example +!!! phraseology **BIK:** "RXA6417, amended tracking and STAR available" **RXA6417:** "RXA6417, go ahead" **BIK:** "RXA6417, recleared direct BOREE for the BOREE4A arrival, runway 34L, maintain FL180" @@ -193,7 +193,7 @@ 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. -!!! example +!!! phraseology **TW ADC** -> **MDE**: "Next, SKV" **MDE** -> **TW ADC**: "SKV, Unrestricted" **TW ADC** -> **MDE**: "SKV" @@ -203,7 +203,7 @@ The Standard Assignable level from **TW ADC** to ARL/MDE is the lower of `A070` #### Arrivals YSTW arrivals shall be heads-up coordinated to **TW ADC** from ARL/MDE prior to **5 mins** from the boundary. -!!! example +!!! phraseology **ARL** -> **TW ADC**: "QLK6D, via MATLA DCT STWWD" **TW ADC** -> **ARL**: "QLK6D" @@ -218,7 +218,7 @@ 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. -!!! example +!!! phraseology **CFS ADC** -> **MNN**: "Next, CFH21" **MNN** -> **CFS ADC**: "CFH21, Unrestricted" **CFS ADC** -> **MNN**: "CFH21" @@ -228,7 +228,7 @@ The Standard Assignable level from **CFS ADC** to MNN is the lower of `A070` or #### Arrivals YCFS arrivals shall be heads-up coordinated to **CFS ADC** from MNN prior to **5 mins** from the boundary. -!!! example +!!! phraseology **MNN** -> **CFS ADC**: "Via KADSI, RXA6438" **CFS ADC** -> **MNN**: "RXA6438" @@ -248,7 +248,7 @@ Voiceless for all aircraft: All other aircraft going to ARL CTA will be **Heads-up** Coordinated by WLM TCU. -!!! example +!!! phraseology **WLM TCU** -> **MLD**: "QJE1597, request DCT OMGAB" **MLD** -> **WLM TCU**: "QJE1597, concur DCT OMGAB" @@ -261,7 +261,7 @@ Voiceless for all aircraft: All other aircraft coming from ARL CTA must be **Heads-up** Coordinated to WLM TCU prior to **20nm** from the boundary. -!!! example +!!! phraseology **CNK** -> **WLM TCU**: "QFA1968, request DCT UPTEB" **WLM TCU** -> **CNK**: "QFA1968, concur DCT UPTEB" @@ -270,5 +270,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **ARL**: "QFA121, identification terminated, report position to Brisbane Radio, 126.45" \ No newline at end of file diff --git a/docs/enroute/Brisbane Centre/INL.md b/docs/enroute/Brisbane Centre/INL.md index 6b7746d8e..c23bfdc5b 100644 --- a/docs/enroute/Brisbane Centre/INL.md +++ b/docs/enroute/Brisbane Centre/INL.md @@ -129,7 +129,7 @@ When operating a PROPS Runway Mode, Aircraft shall be assigned the appropriate ' These standard runway assignments may be modified strategically by the BAS or BFL controller. -!!! example +!!! phraseology 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. **BFL** -> **INL**: "All arrivals via GOMOL to be assigned 19R until further notice" @@ -193,7 +193,7 @@ 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. -!!! example +!!! phraseology **SU ADC** -> **NSA**: "Next, BNZ123, runway 31" **NSA** -> **SU ADC**: "BNZ123, unrestricted" **SU ADC** -> **NSA**: "BNZ123" @@ -202,7 +202,7 @@ The Standard Assignable level from **SU ADC** to INL(NSA/BUR) is the lower of `A Where possible (and no possible conflict exists), a higher level shall be assigned by INL(NSA/BUR) for high performance aircraft during next coordination. -!!! example +!!! phraseology **SU ADC** -> **NSA**: "Next, VOZ924, runway 31" **NSA** -> **SU ADC**: "VOZ924, F120" **SU ADC** -> **NSA**: "F120, VOZ924" @@ -211,7 +211,7 @@ Where possible (and no possible conflict exists), a higher level shall be assign NSA must ensure all YBSU arrivals have been assigned a STAR, unless the pilot is unable to accept one. YBSU arrivals shall be coordinated to **SU ADC** from NSA prior to **5 mins** from the boundary. -!!! example +!!! phraseology **NSA** -> **SU ADC**: "via ITIDE2W Arrival, JST731" **SU ADC** -> **NSA**: "JST731" @@ -249,7 +249,7 @@ 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. -!!! example +!!! phraseology **CFS ADC** -> **INL**: "Next, BNZ185" **INL** -> **CFS ADC**: "BNZ185, Unrestricted" **CFS ADC** -> **INL**: "BNZ185" @@ -259,7 +259,7 @@ The Standard Assignable level from **CFS ADC** to INL is the lower of `A070` or #### Arrivals YCFS arrivals shall be coordinated to **CFS ADC** from INL prior to **5 mins** from the boundary. -!!! example +!!! phraseology **INL** -> **CFS ADC**: "via IDNER, VET" **CFS ADC** -> **INL**: "VET" @@ -272,14 +272,14 @@ By default, **OK TCU** owns the airspace within the **R654A-D** restricted areas #### Departures All aircraft from AMB/OK TCU to INL(All) require Heads-up coordination prior to the boundary. Expect this coordination to be completed a short time after the aircraft becomes airborne (pending controller workload). -!!! example +!!! phraseology **AMB TCU** -> **NSA**: "via COWIE, BUCK03." **NSA** -> **AMB TCU**: "BUCK03, `F190`" #### Arrivals/Overfliers All aircraft transiting from INL(All) to **OK TCU** and **AMB TCU** must be heads-up coordinated prior to **20nm** from the boundary. Operations within **OK TCU** and **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels. ENR and TCU controllers should coordinate to determine the most suitable level. -!!! example +!!! phraseology **GOL** -> **AMB TCU**: "via HUUGO, STAL13, what level can I assign?" **AMB TCU** -> **GOL**: "STAL13, `A090`" **GOL** -> **AMB TCU**: "`A090`, STAL13" @@ -289,5 +289,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **INL**: "QFA121, identification terminated, report position to Brisbane Radio, 126.45" \ No newline at end of file diff --git a/docs/enroute/Brisbane Centre/ISA.md b/docs/enroute/Brisbane Centre/ISA.md index a5d1bd517..ba9941c1d 100644 --- a/docs/enroute/Brisbane Centre/ISA.md +++ b/docs/enroute/Brisbane Centre/ISA.md @@ -34,7 +34,7 @@ Voice may be used in lieu when applicable. ISA is responsible for **ARA**, **STR**, **WEG**, and **CVN** when they are offline. ## Extending -!!! Warning +!!! warning "Important" Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety. ## Sector Responsibilities @@ -83,7 +83,7 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **ISA**: "QFA121, identification terminated, report position to Brisbane Radio, 126.45" ### International (AYPM) @@ -92,6 +92,6 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio ### International (WAAF) As per [Standard coordination procedures](../../../controller-skills/coordination/#other-units), Heads-up Coordination required for all aircraft prior to **30 mins** from boundary. -!!! example +!!! phraseology **ARA** -> **WAAF CTR**: "Estimate, CEB40, TOREX time 59, F360" **WAAF CTR** -> **ARA**: "CEB40, F360" \ No newline at end of file diff --git a/docs/enroute/Brisbane Centre/KEN.md b/docs/enroute/Brisbane Centre/KEN.md index 8042225f3..0ddda171b 100644 --- a/docs/enroute/Brisbane Centre/KEN.md +++ b/docs/enroute/Brisbane Centre/KEN.md @@ -220,7 +220,7 @@ Refer to [Reclassifications](#hm-ctr) for operations when HM ADC is offline. #### Departures Departures from YBHM in to SWY Class C will be coordinated when ready for departure. -!!! example +!!! phraseology **HM ADC** -> **SWY**: "Next, QFA797" **SWY** -> **HM ADC**: "QFA797, Unrestricted" **HM ADC** -> **SWY**: "QFA797" @@ -229,7 +229,7 @@ The Standard Assignable level from HM ADC to SWY is the lower of `A050` or the ` #### Arrivals YBHM arrivals shall be heads-up coordinated to **JM ADC** from SWY prior to **5 mins** from the boundary. -!!! example +!!! phraseology **SWY** -> **HM ADC**: "Via OPOSI for RNP U RWY 32, JST848” **HM ADC** -> **SWY**: "JST848, RNP U RWY 32" @@ -240,5 +240,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **ISA**: "QFA121, identification terminated, report position to Brisbane Radio, 126.45" \ No newline at end of file diff --git a/docs/enroute/Brisbane Centre/TRT.md b/docs/enroute/Brisbane Centre/TRT.md index 61c4fc15a..97be6e070 100644 --- a/docs/enroute/Brisbane Centre/TRT.md +++ b/docs/enroute/Brisbane Centre/TRT.md @@ -39,7 +39,7 @@ When **BRM ADC** is offline, BRM CTR (Class D/E `SFC` to `A055`) reverts to Clas If choosing *not* to provide a top down service, consider publishing an **ATIS Zulu** for the aerodrome, to inform pilots about the airspace reclassification. The *More ATIS* plugin has a formatted Zulu ATIS message. ## Extending -!!! Warning +!!! warning "Important" Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety. ## Sector Responsibilities @@ -104,7 +104,7 @@ BRM ADC is responsible for the Class D airspace `SFC` to `A055`, as well as the #### Departures Departures from YBRM in to ASH CTA will be coordinated when ready for departure. -!!! example +!!! phraseology **BRM ADC** -> **ASH**: "Next, ANO333" **ASH** -> **BRM ADC**: "ANO333, Unrestricted" **BRM ADC** -> **ASH**: "ANO333" @@ -114,7 +114,7 @@ The Standard Assignable level from BRM ADC to TRT(ASH) is the lower of `A050` or #### Arrivals YBRM arrivals shall be heads-up coordinated to **BRM ADC** from TRT prior to **5 mins** from the boundary. -!!! example +!!! phraseology **TRT** -> **BRM ADC**: "Via SAFIR, FD621” **BRM ADC** -> **TRT**: "FD621" @@ -145,12 +145,12 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **ISA**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" ### International (WAAF) As per [Standard coordination procedures](../../../controller-skills/coordination/#other-units), Heads-up Coordination required for all aircraft prior to **30 mins** from boundary. -!!! example +!!! phraseology **TRT** -> **WAAF CTR**: "Estimate, SIA236, KIKEM time 21, F320" **WAAF CTR** -> **TRT**: "SIA236, F320" \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/ASP.md b/docs/enroute/Melbourne Centre/ASP.md index 52f6f76ba..c1afd8757 100644 --- a/docs/enroute/Melbourne Centre/ASP.md +++ b/docs/enroute/Melbourne Centre/ASP.md @@ -42,7 +42,7 @@ When **AS ADC** is offline, AS CTR (Class D and C `SFC` to `F125`) within 80 DME If choosing *not* to provide a top down service, consider publishing an **ATIS Zulu** for the aerodrome, to inform pilots about the airspace reclassification. The *More ATIS* plugin has a formatted Zulu ATIS message. ## Extending -!!! Warning +!!! warning "Important" Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety. ## Surveillance Coverage @@ -83,7 +83,7 @@ Refer to [Reclassifications](#as-ctr) for operations when AS ADC is offline. #### Departures Departures from YBAS in to ASP Class C will be coordinated when ready for departure. -!!! example +!!! phraseology **AS ADC** -> **ASP**: "Next, QFA797" **ASP** -> **AS ADC**: "QFA797, Unrestricted" **AS ADC** -> **ASP**: "QFA797" @@ -92,7 +92,7 @@ The Standard Assignable level from **AS ADC** to ASP is the lower of `A070` or t #### Arrivals YBAS arrivals shall be heads-up coordinated to **AS ADC** from ASP prior to **5 mins** from the boundary. -!!! example +!!! phraseology **ASP** -> **AS ADC**: "Via SADEL, QFA1956” **AS ADC** -> **ASP**: "QFA1956" @@ -108,5 +108,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **ASP**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/BIK.md b/docs/enroute/Melbourne Centre/BIK.md index 2876c57da..da9cd2c17 100644 --- a/docs/enroute/Melbourne Centre/BIK.md +++ b/docs/enroute/Melbourne Centre/BIK.md @@ -49,7 +49,7 @@ When **NW TCU** is online, R421 is activated and administered by the TCU control During times of high traffic, NW TCU may request the release of R420F up to `F300`. -!!! example +!!! phraseology **NW TCU** -> **WOL**: "There's a preplanned military exercise about to commence, request release of R420F up to F300" **WOL** -> **NW TCU**: "R420F released to you F125 to F300" **NW TCU** -> **WOL**: "R420F released F125 to F300" @@ -81,7 +81,7 @@ Sequencing arrivals from the west into YSSY is a joint responsibility of GUN and Aircraft from the south/west shall be assigned **runway 16R/34L** during PROPS. However, some situations may warrant the use of the alternate runway (16L/34R), such as heavy aircraft operationally requiring the longer runway from the north or large volumes of traffic requiring the use of both runways to minimise delay. In this case, coordination must be conducted with Brisbane Centre or Sydney Flow (if operating) to ensure that the sequence is built in an efficient and orderly way. -!!! example +!!! phraseology **BIK** -> **ARL**: "Southwest of Sydney, VOZ421, with your concurrence will be assigned runway 34R for sequencing" **ARL** -> **BIK**: "Concur, VOZ421 runway 34R, required landing time 22 due sequence from the north" **BIK** -> **ARL**: "Runway 34R, landing time 22, VOZ421" @@ -96,7 +96,7 @@ Non-jet aircraft for YSSY shall be assigned the **ODALE** STAR. In this case, coordination should be conducted to ensure that both controllers agree and no additional conflicts are created as a result (particularly with aircraft inbound from the north/east). -!!! example +!!! phraseology **BIK:** "JST421, amended tracking and STAR available" **JST421:** "JST421, go ahead" **BIK:** "JST421, recleared direct AKMIR thence WELSH, ODALE, for the ODALE7 arrival, runway 34R, maintain FL350" @@ -218,7 +218,7 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **BIK**: "QFA121, identification terminated, report position to Brisbane Radio, 124.65" ### BIK Internal diff --git a/docs/enroute/Melbourne Centre/ELW.md b/docs/enroute/Melbourne Centre/ELW.md index 8f0709d5b..56d6d1f8a 100644 --- a/docs/enroute/Melbourne Centre/ELW.md +++ b/docs/enroute/Melbourne Centre/ELW.md @@ -172,7 +172,7 @@ Refer to [Reclassifications](#ay-ctr) for operations when AY ADC is offline. #### Departures Departures from YMAY in to BLA Class C will be coordinated when ready for departure. -!!! example +!!! phraseology **AY ADC** -> **BLA**: "Next, RXA6772" **BLA** -> **AY ADC**: "RXA6772, Unrestricted" **AY ADC** -> **BLA**: "RXA6772" @@ -182,7 +182,7 @@ The Standard Assignable level from **AY ADC** to BLA is the lower of `A070` or t #### Arrivals YMAY arrivals shall be heads-up coordinated to **AY ADC** from BLA prior to **5 mins** from the boundary. -!!! example +!!! phraseology **BLA** -> **AY ADC**: "via VEGRU1 arrival, QLK38" **AY ADC** -> **BLA**: "QLK38, VEGRU1 arrival" @@ -193,5 +193,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **ELW**: "QFA121, identification terminated, report position to Brisbane Radio, 124.65" \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/HUO.md b/docs/enroute/Melbourne Centre/HUO.md index 231a7c9ec..b0af1ce14 100644 --- a/docs/enroute/Melbourne Centre/HUO.md +++ b/docs/enroute/Melbourne Centre/HUO.md @@ -35,7 +35,7 @@ HUO may choose to operate either YMHB or YMLT (or both) aerodromes top down, inc If HUO chooses to operate top down to either aerodrome, they must administer all relevant airspace within the appropriate TMA, including the class D CTR. -!!! important +!!! warning "Important" Ensure you are familiar with the aerodrome procedures for [Launceston](../../../aerodromes/Launceston) and [Hobart](../../../aerodromes/Hobart) before extending top down, and are aware of the limited surveillence coverage available in the lower levels of the TMA. !!! tip @@ -104,5 +104,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **HUO**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/HYD.md b/docs/enroute/Melbourne Centre/HYD.md new file mode 100644 index 000000000..a8c598500 --- /dev/null +++ b/docs/enroute/Melbourne Centre/HYD.md @@ -0,0 +1,163 @@ +--- + title: Hyden (HYD) +--- + +--8<-- "includes/abbreviations.md" +## Positions + +| Name | Callsign | Frequency | Login ID | +| ---- | -------- | --------- | -------- | +| **Hyden** | **Melbourne Centre** | **118.200** | **ML-HYD_CTR** | +| Pingelly† | Melbourne Centre | 133.900 | ML-PIY_CTR | +| Cross† | Melbourne Centre | 135.800 | ML-CRS_CTR | +| Jarrah† | Melbourne Centre | 120.300 | ML-JAR_CTR | +| Leeman† | Melbourne Centre | 122.400 | ML-LEA_CTR | +| Grove† | Melbourne Centre | 133.800 | ML-GVE_CTR | +| Geraldton† | Melbourne Centre | 134.200 | ML-GEL_CTR | + +† *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new} + +### CPDLC +The Primary Communication Method for HYD is Voice. + +[CPDLC](../../../client/cpdlc) may be used in lieu when applicable. + +The CPDLC Station Code is `YHYD`. + +!!! tip + Even though HYD's Primary Communication Method is Voice, CPDLC may be used for Overfliers. + +## Airspace +
+![Hyden Airspace](../assets/piy.png){ width="700" } +
Pingelly Airspace
+
+ +## Sector Responsibilities +### Pingelly (PIY) +PIY will provide final sequencing actions to ensure aircraft comply with their FF times prior to entering the Perth TCU. PIY is also responsible for issuing STAR Clearances for aircraft bound for YPJT, and Non-jets bound for YPPH and YPEA. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. + +For aircraft overflying the PH TCU place `O/FLY` in the LABEL DATA field. + +### Leeman (LEA) +LEA is responsible for assigning and issuing STAR clearance to aircraft inbound to Perth via `IPMOR`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. + +!!! note + Controllers should be aware that VHF coverage near the LEA/IND border may be limited. Controllers should strive to issue HF frequencies and transfer of communications instruction prior to 160 NM PH DME. + +### Grove (GVE) +GVE is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `JULIM` and `SAPKO`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. + +### Hyden (HYD) +HYD is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `KABLI`/`MALUP`, `DAYLR` and `LAVEX`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. + +### Cross (CRS) / Geraldton (GEL) +Just keeping them separated! + +### Jarrah (JAR) +JAR is responsible for assigning and issuing arrival clearance to aircraft inbound to Perth via `SOLUS`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. + +!!! note + Controllers should be aware there may be limited ADS-B coverage around Albany (YABA). Expect some areas of Class E airspace to be outside surveillance coverage. [Procedural Standards](../../../separation-standards/procedural) may need to be used in these cases. + +### Sequencing in to YPPH +Aircraft assigned the **same runway** inbound via **JULIM** and **SAPKO**, 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. + +## YPPH Runway Modes +### Southwest Plan +With the Southwest Plan active, arrivals shall be processed to either runway 21 or 24 based on their feeder fix, as per the table below: + +| Feeder Fix | Assigned Runway | +| --- | --- | +| JULIM | 21 | +| SAPKO | 21 | +| IPMOR | 21 | +| KABLI | 24 (or 21 if operationally required) | +| LAVEX | 24 | +| SOLUS | 24 | + +### Northeast Plan +With the Northeast Plan active (runways 03 and 06 in use), all arrivals shall be processed to runway 03. + +## YPJT Arrivals +To facilitate smooth movement of traffic in the Perth TCU, IFR Arrivals to YPJT shall be assigned a STAR in accordance with the *YPPH Runway Mode*: + +| Feeder Fix | 03/06 | 21/24 | +| ------------------- | ----- | ----- | +| WOORA | Golf | WOORA PH JT (No STAR) | +| LAVEX | Golf | Romeo | +| KABLI (Jet) | Golf | Romeo | +| MALUP (Non-Jet) | Whiskey | Romeo (via KABLI) | + +!!! note + Assigning a STAR to YPJT Arrivals still does not meet [voiceless coordination requirements](#arrivalsoverfliers) to PH TCU. All YPJT Arrivals must be **heads-up coordinated**, including those assigned a STAR. + +## STAR Clearance Expectation + +### Handoff +Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff: + +| Transferring Sector | Receiving Sector | ADES | Notes | +| ---- | -------- | --------- | --------- | +| GVE, CRS, HYD | PIY | YPPH, YPEA | Non-jets only | +| GVE, CRS, HYD | PIY | YPJT | | +| GEL | LEA | YPPH | | + +### First Contact +Aircraft being transferred from the following sectors shall be given STAR Clearance on first contact: + +| Transferring Sector | Receiving Sector | ADES | Notes | +| ---- | -------- | --------- | --------- | +| OLW(MEK, MTK, MZI) | GVE, HYD | YPPH, YPEA | Jets only | +| ASP(ESP) | HYD | YPPH, YPEA | Jets only | +| GVE, CRS, HYD | PIY | YPPH, YPEA | Non-jets only | +| GVE, CRS, HYD | PIY | YPJT | | +| GEL, IND | LEA | YPPH | | +| IND | GEL, LEA, JAR | YPPH | | + +## Coordination +### PH TCU +#### Airspace +The PH TCU is responsible for the airspace within 36 DME of the PH VOR, `SFC` to `F245`. + +Refer to [Perth TCU Airspace Division](../../../terminal/perth/#airspace-division) for information on airspace divisions when **PHD** is online. + +!!! note + A significant portion of the TMA airspace south of the PH VOR (roughly 20 DME onwards) is classified Class E with a lower limit of `F125`. Aircraft arriving from this direction from `F130` and above shall be instructed to leave and re-enter controlled airspace on descent to the standard assignable level (or other appropriate altitude). + +#### Arrivals/Overfliers +Voiceless for all aircraft: + +- With ADES **YPPH**; and +- Assigned a STAR; and +- Assigned `A090` + +All other aircraft coming from PIY CTA must be **Heads-up** Coordinated to PH TCU prior to **20nm** from the boundary. + +#### Departures +Voiceless for all aircraft: + +- Tracking via a Procedural SID terminus; and +- Assigned the lower of `F180` or the `RFL` + +All other aircraft going to PIY CTA will be **Heads-up** Coordinated by PH TCU. + +### Enroute +As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary. + +### HYD Internal +Changes to CFL are permitted up to the boundary from GVE, CRS and HYD to PIY. + +All else is Voiceless, no changes to route or CFL within **20nm** to boundary. + +That being said, it is *advised* that HYD(All) gives **Heads-up Coordination** prior to **20nm** in the following scenarios: +- JAR to PIY for all aircraft +- LEA to PIY for all aircraft + +### IND (Oceanic) +As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. + +Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. + +!!! phraseology + **LEA**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/OLW.md b/docs/enroute/Melbourne Centre/OLW.md index ab425173d..3c562ef1d 100644 --- a/docs/enroute/Melbourne Centre/OLW.md +++ b/docs/enroute/Melbourne Centre/OLW.md @@ -70,7 +70,7 @@ Refer to [Reclassifications](#ka-ctr) for operations when KA ADC is offline. #### Departures Departures from YPKA in to OLW CTA will be coordinated when ready for departure. -!!! example +!!! phraseology **KA ADC** -> **OLW**: "Next, OHN" **OLW** -> **KA ADC**: "OHN, Unrestricted" **KA ADC** -> **OLW**: "OHN" @@ -79,7 +79,7 @@ The Standard Assignable level from KA ADC to OLW is the lower of `A050` or the ` #### Arrivals YPKA arrivals shall be heads-up coordinated to **KA ADC** from OLW prior to **5 mins** from the boundary. -!!! example +!!! phraseology **OLW** -> **KA ADC**: "Via MCNAB, QFA1214 for the RNP U RWY 26” **KA ADC** -> **OLW**: "QFA1214, RNP U RWY 26" @@ -107,5 +107,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **OLW**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" \ No newline at end of file diff --git a/docs/enroute/Melbourne Centre/PIY.md b/docs/enroute/Melbourne Centre/PIY.md index 3404d9eec..17a654b80 100644 --- a/docs/enroute/Melbourne Centre/PIY.md +++ b/docs/enroute/Melbourne Centre/PIY.md @@ -160,5 +160,5 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **PIY**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" diff --git a/docs/enroute/Melbourne Centre/YWE.md b/docs/enroute/Melbourne Centre/YWE.md index e238c2abb..00c00afe1 100644 --- a/docs/enroute/Melbourne Centre/YWE.md +++ b/docs/enroute/Melbourne Centre/YWE.md @@ -35,7 +35,7 @@ The CPDLC Station Code is `YYWE`.
## Extending -!!! Warning +!!! warning "Important" Due to the large geographical area covered by this sector and it's neighbours, controllers are reminded of their obligations under the [ATS Policy](https://vatpac.org/publications/policies) when extending. Ensure that you have sufficiently placed visibility points to cover your primary sector and any secondary, extended sectors in their entirety. ## Sector Responsibilities diff --git a/docs/events/milkrun/aerodrome.md b/docs/events/milkrun/aerodrome.md index 67e6c9ab9..f275c13d5 100644 --- a/docs/events/milkrun/aerodrome.md +++ b/docs/events/milkrun/aerodrome.md @@ -69,7 +69,7 @@ Runway Modes should be selected for maximum aircraft movements, if the winds per       - **16A27D**; or       - **09A16D** -!!! Reminder +!!! info "Reminder" For dry runways, the crosswind limitation is 20kt, and the tailwind limitation is 5kt. For wet runways, no tailwind component is permitted. Remember these limitations in selecting the runway mode which is best optimised and works within these limitations #### Non-Standard Runway Modes @@ -92,5 +92,5 @@ ADC should be aiming for **90 second** spacing between subsequent departures in ### Line Up It is best practice for ADC to line-up aircraft on the runway as soon as possible, ie, as soon as the landing aircraft has passed them, or as soon as the departing aircraft has started to roll. This minimises time spent waiting for aircraft to taxi in to position, and potentially cause gaps in the sequence and/or go-arounds. -!!! suggestion +!!! success "Suggestion" Appending the phrase "Be ready immediate" to the end of a line up instruction can ensure the pilot has all checklists completed, and is ready to commence takeoff roll as soon as the clearance is given. This reduces airborne delays, and potential go-around situations \ No newline at end of file diff --git a/docs/events/milkrun/enroute.md b/docs/events/milkrun/enroute.md index 584c78e8d..24e9098c5 100644 --- a/docs/events/milkrun/enroute.md +++ b/docs/events/milkrun/enroute.md @@ -10,13 +10,13 @@ The most important job of the ELW/BLA controller is the sequencing for YMML. Lik This is most important for the BLA transfer to GUN, as GUN does not have a lot of airspace to complete the YSSY sequence. BLA should aim to handoff aircraft to GUN approximately **50nm** to the boundary, unless there is a restriction (which is quite rare). Note that other aircraft going to GUN airspace (ie: Other aircraft on the YMML-YSSY route) are **not** considered a 'Restriction', as the GUN controller can already see them as Blue (Announced) on their display. -!!! Reminder +!!! info "Reminder" [Handoff Rules](../../../controller-skills/coordination/#handoffs) permit turns of up to **45 degrees left/right**, and **climb/descent to any level** after handoff. Keep this in mind when considering how early you can handoff aircraft to the next sector ## Arrival Sequencing Enroute controllers should be aiming for **2 minute** spacing at the feeder fix between subsequent arrivals. This can be reduced slightly to no less than **10nm**, unless **single runway operations** are in use. -!!! Reminder +!!! info "Reminder" At YMML, aircraft on the LIZZI and BOYSE STARs are considered to be on the same STAR for sequencing purposes. Ie, an aircraft via BOYSE must be sequenced 2 minutes behind an aircraft via LIZZI, and vice versa ### Speed Control @@ -57,7 +57,7 @@ Aircraft can be rerouted on first contact via AKMIR, ODALE, then assigned the OD Although this action may be beneficial to the arrival flow for both Enroute and Approach, it goes against the [Standard runway and STAR assignment](../../enroute/Melbourne Centre/BIK/#sequencing-into-yssy) for YSSY Arrivals from the South-west, so must still be coordinated to SAS or SFL (if online) -!!! example +!!! phraseology **GUN** -> **SFL**: "QFA494 will be via ODALE for 34R" **SFL** -> **GUN**: "QFA494 via ODALE, 34R, Roger" diff --git a/docs/events/milkrun/terminal.md b/docs/events/milkrun/terminal.md index effed33d5..8bf30628c 100644 --- a/docs/events/milkrun/terminal.md +++ b/docs/events/milkrun/terminal.md @@ -47,6 +47,6 @@ Depending on the Runway Mode, additional portions of airspace may be released be ## Go-arounds When there is a go-around in the middle of a bumper-to-bumper sequence, a fair bit of work needs to be done. Obviously there is the additional work of having to vector the aircraft that has gone around back for an approach, but also trying to find a gap for them in the sequence, where none such gap currently exists. This is an important time to use coordination, and get the Enroute controller to create one for you. -!!! example +!!! phraseology **MAE** -> **ELW**: "We've had a Go around. Additional 2 minute delay for all aircraft in this sequence please." **ELW** -> **MAE**: "Copy, additional 2 minute delay for all aircraft in this sequence." \ No newline at end of file diff --git a/docs/events/milkrun/workload.md b/docs/events/milkrun/workload.md index 7d6defce2..40b72d328 100644 --- a/docs/events/milkrun/workload.md +++ b/docs/events/milkrun/workload.md @@ -43,7 +43,7 @@ To mitigate this, pushback requests may be done on **ACD** frequency, to balance 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 +!!! phraseology **ML SMC** -> **ML ACD**: "It's getting quite busy. Happy to implement Pushback requests on your frequency?" **ML ACD** -> **ML SMC**: "Understood, affirm" **ML SMC** -> **ML ACD**: "Thanks, I'll talk to Tower" diff --git a/docs/events/worldflight/Aerodromes/adelaide.md b/docs/events/worldflight/Aerodromes/adelaide.md index 6e70ece3e..002f0b79c 100644 --- a/docs/events/worldflight/Aerodromes/adelaide.md +++ b/docs/events/worldflight/Aerodromes/adelaide.md @@ -35,7 +35,7 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. -!!! example +!!! phraseology **AD ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YPPH VIA GILES Q33 ESP Q158 PH DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### SMC Frequency @@ -97,7 +97,7 @@ Work through the OzStrips Preactive bay from *bottom to top* when sending PDCs. **Do not** give taxi instructions **beyond** your area of responsibility. Instruct aircraft to hold short of taxiways where responsibility changes to the next controller. -!!! example +!!! phraseology **AD SMC:** "QFA7448, Taxi via F2, A, Hold Short of K" **QFA7448:** "Taxi via F2, A, Hold Short of K, QFA7448" When QFA7448 is approaching K: @@ -201,7 +201,7 @@ Due to the tight sequence, there are times that [Wake Turbulence Separation](../ When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. -!!! example +!!! phraseology **AD ADC:** "QFA887, A330 has just departed on the crossing runway. Caution Wake Turbulence. Runway 30, Cleared for Takeoff" **QFA887:** "Cleared for Takeoff Runway 30, QFA887" diff --git a/docs/events/worldflight/Aerodromes/brisbane.md b/docs/events/worldflight/Aerodromes/brisbane.md index e2c687231..353b53b6a 100644 --- a/docs/events/worldflight/Aerodromes/brisbane.md +++ b/docs/events/worldflight/Aerodromes/brisbane.md @@ -26,7 +26,7 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. -!!! example +!!! phraseology **BN ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YSSY VIA SANEG H91 IGDAM H652 TESAT DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams diff --git a/docs/events/worldflight/Aerodromes/darwin.md b/docs/events/worldflight/Aerodromes/darwin.md index 6a63da96a..3126d4549 100644 --- a/docs/events/worldflight/Aerodromes/darwin.md +++ b/docs/events/worldflight/Aerodromes/darwin.md @@ -20,7 +20,7 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. -!!! example +!!! phraseology **DN ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO AYPY VIA RUPEG DCT IGOPO B598 ESKIM DCT GUMBU DCT PY DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams @@ -110,7 +110,7 @@ Due to the tight sequence, there are times that [Wake Turbulence Separation](../ When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. -!!! example +!!! phraseology **DN ADC:** "BNZ1193, A380 has just departed ahead. Caution Wake Turbulence. Runway 29, Cleared for Takeoff" **BNZ1193:** "Cleared for Takeoff Runway 29, BNZ1193" @@ -120,13 +120,13 @@ ADC should assess traffic congestion on both the north and south sides of the ae #### Runway 11 Aircraft intended for the northern aprons should be instructed to vacate at either **E2** or via the **northern grass** if they miss it. Aircraft intended for the southwestern apron should be instructed to vacate on any taxiway to the right. -!!! example +!!! phraseology **DN ADC**: "QFA25, vacate to the right, runway 11, cleared to land" #### Runway 29 Aircraft intended for the northern aprons should be instructed to vacate at either **B2** or **runway 36**. This way, any pilots who miss the crossing runway can still vacate via **C4**. Aircraft intended for the southwestern apron should be instructed to vacate at either **C3** or **A1**. -!!! important +!!! warning "Important" It is **vital** that aircraft do not vacate left (south) prior to runway 36, as this will cause significant conflict with the outbound taxi route and likely to lead to the aircraft being required to disconnect. If an aircraft slows down rapidly, consider instructing them to vacate to the right via **B2** or reminding them to keep their speed up and roll through to vacate at **C3**. ## ATIS diff --git a/docs/events/worldflight/Aerodromes/perth.md b/docs/events/worldflight/Aerodromes/perth.md index b6918066c..67e4b5786 100644 --- a/docs/events/worldflight/Aerodromes/perth.md +++ b/docs/events/worldflight/Aerodromes/perth.md @@ -28,7 +28,7 @@ Land and Hold Short Operations (LAHSO) will be in use, allowing aircraft to land Runway 03 LDA to Runway **06/24** Intersection is **2355m**. -!!! example +!!! phraseology **PH ADC:** "GTI1471, 737 departing on Crossing Runway. Hold Short Runway 06. Cleared to land Runway 03" **GTI1471:** "Cleared to land Runway 03, GTI1471" **PH ADC:** "QFA365, 747 landing on Crossing Runway will Hold Short. Runway 06, Cleared for takeoff" @@ -46,7 +46,7 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. -!!! example +!!! phraseology **PH ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO WIII VIA AVNEX Y15 ESDEG Q587 IGLUT T58 SAPDA A585 IPKON IPKO2G. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams @@ -131,7 +131,7 @@ As per the [YPPH Aerodrome SOPs](../../../../../../aerodromes/classc/Perth/#mane Instead of SMC coordinating runway crossings with ADC, aircraft taxiing via **N** and **C** shall be instructed to **contact ADC** at Holding Point **D**, where ADC will give them taxi instructions on their frequency. No coordination is required between SMC and ADC for this. -!!! example +!!! phraseology **PH SMC:** "DAL209, Taxi Holding point D, Runway 21. Expect Holding Point P for departure." **DAL209:** "Taxi Holding Point D, Runway 21, DAL209" *(at Holding Point)* @@ -176,7 +176,7 @@ As per the [YPPH Aerodrome SOPs](../../../../../../aerodromes/classc/Perth/#mane Instead of SMC coordinating runway crossings with ADC, aircraft taxiing via **N** and **C** shall be instructed to **contact ADC** at Holding Point **D**, where ADC will give them taxi instructions on their frequency. No coordination is required between SMC and ADC for this. -!!! example +!!! phraseology **PH SMC:** "DAL209, Taxi Holding point D, Runway 21. Expect Holding Point P for departure." **DAL209:** "Taxi Holding Point D, Runway 21, DAL209" *(at Holding Point)* @@ -214,7 +214,7 @@ Due to the tight sequence, there are times that [Wake Turbulence Separation](../ When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. -!!! example +!!! phraseology **PH ADC:** "EVY30, 777 has just departed from the crossing runway. Caution Wake Turbulence. Runway 24, Cleared to Land" **EVY30:** "Cleared to Land Runway 24, EVY30" diff --git a/docs/events/worldflight/Aerodromes/portmoresby.md b/docs/events/worldflight/Aerodromes/portmoresby.md index 227643cee..99fa14804 100644 --- a/docs/events/worldflight/Aerodromes/portmoresby.md +++ b/docs/events/worldflight/Aerodromes/portmoresby.md @@ -24,7 +24,7 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. -!!! example +!!! phraseology **AYPY ACD:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YBBN VIA NUPTA DCT APISO B462 MK V153 MUNAR Y61 RUROX Y177 BN DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams @@ -103,7 +103,7 @@ Due to the tight sequence, there are times that [Wake Turbulence Separation](../ When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. -!!! example +!!! phraseology **AYPY ADC:** "ANG3, 747 has just departed. Caution Wake Turbulence. Runway 32L, Cleared for Takeoff" **ANG3:** "Cleared for Takeoff Runway 32L, ANG3" diff --git a/docs/events/worldflight/Aerodromes/sydneyarr.md b/docs/events/worldflight/Aerodromes/sydneyarr.md index b1d62ad93..c56fcc5c4 100644 --- a/docs/events/worldflight/Aerodromes/sydneyarr.md +++ b/docs/events/worldflight/Aerodromes/sydneyarr.md @@ -49,7 +49,7 @@ To avoid creating conflict for SMC, ADC shall instruct all arriving aircraft to | 34L | A2 (left) or B9 (right) | | 34R | T2 or U1 | -!!! example +!!! phraseology **SY ADC**: "JST554, vacate via B9 to the right, runway 34L, cleared to land" ### Runway Efficiency @@ -57,7 +57,7 @@ The success of the event will be decided by ADC's ability to minimise runway occ While runway crossings will be minimised, should a crossing be required, instruct a landing aircraft to report when they are assured of taking the assigned rapid exit. Once that assurance has been received, instruct SMC to cross the applicable aircraft (provided they are further upwind than the assured runway exit). -!!! example +!!! phraseology **SY ADC**: "QFA451, report when assured of vacating via B9 to the right, runway 34L, cleared to land" If any aircraft need to depart during the arrival window, ensure that maximum efficiency is achieved by instructing them to line up as soon as the landing aircraft has cleared the threshold. Avoid go arounds at all costs, and if necessary, delay the departing aircraft where a gap between two arrivals is too tight. diff --git a/docs/events/worldflight/Aerodromes/sydneydep.md b/docs/events/worldflight/Aerodromes/sydneydep.md index ca05cf850..0a3cc7180 100644 --- a/docs/events/worldflight/Aerodromes/sydneydep.md +++ b/docs/events/worldflight/Aerodromes/sydneydep.md @@ -27,7 +27,7 @@ Ensure **all flight plans** are checked for compliance with the approved WF Rout If an aircraft has filed an *incorrect* route and you need to give an amended clearance, this amendment must be specified by **individual private message**, prior to the PDC. -!!! example +!!! phraseology **SY-C_DEL:** *"AMENDED ROUTE CLEARANCE. CLEARED TO YPAD VIA KADOM H44 MAXEM Q60 KAKLU H309 AD DCT. READBACK AMENDED ROUTE IN FULL DURING PDC READBACK. STANDBY FOR PDC."* ### WorldFlight Teams @@ -102,7 +102,7 @@ PDCs will be in use by default, to avoid frequency congestion. ACD shall send a ## Coordinator Coordinator operations shall be conducted in accordance with the Sydney Aerodrome [Coordinator](../../../../aerodromes/classc/Sydney/#sydney-coordinator) procedures, using the OzStrips plugin. -!!! important +!!! warning "Important" Official WorldFlight teams should be afforded priority when requesting pushback or taxi (if no pushback required), and placed ahead of other non-official aircraft. ### OzStrips @@ -125,20 +125,20 @@ A Custom `PDC SENT` bar should be created in the Preactive window, to keep track If three strips are already present below a respective bar, any subsequent aircraft who request pushback must be instructed to remain on the Coordinator frequency, and an estimated delay given if known. Place these strips in the **Cleared Bay Queue**, but above the respective `MONITOR GROUND` bars. The bottom-most strip is always at the front of any queue. -!!! example +!!! phraseology **QFA452**: "Sydney Coordinator, Qantas 452, bay 5, request pushback" **SY COORD**: "Qantas 452, Sydney Coordinator, monitor ground 121.7" ... **VOZ318**: "Sydney Coordinator, Velocity 318, bay 39, request pushback" **SY COORD**: "Velocity 318, Coordinator, remain this frequency, approximate 5 minute delay due traffic congestion" -!!! important +!!! warning "Important" Ensure aircraft are [squawking mode C and the correct code](../../../../client/towerstrips/#strips) before instructing them to monitor ground. ### Delay Expectation Aircraft can expect **extensive** delays for Pushback during the event, possibly *multiple hours*. Try to keep pilots informed of their delay expectation, either by providing a figure in minutes, or a position in the queue. -!!! example +!!! phraseology **JST764**: "Sydney Coordinator, JST764, bay 55, request pushback" **SY COORD**: "JST764, Coordinator, remain this frequency, number 62 in the queue" @@ -151,7 +151,7 @@ With Coordinator online, aircraft will request pushback on the Coordinator frequ When workload (and holding point congestion) allows, issue pushback to the **bottom most** aircraft below the `MONITOR GROUND EAST` or `MONITOR GROUND WEST` bar (as appropriate) and move the strip to the **Pushback Bay**. -!!! important +!!! warning "Important" It is preferable to hold aircraft on the bay (where they aren't blocking taxiways or burning their holding fuel) when congestion leads to blocked holding points. Issue pushback with enough lead time to prevent large gaps in the departure sequence. ### A388 Taxi Routes @@ -188,7 +188,7 @@ To avoid creating conflict for SMC, ADC shall instruct all arriving aircraft to | 34L | A2 (left) or B9 (right) | | 34R | T2 or U1 | -!!! example +!!! phraseology **SY ADC**: "JST554, vacate via B9 to the right, runway 34L, cleared to land" ## ATIS diff --git a/docs/events/worldflight/Enroute/aypyybbn.md b/docs/events/worldflight/Enroute/aypyybbn.md index 7a1501f5a..45cd78e27 100644 --- a/docs/events/worldflight/Enroute/aypyybbn.md +++ b/docs/events/worldflight/Enroute/aypyybbn.md @@ -116,7 +116,7 @@ BFL must **voice coordinate** any changes to instructions after KPL/BUR has put BFL will **voice coordinate** to KPL/BUR any aircraft that must be rerouted via **ENLIP** for **01R/19R**. -!!! example +!!! phraseology **BFL** -> **KPL**: "PAA001 via ENLIP for 01R please" **KPL** -> **BFL**: "PAA001 via ENLIP for 01R, will be" diff --git a/docs/events/worldflight/Enroute/ybbnyssy.md b/docs/events/worldflight/Enroute/ybbnyssy.md index f7c6238b2..182b6c0aa 100644 --- a/docs/events/worldflight/Enroute/ybbnyssy.md +++ b/docs/events/worldflight/Enroute/ybbnyssy.md @@ -75,7 +75,7 @@ SFL must **voice coordinate** any changes to instructions after ARL/CNK has put SFL will **voice coordinate** to ARL/CNK any aircraft that must be rerouted via **OLTIN YAKKA MEPIL** for **16L/34R**. -!!! example +!!! phraseology **SFL** -> **ARL**: "ANZ361 via OLTIN for 34R please" **ARL** -> **SFL**: "ANZ361 via OLTIN for 34R, will be" diff --git a/docs/events/worldflight/Enroute/ypadypph.md b/docs/events/worldflight/Enroute/ypadypph.md index 794544888..96068c06e 100644 --- a/docs/events/worldflight/Enroute/ypadypph.md +++ b/docs/events/worldflight/Enroute/ypadypph.md @@ -18,7 +18,7 @@ TBD has *no Restrictions or Requirements* on YPAD departures tracking DCT **LONL ### Augusta (AUG), Forrest (FOR), Forrest West (FOW) AUG, FOR, and FOW will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. -!!! caution +!!! warning "Caution" AUG and FOR should look out for aircraft converging at **LONLY** and **LESON** respectively, at the same time and level. Use vertical separation wherever possible. ### Esperance (ESP) diff --git a/docs/events/worldflight/Enroute/ypphwiii.md b/docs/events/worldflight/Enroute/ypphwiii.md index 9b78caa29..49fa3a0e6 100644 --- a/docs/events/worldflight/Enroute/ypphwiii.md +++ b/docs/events/worldflight/Enroute/ypphwiii.md @@ -11,7 +11,7 @@ PIY has *no Restrictions or Requirements* on YPPH departures tracking DCT **ESDE ### Leeman (LEA) LEA will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. -!!! caution +!!! warning "Caution" During the 03A06D Runway Mode at YPPH, LEA should look out for aircraft converging at **ESDEG** at the same time and level. Use vertical separation wherever possible. ### Geraldton (GEL), Meekatharra (MEK), Onslow (OLW) @@ -19,7 +19,7 @@ GEL, MEK, and OLW will be responsible for ensuring the separation of aircraft in Aircraft shall have their **identification terminated** on handoff to INE, and instructed to give a **PAVNU** Position Report on first contact. -!!! example +!!! phraseology **OLW:** "BTK6081, at PAVNU, Identification terminates. Contact Brisbane Radio 123.65 with PAVNU Position Report" ### Indian East (INE) diff --git a/docs/events/worldflight/Enroute/yssyypad.md b/docs/events/worldflight/Enroute/yssyypad.md index 62a148ca2..3737f0ac2 100644 --- a/docs/events/worldflight/Enroute/yssyypad.md +++ b/docs/events/worldflight/Enroute/yssyypad.md @@ -30,7 +30,7 @@ This tracking must **only** be issued to **Light** and **Medium** Wake Turbulenc ### Griffith (GTH), Oxley (OXL) GTH and OXL will be responsible for ensuring the separation of aircraft in the Enroute phase of flight. No sequencing actions are required. -!!! caution +!!! warning "Caution" GTH should look out for aircraft converging at **BORLI** at the same time and level. Use vertical separation wherever possible. If [Runway 30 is in use at YPAD](#runway-30-at-ypad), monitor the distribution of aircraft tracking on *Flight Planned Route* VS DCT **DRINA**. diff --git a/docs/events/worldflight/Terminal Areas/adelaide.md b/docs/events/worldflight/Terminal Areas/adelaide.md index 2c8459f12..ace04129e 100644 --- a/docs/events/worldflight/Terminal Areas/adelaide.md +++ b/docs/events/worldflight/Terminal Areas/adelaide.md @@ -75,7 +75,7 @@ Due to the tight sequence, there are times that [Wake Turbulence Separation](../ When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. -!!! example +!!! phraseology **AAE:** "JST762, Traffic is BAW47C, a 747 4nm ahead. Caution Wake Turbulence" **JST762:** "JST762" diff --git a/docs/events/worldflight/Terminal Areas/brisbane.md b/docs/events/worldflight/Terminal Areas/brisbane.md index 0cd6ae327..aeedff1a2 100644 --- a/docs/events/worldflight/Terminal Areas/brisbane.md +++ b/docs/events/worldflight/Terminal Areas/brisbane.md @@ -64,7 +64,7 @@ Ensure you familiarise yourself with the applicable [Separation Standards](../.. Pass *Traffic Information* on aircraft that will come within **1.5nm** of each other on parallel approaches. -!!! example +!!! phraseology **BAN:** "UAL8317, Traffic is an A320 at your 2 o'clock for the parallel runway" #### 19R Arrivals @@ -159,7 +159,7 @@ BFL must **voice coordinate** any changes to instructions after BUR/KPL has put BFL must **voice coordinate** to KPL/BUR any aircraft that must be rerouted via **ENLIP** for **01R/19R**. -!!! example +!!! phraseology **BFL** -> **KPL**: "PAA001 via ENLIP for 01R please" **KPL** -> **BFL**: "PAA001 via ENLIP for 01R, will be" diff --git a/docs/events/worldflight/Terminal Areas/perth.md b/docs/events/worldflight/Terminal Areas/perth.md index 1dbb01507..edb1047af 100644 --- a/docs/events/worldflight/Terminal Areas/perth.md +++ b/docs/events/worldflight/Terminal Areas/perth.md @@ -67,7 +67,7 @@ Due to the tight sequence, there are times that [Wake Turbulence Separation](../ When a following aircraft is of a *lighter* [Wake Turbulence Category](../../../../../../separation-standards/waketurb/#categories) than the preceding aircraft, a traffic statement and wake turbulence **caution** shall be issued. -!!! example +!!! phraseology **PHA:** "VOZ721, Traffic is QFA25, a 747 4nm ahead. Caution Wake Turbulence" **VOZ721:** "VOZ721" diff --git a/docs/events/worldflight/Terminal Areas/sydneyarr.md b/docs/events/worldflight/Terminal Areas/sydneyarr.md index b76ea240c..76fd24a09 100644 --- a/docs/events/worldflight/Terminal Areas/sydneyarr.md +++ b/docs/events/worldflight/Terminal Areas/sydneyarr.md @@ -45,7 +45,7 @@ Ensure you familiarise yourself with the applicable [Separation Standards](../.. Pass *Traffic Information* on aircraft that will come within **1nm** of each other on parallel approaches. -!!! example +!!! phraseology **SFW:** "NPT11W, Traffic is a 767 at your 10 o'clock for the parallel runway" ## Sector Distribution @@ -92,7 +92,7 @@ SFL must **voice coordinate** any changes to instructions after ARL/CNK has put SFL must **voice coordinate** to ARL/CNK any aircraft that must be rerouted via **OLTIN YAKKA MEPIL** for **16L/34R**. -!!! example +!!! phraseology **SFL** -> **ARL**: "ANZ361 via OLTIN for 34R please" **ARL** -> **SFL**: "ANZ361 via OLTIN for 34, will be" diff --git a/docs/oceanic/Positions/IND.md b/docs/oceanic/Positions/IND.md index 0517f2c1f..ea4370297 100644 --- a/docs/oceanic/Positions/IND.md +++ b/docs/oceanic/Positions/IND.md @@ -33,7 +33,7 @@ Voice may be used in lieu when applicable. ## Extending -!!! Warning +!!! warning "Important" IND (and its subsectors) are **not permitted** to extend to any adjacent Domestic/International sectors ## STAR Clearance Expectation @@ -57,6 +57,6 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio ### International Non-Pacific As per [Standard coordination procedures](../../../controller-skills/coordination/#other-units), Heads-up Coordination required for all aircraft prior to **30 mins** from boundary. -!!! example +!!! phraseology **IND** -> **FAJO FSS**: "Estimate, SAA281, XEKOT time 44, F360" **FAJO FSS** -> **IND**: "SAA281, F360" \ No newline at end of file diff --git a/docs/oceanic/Positions/TSN.md b/docs/oceanic/Positions/TSN.md index 3a4b837d2..bfe9e1f39 100644 --- a/docs/oceanic/Positions/TSN.md +++ b/docs/oceanic/Positions/TSN.md @@ -45,7 +45,7 @@ Limited surveillance coverage exists for aircraft in CTA greater than **250nm** The COL subsector includes the AGGG and ANAU FIRs. These FIRs **do not** have their own positions, and **cannot** be split off from COL. ## Extending -!!! Warning +!!! warning "Important" TSN (and its subsectors) are **not permitted** to extend to any adjacent Domestic/International sectors ## STAR Clearance Expectation @@ -65,21 +65,21 @@ As per [Standard coordination procedures](../../../controller-skills/coordinatio ### TSN Internal As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. -!!! important +!!! warning "Important" Aircraft separated by a surveillance separation standard must be re-established at an applicable procedural standard prior to handoff to a procedural enroute sector. Aircraft leaving HWE in it's surveillance configuration must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **HWE**: "UAE845, identification terminated, report position to Brisbane Radio, 124.65" ### Pacific Oceanic + AYPM As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. -!!! important +!!! warning "Important" Aircraft separated by a surveillance separation standard must be re-established at an applicable procedural standard prior to handoff to a procedural enroute sector. Aircraft entering VATNZ airspace on the same track must be either vertically separated or laterally separated by a 10 minute longitudinal standard prior to handoff. Aircraft leaving HWE in it's surveillance configuration must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. -!!! example +!!! phraseology **HWE**: "QFA121, identification terminated, report position to Auckland Radio, 129.0" \ No newline at end of file diff --git a/docs/oceanic/index.md b/docs/oceanic/index.md index e1ca1951f..af3f3684e 100644 --- a/docs/oceanic/index.md +++ b/docs/oceanic/index.md @@ -21,7 +21,7 @@ KZAK - Oakland Oceanic NTTT - Tahiti Oceanic RJTG - Fukuoka Oceanic -!!! information +!!! info Auckland, McMurdo and Tahiti Oceanic are owned and operated by VATNZ, Fukuoka Oceanic is owned and operated by VATJPN, and Oakland Oceanic is owned and operated by the Oakland ARTCC. Under the agreement, a controller holding an oceanic endorsement may control positions within any of these FIRs. diff --git a/docs/oceanic/procedures.md b/docs/oceanic/procedures.md index eb5cf1c42..8fa45dc93 100644 --- a/docs/oceanic/procedures.md +++ b/docs/oceanic/procedures.md @@ -37,7 +37,7 @@ Refer to [Procedural Separation Standards](../../separation-standards/procedural ## HF Radio Simulated HF radio is used as the primary long-range radio communications medium. The nature of HF radio makes it highly vulnerable to atmospheric distortion and noise, and so radiotelephony (R/T) procedures on HF tend to be more formal in order to maximise clarity. -!!! Example +!!! phraseology **UAL873**: "San Francisco Radio, San Francisco Radio, UAL873 on 122.5" **ZAK_FSS**: "UAL873, San Francisco Radio, go-ahead" **UAL873**: "San Francisco Radio, UAL873 request climb FL390" @@ -47,7 +47,7 @@ Given the background noise level experienced on HF radio frequencies, flight cre Controllers must check each aircraft’s flight plan for a discrete SELCAL code. If aircraft have nominated a discrete code (for example `QR-AC`), then a SELCAL Check shall be completed. -!!! Example +!!! phraseology **TSN**: "ANZ254, standby SELCAL check." *The aircraft awaits the SELCAL check before replying.* **ANZ254**: "SELCAL check OK, ANZ254." @@ -71,7 +71,7 @@ If an aircraft fails to report its position within 3 minutes of its estimated ti ATC shall acknowledge a position report by using the aircraft's callsign. A readback of the report is not required. -!!! Example +!!! phraseology **UAL873**: "San Francisco Radio, San Francisco Radio, UAL873 Position" **ZAK_FSS**: "UAL873, San Francisco Radio" **UAL873**: "UAL873 position LHI time 1853, FL360, estimate PANDA at 1953, SANDO next. Maintaining Mach 0.84” @@ -90,7 +90,7 @@ Aircraft using time compression must be assigned the following levels for separa | 2x | FL390 | FL380 | | 4x | FL410 | FL400 | -!!! important +!!! warning "Important" Aircraft at normal speed **always** have priority over aircraft using Time Compression. ## Coordination @@ -100,6 +100,6 @@ As per [Standard coordination procedures](../../controller-skills/coordination/# ### To Other Units As per [Standard coordination procedures](../../controller-skills/coordination/#other-units), Heads-up Coordination required for all aircraft prior to **30 mins** from boundary. -!!! example +!!! phraseology **IND** -> **FAJO FSS**: "Estimate, SAA281, XEKOT time 44, F360" **FAJO FSS** -> **IND**: "SAA281, F360" \ No newline at end of file diff --git a/docs/pacific/New-Caledonia/Magenta.md b/docs/pacific/New-Caledonia/Magenta.md index b33ce9120..528a04485 100644 --- a/docs/pacific/New-Caledonia/Magenta.md +++ b/docs/pacific/New-Caledonia/Magenta.md @@ -19,7 +19,7 @@ NWWM ADC is responsible for the Class D Airspace within the NWWM CTR `SFC` to `A #### Departures All aircraft departing into NWWW TCU Class D airspace must be 'Next' coordinated to NWWW TCU. -!!! example +!!! phraseology **NWWM ADC** -> **NWWW TCU**: "Next, AEU" **NWWW TCU** -> **NWWM ADC**: "AEU, Unrestricted" **NWWM ADC** -> **NWWW TCU**: "AEU" @@ -30,7 +30,7 @@ The standard assignable level from NWWW ADC to NWWW TCU is the lower of `A050` o NWWW TCU will heads-up coordinate arrivals/overfliers prior to **5 mins** from the boundary. VFR aircraft require a level readback. -!!! example +!!! phraseology **NWWW TCU** -> **NWWM ADC**: "Via the LU1N Arrival, TPC220 for the VPT” **NWWM ADC** -> **NWWW TCU**: "TPC220, VPT" diff --git a/docs/separation-standards/assurance.md b/docs/separation-standards/assurance.md index 428ed9a1c..7ce01e2bc 100644 --- a/docs/separation-standards/assurance.md +++ b/docs/separation-standards/assurance.md @@ -107,7 +107,7 @@ Unless a level has been "locked in" for an aircraft entering your airspace, for Their CFL **cannot** be used for separation purposes. Certain aircraft may require additional time to plan restrictions, identify conflicts, etc (For example, as **ELW**, an aircraft cutting across the YMML departure/arrival path at F230), and this is where a **level check** may be useful. If you want to "lock in" a level for an aircraft coming from an adjacent sector, use the following phraseology: -!!! example +!!! phraseology **ELW** -> **YWE**: "Level Check, VOZ456, F360" **YWE** -> **ELW**: "VOZ456, F360" @@ -115,7 +115,7 @@ Any changes to VOZ456's level would now need to be coordinated by YWE, so no sur Level checks are also useful for when you have identified a conflict, and you need to assign a **different level** to the one currently assigned by the controlling sector in order to assure separation. -!!! example +!!! phraseology **BIK** -> **SDS**: "JST123, Assigned F200 due crossing traffic" **SDS** -> **BIK**: "JST123, F200" @@ -154,7 +154,7 @@ It is best to always assign the *lowest possible level* on descent when taking i This reduces controller workload by reducing the number of calls required to facilitate an aircraft's descent, and reduces the likelihood of an aircraft having their descent profile interrupted if you get distracted and/or busy. -!!! Example +!!! phraseology VOZ888 is tracking from Sydney to Melbourne via the Q29 airway to LIZZI for the LIZZI8A arrival runway 34. There are no conflicts on their route ahead, and the CTA LL is `A085`. "VOZ888, when ready, descend via the STAR to A090, QNH 1009." @@ -182,12 +182,12 @@ This is **entirely unnecessary**, and just uses up additional talking time, and #### STAR Level Restrictions Further transmissions can be saved in the busy TMA, with the use of *"Descend via STAR"* phraseology when CTA protection is in place, **only** where Level Restrictions exist on the STAR assuring aircraft remain inside CTA. -!!! Example +!!! phraseology RXA4652 is tracking via ODALE for the ODALE7 STAR to runway 34R. CTA LL is `A075`, but the STAR has built-in CTA protection (At or Above A080 at **KABLO**) "RXA4652, Sydney Approach, runway 34R, descend via the STAR to A060" -!!! Important +!!! warning "Important" **Only** use SID/STAR Level Restrictions to assure separation with CTA, Terrain, and Conflicts, when you are **very familiar** with the airspace. **VERY FEW SIDs/STARs DO THIS!** diff --git a/docs/separation-standards/classd.md b/docs/separation-standards/classd.md index 2f3ec1a57..f4a4a40de 100644 --- a/docs/separation-standards/classd.md +++ b/docs/separation-standards/classd.md @@ -15,7 +15,7 @@ Remember that in [Class D Airspace](../../controller-skills/classofairspace), IF ## Surveillance Although Surveillance standards cannot be used for separation at Class D Towers, overlying TCU/Enroute controllers can use their surveillance standards to help Class D towers achieve separation, when procedural separation is a bit awkward or impractical. -!!! example +!!! phraseology **AY ADC** -> **BLA**: "Can you advise when QLK208D is 5nm clear of DSB?" **BLA** -> **AY ADC**: "Affirm, will do" ... diff --git a/docs/separation-standards/procedural.md b/docs/separation-standards/procedural.md index 43f506243..32251748d 100644 --- a/docs/separation-standards/procedural.md +++ b/docs/separation-standards/procedural.md @@ -57,7 +57,7 @@ Longitudinal separation shall only be applied between aircraft on same or recipr Longitudinal time separation must be established by using pilot estimates and ensuring that the time between two aircraft is equal or greater than the longitudinal time separation minimum. -!!! Example +!!! phraseology "ABC, Cross ALPHA at time 1051 or later" "DEF, Hold at BRAVO to leave BRAVO at time 2215 or later" @@ -219,14 +219,14 @@ Using the time standard, aircraft are considered to have entered the conflict ar When aircraft **are** in lateral conflict, a vertical standard must be applied for that period. -!!! example +!!! phraseology "Climb to reach (vertically separated level) by (prior to entering lateral conflict)" "Expect requested level at (time aircraft leaves lateral conflict)" #### Distance Standard Use BRL to measure a distance to/from a waypoint that is outside of the conflict area, and use it to implement a vertical standard after exiting, or prior to entering the lateral conflict area -!!! example +!!! phraseology "Climb to reach (vertically separated level) by (GNSS distance outside entry of conflict area)" "Report (GNSS distance outside exit of conflict area) for requested level" diff --git a/docs/separation-standards/visual.md b/docs/separation-standards/visual.md index 4d897b1e3..94eb49c88 100644 --- a/docs/separation-standards/visual.md +++ b/docs/separation-standards/visual.md @@ -39,7 +39,7 @@ This technique is useful for situations such as: - Allowing aircraft to conduct airwork in a position which would normally conflict with other aircraft - Providing track shortening or expedited clearances where a delay would normally occur due to other aircraft -!!! example +!!! phraseology *RSCU203 is a VFR helicopter who wishes to depart from Royal Prince Alfred Hospital, which sits directly under the YSSY RWY 16L approach path.* **SY ADC:** "RSCU203, report sighting a Jetstar A320 on a 6nm final RWY 16L" **RSCU203:** "Traffic sighted, RSCU203" diff --git a/docs/stylesheets/admonitions.css b/docs/stylesheets/admonitions.css index da5afb728..18b832c00 100644 --- a/docs/stylesheets/admonitions.css +++ b/docs/stylesheets/admonitions.css @@ -56,4 +56,24 @@ .md-typeset .block > .admonition-title::before, .md-typeset .block > summary::before { height: 0rem; +} + +:root { + --md-admonition-icon--phraseology: url('../assets/headset.svg'); /* Path to your custom SVG */ +} + +.md-typeset .admonition.phraseology { + border-color: #90EE90; /* Light green border */ + background-color: #FFFFFF; /* White background for the text */ +} + +.md-typeset .phraseology > .admonition-title { + background-color: #D3F8D3; /* Lighter green background for the title */ + border-color: #90EE90; /* Light green border for title */ +} + +.md-typeset .phraseology > .admonition-title::before { + background-color: black; /* Set the icon color to black */ + -webkit-mask-image: var(--md-admonition-icon--phraseology); /* Custom SVG for icon */ + mask-image: var(--md-admonition-icon--phraseology); /* Custom SVG for icon */ } \ No newline at end of file diff --git a/docs/terminal/adelaide.md b/docs/terminal/adelaide.md index d2b6981e2..3834823bc 100644 --- a/docs/terminal/adelaide.md +++ b/docs/terminal/adelaide.md @@ -50,7 +50,7 @@ Coordinate the aircraft with ADC, including the use of the appropriate clearance
Clearance Limits (red) and Approach/Departure Path (green)
-!!! example +!!! phraseology **CEY:** "Adelaide Approach, CEY, Cessna 172, 4nm south of PNL, 1,000ft, received charlie, request coastal northbound" **AD TCU:** "CEY, Adelaide Approach, squawk 0542, remain clear of class C airspace" **CEY:** "Squawk 0542, remain OCTA, CEY" @@ -71,7 +71,7 @@ Once the aircraft has transited the extended runway centreline and is clear of p ### PF ADC Offline Due to the low level of CTA at YPPF, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb. -!!! example +!!! phraseology **ABC**: "Adelaide Approach, ABC, PC12, POB 8, IFR, taxiing YPPF for YPAG, Runway 21R" **AD TCU**: "ABC, Adelaide Approach, Squawk 3601, no reported IFR traffic, report ready at the holding point for airways clearance" **ABC**: "Squawk 3601, wilco, ABC" @@ -153,7 +153,7 @@ Voiceless for all aircraft: All other aircraft going to TBD CTA must be **Heads-up** Coordinated by AD TCU prior to the boundary. -!!! example +!!! phraseology **AD TCU** -> **TBD**: "PFY1234, request DCT LOLLS" **TBD** -> **AD TCU**: "PFY1234, concur DCT LOLLS" @@ -173,7 +173,7 @@ All other aircraft coming from TBD CTA will be **Heads-up** Coordinated to AD TC b) Assigned the standard assignable level; and c) Assigned a **Procedural** SID -!!! example +!!! phraseology **AD ADC** -> **AD TCU**: "Next, ABC, runway 05" **AD TCU** -> **AD ADC**: "ABC, Track Extended Centreline, unrestricted" **AD ADC** -> **AD TCU**: "Track Extended Centreline, ABC" @@ -185,7 +185,7 @@ For Non-Jets: The lower of `A040` or the `RFL` ### AD TCU Internal All aircraft transiting between internal AD TCU boundaries must be heads-up coordinated. -!!! example +!!! phraseology **AAW** -> **AAE**: "via AD, FD123" **AAE** -> **AAW**: "FD123, A090" @@ -200,7 +200,7 @@ Refer to [Reclassifications](#pf-ctr) for operations when PF ADC is offline. #### Departures When the aircraft is ready for departure, PF ADC will coordinate with AD TCU for permission to release the aircraft into CTA. -!!! example +!!! phraseology **PF ADC** -> **AAW**: "Next, XMM, 03L" **AAW** -> **PF ADC**: "XMM, Heading 020, unrestricted" **PF ADC** -> **AAW**: "Heading 020, XMM" @@ -212,7 +212,7 @@ AD TCU will heads-up coordinate arrivals/overfliers from Class C to PF ADC prior 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. -!!! example +!!! phraseology **AAW** -> **PF ADC**: "via PAL, YTS" **PF ADC** -> **AAW**: "YTS, A010" @@ -220,13 +220,13 @@ VFR aircraft require a level readback. #### Departures Aircraft departing YPED in to AD TCU Class C will be coordinated from **EDN ADC** at Taxi. -!!! example +!!! phraseology **EDN ADC** -> **AD TCU**: "Taxi, BLKT11 for YMES, via VIRAT" **AD TCU** -> **EDN ADC**: "BLKT11" When the aircraft is ready for takeoff, **EDN ADC** will give a "Next" call, where AD TCU will provide the cleared level. -!!! example +!!! phraseology **EDN ADC** -> **AD TCU**: "Next, BLKT11, runway 18" **AD TCU** -> **EDN ADC**: "BLKT11, A050" **EDN ADC** -> **AD TCU**: "A050, BLKT11" @@ -234,6 +234,6 @@ When the aircraft is ready for takeoff, **EDN ADC** will give a "Next" call, whe #### Arrivals AD TCU Must coordinate the sequence information to **EDN ADC** prior to transfer of jurisdiction. -!!! example +!!! phraseology **AD TCU** -> **EDN ADC**: "New sequence of 2. MRNR21, via AD, Number 1. MRNR22, via AD, Number 2" **EDN ADC** -> **AD TCU**: "MRNR21, Number 1. MRNR22, Number 2" \ No newline at end of file diff --git a/docs/terminal/amberleyoakey.md b/docs/terminal/amberleyoakey.md index bf4bedd62..2d894f9c7 100644 --- a/docs/terminal/amberleyoakey.md +++ b/docs/terminal/amberleyoakey.md @@ -74,7 +74,7 @@ Visual Departures are commonly requested by high performance military jets, and Aircraft will make a visual departure in the circuit direction and fly overhead YAMB to begin tracking for their initial waypoint. -!!! example +!!! phraseology WOLF03 was assiged the BYRON7 departure with their intial clearance. **AMB ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff" **WOLF03**: "Make left turn, reach `F190` by COWIE, cleared for takeoff, WOLF03" @@ -105,7 +105,7 @@ OK ADC owns the airspace within 5 DME of the OK VOR from `SFC` to `A025`. #### Departures 'Next' coordination is required from AMB ADC to AMB TCU for all aircraft. -!!! example +!!! phraseology **AMB ADC** -> **AMB TCU**: "Next, ASY01, runway 33" **AMB TCU** -> **AMB ADC**: "ASY01, Assigned Heading Right 030, unrestricted" **AMB ADC** -> **AMB TCU**: "Assigned Heading Heading Right 030, ASY01" @@ -120,11 +120,11 @@ b) `F190` for Aircraft assigned a Coded Departure. The Standard Assignable from **OK ADC** to **OK TCU** is the lower of `F120` or `RFL`. -!!! example +!!! phraseology **AMB TCU** -> **BN TCU**: "via BN, DRGN02" **BN TCU** -> **AMB TCU**: "DRGN02, `F180`" -!!! example +!!! phraseology BUCK03 is assigned the BYRON 7 coded departure. **AMB TCU** -> **NSA**: "via COWIE, BUCK3." **NSA** -> **AMB TCU**: "BUCK03, `F190`" @@ -132,6 +132,6 @@ The Standard Assignable from **OK ADC** to **OK TCU** is the lower of `F120` or #### Arrivals/Overlfies All aircraft transiting from GOL/DOS/BUR to **AMB TCU** and **OK TCU** must be heads-up coordinated prior to **20nm** from the boundary and aircraft from **BN TCU** to **AMB TCU** only prior to the boundary. Operations within **AMB TCU** are fairly ad-hoc, so there are no standard assignable levels. GOL/DOS/BUR and **AMB TCU**/**OK TCU** controller must agree on a suitable level during coordination. -!!! example +!!! phraseology **GOL** -> **AMB TCU**: "via HUUGO, PUMA11, will be assigned A090" **AMB TCU** -> **GOL**: "PUMA11, A090" diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md index 9533b635e..b0de38236 100644 --- a/docs/terminal/brisbane.md +++ b/docs/terminal/brisbane.md @@ -83,7 +83,7 @@ Aircraft shall be assigned the following runways for arrival when PROPS are in p These standard runway assignments may be modified strategically by the BAS or BFL controller. -!!! example +!!! phraseology 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 separated at all times. **BFL** -> **INL**: "All arrivals via GOMOL to be assigned 19R until further notice" @@ -92,14 +92,14 @@ These standard runway assignments may be modified strategically by the BAS or BF ### Independent Visual Approach Phraseology at Night *"CLEARED INDEPENDENT VISUAL APPROACH RUNWAY (number), NOT BELOW (MVA) UNTIL ESTABLISHED ON THE PAPI (or GLIDEPATH)"* -!!! example +!!! phraseology **BAS:** “QFA660, Turn left heading 040, join final Runway 01L, from that heading Cleared Independent Visual Approach Runway 01L, not below 2400 until established on the PAPI” ## Offline Towers ### AF ADC Offline Due to the low level of CTA (`A015`) in the AF CTR when **AF ADC** is offline, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb. -!!! example +!!! phraseology **ABC**: "Brisbane Approach, ABC, PC12, POB 8, IFR, Taxiing YBAF for YBSU, Runway 28R" **BN TCU**: "ABC, Brisbane Approach, Squawk 3601, No Reported IFR Traffic, Report Ready at the Holding Point for Airways Clearance" **ABC**: "Squawk 3601, Wilco, ABC" @@ -111,7 +111,7 @@ Due to the low level of CTA (`A015`) in the AF CTR when **AF ADC** is offline, i ### CG ADC Offline Due to the low level of CTA (`A035`) in the CG CTR when **CG ADC** is offline, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb. -!!! example +!!! phraseology **JST446**: "Brisbane Approach, JST446, A320, IFR, Taxiing YBCG for YSSY, Runway 214" **BN TCU**: "JST446, Brisbane Approach, Squawk 3601, No Reported IFR Traffic, Report Ready at the Holding Point for Airways Clearance" **JST446**: "Squawk 3601, Wilco, JST446" @@ -140,7 +140,7 @@ Voiceless for aircraft: All other aircraft going to INL CTA must be **Heads-up** Coordinated by BN TCU prior to the boundary. This includes YBCG departures to the North that clip INL(GOL) airspace before re-entering BN TCU airspace -!!! example +!!! phraseology **BAC** -> **GOL**: "Departing YBCG, X4C, do you have any Restrictions or Requirements?" **GOL** -> **BAC**: "X4C, No Restrictions or Requirements" @@ -167,7 +167,7 @@ All other aircraft coming from INL CTA will be **Heads-up** Coordinated to BN TC ^Auto Release is not available during SODPROPS runway mode. All aircraft will be coordinated from BN ADC to BN TCU. -!!! example +!!! phraseology **BN ADC** -> **BN TCU**: "Next, ABC, runway 19L" **BN TCU** -> **BN ADC**: "ABC, Heading 030, Unrestricted" **BN ADC** -> **BN TCU**: "Heading 030, ABC" @@ -201,7 +201,7 @@ Refer to [Reclassifications](#cg-ctr) for operations when CG ADC is offline. b) Assigned the standard assignable level; and c) Assigned a **Procedural** SID -!!! example +!!! phraseology **CG ADC** -> **BAC**: "Next, CBN, runway 14" **BAC** -> **CG ADC**: "CBN, heading 030, unrestricted" **CG ADC** -> **BAC**: "Heading 030, CBN" @@ -221,7 +221,7 @@ Refer to [Reclassifications](#af-ctr) for operations when AF ADC is offline. ### Departures When aircraft planned via a CTA departure are ready for takeoff and expected to depart imminently, **AF ADC** shall seek release of the aircraft through a 'Next' call. -!!! example +!!! phraseology **AF ADC** -> **BN TCU**: "Next, XMM, Runway 10L" **BN TCU** -> **AF ADC**: "XMM, Unrestricted" **AF ADC** -> **BN TCU**: "XMM" @@ -233,20 +233,20 @@ BN TCU will heads-up coordinate arrivals/overfliers from Class C to AF ADC prior 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. -!!! example +!!! phraseology **BN TCU** -> **AF ADC**: "via TVT for the visual approach, UJE" **AF ADC** -> **BN TCU**: "UJE, visual approach" ### AMB TCU All aircraft transiting from **BN TCU** to **AMB TCU** and vice versa must be heads-up coordinated prior to the boundary. -!!! example +!!! phraseology **AMB TCU** -> **BN TCU**: "via BN, DRGN02" **BN TCU** -> **AMB TCU**: "DRGN02, `F140`" For aircraft arriving into AMB TCU there is no standard assignable level and simply is what ever the controllers agree upon. -!!! example +!!! phraseology **BN TCU** -> **AMB TCU**: "via WACKO, STAL13, what level can I assign?" **AMB TCU** -> **BN TCU**: "STAL13, `A090`" **BN TCU** -> **AMB TCU**: "`A090`, STAL13" diff --git a/docs/terminal/cairns.md b/docs/terminal/cairns.md index b7dc7e573..72a76da30 100644 --- a/docs/terminal/cairns.md +++ b/docs/terminal/cairns.md @@ -76,7 +76,7 @@ When VMC exists below `A030`, aircraft of light & medium weight categories (B737 #### Creek Corridor Aircraft for runway 15 will be cleared via the Victor STAR by enroute, which terminates on the Creek Corridor visual procedure (see YBCS DAP Noise Abatement Procedures chart). These aircraft should be cleared for a visual approach *"via the Creek Corridor"* and transferred to ADC prior to reaching the coastline. -!!! example +!!! phraseology *RXA5474 is tracking via the NONUM Victor STAR for runway 15.* **RXA5474**: "RXA5474, visual" **CS TCU**: "RXA5474, cleared visual approach tracking via the Creek Corridor" @@ -87,7 +87,7 @@ Aircraft for runway 33 may be cleared for a visual approach tracking via the STA Aircraft cleared via the KEEWI Victor STAR or otherwise approaching from the north shall be instructed to track for a visual right base and, once clear of departing traffic, assigned `A020 visual`. These aircraft will pass over the top of the CS CTR (owned by ADC), so further descent is not available. CS TCU must coordinate with ADC, then transfer them to ADC, who will issue visual approach clearance. -!!! example +!!! phraseology *JCI is tracking inbound from the north at `A050` and has reported visual.* **TCU** -> **ADC**: "Via right base, JCI, will be assigned A020 visual" **ADC** -> **TCU**: "A020 visual, JCI" @@ -117,7 +117,7 @@ CS ADC is responsible for the Class C Airspace within the CS CTR `SFC` to `A010` - Assigned the standard assignable level; and - Assigned a **Procedural** SID -!!! example +!!! phraseology **ADC** -> **TCU**: "Next, RXA5417, runway 15" **TCU** -> **ADC**: "RXA5417, heading 030, unrestricted" **ADC** -> **TCU**: "Heading 030, RXA5417" @@ -134,7 +134,7 @@ The controller assuming responsibility of **CS ACD** shall give heads-up coordin - VFR Departures - Aircraft using a runway not on the ATIS -!!! example +!!! phraseology **CS ACD** -> **CS TCU**: "ABC, Requesting clearance for a Northbound VFR Coastal departure at A035" **CS TCU** -> **CS ACD**: "ABC, Cleared for a Northbound VFR Coastal departure, A035" **CS ACD** -> **CS TCU**: "Cleared for a Northbound VFR Coastal departure, A035, ABC" @@ -154,7 +154,7 @@ Voiceless for all aircraft: All other aircraft going to KEN CTA must be **Heads-up** Coordinated by CS TCU prior to the boundary. -!!! example +!!! phraseology **CS TCU** -> **KEN**: "JST789, with your concurrence, will be assigned F160, for my separation with ANZ12" **KEN** -> **CS TCU**: "JST789, concur F160" diff --git a/docs/terminal/canberra.md b/docs/terminal/canberra.md index 1473a1995..5f790f5ec 100644 --- a/docs/terminal/canberra.md +++ b/docs/terminal/canberra.md @@ -37,7 +37,7 @@ Voiceless for all aircraft: All other aircraft going to ELW/BIK CTA must be **Heads-up** Coordinated by CB TCU prior to the boundary. -!!! example +!!! phraseology **CB TCU** -> **GUN**: "EVY113, with your concurrence, will be assigned F180, for my separation with QLK165D" **GUN** -> **CB TCU**: "EVY113, concur F180" @@ -60,7 +60,7 @@ CB ADC is responsible for the Class C Airspace within the CB CTR `SFC` to `A035` b) Assigned the standard assignable level; and c) Assigned a **Procedural** SID -!!! example +!!! phraseology **CB ADC** -> **CB TCU**: "Next, ABC, runway 35" **CB TCU** -> **CB ADC**: "ABC, Track Extended Centreline, unrestricted" **CB ADC** -> **CB TCU**: "Track Extended Centreline, ABC" @@ -72,7 +72,7 @@ For VFR aircraft: The lower of `A040` or the `RFL` #### Helipads in the CB CTR The Canberra CTR contains the Southcare Helicopter Base (YXSB) as well as two hospitals (Calvary Hospital and Canberra Hospital). Helicopters inbound to these helipads should be coordinated with **CB ADC** who can use a visual separation techniques as required. ADC and the TMA controller should work together to determine the most appropriate clearance limit (if required due traffic) for the helicopter, before frequency transfer is issued. ADC will issue a visual approach clearance when it is available. -!!! example +!!! phraseology *RSCU201 is an IFR AW139 helicopter tracking from the east for Southcare Base (YXSB).* **CBE** -> **CB ADC**: "To the east, RSCU201, for Southcare Base, are you able to separate with the arrival path to runway 35?" **CB ADC** -> **CBE**: "Affirm, RSCU201 clearance limit Queanbeyan" @@ -85,7 +85,7 @@ Departing helicopters may transit the CTR to Class G (under the direction of ADC ### CB TCU Internal All aircraft transiting between internal CB TCU boundaries must be heads-up coordinated. -!!! example +!!! phraseology **CBW** -> **CBE**: "via CB, FD123" **CBE** -> **CBW**: "FD123, A090" diff --git a/docs/terminal/coral.md b/docs/terminal/coral.md index 5a0e3ea4f..2b0df80df 100644 --- a/docs/terminal/coral.md +++ b/docs/terminal/coral.md @@ -43,7 +43,7 @@ Voiceless for all aircraft: All other aircraft going to SWY/KPL CTA must be **Heads-up** Coordinated by MKA/RKA. -!!! example +!!! phraseology **RKA** -> **KPL**: "QFA114, with your concurrence, will be assigned F130, for my separation with ZYX" **KPL** -> **RKA**: "QFA114, concur F130" @@ -71,7 +71,7 @@ RK ADC is responsible for the Class D airspace in the RK CTR `SFC` to `A010`. b) Assigned the standard assignable level; and c) Assigned a **Procedural** SID -!!! example +!!! phraseology **MK ADC** -> **MKA**: "Next, ABC, runway 14" **MKA** -> **MK ADC**: "ABC, Heading 150 Visual, unrestricted" **MK ADC** -> **MKA**: "Heading 150 Visual unrestricted, ABC" @@ -93,6 +93,6 @@ COR TCU will coordinate all YBMK and YBRK arrivals to ADC prior to **5 mins** fr - Approach type, unless specifically nominated on the ATIS - IFR Circuit joining instructions, if not on Straight-in instrument approach -!!! example +!!! phraseology **RKA** -> **RK ADC**: "via ABVAS, DJU, for the VOR-A” **RK ADC** -> **RKA**: "DJU, VOR-A" \ No newline at end of file diff --git a/docs/terminal/curtin.md b/docs/terminal/curtin.md index 1025c0631..644271988 100644 --- a/docs/terminal/curtin.md +++ b/docs/terminal/curtin.md @@ -31,7 +31,7 @@ CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`. #### Departures 'Next' coordination is required from CIN ADC to CIN TCU for all aircraft. -!!! example +!!! phraseology **CIN ADC** -> **CIN TCU**: "Next, ASY404, runway 29" **CIN TCU** -> **CIN ADC**: "ASY404, unrestricted" **CIN ADC** -> **CIN TCU**: "ASY404" @@ -44,7 +44,7 @@ Planned below `F190`: `Assigned the RFL` Any aircraft not meeting the above criteria must be prior coordinated to ENR. -!!! example +!!! phraseology **CIN TCU** -> **ASH**: "ASY404, with your concurrence, will be assigned F180, for my separation with JTE654" **ASH** -> **CIN TCU**: "ASY404, concur F160" diff --git a/docs/terminal/darwin.md b/docs/terminal/darwin.md index 4f372d652..dda4624dd 100644 --- a/docs/terminal/darwin.md +++ b/docs/terminal/darwin.md @@ -108,7 +108,7 @@ Voiceless for all aircraft: All other aircraft going to TRT CTA must be **Heads-up** Coordinated by DN TCU prior to the boundary. -!!! example +!!! phraseology **DN TCU** -> **TRT**: "PFY1234, with your concurrence, will be assigned F160, for my separation with JTE654" **TRT** -> **DN TCU**: "PFY1234, concur F160" @@ -128,7 +128,7 @@ DN ADC owns the airspace within the DN CTR `SFC`–`A010`. #### Auto Release Auto-Release is **not available** at YPDN. All Departures will be coordinated when ready for departure. -!!! example +!!! phraseology **DN ADC** -> **DN TCU**: "Next, EOC, runway 18" **DN TCU** -> **DN ADC**: "EOC, Track Extended Centreline, unrestricted" **DN ADC** -> **DN TCU**: "Track Extended Centreline, EOC" @@ -147,6 +147,6 @@ Heads-up coordination is not required between DAW and DAE for: All other aircraft must be heads-up coordinated prior to the airspace boundary -!!! example +!!! phraseology **DAW** -> **DAE**: "via DN, CFH23" **DAE** -> **DAW**: "CFH23, A090" \ No newline at end of file diff --git a/docs/terminal/eastsale.md b/docs/terminal/eastsale.md index cc67845d2..a8b49f011 100644 --- a/docs/terminal/eastsale.md +++ b/docs/terminal/eastsale.md @@ -31,7 +31,7 @@ Release coordination with the overlying enroute controller is required. Given the specific nature of the East Sale TCU airspace, surrounding controllers may not be fully aware of its boundaries. Upon logging on as East Sale TCU, it is essential to announce the activation status of R360/M301. -!!! example +!!! phraseology **ESA** -> **ELW**: "Request activation of R360 from SFC to F210" ## Circuit Procedures @@ -95,7 +95,7 @@ Upon pilot request, clear aircraft to transit through the Longford Lane. *RCR is a VFR Archer 10 miles to the north west of McGauran beach* -!!! example +!!! phraseology **RCR**: "East Sale Approach, RCR, Archer, 10 miles north west McGauran beach, 3500, request clearance Loch Sport" **ES TCU**: "RCR, East Sale Approach, squawk 1234, remain outside charlie airspace" **RCR**: "Remain OCTA, squawk 1234, RCR" @@ -200,7 +200,7 @@ When expect instrument approach is advertised on the ATIS: Auto release is not utilized at East Sale. 'Next' coordination is required from ES ADC to ES TCU for all aircraft. -!!! Example +!!! phraseology **ES ADC** -> **ES TCU**: "Next, ASY01, runway 09" **ES TCU** -> **ES ADC**: "ASY01, Assigned Heading Left 030, unrestricted" **ES ADC** -> **ES TCU**: "Left Heading 030, ASY01" @@ -211,7 +211,7 @@ Helicopters departing from helicopter spots will be treated as if departing from *PSDN14 is a VFR helicopter departing from the threshold of RWY04 (in the direction of runway 27)* -!!! Example +!!! phraseology **ES ADC** -> **ES TCU**: "Next, PSDN14, runway 09" **ES TCU** -> **ES ADC**: "PSDN14, Assigned Heading Left 010, unrestricted" **ES ADC** -> **ES TCU**: "Left Heading 010, PSDN14" diff --git a/docs/terminal/learmonth.md b/docs/terminal/learmonth.md index c7ecb1b1b..8a4db8dc4 100644 --- a/docs/terminal/learmonth.md +++ b/docs/terminal/learmonth.md @@ -33,7 +33,7 @@ LM ADC owns the Class C airspace within the LM CTR from `SFC` to `A015`. #### Departures 'Next' coordination is required from LM ADC to LM TCU for all aircraft. -!!! example +!!! phraseology **LM ADC** -> **LM TCU**: "Next, QFA1601, runway 36" **LM TCU** -> **LM ADC**: "QFA1601, Right heading 060 Visual, unrestricted" @@ -45,7 +45,7 @@ Planned below `F270`: `Assigned the RFL` Any aircraft not meeting the above criteria must be prior coordinated to ENR. -!!! example +!!! phraseology **LM TCU** -> **OLW**: "QFA1601, with your concurrence, will be assigned F160, for my separation with JTE654" **OLW** -> **LM TCU**: "QFA1601, concur F160" diff --git a/docs/terminal/melbourne.md b/docs/terminal/melbourne.md index 164b8f515..221ac9e0e 100644 --- a/docs/terminal/melbourne.md +++ b/docs/terminal/melbourne.md @@ -76,7 +76,7 @@ The **ML (RADAR) SID** is used for all non-jet IFR departures (and certain jet a ### Level Assignment When assigning levels on descent to aircraft, remember that you will not receive "Next" Coordination on aircraft assigned Standard Assignable Levels (`A050` for most aircraft), meaning an aircraft could depart at any time without prior warning and climb to `A050`. To maintain separation assurance between arrivals and departures, do not assign below `A060` to arriving aircraft until they are clear of the active runway's departure path. -!!! example +!!! phraseology With RWY 34 in use for arrivals and RWY 27 in use for departures, aircraft inbound on the ARBEY STAR should be assigned no lower than `A060` until established south of the RWY 27 departure track. To avoid conflicting with published departure procedures, aircraft not cleared via a STAR should be issued a requirement to reach `A090` by 20DME. @@ -104,7 +104,7 @@ VFR YMEN Arrivals from ML TCU shall be cleared via any of the following arrival #### Arrivals The class C airspace surrounding YMEN extends to `SFC`. This means that aircraft conducting approaches will remain inside controlled airspace until they land (and in the event of a go around). These aircraft should be cleared for an appropriate approach, advised of any traffic taxiing at YMEN, and instructed to *'report clear of the runway'*. The missed approach path must be protected until the aircraft reports clear. -!!! example +!!! phraseology **ML TCU:** "SH490, cleared ILS Runway 26 approach, traffic taxiing for the holding point is UJA, an Aero Commander, report clear of the runway" **SH490:** "Cleared ILS Runway 26, copy UJA, SH490" @@ -114,7 +114,7 @@ The class C airspace surrounding YMEN extends to `SFC`. This means that aircraf #### Departures Essendon has unique procedures due to its position in the ML CTR, with controlled airspace to the ground. Departing aircraft will request airways clearance and engine start while on the bay and ML TCU will provide current weather conditions, expected runway for departure, and clearance. On completion of the readback, aircraft should be instructed to *'report taxiing to runway XX'*. -!!! example +!!! phraseology **FDK**: "Melbourne Approach, FDK, YMEN for YSHT, request clearance and engine start" **ML TCU**: "FDK, Melbourne Approach, wind 290 degrees 4 knots, QNH 1017, cleared to YSHT via MNG, flight planned route, visual departure, climb to A040, squawk 4423, expect runway 35" **FDK**: "QNH 1017, cleared to YSHT via MNG, flight planned route, visual departure, climb to A040, squawk 4423, FDK" @@ -122,13 +122,13 @@ Essendon has unique procedures due to its position in the ML CTR, with controlle **FDK**: "Start approved, FDK" When the aircraft reports taxiing, issue a traffic statement and instruct them to report at the holding point for departure instructions. -!!! example +!!! phraseology **FDK**: "FDK, taxiing runway 35" **ML TCU**: "FDK, traffic is CBN, a Cherokee, 5nm final runway 35, report at the holding point for departure instructions" **FDK**: "Copy CBN, wilco, FDK" Once the aircraft is ready for departure and no conflict exists in your airspace, issue any relevant departure instructions (assigned heading, visual turns, etc). If a departure is not yet available, instruct the pilot to hold on the ground and indicate the reason for the delay. -!!! example +!!! phraseology **FDK**: "FDK, ready runway 35" **ML TCU**: "FDK, hold at the holding point, short delay due inbound aircraft" **FDK**: "Hold at the holding point, FDK" @@ -143,7 +143,7 @@ Due to the low level of CTA above Avalon, aircraft conducting approaches will co !!! note A clearance to conduct an instrument approach constitutes a clearance to carry out the published missed approach. As a result, there is no need to issue a clearance to re-enter controlled airspace in the event the aircraft goes around. -!!! example +!!! phraseology **ML TCU:** "JST607, leave controlled airspace descending via the ILS Runway 18 approach, no reported IFR traffic, report clear of the runway" **JST607:** "Leave controlled airspace descending via the ILS Runway 18 approach, JST607" @@ -153,7 +153,7 @@ Due to the low level of CTA above Avalon, aircraft conducting approaches will co #### Departures Departing aircraft will require an airways clearance on the ground, due to the low level of CTA. Aircraft should report taxiing to the TCU controller, who will issue a squawk code and traffic statement. These aircraft should be instructed to report at the holding point, where airways clearance will be issued. -!!! example +!!! phraseology **AM318**: "Melbourne Approach, AM318, King Air, POB 2, IFR, taxiing YMAV runway 18 for YMEN" **ML TCU**: "AM318, Melbourne Approach, squawk 3542, no reported IFR traffic, report ready at the holding point for airways clearance" **AM318**: "Squawk 3542, wilco, AM318" @@ -168,14 +168,14 @@ Departing aircraft will require an airways clearance on the ground, due to the l #### Arrivals IFR aircraft cruising inside CTA will generally commence an instrument approach from within controlled airspace and leave CTA on descent. The missed approach procedure will keep these aircraft outside controlled airspace, so does not need to be protected by the TCU controller. Clear these aircraft to leave CTA descending via an appropriate approach. -!!! example +!!! phraseology **ML TCU:** "OFX, Leave controlled airspace descending via the RNP Runway 17L approach, no reported IFR traffic" **OFX:** "Leave controlled airspace descending via the RNP Runway 17L approach, OFX" #### Departures Due to the low level of CTA surrounding YMMB, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb. -!!! example +!!! phraseology **AAC:** "Melbourne Approach, AAC, PC12, POB 7, IFR, taxiing YMMB for YBLT, runway 35L" **ML TCU:** "AAC, Melbourne Approach, squawk 4301, no reported IFR traffic, report ready at the holding point for airways clearance" **AAC:** "Squawk 4301, wilco, AAC" @@ -231,7 +231,7 @@ Voiceless to all surrounding Enroute sectors for all aircraft: All other aircraft going to Enroute CTA must be **Heads-up** Coordinated by ML TCU prior to the boundary. -!!! example +!!! phraseology **ML TCU** -> **YWE**: "QFA420, with your concurrence, will be assigned F190, for my separation with QLK52D" **YWE** -> **ML TCU**: "QFA420, concur F190" @@ -246,7 +246,7 @@ All other aircraft coming from Enroute CTA will be **Heads-up** Coordinated to M ### ML ADC #### Auto Release -!!! important +!!! warning "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: @@ -265,7 +265,7 @@ All other aircraft coming from Enroute CTA will be **Heads-up** Coordinated to M Any aircraft that don't meet these criteria will be coordinated to ML TCU with a "Next" Call. -!!! example +!!! phraseology **ML ADC** -> **ML TCU**: "Next, CYF, runway 34" **ML TCU** -> **ML ADC**: "CYF, track extended centreline, unrestricted" **ML ADC** -> **ML TCU**: "Track extended centreline, CYF" @@ -301,7 +301,7 @@ Essendon departures that will not enter ML TCU Class C airspace are not required All aircraft departing into Class C must be coordinated to ML TCU with a "Next" Call -!!! example +!!! phraseology **EN ADC** -> **ML TCU**: "Next, FD318" **ML TCU** -> **EN ADC**: "FD318, heading 330, unrestricted" **EN ADC** -> **ML TCU**: "Heading 330, FD318" @@ -313,7 +313,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from Class C to EN ADC prior IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to EN ADC, unless EN ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **ML TCU** -> **EN ADC**: "via KAO, KHU" **EN ADC** -> **ML TCU**: "KHU, A015" @@ -336,7 +336,7 @@ Refer to [Reclassifications](#av-ctr) for operations when AV ADC is offline. Any aircraft that don't meet these criteria will be coordinated to ML TCU with a "Next" Call -!!! example +!!! phraseology **AV ADC** -> **MDS**: "Next, UJI, Runway 18" **MDS** -> **AV ADC**: "UJI, left 030, unrestricted" **AV ADC** -> **MDS**: "Left 030, UJI" @@ -348,7 +348,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from CTA to AV ADC prior to IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to AV ADC, unless AV ADC nominates a restriction. VFR aircraft will have their control services terminated upon leaving controlled airspace, and instructed to contact AV ADC for onwards clearance. -!!! example +!!! phraseology **MDS** -> **AV ADC**: "via TEMPL for the ILS-Y 18, JST631" **AV ADC** -> **MDS**: "JST631, ILS-Y 18" @@ -363,7 +363,7 @@ Refer to [Reclassifications](#mb-ctr) for operations when MB ADC is offline. Autorelease is not in effect at YMMB and all departures into Class C airspace require a 'Next' call. Consider the current traffic picture and provide a release when able. -!!! example +!!! phraseology **MB ADC** -> **MDS**: "Next, SGE" **MDS** -> **MB ADC**: "SGE, unrestricted" @@ -372,7 +372,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from Class C to MB ADC prior IFR aircraft will be cleared to **leave and re-enter controlled airspace** via the coordinated approach (Instrument or Visual) prior to handoff to MB ADC, unless MB ADC nominates a restriction. VFR aircraft will have their control services terminated passing `A025` on descent, and instructed to contact MB ADC for onwards clearance. -!!! example +!!! phraseology **MDS** -> **MB ADC**: "To the west, PLE, for the NDB-A" **MB ADC** -> **MDS**: "PLE, NDB-A" diff --git a/docs/terminal/nowra.md b/docs/terminal/nowra.md index 07a0ecc6b..3258ad1e8 100644 --- a/docs/terminal/nowra.md +++ b/docs/terminal/nowra.md @@ -23,14 +23,14 @@ Due to the temporary nature of the airspace, surrounding controllers may not be ### Activating R420F Where it is deemed operationally beneficial to activate R420F, this should be requested from the overlying enroute controller. -!!! example +!!! phraseology **NW TCU** -> **WOL**: "There's a preplanned military exercise about to commence, request release of R420F up to F300" **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. -!!! important +!!! 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. ## VFR Lane of Entry @@ -72,7 +72,7 @@ Auto release is not utilised at Nowra. 'Next' coordination is required from NW A The Standard Assignable Level from **NW ADC** to **NW TCU** is `F120` or `RFL`, whichever is lower. -!!! example +!!! 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" \ No newline at end of file diff --git a/docs/terminal/perth.md b/docs/terminal/perth.md index 187b6aff3..461822455 100644 --- a/docs/terminal/perth.md +++ b/docs/terminal/perth.md @@ -74,7 +74,7 @@ Other levels are available at the discretion of the TCU controller but coordinat Aircraft wishing to conduct a scenic flight over the Perth CBD should be cleared via the Victor 65 route. **No lateral separation standard exists between Victor 65 and the extended centreline of runway 06/24**, so controllers must ensure that an alternative form of separation assurance exists. -!!! example +!!! phraseology **VH-CYF:** "Perth Approach, CYF, Cessna 172, overhead FREM, 1,500ft, received Bravo, request Victor 65" **PHA:** "CYF, squawk 0542, remain clear of class C airspace" **VH-CYF:** "Squawk 0542, remain OCTA, CYF" @@ -89,7 +89,7 @@ Aircraft departing YPPH and intending to conduct the Victor 65 route will be coo ### JT/PEA ADC Offline Due to the low level of CTA at these aerodromes, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb. -!!! example +!!! phraseology **AAC**: "Perth Approach, AAC, PC12, POB 8, IFR, Taxiing YPJT for YPKG, Runway 06L" **PHA**: "AAC, Perth Approach, Squawk 3601, No Reported IFR Traffic, Report Ready at the Holding Point for Airways Clearance" **AAC**: "Squawk 3601, Wilco, AAC" @@ -101,7 +101,7 @@ Due to the low level of CTA at these aerodromes, it is best practice to give air ### Departure Procedures Aircraft departing the TMA to the south planned at `F130` or above will likely leave and re-enter CTA on climb. These aircraft should be instructed to leave and re-enter on climb to the standard assignable level (or other level as appropriate). -!!! example +!!! phraseology **PHD**: "RXA2125, leave and re-enter controlled airspace on climb to F180, no reported IFR traffic" **RXA2125**: "Leave and re-enter controlled airspace on climb to F180, RXA2125" @@ -118,7 +118,7 @@ Voiceless for all aircraft: All other aircraft going to PIY CTA must be **Heads-up** Coordinated by PH TCU prior to the boundary. -!!! example +!!! phraseology **PH TCU** -> **PIY**: "PFY9916, with your concurrence, will be assigned F130, for my separation with JTE654" **PIY** -> **PH TCU**: "PFY9916, concur F130" @@ -140,7 +140,7 @@ All other aircraft coming from PIY CTA will be **Heads-up** Coordinated to PH TC All other aircraft require a 'Next' call to PH TCU. -!!! example +!!! phraseology **PH ADC** -> **PH TCU**: "Next, ABC, runway 03" **PH TCU** -> **PH ADC**: "ABC, Heading 010, unrestricted" **PH ADC** -> **PH TCU**: "Heading 010, ABC" @@ -157,7 +157,7 @@ The controller assuming responsibility of ACD shall give heads-up coordination t a) VFR Departures b) Aircraft using a runway not on the ATIS -!!! example +!!! phraseology **PH ACD** -> **PH TCU**: "ABC, requesting Victor 65" **PH TCU** -> **PH ACD**: "ABC, cleared Victor 65, 1,500ft" **PH ACD** -> **PH TCU**: "Cleared Victor 65, 1,500ft, ABC" @@ -174,7 +174,7 @@ Other levels are available at the discretion of the TCU controller but coordinat All other aircraft transiting between internal PH TCU boundaries must be heads-up coordinated. -!!! example +!!! phraseology **PHA** -> **PHD**: "via PH, FD123" **PHD** -> **PHA**: "FD123, A090" @@ -187,7 +187,7 @@ Refer to [Reclassifications](#jt-ctr) for operations when JT ADC is offline. #### Departures When the aircraft is ready for departure, JT ADC will coordinate with the relevant PH TCU controller above them for permission to release the aircraft into their CTA. -!!! example +!!! phraseology **JT ADC** -> **PH TCU**: "Next, FD420, runway 24R" **PH TCU** -> **JT ADC**: "FD420, Unrestricted" **JT ADC** -> **PH TCU**: "FD420" @@ -199,7 +199,7 @@ PH TCU will heads-up coordinate arrivals/overfliers from Class C to JT ADC prior IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to JT ADC, unless JT ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **PH TCU** -> **JT ADC**: "via RNAV-Z RWY 06L, FD416, circling to land RWY 24R" **JT ADC** -> **PH TCU**: "FD416, RNAV-Z RWY 06L with a circle to land RWY 24R" diff --git a/docs/terminal/scherger.md b/docs/terminal/scherger.md index c29aeedb8..c4afe3d83 100644 --- a/docs/terminal/scherger.md +++ b/docs/terminal/scherger.md @@ -33,7 +33,7 @@ SG ADC owns the Class C airspace within the SG CTR from `SFC` to `A015`. #### Departures 'Next' coordination is required from SG ADC to SG TCU for all aircraft. -!!! example +!!! phraseology **SG ADC** -> **SG TCU**: "Next, ASY219, runway 30" **SG TCU** -> **SG ADC**: "ASY219, unrestricted" @@ -45,7 +45,7 @@ Planned below `F245`: `Assigned the RFL` Any aircraft not meeting the above criteria must be prior coordinated to ENR. -!!! example +!!! phraseology **SG TCU** -> **ARA**: "ASY219, with your concurrence, will be assigned F200, for my separation with ASY404" **ARA** -> **SG TCU**: "ASY219, concur F200" diff --git a/docs/terminal/sydney.md b/docs/terminal/sydney.md index 1d8330eb2..fd63fff90 100644 --- a/docs/terminal/sydney.md +++ b/docs/terminal/sydney.md @@ -192,12 +192,12 @@ SFW/SFE should provide aircraft an approximate 'miles to run' on first contact, A typical downwind will take roughly 25 track miles from the normal point have handover from SAN/SAS to SFE/SFW. -!!! example +!!! phraseology "QLK402, Sydney Director, descend to A040, 25 miles to run" SFW/SFE may provide distance to touchdown, when transferring an aircraft to tower after the aircraft is established on their approach runway centreline (see below). -!!! example +!!! phraseology "QFA490, 8 miles to touchdown, contact tower 120.5" ### Instrument Approach @@ -208,7 +208,7 @@ Two aircraft established on adjacent parallel approaches require `1nm` lateral s ### Independent Visual Approach When conducting IVAs, aircraft shall not be transferred to **SY ADC** until established on final. -!!! example +!!! phraseology **SFW:** “BNZ444, Turn left heading 360, join final Runway 34L, from that heading Cleared Independent Visual Approach” **BNZ444:** "Left heading 360, join final Runway 34L, from that heading Cleared Independent Visual Approach, BNZ444" @@ -218,7 +218,7 @@ When conducting IVAs, aircraft shall not be transferred to **SY ADC** until esta #### Phraseology at Night *"CLEARED INDEPENDENT VISUAL APPROACH RUNWAY (number), NOT BELOW (MVA) UNTIL ESTABLISHED ON THE PAPI (or GLIDEPATH)"* -!!! example +!!! phraseology **SFE:** “ANZ361, Turn right heading 330, join final Runway 34R, from that heading Cleared Independent Visual Approach Runway 34R, not below 1500 until established on the PAPI” @@ -231,15 +231,15 @@ Flights may be cleared for one of two standard scenic flight routes at `A015`, * Aircraft must track via Class G airspace to Long Reef and contact SY TCU prior to reaching Long Reef requesting a ‘Harbour Scenic’ clearance. Attempt to identify the aircraft, and if a clearance cannot be given immediately, instruct the pilot to remain in Class G airspace. -!!! example +!!! phraseology "LOI, squawk 0542, remain clear of Class C airspace" A **‘Harbour Scenic One’** (or **‘Two’**) clearance is used to authorise flight in the nominated route at `A015`. Sydney QNH must be issued with the clearance. -!!! example +!!! phraseology "LOI, identified, cleared Harbour Scenic One, Sydney QNH 1014" -!!! caution +!!! warning "Caution" The Harbour Scenic One procedure may cause conflict with departures from Runway 34R to the north. Before issuing a Harbour Scenic One clearance, assess the traffic situation on the ground at YSSY and determine whether a departure to the north of the harbour is likely in the next few minutes. If necessary, instruct the aircraft to remain OCTA and advise of the delay, or alternatively, issue the Harbour Scenic Two clearance.
@@ -265,7 +265,7 @@ These can be displayed on vatSys using the `SY_VFR` map. ### Inbound/Outbound Routes Helicopters outbound from YSSY will make contact with the Departures controller established on a Helicopter Route. Controllers need only identify the aircraft, as they will already be cleared to climb to a suitable level (generally not above `A010`) through their coded clearance. Each clearance stipulates a point where identification and control services are automatically terminated, but controllers may explicitely cancel these services for new pilots who may not understand where they exit CTA. -!!! example +!!! phraseology **YZD:** "Sydney Departures, helicopter YZD, passing A009 on the Barracks 5 Outbound" **SY TCU:** "YZD, Departures, identified" @@ -273,7 +273,7 @@ Helicopters tracking inbound to YSSY will generally do so via a Helicopter Route Controllers should identify the aircraft and then provide clearance if traffic permits. -!!! example +!!! phraseology **HSZ:** "Sydney Departures, helicopter HSZ, Sydney Heads, A010, received Delta, request Harbour Bridge 5 Inbound" **SY TCU:** "HSZ, squawk 0552" @@ -296,7 +296,7 @@ The `BONDI 5` coded clearance is only available to helicopters, provided PRM app Helicopters should be identified and then cleared for the `BONDI 5 NORTHBOUND` or `BONDI 5 SOUTHBOUND`. Traffic information must be provided on any other helicopters operating on the route or any other aircraft in the area (e.g. aircraft in Victor One). Sydney QNH should be provided if the aircraft didn't depart from YSSY recently. -!!! example +!!! phraseology **YOE:** "Sydney Approach, helicopter YOE, Jibbon Point, A005, received Whiskey, request Bondi 5 Northbound" **SY TCU:** "YOE, Sydney Approach, squawk 0451" @@ -304,7 +304,7 @@ Helicopters should be identified and then cleared for the `BONDI 5 NORTHBOUND` o Once the aircraft exits CTA at Long Bay Headland (southbound) or Sydney Heads (northbound), cancel their identification and control services. If the helicopter is likely to request a clearance via one of Sydney's Helicopter Routes, consider instructing them to remain on their assigned squawk code to assist with identification. -!!! example +!!! phraseology "YOE, clear of controlled airspace, identification and control service terminated, squawk 1200, frequency change approved" #### Sector Coded Clearances @@ -321,7 +321,7 @@ To reduce frequency congestion, several commonly used geographically defined are Helicopters should be identified and then provided the clearance where traffic permits. Helicopters established on a Helicopter Route should be issued an onwards clearance into the requested sector. -!!! example +!!! phraseology **HWD:** "Sydney Departures gday, helicopter HWD, passing 800ft on the Harbour Bridge 5 outbound, request South Harbour Sector" **SY TCU:** "HWD, Departures, identified, onwards clearance South Harbour Sector" **HWD:** "Onwards clearance South Harbour Sector, HWD" @@ -334,7 +334,7 @@ Helicopters should be identified and then provided the clearance where traffic p ### BK ADC Offline Due to the low level of CTA (`A015`) in the BK CTR when **BK ADC** is offline, it is best practice to give airways clearance to aircraft at the holding point, to ensure departing aircraft can have uninterrupted climb. -!!! example +!!! phraseology **LOA**: "LOA, King Air, POB 10, IFR, taxing Bankstown for Shellharbour, Runway 11C" **SY TCU**: "LOA, Sydney Approach, squawk 3601, no reported IFR traffic, report ready at the holding point for airways clearance" **LOA**: "Squawk 3601, wilco, LOA" @@ -407,7 +407,7 @@ Voiceless to all surrounding Enroute sectors for all aircraft: All other aircraft going to Enroute CTA must be **Heads-up** Coordinated to the relevant sector as soon as practical. -!!! example +!!! phraseology **SY TCU** -> **ARL**: "DAL40, with your concurrence, will be right of route, DCT GUTIV" **ARL** -> **SY TCU**: "DAL40, concur right of route DCT GUTIV" @@ -456,7 +456,7 @@ Westbound: `A080` Any aircraft not meeting these requirements **must** be prior coordinated to DIR. -!!! example +!!! phraseology **QFA421:** "QFA421, request direct SOSIJ" **SAS:** "QFA421, standby" @@ -467,7 +467,7 @@ Any aircraft not meeting these requirements **must** be prior coordinated to DIR **SAS:** "QFA421, cancel STAR, recleared direct SOSIJ, A060" **QFA421:** "Cancel STAR, recleared direct SOSIJ, A060, QFA421" -!!! example +!!! phraseology **SAS** -> **SFW**: "VOZ456, with your concurrence, will be assigned A070, for my separation with UJI" **SFW** -> **SAS**: "VOZ456, concur A070" @@ -483,7 +483,7 @@ Within 15 DME of SY, Departure controllers (**SDN** and **SDS**) can allow aircr It is vital that Approach controllers ensure all arriving aircraft are established below `A090` no later than 20DME to avoid conflicting with departures utilising the airspace. All STARs have height requirements which ensure this is achieved. Aircraft inbound to YSBK or YSSY who are not cleared via a STAR should be instructed to reach `A090` by 20DME. -!!! information +!!! info Circumstances like excessive weather deviation may make the use of REP impractical. Controllers should coordinate with other TMA positions and suspend REP in this case. ##### MARLN Corridor @@ -493,7 +493,7 @@ Aircraft are permitted to cross the MARLN corridor at or above `A060` without co If aircraft are cleared off runway 11 at YSBK into CTA, coordination is required from SDN (who will be receiving the aircraft from BK ADC) with SFW or SAN (depending on YSSY runway config) as the aircraft will pass closer than 1.5nm from the sector boundary. Refer to [Sydney TCU Airspace Division](#airspace-division) for more information. -!!! Example +!!! phraseology **SDN** -> **SFW**: “Request left turn out of Bankstown” **SFW** -> **SDN**: "Approved" *(no callsigns need be used here)* @@ -509,7 +509,7 @@ Upon receipt of the heads-up coordination from SRI, the SY TCU controller has se - "Remain outside Class C airspace, expect XX minute delay" - *Useful if it's busy* - "I'll call you back" - *Useful if the SY TCU controller hasn't had time to assess the aircraft yet* -!!! Example +!!! phraseology **SRI** -> **SDS**: “Departed YSHL, EQU” **SDS** -> **SRI**: "EQU, F170" **SRI** -> **SDS**: “F170, EQU” @@ -528,7 +528,7 @@ Heads-up coordination is not required from a SY TCU position to SRI for aircraft - Assigned 500ft above the BCTA as the CFL; and - Handed off to SRI -!!! example +!!! phraseology *FD214 is intending on leaving Class C airspace on descent into Bankstown. The lower limit of CTA is `A045`.* **SDS:** "FD214 descend to 5,000ft, contact Sydney Centre 124.55" **FD214:** "Descend 5,000ft, 124.55, FD214" @@ -541,7 +541,7 @@ Heads-up coordination is not required from a SY TCU position to SRI for aircraft - Handed off to SRI upon termination of control services -!!! example +!!! phraseology *CYF is an IFR C172 leaving CTA to the north at `A050`.* **SAN:** "CYF at 30DME SY, control service terminates, contact Sydney Centre 124.55" **CYF:** "124.55, CYF" @@ -586,7 +586,7 @@ All other aircraft require a 'Next' call from SY ADC. d) Jets departing 16L via WOL e) All aircraft during the Curfew Runway Mode -!!! example +!!! phraseology **SY ADC** -> **SY TCU**: "Next, ADA4, runway 34R" **SY TCU** -> **SY ADC**: "ADA4, Heading 030, unrestricted" **SY ADC** -> **SY TCU**: "Heading 030, ADA4" @@ -606,7 +606,7 @@ Refer to [Reclassifications](#bk-ctr) for operations when BK ADC is offline. #### Departures Aircraft departing YSBK in to SY TCU Class C will be coordinated from **BK ADC** when ready for takeoff. -!!! example +!!! phraseology **BK ADC** -> **SY TCU**: "Next, TFX12" **SY TCU** -> **BK ADC**: "TFX12, Unrestricted" **BK ADC** -> **SY TCU**: "TFX12" @@ -620,7 +620,7 @@ SY TCU will heads-up coordinate arrivals/overfliers from Class C to BK ADC prior IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to BK ADC, unless BK ADC nominates a restriction. VFR aircraft require a level readback. -!!! example +!!! phraseology **SY TCU** -> **BK ADC**: "via GRB, UJN" **BK ADC** -> **SY TCU**: "UJN, A010" @@ -636,7 +636,7 @@ Refer to [Reclassifications](#cn-ctr) for operations when CN ADC is offline. #### Departures CN ADC must advise SY TCU when the aircraft has called 'Ready'. In response to a ready call, SY TCU will issue a traffic statement. -!!! example +!!! phraseology **CN ADC** -> **SRI**: "Ready, MHQ, Runway 06" **SRI** -> **CN ADC**: "MHQ, traffic is MEH, an IFR AC50, tracking SHL RAKSO SB2WI, A035, estimate RAKSO time 35" (or "No Reported IFR Traffic") **CN ADC** -> **SRI**: "Traffic is MEH tracking SHL RAKSO SB2WI A035, RAKSO at 35" @@ -655,7 +655,7 @@ SY TCU must heads-up coordinate inbound IFR aircraft prior to **5 mins** from th SY TCU will **NOT** clear the aircraft for the approach. -!!! example +!!! phraseology **SRI** -> **CN ADC**: “via RNP W, HRP” **CN ADC** -> **SRI**: “HRP” diff --git a/docs/terminal/tassie.md b/docs/terminal/tassie.md index 6aec172f6..950abeb2c 100644 --- a/docs/terminal/tassie.md +++ b/docs/terminal/tassie.md @@ -60,7 +60,7 @@ Voiceless for all aircraft: All other aircraft going to HUO CTA must be **Heads-up** Coordinated by TAS TCU prior to the boundary. -!!! example +!!! phraseology **LTA** -> **HUO**: "via IRSOM, QFA114, with your concurrence, will be assigned F150, for my separation with ZYX" **HUO** -> **LTA**: "QFA114, concur F150" @@ -97,7 +97,7 @@ HBA will coordinate all YMHB arrivals to HB ADC prior to **5 mins** from the bou - Approach type, unless specifically nominated on the ATIS - IFR Circuit joining instructions, if not on Straight-in instrument approach -!!! example +!!! phraseology **HBA** -> **HB ADC**: "via BUSKA, QJE1789, for the ILS” **HB ADC** -> **HBA**: "QJE1789, ILS" @@ -122,6 +122,6 @@ LTA will coordinate all YMLT arrivals to LT ADC prior to **5 mins** from the bou - Approach type, unless specifically nominated on the ATIS - IFR Circuit joining instructions, if not on Straight-in instrument approach -!!! example +!!! phraseology **LTA** -> **LT ADC**: "via IRSOM, JST416, for the DGA, will join left downwind 32L” **LT ADC** -> **LTA**: "JST416" \ No newline at end of file diff --git a/docs/terminal/townsville.md b/docs/terminal/townsville.md index d3974704c..372ec80fc 100644 --- a/docs/terminal/townsville.md +++ b/docs/terminal/townsville.md @@ -36,7 +36,7 @@ Voiceless for all aircraft: All other aircraft going to TBP CTA must be **Heads-up** Coordinated by TL TCU prior to the boundary. -!!! example +!!! phraseology **TL TCU** -> **TBP**: "JST729, with your concurrence, will be assigned `F160`, for my separation with QLK327D" **TBP** -> **TL TCU**: "JST729, concur `F160`" @@ -59,7 +59,7 @@ a) Departing from a runway nominated in the ATIS; and b) Assigned the standard assignable level; c) Assigned a **Procedural** SID -!!! example +!!! phraseology **TL ADC** -> **TL TCU**: "Next, DNGO05, runway 19" **TL TCU** -> **TL ADC**: "DNGO05, Assigned Heading Left 150, unrestricted" **TL ADC** -> **TL TCU**: "Assigned Heading Left 150, DNGO05" diff --git a/docs/terminal/williamtown.md b/docs/terminal/williamtown.md index eaef73dc9..909267afa 100644 --- a/docs/terminal/williamtown.md +++ b/docs/terminal/williamtown.md @@ -57,7 +57,7 @@ Voiceless for all aircraft: All other aircraft going to ARL CTA must be **Heads-up** Coordinated by WLM TCU prior to the boundary. -!!! example +!!! phraseology **WLM TCU** -> **MLD**: "QJE1597, request DCT OMGAB" **MLD** -> **WLM TCU**: "QJE1597, concur DCT OMGAB" @@ -80,7 +80,7 @@ a) Departing from a runway nominated in the ATIS; and b) Assigned the standard assignable level; c) Assigned a **Procedural** SID -!!! example +!!! phraseology **WLM ADC** -> **WLM TCU**: "Next, MVP" **WLM TCU** -> **WLM ADC**: "MVP, Left Heading 010, Unrestricted" **WLM ADC** -> **WLM TCU**: "Left Heading 010, MVP" @@ -90,6 +90,6 @@ The Standard Assignable level from WLM ADC to WLM TCU is the lower of `F120` or #### Arrivals/Overfliers Voiceless coordination is in place from WLM TCU to WLM ADC for arrivals cleared for an approach on to a runway nominated on the ATIS. All other aircraft and all overfliers must be heads-up coordinated as soon as practical. -!!! example +!!! phraseology **WLM TCU** -> **WLM ADC**: "via WLM, ZULU, Close formation of 5, do you have any restrictions or requirements?” **WLM ADC** -> **WLM TCU**: "ZULU, no restrictions or requirements, A040" \ No newline at end of file From a387c79b76d0bfaba6a6d210b7a18ec96566c4b9 Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Fri, 13 Dec 2024 18:01:47 +1100 Subject: [PATCH 2/3] Delete HYD.md --- docs/enroute/Melbourne Centre/HYD.md | 163 --------------------------- 1 file changed, 163 deletions(-) delete mode 100644 docs/enroute/Melbourne Centre/HYD.md diff --git a/docs/enroute/Melbourne Centre/HYD.md b/docs/enroute/Melbourne Centre/HYD.md deleted file mode 100644 index a8c598500..000000000 --- a/docs/enroute/Melbourne Centre/HYD.md +++ /dev/null @@ -1,163 +0,0 @@ ---- - title: Hyden (HYD) ---- - ---8<-- "includes/abbreviations.md" -## Positions - -| Name | Callsign | Frequency | Login ID | -| ---- | -------- | --------- | -------- | -| **Hyden** | **Melbourne Centre** | **118.200** | **ML-HYD_CTR** | -| Pingelly† | Melbourne Centre | 133.900 | ML-PIY_CTR | -| Cross† | Melbourne Centre | 135.800 | ML-CRS_CTR | -| Jarrah† | Melbourne Centre | 120.300 | ML-JAR_CTR | -| Leeman† | Melbourne Centre | 122.400 | ML-LEA_CTR | -| Grove† | Melbourne Centre | 133.800 | ML-GVE_CTR | -| Geraldton† | Melbourne Centre | 134.200 | ML-GEL_CTR | - -† *Non-standard positions* may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new} - -### CPDLC -The Primary Communication Method for HYD is Voice. - -[CPDLC](../../../client/cpdlc) may be used in lieu when applicable. - -The CPDLC Station Code is `YHYD`. - -!!! tip - Even though HYD's Primary Communication Method is Voice, CPDLC may be used for Overfliers. - -## Airspace -
-![Hyden Airspace](../assets/piy.png){ width="700" } -
Pingelly Airspace
-
- -## Sector Responsibilities -### Pingelly (PIY) -PIY will provide final sequencing actions to ensure aircraft comply with their FF times prior to entering the Perth TCU. PIY is also responsible for issuing STAR Clearances for aircraft bound for YPJT, and Non-jets bound for YPPH and YPEA. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. - -For aircraft overflying the PH TCU place `O/FLY` in the LABEL DATA field. - -### Leeman (LEA) -LEA is responsible for assigning and issuing STAR clearance to aircraft inbound to Perth via `IPMOR`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. - -!!! note - Controllers should be aware that VHF coverage near the LEA/IND border may be limited. Controllers should strive to issue HF frequencies and transfer of communications instruction prior to 160 NM PH DME. - -### Grove (GVE) -GVE is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `JULIM` and `SAPKO`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. - -### Hyden (HYD) -HYD is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via `KABLI`/`MALUP`, `DAYLR` and `LAVEX`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. - -### Cross (CRS) / Geraldton (GEL) -Just keeping them separated! - -### Jarrah (JAR) -JAR is responsible for assigning and issuing arrival clearance to aircraft inbound to Perth via `SOLUS`. See [Perth Runway Modes](#ypph-runway-modes) for runway assignment. - -!!! note - Controllers should be aware there may be limited ADS-B coverage around Albany (YABA). Expect some areas of Class E airspace to be outside surveillance coverage. [Procedural Standards](../../../separation-standards/procedural) may need to be used in these cases. - -### Sequencing in to YPPH -Aircraft assigned the **same runway** inbound via **JULIM** and **SAPKO**, 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. - -## YPPH Runway Modes -### Southwest Plan -With the Southwest Plan active, arrivals shall be processed to either runway 21 or 24 based on their feeder fix, as per the table below: - -| Feeder Fix | Assigned Runway | -| --- | --- | -| JULIM | 21 | -| SAPKO | 21 | -| IPMOR | 21 | -| KABLI | 24 (or 21 if operationally required) | -| LAVEX | 24 | -| SOLUS | 24 | - -### Northeast Plan -With the Northeast Plan active (runways 03 and 06 in use), all arrivals shall be processed to runway 03. - -## YPJT Arrivals -To facilitate smooth movement of traffic in the Perth TCU, IFR Arrivals to YPJT shall be assigned a STAR in accordance with the *YPPH Runway Mode*: - -| Feeder Fix | 03/06 | 21/24 | -| ------------------- | ----- | ----- | -| WOORA | Golf | WOORA PH JT (No STAR) | -| LAVEX | Golf | Romeo | -| KABLI (Jet) | Golf | Romeo | -| MALUP (Non-Jet) | Whiskey | Romeo (via KABLI) | - -!!! note - Assigning a STAR to YPJT Arrivals still does not meet [voiceless coordination requirements](#arrivalsoverfliers) to PH TCU. All YPJT Arrivals must be **heads-up coordinated**, including those assigned a STAR. - -## STAR Clearance Expectation - -### Handoff -Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff: - -| Transferring Sector | Receiving Sector | ADES | Notes | -| ---- | -------- | --------- | --------- | -| GVE, CRS, HYD | PIY | YPPH, YPEA | Non-jets only | -| GVE, CRS, HYD | PIY | YPJT | | -| GEL | LEA | YPPH | | - -### First Contact -Aircraft being transferred from the following sectors shall be given STAR Clearance on first contact: - -| Transferring Sector | Receiving Sector | ADES | Notes | -| ---- | -------- | --------- | --------- | -| OLW(MEK, MTK, MZI) | GVE, HYD | YPPH, YPEA | Jets only | -| ASP(ESP) | HYD | YPPH, YPEA | Jets only | -| GVE, CRS, HYD | PIY | YPPH, YPEA | Non-jets only | -| GVE, CRS, HYD | PIY | YPJT | | -| GEL, IND | LEA | YPPH | | -| IND | GEL, LEA, JAR | YPPH | | - -## Coordination -### PH TCU -#### Airspace -The PH TCU is responsible for the airspace within 36 DME of the PH VOR, `SFC` to `F245`. - -Refer to [Perth TCU Airspace Division](../../../terminal/perth/#airspace-division) for information on airspace divisions when **PHD** is online. - -!!! note - A significant portion of the TMA airspace south of the PH VOR (roughly 20 DME onwards) is classified Class E with a lower limit of `F125`. Aircraft arriving from this direction from `F130` and above shall be instructed to leave and re-enter controlled airspace on descent to the standard assignable level (or other appropriate altitude). - -#### Arrivals/Overfliers -Voiceless for all aircraft: - -- With ADES **YPPH**; and -- Assigned a STAR; and -- Assigned `A090` - -All other aircraft coming from PIY CTA must be **Heads-up** Coordinated to PH TCU prior to **20nm** from the boundary. - -#### Departures -Voiceless for all aircraft: - -- Tracking via a Procedural SID terminus; and -- Assigned the lower of `F180` or the `RFL` - -All other aircraft going to PIY CTA will be **Heads-up** Coordinated by PH TCU. - -### Enroute -As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary. - -### HYD Internal -Changes to CFL are permitted up to the boundary from GVE, CRS and HYD to PIY. - -All else is Voiceless, no changes to route or CFL within **20nm** to boundary. - -That being said, it is *advised* that HYD(All) gives **Heads-up Coordination** prior to **20nm** in the following scenarios: -- JAR to PIY for all aircraft -- LEA to PIY for all aircraft - -### IND (Oceanic) -As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. - -Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector. - -!!! phraseology - **LEA**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25" \ No newline at end of file From b3af43649dfd507d77738d5b7ee6002e2cfd269f Mon Sep 17 00:00:00 2001 From: alexdiederich Date: Fri, 13 Dec 2024 20:20:07 +1100 Subject: [PATCH 3/3] Update best-practices.md --- docs/assist-us/best-practices.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/assist-us/best-practices.md b/docs/assist-us/best-practices.md index 4c1132d8c..6a08f19c2 100644 --- a/docs/assist-us/best-practices.md +++ b/docs/assist-us/best-practices.md @@ -50,7 +50,7 @@ Radio calls should take the following format: **STATION NAME**: "Message" ``` -!!! phraseology +!!! example **VOZ1545**: "VOZ1545, request descent" **HUO**: "VOZ1545, descend to FL130" @@ -73,7 +73,7 @@ As a general rule of thumb, hotlines should be used in all circumstances, except - Oceanic coordination - Airways clearance requests from ACD to overlying TCU/ENR position (e.g. Sydney Delivery requesting clearance to YSBK on behalf of an aircraft) -!!! phraseology +!!! example **NW TCU** -> **WOL**: "Taxi, PSDN18 for YMCO via URBOB, Requesting F130" **WOL** -> **NW TCU**: "PSDN18, F130" **NW TCU** -> **WOL**: "F130, PSDN18"