Claimed flights we could NOT retrieve a primary ADS-B trace for
Generated 2026-08-24T16:03:53.124Z by
site/docs/Planes/following/apis/public_open_source/code/pull_all.js.
Source tried: adsb.lol globe history —
https://adsb.lol/globe_history/YYYY/MM/DD/traces/<hh>/trace_full_<hex>.json
This is the only free, no-account source of historical ADS-B tracks we have found. It serves only what its volunteer feeder network actually received.
WHAT AN EMPTY RESULT DOES AND DOES NOT MEAN. A 404 here means adsb.lol holds no
trace for that airframe on that UTC day. It does not establish that the aircraft
did not fly, and it does not establish that a transponder was switched off. The
ordinary explanations come first: the aircraft was parked and silent, it flew outside
volunteer receiver coverage (most of the Atlantic, most of North Africa, much of the
rural US at low altitude), or the claimed date is simply wrong. Several of the rows
below are already recorded in overlaps.csv as audited inaccurate.
The claim is what is listed. The absence is what we found. Neither is proof.
| Tail | UTC date | HTTP | Why we looked |
|---|---|---|---|
| SU-BTT | 2025-07-21 | 404 | day after claimed departure from Le Bourget (LFPB); overlap OWENS-038 - Omaha / Lincoln NE (audited_partial, audit: partial); overlap OWENS-067 - Lincoln NE (audited_accurate, audit: accurate) |
Where this page fits
These are the empty lookups for OWENS-038, the 20 July 2025 Omaha-and-Lincoln row whose SU-BTT half the archives confirmed — a reminder that a confirmed row still has days around it nobody can see. Coverage gaps run through the human side of this case too, and they are usually the more consequential ones: the FBI Form 302 interviews that have never been released, the full autopsy that is still not public, the device and location warrants reportedly sealed to March 2026. Where the flight-side gaps do get closed is flight data recovery — four free routes, one of them a complete public mirror of an archive whose live API refuses the very same dates.