North Atlantic air traffic control still can’t quantify space-based ADS-B use

No public source puts a current number on how much of North Atlantic traffic is separated using space-based ADS-B rather than procedural control. Space-based surveillance has been live since 2019, and reduced-separation minima are implemented — but the displacement itself remains unquantified.

The closest available proxy is equipage: to fly a designated PBCS track, an aircraft needs RNP 4 approval and State sign-off for both RCP 240 and RSP 180, with ADS-B output part of the eligibility mix.

Ask for the share of transatlantic flights now off procedural control, and the public record goes quiet. Not ICAO, not the North Atlantic air navigation providers, not the operator bulletins available in the public record — none publishes a percentage or a flight count that puts the two regimes side by side.

That silence is the interesting part. For decades the corridor ran on pilot-initiated position reports, and separation standards were wide enough to absorb the uncertainty between one report and the next. Without real-time surveillance, traffic volumes over the ocean could not be managed directly; the Organized Track System existed to funnel flights onto fixed tracks rather than preferred routes.

Space-based ADS-B changed that input. In principle, it enables narrower separation and freer routings. In practice, the operational record remains split by route, aircraft and control area, never consolidated into the figure a transatlantic flyer might actually want.

This piece treats the pre-2019 procedural system as the baseline and compares what has measurably changed — reporting frequency, separation minima, equipage thresholds — before naming the metric nobody has published.

What changed: 8 seconds against 14 minutes

Before 2019, controllers tracked North Atlantic aircraft through periodic pilot reports rather than continuous surveillance. Lateral separation sat at 60 NM, and longitudinal separation ran at 10 minutes — roughly 80 NM — because the next reliable position might be a long way off.

Space-based ADS-B delivers position updates roughly every 8 seconds. The old pilot-initiated voice or data-link reports typically arrived every 14 to 30 minutes. That changed input is what makes reduced separation and freer routing possible in principle.

The progression in the current manual is easy to misread. A 19 NM lateral value often appears as the headline, but that is an earlier implementation milestone. The current ICAO NAT Doc 007 puts the smallest PBCS minima in the NAT Region at 15 NM laterally and 14 NM longitudinally, under PANS-ATM procedures.

No row in this table answers the traffic-share question. It compares the two frameworks and shows what is implemented, not how many aircraft or flights now sit on each side.

The equipage gate is defined but unmeasured

Satellite visibility alone does not make an aircraft eligible. The current NAT manual sets three approvals for designated PBCS tracks: RNP 4 navigation performance, plus State authorization for RCP 240 and RSP 180. The 2019 operational bulletin published by the National Business Aviation Association adds an equipment condition: trial eligibility required ADS-B capability, with output on 1090 MHz.

That equipment gate is the closest public proxy for how far the displacement can go. Yet no ICAO or ANSP document reviewed for this piece states what proportion of the transatlantic fleet meets that bar. Displacement is capped by the aircraft an airline flies, not by the satellite coverage above them.

Why the consolidated number doesn’t exist

Part of the reason is definitional. To set random-route traffic against Organized Track System traffic, someone would first have to settle which aircraft count as PBCS-equipped or surveillance-separated, then classify routes from ANSP traffic datasets or NAT Doc 007, then match counts across every NAT oceanic control area — Santa Maria, Bodo, Reykjavik, Shanwick and Gander. No one has published that dataset.

Nothing published since 2021 sets random-route traffic against OTS volume, and no industry-wide yearly figure shows how far procedural-control reliance has fallen across all North Atlantic control areas. Without a common denominator, the transition remains documented in parts but unquantified as a whole.

What this means for a transatlantic flyer

Treat the transition as uneven. Two flights on the same city pair can sit in different control regimes depending on whether the carrier’s aircraft clear the PBCS equipage bar. Where they do, reduced separation and freer trajectories may mean a more direct routing or less time held at a fixed speed or altitude. Where they don’t, the old procedural baseline still applies.

Until a fleet-share or traffic-share figure is published, any claim that the North Atlantic is fully modernized should be treated as unproven. What the evidence supports applies to the North Atlantic alone; Asia-Pacific oceanic airspace has no comparable public verification.

Key terms

PBCS

PBCS stands for Performance-Based Communication and Surveillance, a framework that ties an aircraft’s eligibility for reduced separation to specified communication and surveillance performance. In the North Atlantic, a designated PBCS track is open only to aircraft with RNP 4 approval and State authorization for RCP 240 and RSP 180. Because no public source reports what share of the transatlantic fleet holds those approvals, PBCS eligibility is the closest available proxy for how far the region has moved off procedural control.

RNP 4

RNP 4 is a required navigation performance specification that an aircraft must meet to fly designated tracks in oceanic airspace. The current NAT manual lists it as one of the approvals needed for PBCS-based separation in the North Atlantic. Because it is paired with State-issued RCP 240 and RSP 180 authorization, RNP 4 approval on its own does not unlock reduced separation.

RCP 240

RCP 240 is a required communication performance standard covering how quickly and reliably an aircraft can exchange messages with air traffic control. Aircraft on designated PBCS tracks in the North Atlantic need State authorization for RCP 240, alongside RNP 4 approval and RSP 180 authorization. No public source reports what share of the North Atlantic fleet holds that authorization, so the equipage bar stays defined but unmeasured.

RSP 180

RSP 180 is a required surveillance performance standard covering how often and how accurately an aircraft’s position must be available to controllers. In the North Atlantic it is one of the three approvals — with RNP 4 and RCP 240 — that the current NAT manual requires for designated PBCS tracks. Neither ICAO nor the air navigation service providers reviewed here publish what proportion of the transatlantic fleet meets it.

Organized Track System

The Organized Track System is the North Atlantic’s daily structure of fixed, published routes that aircraft file along rather than flying their preferred trajectories. It predates space-based surveillance, when separation standards were wide enough to absorb the uncertainty between one position report and the next. Because the system fixes routes rather than allowing preferred trajectories, the shift away from it is capped by how many aircraft clear the PBCS equipage bar.

Questions? Answers.