diff --git a/docs/aerodromes/classc/Cairns.md b/docs/aerodromes/classc/Cairns.md index 897229779..7dd4a12ab 100644 --- a/docs/aerodromes/classc/Cairns.md +++ b/docs/aerodromes/classc/Cairns.md @@ -85,8 +85,8 @@ Aircraft planning to enter the CS CTR between *Mt Gorton*, CGF and Upolo Cay at Within the Cairns CTR, there are over a dozen HLS's, including one hospital: Cairns Hospital (YCBH).
-![CS ADC Airspace](img/CS_ctr_heli.png){ width="700" } -
CS ADC Airspace
+![HLS in CS ADC Airspace](img/CS_ctr_heli.png){ width="700" } +
HLS in CS ADC Airspace
### Radisson Pier Helipad diff --git a/docs/aerodromes/classc/Canberra.md b/docs/aerodromes/classc/Canberra.md index 5b9e458cf..2ae36cdf9 100644 --- a/docs/aerodromes/classc/Canberra.md +++ b/docs/aerodromes/classc/Canberra.md @@ -16,7 +16,7 @@ CB ADC is responsible for the Class C Airspace within the CB CTR `SFC` to `A035`.
-![CB ADC Airspace](img/CBTWR.png){ width="700" } +![CB ADC Airspace](img/cbadc.png){ width="700" }
CB ADC Airspace
diff --git a/docs/aerodromes/classc/GoldCoast.md b/docs/aerodromes/classc/GoldCoast.md index dc766f53d..e691e62e4 100644 --- a/docs/aerodromes/classc/GoldCoast.md +++ b/docs/aerodromes/classc/GoldCoast.md @@ -16,7 +16,7 @@ CG ADC is responsible for the Class C Airspace within the CG CTR `SFC` to `A015`.
-![CG ADC Airspace](img/CGTWR.png){ width="700" } +![CG ADC Airspace](img/cgadc.png){ width="700" }
CG ADC Airspace
@@ -154,8 +154,8 @@ Local helicopter operations are conducted on the Western Grass which is the area Within the Gold Coast CTR, there are two main hospital helipads. Tweed Heads Hospital (YTWH), and Tweed Valley Hospital (YXTV).
-![CG ADC Airspace](img/CG_ctr_heli.png){ width="700" } -
CG ADC Airspace
+![HLS in CG ADC Airspace](img/CG_ctr_heli.png){ width="700" } +
HLS in CG ADC Airspace
#### Arrivals @@ -173,7 +173,7 @@ Both hospital helipads are outside the manoeuvring area and do not require a lan **WP1:** "Cleared visual approach YXTV, wilco, WP1" #### Departures -Aircraft departing from hospitals within the Gold Coast CTR must obtain clearance prior to becoming airborne. The Tweed Valley Hospital (YXTV) helipad, is located 6nm south beneath Runway 32 extended centerline, and may present potential traffic conflicts. Aircraft will be subject to delays depending on traffic in the Gold Coast CTR. +Aircraft departing from hospitals within the Gold Coast CTR must obtain clearance prior to becoming airborne. The Tweed Valley Hospital (YXTV) helipad is located 6nm south beneath Runway 32 extended centerline, and may present potential traffic conflicts. Aircraft will be subject to delays depending on traffic in the Gold Coast CTR. Both hospital helipads are outside the manoeuvring area and do not require a takeoff clearance from CG ADC, however a clearance to become airborne is required. Helicopters departing from these helipads should be instructed to "report airborne". diff --git a/docs/aerodromes/classc/Sydney.md b/docs/aerodromes/classc/Sydney.md index 988e6a953..eb476c635 100644 --- a/docs/aerodromes/classc/Sydney.md +++ b/docs/aerodromes/classc/Sydney.md @@ -24,7 +24,7 @@ SY ADC is responsible for the Class C airspace in the SY CTR `SFC` to `A005` as shown below.
-![SY ADC Airspace](img/SYTWR.png){ width="700" } +![SY ADC Airspace](img/syadc.png){ width="700" }
SY ADC Airspace
diff --git a/docs/aerodromes/classc/Williamtown.md b/docs/aerodromes/classc/Williamtown.md index af517ee1b..79f9e8cfb 100644 --- a/docs/aerodromes/classc/Williamtown.md +++ b/docs/aerodromes/classc/Williamtown.md @@ -17,24 +17,136 @@ YWLM is a [joint military/civil aerodrome](../../../controller-skills/military/#military-aerodromes) and procedures can differ significantly to those at a civil aerodrome. Ensure you are familiar with the [military controller skills](../../../controller-skills/military) necessary to provide a quality service. ## Airspace -WLM ADC owns the airspace within the WLM MIL CTR A (`SFC`-`A050`). This may be amended/released as required between WLM ADC and WLM TCU. +WLM ADC owns the airspace within the WLM MIL CTR A (`SFC`-`A015`).
![WLM ADC Airspace](img/wlmadc.png){ width="700" }
WLM ADC Airspace
+### Restricted Area Activations +There are no [restricted areas or MOAs](../../controller-skills/sua) activated by default when WLM ADC is online. + +## Local Procedures +### Initial and Pitch +The [intial points](../../controller-skills/military/#initial-and-pitch) are aligned with Taxiway A at the following locations. + +| RWY | Initial Point | Altitude | +| ---- | ------------- | --------------------------- | +| 12 | South-western tip of Grahamstown Dam | `A025`
(`A020` for PC21) | +| 30 | Intersection of the coast and extended Taxiway A centreline | `A025`
(`A020` for PC21) | + +### Coded Clearances +Aircraft departing to the western training areas should be cleared the **STORM 1** coded clearance, in addition to the [appropriate SID](#sid-selection). The **STORM 1** coded clearance gives aircraft permission to transit via the **[Thunder Corridor](../../terminal/williamtown/#thunder-corridor)**, a [military corridor](../../controller-skills/military/#military-corridors) that connects the WLM TCU to the R560 amd R570 restricted areas. + +[Coordination](#acd-to-wlm-tcu) may be required with WLM TCU prior to issuing clearance to an aircraft intending to operate in an SUA. + +!!! phraseology + *BARN21 plans to enter R570 via THNDA for military training.* + **WLM ACD**: "BARN21, Cleared Storm 1. Runway 12, CLASSIC departure. Climb via SID to `FL110`, squawk 6003, departure frequency 135.7" + +!!! note + ACD shall write the coded clearance in the **global ops field** prior to issuing clearance, for the awareness of other controllers. + +#### Military Gates +There are numerous [military gates](../../controller-skills/military/#military-gates) established throughout the WLM TCU to facilitate entry and exit to adjoining SUA. + +
+![WLM SUA Gates](../../terminal/img/wlm_mil_gates.png){ width="700" } +
WLM SUA Gates
+
+ +Pilots should include the desired departure gate when requesting clearance. + +!!! phraseology + *RPLC15 plans to enter the M581 MOA via Gate 7 for military training and airwork.* + **RPLC15**: "Willy Delivery, RPLC15 for Gate 7, `F120` for M581, request clearance." + **WLM ACD**: "RPLC15, Willy Delivery. Cleared Gate 7, CLASSIC departure. Climb via SID to `F120`, squawk 6001, departure frequency 135.7." + +If the pilot **does not** nominate a gate, or nominates a gate that does not provide access to their intended SUA, WLM ACD should clear the aircraft to depart via the **appropriate gate**. + +| Intended SUA | TCU Exit Gate | +| --------------- | ------------------- | +| M581 | Gates 4-7 | +| M582 | Gate 6 | +| M583 | Lightning Gate (LG) | +| M584 | Lightning Gate (LG) | +| R585A | Gate 1 | +| R585B | Gate 9 | +| R585C | Gate 10 | +| R585D | Gate 11 | +| R586 | Gates 1-3 | + +!!! tip + [Coordination requirements](#acd-to-wlm-tcu) exist between ACD and TCU when aircraft are requesting clearance to operate in an SUA that has not been activated. Controllers performing the role of ACD should ensure they coordinate with TCU before providing clearance + +### Special Use Airspace +#### Salt Ash SUA +The Salt Ash Air Weapons Range is located within the WLM MIL CTR, and is used for air-surface gunnery and bombing practice. It is entirely contained within the R596 [restricted area](../../controller-skills/sua/#restricted-areas). + +
+![The Salt Ash Weapons Range](../../terminal/img/wlm_salt_ash.png){ width="700" } +
The Salt Ash Air Weapons Range
+
+ +The restricted area can be activated in two configurations according to the requirements of the operation. Only VFR aircraft are permitted. + +| Configuration Name | Vertical Limits | Notes | +| ------------------ | ---------------- | ------ | +| R596 High | `SFC` - `A130` | Aircraft will remain on local QNH above `A100` | +| R596 Low | `SFC` - `A050` | | + +When the R596 restricted area is active all airspace within the SUA is managed by **WAL**, and the [ATIS should be updated](#sua-activations) to reflect the activation. + +Aircraft departing YWLM for the [Salt Ash Air Weapons Range (R596)] should be cleared the **SALT ASH** departure, in lieu of a SID. On this departure, aircraft will maintain runway heading until turning between 2 TAC and 7.5 TAC WLM to enter the restricted area. + +!!! phraseology + *RPLC15 plans to enter the M581 MOA via Gate 7 for military training and airwork.* + **PTHR21**: "Willy Delivery, PTHR21 for Salt Ash High, `A100`, transit not above `A050`, request clearance." + **WLM ACD**: "PTHR21, Willy Delivery. Standby." + *WLM ACD [coordinates the SUA activation request](#acd-to-wlm-tcu) with WAL* + **WLM ACD**: "PTHR21, clearance available." + **PTHR21**: "PTHR21" + **WLM ACD**: "PTHR21, cleared Salt Ash runway 12 departure, transit `A050` for operations in Salt Ash High, not above `A100`, squawk 6001." + ## SID Selection -Aircraft planned via **KEXAR**, **LIMLO**, **MONDO**, and **UBNON^** shall be assigned the **Procedural SID** that terminates at the appropriate SID terminus. Jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID. +### Civil Aircraft +Civil aircraft planned via **KEXAR**, **LIMLO**, **MONDO**, and **[UBSON](#ubson-departures)** shall be assigned the **Procedural SID** that terminates at the appropriate SID terminus. Civil jet Aircraft **not** planned via any of these waypoints shall receive amended routing via the most appropriate SID terminus, unless the pilot indicates they are unable to accept a Procedural SID. + +Civil aircraft unable to accept a procedural SID and **non-RNAV** aircraft shall be assigned either the RADAR SID or a visual departure. + +#### UBSON Departures +When the R596 restricted area is active, aircraft planned via **UBSON** and departing Runway 12 shall be assigned the **UBSON BRAVO** SID. -Aircraft unable to accept a procedural SID, and **non-RNAV** aircraft shall be assigned either the RADAR SID or a visual departure. +### Military Aircraft +Military aircraft planned for **Gate 1 and Gate 2** shall be assigned the **PEPPER** SID. -!!! note - ^ When the R596 area is active, aircraft planned via **UBNON** and departing Runway 12 shall be assigned the **UBNON BRAVO** SID. +Military aircraft planned for **Gates 3-7**, or for the western training areas, shall be assigned the **CLASSIC** SID. Aircraft planned for the western training areas will additionally be cleared via the **STORM** [coded clearance](#coded-clearances) + +Military Aircraft planned for the **[Salt Ash Air Weapons Range](#salt-ash-sua)** shall be assigned a **SALT ASH** departure. + +All other military aircraft, including military aircraft that are unable to fly a SID, shall be assigned either the RADAR SID or a visual departure. + +## ATIS +### Approach Types +During high levels of military traffic, **WAL** may nominate [stereo approaches](../../military/#stereo-approaches) as the preferred approach type. + +| Condition | ATIS APCH field | +| ----------------- | --------------- | +| Stereo Approaches | `MIL ACFT EXP STEREO APCH` | + +### Operational Info +#### SUA Activations +The Operational Information field should be updated when either of the [Salt Ash Weapons Range](#salt-ash-sua) restricted areas are active. + +| Activated SUA | OPR INFO Field | +| ------------- | -------------- | +| R596 High | `R 5 9 6 HIGH ACTIVE` | +| R596 Low | `R 5 9 6 LOW ACTIVE` | ## Coordination ### Auto Release -[Next](../../controller-skills/coordination.md#next) coordination is **not** required from WLM ADC to WLM TCU for aircraft that are: +[Next](../../controller-skills/coordination/#next) coordination is **not** required from WLM ADC to WLM TCU for aircraft that are: - Departing from a runway nominated in the ATIS; and - Assigned the standard assignable level; and @@ -43,15 +155,24 @@ Aircraft unable to accept a procedural SID, and **non-RNAV** aircraft shall be a The Standard Assignable level from WLM ADC to WLM TCU is: | Aircraft | Level | -| ------- | ----- | +| -------- | ----- | | All | The lower of `F120` and `RFL` | - -### 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. + +### ACD to WLM TCU +The controller assuming responsibility of **ACD** shall give [heads-up](../../controller-skills/coordination/#airways-clearance) coordination to WAL (or the enroute controller responsible for the WLM TCU) prior to the issue of a clearance to an aircraft intending to operate in an SUA that **has not** been activated. !!! phraseology - **WAL** -> **WLM ADC**: "via WLM, ZULU, Close formation of 5, do you have any restrictions or requirements?” - **WLM ADC** -> **WAL**: "ZULU, no restrictions or requirements, `A040`" + **WLM ACD** -> **WAL**: "PTHR11 requests clearance to R570 via Thunder corridor.” + **WAL** -> **WLM ACD**: "PTHR11, clearance approved." + +### Departures Controller +When a TCU controller is online, aircraft shall be issued with a departure frequency during their airways clearance in accordance with the table below. If no TCU controllers are online, the advisory frequency shall be issued. + +| Runway | Via | Departure Frequency | +| ------ | ---- | ------------------- | +| All | All | 135.7 (WAL) | + ## Charts !!! abstract "Reference" - Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new} \ No newline at end of file + In addition to the civilian `ERSA` and `AIP` publications, [the RAAF AIP website](https://ais-af.airforce.gov.au/australian-aip){target=new} contains the necessary charts (available in the TERMA) and description of procedures (in each airports' FIHA). + diff --git a/docs/aerodromes/classc/img/CBTWR.png b/docs/aerodromes/classc/img/CBTWR.png deleted file mode 100644 index 4941b7c99..000000000 Binary files a/docs/aerodromes/classc/img/CBTWR.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/CGTWR.png b/docs/aerodromes/classc/img/CGTWR.png deleted file mode 100644 index 70dc6477a..000000000 Binary files a/docs/aerodromes/classc/img/CGTWR.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/ENTWR.png b/docs/aerodromes/classc/img/ENTWR.png deleted file mode 100644 index 7cc53772f..000000000 Binary files a/docs/aerodromes/classc/img/ENTWR.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/PHTWR.png b/docs/aerodromes/classc/img/PHTWR.png deleted file mode 100644 index 651d2d5df..000000000 Binary files a/docs/aerodromes/classc/img/PHTWR.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/cbadc.png b/docs/aerodromes/classc/img/cbadc.png index 02105a8c5..4941b7c99 100644 Binary files a/docs/aerodromes/classc/img/cbadc.png and b/docs/aerodromes/classc/img/cbadc.png differ diff --git a/docs/aerodromes/classc/img/mladc.png b/docs/aerodromes/classc/img/mladc.png deleted file mode 100644 index e90584a9f..000000000 Binary files a/docs/aerodromes/classc/img/mladc.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/phadc.png b/docs/aerodromes/classc/img/phadc.png deleted file mode 100644 index 879b0ea1f..000000000 Binary files a/docs/aerodromes/classc/img/phadc.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/SYTWR.png b/docs/aerodromes/classc/img/syadc.png similarity index 100% rename from docs/aerodromes/classc/img/SYTWR.png rename to docs/aerodromes/classc/img/syadc.png diff --git a/docs/aerodromes/classc/img/wlmadc.png b/docs/aerodromes/classc/img/wlmadc.png index 97e3061e5..3dae90a3e 100644 Binary files a/docs/aerodromes/classc/img/wlmadc.png and b/docs/aerodromes/classc/img/wlmadc.png differ diff --git a/docs/aerodromes/classc/img/wlmapp.png b/docs/aerodromes/classc/img/wlmapp.png deleted file mode 100644 index a01211399..000000000 Binary files a/docs/aerodromes/classc/img/wlmapp.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/wlmtcu.png b/docs/aerodromes/classc/img/wlmtcu.png deleted file mode 100644 index 30d8323a6..000000000 Binary files a/docs/aerodromes/classc/img/wlmtcu.png and /dev/null differ diff --git a/docs/aerodromes/classc/img/wlmtwr.png b/docs/aerodromes/classc/img/wlmtwr.png deleted file mode 100644 index 648185a39..000000000 Binary files a/docs/aerodromes/classc/img/wlmtwr.png and /dev/null differ diff --git a/docs/controller-skills/military.md b/docs/controller-skills/military.md index 1c0c752e4..b50d9f2ed 100644 --- a/docs/controller-skills/military.md +++ b/docs/controller-skills/military.md @@ -188,7 +188,7 @@ Clearing an aircraft for a stereo approach gives aircraft permission to descend **CLAS11**: "Tindal Approach, CLAS11. `A090` visual, for stereo approach with information A" **TNA**: "CLAS11, Tindal Approach, track via stereo approach, not below `A060`" **CLAS11**: "Track via stereo approach, not below `A060`, CLAS11" - + Stereo approaches should generally be used during high military traffic levels, and nominated on the appropriate aerodrome ATIS. ### Restricted Area Operations in Civil Airspace diff --git a/docs/controller-skills/sua.md b/docs/controller-skills/sua.md index 6a6f6e378..bd55905cb 100644 --- a/docs/controller-skills/sua.md +++ b/docs/controller-skills/sua.md @@ -89,7 +89,7 @@ SUA may also be activated by controllers **upon request** of an aircraft perform Where a requested airspace release would impact a large number of pilots, consider working with the aircraft to establish a mutually beneficial solution. The full extent of the requested airspace can be released at a later time when the traffic picture allows. -Controllers shall ensure that SUA activation is limited to the **smallest extent necessary** to enable the requested operations while ensuring adequate [separation](#separation) with non-participating aircraft. +Controllers shall ensure that SUA activation is limited to the **smallest extent necessary** to enable the requested operations while ensuring adequate [separation](#separation-from-sua) with non-participating aircraft. !!! warning "Important" Activation of SUA in excess of operational requirements, or when there is no active/planned operations at all, is unreasonable and not permitted. @@ -141,4 +141,3 @@ Vertical limits of an SUA activation should include a buffer of at least 1000ft !!! example A military exercise is planned in the R225J restricted area, involving abrupt vertical manoeuvres from `SFC` to `F196`. ASP applies a buffer of 1000ft to the upper limit of the exercise, and activates the restricted area from`SFC-F210`. - diff --git a/docs/enroute/brisbane/ARL.md b/docs/enroute/brisbane/ARL.md index ea3c4f6d6..df861eb3a 100644 --- a/docs/enroute/brisbane/ARL.md +++ b/docs/enroute/brisbane/ARL.md @@ -80,7 +80,6 @@ Arrivals from the north shall be given initial descent to not below `F250`. **CN **ARL:** "RXA6417, recleared direct BOREE for the BOREE4A arrival, runway 34L, maintain F180" **RXA6417:** "Recleared direct BOREE for the BOREE4A arrival, runway 34L, maintain F180, RXA6417" - #### Sequencing Sequencing arrivals from the north/east into YSSY is a joint responsibility of the subsectors of ARL. Initial sequencing actions for aircraft from the north should be performed by ARL, with fine tuning and any holding required issued by CNK. @@ -145,11 +144,99 @@ The following subsectors are responsible for issuing STAR clearance. | MNN | LAXUM | All | | | OCN | ASUVA | All | | - +The MOAs directly adjoin the WLM TCU, and when WAL is online aircraft will be transferred directly to/from the MOAs. When [WAL is offline](#reclassifications), aircraft will contact ARL for transit through the surrounding civilian airspace. + +##### Affected Civil Operations +When activated these MOAs significantly disrupt traffic on the busy **A579**, **B450**, **B474**, **B580**, and **H258** high altitude airways, which connect YSSY to the Pacific and North America. + +| Planned Airway | ERSA Recommended Rerouting | +| -------------- | -------------------------- | +| A579 | `DIPSO G595 ATNAT DCT DUDEP DCT UPSAD A579 ...` | +| B450 | `DIPSO G595 ATNAT DCT ABARB B450 ...` | +| B474 | `OLSEM Y193 BANDA DCT VEMLA B474 ...`
`DIPSO G595 ATNAT DCT DUDEP Y70 BISAB J328 ISTEM B474 ...` (when M670 is also active) | +| B580 | `DIPSO G595 ATNAT DCT DUDEP Y70 BISAB J328 MISLY B580 ...` | + +The **W149** and **W768** low altitude airways, connecting YLHI to YWLM and YPMQ, are also affected, requiring extensive rerouting or facilitated transit through the SUA. + +!!! note + Aircraft tracking via a recommended rerouting must still be [separated from the SUA](../../sua/#separation-from-sua) laterally and vertically. After amending flight plans for the purposes of rerouting around SUA, controllers should ensure the route is displayed visually and the BRL is used to measure for [>2.5nm](../../sua/#controlled-airspace) clearance with all parts of the SUA. + +#### R560 & R570 Williamtown +The R560A-B and R570A-H restricted areas are located west of YWLM and YSTW within the ARL and MDE subsectors. The restricted areas are connected to the WLM TCU by the **Thunder Corridor**. + +
+![WLM Thunder Military Corridor](../img/wlm_thunder.png){ width="500" } +
WLM Thunder Military Corridor
+
+ +Aircraft departing the WLM TCU will be cleared the **STORM 1** coded clearance. Aircraft returning to the TCU will be cleared the **STORM 2** coded clearance by ARL. + +!!! phraseology + *BARN21 has completed their military training operations in R570, and intends to return to base.* + **BARN21**: "Brisbane Centre, BARN21" + **ARL**: "BARN21, Brisbane Centre, identified" + **BARN21**: "Brisbane Centre, BARN21, detail complete, for RTB, `F130`" + **ARL**: "BARN21, cleared Storm 2. At THNDA, contact Willy Approach, 135.7" + **BARN21**: "Cleared Storm 2, at THNDA contact Willy Approach, BARN21" + +!!! note + Aircraft tracking via the STORM coded clearances does **not** constitute a voiceless coordination route between WLM TCU and ARL. Aircraft should still be heads-up coordinated prior to **5 minutes** to the boundary, unless coordinated otherwise. + +Aircraft transiting the Thunder Corridor should be assigned the appropriate altitude to ensure separation with opposite direction traffic while transiting to their desired restricted area. + +| Coded Clearance | Altitude | +| --------------- | -------- | +| STORM 1 | `F140` | +| STORM 2 | `F130` | + +##### Affected Civil Operations +When activated these restricted areas distrupt traffic on the **Q16**, **Q235**, **Q293**, and **Y46** high altitude airways, used by aircraft travelling between YPAD-YBBN, and YSSY-North Queensland/East Asia. + +| Planned Airway | ERSA Recommended Rerouting | +| -------------- | -------------------------- | +| Q16 | via `Q4` | +| Q235 | `... RIC H530 KABIX ...` | +| Q293 | `... RIC H530 KABIX ...` | +| Y46 | via `Y27` | + +Aircraft travelling below `F240` on the **H66**, **H76**, and **Q35** airways are also disrupted, most directly affecting aircraft departing YSBK to the northwest, and aircraft climbing out of YSSY via RIC. These aircraft may be given altitude requirements to assure separation with the restricted areas, where appropriate. + +!!! note + Aircraft tracking via a recommended rerouting must still be [separated from the SUA](../../sua/#separation-from-sua) laterally and vertically. After amending flight plans for the purposes of rerouting around SUA, controllers should ensure the route is displayed visually and the BRL is used to measure for [>2.5nm](../../sua/#controlled-airspace) clearance with all parts of the SUA. + +#### R585-R586 Williamtown +The R585A-D and R586A-C restricted areas are located north of the WLM TCU in the ARL and MNN subsectors. + +The MOAs directly adjoin the WLM TCU, and when WAL is online aircraft will be transferred directly to/from the restricted areas. When [WAL is offline](#reclassifications), aircraft will contact ARL for transit through the surrounding civilian airspace. + +#### Amberley SUA +There are three SUA associated with military operations at [Amberley](../../terminal/amberleyoakey) which clip ARL airspace: the R639D restricted area, located northeast of MOR VOR partially in the MDE subsector, and the M661A and M670A-B MOAs, which clips MNN airspace offshore east of YCFS. + +AMA (or INL(DOS, INL, SDY) on their behalf) will coordinate the activation these SUA **prior** to any activity. ## STAR Clearance Expectation ### Handoff @@ -240,11 +327,10 @@ Additionally, Voiceless Coordination exists from SY TCU for aircraft: - With ADES **YWLM**; and - Assigned a STAR; and -- Tracking from **SDN** or **SDS** [airspace](../../../terminal/sydney/#airspace-division); and - Assigned the lower of `F130` or the `RFL` !!! note - YWLM arrivals are handed off to MLD, not directly to WLM TCU, unless coordinated as such + YWLM arrivals are handed off to MLD, not directly to WLM TCU, unless otherwise coordinated. ### Enroute As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary. @@ -311,9 +397,12 @@ The Standard Assignable level from ARL/MDE to **TW ADC** is `A080`, any other le ### WLM TCU #### Airspace -By default, WLM TCU owns the airspace from `SFC` to `F125`. In exceptional circumstances, such as specific military exercises or events, an additional TCU controller may log on, splitting the TCU vertically. In these situations, the controller will negotiate an upper limit with ARL(All) which works for both parties. +By default, WLM TCU owns the airspace from `SFC` to `F125`. -When WLM TCU is active above `F125` by ad-hoc release, **WLM-H_APP** owns the airspace above `F125`. +An additional, non-standard TCU position may be activated for specific military exercises or events to control airspace above `F125`. When this happens, **WAH** owns the airspace above `F125` to the agreed upper limit. + +!!! note + The upper limit of **WAH** must be coordinated with ARL *prior* to the position logging on. Refer to [Reclassifications](#reclassifications) for operations when WLM TCU is offline. @@ -326,8 +415,8 @@ Voiceless for all aircraft: All other aircraft going to ARL CTA will be **Heads-up** Coordinated by WLM TCU. !!! phraseology - **WLM TCU** -> **MLD**: "QJE1597, request DCT OMGAB" - **MLD** -> **WLM TCU**: "QJE1597, concur DCT OMGAB" + **WAL** -> **MLD**: "QJE1597, request DCT OMGAB" + **MLD** -> **WAL**: "QJE1597, concur DCT OMGAB" #### Arrivals/Overfliers Voiceless for all aircraft: @@ -339,8 +428,8 @@ 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. !!! phraseology - **CNK** -> **WLM TCU**: "QFA1968, request DCT UPTEB" - **WLM TCU** -> **CNK**: "QFA1968, concur DCT UPTEB" + **CNK** -> **WAL**: "QFA1968, request DCT UPTEB" + **WAL** -> **CNK**: "QFA1968, concur DCT UPTEB" ### TSN/HWE (Oceanic) As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. diff --git a/docs/enroute/brisbane/KEN.md b/docs/enroute/brisbane/KEN.md index 2407fe81b..85178d6cb 100644 --- a/docs/enroute/brisbane/KEN.md +++ b/docs/enroute/brisbane/KEN.md @@ -58,7 +58,7 @@ The following subsectors are responsible for issuing STAR clearance. === "RWY 33" | Subsector | STAR | Type | Notes | | ---- | ----- | -------- | ----- | - | BAR | HENDO
KEEWIE
TOTTY | All | INST APCH
VISUAL APCH
RNP-W | + | BAR | HENDO
KEEWI
TOTTY | All | INST APCH
VISUAL APCH
RNP-W | | KEN | HENDO
TOTTY | All | INST APCH
RNP-W | | TBP | HENDO
TOTTY | All | Descent not below `F190` | diff --git a/docs/enroute/img/arl_sua.png b/docs/enroute/img/arl_sua.png new file mode 100644 index 000000000..666176150 Binary files /dev/null and b/docs/enroute/img/arl_sua.png differ diff --git a/docs/enroute/img/wlm_thunder.png b/docs/enroute/img/wlm_thunder.png new file mode 100644 index 000000000..324359acb Binary files /dev/null and b/docs/enroute/img/wlm_thunder.png differ diff --git a/docs/enroute/melbourne/GUN.md b/docs/enroute/melbourne/GUN.md index 5af3aaeab..a27ea3327 100644 --- a/docs/enroute/melbourne/GUN.md +++ b/docs/enroute/melbourne/GUN.md @@ -126,11 +126,17 @@ Refer to the vatSys Enroute Holds map for details of published holds on the airw ### YWLM -[SY TCU is responsible](../../../terminal/sydney/#ywlm-stars) for issuing STARs to aircraft inbound to YWLM via **EKIPU** and **OVLUX**. BIK/KAT shall conduct heads-up coordination with the relevant SY TCU controller to facilitate initial descent. +#### STAR Assignment +| Subsector | STAR | Type | Notes | +| ---- | ----- | -------- | ----- | +| BIK | EKIPU
OVLUX | All | Descent not below `F290`
Descent not below `F290` | +| KAT | EKIPU
OVLUX | All | Descent not below `F290`
Descent not below `F290` | + +BIK/KAT shall conduct heads-up coordination with the relevant SY TCU controller to facilitate further descent. !!! phraseology - **BIK** -> **SAS**: "via RIVET, JST472, will be assigned F250" - **SAS** -> **BIK**: "JST472, F250" + **BIK** -> **SAS**: "via RIVET, JST472, will be assigned `F250`" + **SAS** -> **BIK**: "JST472, `F250`" ## STAR Clearance Expectation ### Handoff diff --git a/docs/oceanic/.pages b/docs/oceanic/.pages new file mode 100644 index 000000000..f992e1256 --- /dev/null +++ b/docs/oceanic/.pages @@ -0,0 +1,8 @@ +title: Oceanic +nav: + - Overview: index.md + - Procedures: procedures.md + - Positions: + - Indian (IND): IND.md + - Tasman (TSN): TSN.md + - ... \ No newline at end of file diff --git a/docs/oceanic/Positions/IND.md b/docs/oceanic/IND.md similarity index 66% rename from docs/oceanic/Positions/IND.md rename to docs/oceanic/IND.md index 751218a43..39c455689 100644 --- a/docs/oceanic/Positions/IND.md +++ b/docs/oceanic/IND.md @@ -16,17 +16,17 @@ 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). ### CPDLC -The Primary Communication Method for IND is [CPDLC](../../../client/cpdlc). Voice may be used in lieu when applicable. The CPDLC Station Code is `YIND`. +The Primary Communication Method for IND is [CPDLC](../../client/cpdlc). Voice may be used in lieu when applicable. The CPDLC Station Code is `YIND`. ## Airspace
-![Indian Airspace (Zoomed)](../assets/indzoomin.png){width="700" } +![Indian Airspace (Zoomed)](img/indzoomin.png){width="700" }
Indian Airspace (Zoomed)
-![Indian Airspace](../assets/indzoomout.png){width="700" } +![Indian Airspace](img/indzoomout.png){width="700" }
Indian Airspace
@@ -40,20 +40,20 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR | Transferring Sector | Receiving Sector | ADES | Notes | | ---- | -------- | --------- | --------- | -| IND | HYD(LEA, JAR) | YPPH | | +| IND | HYD(LEA, JAR) | YPPH | | ## Coordination ### Domestic Enroute -As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. +As per [Standard coordination procedures](../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. ### IND Internal -As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. +As per [Standard coordination procedures](../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. ### TSN/NZZO/NZCM (Pacific Oceanic) -As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. +As per [Standard coordination procedures](../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. ### 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. +As per [Standard coordination procedures](../../controller-skills/coordination/#other-units), Heads-up Coordination required for all aircraft prior to **30 mins** from boundary. !!! phraseology **IND** -> **FAJO FSS**: "Estimate, SAA281, XEKOT time 44, F360" diff --git a/docs/oceanic/Positions/TSN.md b/docs/oceanic/TSN.md similarity index 74% rename from docs/oceanic/Positions/TSN.md rename to docs/oceanic/TSN.md index 3913e0c84..bc3f6bd45 100644 --- a/docs/oceanic/Positions/TSN.md +++ b/docs/oceanic/TSN.md @@ -19,32 +19,38 @@ 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). ### CPDLC -The Primary Communication Method for TSN is [CPDLC](../../../client/cpdlc). Voice may be used in lieu when applicable. The CPDLC Station Code is `YTSN`. +The Primary Communication Method for TSN is [CPDLC](../../client/cpdlc). Voice may be used in lieu when applicable. The CPDLC Station Code is `YTSN`. ## Airspace
-![Tasman Airspace](../assets/tsn.png){width="500" } +![Tasman Airspace](img/tsn.png){width="500" }
Tasman Airspace
+#### Extending +!!! warning "Important" + TSN (and its subsectors) are **not permitted** to extend to any adjacent Domestic/International sectors + ### Howe (HWE) HWE is a non-standard subsector that sits within TSN. Unlike TSN, it operates as a **VHF Surveillance** sector when it is open. Due to limitations in VHF/HF coupling, HWE **cannot** extend to adjacent HF units. +#### Sector Ownership +Due to limitations in vatSys, TSN cannot relinquish sector ownership of the HWE sector when HWE is online. Tracks inbound to HWE airspace will appear as Blue Announced tracks to both TSN and HWE. + ### Coral (COL) 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 "Important" - TSN (and its subsectors) are **not permitted** to extend to any adjacent Domestic/International sectors +## Surveillance Coverage +Limited surveillance coverage exists for aircraft in CTA greater than **250nm** from LHI. [Procedural Standards](../../separation-standards/procedural/) must be implemented **prior** to losing surveillance coverage -## Sector Ownership -Due to limitations in vatSys, TSN cannot relinquish sector ownership of the HWE sector when HWE is online. Tracks inbound to HWE airspace will appear as Blue Announced tracks to both TSN and HWE. +## Local Procedures +### Special Use Airspace +There are multiple volumes of [SUA](../../controller-skills/sua) within TSN airspace, mostly associated with military operations in and out of YAMB and YWLM. -## Surveillance Coverage -Limited surveillance coverage exists for aircraft in CTA greater than **250nm** from LHI. [Procedural Standards](../../../separation-standards/procedural/) must be implemented **prior** to losing surveillance coverage +AMA (or INL on their behalf) and WLM TCU (or ARL) will coordinate the activation these SUA **prior** to any activity. ## STAR Clearance Expectation ### Handoff @@ -58,10 +64,10 @@ Aircraft being transferred to the following sectors shall be told to Expect STAR ## Coordination ### Domestic Enroute -As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. +As per [Standard coordination procedures](../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. ### TSN Internal -As per [Standard coordination procedures](../../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. +As per [Standard coordination procedures](../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. !!! 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. @@ -72,10 +78,10 @@ Aircraft leaving HWE in it's surveillance configuration must have their identifi **HWE**: "UAE845, identification terminated, report position to Brisbane Radio, 124.65" ### NWWWA/NVVVA -The vertical limits of CTA within TSN and NWWWA/NVVVA mean it is not possible for an aircraft to transit directly from either TCU into TSN CTA and vice versa. As per [Standard coordination procedures](../../../controller-skills/coordination/#octa-coordination) no coordination is required, provided there are no changes to route or level within **5 mins** to boundary. +The vertical limits of CTA within TSN and NWWWA/NVVVA mean it is not possible for an aircraft to transit directly from either TCU into TSN CTA and vice versa. As per [Standard coordination procedures](../../controller-skills/coordination/#octa-coordination) no coordination is required, provided there are no changes to route or level within **5 mins** to boundary. ### 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. +As per [Standard coordination procedures](../../controller-skills/coordination/#pacific-units), Voiceless, no changes to route or CFL within **15 mins** to boundary. !!! 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. diff --git a/docs/oceanic/assets/10min.png b/docs/oceanic/img/10min.png similarity index 100% rename from docs/oceanic/assets/10min.png rename to docs/oceanic/img/10min.png diff --git a/docs/oceanic/assets/15DME.png b/docs/oceanic/img/15DME.png similarity index 100% rename from docs/oceanic/assets/15DME.png rename to docs/oceanic/img/15DME.png diff --git a/docs/oceanic/assets/15min.png b/docs/oceanic/img/15min.png similarity index 100% rename from docs/oceanic/assets/15min.png rename to docs/oceanic/img/15min.png diff --git a/docs/oceanic/assets/20DME.png b/docs/oceanic/img/20DME.png similarity index 100% rename from docs/oceanic/assets/20DME.png rename to docs/oceanic/img/20DME.png diff --git a/docs/oceanic/assets/50RNAV.png b/docs/oceanic/img/50RNAV.png similarity index 100% rename from docs/oceanic/assets/50RNAV.png rename to docs/oceanic/img/50RNAV.png diff --git a/docs/oceanic/assets/Both.png b/docs/oceanic/img/Both.png similarity index 100% rename from docs/oceanic/assets/Both.png rename to docs/oceanic/img/Both.png diff --git a/docs/oceanic/assets/ETP.png b/docs/oceanic/img/ETP.png similarity index 100% rename from docs/oceanic/assets/ETP.png rename to docs/oceanic/img/ETP.png diff --git a/docs/oceanic/assets/Oceanic.png b/docs/oceanic/img/Oceanic.png similarity index 100% rename from docs/oceanic/assets/Oceanic.png rename to docs/oceanic/img/Oceanic.png diff --git a/docs/oceanic/assets/OffTrack.png b/docs/oceanic/img/OffTrack.png similarity index 100% rename from docs/oceanic/assets/OffTrack.png rename to docs/oceanic/img/OffTrack.png diff --git a/docs/oceanic/assets/POCA.png b/docs/oceanic/img/POCA.png similarity index 100% rename from docs/oceanic/assets/POCA.png rename to docs/oceanic/img/POCA.png diff --git a/docs/oceanic/assets/conflictarea.png b/docs/oceanic/img/conflictarea.png similarity index 100% rename from docs/oceanic/assets/conflictarea.png rename to docs/oceanic/img/conflictarea.png diff --git a/docs/oceanic/assets/conflictarea2.png b/docs/oceanic/img/conflictarea2.png similarity index 100% rename from docs/oceanic/assets/conflictarea2.png rename to docs/oceanic/img/conflictarea2.png diff --git a/docs/oceanic/assets/indzoomin.png b/docs/oceanic/img/indzoomin.png similarity index 100% rename from docs/oceanic/assets/indzoomin.png rename to docs/oceanic/img/indzoomin.png diff --git a/docs/oceanic/assets/indzoomout.png b/docs/oceanic/img/indzoomout.png similarity index 100% rename from docs/oceanic/assets/indzoomout.png rename to docs/oceanic/img/indzoomout.png diff --git a/docs/oceanic/assets/navcap2.png b/docs/oceanic/img/navcap2.png similarity index 100% rename from docs/oceanic/assets/navcap2.png rename to docs/oceanic/img/navcap2.png diff --git a/docs/oceanic/assets/navcapZ.png b/docs/oceanic/img/navcapZ.png similarity index 100% rename from docs/oceanic/assets/navcapZ.png rename to docs/oceanic/img/navcapZ.png diff --git a/docs/oceanic/assets/oceanicmap.png b/docs/oceanic/img/oceanicmap.png similarity index 100% rename from docs/oceanic/assets/oceanicmap.png rename to docs/oceanic/img/oceanicmap.png diff --git a/docs/oceanic/assets/tsn.png b/docs/oceanic/img/tsn.png similarity index 100% rename from docs/oceanic/assets/tsn.png rename to docs/oceanic/img/tsn.png diff --git a/docs/oceanic/index.md b/docs/oceanic/index.md index ffba9f47f..6cdaf31e3 100644 --- a/docs/oceanic/index.md +++ b/docs/oceanic/index.md @@ -26,7 +26,7 @@ RJTG - Fukuoka Oceanic Under the agreement, a controller holding an oceanic endorsement may control positions within any of these FIRs.
-![Pacific Oceanic Agreement Units](assets/oceanicmap.png){width="700"} +![Pacific Oceanic Agreement Units](img/oceanicmap.png){width="700"}
Pacific Oceanic Agreement Units
diff --git a/docs/separation-standards/procedural.md b/docs/separation-standards/procedural.md index 32251748d..4f87a4598 100644 --- a/docs/separation-standards/procedural.md +++ b/docs/separation-standards/procedural.md @@ -50,7 +50,7 @@ title: Procedural ## Longitudinal
-![Oceanic](../oceanic/assets/Oceanic.png) +![Oceanic](../oceanic/img/Oceanic.png)
Longitudinal separation shall only be applied between aircraft on same or reciprocal tracks. @@ -65,13 +65,13 @@ Longitudinal time separation must be established by using pilot estimates and en #### Same Track Aircraft that are on the same track, including situations where one aircraft is climbing or descending through the level of another, are to be separated by **10 minutes**
-![10min](../oceanic/assets/10min.png) +![10min](../oceanic/img/10min.png)
#### Reciprocal Track Aircraft flying on reciprocal tracks may only be separated vertically. Such separation must exist **at least 10 minutes** prior to the estimated time of passing
-![ETP](../oceanic/assets/ETP.png) +![ETP](../oceanic/img/ETP.png)
After the estimated time of passing, aircraft may not climb or descend through the level of the opposite direction aircraft until **10 minutes** after the estimated time of passing. It is possible to reduce this requirement if definite passing has been achieved, and this will be explained later in this section. @@ -132,12 +132,12 @@ Distance checks must be conducted as per the following table: ### Time-based crossing track Aircraft that are on crossing tracks, including situations where one aircraft is climbing or descending through the level of another, are to be separated by **15 minutes** at the point of intersection
-![15min](../oceanic/assets/15min.png) +![15min](../oceanic/img/15min.png)
Where a difference 15 minutes does not exist at the crossing point, vertical separation shall be applied from the time at which the second aircraft is 15 minutes from the crossing point until the first aircraft is 15 minutes past the crossing point.
-![Both](../oceanic/assets/Both.png) +![Both](../oceanic/img/Both.png)
@@ -160,12 +160,12 @@ All aircraft have a NAVCAP, associated with a ***Circular Error of Position***. | Z | None | 30nm |
-![NAVCAP Z Example](../oceanic/assets/navcapZ.png){ width="300" } +![NAVCAP Z Example](../oceanic/img/navcapZ.png){ width="300" }
NAVCAP Z Example
-![NAVCAP 2 Example](../oceanic/assets/navcap2.png){ width="300" } +![NAVCAP 2 Example](../oceanic/img/navcap2.png){ width="300" }
NAVCAP 2 Example
@@ -187,7 +187,7 @@ The minimum number you must select when using the tool, is equal to: **Aircraft #### Working with Conflict Area
-![Conflict Area Example 1](../oceanic/assets/conflictarea.png){ width="300" } +![Conflict Area Example 1](../oceanic/img/conflictarea.png){ width="300" }
Conflict Area Example 1
@@ -200,7 +200,7 @@ Once you've established the Conflict area, you now know the area in which the ai Using the time standard, aircraft are considered to have entered the conflict area **5 minutes prior** to the estimate shown, and to have left the conflict area **5 minutes after** the estimate shown.
-![Conflict Area Example 2](../oceanic/assets/conflictarea2.png){ width="600" } +![Conflict Area Example 2](../oceanic/img/conflictarea2.png){ width="600" }
Conflict Area Example 2
diff --git a/docs/terminal/darwin.md b/docs/terminal/darwin.md index f506182cb..d36577cde 100644 --- a/docs/terminal/darwin.md +++ b/docs/terminal/darwin.md @@ -35,11 +35,6 @@ The CTR extends 7NM from the thresholds of runways 11 and 29 but does not includ ADC may request DN TCU (`SFC`-`A020`) from DN TCU to facilitate fixed-wing circuit operations. Fixed-wing circuit operations are typically conducted at Delissaville (YDLV) due to high traffic density at Darwin. -
-![DN ADC Airspace](img/dnadc.png){ width="700" } -
DN ADC Airspace
-
- ## Local Procedures ### IFR Training Area IFR aircraft requiring an area for training shall be cleared to operate in the North Eastern Training Area (NETA) diff --git a/docs/terminal/img/dnadc.png b/docs/terminal/img/dnadc.png deleted file mode 100644 index 1b499da83..000000000 Binary files a/docs/terminal/img/dnadc.png and /dev/null differ diff --git a/docs/terminal/img/ltarls.png b/docs/terminal/img/ltarls.png deleted file mode 100644 index 627d942f8..000000000 Binary files a/docs/terminal/img/ltarls.png and /dev/null differ diff --git a/docs/terminal/img/tltcu.png b/docs/terminal/img/tltcu.png deleted file mode 100644 index dc9456936..000000000 Binary files a/docs/terminal/img/tltcu.png and /dev/null differ diff --git a/docs/terminal/img/wlm_mil_corridors.png b/docs/terminal/img/wlm_mil_corridors.png new file mode 100644 index 000000000..9daca3d11 Binary files /dev/null and b/docs/terminal/img/wlm_mil_corridors.png differ diff --git a/docs/terminal/img/wlm_mil_gates.png b/docs/terminal/img/wlm_mil_gates.png new file mode 100644 index 000000000..a4a02beb6 Binary files /dev/null and b/docs/terminal/img/wlm_mil_gates.png differ diff --git a/docs/terminal/img/wlm_salt_ash.png b/docs/terminal/img/wlm_salt_ash.png new file mode 100644 index 000000000..ff1a5664e Binary files /dev/null and b/docs/terminal/img/wlm_salt_ash.png differ diff --git a/docs/terminal/img/wlmadc.png b/docs/terminal/img/wlmadc.png deleted file mode 100644 index 97e3061e5..000000000 Binary files a/docs/terminal/img/wlmadc.png and /dev/null differ diff --git a/docs/terminal/img/wlmapp.png b/docs/terminal/img/wlmapp.png deleted file mode 100644 index a01211399..000000000 Binary files a/docs/terminal/img/wlmapp.png and /dev/null differ diff --git a/docs/terminal/sydney.md b/docs/terminal/sydney.md index d5c01e228..4ccf9a71a 100644 --- a/docs/terminal/sydney.md +++ b/docs/terminal/sydney.md @@ -247,7 +247,24 @@ SFW/SFE may provide distance to touchdown, when transferring an aircraft to towe "QFA490, 8 miles to touchdown, contact tower 120.5" ### YWLM STARs -SY TCU is responsible for issuing STARs to aircraft inbound to YWLM via **EKIPU** and **OVLUX**. Aircraft shall be assigned the **EKIPU** or **OVLUX** STAR (as appropriate) by default, unless coordinated otherwise (eg. via the **IVTAG** STAR). +YWLM arrivals from the south and west will transit the SY TCU as they descend. BIK/KAT will provide these aircraft with their STAR clearance and initial descent, before conduct heads-up coordination with the relevant SY TCU controller to facilitate further descent. + +IFR aircraft which depart from the SY TMA with ADES YWLM must be issued STAR clearance by SY TCU. + +!!! phraseology + **BIK** -> **SAS**: "via RIVET, JST472, will be assigned `F250`" + **SAS** -> **BIK**: "JST472, `F250`" + +SY TCU is then responsible for facilitating descent to these aircraft to `F130` (or an otherwise [coordinated level](#ywlm-arrivals)), before handing the aircraft to ARL(MLD). + +Alternately, SY TCU may coordinate `F130` and "[no frequency requirements](../../controller-skills/coordination/#no-frequency-requirements-nfr)" with BIK/KAT, if traffic levels allow. This permits BIK/KAT to provide the aircraft with continuous descent as they transit the TMA. SAS is responsible for onwards coordination to other affected sectors within SY TCU, if multiple controllers are online. + + +!!! phraseology + **BIK** -> **SAS**: "via RIVET, QLK1997, will be assigned `F250`" + **SAS** -> **BIK**: "QLK1997, `F130` and no frequency requirements. My onwards with SDN." + **BIK** -> **SAS**: "QLK1997, `F130`, yours with SDN." + *BIK will put SAS C130 NFR in the label data, and hand the aircraft directly off to ARL(MLD).* ## Offline Towers ### BK ADC Offline @@ -473,11 +490,10 @@ Additionally, Voiceless Coordination exists to ARL(All) for aircraft: - With ADES **YWLM**; and - Assigned a STAR; and -- Tracking from **SDN** or **SDS** [airspace](#airspace-division); and - Assigned the lower of `F130` or the `RFL` !!! note - YWLM arrivals are handed off to ARL(MLD), not directly to WLM TCU, unless coordinated as such + YWLM arrivals are handed off to ARL(MLD), not directly to WLM TCU, unless otherwise coordinated. #### Arrivals Voiceless for all aircraft: diff --git a/docs/terminal/townsville.md b/docs/terminal/townsville.md index 857e217d0..1077cb67f 100644 --- a/docs/terminal/townsville.md +++ b/docs/terminal/townsville.md @@ -21,11 +21,6 @@ TL TCU owns the Class C and G airspace within 36 DME TL from `SFC` to `F180`
TL TCU Structure
-
-![TL Airspace Cross-Section](img/tltcu.png){ width="2000" } -
TL Airspace Cross-Section
-
- TL ADC owns the Class C airspace in the TL CTR (Extends to 7NM from the thresholds of Runway 01/19) from `SFC` to `A015`. This airspace is designed to facilitate helicopter and ciruit traffic. ## Flow diff --git a/docs/terminal/williamtown.md b/docs/terminal/williamtown.md index f4342383b..fc7398275 100644 --- a/docs/terminal/williamtown.md +++ b/docs/terminal/williamtown.md @@ -26,37 +26,170 @@ WLM TCU owns the airspace within the WLM MIL CTR `SFC` to `F125`.
WLM TCU Structure
-## Airspace Division -### Williamtown High and Low -**WLM APP** owns the WLM TCU airspace `SFC` to `F125`. +### WLM ADC +WLM ADC is responsible for the airspace within the WLM MIL CTR A from `SFC` to `A015`. + +### Airspace Division +**WAL** owns the WLM TCU airspace `SFC` to `F125`. -**WLM-H_APP** owns the airspace above `F125` when activated by ad-hoc release or NOTAM. +**WAH** owns any airspace above `F125` activated by ad-hoc release with ARL or NOTAM. !!! note - It is the responsibility of the WLM TCU controller(s) to negotiate any airspace releases with ARL. + The upper limit of **WAH** must be coordinated with ARL *prior* to the position logging on. -### WLM ADC -When WLM ADC is online, they own the airspace within the WLM MIL CTR A (`SFC`-`A050`). This may be amended/released as required between **WLM ADC** and **WLM TCU**. +### Restricted Area Activations +There are no [restricted areas or MOAs](../../controller-skills/sua) activated by default when WAL is online. + +#### SUA in Enroute Airspace +Most military operations will take place in SUA nearby the TCU in enroute airspace, outside the jurisdiction of WLM TCU. + +Upon receiving [airways clearance coordination from ACD](#acd-to-wlm-tcu) of an aircraft intending to operate in a currently inactive SUA, WLM TCU must give **heads up** coordination to relevant enroute controllers. + +This gives the enroute controller sufficient time to assess the request, make necessary adjustments to any aircraft in the area currently, and activate the SUA; or alternately to refuse the activation request before the aircraft is in the air. + +!!! phraseology + *PTHR11 is requesting clearance to operate in the R560A restricted area.* + **WLM ACD** -> **WAL**: "PTHR11 requests clearance to R560A via Thunder corridor.” + **WAL** -> **WLM ACD**: "Standby, call you back." + + **WAL** -> **ARL**: "On the groud YWLM, PTHR11, requests activation of R560A `A085-F240`, from 0300 until 0500.” + **ARL** -> **WAL**: "PTHR11, expect activation of R560A `A085-F240` at 0300 until 0500." + **WAL** -> **ARL**: "PTHR11." + + **WAL** -> **WLM ACD**: "PTHR11, clearance approved." + **WLM ACD** -> **WAL**: "Clearance approved, PTHR11" + +!!! note + The requirement to coordinate activation of an SUA is in **addition** to existing coordination requirements. [**Heads-up** coordination](#departures) is still required for these aircraft if they do not meet the voiceless coordination criteria. + +## Local Procedures +### Initial and Pitch +The [intial points](../../controller-skills/military/#initial-and-pitch) are aligned with Taxiway A at the following locations. + +| RWY | Initial Point | Altitude | +| ---- | ------------- | --------------------------- | +| 12 | South-western tip of Grahamstown Dam | `A025`
(`A020` for PC21) | +| 30 | Intersection of the coast and extended Taxiway A centreline | `A025`
(`A020` for PC21) | + +### Military Gates +There are numerous [military gates](../../controller-skills/military/#military-gates) established throughout the WLM TCU to facilitate entry and exit to adjoining SUA.
-![WLM ADC Airspace](img/wlmadc.png){ width="700" } -
WLM ADC Airspace
+![WLM SUA Gates](img/wlm_mil_gates.png){ width="700" } +
WLM SUA Gates
-## Local Procedures -### Stereo Approaches (Fast Jet Aircraft) -Fast jet aircraft typically transit from M550 to YWLM via Gate 6 at `F125`. When requested, or advised via ATIS, the stereo approach may be utilised to facilitate aircraft recovery. +If the pilot **does not** nominate a gate, or nominates a gate that does not provide access to their intended SUA, WLM ACD should clear the aircraft to depart via the **appropriate gate**. + +| Intended SUA | TCU Exit Gate | +| --------------- | ------------------- | +| M581 | Gates 4-7 | +| M582 | Gate 6 | +| M583 | Lightning Gate (LG) | +| M584 | Lightning Gate (LG) | +| R585A | Gate 1 | +| R585B | Gate 9 | +| R585C | Gate 10 | +| R585D | Gate 11 | +| R586 | Gates 1-3 | !!! tip - See [Controller Skills](../controller-skills/military.md#stereo-approaches) for more details about stereo approaches. + [Coordination requirements](#acd-to-wlm-tcu) exist between ACD and TCU when aircraft are requesting clearance to operate in an SUA that has not been activated. Controllers performing the role of ACD should ensure they coordinate with TCU before providing clearance + +### Military Corridors +There are two [military corridors](../controller-skills/military/#military-corridors) established around the WLM TCU to facilitate transit of military aircraft between the TCU and adjoining SUAs. -!!! phraseology - **MAPL45**: "Willy Approach, MAPL45, RTBing via G6, runway 12" - **WAL**: "MAPL45, Willy Approach, cleared stereo approach runway 12, via G6, once 9DME north of the TACAN, descend not below `A050`" - **MAPL45**: "Cleared stereo approach runway 12, via G6, once 9DME north of the TACAN, descend not below `A050`, MAPL45" +
+![WLM TCU Military Corridors](img/wlm_mil_corridors.png){ width="700" } +
WLM TCU Military Corridors
+
+ +These corridors are located **outside** the jurisdiction of the WLM TCU. + +#### Thunder Corridor +The **Thunder Corridor** is used by aircraft to transit civilian enroute airspace between the WLM TCU and the R560 and R570 restricted areas. + +Aircraft departing to the areas will be cleared the **STORM 1** coded clearance by ACD, aircraft returning to the airport will be cleared the **STORM 2** coded clearance by ARL. + +Aircraft transiting the Thunder Corridor should be assigned the appropriate altitude to ensure separation with opposite direction traffic while transiting to their desired restricted area. + +| Coded Clearance | Altitude | +| --------------- | -------- | +| STORM 1 | `F140` | +| STORM 2 | `F130` | !!! note - Stereo approach charts are available in the [RAAF TERMA](https://ais-af.airforce.gov.au/australian-aip){target=new}. + Aircraft tracking via the STORM coded clearance does **not** constitute a voiceless coordination route between WLM TCU and ARL. Aircraft should still be heads-up coordinated to ARL prior to **5 minutes** to the boundary, unless coordinated otherwise. + +#### Lightning Corridor +The **Lightning Corridor** is used by aircraft to transit between the WLM TCU and the M581-M584 restricted areas. +Aircraft will access the corridor through the **[Lightning Gate](#military-gates)** (LG) and transit the corridor before reaching their desired operating area. + +The corridor itself is located entirely within SUA, and aircraft entering the corridor from WLM TCU airspace do not need to be handed off to ARL if the restricted areas are active. + +!!! phraseology + **WAL**: "WGTL45 at LG cleared operating, report [ops normal](../controller-skills/airwork/#ops-normal) time 30." + **WGTL45**: "At LG cleared operating, ops normal time 30, WGTL45." + +Aircraft transiting the Thunder Corridor should be assigned the appropriate altitude to ensure separation with opposite direction traffic while transiting to their desired restricted area. + +| Coded Clearance | Altitude | Notes | +| --------------- | -------- | ----- | +| Outbound | `A100`-`A140`
`A200`-`A240` | Aircraft will remain on local QNH above `A100` | +| Inbound | `A050`-`A090`
`A150`-`A190` | Aircraft will remain on local QNH above `A100` | + +Aircraft returning to base via the corridor will contact WLM TCU prior to leaving their training area. Once the aircraft has been identified by WLM TCU, they will then pass details of their intended return. + +!!! phraseology + **WGTL45**: "Willy Approach, WGTL45." + **WAL**: "WGTL45, Willy Approach, identified." + **WGTL45**: "Willy Approach, WGTL45. `A090` visual, for visual approach with information A." + +##### M581-M584 MOA Subsets +The M581-M584 MOAs are themselves divided into eighteen different subareas that are used to confine different operations within the area. These areas are arranged in a grid pattern and are identified by a grid reference. + +| MOA | Subareas | +| ---- | ------- | +| M581 | A1, B1, and C1 | +| M582 | A2, B2, B3, C2, and C3 | +| M583 | D1-D3, and E1-E3 | +| M584 | F1-F3, and G | + +WLM TCU is not responsible for assigning subareas, or ensuring separation between aircraft operations between areas. + +When an aircraft has declared an intention to operate within a subarea, the WLM TCU may provide a traffic statement to help provide situational awareness to the departing aircraft. + +!!! phraseology + **WAL**: "WGTL46 at LG cleared operating, number 2 in Bravo One and Charlie One, report [ops normal](../controller-skills/airwork/#ops-normal) time 30. + +### Special Use Airspace +#### Salt Ash SUA +The Salt Ash Air Weapons Range is located within the WLM MIL CTR, and is used for air-surface gunnery and bombing practice. It is entirely contained within the R596 [restricted area](../../controller-skills/sua/#restricted-areas). + +
+![The Salt Ash Weapons Range](img/wlm_salt_ash.png){ width="700" } +
The Salt Ash Air Weapons Range
+
+ +The restricted area can be activated in two configurations according to the requirements of the operation. Only VFR aircraft are permitted. + +| Configuration Name | Vertical Limits | Notes | +| ------------------ | ---------------- | ------ | +| R596 High | `SFC` - `A130` | Aircraft will remain on local QNH above `A100` | +| R596 Low | `SFC` - `A050` | | + +When the R596 restricted area is active all airspace within the SUA is managed by **WAL**, and the [ATIS should be updated](../../aerodromes/classc/Williamtown/#sua-activations) to reflect the activation. + +### Stereo Approaches +In times of heavy military traffic, WLM TCU may choose to nominate [stereo approaches](../controller-skills/military/#stereo-approaches) as the preferred approach method. When stereo approaches have been nominated, the ATIS [APCH EXP field must be updated](../../aerodromes/classc/Williamtown/#approach-types) accordingly. + +Aircraft arriving from Gates 1-4 and 6 will join the stereo approach at the gate; other aircraft may start the approach from overhead WLM TAC. + +!!! phraseology + *WGTL45 is returning from M581 via Gate 6, and has already been identified. Runway 30 is in use.* + **WGTL45**: "Willy Approach, WGTL45. `F150` visual, for stereo approach with information A." + **WAL**: "MAPL45, Willy Approach, cleared stereo approach. At 11 TACAN WLM contact Tower, 118.3" + **MAPL45**: "Cleared stereo approach, tower at 11 TACAN WLM, WGTL45" ## Flow ### Local Knowledge @@ -115,10 +248,6 @@ The following calculator will generate a landing time from a feeder fix ETA, or ## Coordination ### ARL(All) - -#### Airspace -Any airspace releases from the default setup must be coordinated and agreed upon with ARL. It is also good practice to remind them of any airspace releases that may be active due to NOTAMs. - #### Departures Voiceless for all aircraft: @@ -143,9 +272,9 @@ Voiceless for all aircraft: All other aircraft coming from ARL CTA will be **Heads-up** Coordinated to WLM TCU. -### ADC +### WLM ADC #### Airspace -WLM ADC owns the airspace within the WLM MIL CTR A (`SFC`-`A050`). This may be amended/released as required between WLM ADC and WLM TCU. +WLM ADC owns the airspace within the WLM MIL CTR A (`SFC`-`A015`). #### Departures [Next](../controller-skills/coordination.md#next) coordination is **not** required from WLM ADC to WLM TCU for aircraft that are: @@ -154,19 +283,23 @@ WLM ADC owns the airspace within the WLM MIL CTR A (`SFC`-`A050`). This may be a - Assigned the standard assignable level; and - Assigned a **Procedural** SID +All other aircraft require a 'Next' call to WLM TCU. + The Standard Assignable level from WLM ADC to WLM TCU is: | Aircraft | Level | -| ------- | ----- | -| All | The lower of `F120` and `RFL` | - -#### 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. +| -------- | ----- | +| All | The lower of `F120` and `RFL` | + +#### ACD to WLM TCU +The controller assuming responsibility of **ACD** shall give [heads-up](../controller-skills/coordination/#airways-clearance) coordination to WAL (or the enroute controller responsible for the WLM TCU) prior to the issue of a clearance to an aircraft intending to operate in an SUA that **has not** been activated. !!! phraseology - **WAL** -> **WLM ADC**: "via WLM, ZULU, Close formation of 5, do you have any restrictions or requirements?" - **WLM ADC** -> **WAL**: "ZULU, no restrictions or requirements, A040" + **WLM ACD** -> **WAL**: "PTHR11 requests clearance to R570 via Thunder corridor.” + **WAL** -> **WLM ACD**: "PTHR11, clearance approved." + +Most military operations will take place in SUA adjoining the [TCU in enroute airspace](#sua-in-enroute-airspace). WLM TCU must coordinate the activation of these SUAs with the relevant enroute controllers **prior** to approving any clearances. ## Charts !!! abstract "Reference" - Additional charts to the AIP may be found in the RAAF TERMA document, available towards the bottom of [RAAF AIP page](https://ais-af.airforce.gov.au/australian-aip){target=new} + In addition to the civilian `ERSA` and `AIP` publications, [the RAAF AIP website](https://ais-af.airforce.gov.au/australian-aip){target=new} contains the necessary charts (available in the TERMA) and description of procedures (in each airports' FIHA). \ No newline at end of file