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-09-05 | 404 | day after claimed departure from Le Bourget (LFPB); overlap OWENS-040 - Provo UT (audited_accurate, audit: accurate) |
Where this page fits
One lookup, one 404: OWENS-040 is a confirmed row in the register — SU-BTT measured 0.16 km from the Provo ramp on 4 September 2025 — and all this page records is that the following day produced nothing. That single blank sits six days before the killing, in the week when contractors reportedly carrying "US DoD Liaison" badges were said to be dropped at this field and counter-UAS equipment was reportedly tested there — claims published here as claims, with no badge list and no test log obtained by anyone. The date all of it converges on is 10 September 2025 — Orem, the only same-day same-airport overlap in the whole record by any definition, including the one Liz Wheeler uses to cut the tally to a single row.