Aerodrome Flight Information Service (AFIS)
Event Only Positions
The following positions may only be staffed during approved VATNZ events, or when authorised by the Operations Director.
Positions
| Position Name | Shortcode | Callsign | Frequency | Login ID | Usage |
|---|---|---|---|---|---|
| Paraparaumu Flight Service | FPP | Paraparaumu Traffic | 118.300 | NZPP_TWR | Event Only |
| Milford Flight Service | FMF | Milford Traffic | 118.200 | NZMF_TWR | Event Only |
Overview
An Aerodrome Flight Information Service (AFIS) provides pilots with information to assist the safe and efficient conduct of flight operations at non-controlled aerodromes.
ATC vs AFIS
Unlike Air Traffic Control, an AFIS does not issue clearances or provide separation. Pilots remain responsible for the safe operation of their aircraft.
Supervised UNICOM
Think of AFIS as a supervised UNICOM. The AFIS Operator provides information to improve situational awareness, while pilots remain responsible for making operational decisions.
AFIS Responsibilities
An AFIS Operator should provide:
- Preferred runway.
- Surface wind.
- QNH.
- Traffic information.
- Weather information.
- Known hazards affecting operations.
AFIS Limitations
AFIS Operators must not:
- Issue taxi, take-off or landing clearances.
- Sequence aircraft.
- Separate aircraft.
- Issue ATC instructions.
- Amend or issue IFR clearances.
Traffic Information
Pilot Coordination
If pilots are already communicating directly with one another, there is generally no need to repeat traffic information they already know.
IFR Operations
IFR Clearances
An AFIS Operator may relay an IFR clearance issued by the responsible ATS unit.
AFIS Operators must not issue, amend or cancel IFR clearances.
Standard Phraseology
The following examples demonstrate generic AFIS phraseology. Aerodrome-specific reporting points, frequencies and local procedures are published on each aerodrome's individual page.
VFR Operations
Aircraft Operating Within the AFIS Area
Pilot: "[Aerodrome] Flight Service, KAL"
AFIS: "KAL, [Aerodrome] Flight Service"
Pilot: "KAL, [Aircraft Type], on the apron, 2 POB, to operate [area], [altitude]"
AFIS: "KAL, preferred runway SEAL 34, surface wind 340 degrees 10 knots, QNH 1001, traffic is [traffic information]"
Pilot: "Runway 34, QNH 1001, copy traffic and conditions, KAL"
Pilot: "KAL taxiing to Holding Point Alpha"
AFIS: "KAL"
Pilot: "KAL lining up SEAL 34"
AFIS: "KAL, [traffic] short final SEAL 34"
Pilot: "KAL, roger, holding short SEAL 34"
AFIS: "KAL"
Pilot: "KAL lining up SEAL 34 behind the [traffic]"
AFIS: "KAL"
Pilot: "KAL rolling SEAL 34 departing [direction]"
AFIS: "KAL"
Pilot: "KAL operating [area], [altitude]"
Operations Within the AFIS Area
Pilots should remain on the Flight Service frequency whilst operating within the AFIS area or circuit.
AFIS Operators should continue providing traffic information as required. If pilots are already coordinating directly with one another, there is generally no need to repeat information they already have.
VFR Arrival
Inbound Aircraft
Pilot: "[Aerodrome] Flight Service, TWN"
AFIS: "TWN, [Aerodrome] Flight Service"
Pilot: "TWN, [Aircraft Type], [position], [altitude], two POB, joining, full stop"
AFIS: "TWN, preferred runway SEAL 34, surface wind 340 degrees 10 knots, QNH 1001, traffic is [traffic information]"
Pilot: "Runway 34, QNH 1001, copy traffic and conditions, TWN"
Pilot: "TWN joining left downwind SEAL 34"
AFIS: "TWN, [relevant circuit traffic]"
Pilot: "Copy traffic"
Pilot: "TWN left downwind SEAL 34, full stop"
AFIS: "TWN"
Pilot: "TWN rolling through SEAL 34 to vacate"
AFIS: "TWN"
IFR Departure
Relaying an IFR Clearance
Pilot: "[Aerodrome] Flight Service, KVY"
AFIS: "KVY, [Aerodrome] Flight Service"
Pilot: "KVY at the apron, six POB, request IFR clearance to [Destination], 5000 feet"
AFIS: "KVY, preferred runway SEAL 34, surface wind 320 degrees 10 knots, QNH 1001, clearance on request"
See Coordination with the Overlying ATS Unit below.
AFIS: "KVY, clearance available"
Pilot: "KVY, ready to copy"
AFIS: "[Approach] clears KVY via the [] departure, [] transition, [altutide] clearance not yet valid, remain outside of controlled airspace report ready for departure"
Pilot: "Cleared... , KVY"
AFIS: "KVY, readback correct, clearance not yet valid"
Pilot: "KVY, Ready for departure"
(Once advised by the controlling ATS unit.)
AFIS: "KVY, clearance now valid, enter controlled airspace via the GUGAK6 departure "
Pilot: "KVY, enter controlled airspace via the GUGAK6 departure, lining up SEAL 34"
AFIS: "KVY, passing 2000 feet contact [Approach] [frequency], no reported IFR traffic"
Pilot: "Passing 2000 feet contact [Approach], copy traffic, KVY, rolling SEAL 34 departing [direction] climbing to 5000 feet"
AFIS: "KVY"
IFR Arrival
Arrival from Controlled Airspace
TMA: "KAL, cleared [arrival] arrival for the RNP approach Runway 34 at [Aerodrome], when ready descend 3000 feet"
Pilot: "Cleared [arrival] arrival, RNP Runway 34, when ready descend 3000 feet, KAL"
(When established on the approach.)
Pilot: "KAL established RNP Runway 34"
TMA: "KAL, cleared to leave controlled airspace on the RNP approach Runway 34, contact [Aerodrome] Flight Service on [frequency]"
Pilot: "Cleared to vacate controlled airspace on the RNP approach Runway 34, contact [Aerodrome] Flight Service on [frequency], KAL"
Pilot: "[Aerodrome] Flight Service, KAL, [distance] [direction] of the field descending through 3500 feet on the RNP approach to land"
AFIS: "KAL, [Aerodrome] Flight Service, surface wind 290 degrees 12 knots, QNH 1007, no significant traffic"
Pilot: "Copy traffic and conditions, QNH 1007, KAL"
Approach Completion
From this point, pilots should continue making appropriate position reports until clear of the runway.
The AFIS Operator should provide updated traffic information whenever required.
Coordination with the Overlying ATS Unit
IFR departure clearances shall be coordinated with the appropriate overlying ATS unit before being relayed to the pilot.
The pilot must not be advised that the clearance is valid until the overlying ATS unit has confirmed that the clearance is active.
Note
See the individual aerodrome SOPs for examples of local coordination procedures.
Local Procedures
Aerodrome-specific procedures, reporting points and phraseology are published separately: