Perth (YPPH)
Positions
| Name | Callsign | Frequency | Login ID |
|---|---|---|---|
| Perth ADC | Perth Tower | 127.400 | PH_TWR |
| Perth SMC West | Perth Ground | 121.700 | PH_GND |
| Perth SMC East | Perth Ground | 122.200 | PH-E_GND |
| Perth ACD | Perth Delivery | 118.550 | PH_DEL |
| Perth ATIS | 123.800 | YPPH_ATIS |
Non-Standard Positions
Non-standard positions may only be used in accordance with VATPAC Air Traffic Services Policy.
Approval must be sought from the bolded parent position prior to opening a Non-Standard Position, unless NOTAMs indicate otherwise (eg, for events).
Airspace
PH ADC is not responsible for any airspace by default.
Manoeuvring Area
Manuevering Area Responsibility
The area of responsibility between SMC West and East is divided by Runway 03/21.
Transferring Between SMCs
When both SMC positions are online and an aircraft is to be passed from one to the other (e.g. an aircraft vacates runway 24 for the eastern terminal), they should be instructed to hold short of runway 03/21 and to contact the next SMC frequency.
The aircraft's strip shall be placed in the receiving controller's bay prior to frequency transfer. The receiving controller is responsible for coordinating the runway crossing with ADC.
Phraseology
SMC West: "RXA2112, taxi Alpha, Alpha Six, hold short runway 21, contact ground 122.2"
RXA2112: "Taxi Alpha, Alpha Six, hold short runway 21, contact ground 122.2, RXA2112"
SMC East -> ADC: "On A6, RXA2112 to cross runway 21"
ADC -> SMC East: "RXA2112 cross runway 21"
RXA2112: "Perth Ground, RXA2112, holding short runway 21"
SMC East: "RXA2112, cross runway 21, taxi to bay 206"
RXA2112: "Cross runway 21, taxi to bay 206, RXA2112"
The video below demonstrates the SMC transfer process at Sydney. The same principles apply at Perth.
Separation
Reduced Runway Separation
When conditions permit, the 2400m separation standard for landing aircraft may be applied to aircraft arriving Runway 03/21
Workload Management
Pushback Requests on ACD
During busy periods, SMC and ACD may coordinate to implement the Pushback Requests on ACD procedure to balance the workload across ACD and SMC frequencies.
When implementing the procedure the ATIS OPR INFO field must be updated to inform pilots the correct frequency on which to request pushback.
Local Procedures
Scenic Flights
When traffic permits, VFR scenic flights over Perth are cleared via VICTOR 65 route (CTE-PCTY-HKE). Coordination with PH TCU is required prior to issuing this clearance, see ACD to PH TCU
Helicopter Operations
There are no helipad facilities at YPPH. Helicopters should be issued an airways clearance in accordance with the fixed-wing operation applicable to their flight rules (i.e. SID for IFR helicopters, VFR departure via appropriate VFR route if necessary for VFR helicopters). Helicopters should be cleared to takeoff/land from runways or taxiways (following appropriate coordination), as deemed appropriate by ADC. The point of takeoff/landing must be specified by ADC.
Phraseology
PH ADC: "YOE, taxiway Romeo, cleared to land"
PH ADC: "HWD, runway 21, cleared for takeoff"
Runway Modes
Preferred Runway Modes
If winds are too great, single runway operations may be necessary (eg, Runway 21 for Arrivals and Departures). However, pending wind limitations (Crosswind <20kts, Tailwind <5kts), the following runway modes are to be used:
| Mode | Arrivals | Departures |
|---|---|---|
| Southwest Plan (24A/21AD) | 21 & 24 | 21 |
| Northeast Plan (03AD/06D) | 03 | 03 (via AVNEX, OTLED, OLMAM, SOLUS, and OPEGA), 06 (all other deps) |
Circuit Training
Circuit training traffic shall be issued SSR code and clearance to operate within circuit area not above A015. Circuit training is typically conducted on Runway 03/21.
All circuits are to be conducted to the east of Runway 03/21 (right-hand circuit Runway 03).
SID Selection
Jet Aircraft planned via AMANA, AVNEX, HECTO, MEMUP, MUBID, YNRV, OLMAM, SOLUS, or OPEGA, shall be assigned the Procedural SID that terminates at the appropriate waypoint.
Non-jet Aircraft planned via LENVU, PUMRY, OLMAM, SOLUS, OPEGA, OTLED, or REPOK, shall be assigned the Procedural SID that terminates at the appropriate waypoint.
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.
Phraseology
PH ACD: "RXA2357, cleared to YESP via amended LENVU thence direct ESP, LENVU1 departure, climb via SID A050, squawk 7172, departure frequency 123.6"
Off Mode Departures
Definition
Off Mode: Aircraft departing from a runway not prescribed as active for departures on the ATIS. For example, a heavy aircraft planned via HECTO that operationally requires Runway 03 for departure during the Northeast Plan Mode.
For aircraft departing Runway 03 Off Mode via AMANA, HECTO, MEMUP, or YNRV, the Radar SID must be assigned.
Note
Assigning the Radar SID to an off-mode departure does not meet the requirements for auto release. These aircraft must be 'Next' coordinated with PH TCU.
Runway 03 Departures
When the R155A and R115B restricted areas overhead Pearce are not active, aircraft departing departing Runway 03 to the north may be assigned either the Radar SID or the EKEPO SID. This offers aircraft a shorter, more direct route than the OTLED and AVNEX SIDs.
ATIS
Approach Types
| Runway Mode | Condition | ATIS APCH field |
|---|---|---|
| Southwest Plan | All | EXP ILS APCH |
| Northeast Plan | Cloud base at or below A032, orBy night |
EXP ILS APCH |
Runway Mode Formatting
| Mode | ATIS Runway information |
|---|---|
| Southwest Plan | 21 AND RWY 24 FOR ARR. RWY 21 FOR DEP. |
| Northeast Plan | 03 FOR ARR. RWY 03 FOR DEP VIA OTLED, AVNEX, OLMAM, SOLUS AND OPEGA. RWY 06 FOR ALL OTHER DEP. |
Operational Info
ACD Pushback Requests
When implementing the Pushback Requests on ACD procedure, the OPR INFO shall include:
ALL DEPARTURES MUST REQUEST PUSH BACK ON 118.55
Coordination
Auto Release
Next coordination is not required for aircraft that are:
- Departing from a runway nominated on the ATIS; and
- Assigned the standard assignable level; and
- Assigned a Procedural SID
All other aircraft require a 'Next' call to PH TCU.
The Standard Assignable level from PH ADC to PH TCU is:
| Aircraft | Level |
|---|---|
| All | The lower of A050 and RFL |
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 most appropriate Enroute controller or Advisory frequency shall be issued.
| Runway | Via | Departure Frequency |
|---|---|---|
| All | All | 118.7 (PHD) |
ACD to TCU
The controller assuming responsibility of ACD shall give heads-up coordination to the relevant PH TCU controller prior to the issue of the following clearances:
- VFR departures into PH TCU CTA
- Aircraft using a runway not on the ATIS