Skip to main content

Claimed flights we could NOT retrieve a primary ADS-B trace for

Generated 2026-08-24T16:03:53.113Z 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.

TailUTC dateHTTPWhy we looked
SU-BND2025-05-24404day after claimed departure from Le Bourget (LFPB); overlap OWENS-035 - Provo UT (audited_accurate, audit: accurate); overlap OWENS-065 - Provo UT (audited_accurate, audit: accurate)

Where this page fits​

Even a row the archives confirmed has an empty column, and this is it for OWENS-035 — the dates around 23 May 2025 where SU-BND produced no trace at Provo at all, kept in public beside the hit rather than quietly dropped from the register. That discipline is the whole point of the flight-data recovery effort: the first thing the backup network did was knock four claims out of the count, which is worth more to a reader than another confirmation, and it is a standard the sealed side of this case — warrants reportedly sealed to March 2026, the foreign-nexus review that was stopped — has never been held to. The confirmed half of this same date is worth the click: SU-BND measured 0.03 km from the Provo ramp, a co-location so tight it was entered on the sheet twice and counted twice — see the duplicate row OWENS-065.