A witness sees a light, opens a flight-tracking app and finds no aircraft at the apparent location. That is worth recording. It does not, by itself, rule out an aircraft. A public map is the output of a detection and display system, not a complete census of everything overhead.
The useful question is not simply whether an icon appeared. It is whether that service could reasonably have detected and displayed the particular kind of aircraft, at that altitude and location, during the relevant interval.
Three different gaps
First comes equipment. ADS-B Out broadcasts an aircraft’s position and other information, but the United States does not impose a universal requirement covering every flight everywhere. The FAA’s airspace guide lists the airspace and altitude conditions where equipage is required. A rule tied to particular airspace is not proof that every aircraft visible from the ground must appear on a consumer screen.
Second comes reception. Flightradar24’s own explanation of missing aircraft says visibility depends on local coverage and aircraft/transponder type. It specifically notes difficulties at low altitudes and says aircraft may become visible only after climbing high enough for receivers to pick them up.
Third comes display policy. The same provider says some military and government aircraft are blocked for security reasons. This describes that service’s display, not a claim that every tracker follows an identical policy. It also does not establish that a particular unexplained light was military.
Turn a blank screen into a documented check
For a useful record, save the service name, time searched, map extent, filters and any playback settings. State the sighting time separately from the time of the lookup. Record the witness’s position and viewing direction, rather than treating a guessed point on the map as a measured target location.
Consider a hypothetical light seen low over a ridge. Searching only directly above the ridge could miss an aircraft much farther away along the same line of sight. That example is a geometric caution, not an identification. A candidate flight needs to match the observation’s direction, timing and apparent movement, with uncertainties acknowledged.
Compare another source where available, but ask what it adds. Two websites may rely on overlapping receivers or data feeds. Agreement is more useful when their coverage and data origins are understood. Conversely, a flight appearing on one map but not another is a reason to investigate the difference, not to assume the aircraft itself behaved anomalously.
A defensible conclusion might be: no matching track was found in the services and interval checked. That wording preserves the negative result without claiming an exhaustive exclusion. A strong aircraft identification requires a positive fit; a strong claim that aircraft have been excluded requires evidence about the search’s completeness.
The blank map is therefore a limit to investigate. It is neither proof of an extraordinary object nor permission to disregard a careful witness account.
Featured image: Generated illustration. Original Dark Fires conceptual tracking diagram, not a real flight plot.
Leave a Reply