Skip to main content

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

Generated 2026-08-24T16:03:53.122Z 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-BTT2024-07-24404overlap OWENS-060 - Omaha / Lincoln NE (audited_inaccurate, audit: inaccurate)
SU-BTT2024-07-25404overlap OWENS-060 - Omaha / Lincoln NE (audited_inaccurate, audit: inaccurate)
SU-BTT2024-07-26404overlap OWENS-060 - Omaha / Lincoln NE (audited_inaccurate, audit: inaccurate)

Where this page fits​

This gap file backs row OWENS-060, a claimed Paris to Omaha to Lincoln to Wilmington to Cairo rotation the auditor placed in Egypt outright, and the 404s recorded here neither confirm nor contradict that, because all they say is that a volunteer network heard nothing on days already recorded as inaccurate in the overlap directory. The honest position is that the free archives cannot settle mid-2024 at all for these tails, which is why the paid history, the government records route and ultimately a forced-disclosure statute are the only ways this ends, the same conclusion the case reaches on sealed evidence. Read Per-Aircraft Recovery Status next, one section per tail saying exactly how far back each source reaches, the document that stops an ordinary retention boundary being written up as suppression, a mistake this site made once and corrected in public and the standard every recovery page here is held to.