What information must be included in a mandatory IFR position report?

According to the AIM, a standard IFR position report must include: aircraft identification, position, time over the fix, altitude, type of flight plan, estimated time of arrival (ETA) at the next reporting point, and the name of the succeeding reporting point. These reports are required at all designated compulsory reporting points, which are depicted on en route charts as solid triangles, whenever the aircraft is not in radar contact with ATC. Providing complete and accurate position reports allows ATC to maintain positive separation between IFR traffic in non-radar environments.

When is an IFR pilot required to make a position report versus when is it optional?

Mandatory position reports are required at compulsory reporting points — depicted as solid triangles on en route charts — whenever ATC has not advised the pilot that radar contact is established. Optional (on-request) reporting points are depicted as open triangles and only require reports if ATC specifically requests them or the pilot voluntarily provides information useful to ATC. Additionally, pilots should make immediate reports of unforecast weather, airspeed changes of 10 knots or 5% TAS, or the inability to climb or descend at 500 fpm, as outlined in the AIM.

Why do IFR position reporting requirements not apply when a controller says 'radar contact'?

When ATC advises 'radar contact,' the controller is able to positively identify and track the aircraft on radar, eliminating the need for the pilot to provide verbal position updates at compulsory fixes. In a radar environment, ATC derives continuous position data directly from the radar return, which is more accurate and timely than a pilot report over a fix. However, if radar contact is subsequently lost and ATC advises 'radar contact lost,' the pilot must resume mandatory position reports as required by the AIM and 14 CFR Part 91.

Position Reporting Requirements on IFR Flight Plans

When you fly IFR, the air traffic control system depends on knowing where you are. In a radar environment, a controller can see your blip on the scope and doesn't need you to announce your position every few minutes. But the moment you fly outside radar coverage — crossing remote terrain, operating at low altitudes in mountainous areas, or flying oceanic routes — you become invisible to ATC. Position reporting is the procedural bridge that keeps the system working when radar cannot. Understanding exactly what to report, when to report it, and how to phrase it is both a practical IFR skill and a heavily tested topic on the FAA Instrument Rating knowledge exam.

Position reporting requirements are detailed in the Aeronautical Information Manual (AIM), Chapter 5, and form a core part of enroute IFR procedures. There are two categories: mandatory position reports, which you must make at every designated fix when not in radar contact, and additional position reports, which are required whenever specific situations arise regardless of radar contact. Mastering both categories will keep you safe and keep controllers happy.

Radar Contact vs. Non-Radar Environments

The first thing to understand is what changes when radar contact is established — or lost. When a controller tells you "radar contact," they can see your position continuously and no longer need you to report over each fix. You still have communication responsibilities, but routine fix-by-fix position reports are suspended. When radar contact is lost — the controller will explicitly say "radar contact lost" — you revert to non-radar procedures immediately and must begin making mandatory position reports at every designated fix along your route.

It's worth noting that radar contact is not guaranteed even in the contiguous United States. Mountainous terrain, low altitudes, and remote areas can all put you in a non-radar environment. Internationally, non-radar enroute operations are the norm over large oceanic stretches. Solid habit formation around position reporting protects you in any environment.

Mandatory Position Reports

When operating without radar contact on an IFR flight plan, you are required to report your position at every compulsory reporting point along your route. On aeronautical charts, compulsory reporting points are depicted as solid triangle symbols (filled-in triangles) overlaid on VORs, intersections, or other fixes. Non-compulsory reporting points use an open triangle — you would report there only if requested by ATC or if a significant situation arises.

Each mandatory position report contains a specific set of information. The AIM defines the standard format, often remembered as a structured sequence:

Aircraft identification — your full callsign as filed on the flight plan.
Position — the name of the fix or reporting point you are over or abeam.
Time — the actual time (in UTC/Zulu) you crossed the fix.
Altitude or flight level — the altitude you are maintaining at that point.
Type of flight plan — IFR (this clarifies the context for the controller).
ETA and name of the next reporting point — gives ATC a target to work with for sequencing and separation.
Name only of the next succeeding reporting point — the fix after the next one, so ATC has situational awareness further down your route.

A practical example: "Denver Center, Cessna 4521 Tango, over KARFO intersection at 1432 Zulu, one zero thousand feet, IFR, estimating BUGGS intersection at 1457 Zulu, HAWKK intersection next." This complete seven-element report is what the AIM prescribes and what the knowledge test will probe.

Additional (Non-Mandatory) Position Reports

Beyond the compulsory fix-by-fix reports, the AIM identifies a list of situations that require a position report regardless of whether you are in radar contact. These are sometimes called "additional reports" and they apply universally — even if you have a solid radar return on the controller's scope. Think of them as safety-driven notifications that ATC needs to maintain the integrity of your clearance and keep other traffic separated from you.

The AIM lists the following situations requiring an immediate report to ATC:

Vacating a previously assigned altitude for a newly assigned altitude — anytime you leave a level, report it.
An altitude change when operating under VFR-on-top — if you are climbing or descending under a VFR-on-top clearance, ATC needs to know.
When unable to climb or descend at a rate of at least 500 feet per minute — this affects ATC's ability to provide standard separation and must be reported immediately.
When cruise clearance altitude is not reached within approximately three minutes of the estimated time — a significant timing discrepancy signals possible problems.
Missed approach — when you execute a missed approach, report it immediately. ATC must resequence you, issue new instructions, and protect airspace.
When your filed TAS changes by 5 percent or 10 knots (whichever is greater) from what was filed — a significant speed change affects ETAs and spacing of other IFR traffic.
Loss of navigation capability — if any nav equipment fails that was part of your filed routing or required for the route, ATC must know so they can issue alternate routing or radar vectors.
Any loss of communications equipment — though if you've truly lost comms, you follow the lost comms procedures in 14 CFR 91.185 rather than making a radio call you can't make.
Unforecast weather conditions — including icing, turbulence, or wind shear that was not in the forecast and could affect other aircraft on the route.
Safety of flight information — any other information you believe is essential to the safety of the flight.

Why Position Reporting Matters

IFR separation is not magic — it is a system of rules, timing, and procedures that controllers apply to keep aircraft from occupying the same airspace. In a non-radar environment, the controller must use procedural separation, which means ensuring that aircraft are separated by defined time or distance intervals at fixes. If you fail to report over a fix, the controller has no way of knowing whether you actually crossed it on time, flew past it, or experienced an emergency. Without that information, they cannot safely release conflicting traffic to cross the same fix.

Timely position reports also trigger Search and Rescue (SAR) actions if you go missing. If your last known position report was at a specific fix, SAR resources can be directed to the right area quickly. A missing position report followed by loss of communication is one of the triggers that initiates a formal communication search and, eventually, SAR procedures.

Key Numbers and Rules

500 ft/min climb or descent rate: If you cannot achieve this rate, you must report it immediately to ATC.
5% or 10 knots TAS change: Whichever is greater triggers a required report of your new speed.
Solid triangle on charts = compulsory reporting point (report over it when not in radar contact).
Open triangle on charts = non-compulsory reporting point (report only when requested by ATC).
Seven elements make up a complete mandatory position report: identification, position, time, altitude, type of flight plan, ETA/next fix, and succeeding fix.
Radar contact does NOT eliminate additional reports — those situational reports are always required.

Memory Aid

For the seven elements of a position report, many instrument students use the phrase "Pt PAIN" — though the classic and most widely used memory tool in FAA training is the acronym built from the report elements themselves. A practical way to lock them in is to remember the phrase "Pilots Tell All: Position, Time, Altitude — then IFR type, ETA Next, Name Next-Next." Walk through it on every practice position report call until the sequence is automatic: Who you are, Where you are, When you got there, How high, What kind of flight, When you'll be at the next fix, and what comes after that.

Common Test Traps

Assuming radar contact eliminates all reports: Radar contact only suspends mandatory compulsory fix reports. The situational additional reports (missed approach, speed changes, altitude deviations, etc.) are required regardless of radar contact.
Confusing solid vs. open triangles: Only solid triangles are compulsory reporting points. Open triangles require a report only when ATC requests it or a significant situation dictates.
Forgetting the 500 ft/min rule: The exam may describe a scenario where you're in a heavily loaded aircraft struggling to climb — you must report to ATC if you can't maintain 500 ft/min.
Omitting the "name only of the next succeeding reporting point": Students often stop after giving the ETA to the next fix and forget to name the fix after that. The AIM requires both.
Not reporting a missed approach immediately: A missed approach is always an immediate mandatory report — don't wait until you're established on the missed approach procedure. Call ATC as soon as the decision is made.