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 | 2024-04-20 | 404 | overlap OWENS-025 - Provo UT (audited_inaccurate, audit: inaccurate) |
Where this page fits
These are the empty lookups behind row OWENS-025, the first documented Utah arrival in the whole Provo record, and an empty result here is a coverage gap in a volunteer network rather than a deletion, a distinction set out in full on the recovery hub. Provo is where the aircraft thread meets the rest of the case: an Egyptian Falcon crew is reported to have boarded there wearing DoD-liaison badges, Utah's governor is claimed to have met Egyptian and French figures thirteen days after the shooting, the foreign-involvement leads were reportedly closed off within six days, and the same airport carries the Israel thread's strongest aviation claim. Read Per-Aircraft Recovery Status next, because it says tail by tail how far back each archive reaches, which is the only honest way to tell a retention boundary from a removal, and it is the standard every claim on this site about missing flight data should be held to.