FANS-1/A Explained: CPDLC, ADS-C and Oceanic Datalink for Pilots

Somewhere over the middle of the North Atlantic, roughly four hours from the nearest radar head, a Boeing 787 changes flight level. No one keys a microphone. No one shouts a position report into a crackling HF frequency. A short block of text appears on the crew's control display unit, the captain presses ACCEPT, and a controller in Gander sees the aircraft's new altitude confirmed automatically a few seconds later. That quiet exchange is FANS-1/A doing its job.

FANS-1/A is one of those acronyms that every long-haul pilot uses daily and very few people outside the flight deck can explain. This guide unpacks what it actually is, how CPDLC and ADS-C differ, why the North Atlantic now effectively requires it, and what the alphabet soup on your flight plan — J5, P2, D1, SUR/RSP180 — really means.

What is FANS-1/A?

FANS stands for Future Air Navigation System. FANS-1/A is a family of products that lets air traffic control see and talk to aircraft in airspace where conventional radar is impractical — oceans, polar regions, deserts and jungle. It is not a single box. It is a chain that runs from the flight crew, through the aircraft's avionics, over satellite or HF links, into ground networks and finally onto a controller's screen.

The name itself is a piece of industry history. FANS-1 was Boeing's implementation; FANS-A was Airbus's. Rather than force convergence, the industry standardised the interoperability instead, and the combined designation FANS-1/A stuck. Both the Airbus A380 and the Boeing 787 are FANS-1/A capable, and the standards describing how the products behave are ARINC 622 and EUROCAE ED-100 / RTCA DO-258.

Functionally, FANS-1/A is made of two applications that are easy to confuse and worth keeping firmly separate in your head:

• CPDLC — Controller–Pilot Data Link Communications. The conversation.
• ADS-C — Automatic Dependent Surveillance – Contract. The surveillance.

CPDLC: text messaging with air traffic control

CPDLC replaces the voice loop with a structured, two-way digital exchange when the aircraft is beyond the reach of VHF. Controllers uplink clearances; crews downlink requests and reports. Crucially, the messages are not free text in normal use — they come from a defined message set, which is exactly what makes them machine-readable at both ends and far less prone to the readback/hearback errors that plague HF voice.

Anyone who has spent a night shift on HF, straining through static to copy a clearance relayed by a third-party radio operator, understands immediately why crews prefer the datalink. The message arrives, it is printed on the screen, it stays there, and both pilots can read it.

CPDLC also carries operational housekeeping. On the North Atlantic, a "Confirm Assigned Route" message was introduced in 2016 to make crews verify the planned oceanic route before entry — a simple, effective trap for the classic wrong-track error. Since 2021, crews logging on to a new oceanic control area can expect the uplink "SET MAX UPLINK DELAY VALUE TO 300 SECONDS."

ADS-C: the contract that reports for you

ADS-C is where most confusion lives, largely because of its near-twin, ADS-B. The difference is in the last letter. ADS-B broadcasts continuously to anyone listening. ADS-C sends data only to specific ground facilities that have negotiated a contract with the aircraft — and the aircraft answers on the terms of that contract.

ADS-C transmits position, altitude, speed, elements of navigational intent and meteorological data. There are three contract types:

• Periodic contract — the ground unit specifies a reporting interval and which optional data groups to include. Optional groups can carry their own modulus, so a group might be attached to, say, every fifth report rather than every one.
• Demand contract — a one-off request for a single report. It does not cancel or alter any other contract in force.
• Event contract — a report triggered when something specific happens. Event types include waypoint change, level range deviation, lateral deviation and vertical rate change. Only one event contract can exist at a time, though it may contain several event types.

A single aircraft can hold multiple simultaneous contracts — typically one periodic and one event contract, supplemented by demand contracts — and up to five separate ground systems can hold contracts with the same aircraft. The ground system can establish contracts without any crew action, provided ADS-C has not been selected off.

There is also an emergency function. An ADS-C emergency report is a periodic report flagged as an emergency, and it can be triggered manually, indirectly (by transmitting a CPDLC position report or selecting an SSR emergency code), or covertly on aircraft that support it. Once triggered, the avionics keep sending emergency reports until the crew deselects the function — which is a detail worth remembering during any post-event tidy-up.

If you enjoy this kind of systems detail, our free aviation tools page is a useful companion for decoding the other data pilots meet every day.

Why the North Atlantic made FANS-1/A non-negotiable

The economics of oceanic airspace come down to one number: separation. The closer aircraft can safely fly, the more of them fit on the efficient tracks and levels. Tighter separation demands better surveillance and faster communication, and that is precisely what FANS-1/A delivers.

The North Atlantic timeline tells the story. Half-track spacing arrived from December 2015 under the reduced lateral separation trial. From December 2017, datalink became mandatory at FL350–390 in the NAT, with exemptions including the Tango routes, airspace north of 80N and surveillance airspace. In 2020 the mandate expanded to require CPDLC and ADS-C between FL290 and FL410 across most of the region, with exemptions including north of 80N, surveillance airspace and New York Oceanic East. In 2023, the northern datalink-exempt area was trimmed back, pulling more of Gander's Greenland sector into the mandate.

One trap worth flagging: since 2022, HF datalink no longer counts as satcom for NAT datalink mandate compliance. You need Inmarsat or Iridium — HF ACARS alone will not do.

PBCS, RCP240 and RSP180 explained

From March 2018, the older reduced-separation trials were replaced by PBCS — Performance Based Communication and Surveillance. The idea is straightforward: instead of asking whether an aircraft has a certain box fitted, ATC asks how quickly and reliably the whole communication and surveillance chain actually performs, end to end.

For the North Atlantic that means three things together: RNP 4 navigation performance, CPDLC capable of RCP240, and ADS-C capable of RSP180. The numbers are transaction times in seconds — a four-minute communication loop and a three-minute surveillance loop respectively.

The reward is tighter spacing. The reduced lateral separation trial that PBCS replaced had already brought 25 NM lateral spacing — those extra daily "half tracks" separated by half a degree of latitude — with reduced longitudinal separation of five minutes in the Shanwick oceanic control area. In 2019, ASEPS took it further, reducing lateral separation to 19 NM for fully compliant aircraft equipped with ADS-B, RNP 4, RCP240 and RSP180.

There is a catch that catches operators out regularly. Plenty of aircraft physically have CPDLC and ADS-C but have never demonstrated RCP or RSP compliance and hold no statement of compliance — several early Boeing aircraft and most Honeywell Primus installations among them. Equipment fitted is not the same as approval held.

Filing it correctly: the flight plan codes

None of this works if the flight plan does not declare it. For NAT High Level Airspace operations:

• Item 10a: J2, J3, J4, J5 and/or J7 for FANS-1/A CPDLC equipment.
• Item 10a: P2 if CPDLC is RCP240 compliant.
• Item 10b: D1 for FANS-1/A ADS-C.
• Item 18: SUR/RSP180 for ADS-C RSP180 compliance.
• Item 18: PBN/L1 for RNP 4.

Operators also need the underlying authorisation. US operators, for example, update their A056 Data Link Communications letter of authorisation, supported by an AFM statement of compliance. Aircraft and crews must both be certified to operate in FANS airspace, with functional testing carried out to RTCA DO-258A / ED-100A and compliance demonstrated against AC 20-140C.

The limits of FANS-1/A

FANS-1/A was designed for oceanic and remote airspace, and it shows. Many of its known deficiencies for high-density airspace were addressed in the later FANS-1/A+ standard, but it has never been fully adopted for continental use — that role went to the ATN-based datalink systems in European and US domestic airspace.

Nor is it a cure-all operationally. Gander removed CPDLC for pre-oceanic route changes in 2025, sending crews back to VHF voice for that specific task after confusion around route uplinks. And by 2026, GNSS jamming and spoofing are treated as a routine North Atlantic risk rather than an exotic one: position may recover after an event, but timing and surveillance performance may not — which is why crews are asked to tell ATC early, usually in the oceanic clearance request.

That is the honest summary. FANS-1/A is not magic; it is a performance chain, and every link — avionics, satcom, ground network, crew procedure — has to hold up for the separation benefits to be real.

Studying this for an exam?

Datalink, ADS-C contract types and PBCS designators turn up regularly in communications and air law question banks, and they are exactly the kind of detail that is easy to half-remember. If you are working towards airline exams, our free ATPL practice questions are a practical way to test whether you really know the difference between an event contract and a demand contract. And if you still fly plenty of sectors where the radio matters more than the datalink, a decent set from the pilot headsets collection remains the single best comfort investment on a long night crossing.

The short version

FANS-1/A is the combination of CPDLC — structured text messaging with ATC — and ADS-C — automatic position reporting under a negotiated contract — that makes modern oceanic flying possible. Boeing called it FANS-1, Airbus called it FANS-A, and the standards behind it are ARINC 622 and ED-100/DO-258. On the North Atlantic it is mandatory between FL290 and FL410 across most of the region, and if you want the tightest tracks and levels you need the performance credentials to go with the equipment: RNP 4, RCP240 and RSP180, correctly filed.

Next time a clearance appears silently on the CDU at 39,000 feet with 2,000 miles of water below, you will know exactly how many links in that chain had to work.