Flight tracking data is the broadcast record of where an aircraft was, when it was there, and what it looked like in the air — most of it coming from the ADS-B signal that most aircraft transmit automatically. Knowing how to use flight tracking data in reporting means turning those raw position points into a claim you can defend: a verified route, a named aircraft, a documented pattern, and an honest statement of what the data cannot show. The process takes an hour for a simple check and a couple of weeks when you are building a pattern.
Three things matter more than anything else, and they run through every step below.
- One flight proves a flight happened. A pattern of flights can support a story about an operator, a route, or a network.
- A callsign is not an identity. Airlines reuse and swap them, so a callsign tells you almost nothing about who actually owns or operates the aircraft.
- Missing data is ambiguous. A flight that vanishes from a map may have had its transponder switched off, or it may simply have flown past an area with no receiver. You have to tell those apart before you write a word.
Below is the workflow I would hand a reporter starting on this beat: where the data comes from, which source answers which question, how to collect and check the records, how to compare a flight against its own habits, and how to write it up without overclaiming.
What You Need
You need four things before you open a tracker, and none of them is a subscription.
A narrow question. “Something interesting keeps flying out of this airport” is a lead. “Did aircraft registered to this operator visit this airport more than twice between March and June” is a question you can answer yes or no. Everything downstream gets easier once the question has a date range, a geography and a subject.
Two independent sources, not one. Any single map is a starting point. Keep a second tracker open in another tab or browser profile and compare. If a movement appears in only one feed, you have a lead, not a finding.
An ownership source. Aircraft positions are anonymous until you bridge them to a registration. You need somewhere to look up who owns the airframe, and you need to treat that lookup as its own claim with its own source.
A record-keeping habit. One row per flight observation, saved the day you make it. Screenshot the raw output, note the exact time you pulled it, and keep the URL. Memory degrades, sources change, and readers ask how you knew six months later.
It also helps to know which kind of data you are holding. Live tracking data is what a map shows now, usually seconds old. Historical records are archives with different retention rules per service. Scheduled-flight data is a published timetable, which is a plan rather than a fact. Official aviation statements are what an authority, airport or airline says happened. Mixing those four up is the most common way a careful reporter ends up with a wrong story.
Step-by-Step: Turn Flight Tracking Data Into a Reported Story
The workflow runs in six steps before you write anything. Document each one as you go, stamp every record with the time you retrieved it, and never publish a movement you have not checked against at least one independent source.
1. Define the reporting question
Start by turning a hunch into something falsifiable. Questions that survive scrutiny name an actor, a place and a window: whether a flight diverted, whether an aircraft visited a restricted area, whether a jet operated at an unusual hour, whether a route changed between two dates.
Write down what evidence would confirm it and what evidence would kill it. If the answer is “a long line of flights from one registered aircraft to one airport,” you know exactly what to go and collect. If the answer is “they were spying,” stop — that is an intent claim, and flight data records movement, not purpose.
Fix three parameters before you start: the time zone, the date range and the geographic boundary. Time zones alone cause more published errors in this beat than anything else, because a tracker displays local time while a report may quote UTC.
2. Choose the right flight-tracking source
Different sources answer different questions, and mixing them up is how reporters end up citing a consumer map for something that needs an official record.
Open ADS-B services — ADS-B Exchange, OpenSky Network, FlightAware, Icarus Flights. These collect broadcast signals from ground receivers and satellites. They are good for live positions and for reconstructing a path you watched yourself. Coverage is uneven: dense over North America and Europe, thin across large parts of Africa, Central Asia and open ocean.
Consumer map services — Flightradar24 and similar. Excellent interfaces, strong playback, useful alerts, and they handle enrichment (aircraft type, operator, registration) that the raw feeds lack. Treat them as a convenient view over an aggregated feed rather than a citable primary record, and corroborate anything load-bearing.
Status and schedule databases — airline and airport records, arrival and departure boards, published timetables. These are slower and less precise, but they are the ones operators and regulators recognise, which makes them the right source for a disputed claim.
Registration and ownership databases — AirFrames.org and similar. These bridge a tail number or hex address to an airframe history. They are indispensable and they are also incomplete: many airframes have a messy ownership chain, and a lookup tells you a registered owner, not who was in the cabin.
Official publications — aviation authority notices, airport statements, regulator reports, safety investigation findings. Slow, but the only thing that settles a contested fact.
Two things to check before you commit: how far back the archive goes, and whether the feed is delayed. Some services retain a couple of days of full detail and keep a summary for longer. If your question needs the shape of a path from two years ago, you may find only a departure and arrival pair, which tells you nothing about the route.
3. Collect the aircraft and flight records
Search the way the tool allows: by registration, by hex address, by callsign, by route, by airport, by date, or by drawing a box on the map over an area and reading off whatever crossed it. The area filter is the one reporters underuse, and it is how story ideas get generated in the first place.
For every flight record you keep, capture the same fields. Consistency is what lets you sort and group later:
- Flight number and callsign as displayed
- Aircraft registration and the 24-bit hex address
- Operator as displayed by that source, with the source named
- Departure and arrival airports, plus actual off-block and on-block times
- Timestamp, coordinates, altitude and ground speed for key points
- The source, the exact URL and the moment you retrieved it
Two cautions on the record itself. First, never treat a callsign as a legal identity: carriers reassign them, and the same three letters can belong to different aircraft on different days. Second, keep the hex address with every row. It is the one identifier that stays with the airframe, which is exactly what you need when the ownership story runs six months.
Where you can, work from a list of hex addresses or registrations rather than re-searching by hand each time. That list becomes your raw row set in the spreadsheet, and keeping one identifier column intact is what lets you sort, group and re-check the whole set at the end.
4. Check whether the movement is reliable
Before a movement supports anything, it has to survive a reliability check. Most raw feeds show several tell-tale problems.
Receiver gaps look like a flight sitting still or jumping forward in a straight line across hundreds of kilometres. It means nobody was listening, not that the aircraft teleported.
Duplicated points appear when several receivers hear the same broadcast. Identical timestamps with identical positions are one observation, not several.
Stale records are the same position repeated after an aircraft has landed and switched its transponder off. The signal stopping at an airport is normal.
Apparent jumps can be re-identified aircraft, a hex mismatch, or a receiver picking up a different signal on the same frequency.
The rule I hold to: if the suspicious movement does not show up in a second, independent tracker, treat it as an artefact until proven otherwise. If it does, escalate to the next tier — the airport or airline movement record, the operator’s own statement, satellite imagery, a weather report for the time and place, or an official aviation notice.
And when two sources disagree, that disagreement is itself reportable. Saying “the aircraft appears on one feed but not the other” is honest; quietly picking whichever feed supports your thesis is not.
5. Compare the flight with a baseline
A single flight is an event. A deviation is only meaningful against what normally happens. So build a baseline before you decide anything is unusual.
There are several, and you want at least two. Compare this flight with the same aircraft’s usual route. Compare it with its scheduled slot on the day. Compare it with the same operator’s other aircraft on the same day. Compare it with the same aircraft over a longer window — ninety days, a year — and look for the exception rather than the average.
Plenty of deviation is routine. Weather reroutes aircraft, air-traffic-control routing shifts paths for congestion or airspace restrictions, maintenance moves an airframe to a different base for weeks, and schedules change with the season. A jet that normally flies a 900-kilometre leg turning 40 kilometres off course because of a flow restriction overnight is a non-story.
The pattern becomes a story when it recurs, when it clusters geographically, or when it coincides with something externally checkable. Repeated overnight arrivals at an unusual airfield, a regular rotation between two airports, a schedule that consistently breaks a published slot — those hold up. One odd Tuesday does not.
6. Map the flight and quantify the pattern
Now make the evidence readable. Plot the recorded points in a mapping tool or a geographic information system and draw the path. Measure total distance and duration rather than eyeballing it. Filter the rows to the aircraft or operator you care about and count movements by airport, by month or by operator.
A count is far harder to argue with than a screenshot. “This aircraft visited that airport 14 times in 11 months, against 2 in the preceding 14 months” survives a fact-check in a way that “it keeps going there” does not.
Three formats do most of the work here. A path map answers “where did it go.” A repeat-visit timeline answers “how often, and when did it change.” A frequency table by airport or operator answers “is this unusual, and for whom.”
One caution on the map: it shows where an aircraft was, never why. A line drawn between two points does not carry intent, cargo, passengers or purpose. Resist writing around an image that looks damning.
7. Report the evidence without overclaiming
Write the finding first, then the sourcing, then the caveats, and keep them in that order.
Lead with what you verified. “Tracking data shows the aircraft flew from A to B on four dates between March and June” is a reportable fact. “A jet linked to the official visited the country three times before the vote” is an interpretation built on an ownership claim that needs its own evidence.
Name the source and the window in the sentence that carries the claim, not in a footnote. State the comparison you ran and the period it covers. Then describe the limits plainly: thin receiver coverage in the region, a feed that stopped at the border, a record that shows position but not occupancy.
Two more things make the work defensible. Publish enough method that someone else can repeat it — the aircraft identifier, the date range, the tools used — so a reader can rerun your analysis and get the same answer. And attribute anything disputed to the person who disputes it, including the operator’s denial, with the denial given in full if you cannot independently resolve the conflict.
On private individuals, slow down. Movement data on a private jet tied to a company or a public body is usually a public-interest matter. Movement data on an individual who has done nothing publicly wrong is a different question, and publishing a live location can create a safety risk that no newsroom wants on its hands. Delay the publication where delay does not cost you the story, and be able to state the public-interest reason for publishing at all.
Common Mistakes
Treating a dot on a map as proof of intent. The map shows position and nothing else. Fix: write “the aircraft flew,” not “the aircraft was carrying,” and never the reverse of what you want.
Assuming one identity across a callsign. A callsign belongs to an operator for a moment, not to an aircraft forever. Fix: track by hex address and registration, and verify who operated each individual flight.
Ignoring time zones. One tracker in local time, a report quoting UTC, and a witness quoting a different local time will produce a story nobody can confirm. Fix: fix one zone, state it in the text, and convert everything to it before comparing.
Using unsourced screenshots. A cropped image with no timestamp, no source and no identifier proves nothing and cannot be checked. Fix: publish the identifier, the date range and the method, so the image becomes evidence rather than decoration.
Overlooking gaps and calling them evasions. The most common data gap is a region with no receivers. Fix: cross-check every disputed movement in a second tracker, then check whether coverage in that area is dense at all.
Over-reading a single flight. One unusual movement is an anecdote. Fix: require repetition across a defined window before you call a pattern.
Failing to ask. Operators deny quickly and sometimes wrongly; airports and pilots confirm quickly and often help. Fix: send specific written questions with a deadline, publish the response or the fact that no response arrived, and give the right of reply before you publish rather than after.
Frequently Asked Questions
Is Flightradar24 trustworthy for journalism?
Treat it as a strong starting point rather than a citable primary record. The service aggregates feeds from volunteer receivers and satellites, so coverage and latency vary by region, and some data is enriched or delayed. Where receivers are dense its positions are good. Corroborate anything you plan to publish with a second tracker and a registration database, and note the retrieval time with each record.
How do air traffic controllers keep track of planes?
Controllers primarily rely on ground-based radar, voice communication and the aircraft’s Mode S transponder reply, which carries identity and altitude back to the controller. ADS-B is the broadcast version of that reply, sent outward to any receiver in range, and that broadcast is what makes public flight tracking possible. It supplements the safety network rather than replacing it, which is why a gap in ADS-B data says little about whether a flight was controlled.
Can I track a flight using my phone?
Yes, and it is a fine way to check a single movement. Consumer apps give live position, the registration and often the operator in seconds. For reporting they fall short: history depth is limited, export is clumsy, and you still need a second database plus a registration lookup before you can support a claim. Use the phone to scout, then move to a desktop workflow with your records saved.
Why can I not find a flight on a tracker?
Three reasons, and you have to separate them before drawing any conclusion. The aircraft may have flown beyond the reach of any receiver, which is common over oceans and sparsely covered regions. The transponder may have been switched off, which happens at the end of a flight or, occasionally, deliberately. Or the operator may be a military or state aircraft that broadcasts little or nothing in civil feeds. A second tracker usually distinguishes the first case from the rest.
Is it legal to publish someone’s flight location?
Rules differ by country and the legal specifics are not something to work out alone. The practical test is public interest and proportionality: is the movement itself newsworthy, does the aircraft connect to a company or public body, and would publishing a live position put someone at risk? Aircraft movement data is generally publishable in aggregate and routinely published by airlines. Delay where delay costs the story nothing, and get a legal review before naming an individual rather than a company.
Conclusion
Knowing how to use flight tracking data in reporting comes down to discipline rather than clever tools. Start with a question narrow enough to fail, keep two trackers open, record every row with its hex address and retrieval time, separate coverage gaps from deliberate silence, and test every movement against a baseline before you call it unusual. Then write the finding, name the source and window, state what the data cannot show, and give the operator a chance to answer.
Do the first three things before you do anything else: define the question, save the raw records, and confirm one disputed movement against a second source. Everything after that is faster.
