PUBLIC FLIGHT DATA · READING MISSING OBSERVATIONS

A gap in a flight track: what did the tracker actually observe?

A line stops over the coast and resumes inland twelve minutes later. That gap does not tell you that the aircraft landed, changed course or stopped transmitting. It tells you that the displayed record lacks observations for an interval. Before interpreting the flight, establish what the website supplied: timestamped positions, an estimated segment, a schedule or a mixture.

Follow the measurement from aircraft to screen

ADS-B is a system through which equipped aircraft broadcast surveillance information. A public tracking page is a further product built from available data. A break on that page is therefore several steps removed from a finding about equipment aboard the aircraft.

The FAA explains that reception range depends on altitude, terrain, transmitter power and receiver sensitivity in its ADS-B FAQ. A receiver that can hear traffic higher up may have a more restricted view near the ground. A coastal gap and a low-altitude gap need context; their shapes alone do not diagnose a cause.

Flightradar24’s provider guidance describes signal loss, coverage and technical problems as explanations for a disappearing aircraft. It also distinguishes track information from route labels assembled using schedule databases. Read the documentation for the actual provider in your case rather than transferring one service’s explanation to every tracker.

Four different things a flight page can show

A smooth line is visually persuasive. Unless the source supplies intermediate observations, it cannot show every turn between its endpoints. Do not measure a bend in an illustrative connection and report it as an observed diversion.

Twelve missing minutes, three different conclusions

Fictional desk exercise. Consider an invented, publicly scheduled passenger service. This is a teaching packet, not a live flight lookup. The packet contains a position at 12:04 UTC, another at 12:16 UTC and an airport arrival-board entry labelled “actual arrival 12:31 UTC.” No positions are included between the first two times.

The subtraction is straightforward: the interval between the supplied positions is twelve minutes. The path during those minutes is unresolved. The arrival-board entry is a separate reported event; it does not supply the missing track points, establish a touchdown time without the board’s definition, or identify anyone aboard.

• Supported by the packet: two displayed positions twelve minutes apart and an actual-arrival entry at 12:31.
• Still open: the intervening path and why the position record has a gap.
• Unsupported: “the crew switched off the transmitter for twelve minutes.” The packet contains no equipment-state evidence.

Try rewriting the finding in one sentence before adding explanations: “The supplied track has no intermediate observations between 12:04 and 12:16 UTC; the reason for that gap is unresolved.” Keep the arrival evidence in the next sentence, with its source and status label.

Choose a check that can change the answer

First confirm the date, service identifier and time zone. Reused daily flight numbers make the date part of the match. Preserve the original display and your observation time. If the issue is finding the correct record at all, start with the search-coverage checks; this article assumes you already have the relevant track.

Next inspect the provider’s data labels and available history through ordinary access. A second public source can help establish an event, but two websites may redistribute the same underlying feed. Agreement between them is not automatically two independent measurements. Missing historical coverage should stay a documented limit; do not evade an access or privacy restriction to fill it.

If the decision concerns whether a scheduled passenger service arrived, an official airline or airport status record may answer it more directly than reconstructing every airborne point. If it concerns the exact route during the gap, an arrival entry will not finish the task. Separate those questions before collecting more screenshots.

Use the OSINT report template to record the interval, supplied positions, source labels, independent event evidence and unresolved explanation. A useful handover makes the missing segment visible in the reasoning as well as on the map.