VFR Position Reports

What is a position report

A position report is a pilot communication to ATC describing where they are in the sky, at what altitude, and with what intention. It's done:

• On controller request ("report position")
• Spontaneously when crossing a significant point (e.g. CTR boundary, VFR reference point)
• Periodically in long flights if in contact with FIS

It's the main way the controller (even without radar coverage) knows where you are.

Standard report structure

Three essential elements, in this order:

1. Horizontal position — where you are on the map
2. Altitude — what altitude you're at
3. Intention or next point — where you're going

For more elaborate reports you can add: speed, next reporting point, ETA at next waypoint, flight status.

VFR reference points

To give a clear horizontal position, the standard is to use published VFR reference points. These are geographic points recognizable from the ground:

• Geographic: lakes, rivers, mountains ("Lago di Lugano center", "Foce del Ticino")
• Anthropic: cities, bridges, dams, highways ("Mendrisio", "Verzasca dam")
• Aeronautic: VOR, NDB, intersections ("LUG VOR", "ALAGO intersection")

VFR charts (ICAO 1:500.000 and VFR Manual Switzerland) list standard points for each region. Study them before flight and use them in reports.

Altitude: how to say it

Altitude is given in feet with correct convention:

• Below transition altitude: in feet MSL (with local QNH set) — "altitude four thousand five hundred feet"
• Above transition altitude: in flight level (1013 standard) — "flight level eight zero" (FL080)

If you're VFR cross-country and change QNH often, always specify the QNH used when the controller asks:

Spontaneous reports

There are points where you must announce yourself spontaneously, even without explicit request:

1. CTR entry and exit

Even after the controller has cleared your route, report:

• At CTR entry (at a standard reporting point, e.g. "reporting Bironico, altitude 3500 feet")
• At CTR exit ("leaving CTR abeam Mendrisio, altitude 3000 feet")

2. Pattern and final reports

On approach to land, report in pattern:

• Downwind: "HB-PMR, downwind runway 19"
• Base: "HB-PMR, turning base runway 19" (rare, on request)
• Final: "HB-PMR, final runway 19"

3. Significant route or altitude change

If you decide a wide deviation (e.g. to avoid weather), communicate it:

Reports on request

Sometimes the controller will explicitly ask "Report position" or "Report passing 4000 feet". These are conditional future requests: meaning "when you reach that point/altitude, communicate it".

The art of concise reporting

A good report is not verbose. Examples comparing:

Swiss specifics

Summary — to remember

1. Three elements: position, altitude, intention.
2. Position = VFR reference point + distance/bearing.
3. Altitude in feet MSL (with QNH) below TA; FL above.
4. Spontaneous reports: CTR entry/exit, downwind, final, significant deviations.
5. Reports on request: conditional futures ("report passing 4000").
6. Concise, not verbose: same information, less radio time.

Sources

• ICAO Doc 9432 — Manual of Radiotelephony, Chapter 4
• ICAO Doc 4444 — PANS-ATM
• VFR Manual Switzerland — standard VFR points
• AIP Switzerland — ENR 1.2 (VFR procedures)