Parafield (YPPF)
Positions
| Name | Callsign | Frequency | Login ID |
|---|---|---|---|
| Parafield ADC East | Parafield Tower | 118.700 | PF_TWR |
| Parafield ADC West | Parafield Tower | 124.600 | PF-W_TWR |
| Parafield SMC | Parafield Ground | 119.900 | PF_GND |
| Parafield ATIS | 120.900 | YPPF_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).
Dual ADC Operations
When Parafield ADC West is online, responsibility for the Runway, Circuit, and Airspace is divided between the two ADC controllers.
ADC East takes responsibility for the South/East Runway, Circuit and Airspace (Runway 08R/26L and 03R/21L).
ADC West takes responsibility for the North/West Runway, Circuit and Airspace (Runway 08L/26R and 03L/21R).
ADC West is not permitted online when Single Runway Operations are in use.
Refer to the ATIS section for information on ATIS formatting when ADC West is online.
Airspace
PF ADC is responsible for the Class D airspace in the PF CTR SFC to A015.
Dual ADC Operations
Airspace Ownership when ADC West is online, is split down the middle of the two active extended centrelines.
Circuits
Circuits to be flown at A010
| Runway | Day | Night |
|---|---|---|
| 03L | Left | Left |
| 03R | Right | - |
| 21L | Left | - |
| 21R | Right | Right |
| 08L | Left | - |
| 08R | Right | - |
| 26L | Left | - |
| 26R | Right | - |
VFR Operations
Arrivals
| VFR Approach Point | RWYs 03 | RWYs 21 | RWYs 08 | RWYs 26 |
|---|---|---|---|---|
| OHB | Join base (or downwind) RWY 03L | Join base (or downwind) RWY 21R | Join final RWY 08L | Join downwind RWY 26R |
| DMW | Join downwind RWY 03R | Join 3NM final RWY 21L | Join downwind RWY 08L | Join final RWY 26R |
Important
Visually monitor all aircraft to ensure tracking South of Bolivar Strobe (located at the Southern tip of the EDN CTR), to ensure aircraft remain outside of EDN CTR.
IFR Operations
Departures
IFR Departures from YPPF shall be assigned PF RADAR SID when Runway 03/21 is in use.
ATIS
Runway Nomination
| Priority | Runway Mode |
|---|---|
| =1 | 03L & 03R |
| =1 | 21L & 21R |
| =2 | 08L & 08R |
| =2 | 26L & 26R |
| 3 | Any Single Runway Operations |
When 2 ADC controllers are online, the ATIS shall be formatted: RWY 03R/08R/21L/26L FOR ARRS AND DEPS EAST, FREQ 118.7. RWY 03L/08L/21R/26R FOR ARRS AND DEPS WEST, FREQ 124.6
By Night, Only Runway 03L/21R may be used.
Approach Expectation
The APCH field should include EXP INST APCH when:
- the ceiling is at or below A020; or
- visibility is less than 5000m
Coordination
Departures
Next coordination is required from PF ADC to AD TCU for all aircraft entering AD TCU CTA.
The Standard Assignable level from PF ADC to AD TCU is:
| Aircraft | Level |
|---|---|
| All | The lower of A030 and RFL |
Arrivals
AD TCU will heads-up coordinate arrivals/overfliers from Class C to PF ADC.
IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to PF ADC, unless PF ADC nominates a restriction.
VFR aircraft require a level readback.
Phraseology
AAW -> PF ADC: "via PAL, YTS"
PF ADC -> AAW: "YTS, A010"
Tip
Remember that IFR aircraft are only separated from other IFR or SVFR aircraft in class D. You should generally be able to issue a clearance for an approach and use other separation methods (visual separation, holding a departure on the ground) if separation is required with these aircraft.
Taxi Routes
Taxiway Bravo crosses through the Undershoots of Runway 26L and 26R. As per YPPF Aerodrome Chart, a Clearance is Required to taxi through these areas, using the same phraseology as normal Runway Crossings.
Phraseology
PF SMC: "USP, On Bravo cross the undershoots of Runway 26L and 26R. Taxi to Holding Point B1, Runway 03L." USP: "On Bravo cross undershoots of Runway 26L & 26R. Taxi to Holding Point B1 Runway 03L, USP."
ADC West Online
When ADC West is online, AD TCU may not be familiar with which controller owns what airspace. Best practice is to receive the coordination no matter what, and if it was meant for the other ADC controller, relay the coordination to them internally.
PF ADC Internal
PF ADC must heads-up coordinate all aircraft transiting from one ADC controller to the other.
Phraseology
PF ADC W -> PF ADC E: "via OHB, YNM for an overhead join"
PF ADC E -> PF ADC W: "YNM, A015"