Difference between revisions of "Study Guide:Flight Information Center"
| Line 23: | Line 23: | ||
If positive flight plan you reply: | If positive flight plan you reply: | ||
| − | Info: OEBAC, Wien Info, servus. I got all your information. | + | Info: OEBAC, Wien Info, servus. I got all your information. QNH LOWI 1014. |
If negative flight plan, you simply reply by: | If negative flight plan, you simply reply by: | ||
| Line 37: | Line 37: | ||
Info: OEBAC, be advised of active restricted area Allentsteig up to FL125. | Info: OEBAC, be advised of active restricted area Allentsteig up to FL125. | ||
| − | In case of the route crossing any TMA, inform the pilot and ask if they want to cross it | + | In case of the route crossing any TMA, inform the pilot and ask if they want to cross it: |
Info: OEBAC, confirm you want to cross the TMA Linz? | Info: OEBAC, confirm you want to cross the TMA Linz? | ||
| Line 47: | Line 47: | ||
Info: OEBAC, you are cleared through the TMA Linz between 5000ft and 6000ft, remain on my frequency. | Info: OEBAC, you are cleared through the TMA Linz between 5000ft and 6000ft, remain on my frequency. | ||
| + | |||
| + | ==== 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 iniating a traffic information call, give the pilot some time to respond: | ||
| + | |||
| + | Info: OEBAC, traffic information. | ||
| + | OEBAC: Go ahead. | ||
| + | Info: OEBAC, vfr traffic, 3 o'clock, 3nm, same direction, 500ft below, C172. | ||
| + | |||
| + | ==== Weather Information ==== | ||
| + | You may providfe weather information to pilots, above a certain serverity. | ||
| + | |||
| + | Info: OEBAC, be advised of CB overhead Graz, ceiling 6000ft. | ||
| + | |||
| + | == Do Not == | ||
| + | * You only provide information, do not order the pilot to do certain things (climb, turn) only provide suggestions. | ||
| + | * The phrase "Currently no traffic." shall not be used. | ||
| + | * Do not hand over pilots to other frequencies. This does not apply for TMA crossings or CTR entries. If a pilot informs you about there wish to leave, you may respond: | ||
| + | Info: OEBAC, you may leave my frequenzy, servus. | ||
| + | |||
| + | |||
| + | TBD: | ||
| + | |||
| + | * VFR Squawks | ||
| + | * ASAS | ||
| + | * CTAs | ||
| + | * VFR climbs | ||
Revision as of 11:38, 5 September 2020
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). ???
TBD: Add Chart here
On VATSIM, we conduct FIC by using the logon LOVV_I_CTR, on frequency 124.400 only.
Phraseology
Basic principles
A pilot should initiate radio contact by calling in and providing his callsign. Any other information shall not be passed on initial contact,
Making contact
OEBAC: 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: OEBAC, Wien Info, servus. I got all your information. QNH LOWI 1014.
If negative flight plan, you simply reply by:
Info: OEBAC, Wien Info, servus. Go ahead. OEBAC: OEBAC, Sierra Romeo Two Two, VFR from LOWZ to LOGO, 2 Minutes south of Goldegg, 5500ft, request traffic information.
You now create a flight plan for the pilot.
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: OEBAC, be advised of active restricted area Allentsteig up to FL125.
In case of the route crossing any TMA, inform the pilot and ask if they want to cross it:
Info: OEBAC, confirm you want to cross the TMA Linz? OEBAC: OEBAC, affirmative, we would like to cross the TMA Linz at 5500ft. Info: OEBAC, 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: OEBAC, you are cleared through the TMA Linz between 5000ft and 6000ft, remain on my frequency.
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 iniating a traffic information call, give the pilot some time to respond:
Info: OEBAC, traffic information. OEBAC: Go ahead. Info: OEBAC, vfr traffic, 3 o'clock, 3nm, same direction, 500ft below, C172.
Weather Information
You may providfe weather information to pilots, above a certain serverity.
Info: OEBAC, be advised of CB overhead Graz, ceiling 6000ft.
Do Not
- You only provide information, do not order the pilot to do certain things (climb, turn) only provide suggestions.
- The phrase "Currently no traffic." shall not be used.
- Do not hand over pilots to other frequencies. This does not apply for TMA crossings or CTR entries. If a pilot informs you about there wish to leave, you may respond:
Info: OEBAC, you may leave my frequenzy, servus.
TBD:
- VFR Squawks
- ASAS
- CTAs
- VFR climbs