¶ Aerodrome Flight Information Service
Aerodrome Flight Information Service (AFIS) is the term used to describe the provision of information useful for the safe and efficient conduct of aerodrome traffic at airports where an Air Traffic Control Service is not provided.
The operator providing the AFIS is the Aerodrome Flight Information Unit (AFIU)
The AFIU is not an air traffic controller, the AFIU shall only provide information and warnings to pilots, who are responsible for the safe conduct of their airplane and the conformity to the rules of the air.
¶ AFIU Procedures
¶ Objectives
The AFIU shall issue information to aircraft located within its area of responsibility (usually the class G ATZ) in order to achieve a safe, orderly and expeditious flow of traffic.
One of the main goals of the AFIU is to aid pilots in preventing collisions between:
- Aircraft flying within the designated AoR, including the aerodrome traffic circuit;
- Aircraft operating on the maneuvering area
- Aircraft landing and taking off
The AFIU shall maintain a constant watch by visual observation and an ATS surveillance system (when available), on all flight operation on and in the vicinity of the aerodrome of responsibility.
¶ Preferred runway
The AFIU is responsible for the determination of the most suitable runway to use for takeoff and landing at the aerodrome.
The preferred runway shall be determined taking into consideration the following factors:
- Wind
- Aerodrome traffic circuits
- Runway length
- Available approach and landing aids
- Instrument approach procedures in progress
- Local procedures
The pilot in command can choose a different runway than the one suggested by the AFIU, in the case it is the AFIU’s responsibility to provide detailed information about other traffic to ensure safe spacing is maintained.
¶ Priority
An aircraft landing or in the final stages of the approach shall normally have priority over an aircraft intending to depart from the same or an intersecting runway.
¶ Departures
Prior to taxi or departure, aircraft shall receive the following information:
- Preferred runway
- Latest weather
- Clearance for IFR traffic (relayed from ATC)
- Coordination with appropriate ATC for IFR pick up (when applicable)
- Start up information (for VFR)
- Start up clearance (for IFR)
- Taxi instructions and traffic information
- Active NOTAMs or other important information (if applicable)
The AFIU shall provide relevant information on local traffic and aerodrome conditions to assist the flight crew in deciding when to take-off. Such information shall be updated at AFIU discretion or when requested by the pilot. Pilots shall inform the AFIU of their intentions, e.g. ‘holding’, ‘lining up’, ‘taking off’.
Pilots must not take off if there are other aircraft on the runway.
¶ Procedures for departing VFR aircraft:
- Aircraft is ready for startup:
Trento Info buongiorno, I-ABCD, C172, stand 11, ready for startup, VFR to LIDB
I-ABCD, Trento Info buongiorno, start up at your discretion
- After startup aircraft will normaly request departure information:
I-ABCD, request departure information
I-ABCD, Trento Info, preferred runway 36, wind calm, QNH 1013, report ready to taxi.
If METAR is available, the AFIU shall provide it.
- Aircraft is ready for taxi:
I-ABCD, ready to taxi
I-ABCD, Trento Info, report at holding point A, runway 36 (traffic information if applicable)
- Aircraft is ready for backtrack and departure:
I-ABCD, holding point A, ready for backtrack 36
I-ABCD, Trento Info, (traffic information / no reported traffic), backtrack on discretion, report ready for departure
I-ABCD, ready for departure runway 36
I-ABCD, Trento Info, runway 36 no reported traffic, wind calm.
or
I-ABCD, Trento Info, runway 36 free for departure, wind calm
- In case the runway is blocked:
I-ABCD, Trento Info, runway 36 occupied by [traffic information]
- Once the aircraft is airborne:
I-ABCD, Trento Info, airborne at 1305, report Calliano (traffic information if applicable)
- Aircraft leaving the area:
I-ABCD, over Calliano, 3000 ft, request frequency change.
I-ABCD, Trento Info, contact Padova Information 124.150, ciao
¶ Procedures for departing IFR aircraft:
Phraseology for IFR traffic is mostly similar, with some operational differences.
At aerodromes where IFR procedures are available, the AFIU shall coordinate with the appropriate ATC and relay the IFR clearance to the aircraft on the ground:
Skyalps 1956, Bolzano Info, Padova Radar clears you to destination, NAXAV 1W departure, initial climb FL120, squawk 0252
- Aircraft requesting startup:
Skyalps 1956, Bolzano Info, startup approved, QNH 1013
All departing IFR aircraft are held for release by the relevant ATC, IFR traffic shall not enter the runway unless released.
¶ Arrivals
Prior to entering the airspace or commencing the approach, aircraft shall receive the following information:
- Preferred runway
- Latest weather
- Traffic information
- Instructions to join the traffic pattern (for VFR)
- Active NOTAMs or other important information (if applicable)
The AFIU shall provide relevant information on local traffic and aerodrome conditions to assist the flight crew in deciding whether to land or go-around. Such information shall be updated at AFIU discretion or when requested by the pilot.
Pilots shall not land if there are other aircraft on the runway
¶ Procedures for arriving VFR aircraft:
Trento Info buongiorno, I-ABCD, C172, from LIPN to LIDT, over Calliano 2500 ft, request information for a full stop landing
I-ABCD, Trento Info buongiorno, preferred runway 18, wind 180° 12 knots, QNH 1013 (traffic informations/no reported traffic) report left downwind runway 18
If METAR is available, the AFIU shall provide it.
- Aircraft joins the pattern:
Trento Info, I-ABCD, left downwind 18, full stop
I-ABCD, Trento Info, [no reported traffic / traffic information], report final runway 18
- Aircraft is on final:
I-ABCD, Trento Info, runway 18 no reported traffic, wind 180 degrees 5 knots
or
I-ABCD, Trento Info, runway 18 is free
- In case the runway is occupied:
I-ABCD, Trento Info, runway 18 occupied by [traffic information]
- Once the aircraft has vacated:
I-ABCD, Trento Info, on the ground at 1350, taxi stand 11 via A
¶ Procedures for arriving IFR aircraft:
Trento Info, buongiorno, I-ABCD, established VOR approach runway 18, 7 miles
I-ABCD, Trento Info buongiorno, runawy 18 no reported traffic, wind calm
¶ Coordination with ATC
For arriving IFR traffic the appropriate ATC unit shall provide an estimated time of arrival (ETA) to the AFIU. The ETA message shall if possible be provided at least 15 minutes before the ETA.
Transfer of communications shall be achieved not later than when the aircraft passes the controlled airspace boundary, if no other agreement has been made between the units concerned or in local instructions.
For departing IFR traffic, the AFIU shall relay the ATC clearance provided, traffic information and transponder code to the aircraft before departure and in exactly the form it was received.
Transfer of communication from the AFIS unit to the ATC unit shall be made as soon as safely possible and not more than 2 minutes after departure, in all cases not later than when the aircraft is estimated to exit the ATZ.