Claimed flights we could NOT retrieve a primary ADS-B trace for
Generated 2026-08-24T16:03:53.119Z 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 | 2024-01-09 | 404 | overlap OWENS-019 - Sacramento CA (audited_inaccurate, audit: inaccurate) |
| SU-BTT | 2024-01-10 | 404 | overlap OWENS-019 - Sacramento CA (audited_inaccurate, audit: inaccurate) |
| SU-BTT | 2024-01-11 | 404 | overlap OWENS-019 - Sacramento CA (audited_inaccurate, audit: inaccurate) |
Where this page fits
By January 2024 the free archives do cover the dates, so the empty results listed here for SU-BTT mean something narrower and more interesting than the 2023 gaps: the network was listening and heard nothing, leaving OWENS-019 untested inside the overlap index rather than refuted, and outside the confirmed column of the 73 overlaps. An aircraft in a hangar and an aircraft with its transponder off produce identical silence, worth remembering wherever this case reads a switched-off signal as intent — the transponder claims at Provo, the N888KG departure, the drone reports. The page that pays off here is per-aircraft recovery status: one row per tail showing exactly how far back each archive reaches, which turns a shrug into a boundary you can cite.