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 | 2023-09-02 | 404 | overlap OWENS-018 - Wilmington DE (audited_inaccurate, audit: inaccurate) |
| SU-BTT | 2023-09-03 | 404 | overlap OWENS-018 - Wilmington DE (audited_inaccurate, audit: inaccurate) |
| SU-BTT | 2023-09-04 | 404 | overlap OWENS-018 - Wilmington DE (audited_inaccurate, audit: inaccurate) |
Where this page fits
Three 404s for SU-BTT in early September 2023 stand behind OWENS-018, and they are archive-range 404s — the control basket returned the same, so nothing here speaks to the Wilmington claim in either direction, as the overlap index notes. This site publishes its dead ends because a claim that has been tested and failed is a different object from a claim nobody can reach, and that distinction runs straight through the cover-up allegations, the censorship record and the account of a witness asked to delete his video. Read what a 403 actually means for the case that cost this investigation a published headline: flightradar24.com returns 403 to every scripted client, including its own homepage, while the page loads normally in a browser — the whole reason browser capture exists as a separate pass.