ADS-B coverage gap characterisation over polar routes
Ground radar and VHF radio fade out above roughly 78°N. Space-based ADS-B receivers on Iridium NEXT and Spire LEMUR-2 satellites now quantify exactly where surveillance gaps remain, and by how much, informing ICAO performance-based requirements for polar route approval.
Sensors
- Aireon (Iridium NEXT hosted payload): 66 cross-linked LEO satellites at 780 km altitude, each carrying a hosted ADS-B receiver. Provides global, including full polar, coverage. Published validation with NAV CANADA and ENAV demonstrated message reception rates above 99% for 1090 MHz Extended Squitter at high latitudes under nominal traffic conditions, with position update intervals of approximately 8 seconds for aircraft transmitting at 6.2 Hz.
- Spire LEMUR-2 ADS-B: Constellation of over 100 small LEO satellites carrying 1090 MHz ADS-B receivers alongside GNSS-RO and AIS payloads. Polar coverage is strong given the natural convergence of LEO orbital planes at high latitudes. Latency to data delivery is typically a few minutes via ground station downlink, making it suitable for post-hoc gap analysis rather than real-time separation assurance.
- 1090 MHz Extended Squitter (1090ES) signal standard: The ICAO-mandated broadcast format for ADS-B Out. Aircraft transmit position, velocity, identity and intent at up to 6.2 Hz. Signal range in free space is sufficient for LEO reception, but fruit (simultaneous transmissions from multiple aircraft) and multipath can degrade message decode rates in dense airspace. At polar latitudes, traffic density is low enough that fruit is rarely the limiting factor.
- Ground-based VHF and SSR (baseline comparison): Secondary Surveillance Radar and VHF radio cover roughly up to 78°N from Icelandic, Norwegian and Canadian stations. Beyond that, coverage is absent. This documented gap is the reference against which space-based reception statistics are measured; it is not a sensor for this use case but the gap being characterised.
Why the Arctic is a surveillance black hole
Ground-based Secondary Surveillance Radar has a practical range of around 450 km. VHF radio, used for controller-pilot voice, follows a similar horizon. North of roughly 78°N, there are no radar stations, and the geometry of the Earth means there never will be economically viable ones. Aircraft flying transpolar routes between North America, Europe and Asia spend hours in airspace where controllers have no real-time position data. They rely instead on procedural separation: fixed Mach number assignments, large lateral offsets, and position reports over HF radio at mandatory waypoints every 10 to 14 minutes.
That procedural system works, but it is conservative by necessity. The separation standards applied in non-surveillance airspace are substantially larger than those used under radar or ADS-B coverage, which limits the number of aircraft that can be accommodated on the most fuel-efficient tracks. As polar traffic has grown, particularly on Asia-to-North America city pairs, the capacity constraint has become commercially significant.
What a LEO constellation does that a ground station cannot
A satellite in low Earth orbit at 780 km altitude sees a ground footprint of roughly 4,500 km diameter. At polar latitudes, the orbital planes of a LEO constellation converge, meaning a given point near the pole is overflown by more satellites per unit time than a point at the equator. This is a geometric accident that happens to be exactly what polar surveillance needs.
Iridium NEXT exploits this directly. Its 66 satellites are distributed across six orbital planes inclined at 86.4°, giving continuous coverage of both poles. Each satellite carries an Aireon ADS-B hosted payload that listens on 1090 MHz. Because the satellites are cross-linked, a message received over the Arctic can be routed to a ground station without waiting for the receiving satellite to pass over land, reducing latency. Aireon published validation results jointly with NAV CANADA and ENAV showing that, for aircraft equipped with compliant ADS-B Out transponders, position reception rates exceeded 99% across the North Atlantic and Arctic test corridors. The update interval achieved was consistent with the 8-second figure that underpins ICAO's RCP 240 performance-based communication standard.
Spire's LEMUR-2 constellation takes a different architecture: smaller satellites, no cross-links, data stored and downlinked when a ground station is in view. Latency is higher, typically several minutes, which means Spire ADS-B data is better suited to gap mapping, traffic analysis and post-flight validation than to live separation assurance.
Turning reception statistics into a coverage gap map
A coverage gap characterisation is not simply a question of whether a satellite was in view. It requires computing, for every point in the polar airspace and every moment in a representative time window, the probability that at least one space-based receiver would have decoded a compliant ADS-B transmission from an aircraft at that location and altitude. That probability is a function of satellite geometry, signal propagation, receiver sensitivity, and the fruit environment from nearby aircraft.
The standard approach uses historical constellation ephemeris data combined with link-budget calculations anchored to published receiver sensitivity figures. For Aireon, the hosted payload specifications and the NAV CANADA validation dataset provide the empirical grounding. The output is a grid, typically at 0.5° or 1° resolution over the polar cap, showing minimum, mean and worst-case reception probability across a 24-hour or 30-day window. Gaps are defined against a threshold, commonly the 99% reception probability required under ICAO's RCP 240 standard.
One honest caveat: the analysis assumes aircraft are equipped with compliant ADS-B Out transponders transmitting at the required power and update rate. Older aircraft on polar routes may carry non-compliant or degraded equipment. Space-based reception statistics cannot distinguish a genuine coverage gap from a non-transmitting aircraft, so ground-truth cross-referencing with flight plan data is necessary for rigorous gap attribution.
ICAO performance-based requirements and what gap maps feed into
ICAO's Performance-Based Communication and Surveillance (PBCS) framework, documented in Doc 9869, defines Required Communication Performance (RCP) and Required Surveillance Performance (RSP) specifications. RSP 180 requires that 95% of position reports are received within 180 seconds; RSP 400 relaxes this to 400 seconds. Polar route approval under reduced separation minima depends on demonstrating that the surveillance infrastructure, including space-based ADS-B, meets the applicable RSP specification along the proposed route.
A gap characterisation study produces the evidence base for that demonstration. It identifies route segments where RSP compliance is marginal, quantifies the probability of extended non-reception events, and flags whether additional procedural mitigations are needed. NAV CANADA used Aireon data to support the introduction of reduced separation on North Atlantic tracks, moving from 50 nautical mile lateral separation to 14 nautical miles on routes where space-based ADS-B coverage was validated. The fuel savings across the North Atlantic traffic flow from denser, more optimal routing are substantial, though the precise figures vary by season and traffic mix.
Limits worth stating plainly
Space-based ADS-B is only as good as the transponders it listens to. Aircraft that are not yet ADS-B Out equipped, or whose equipment is malfunctioning, are invisible regardless of how many satellites are in view. The mandate for ADS-B Out on aircraft operating in certain airspace classes has been phased in across ICAO member states at different rates, so polar traffic today is a mixed population.
Message decode rate is not the same as position accuracy. ADS-B position quality depends on the GNSS receiver in the aircraft; a satellite receiver with poor geometry or interference at high latitudes can produce positions with horizontal uncertainty of several nautical miles even when the message is successfully received from space. The RSP framework accounts for this by specifying total system error budgets, not just reception probability, but analysts must be careful not to conflate link availability with navigation accuracy.
Finally, the Antarctic poses a harder problem than the Arctic. Traffic density is very low, validation datasets are sparse, and the few aircraft operating there (research support flights, occasional tourist overflights) may not carry current-generation transponders. Gap characterisation over the Antarctic is methodologically identical but empirically less well validated.
What an analysis engagement looks like
A typical gap characterisation study for a new polar route or an airspace redesign proposal starts with defining the geographic corridor and the traffic population. Constellation ephemeris data for the relevant period is combined with link-budget modelling to produce reception probability grids. These are cross-referenced against actual received message counts from Aireon or Spire archives to validate the model against reality. The output is a set of GIS layers showing RSP-compliant and non-compliant zones, a statistical summary of worst-case gap durations, and a written assessment against the applicable ICAO standard.
Satellize can structure this analysis for civil aviation authorities or route operators who need an independent, non-operator view of coverage performance. The methodology draws on the same published Aireon validation work and ICAO PBCS documentation that regulators already accept.
If you are assessing a specific polar route for RSP compliance, the concrete next step is to define the corridor boundaries and the time window you need analysed, so that the reception probability computation can be scoped accurately.
Typical figures
| Signal frequency | 1090 MHz (1090ES ADS-B Out, ICAO Annex 10 standard) |
| Satellite altitude (Aireon/Iridium NEXT) | 780 km |
| Ground footprint per satellite | Approximately 4,500 km diameter at 780 km altitude |
| Position update interval (Aireon, compliant aircraft) | Approximately 8 seconds (aircraft transmitting at 6.2 Hz) |
| Published reception rate (Aireon, NAV CANADA/ENAV validation) | Greater than 99% for compliant ADS-B Out transponders on North Atlantic and Arctic corridors |
| Latency to data availability (Aireon, cross-linked) | Seconds to low single-digit minutes via cross-linked architecture |
| Latency to data availability (Spire LEMUR-2) | Typically 2 to 10 minutes depending on ground station contact |
| Coverage | Global including both poles; no geometric exclusion zones |
| Gap map spatial resolution (analysis output) | Typically 0.5° to 1° grid over polar cap |
| ICAO RSP threshold for reduced separation | RSP 180 (95% of reports within 180 s) or RSP 400 depending on separation standard |
Analytics Satellize can run
| Polar corridor reception probability grid | Link-budget modelling using published satellite ephemeris and receiver sensitivity, validated against archived message counts | GIS layer (GeoTIFF or GeoJSON) showing mean and worst-case reception probability at 0.5° resolution over the defined corridor |
| RSP compliance zone map | Thresholding reception probability grid against ICAO RSP 180 or RSP 400 specifications from Doc 9869 | Annotated GIS layer distinguishing compliant, marginal and non-compliant zones, with summary statistics per route segment |
| Worst-case gap duration analysis | Monte Carlo simulation over constellation geometry and traffic population, drawing on published Aireon orbital parameters | Statistical report giving 95th-percentile gap duration by corridor segment, formatted for submission to a civil aviation authority |
| Historical traffic validation cross-check | Comparison of modelled reception probability against actual received message counts from Aireon or Spire archives for a specified historical period | Validation report quantifying model-to-reality deviation, with identified anomalies flagged for transponder compliance review |
| Seasonal coverage variation assessment | Repeat gap analysis across summer and winter traffic seasons to capture variation in traffic mix and transponder equipage | Multi-season comparison report with worst-case season identified and mitigation options assessed |
| Non-equipped aircraft exposure estimate | Cross-referencing flight plan data with received ADS-B message counts to estimate the fraction of polar traffic not visible to space-based receivers | Briefing document quantifying residual surveillance blind fraction, with equipage trend data where available from published ICAO monitoring reports |
Who does the work
We can get this done for you. Satellize runs its own analyst desk and a strong science team. You do not buy a data feed and work out what it means; our people source the imagery, run the analysis described on this page, and hand you the answer with its confidence limits stated. Discuss this requirement.