Study Guide:Flight Information Center

Flight Information Center (FIC)

Introduction

The Flight Information Center provides VFR traffic with info service and takes care of the alarm service in the Austrian airspace. The info service contains the information necessary to safely conduct a VFR flight by providing weather information, informing about hazards en route as well as giving out traffic information.

The area covered by FIC (Callsign Wien Information, or short, Wien Info) is split into two sectors, Wien Information North (134.625) and Wien Information South (124.400). Additionally, FIC in the TMA LOWW is provided on frequency 118.525.

On VATSIM, we conduct FIC by using the logon LOVV_I_CTR, on frequency 124.400 and LOWW_I_APP (TMA LOWW only), on frequency 118.525.

Phraseology

Basic principles

A pilot should initiate radio contact by calling in and providing only their callsign. Any other information shall not be passed on initial contact.

Making contact

OEABC: Wien Info, servus, OEBAC.

As the Info Controller, you now check for the aircraft and the flight plan. If positive flight plan you reply:

Info: OEABC, Wien Info, servus. I got all your information. QNH LOWI 1014.

or, if it's a short sightseeing flight, from LOWI to LOWI, for example, replying with the following suffices:

Info: OEABC, Wien Info, servus. QNH LOWI 1014.

If negative flight plan, you reply by:

Info: OEABC, Wien Info, servus. Go ahead.
OEBAC: OEABC, SR22, VFR from LOWZ to LOGO, 5nm west of St Johann im Pongau, squawk 7000, 5500ft, request traffic information.

You now create a flight plan for the pilot and reply:

Info: OEABC, roger, QNH LOWI 1012.

The phrase, "Currently no traffic" or similar shall not be used.

Further information

As you now got all information needed, check the route of the pilot for any hazards en route (military activity, parachuting, active restricted/danger areas) and inform the pilot about them:

 Info: OEABC, be advised of parachuting activity overhead LOGO up to Alt 6500ft.

In case of the route crossing any TMA, inform the pilot and ask if they want to cross it:

Info: OEABC, confirm you want to cross the TMA Linz?
OEBAC: OEABC, affirmative, we would like to cross the TMA Linz at 5500ft.
Info: OEABC, roger, call you back.

Now you coordinate with the current controller, which is responsible for the LOWL TMA, and ask for a VFR TMA crossing. Linz either tells you to keep the aircraft on your frequency or asks you to hand them over.

Info: OEABC, Linz Radar clears you to cross TMA Linz between 5000ft and 6000ft VFR, remain on my frequency.

or, if the responsible controller requests you to hand the pilot over:

Info: OEABC, for TMA crossing Linz contact Linz Radar on 129.625.

Traffic Information

Traffic information shall be provided in the following format:

• Type of traffic (VFR, IFR, Military,...)
• Position, based on the clock bearing
• Distance
• Direction
• Relative altitude
• Type of aircraft

When initiating a traffic information call, give the pilot a chance to respond first:

Info: OEABC, traffic information.
OEBAC: Go ahead.
Info: OEABC, VFR traffic, 3 o'clock, 3nm, opposite direction, 500ft below, Cessna 172.

Based on the type of traffic, traffic information shall not be issued above 3nm of separation. If the traffic is a fast-moving military jet, the 3nm rule get's voided ofc :)

Additionally, traffic information for aircraft flying at 4 - 6 o'clock might be suboptimal, given the limited view behind.

If a Pilot responds:

OEBAC: Traffic insight.

everything is fine. On the other hand, if the pilot reports:

OEABC: Traffic not insight. 

you may provide updated traffic information if the two targets move closer together. Nonetheless, you are not responsible for the separation at any time. If the aircraft is clear of traffic you respond:

Info: OEABC, clear of traffic.

Weather Information

You may provide weather information to pilots, above a certain severity.

Info: OEABC, be advised of CB overhead Graz, ceiling 6000ft.

For an up-to-date weather map, refer to the homebriefing. If you do not have access, weather info can be omitted.

MISC

Squawks

It is mandatory that all aircraft flying in Austrian airspace are equipped with a Mode-S transponder, so using squawk 7000 exclusively suffices for proper radar identification.

If you want to simulate only primary radar contacts, like in valleys, where secondary radar contacts are no longer possible, use the squawk range of 1550 - 1557. TopSky will assign the correct squawk automatically.

ASA

Altimeter setting areas, short ASA, are the 8 providing QNH areas, based on the aircraft's position. You may refer to the EAIP for an overview of the covered areas by each ASA: [1]

Turns & Climbs

In certain situations, may it be for avoiding danger areas, weather, or terrain, you are allowed to suggest headings/altitudes to the pilot:

Info: OEABC, VFR heading 180 to avoid restricted area Allentsteig.

If a pilot requests an IFR pick-up, they often have to climb above the MVA to be able to join IFR. In this case, use:

Info: OEABC, climb VFR altitude 9500ft.

After that, you may send them over to the responsible radar unit for their IFR clearance.

Entering CTAs

In certain situations, a pilot might need to fly a higher altitude than airspace E allows. In this case, coordinate with the responsible radar unit for clearance.

Info: OEABC, Klagenfurt Radar clears you into airspace D up to FL 125, climb VFR FL125, remain this frequency.

The radar unit may still requests you to hand them over.

You may leave vs rrequency change approved

A VFR pilot may leave your frequency at any time.

OEABC: Wien Info, OEABC approaching LOAV, leaving your frequency.
Info: OEABC, you may leave, servus.

If you told the pilot to remain your frequency, they are no longer allowed to leave on their own. In this case use:

Info: OEABC, frequency change approved, servus.

In case you assigned an SQ other then 7000, you tell them:

Info: OEABC, squawk VFR, frequency change approved/you may leave, servus.