Claimed flights we could NOT retrieve a primary ADS-B trace for
Generated 2026-08-24T16:03:53.111Z 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-BND | 2023-05-11 | 404 | overlap OWENS-050 - St. Louis MO (audited_inaccurate, audit: inaccurate) |
| SU-BND | 2023-05-13 | 404 | overlap OWENS-050 - St. Louis MO (audited_inaccurate, audit: inaccurate) |
Where this page fits
The 404s listed here are the outer days around OWENS-050, a row that did not need them to fall: on the claimed date itself both free archives hold SU-BND flying Paris-Le Bourget to Greece, nowhere near St Louis. A refutation built on a tracked position is a different object from an empty archive, and keeping the two apart is the same discipline this site applies to evidence sealed until 2026, airborne surveillance records withheld over UVU and the autopsy that has never been released. For the case where this site got that wrong and had to say so, read what a 403 actually means — a published removal claim collapsed once five control aircraft returned the identical refusal.