GDE-070 |
Flight tracking verification | |||||||
Aviation | ||||||||
October 2026 | ||||||||
01
What it is
A flight tracker is a website that maps aircraft positions from the radio signals planes broadcast, and for OSINT it is the fastest way to verify where a flight actually went, when it diverted and whether it declared an emergency.
Most airliners and many smaller aircraft carry an ADS-B transponder, which broadcasts position about twice a second along with identity, altitude and speed. ADS-B (Automatic Dependent Surveillance-Broadcast) is an open signal, and thousands of volunteers run ground receivers that feed it to tracking networks. Where an aircraft has an older Mode S transponder, networks calculate its position by multilateration (MLAT), timing the same signal at several receivers.
That shared record answers practical questions fast: did this flight turn back, where did it land, when did it change course and what code was it squawking? Journalists, fact-checkers and OSINT researchers use it to test claims about flight incidents within minutes, well before official reports appear.
| When to use this guide
|
02
How do you verify a flight with a flight tracker?
Identify the aircraft, pull its track from more than one network, then test what the track can and cannot prove before you report it.
These tools cover the workflow. Most are free, and several exist because volunteers share their receiver data.
ADS-B Exchange: Free. A community feeder network that states it displays all aircraft broadcasts as received, without filtering. The live map includes trace playback; bulk historical data is a paid product.
airplanes.live: Free. A community-run ADS-B and MLAT aggregator that states it never filters aircraft data, useful as a second unfiltered source.
GPSJam: Free. A daily map of areas where aircraft reported low navigation accuracy, built from airplanes.live and ADS-B Exchange data.
Aviation Weather Center: Free, no login. The US National Weather Service source for METAR and TAF airport weather reports.
OpenSky Network: Free with registration. A non-profit research network with live data; its historical database is open on application to university researchers, government bodies and aviation authorities.
Flightradar24: Free and paid tiers. A widely used consumer tracker, combining ADS-B, MLAT and satellite data. The free plan keeps 7 days of flight history; paid plans extend it to 90 days, 365 days or 3 years.
| Before you begin Stop at the login. Every step here works from public maps without an account. If a tracker asks you to sign in or pay for older history, switch to an unfiltered network or record the gap rather than creating an account under your own name. Legal considerations. Rules on receiving and republishing aviation radio data differ by country, so check local law before running your own receiver. Linking a flight to a named passenger is processing personal data under the GDPR and UK GDPR, so record your lawful basis, such as legitimate interests, and whether the journalism exemption applies. |
Flight number, ATC callsign, tail registration and 24-bit ICAO hex code are four different identifiers. Flight numbers repeat daily, so open the aircraft panel, record the registration and hex code, and search every other source by hex code.
Replay the flight on Flightradar24. Note departure, every turn, hold or altitude change and the landing airport, all in UTC. Screenshot the track and data panel at each point that matters to the claim.
Search the hex code on ADS-B Exchange and airplanes.live. Different receiver networks see different parts of a route, and some consumer trackers withhold aircraft whose operators ask them to. Agreement across networks strengthens the record; a difference is a finding to log, not to smooth over.
The transponder data panel shows the squawk code. Under FAA guidance, 7700 signals distress or urgency, 7600 a loss of two-way radio and 7500 unlawful interference. Note when the code first appeared, how long it held and whether it changed.
Zoom into gaps and check each segment: ADS-B, MLAT or satellite positions are received data, while a straight line across a coverage gap is not. MLAT needs the same signal at three or more receivers, so it drops out over sea and sparse terrain. Mark every gap with its start and end time.
Pull METAR reports for the departure, destination and diversion airports from the Aviation Weather Center for the hour in question; the database holds the previous 15 days, so pull them early. Then open GPSJam for that date: low navigation accuracy in the area can explain a wandering or impossible track.
Save each tracker page to the Wayback Machine where it allows capture, and export track data where the platform offers it. Write a short log: identifiers, sources, times in UTC, gaps and what each source showed. Free history windows expire, so capture early.
|
03
Where flight tracker data misleads
A track looks precise, but each line on the map rests on receivers, codes and identifiers that can mislead without a second check.
Estimated track read as a flown route: Some trackers draw a line across coverage gaps, and it is easy to quote that line as the route flown. A diversion described from an estimated segment can be wrong by hundreds of kilometres. Verifying check: confirm received positions on both sides of the turn on at least two networks.
Flight tracker gap read as a transponder switch-off: A missing segment usually means no receiver heard the aircraft, not that the crew turned the transponder off. Oceanic and remote routes are patchy on every network. Verifying check: compare the gap with neighbouring aircraft on the same route; if they vanish too, it is coverage.
A brief 7700 read as a declared emergency: FAA guidance warns pilots that passing through 7500, 7600 or 7700 while changing codes can cause momentary false alarms. One stray message is not a declaration. Verifying check: look for the code held across consecutive messages, plus a change in route or altitude, or confirmation from the airline or authorities.
Flight number matched to the wrong aircraft: The same flight number flies every day and is sometimes operated by a different aircraft at short notice. Historical searches by flight number can return the wrong date or airframe. Verifying check: match the hex code, registration and date across every source.
Chain of custody: Free flight history expires and live pages update, so the evidence for a flight finding can disappear within days. Retain what a reviewer would need to reproduce your conclusion, including what each source did not show.
Record the hex code, registration, callsign and flight date in UTC before any analysis.
Screenshot each tracker track and data panel with the URL and capture time visible.
Archive each tracker page and METAR report, and note the capture URL.
Export and hash any downloadable track data, and log the platform and query used.
Log every gap, estimated segment and network disagreement alongside the finding.
04
Go deeper
Take the method further with the aviation reference cards and the full ADS-B tutorial.
CARD · AVI-001 · SIGNAL TIER
Aviation OSINT: flight tracking to evidentiary standard
Flightradar24 and ADS-B Exchange, queried in the right order for a defensible flight record.
CARD · AVI-002 · SIGNAL TIER
Aircraft registration and ownership databases
Civil aviation registries and corporate records, traced from tail number to owner.
METHODS · SIGNAL TIER
Tracking aircraft with ADS-B and transponder records
Hex codes, redaction and registry lookups, built into a flight record that holds up in publication.
Evidentiary standard
Signal & Shadow operates to the LST-001 evidentiary standard. All claims are graded against the LST-001 v1.0.3 confidence tiers (Confirmed, Corroborated, Reported, Alleged) per the canonical voice and structural specification.
About Signal & Shadow
Signal & Shadow is an independent forensic investigation and methodology practice publishing tutorials, reference cards, and forensic dossiers for working practitioners. Founded by Derek Bowler.