Skip to main content

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

Generated 2026-08-24T16:03:53.108Z 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
N40JD2025-09-01404September 2025 window sweep (kirk side) - not a claimed date, a systematic look
N40JD2025-09-03404September 2025 window sweep (kirk side) - not a claimed date, a systematic look
N40JD2025-09-07404September 2025 window sweep (kirk side) - not a claimed date, a systematic look
N40JD2025-09-08404September 2025 window sweep (kirk side) - not a claimed date, a systematic look
N40JD2025-09-12404September 2025 window sweep (kirk side) - not a claimed date, a systematic look
N40JD2025-09-13404September 2025 window sweep (kirk side) - not a claimed date, a systematic look