Skip to content

Commit e5145f1

Browse files
m-9cm-9c
authored
PH TCU/HYD Coordination Change (vatpac-technology#652)
* Perth coordination change * update wording
1 parent fb94972 commit e5145f1

3 files changed

Lines changed: 33 additions & 30 deletions

File tree

‎docs/enroute/Melbourne Centre/HYD.md‎

Lines changed: 29 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -329,6 +329,17 @@ Refer to [Perth TCU Airspace Division](../../../terminal/perth/#airspace-divisio
329329

330330
!!! note
331331
A significant portion of the TMA airspace south of the PH VOR (roughly 20 DME onwards) is classified Class E with a lower limit of `F125`. Aircraft arriving from this direction from `F130` and above shall be instructed to leave and re-enter controlled airspace on descent to the standard assignable level (or other appropriate altitude).
332+
333+
#### Departures
334+
Voiceless for all aircraft:
335+
336+
- Tracking via a Procedural SID procedure<sup>‡</sup>; and
337+
- Assigned the lower of `F180` or the `RFL`
338+
339+
!!! note
340+
<sup>‡</sup> In contrast to many other TCUs, aircraft are *required* to be tracking via the **SID procedure**. Aircraft simply tracking via any of the terminus waypoints (including aircraft given track shortening) **is not** sufficient to meet the criteria for voiceless coordination.
341+
342+
All other aircraft going to PIY CTA will be **Heads-up** Coordinated by PH TCU.
332343

333344
#### Arrivals/Overfliers
334345
Voiceless for all aircraft:
@@ -339,14 +350,27 @@ Voiceless for all aircraft:
339350

340351
All other aircraft coming from PIY CTA must be **Heads-up** Coordinated to PH TCU prior to **20nm** from the boundary.
341352

353+
### PE TCU
354+
#### Airspace
355+
PEA is responsible for the restricted airspace within R155A and R155B. This airspace is reclassified to **Class C** when PEA is online. Additional airspace may be released by NOTAM, or coordinated between PEA, PH TCU, and LEA/PIY to facilitate military operations.
356+
357+
!!! phraseology
358+
<span class="hotline">**PEA** -> **PH TCU**</span>: "Request release of M166, SFC to F160, for Military Operations. My onwards with LEA"
359+
<span class="hotline">**PH TCU** -> **PEA**</span>: "M166, SFC to F160, released to you. Your onwards with LEA"
360+
361+
<span class="hotline">**PEA** -> **LEA**</span>: "Request release of M166, SFC to F160, for Military Operations. My onwards with PH TCU"
362+
<span class="hotline">**LEA** -> **PEA**</span>: "M166, SFC to F160, released to you. Your onwards with PH TCU"
363+
342364
#### Departures
343-
Voiceless for all aircraft:
344-
345-
- Tracking via a Procedural SID terminus; and
346-
- Assigned the lower of `F180` or the `RFL`
365+
All aircraft from PE TCU to HYD require [Heads-up](../../../controller-skills/coordination/#heads-up) coordination prior to the boundary, however, as soon as practical (when is the aircraft becomes airborne) is preferred.
347366

348-
All other aircraft going to PIY CTA will be **Heads-up** Coordinated by PH TCU.
367+
#### Arrivals/Overfliers
368+
All aircraft transiting from HYD to **PE TCU** must be [Heads-up](../../../controller-skills/coordination/#heads-up) coordinated prior to **20nm** from the boundary. There are no standard assignable levels; HYD and **PEA** controller must agree on a suitable level during coordination.
349369

370+
!!! phraseology
371+
<span class="hotline">**LEA** -> **PEA**</span>: "via AVNEX, EGLE9, will be assigned A090"
372+
<span class="hotline">**PEA** -> **LEA**</span>: "EGLE9, A090"
373+
350374
### Enroute
351375
As per [Standard coordination procedures](../../../controller-skills/coordination/#enr-enr), Voiceless, no changes to route or CFL within **50nm** to boundary.
352376

@@ -366,24 +390,3 @@ Aircraft must have their identification terminated and be instructed to make a p
366390

367391
!!! phraseology
368392
**LEA**: "QFA121, identification terminated, report position to Brisbane Radio, 129.25"
369-
370-
### PE TCU
371-
#### Airspace
372-
PEA is responsible for the restricted airspace within R155A and R155B. This airspace is reclassified to **Class C** when PEA is online. Additional airspace may be released by NOTAM, or coordinated between PEA, PH TCU, and LEA/PIY to facilitate military operations.
373-
374-
!!! phraseology
375-
<span class="hotline">**PEA** -> **PH TCU**</span>: "Request release of M166, SFC to F160, for Military Operations. My onwards with LEA"
376-
<span class="hotline">**PH TCU** -> **PEA**</span>: "M166, SFC to F160, released to you. Your onwards with LEA"
377-
378-
<span class="hotline">**PEA** -> **LEA**</span>: "Request release of M166, SFC to F160, for Military Operations. My onwards with PH TCU"
379-
<span class="hotline">**LEA** -> **PEA**</span>: "M166, SFC to F160, released to you. Your onwards with PH TCU"
380-
381-
#### Departures
382-
All aircraft from PE TCU to HYD require [Heads-up](../../../controller-skills/coordination/#heads-up) coordination prior to the boundary, however, as soon as practical (when is the aircraft becomes airborne) is preferred.
383-
384-
#### Arrivals/Overfliers
385-
All aircraft transiting from HYD to **PE TCU** must be [Heads-up](../../../controller-skills/coordination/#heads-up) coordinated prior to **20nm** from the boundary. There are no standard assignable levels; HYD and **PEA** controller must agree on a suitable level during coordination.
386-
387-
!!! phraseology
388-
<span class="hotline">**LEA** -> **PEA**</span>: "via AVNEX, EGLE9, will be assigned A090"
389-
<span class="hotline">**PEA** -> **LEA**</span>: "EGLE9, A090"

‎docs/pacific/Fiji/Nadi/TCU.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Upon receiving a '[Next](../../../../controller-skills/coordination/#boundary)'
7272
<span class="hotline">**NFFN ADC** -> **NFFNA**</span>: "FJI211"
7373

7474
#### Sequencing
75-
Consecutive arrivals sequenced **5 minutes or less** apart will not provide adequate spacing for a departure on the reciprocal runway. While aircraft in the air take priority over aircraft on the ground, where possible NFFNA should consider minor adjustments to extended delays for departures.
75+
Consecutive arrivals sequenced **5 minutes or less** apart will not provide adequate spacing for a departure on the reciprocal runway. While aircraft in the air take priority over aircraft on the ground, where possible NFFNA should consider minor adjustments to avoid extended delays for departures.
7676
<!---## Tower Offline Procedure
7777
## Runway Modes
7878
## Helicopter Operations--->

‎docs/terminal/perth.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -205,11 +205,11 @@ The following calculator will generate a landing time from a feeder fix ETA, or
205205
#### Departures
206206
Voiceless for all aircraft:
207207

208-
- Tracking via a Procedural SID terminus; and
208+
- Tracking via a Procedural SID procedure<sup>‡</sup>; and
209209
- Assigned the lower of `F180` or the `RFL`
210-
210+
211211
!!! note
212-
Aircraft are *not required* to be tracking via the **SID procedure**, simply tracking via any of the terminus waypoints (Regardless of *departure airport* or *assigned SID*) is sufficient to meet the criteria for **voiceless coordination**
212+
<sup>‡</sup> In contrast to many other TCUs, aircraft are *required* to be tracking via the **SID procedure**. Aircraft simply tracking via any of the terminus waypoints (including aircraft given track shortening) **is not** sufficient to meet the criteria for voiceless coordination.
213213

214214
All other aircraft going to HYD(PIY) CTA must be **Heads-up** Coordinated by PH TCU prior to the boundary.
215215

0 commit comments

Comments
 (0)