Skip to content

3. Perth (YPPH)

Runway Modes

Priority Mode Operation
1 24A21D Simultaneous Independent Crossing Runway Operations
2 03A06D Land and Hold Short Operations

Single Runway Operations shall be avoided at all costs.

24A21D

Simultaneous Independent Crossing Runway Operations will be in use, allowing aircraft to depart from Runway 21 without conflicting with Runway 24 arrivals.

Runway 21 TORA from Intersection P is 2000m.

Expect some arrivals to be landing on Runway 21 due to operational requirements.

03A06D

Land and Hold Short Operations (LAHSO) will be in use, allowing aircraft to land on Runway 03 without conflicting with Runway 06 departures.

Runway 03 LDA to Runway 06/24 Intersection is 2355m.

Example

PH ADC: "GTI1471, 737 departing on Crossing Runway. Hold Short Runway 06. Cleared to land Runway 03"
GTI1471: "Cleared to land Runway 03, GTI1471"
PH ADC: "QFA365, 747 landing on Crossing Runway will Hold Short. Runway 06, Cleared for takeoff"
QFA365: "Cleared for takeoff Runway 06, QFA365"

Aircraft that are unable to Land and Hold Short of Runway 06 will have XX entered in their scratchpad by preceding controllers.

Airways Clearance Delivery (ACD)

Flight Plan Compliance

Ensure all flight plans are checked for compliance with the approved WF Route:

DCT PH Y15 ESDEG Q587 IGLUT T58 SAPDA A585 IPKON IPKO2G

WorldFlight Teams

WorldFlight Teams shall have STS/STATE added to their remarks, and WF TEAM added to their Global Ops Field, to ensure they receive priority.

Strip Setup

By default, vatSys strips will be set to show in Alphabetical Order.
This must be changed to be ordered by Time, as shown below.

Strips Menu

Strips Menu

Change to Time

Change to Time

03A06D

All Medium and Light aircraft are assumed to be able to accept Runway 06 for Departure.

Heavy and Super aircraft must be queried if they are able to accept Runway 06 for Departure.

Note

Requests for Runway 03 cannot be facilitated. The aircraft must operationally require longer than 2163m TORA to receive it.

Aircraft that operationally require Runway 03 shall be assigned it.

SID Selection

Departures from Runway 06 will be assigned the PH7 SID.
Departures from Runway 03 and 21 will be assigned the standard AVNEX5 SID.

PDCs

PDCs will be in use by default, to avoid frequency congestion. ACD shall send a PDC to each aircraft as they connect. Upon successful readback of the PDC, ACD shall direct the pilot to contact SMC when ready for pushback or taxi.

Surface Movement Control (SMC)

Pushback Delays

SMC East and West will be responsible for delaying aircraft's pushback requests, in order to avoid overloading the taxiways.

If there are more than 5 aircraft in the queue at the Holding Point for any runway, do not approve any more pushback requests.

OzStrips

All aerodrome controllers must be familiar with the VATPAC recommended workflow for OzStrips.

Ensure the Queue function is used to actively to keep track of the order of requests.

Runway 21 Departures

By default, all aircraft will be assigned Intersection P for departure. Verify with Heavy and Super aircraft when they request taxi if they can accept Intersection P.

Note

Requests for the full length runway cannot be facilitated. The aircraft must operationally require longer than 2000m TORA to receive it.

Aircraft from the Western Apron shall be taxied via D and N.

Aircraft that cannot accept Intersection P for departure will be assigned a full length departure.

Runway 06 Departures

Ensure that all aircraft queue for Runway 06 to the South East, via A and V.

Runway 06 Queue Paths

Runway 06 Queue Paths

This will avoid blocking up the Western Apron, and ensure aircraft have room to pushback.

Runway 03 Arrivals

Aircraft for the Western Apron will be instructed to vacate right. These aircraft shall be taxied via C, W and B to remain clear of aircraft taxiing for departure.

Tower Control (ADC)

Runway 21 Full Length Departures

Full Length Departures have equal priority to aircraft that are compliant with Simultaneous Independent Crossing Runway Operations. However, Full Length departures may incur additional delays while being separated from Runway 24 Arrivals.

Tip

Ensure the OzStrips queue bay is used actively to keep track of the queue.

Runway 06 Departures

Departures from Runway 06 will be assigned the PH7 SID, with an Assigned Heading of Runway Heading.

Runway 03 Arrivals

Instruct all Runway 03 Arrivals to vacate right, even if they are for the Western Apron.

Departure Spacing

Ensure that a minimum of 90 second spacing is applied between subsequent departures from the same runway.

Wake Turbulence Separation

Due to the tight sequence, there are times that Wake Turbulence Separation cannot practically be applied.

When a following aircraft is of a lighter Wake Turbulence Category than the preceding aircraft, a traffic statement and wake turbulence caution shall be issued.

Example

PH ADC: "EVY30, 777 has just departed from the crossing runway. Caution Wake Turbulence. Runway 24, Cleared to Land"
EVY30: "Cleared to Land Runway 24, EVY30"

ATIS

The ATIS OPR INFO shall include:
EXP CLR VIA PDC

During 24A21D, the ATIS OPR INFO shall include:
SIMUL INDEP CROSSING RWY OPS IN PROG

During 03A06D, the ATIS OPR INFO shall include:
LAHSO IN PROG. RWY 03 LANDING DISTANCE AVBL 2355 METRES

Coordination

PH TCU

Auto Release

Standard as per PH TCU Local Instructions, with the exception of auto-release being available for 06 Departures assigned Runway Heading during the the 03A06D Runway Mode