Investigation guide · Sources checked November 5, 2026, Chicago time.
A flight-tracking screenshot can look decisive: an aircraft was at a particular altitude, so it could not have been the light in a witness’s video. Before using that number to exclude a candidate, check what kind of altitude it represents. Two legitimate values can describe the same aircraft without representing the same measurement.
Pressure altitude is not geometric height
The FAA’s ADS-B FAQ distinguishes barometric and geometric altitude. The transmitted barometric value is pressure altitude, corresponding to an altimeter set to the standard 29.92 inches of mercury. The geometric value comes from GPS and represents height above the Earth ellipsoid.
Those are different reference systems. Neither should automatically be read as height above the observer’s roof or nearby terrain. A comparison that silently treats all three as interchangeable can create an apparent discrepancy before any unusual object has entered the analysis.
Read the actual data field
The ADS-B Exchange streaming documentation provides a concrete example. It labels alt_baro as barometric altitude in feet and alt_geom as geometric GNSS altitude in feet. It also distinguishes measured altitude from selected autopilot altitude fields. A pilot’s selected level is not proof that the aircraft has reached it.
The documentation says an unavailable field may be absent, and the barometric field can contain a ground-state indicator rather than a numerical altitude. Missing information should remain missing. Converting an absent value into zero, or interpreting a ground indicator as a measured height, introduces an error of the analyst’s own making.
A fair comparison
Our recommended workflow is to preserve the original field name, units, timestamp and provider alongside every extracted value. Record whether the website explains corrections applied to its display. If its treatment is unclear, say so rather than guessing from the map label.
Next, keep aircraft altitude separate from observer elevation and apparent angle above the horizon. A proper comparison needs a common vertical reference and the aircraft’s position relative to the observer. The existence of a plausible aircraft nearby is a lead, not a completed identification.
Finally, test the proposed match against the sequence: direction, time, changing position and visibility. If the claimed mismatch survives a documented comparison, retain it as a real limitation. If it disappears after correcting incompatible altitude definitions, explain that transparently.
The lesson is narrow but important. An altitude disagreement does not prove an exotic maneuver, and an altitude agreement does not prove an aircraft identification. The numbers become evidence only after their definitions are made explicit.









