Pingelly (PIY)
Positions
Name | Callsign | Frequency | Login ID |
---|---|---|---|
Pingelly | Melbourne Centre | 133.900 | ML-PIY_CTR |
Cross† | Melbourne Centre | 135.800 | ML-CRS_CTR |
Hyden† | Melbourne Centre | 118.200 | ML-HYD_CTR |
Jarrah† | Melbourne Centre | 120.300 | ML-JAR_CTR |
Leeman† | Melbourne Centre | 122.400 | ML-LEA_CTR |
Grove† | Melbourne Centre | 133.800 | ML-GVE_CTR |
Geraldton† | Melbourne Centre | 134.200 | ML-GEL_CTR |
† Non-standard positions may only be used in accordance with VATPAC Air Traffic Services Policy
CPDLC
The Primary Communication Method for PIY is Voice.
CPDLC may be used in lieu when applicable.
The CPDLC Station Code is YPIY
.
Tip
Even though PIY's Primary Communication Method is Voice, CPDLC may be used for Overfliers.
Airspace
Sector Responsibilities
Pingelly (PIY)
PIY will provide final sequencing actions to ensure aircraft comply with their FF times prior to entering the Perth TCU. PIY is also responsible for issuing STAR Clearances for aircraft bound for YPJT, and Non-jets bound for YPPH and YPEA. See Perth Runway Modes for runway assignment.
For aircraft overflying the PH TCU place O/FLY
in the LABEL DATA field.
Leeman (LEA)
LEA is responsible for assigning and issuing STAR clearance to aircraft inbound to Perth via IPMOR
. See Perth Runway Modes for runway assignment.
Note
Controllers should be aware that VHF coverage near the LEA/IND border may be limited. Controllers should strive to issue HF frequencies and transfer of communications instruction prior to 160 NM PH DME.
Grove (GVE)
GVE is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via JULIM
and SAPKO
. See Perth Runway Modes for runway assignment.
Hyden (HYD)
HYD is responsible for assigning and issuing STAR clearance to Jet aircraft inbound to Perth via KABLI
/MALUP
, DAYLR
and LAVEX
. See Perth Runway Modes for runway assignment.
Cross (CRS) / Geraldton (GEL)
Just keeping them separated!
Jarrah (JAR)
JAR is responsible for assigning and issuing arrival clearance to aircraft inbound to Perth via SOLUS
. See Perth Runway Modes for runway assignment.
Note
Controllers should be aware there may be limited ADS-B coverage around Albany (YABA). Expect some areas of Class E airspace to be outside surveillance coverage. Procedural Standards may need to be used in these cases.
Sequencing in to YPPH
Aircraft assigned the same runway inbound via JULIM and SAPKO, must be considered to be on the same STAR for sequencing purposes. That is, they must be at least 2 minutes apart at their respective Feeder fixes.
YPPH Runway Modes
Southwest Plan
With the Southwest Plan active, arrivals shall be processed to either runway 21 or 24 based on their feeder fix, as per the table below:
Feeder Fix | Assigned Runway |
---|---|
JULIM | 21 |
SAPKO | 21 |
IPMOR | 21 |
KABLI | 24 (or 21 if operationally required) |
LAVEX | 24 |
SOLUS | 24 |
Northeast Plan
With the Northeast Plan active (runways 03 and 06 in use), all arrivals shall be processed to runway 03.
YPJT Arrivals
To facilitate smooth movement of traffic in the Perth TCU, IFR Arrivals to YPJT shall be assigned a STAR in accordance with the YPPH Runway Mode:
Feeder Fix | 03/06 | 21/24 |
---|---|---|
WOORA | Golf | WOORA PH JT (No STAR) |
LAVEX | Golf | Romeo |
KABLI (Jet) | Golf | Romeo |
MALUP (Non-Jet) | Whiskey | Romeo (via KABLI) |
Note
Assigning a STAR to YPJT Arrivals still does not meet voiceless coordination requirements to PH TCU. All YPJT Arrivals must be heads-up coordinated, including those assigned a STAR.
STAR Clearance Expectation
Handoff
Aircraft being transferred to the following sectors shall be told to Expect STAR Clearance on handoff:
Transferring Sector | Receiving Sector | ADES | Notes |
---|---|---|---|
GVE, CRS, HYD | PIY | YPPH, YPEA | Non-jets only |
GVE, CRS, HYD | PIY | YPJT | |
GEL | LEA | YPPH |
First Contact
Aircraft being transferred from the following sectors shall be given STAR Clearance on first contact:
Transferring Sector | Receiving Sector | ADES | Notes |
---|---|---|---|
OLW(MEK, MTK, MZI) | GVE, HYD | YPPH, YPEA | Jets only |
ASP(ESP) | HYD | YPPH, YPEA | Jets only |
GVE, CRS, HYD | PIY | YPPH, YPEA | Non-jets only |
GVE, CRS, HYD | PIY | YPJT | |
GEL, IND | LEA | YPPH | |
IND | GEL, LEA, JAR | YPPH |
Coordination
PH TCU
Airspace
The PH TCU is responsible for the airspace within 36 DME of the PH VOR, SFC
to F245
.
Refer to Perth TCU Airspace Division for information on airspace divisions when PHD is online.
Note
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).
Arrivals/Overfliers
Voiceless for all aircraft:
- With ADES YPPH; and
- Assigned a STAR; and
- Assigned
A090
All other aircraft coming from PIY CTA must be Heads-up Coordinated to PH TCU prior to 20nm from the boundary.
Departures
Voiceless for all aircraft:
- Tracking via a Procedural SID terminus; and
- Assigned the lower of
F180
or theRFL
All other aircraft going to PIY CTA will be Heads-up Coordinated by PH TCU.
Enroute
As per Standard coordination procedures, Voiceless, no changes to route or CFL within 50nm to boundary.
PIY Internal
Changes to CFL are permitted up to the boundary from GVE, CRS and HYD to PIY.
All else is Voiceless, no changes to route or CFL within 20nm to boundary.
That being said, it is advised that PIY(All) gives Heads-up Coordination prior to 20nm in the following scenarios:
- JAR to PIY for all aircraft
- LEA to PIY for all aircraft
IND (Oceanic)
As per Standard coordination procedures, Voiceless, no changes to route or CFL within 15 mins to boundary.
Aircraft must have their identification terminated and be instructed to make a position report on first contact with the next (procedural) sector.
Example
PIY: "QFA121, identification terminated, report position to Brisbane Radio, 129.25"