Position reporting (when requested or required)

Position Reports

Position reports are the structured communications from pilot to ATC about current position, altitude, and forecast.

Source: ICAO Annex 11 Air Traffic Services, ICAO Doc 4444 PANS-ATM, Chapter 4.

When required?

Position reports are required in the following cases:

1. At standard reporting points in IFR (compulsory reporting points, charted on IFR maps).
2. At FIR transition (sector change).
3. At altitude change (climb / descent reached).
4. On specific ATC instruction: "Report passing [point]".
5. For traffic advisory verification: "Confirm passing [point]".
6. On entering controlled airspace (e.g. Class D).
7. In the pattern at controlled aerodromes — short position calls.

Standard format

[Own callsign], [position], [time], [altitude], [next reporting point + ETA]

Example

"Munich Radar, DEMRA, position BIBOS, time 1245 zulu, level 5500 ft, next MORAL, estimating 1305."

Components

1. Own callsign

• Full or abbreviated (if ATC has already abbreviated).

2. Position

• Reporting point name: "BIBOS"
• VOR + radial + distance: "TGO 270 radial, 15 DME"
• Geographic location: "10 NM south of Munich"
• Waypoint: "ARNUM"

3. Time

UTC (Zulu), optionally with minutes:

• "Time 1245" (12
  UTC).
• "Time 1245 zulu" (explicit).

4. Altitude (level)

• VFR: "level 5500 ft QNH 1015" or simply "5500 ft".
• IFR: "flight level 100".

5. Next reporting point + ETA

• "Next MORAL, estimating 1305"
• "Next [point], estimating [time]"

Position report in the pattern

In the pattern of a controlled aerodrome the position reports are shorter and more simply structured. They typically contain only two core elements:

Example pattern calls (controlled field):

• "DEMRA, downwind runway 26, Munich Tower."
• "DEMRA, base runway 26."
• "DEMRA, final runway 26."

At uncontrolled fields (self-radio):

• "[Field name] traffic, DEMRA, downwind runway 08."

→ Pure pattern reports need no altitude (other than standard pattern altitude) or time — tower knows these from context.

"Downwind 16" — interpretation

When a pilot reports "Downwind 16", the geometric situation is unambiguously derivable:

→ Interpreting a "Downwind XX" pattern call gives other pilots/ATC an instant 3D overview: heading, position relative to field, expected next route.

Examples:

• "Downwind 26" → pilot heading ≈ 080°, runway to left (in standard left pattern).
• "Downwind 12" → pilot heading ≈ 300°, runway to left (in standard left pattern).

When are VFR position reports required?

In VFR usually NOT required, because:

• Reporting points are primarily for IFR.
• VFR traffic often follows own routes.
• See-and-avoid principle dominates.

However: with FIS service or on entering controlled airspaces ATC may require or expect a position report:

Entry into Class D airspace (CTR / TMA)

Position reports are usually required on VFR entry into Class D — pilot reports:

• Position at entry (e.g. "Over VRP November, joining Munich CTR").
• Altitude.
• Intentions (landing, transit, next route).

ATC can additionally require periodic position updates during Class D transit.

Example on CTR entry: "Munich Tower, DEMRA, over VRP November, level 2500 ft QNH 1015, request landing instructions runway 26."

Entry into Class C

Class C is similar to Class D but usually with the additional 5-minute pre-call requirement (see lesson "Initial Call Structure").

FIS service

ATC may at any time request a position report:

• "DEMRA, report position."
• Pilot: "DEMRA, position 10 NM north of Augsburg, level 5500 ft."

Example — standard IFR position report

Pilot

"Frankfurt Radar, DEMRA, position BIBOS, time 1230, flight level 100, next MORAL, estimating 1255, request descent."

ATC

"DEMRA, Frankfurt Radar, position correct, descend to flight level 70, report leaving flight level 100."

Pilot read-back

"Descend to flight level 70, report leaving flight level 100, DEMRA."

Pilot on leaving

"Frankfurt Radar, DEMRA, leaving flight level 100."

ATC

"DEMRA, roger, descend to flight level 70."

Shorter position updates

For simpler cases:

• "DEMRA, passing Augsburg, level 5500 ft."

"Report passing [point]"

ATC requests specific report:

• ATC: "DEMRA, report passing VOR Munich."
• Pilot on passing: "DEMRA, passing Munich VOR, level 5500 ft."

"Report reaching [altitude]"

ATC requests altitude confirmation:

• ATC: "DEMRA, report reaching flight level 80."
• Pilot on reaching: "DEMRA, reaching flight level 80."

"Report leaving"

ATC requests report on leaving an altitude:

• "DEMRA, report leaving flight level 100 for descent."

Important conventions

• Time always UTC (Zulu).
• Position always with altitude (except pattern reports).
• ETA always as HHMM (four digits).

Common errors

• Local time instead of UTC.
• Vague position ("over Augsburg area").
• Altitude forgotten outside pattern.
• Report before reaching reporting point (too early) — ATC awaits actual passage.
• Wrong pattern-position order confuses other traffic.

Practical recommendation

• PLOG ready with all reporting points + expected times.
• Before passing pre-formulate the call (1-2 s), then transmit at passage.
• Verify GPS for accurate reporting-point passage.