How Live Flight Tracking Actually Works

If you have ever wondered how live flight tracking works, the short version is that the aircraft is doing most of the work before any tracking site sees a thing. It already knows exactly where it is, and a tracking map is really just the last stop in a chain that starts in the cockpit and ends on your screen. This guide follows that chain link by link, from what the aircraft measures about itself to why the dot sometimes stops moving for an hour over open water, and it is honest about the last part rather than glossing over it.

What a modern aircraft already knows about itself

Every commercial aircraft flying today carries navigation equipment that continuously works out its own position, altitude, ground speed and heading. The core of this is satellite-based positioning, the same GPS family of systems your phone uses, feeding into onboard avionics that combine it with other instruments (barometric altitude, inertial reference, airspeed) to produce a position the aircraft is confident in several times a second.

None of this exists for tracking purposes. It exists so the aircraft and the people flying it know where they are, how fast they are going and which way they are pointed, which is the basic information any aircraft needs regardless of who else is watching. Tracking only becomes possible because that information does not stay locked inside the aircraft. It gets broadcast outward, and that broadcast is the part a tracking map actually depends on.

ADS-B: how the aircraft tells the ground where it is

The broadcast mechanism most community flight trackers rely on is called ADS-B, short for Automatic Dependent Surveillance-Broadcast. The name describes the whole idea in four words: it is automatic (no pilot has to trigger it), dependent (it depends on the aircraft's own onboard systems to determine position, rather than a ground radar station measuring the aircraft externally), and it surveils by broadcasting that position outward for anyone equipped to receive it.

In practice, an ADS-B-equipped aircraft periodically transmits a message that includes its identity (usually a registration-linked code and often the flight number), its GPS-derived position, its altitude, and its velocity. It does this whether or not anyone is listening. The aircraft is not asking permission or waiting for a request; it is simply putting its own state out on a radio frequency at regular intervals, several times a second in the case of position, for anything nearby that is tuned to receive it.

This matters for understanding what a tracking map is actually showing you. It is not radar in the classic sense, where a ground station sends out a signal and measures what bounces back. It is the aircraft self-reporting, and the map is only as good as whatever picks that self-report up.

From a receiver to a map: the aggregation step

A broadcast is only useful if something is listening, and this is where ground receivers come in. An ADS-B ground receiver is a relatively simple, inexpensive piece of equipment, often no more elaborate than an antenna and a small radio tuned to the right frequency, that anyone can set up. Community flight-tracking networks are built out of thousands of these receivers, run by individual hobbyists and volunteers rather than by a single company operating its own sensor infrastructure.

Each receiver hears the aircraft broadcasts within its own radio range, decodes them, and forwards what it heard to an aggregation service. That service is where the real work of "tracking" happens: it takes reports arriving from potentially dozens of receivers at once, many of them seeing the same aircraft from slightly different angles and distances, works out which reports belong to which aircraft, and stitches the whole thing into one continuous track. The dot moving smoothly across a map is the output of that aggregation step, not a single unbroken feed from the aircraft to your screen.

This also explains why coverage is a receiver problem before it is anything else. A tracking network cannot see an aircraft in a place with no receiver listening, no matter how strong or clear that aircraft's own broadcast is. The signal has to land on an antenna somewhere, and somebody has to have put that antenna there.

Where this breaks down: land vs ocean

This is the part most explanations of flight tracking skip, and it is the part worth stating plainly rather than glossing over. Community ADS-B coverage is ground-receiver based, which means it is only as good as the density of receivers underneath the flight path.

Near cities, along busy air corridors, and around major hubs, where hobbyists and enthusiasts have set up receivers in large numbers, coverage tends to be dense. A flight approaching a well-covered hub airport, Singapore's Changi among them, is passing over ground that is likely to have several receivers within range at any given moment, so the aircraft's broadcasts get picked up reliably and the map tracks it closely.

Over open ocean and over the more sparsely populated stretches of a long-haul route, there is nowhere to put a ground receiver, so there is nothing to hear the broadcast. This is not a flaw in a particular tracker or a gap that better software could close; it is the physical limit of a system that depends on a ground-based antenna being within radio range. A community ADS-B network's coverage genuinely thins out and can disappear entirely over the middle of an ocean crossing, and any description of "live flight tracking" that does not say this plainly is leaving out the one thing that matters most to someone actually trying to follow a long international flight.

None of this is a claim about any specific tracker's numbers, its uptime, or how often it drops a particular flight. It is a description of how the underlying technology works: ground-receiver ADS-B networks are strong near populated receiver clusters and weak to absent over water and empty terrain, as a matter of physics rather than product quality.

Radar vs ADS-B vs a phone app doing math

It helps to separate three things that get talked about as if they were one thing.

Radar, in the traditional air-traffic-control sense, is government-operated infrastructure. Primary radar sends out a pulse and measures the reflection bouncing off an aircraft's fuselage; secondary radar sends a pulse that the aircraft's own transponder actively answers with an identifying code and altitude. This is the system air traffic controllers use to separate aircraft, and it is not what a consumer flight-tracking map is built on. It is a closed system run by national aviation authorities, not something a hobbyist receiver can tap into.

ADS-B is the broadcast described above: the aircraft self-reporting its GPS-derived state, openly, on frequencies that both official air-traffic systems and independent community receivers can pick up. This is the layer that makes consumer flight tracking possible at all, because unlike classic radar, anyone with the right equipment can legally receive it.

The map itself is neither a sensor nor a radar station. It is a rendering layer sitting on top of the aggregated ADS-B feed, drawing an aircraft icon at the reported coordinates and animating it as new position reports arrive. When people say a tracking app "sees" a flight, what actually happened is: the aircraft broadcast, a receiver somewhere heard it, an aggregation service matched it to the right track, and the app drew a dot at the resulting coordinates. Nothing in that chain is the app doing its own detection.

Understanding this chain is the difference between treating a gap in coverage as a mystery and recognising it for what it is: a stretch of the route with no receiver in range, which resolves itself as soon as the aircraft comes back within reach of one.

What actually shows up on your screen

The dot itself is only the headline. Most tracking maps surface several fields alongside it that come straight out of the same ADS-B broadcast, rather than being calculated separately by the app you're looking at.

• Callsign or flight number. Airlines typically transmit an identifier tied to the flight, which is how a map can label the moving icon "AI131" rather than showing an anonymous dot. This is the same identifier that shows up on an airport departure board, which is why cross-checking a tracker against the airline's own status page for the same flight number is a reasonable way to sanity-check what you're seeing.
• Altitude. Reported in feet, taken from the aircraft's own barometric or GPS-derived altitude reading, and updated at the same interval as position.
• Ground speed and heading. How fast the aircraft is moving over the ground, and which direction it is pointed, both derived from the same navigation systems that feed the position broadcast.
• Aircraft type. Many broadcasts include an identifier that maps to a specific aircraft type, which is how a tracker can show an A320 icon rather than a generic aeroplane silhouette. This detail comes from a lookup against the transmitted identifier, not from anything the tracker observes directly.

None of these fields requires a separate sensor or a separate broadcast. They arrive together, decoded from the same message a ground receiver picked up, which is part of why a good tracking map can update several fields at once rather than the position lagging behind everything else.

Why the picture can look slightly different across two trackers

Open the same flight on two different tracking sites at the same moment and the positions are usually close but rarely pixel-identical. There's a simple reason for this that has nothing to do with either site being wrong: each aggregation network draws on its own set of ground receivers, and if one network's nearest receiver to the aircraft is a few kilometres closer than the other's, the two networks may be working from reports that are a few seconds apart. A few seconds of flight at cruising speed is a real but small difference in plotted position, which is usually the entire explanation for two maps disagreeing slightly rather than either one malfunctioning.

The same logic explains why one map might show a flight a little sooner after takeoff than another, or hold onto a signal a little longer before losing it over water. It comes down to which receivers each network happens to have in range at that exact moment, not a difference in how carefully either one is built.

How TrackMyWings™ helps

TrackMyWings™ is a flight-tracking platform in development, India-first in go-to-market with no region ruled out of scope. A private beta shipped on 2026-08-24, Android only, on the Play internal testing track. Public launch has no fixed date, because it is gated on trade-mark clearance and on the app being good enough to hand to strangers.

Among the planned features is a live map, built around the same ADS-B mechanism described in this guide, and planned aircraft tracking built on the same idea of following a specific aircraft's broadcasts rather than only a scheduled flight number. Both are planned, not shipped.

FAQ

How does live flight tracking actually work?

An aircraft's onboard systems work out its own GPS-derived position, altitude and speed, and broadcast that information via ADS-B. Ground receivers within range pick up the broadcast, an aggregation service stitches together reports from many receivers into one continuous track, and a tracking map draws the resulting position as a moving icon.

Is flight tracking the same thing as radar?

No. Traditional air-traffic radar is government-operated infrastructure that either bounces a signal off the aircraft (primary radar) or interrogates its transponder (secondary radar). Consumer flight tracking runs on ADS-B, a broadcast the aircraft sends out on its own that anyone with a suitable receiver can legally pick up, which is what makes community tracking possible in the first place.

Why does a tracking map sometimes stop showing a flight mid-ocean?

Because community ADS-B coverage depends on ground receivers being within radio range, and there is nowhere to put a receiver in the middle of an ocean. The aircraft keeps broadcasting; there is simply nothing nearby to hear it until the flight comes back within range of a receiver on land. This is a receiver-density limitation, not a fault with the aircraft or a sign anything has gone wrong.

Do I need special equipment to see live flight tracking?

No, as a reader viewing a tracking map or app. The receivers that pick up ADS-B broadcasts are run by the tracking network's own community of hobbyists; you only need a browser or an app to view the resulting map. Setting up your own receiver is possible for enthusiasts but is not required to follow a flight.

Sources

• Wikipedia, "Automatic Dependent Surveillance-Broadcast," https://en.wikipedia.org/wiki/Automatic_dependent_surveillance-broadcast (captured 2026-09-23), used for the ADS-B broadcast mechanism and message content described above.
• Federal Aviation Administration, "Automatic Dependent Surveillance-Broadcast (ADS-B)," https://www.faa.gov/air_traffic/technology/adsb (captured 2026-09-23), used for the primary/secondary radar distinction and the regulatory context around ADS-B.