VFR for Approach or ACC
VFR traffic entering Class C or D airspace of a TMA (e.g., the Faxi TMA) require clearance to enter the airspace. Clearance is considered to be given when the APP unit gives airport information and route clearance. For example:
🎧(TF-)ISN, cleared to enter the Faxi TMA routing Southbound towards Reykjavik, 6500ft, QNH 1014, report 6 miles from Reykjavik airport.
For VFR traffic in Class E enroute airspace, or beneath controlled airspace (e.g., Class G airspace below a TMA or enroute airspace), the ACC unit may provide them flight information service, workload permitting (traffic information, as well as known weather, aerodrome, etc. information at pilot’s request.)
Aircraft within ATS surveillance coverage may be radar identified and provided a radar service (either air traffic control service, or flight information service) by the relevant APP/ACC unit.
VFR aircraft in the TMA and enroute airspace are expected to maintain their own navigation, and generally (except in Class C airspace, like that of the Faxi TMA) to maintain their own separation with other traffic, based on traffic information from ATC.
If necessary to ensure separation or avoid an imminent collision between two aircraft, ATC may temporarily vector VFR aircraft. When vectoring is complete, the VFR aircraft should be instructed to “resume own navigation.” This is, however, not preferred and should be considered a last resort.
VFR Cruising Levels (>3000ft)
From 3000ft – FL195, VFR aircraft are allocated cruising levels separated by 1000ft, following the East/West semi-circular rule plus 500ft (i.e., Eastbound flights fly at odd thousands of ft + 500ft, and Westbound flights fly at even thousands of ft + 500ft). For example:
- An Eastbound VFR flight might cruise at 3500ft, 5500ft, FL75, etc.
- A Westbound VFR flight might cruise at 4500ft, 6500ft, FL85, etc.
No VFR levels are allocated above FL195, as all airspace in BIRD CTA above FL195 is Class A, and thus VFR is not permitted.
VFR in a Class C/D TMA (Approach)
VFR traffic entering the Class C or D airspace of a TMA require clearance to enter the airspace. Clearance is considered to be given when the APP unit gives airport information and route clearance (using the phrase “enter controlled airspace“ plus any necessary details/instructions.) E.g.,
🎧 (TF-)ISN, enter the Faxi TMA, route Southbound towards Reykjavik, 6500ft, QNH 1014, report 6 miles from Reykjavik airport.
Once the aircraft is in the TMA, APP may identify them and provide them with a radar ATC service, including radar-based traffic information (“o’clock” and giving specific distance.)
The above does not apply to Akureyri TWR’s procedural approach service in the Akureyri TMA. As the approach service is procedural (non-radar), TWR must only give non-radar traffic information to VFR aircraft in the TMA.
However, like in a CTR, the VFR aircraft will navigate at pilot’s discretion, and APP should not issue vectors or otherwise direct the aircraft’s movement unless required for traffic separation (in Class C airspace, VFR must be separated from IFR, but not other VFR; in Class D airspace, VFR does not need to be separated from other traffic.)
If vectoring a VFR aircraft for separation, APP shall use the phrase “resume own navigation” to indicate when the vectoring is complete and aircraft may navigate again at their discretion.
VFR in Class E or G Airspace
VFR traffic in Class E enroute airspace (like the Icelandic Domestic Area), or in Class G uncontrolled airspace underneath controlled airspace (outside of an ATZ/FIZ), do not have to contact ATC. They may, however, request flight information service (traffic information, as well as known meteorological, aerodrome, etc. information as relevant for the safe flight of the aircraft.) ATC should provide this as much as possible, workload permitting, but may refuse such service if traffic/workload is too high.
Aircraft within ATS surveillance coverage may be radar identified and provided radar-based traffic information by the relevant APP/ACC unit.