Claimed flights we could NOT retrieve a primary ADS-B trace for
Generated 2026-08-24T16:03:53.125Z 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-08-18 | 404 | day after claimed departure from Le Bourget (LFPB); overlap OWENS-039 - Omaha / Lincoln NE (audited_partial, audit: partial) |
Where this page fits
The blank lookups for OWENS-039 — 17 August 2025, SU-BTT, the last Lincoln rotation before Charlie Kirk was killed — are listed here rather than folded into the row's verdict, because a checked-and-empty date and an unchecked date are not the same claim. Three weeks after this rotation the aircraft thread arrives at 10 September, where the questions stop being about maintenance schedules and become questions about what the intelligence services knew and why a foreign-nexus review was reportedly stopped. The 73 overlaps shows what this rotation looked like before anyone tested it — every date, city, airport and tail the spreadsheet published, reconstructed line by line and now carrying a primary-data verdict each.