diff --git a/docs/aerodromes/classc/Adelaide.md b/docs/aerodromes/classc/Adelaide.md index 66ac943a0..62c5a341c 100644 --- a/docs/aerodromes/classc/Adelaide.md +++ b/docs/aerodromes/classc/Adelaide.md @@ -126,28 +126,21 @@ The Operational Information field should be updated based on the runway mode in All other aircraft require a Next call to AD TCU. -The Standard Assignable level from AD ADC to AD TCU is: +The Standard Assignable level from AD ADC to AD TCU is: | Aircraft | Level | -| -------- | ----- | +| ------------ | ----- | | Jets | `A050` | | Non-Jets | The lower of `A040` and `RFL` | ### Departures Controller -When **AAW** is online, the AD TCU airspace is split down the 05/23 Runway Centreline. As such, departing aircraft shall be instructed to contact the departures controller corresponding to the direction of turn of the aircraft after departure - -| Tracking via | Departure Runway | Departures Controller | -| ------------------ | -------------- | ---------------- | -| VILAD | 05/23/12 | AAE | -| UPROT | 05/23/12 | AAE | -| AVDEN | 05/23/12 | AAE | -| BENDO | 05/23/12 | AAE | -| ALBUT | 05/23/12 | AAE | -| EEMUE | 05/23/30 | AAW | -| GILES | 05/23/30 | AAW | -| YORKE | 05/23/30 | AAW | -| AREPA | 05/23/30 | AAW | -| HOLIT | 05/23/30 | AAW | -| ORBUN | 05/23/30 | AAW | -| All | 12 | AAE | -| All | 30 | AAW | \ No newline at end of file +When **AAW** is online, the AD TCU is [split down the runway 05/23 centreline](../../terminal/adelaide#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel. + +| Runway | Via | Departure Controller | +| ------ | ---- | -------------------- | +| 05 | AREPA
GILES
ORBUN
West | AAW | +| 05 | AVDEN
BENDO
UPROT
East | AAE | +| 12 | All | AAE | +| 23 | AREPA
GILES
ORBUN
West | AAW | +| 23 | AVDEN
BENDO
UPROT
East | AAE | +| 30 | All | AAW | \ No newline at end of file diff --git a/docs/aerodromes/classc/Brisbane.md b/docs/aerodromes/classc/Brisbane.md index ef1c889be..229f37407 100644 --- a/docs/aerodromes/classc/Brisbane.md +++ b/docs/aerodromes/classc/Brisbane.md @@ -240,13 +240,34 @@ The Standard Assignable level from BN ADC to BN TCU is: | Non-Jets | The lower of `A040` and `RFL` | ### Departures Controller -Refer to [Brisbane TCU Airspace Division](../../../terminal/brisbane/#airspace-division) for information on airspace divisions when **BDN** and/or **BDS** are online. +When both **BDN** and **BDS** are online, the BN TCU is [split down the runway 01R/19L centreline](../../terminal/brisbane#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel. + +=== "01 PROPS" + + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 01L | All | BDN | + | 01R | All | BDS | + +=== "19 PROPS" + + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 19L | BIXAD
WACKO | BDN | + | 19L | All others | BDS| + | 19R | All | BDN | + +=== "SODPROPS" + + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 01R | All | BDS | ### Standard Assignable Departure Headings Aircraft that have been cleared the **BN (RADAR) SID** must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required (excluding during SODPROPS) to the BN TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below: -| Runway | Assigned Heading -| ----------------- | -------------- | +| Runway | Assigned Heading | +| ------ | -------------- | | 01L | H340 | | 01R | H120 | | 19L | H110 | diff --git a/docs/aerodromes/classc/Canberra.md b/docs/aerodromes/classc/Canberra.md index 487436b4c..60c611faa 100644 --- a/docs/aerodromes/classc/Canberra.md +++ b/docs/aerodromes/classc/Canberra.md @@ -163,5 +163,14 @@ The Standard Assignable level from CB ADC to CB TCU is: | IFR | `A100` | | VFR | The lower of `A040` and `RFL` | -### Runway Change -Any Runway change must be prior coordinated to **CB TCU**. +### Departures Controller +When **CBW** is online, the CB TCU is [split down the runway 17/35 centreline](../../terminal/Canberra#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel. + +| Runway | Via | Departure Controller | +| ------ | ---- | -------------------- | +| 12 | All | AAE | +| 17 | DUBUS
HOWLY
NONUP
TANTA
WG VOR
West | AAW | +| 17 | AKMIR
AVBEG
CULIN
East | AAE | +| 30 | All | CBW | +| 35 | AVBEG
DUBUS
HOWLY
NONUP
TANTA
WG VOR
West | AAW | +| 35 | AKMIR
CULIN
East | AAE | \ No newline at end of file diff --git a/docs/aerodromes/classc/Melbourne.md b/docs/aerodromes/classc/Melbourne.md index a730ab43f..1789c4021 100644 --- a/docs/aerodromes/classc/Melbourne.md +++ b/docs/aerodromes/classc/Melbourne.md @@ -268,7 +268,31 @@ The following Standard Assignable Headings may be used for aircraft assigned the Any runway change must be prior coordinated to **MAE** and **EN ADC**. ### Departures Controller -Refer to [Melbourne TCU Airspace Division](../../../terminal/melbourne/#airspace-division) for information on airspace divisions when **MDN** and/or **MDS** are online. +When both **MDS** and **MDN** are online, the ML TCU is [divided according to the runway mode in use](../../terminal/melbourne#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure and direction of travel. + +=== "09" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 09 | Tracking NW, N, or NE | MDN | + | 09 | Tracking SW, S, or SE | MDS | + +=== "16" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 16 | MNG
NONIX
DOSEL
KEPPA
PEDNI
Tracking NW, N, or NE | MDN | + | 16 | CORRS
CRENA
ESDIG
ISPEG
SUNTI
Tracking SW, S, or SE | MDS | + +=== "27" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 27 | MNG
NONIX
DOSEL
KEPPA
PEDNI
Tracking NW, N, or NE | MDN | + | 27 | CORRS
CRENA
ESDIG
SUNTI
Tracking SW, S, or SE | MDS | + +=== "34" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 34 | CORRS
MNG
NONIX
DOSEL
KEPPA
PEDNI
SUNTI
Tracking NW, N, or NE | MDN | + | 34 | CRENA
ESDIG
Tracking SW, S, or SE | MDS | ### 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. diff --git a/docs/aerodromes/classc/Sydney.md b/docs/aerodromes/classc/Sydney.md index ab2c4fa71..36bc1bb90 100644 --- a/docs/aerodromes/classc/Sydney.md +++ b/docs/aerodromes/classc/Sydney.md @@ -476,17 +476,14 @@ When [Coordinator](#sydney-coordinator) is online and start approval is required - Departing from a runway nominated on the ATIS; and - Assigned the Standard assignable level; and -- Assigned a **Procedural SID** (except **ABBEY** SID); or -- Assigned the **Radar** SID with a [Standard Assignable Heading](#standard-assignable-departure-headings) +- Assigned a **Procedural SID** or the **Radar** SID with a [Standard Assignable Heading](#standard-assignable-departure-headings); or +- A helicopter cleared via an outbound helicopter route. All other aircraft require a 'Next' call to SY TCU. 'Next' coordination is additionally required for: - -- Visual departures -- Departures to YSBK + - After a go around, the next departure from that runway -- Jets departing 16L via WOL - All aircraft during the Curfew Runway Mode The Standard Assignable level from SY ADC to SY TCU is: @@ -497,7 +494,35 @@ The Standard Assignable level from SY ADC to SY TCU is: | Non-Jets | The lower of `A030` and `RFL` | ### Departures Controller -Refer to [Sydney TCU Airspace Division](../../../terminal/sydney/#airspace-division) for information on airspace divisions when **SDN** and/or **SDS** are online. +When both **SDS** and **SDN** are online, the SY TCU is [divided according to the runway mode in use](../../terminal/sydney#airspace-division). Aircraft should be instructed to contact the appropriate departures controller based on their runway of departure, SID, and direction of travel. + +=== "07" + | Runway | | Departure Controller | + | ------ | ---- | -------------------- | + | 07 | FISHA SID, OLSEM Transition
Tracking N, or NE | SDN | + | 07 | FISHA SID, WOL Transition
Tracking S, W, or SW | SDS | + +=== "16s" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 16L | ABBEY SID, WOL Transition
Tracking S or SW | SDS | + | 16L | KEVIN SID
Tracking SE, E, NE, or N | SDN | + | 16R | All | SDS | + +=== "25" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 25 | Tracking N, or NE | SDN | + | 25 | Tracking S, W, or SW | SDS | + +=== "34s" + | Runway | Via | Departure Controller | + | ------ | ---- | -------------------- | + | 34L | RIC SID
Tracking N, or NE | SDN | + | 34L | KADOM SID
WOL SID
Tracking S, W, or SW | SDS | + | 34R | OLSEM SID
Tracking N, or NE | SDN | + | 34R | MARUB SID, WOL Trans
Tracking S, W, or SW | SDS | + ### Standard Assignable Departure Headings Aircraft that have been cleared the **SY (RADAR) SID** must receive an assigned heading with their line up or takeoff clearance. 'Next' coordination is not required to the SY TCU controller when the departing aircraft has been assigned the standard assignable level and assigned one of the headings listed below: diff --git a/docs/terminal/adelaide.md b/docs/terminal/adelaide.md index 903780b73..eb692b60b 100644 --- a/docs/terminal/adelaide.md +++ b/docs/terminal/adelaide.md @@ -9,8 +9,9 @@ | Name | ID | Callsign | Frequency | Login ID | | ----------------------------- | ------- | ----------------------- | ----------- | ------------- | | **Adelaide Approach East** | **AAE** | **Adelaide Approach** | **118.200** | **AD_APP** | -| Adelaide Approach West :material-information-outline:{ title="Non-standard position"} | AAW | Adelaide Approach | 124.200 | AD-W_APP | -| Adelaide Flow :material-information-outline:{ title="Non-standard position"} | AFL | | | AD_FMP | +| Adelaide Approach West :material-information-outline:{ title="Non-standard position"} | AAW | Adelaide Approach | 124.200 | AD-W_APP | +| Adelaide Radar :material-information-outline:{ title="Non-standard position"} | AAR | Adelaide Approach | 130.450 | AD-R_DEP | +| Adelaide Flow :material-information-outline:{ title="Non-standard position"} | AFL | | | AD_FMP | !!! abstract "Non-Standard Positions" :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}. @@ -37,6 +38,9 @@ ED CTR reverts to Class G when **ED ADC** is offline, and is administered by the
AD TCU Structure
+#### Adelaide Radar (AAR) +AAR is responsible for the provision of FIS in Class G airspace within the AD TMA. It is a role normally performed by the controller responsible for **AAE**. The position is designed to reduce the workload of other TMA positions by identifing and issuing clearance (where available) to aircraft OCTA, then transferring them to the relevant TMA controller. + ## Local Procedures ### Scenic Coastal Flights VFR aircraft may transit the control zone tracking coastal north or southbound, generally at `A005`. **AD TCU** is responsible for ensuring these aircraft remain separated from aircraft arriving/departing at YPAD and may delegate this responsibility to **AD ADC**. diff --git a/docs/terminal/brisbane.md b/docs/terminal/brisbane.md index cdb78d72a..2f3cc04bb 100644 --- a/docs/terminal/brisbane.md +++ b/docs/terminal/brisbane.md @@ -13,6 +13,7 @@ | Brisbane Departures North :material-information-outline:{ title="Non-standard position"} | BDN | Brisbane Departures | 133.450 | BN_DEP | | Brisbane Departures South :material-information-outline:{ title="Non-standard position"} | BDS | Brisbane Departures | 118.450 | BN-S_DEP | | Gold Coast Approach :material-information-outline:{ title="Non-standard position"} | BAC | Brisbane Approach | 123.500 | BN-C_APP | +| Brisbane Radar :material-information-outline:{ title="Non-standard position"} | SHN | Brisbane Centre | 119.500 | BN-R_DEP | | Brisbane Flow :material-information-outline:{ title="Non-standard position"} | BFL | | | BN_FMP | !!! abstract "Non-Standard Positions" @@ -59,6 +60,9 @@ The divisions of the airspace between **BAN**, **BAS**, **BDS**, **BDN**, and ** ![SODPROPS TCU Structure](img/bnsodprops.png){ width="700" }
SODPROPS TCU Structure
+ +#### Brisbane Radar (SHN) +SHN is responsible for the provision of FIS in Class G airspace within the BN TMA. The position is designed to reduce the workload of other TMA positions by identifing and issuing clearance (where available) to aircraft OCTA, then transferring them to the relevant TMA controller. #### Airspace Structural Arrangements Pursuant to Section 2 of the [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}, **"North"**/**"West"** positions shall assume the airspace of corresponding **"South"**/**"East"** positions when the latter are inactive (e.g. **BAN** assumes **BAS** airspace), and vice versa. diff --git a/docs/terminal/img/16PROPS.png b/docs/terminal/img/16PROPS.png deleted file mode 100644 index d93cbd017..000000000 Binary files a/docs/terminal/img/16PROPS.png and /dev/null differ diff --git a/docs/terminal/img/adtcu_annotated.png b/docs/terminal/img/adtcu_annotated.png index 194a7b37f..086347d08 100644 Binary files a/docs/terminal/img/adtcu_annotated.png and b/docs/terminal/img/adtcu_annotated.png differ diff --git a/docs/terminal/img/ml09.png b/docs/terminal/img/ml09.png index 9ba5bddaf..0dc6e8e49 100644 Binary files a/docs/terminal/img/ml09.png and b/docs/terminal/img/ml09.png differ diff --git a/docs/terminal/img/ml09a16d.png b/docs/terminal/img/ml09a16d.png index 3912d319b..90a03524d 100644 Binary files a/docs/terminal/img/ml09a16d.png and b/docs/terminal/img/ml09a16d.png differ diff --git a/docs/terminal/img/ml16.png b/docs/terminal/img/ml16.png index 927da57f6..614141eac 100644 Binary files a/docs/terminal/img/ml16.png and b/docs/terminal/img/ml16.png differ diff --git a/docs/terminal/img/ml16a27d.png b/docs/terminal/img/ml16a27d.png index 1bfb35308..4dbd60e27 100644 Binary files a/docs/terminal/img/ml16a27d.png and b/docs/terminal/img/ml16a27d.png differ diff --git a/docs/terminal/img/ml27.png b/docs/terminal/img/ml27.png index cd63e9f62..4ed13ccfe 100644 Binary files a/docs/terminal/img/ml27.png and b/docs/terminal/img/ml27.png differ diff --git a/docs/terminal/img/ml27a34ad.png b/docs/terminal/img/ml27a34ad.png index f70aa5834..17b54af4d 100644 Binary files a/docs/terminal/img/ml27a34ad.png and b/docs/terminal/img/ml27a34ad.png differ diff --git a/docs/terminal/img/ml27ad34d.png b/docs/terminal/img/ml27ad34d.png index 014212d1d..ce915868e 100644 Binary files a/docs/terminal/img/ml27ad34d.png and b/docs/terminal/img/ml27ad34d.png differ diff --git a/docs/terminal/img/ml34.png b/docs/terminal/img/ml34.png index f3d30a280..d6a7727e6 100644 Binary files a/docs/terminal/img/ml34.png and b/docs/terminal/img/ml34.png differ diff --git a/docs/terminal/img/sy07.png b/docs/terminal/img/sy07.png index 7353c1afb..df90bddaa 100644 Binary files a/docs/terminal/img/sy07.png and b/docs/terminal/img/sy07.png differ diff --git a/docs/terminal/img/sy16PROPS.png b/docs/terminal/img/sy16PROPS.png index b39b3daf2..6250e0770 100644 Binary files a/docs/terminal/img/sy16PROPS.png and b/docs/terminal/img/sy16PROPS.png differ diff --git a/docs/terminal/img/sy25.png b/docs/terminal/img/sy25.png index ccf4e7909..0c773b80c 100644 Binary files a/docs/terminal/img/sy25.png and b/docs/terminal/img/sy25.png differ diff --git a/docs/terminal/img/sy34PROPS.png b/docs/terminal/img/sy34PROPS.png index 7eb4a716c..e2ca036a3 100644 Binary files a/docs/terminal/img/sy34PROPS.png and b/docs/terminal/img/sy34PROPS.png differ diff --git a/docs/terminal/img/sySODPROPS.png b/docs/terminal/img/sySODPROPS.png index 9d164341d..72366ca49 100644 Binary files a/docs/terminal/img/sySODPROPS.png and b/docs/terminal/img/sySODPROPS.png differ diff --git a/docs/terminal/melbourne.md b/docs/terminal/melbourne.md index 864b45140..c61a0de64 100644 --- a/docs/terminal/melbourne.md +++ b/docs/terminal/melbourne.md @@ -9,10 +9,11 @@ | Name | ID | Callsign | Frequency | Login ID | | ----------------------------- | ------- | ----------------------- | ----------- | ------------- | | **Melbourne Approach East** | **MAE** | **Melbourne Approach** | **132.000** | **ML_APP** | -| Melbourne Departures North :material-information-outline:{ title="Non-standard position"} | MDN | Melbourne Departures | 118.900 | ML_DEP | -| Melbourne Departures South :material-information-outline:{ title="Non-standard position"} | MDS | Melbourne Departures | 129.400 | ML-S_DEP | -| Melbourne (Avalon) Approach :material-information-outline:{ title="Non-standard position"} | MAV | Avalon Approach | 133.550 | AV_APP | -| Melbourne Flow :material-information-outline:{ title="Non-standard position"} | MFL | | | ML_FMP | +| Melbourne Departures North :material-information-outline:{ title="Non-standard position"} | MDN | Melbourne Departures | 118.900 | ML_DEP | +| Melbourne Departures South :material-information-outline:{ title="Non-standard position"} | MDS | Melbourne Departures | 129.400 | ML-S_DEP | +| Melbourne (Avalon) Approach :material-information-outline:{ title="Non-standard position"} | MAV | Avalon Approach | 133.550 | AV_APP | +| Melbourne Radar :material-information-outline:{ title="Non-standard position"} | MAW | Melbourne Centre | 135.700 | ML-R_DEP | +| Melbourne Flow :material-information-outline:{ title="Non-standard position"} | MFL | | | ML_FMP | !!! abstract "Non-Standard Positions" :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}. @@ -84,16 +85,23 @@ The divisions of the airspace between **MAE**, **MDN**, **MDS**, and **MAV** cha #### Avalon Approach (MAV) -MAV is responsible for the Class D and E airspace in the AV CTR, `SFC`-`A045`. +MAV is responsible for the Class D and E airspace in the AV CTR, `SFC`-`A045`. + They are responsible for the same portion of airspace when it is [reclassified](#av-ctr) due to AV ADC being offline. -MAV extends south outside of **30nm ML**, in to YWE(WON) airspace. The Southern portion of this extension (shown below) is Class E `A015`-`A045`, and YWE(WON) is responsible for the airspace **above and below** it. +MAV extends south outside of **30nm ML**, in to HUO(WON) airspace. The Southern portion of this extension (shown below) is Class E `A015`-`A045`, and HUO(WON) is responsible for the airspace **above and below** it.
![MAV Airspace Side Profile](img/mavairspace1.png){ width="700" }
MAV Airspace Side Profile
+#### Melbourne Radar (MAW) +MAW is responsible for the provision of FIS in Class G airspace within the ML TMA. It is a role normally performed by the controller responsible for **MAV**. The position is designed to reduce the workload of other TMA positions by identifing and issuing clearance (where available) to aircraft OCTA, then transferring them to the relevant TMA controller. [Explicit coordination requirements](#between-maw-and-appdep) exist between MAW and other ML TCU positions. + +!!! tip + It is **not recommended** that the MAV and MAW positions are held by 2 separate controllers, due to the low traffic levels at Avalon. MAV should be opened in preference to MAW, unless traffic levels at Avalon require the role to be split. + ## Departure and Arrival Procedures ### Departure Procedures #### ML (RADAR) SID @@ -209,10 +217,22 @@ Due to the low level of CTA surrounding YMMB, it is best practice to give airway #### 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. +When MAW is online, aircraft should be transferred to them once established on the RNP approach. + !!! 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" +***If MAW is online:*** + +!!! phraseology + **MDN:** "OFX, Leave Controlled Airspace descending via the RNP Approach Runway 17L, established contact Melbourne Centre 135.7" + **OFX:** "Leave controlled airspace descending via the RNP Runway 17L approach, contact Melbourne Centre 135.7 established, OFX" + + **OFX:** "Melbourne Centre, OFX Established RNP Runway 17L" + **MAW:** "OFX, Melbourne Centre no reported IFR traffic" + **OFX:** "OFX" + ## Runway Modes ### LAHSO !!! warning "Important" @@ -354,35 +374,76 @@ The following Standard Assignable Headings may be used for aircraft assigned the **When Runway 09 is in use for arrivals, all Runway 16 departures shall be assigned heading 160. ### ML TCU Internal -#### Arrivals -Voiceless Coordination is in place for arrivals transiting between ML TCU positions, provided the aircraft is: +#### APP / DEP +Voiceless Coordination is in place for aircraft transiting between ML TCU positions, provided the aircraft is: -- ADES **YMML**; and -- Assigned a STAR; and -- Descending via STAR to `A070` +- With ADEP **YMML**: + - Assigned a SID; and + - Climbing via SID to `A100` or higher, or -#### Departures -Voiceless Coordination is in place for departures transiting between ML TCU positions, provided the aircraft is: +- With ADES **YMML**: + - Assigned a STAR; and + - Descending via STAR to `A070` -- ADEP **YMML**; and -- Assigned a SID; and -- Climbing via SID to `A100` or higher - -#### Others (Heads-up) -All other aircraft not meeting the Departures/Arrivals criteria that transit between internal ML TCU boundaries must be heads-up coordinated. +All other aircraft, including aircraft that transit between internal ML TCU boundaries, must be heads-up coordinated. !!! phraseology **MDS** -> **MAV**: "via JAYBI, JST603" **MAV** -> **MDS**: "JST603, A030" -##### YMAV Arrivals/Departures -YMAV arrivals and departures **do not** meet the voiceless criteria between MDS and MAV. When MAV is conducting Heads-up Coordination to MDS on a YMAV departure, it is good practice for MDS to coordinate back a higher level (`F240` or the `RFL`, if no restrictions), so that the aircraft does not have interrupted climb +#### Between MAV and APP/DEP +YMAV arrivals and departures **do not** meet the voiceless criteria between APP/DEP and MAV, and must be heads-up coordinated. + +!!! tip + When MAV is conducting Heads-up Coordination to MDS on a YMAV departure, it is good practice for MDS to coordinate back a higher level (`F240` or the `RFL`, if no restrictions), so that the aircraft does not have interrupted climb !!! phraseology **MAV** -> **MDS**: "via JUSTY, JST616" **MDS** -> **MAV**: "JST616, F240" **MAV** -> **MDS**: "F240, JST616" +#### Between MAW and APP/DEP +##### Entering CTA +Heads up coordination is required for **all aircraft** entering ML TCU Class C from MAW Class G. Heads-up coordination must be completed prior to handoff, however, best practice is to complete coordination as soon as possible. + +!!! phraseology + **MAW** -> **MDN**: “Departed YLIL, OXP” + **MDN** -> **MAW**: "OXP, A080" + **MAW** -> **MDN**: “A080, OXP” + + **MAW:** "OXP cleared to YMTG via ML, flight planned route. Climb A080" + **OXP:** "Cleared to YMTG via ML, flight planned route. Climb A080, OXP" + **MAW:** "OXP Contact Melbourne Departures 118.9" + **OXP:** "118.9, OXP" + +##### Leaving CTA +Heads-up coordination is not required from a ML TCU position to MAW for aircraft: + +**Leaving CTA *vertically*:** +- Assigned 500ft above BCTA as the CFL; and +- Handed off to MAW + +!!! phraseology + *KDJ is intending on leaving Class C airspace on descent into YMMB. The lower limit of CTA is `A045`.* + + **MDN:** "KDJ descend to A050, contact Melbourne Centre 135.7" + **KDJ:** "Descend to A050, 135.7, KDJ" + + **KDJ:** "Melbourne Centre, KDJ descending A050" + **MAW:** "KDJ, Melbourne Centre, leave controlled airspace descending, no reported IFR traffic" + **KDJ:** "Leave controlled airspace descending KDJ" + +**Leaving CTA laterally** +- Handed off to MAW upon termination of control services + +!!! phraseology + *BSV is an IFR C172 leaving CTA to the south at `A040`.* + **MDS:** "BSV at 19 DME ML, control service terminates, contact Melbourne Centre 135.7" + **BSV:** "135.7, BSV" + + **BSV:** "Melbourne Centre, BSV maintaing A040" + **MAW:** "BSV, Melbourne Centre, no reported IFR traffic, area QNH 1016 + ### EN ADC #### Airspace EN ADC is responsible for the Class C airspace shown below, `SFC` to `A020`. diff --git a/docs/terminal/perth.md b/docs/terminal/perth.md index c138c538d..a141dbb86 100644 --- a/docs/terminal/perth.md +++ b/docs/terminal/perth.md @@ -7,8 +7,9 @@ | Name | ID | Callsign | Frequency | Login ID | | ----------------------------- | ------- | ----------------------- | ----------- | ------------- | | **Perth Approach** | **PHA** | **Perth Approach** | **123.600** | **PH_APP** | -| Perth Departures :material-information-outline:{ title="Non-standard position"} | PHD | Perth Departures | 118.700 | PH_DEP | -| Perth Flow :material-information-outline:{ title="Non-standard position"} | PFL | | | PH_FMP | +| Perth Departures :material-information-outline:{ title="Non-standard position"} | PHD | Perth Departures | 118.700 | PH_DEP | +| Perth Radar :material-information-outline:{ title="Non-standard position"} | PHR | Perth Centre | 135.250 | PH-R_DEP | +| Perth Flow :material-information-outline:{ title="Non-standard position"} | PFL | | | PH_FMP | !!! abstract "Non-Standard Positions" :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}. @@ -47,6 +48,9 @@ The divisions of the airspace between **PHA**, and **PHD** change based on the R
21/24 TCU Structure
+#### Perth Radar (PHR) +PHR is responsible for the provision of FIS in Class G airspace within the PH TMA. The position is designed to reduce the workload of other TMA positions by identifing and issuing clearance (where available) to aircraft OCTA, then transferring them to the relevant TMA controller. + #### Pearce Airspace When **PEA TCU** is online, they assume responsibility for the airspace in R155A and R155B from `SFC` to `F160`. diff --git a/docs/terminal/sydney.md b/docs/terminal/sydney.md index 440fe6bac..b555788d3 100644 --- a/docs/terminal/sydney.md +++ b/docs/terminal/sydney.md @@ -14,15 +14,13 @@ | Sydney Departures North :material-information-outline:{ title="Non-standard position"} | SDN | Sydney Departures | 123.000 | SY-N_DEP | | Sydney Director West :material-information-outline:{ title="Non-standard position"} | SFW | Sydney Director | 126.100 | SY-D_APP | | Sydney Director East :material-information-outline:{ title="Non-standard position"} | SFE | Sydney Director | 125.300 | SY-DE_APP| -| Sydney Radar :material-information-outline:{ title="Non-standard position"} :octicons-checklist-24:{ title="Non-standard position"} | SRI | Sydney Centre | 124.550 | SY-C_DEP | -| Sydney Flow :material-information-outline:{ title="Non-standard position"} | SFL | | | SY_FMP | +| Sydney Radar :material-information-outline:{ title="Non-standard position"} | SRI | Sydney Centre | 124.550 | SY-R_DEP | +| Sydney Flow :material-information-outline:{ title="Non-standard position"} | SFL | | | SY_FMP | !!! abstract "Non-Standard Positions" :material-information-outline: Non-standard positions may only be used in accordance with [VATPAC Air Traffic Services Policy](https://vatpac.org/publications/policies){target=new}. Approval must be sought from the **bolded parent position** prior to opening a Non-Standard Position, unless [NOTAMs](https://vatpac.org/publications/notam){target=new} indicate otherwise (eg, for events). - :octicons-checklist-24: [Additional requirements](#airspace-structural-arrangements) must be met prior to opening SRI as a stand-alone position. - ## Airspace The Vertical limits of the SY TCU are `SFC` to `F285`. SY TCU is responsible for the Sydney TMA, except: @@ -95,9 +93,7 @@ a) **"South"**/**"West"** positions shall assume the airspace of corresponding * b) Approach assumes Director/Departure airspace "on-side" when the latter positions are inactive (e.g. with **SAS** and **SAN** online only, **SAS** assumes **SDS** and **SFW**) -c) Departures assumes **SRI** airspace when the position is inactive - -d) **SRI** is **not permitted** to be logged on to, unless there are already at least **2 other active positions** (ie, SY APP and SY DEP, or SY APP and SY DIR) in the SY TCU. +c) Departures assumes **SRI** airspace when the position is inactive. !!! note The default ownership of sectors within the SY TCU is merely a suggestion for starters. There are 7 executive controller positions within the SY TCU, plus a flow controller, and the ownership of these sectors can be delegated as desired based on the traffic disposition, when agreed between the controllers. For example, during a Milk Run event, if SY APP and SY DEP are online, SY APP may have a lot more work to do than SY DEP, and it would mostly be concentrated on the RIVET/ODALE corridor. In light of this, it might be wise for SY APP to take ownership of SAS, SFW and SFE airspace, whilst SY DEP take ownership of SAN, SDS, SDN, and SRI airspace. @@ -624,17 +620,14 @@ Auto Release is used for virtually all fixed-wing departures at Sydney. Unlike s - Departing from a runway nominated on the ATIS; and - Assigned the Standard assignable level; and -- Assigned a **Procedural SID** (except **ABBEY** SID); or -- Assigned the **Radar** SID with a Standard Assignable Heading +- Assigned a **Procedural SID** or the **Radar** SID with a Standard Assignable Heading; or +- A helicopter cleared via an outbound helicopter route. All other aircraft require a 'Next' call to SY TCU. 'Next' coordination is additionally required for: -- Visual departures -- Departures to YSBK - After a go around, the next departure from that runway -- Jets departing 16L via WOL - All aircraft during the Curfew Runway Mode The Standard Assignable level from SY ADC to SY TCU is: diff --git a/includes/abbreviations.md b/includes/abbreviations.md index 56b8b8f30..1b26d710a 100644 --- a/includes/abbreviations.md +++ b/includes/abbreviations.md @@ -63,12 +63,14 @@ *[SDC]: Standard Departure Clearance *[AAW]: Adelaide Approach West *[AAE]: Adelaide Approach East +*[AAR]: Adelaide Radar *[AMA]: Amberley Approach *[BAC]: Brisbane (Gold Coast) Approach *[BAN]: Brisbane Approach North *[BAS]: Brisbane Approach South *[BDN]: Brisbane Departures North *[BDS]: Brisbane Departures South +*[SHN]: Brisbane (Sunshine) Radar *[CS1]: Cairns Approach 1 *[CS2]: Cairns Approach 2 *[CSA]: Cairns Approach @@ -88,9 +90,11 @@ *[MDN]: Melbourne Departures North *[MDS]: Melbourne Departures South *[MAV]: Melbourne (Avalon) Approach +*[MAW]: Melbourne Radar *[OKA]: Oakey Approach *[PHA]: Perth Approach *[PHD]: Perth Departures +*[PHR]: Perth Radar *[SAN]: Sydney Approach North *[SAS]: Sydney Approach South *[SDN]: Sydney Departures North @@ -373,4 +377,4 @@ *[TSAT]: Tactical Start Approved Time *[AOBT]: Actual Off Blocks Time *[CTOT]: Calculated Take Off TIme -*[ATOT]: Actual Off Blocks Time +*[ATOT]: Actual Off Blocks Time \ No newline at end of file