Detailed working notes on ATS data link services, principally Controller-Pilot Data Link Communications (CPDLC), together with ADS-C, D-ATIS, D-VOLMET, and DCL. Covers the service taxonomy, technology substrates (FANS-1/A, ATN B1, ATN B2), RCP/RSP performance framework, EU mandate, and operational domains.

Files in this folder#

• overview.md — what ATS data link is, the service family, and where it sits in the ICAO/ATM framework.
• components.md — building blocks: services, avionics, ground systems, subnetworks, message set, CDA/NDA architecture.
• blocks.md — technology generations as blocks: FANS-1/A, ATN B1 (Link 2000+), ATN B2 (TBO substrate); oceanic vs continental domains.
• threads.md — functional axes: CPDLC service, ADS-C, sub-networks, RCP/RSP performance, ATN/IPS migration, mandates and equipage.
• modules.md — anatomy of one service: continental CPDLC over ATN B1 with RCP 240 worked through end-to-end.
• enablers.md — CNS infrastructure, procedures, avionics certification, training, regulation, institutional arrangements.
• performance_objectives.md — KPA/KPI matrix; capacity, safety, efficiency, interoperability, and predictability framing.
• timeline.md — chronological table from FANS-1/A 1995 to ATN B2/TBO.
• references.md — consolidated ICAO and authoritative external references for everything in this folder.

Reading order#

Start with overview.md, then components.md to understand the full technology stack. Read blocks.md for the generational progression, threads.md for functional axes, then modules.md for the worked example. Use enablers.md and performance_objectives.md as reference material, timeline.md for date context, and references.md for all citations.

Source basis#

Content is grounded in:

• Annex 10 Vol II (Communication Procedures, Seventh Edition, 2016), Chapter 8 — SARPs for data link communications.
• Annex 10 Vol III (Communication Systems, Second Edition, 2007), Chapter 6 — VDL SARPs.
• Doc 4444 (PANS-ATM) Chapters 13, 14, Section 4.15, Appendix 5 — ADS-C and CPDLC procedures and message set.
• Doc 10037 (GOLD Manual, First Edition, 2017) — global operational guidance for DLIC, ADS-C, CPDLC.
• Doc 9869 (PBCS Manual, Second Edition) — RCP and RSP specifications.
• Regulation (EC) No 29/2009 — EU Data Link Services Implementing Rule.

What ATS data link is#

ATS data link is the use of digital message exchange between aircraft and air traffic services units (ATSUs) for air traffic control communications that would otherwise require voice. ICAO defines Controller-Pilot Data Link Communications (CPDLC) in Annex 10 Volume II and PANS-ATM (Doc 4444) as "a means of communication between controller and pilot, using data link for ATC communications."

The term "data link" in the ATS context is not a single technology. It is a generic label for a family of application-layer services sharing a common characteristic: messages are structured, machine-readable, and exchanged over digital subnetworks rather than voice circuits. The services include:

• DLIC — Data Link Initiation Capability (the session establishment handshake, prerequisite for CPDLC and ADS-C).
• CPDLC — the primary clearance and instruction exchange service.
• ADS-C — Automatic Dependent Surveillance-Contract (surveillance reporting under negotiated contracts).
• D-ATIS — digital terminal information service.
• D-VOLMET — meteorological information via data link.
• DCL — Departure Clearance service.

Together these are sometimes called the ATS data link services. The GOLD Manual (Doc 10037) is the ICAO manual that provides globally harmonised operational guidance for DLIC, ADS-C, and CPDLC.

Where data link sits in the ICAO/ATM framework#

Data link sits within the CNS (Communications, Navigation, Surveillance) pillar of the ICAO Global Air Navigation Plan (GANP). In the ASBU framework it corresponds to the COMI (Air-Ground Communications Infrastructure) technology thread. Block 0/B1 captures FANS-1/A and ATN B1 deployment; Block 2 introduces ATN B2 for trajectory-based operations. The datalink services topic is therefore closely coupled to:

• TBO (trajectory-based operations) — ATN B2 is the data link substrate; i4D RTA delivery is the initial operational use case.
• ATFM — CPDLC carries network flow management constraints such as Calculated Take-Off Times (CTOTs) and level restrictions.
• FF-ICE — SWIM-based trajectory exchange in the ground domain, with data link as the air-ground interface for trajectory negotiation.
• ADS-C / PBCS — surveillance performance specifications (RSP 180, RSP 400) underpin the reduced separation minima enabled by CPDLC/ADS-C.

The oceanic/remote vs continental split#

The same CPDLC application-layer service operates in two technically distinct environments:

Oceanic and remote airspace (NAT, APAC, AFI, MID): FANS-1/A over ACARS subnetworks (VHF ACARS, HFDL, SATCOM). The FANS-1/A specification (EUROCAE ED-100A / RTCA DO-258A) covers the application layer. The subnetworks carry ACARS-encoded messages to/from the ATSU's ground ACARS/ATSU system. No VDL Mode 2 coverage is needed. ADS-C is the primary surveillance tool in oceanic airspace.

Continental European airspace (EUR above FL285): ATN B1 over VDL Mode 2. The ATN B1 specification (EUROCAE ED-110B / RTCA DO-280B) defines the context management (CM) and CPDLC applications. The subnetwork is VDL Mode 2, operating at 136.975 MHz (common signalling channel). The EU Data Link Services Implementing Rule (EC 29/2009) makes ATN B1 CPDLC equipage mandatory for operators in the specified airspace.

Both domains: An aircraft travelling from North America across the NAT into Europe may use FANS-1/A for the oceanic crossing and ATN B1 for the continental segment. The FANS-1/A - ATN B1 interoperability standard (EUROCAE ED-154A / RTCA DO-305A) enables automatic CPDLC transfer between the two systems without the flight crew needing to manually switch between them.

Why CPDLC matters operationally#

Three operational arguments drive CPDLC deployment:

1. Frequency congestion relief. In high-density en-route sectors each VHF frequency becomes a bottleneck. Moving routine clearances to data link removes non-urgent exchanges from the voice circuit, leaving it for safety-critical and non-standardisable communications.

2. Error reduction. Structured CPDLC message elements reduce misread-back errors and the risk of callsign confusion; the message set is designed to mirror PANS-ATM phraseology but in a way that eliminates the ambiguity introduced by accent, channel noise, and simultaneous transmissions.

3. Extended reach. In oceanic airspace beyond VHF coverage, CPDLC over HFDL or SATCOM is more reliable than HF voice and enables positive controller contact. Combined with ADS-C it enables the PBCS framework and the reduced lateral/longitudinal separations that depend on communication and surveillance performance.

References#

• Annex 10 Vol II (Aeronautical Telecommunications — Communication Procedures), Chapter 1, §1.8 — ICAO definitions for CPDLC, ADS-C, DLIC, D-ATIS, and logon address.
• Annex 10 Vol II, Chapter 8 — SARPs for aeronautical mobile service data link communications.
• Annex 10 Vol III (Communication Systems), Chapter 6 — VDL SARPs including VDL Mode 2.
• Doc 4444 (PANS-ATM), Chapter 14 — CPDLC procedures; Chapter 13 — ADS-C procedures.
• Doc 10037 (GOLD Manual, First Edition, 2017) — ICAO global operational guidance manual for DLIC, ADS-C, CPDLC.
• Doc 9869 (PBCS Manual, Second Edition) — RCP and RSP specifications framework.
• Regulation (EC) No 29/2009 — EU Data Link Services Implementing Rule (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

The ATS data link service family#

The GOLD Manual (Doc 10037) and PANS-ATM (Doc 4444) define five ATS data link services that together constitute the operational data link capability:

• DLIC — Data Link Initiation Capability.
• CPDLC — Controller-Pilot Data Link Communications.
• ADS-C — Automatic Dependent Surveillance-Contract.
• D-ATIS — Data Link-Automatic Terminal Information Service.
• DCL — Departure Clearance.

D-VOLMET is listed separately in Annex 10 Vol II Chapter 8 Note 1 as a D-FIS (Data Link-Flight Information Service) application alongside D-ATIS.

DLIC#

DLIC is the session establishment service. Before CPDLC or ADS-C can operate, the aircraft and the ATSU must exchange addresses, system names, and version numbers via the AFN (ATS Facilities Notification) for FANS-1/A, or the context management (CM) application for ATN B1. PANS-ATM §4.15 and Annex 10 Vol II §8.1.1 carry the DLIC provisions. Without a successful DLIC logon, the ATSU cannot route CPDLC or ADS-C messages to the correct aircraft.

CPDLC#

CPDLC is the primary ATC communication service. It uses the CPDLC message set (PANS-ATM Appendix 5) to exchange uplink messages (ground to air) and downlink messages (air to ground). A CPDLC message consists of one or more message elements — standardised textual elements such as CLIMB TO LEVEL (level), PROCEED DIRECT TO (waypoint), or REPORT POSITION. Free-text elements are permitted but discouraged for standardisation and automation reasons.

The CDA/NDA concept governs which ground ATSU may issue CPDLC messages:

• CDA (Current Data Authority) — the only ATSU permitted to conduct a CPDLC dialogue with a flight at any given time.
• NDA (Next Data Authority) — the receiving ATSU during a transfer; it may establish an ADS-C contract but must not send CPDLC operational messages until it becomes the CDA.
• Address forwarding — when aircraft transit between ATSU areas, the NDA message and address forwarding sequence transfer CDA status to the next ATSU.

PANS-ATM §14.2 governs CPDLC establishment. §14.3 covers message exchange. §14.3.2 specifies that once a message is sent, the initiator waits for a response within the response time; if none is received, the timer expires and the controller or pilot reverts to alternative communication.

ADS-C#

ADS-C enables ground systems to receive automatic position and intent reports from aircraft by establishing surveillance contracts. Under a periodic contract the aircraft sends reports at a defined interval. Under an event contract (waypoint change, level range deviation, lateral deviation) the aircraft triggers a report when the specified condition is met. Under a demand contract the ground requests an immediate report.

The ADS-C data blocks defined in PANS-ATM §4.11.5 are:

• Basic data block (mandatory): position, time, flight level, speed, heading.
• Ground vector block: track, speed over ground, vertical rate.
• Air vector block: true heading, airspeed, vertical rate.
• Projected profile block: next waypoint, next+1 waypoint.
• Meteorological information block: wind, temperature, turbulence.
• Earth reference block: latitude, longitude, altitude.
• Extended projected profile (EPP): full downstream intended trajectory for intent validation (used in TBO conformance monitoring).

D-ATIS and D-VOLMET#

D-ATIS delivers the Automatic Terminal Information Service message to the cockpit printer or display via data link, allowing pilots to receive current terminal information without occupying the VHF voice frequency. Defined in PANS-ATM Chapter 1 and referenced in Annex 10 Vol II Chapter 8 Note 1.

D-VOLMET delivers meteorological broadcasts (METAR, TAF, SIGMET, AIREP) over data link for en-route use.

DCL#

DCL delivers pre-departure clearances (SID, initial level, squawk, departure frequency) to the cockpit before start-up, reducing congestion on the ATC clearance delivery voice frequency. DCL is carried over ACARS ATS (ED-85A standard) or ATN B1 ground systems. At many airports it has substantially replaced PDC (Pre-Departure Clearance) voice delivery.

End-system avionics#

Data link requires avionics capable of at least one technology pairing:

Aircraft with FANS-1/A - ATN B1 capability can operate in both oceanic (FANS-1/A) and continental (ATN B1) domains without flight-crew manual switching, provided the aircraft complies with the interoperability standard.

Network substrates (subnetworks)#

Data link applications share the same message set regardless of which subnetwork carries them, but the subnetwork determines latency, coverage, cost, and reliability characteristics.

The nested structure from application to radio:

• Application layer: CPDLC / ADS-C / DLIC / D-ATIS / DCL.
• Data link subnetwork layer (transports ACARS or ATN packets):
  • VDL Mode 2 — primary ATN B1 subnetwork; continental VHF coverage.
  • VDL Mode 0/A (legacy ACARS VHF) — primary FANS-1/A VHF subnetwork.
  • HFDL (High Frequency Data Link) — oceanic coverage via HF spectrum.
  • SATCOM (Inmarsat Classic Aero, Iridium Short Burst Data) — global coverage including polar and remote regions.

VDL Mode 2 uses 25 kHz channels in the aeronautical VHF band (117.975 to 137 MHz). The common signalling channel (CSC) is 136.975 MHz globally (Annex 10 Vol III §6.1.2.4). It uses D8PSK modulation and CSMA access.

Ground ATSU system#

The ground side of the data link service comprises:

• ATSU data link server — manages CDA/NDA state, message queuing, timer monitoring, and interface to the controller working position.
• Controller working position (CWP) — the controller's display and input device for CPDLC message composition and acknowledgement; integrated with the radar display or stand-alone CPDLC workstation.
• Communication Service Provider (CSP) — the entity providing the subnetwork transport (VDL ground station network, SATCOM earth station, HFDL ground station). The CSP holds availability contracts against the RCP/RSP specifications.
• ACARS/ATN router / addressing system — routes messages between airborne systems and ATSUs by aircraft address (FANS-1/A uses 24-bit ICAO aircraft address; ATN B1 uses ATN address).

The CPDLC message set#

The PANS-ATM Appendix 5 message set is the normative catalogue of CPDLC message elements. Elements are grouped by operational category:

• Vertical — level assignments, climb/descend, cruise level changes.
• Lateral — direct-to, offset, route modifications, position reports.
• Speed — speed assignments and restrictions.
• Time-based — RTA (Required Time of Arrival) constraint at a fix.
• ADS-C management — periodic contract, event contract, demand contract.
• Emergency and urgency — emergency descent, radio failure protocols.
• Free text — for non-standard requirements not covered by coded elements.

Message attributes determine the response required: WU (WILCO or UNABLE), W/U (WILCO or UNABLE), R (ROGER), NE (not expected), AL (AFFIRM or NEGATIVE). The ground system tracks the response timer per RCP 240 rules.

References#

• Annex 10 Vol II (Aeronautical Telecommunications — Communication Procedures), Chapter 8, §8.1 — DLIC SARPs and data link service provisions.
• Annex 10 Vol II, Chapter 8, §8.2 — CPDLC procedures.
• Annex 10 Vol III (Communication Systems), Chapter 6 — VDL SARPs; VDL Mode 2 CSC 136.975 MHz (§6.1.2.4).
• Doc 4444 (PANS-ATM), Chapter 1 — definitions for CPDLC, ADS-C, DLIC, D-ATIS, DCL.
• Doc 4444, Section 4.15 — DLIC procedures.
• Doc 4444, Chapter 13, §4.11.5 — ADS-C data blocks.
• Doc 4444, Chapter 14 — CPDLC procedures including CDA/NDA concept.
• Doc 4444, Appendix 5 — CPDLC message set with operational categories and response attributes.
• Doc 10037 (GOLD Manual, First Edition, 2017), Chapter 1 and Table 1-1 — data link system overview, technology types, and applicable standards for each avionics class.
• Doc 9869 (PBCS Manual, Second Edition), Chapter 2 — RCP and RSP specifications; Appendix B (RCP 240, RCP 400) and Appendix C (RSP 180, RSP 400).

Technology generations as blocks#

In the ASBU COMI (Air-Ground Communications Infrastructure) thread, data link services progress through three technology generations. These correspond loosely to ASBU Block 0/1 (FANS-1/A and ATN B1 deployment), Block 2 (ATN B2 and satcom expansion), and Block 3 (fully integrated digital communications). The generation structure below maps this progression.

Generation 1 — FANS-1/A (Oceanic and Remote Airspace)#

What it is#

FANS-1/A (Future Air Navigation System — Initial) is the data link standard developed by Boeing and Airbus in the early 1990s, standardised through EUROCAE/RTCA. It implements DLIC (via AFN — ATS Facilities Notification), ADS-C, and CPDLC over ACARS-protocol subnetworks.

The GOLD Manual documents the evolution: the First Edition of the GOLD (then a regional document, 2010) merged the APAC FANS 1/A Operations Manual with the NAT guidance material; the Second Edition (2013) incorporated LINK2000+ guidance; the ICAO First Edition of Doc 10037 (2017) unified them under ICAO authority.

Subnetworks#

FANS-1/A operates over the ACARS network, which comprises:

• VDL Mode 0/A — the original ACARS VHF subnetwork. Legacy modulation (AM-MSK at 2400 bit/s). Widely deployed; lower capacity than Mode 2.
• HFDL — High Frequency Data Link. Provides oceanic and polar coverage where VHF and SATCOM have gaps. Specified in Annex 10 Vol III; RTCA DO-265.
• SATCOM — Inmarsat Classic Aero (ARINC 741) and Iridium Short Burst Data. Global coverage including polar. For FANS-1/A purposes referenced in Doc 10037 Table 1-1 under SATCOM (Inmarsat) and SATCOM (Iridium).

Operational domain#

All oceanic controlled airspace using procedural separation: NAT (HLA), APAC (oceanic FIRs), AFI (oceanic portions), MID (oceanic). Regional SUPPs (Doc 7030) specify where FANS-1/A CPDLC and ADS-C are required or recommended. RCP 240 and RSP 180 are the applicable PBCS specifications for CPDLC and ADS-C respectively in this domain.

Equipage note#

FANS-1/A+ (Revision A of ED-100A / DO-258A) adds a message latency monitor (MLM) that provides automatic alerting when a CPDLC message is unduly delayed. This is a flight-safety enhancement required by some regions. FANS-1/A ADS-C is a subset that implements only AFN and ADS-C, not CPDLC.

Generation 2 — ATN B1 / Link 2000+ (Continental EUR)#

What it is#

ATN B1 (Aeronautical Telecommunication Network Baseline 1) is the European continental data link standard, implementing context management (CM) for DLIC and CPDLC for ATC communications management (ACM), ATC clearance (ACL), and ATC microphone check (AMC). The standard is EUROCAE ED-110B / RTCA DO-280B.

ATN B1 operates over VDL Mode 2 (Annex 10 Vol III Chapter 6), which provides higher bit rates than VDL Mode 0/A and is designed specifically for the ATN environment.

The Link 2000+ deployment#

LINK2000+ was the EUROCONTROL programme that deployed ATN B1 CPDLC across the European core area. By approximately 2015, ATN B1 ground systems were operational in 32 EUR FIRs and UIRs above FL285. The programme established the VDL Mode 2 ground network and the ATN B1 ATSU systems. The GOLD Manual Appendix B (EUR procedures) governs continental CPDLC operations.

The EU mandate#

Regulation (EC) No 29/2009 (DLS IR) mandated implementation of ATN B1 CPDLC services and avionics equipage for operators flying in the specified European airspace above FL285. The DLS IR requires aircraft operators to carry ATN B1-compliant data link avionics and to include J1 in Item 10a of the flight plan when operating in the mandate area.

Interoperability — FANS-1/A to ATN B1#

An aircraft on a transatlantic crossing may use FANS-1/A for the NAT oceanic segment, then transition to ATN B1 on entering EUR continental airspace. The interoperability standard EUROCAE ED-154A / RTCA DO-305A enables automatic CPDLC transfer so that the flight crew does not manually switch systems. Aircraft that do not comply with ED-154A implement FANS-1/A and ATN B1 as separate systems and require manual procedures.

Generation 3 — ATN B2 and Beyond (TBO Substrate)#

What it is#

ATN B2 is the data link generation supporting Trajectory-Based Operations (TBO) under ASBU Block 2 (from 2025) and Block 3 (from 2031). It extends ATN B1 to add:

• RTA (Required Time of Arrival) message delivery to the FMS for i4D (initial 4D) operations — already in the PANS-ATM Appendix 5 message set.
• Extended Projected Profile (EPP) downlink from ADS-C for trajectory conformance monitoring.
• Higher-capacity data link to support trajectory negotiation message flows for FF-ICE / FICE ASBU module exchanges.

ATN/IPS (ATN using Internet Protocol Suite) is the network evolution underpinning ATN B2. Doc 9880 (ATN/OSI) and the ATN/IPS work referenced in Annex 10 Vol II (Amendment 94, 2 April 2025) provide the network layer for SWIM-aligned information services.

Satcom expansion#

For oceanic and remote airspace, satellite communication services continue to evolve. Iris (European Space Agency / Inmarsat L-band service) is being evaluated for SESAR ATN B2 operations. Space-based ADS-B (Aireon / Spire) is a parallel advancement that provides global ADS-B (not ADS-C) surveillance, complementing PBCS-governed ADS-C in oceanic airspace.

Future technologies (horizon)#

• LDACS (L-band Digital Aeronautical Communications System) — a candidate for future continental data link, providing higher capacity than VDL Mode 2 and supporting ATN/IPS directly. Under standardisation in ICAO and ETSI.
• AeroMACS — WiMAX-based airport surface data link for airport surface operations; separate from en-route data link.

Summary: block/generation matrix#

References#

• Annex 10 Vol II (Communication Procedures), Chapter 8, §8.1 — DLIC and data link service SARPs.
• Annex 10 Vol III (Communication Systems), Chapter 6 — VDL SARPs; VDL Mode 2.
• Doc 10037 (GOLD Manual, First Edition, 2017), Introduction — evolution of FANS-1/A, NAT, and LINK2000+ guidance into ICAO Doc 10037.
• Doc 10037, Table 1-1 — data link technology types and applicable standards (FANS-1/A, ATN B1, FANS-1/A ADS-C, ACARS ATS, interoperability standards).
• Doc 10037, Appendix B — European continental (ATN B1 CPDLC) procedures; DLS IR equipage and flight plan requirements.
• Doc 9869 (PBCS Manual, Second Edition), §2.2.1.12-2.2.1.14 — RCP 240 and RCP 400 specifications; §2.4.1.9-2.4.1.11 — RSP 180 and RSP 400 specifications.
• Regulation (EC) No 29/2009 — DLS IR; ATN B1 mandate (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

Six functional axes cut across the data link topic. Each axis is a thread in the sense that it spans the generational progression and has its own set of capabilities, standards, performance requirements, and stakeholder responsibilities.

Thread 1 — CPDLC Service#

The primary ATC communication service. Covers the message set, dialogue management (CDA/NDA), establishment procedures, timer management, and failure protocols.

Key provisions#

PANS-ATM Chapter 14 carries the CPDLC procedures. The chapter covers establishment (§14.2), exchange of operational messages (§14.3), and management of CPDLC failures (within Chapter 14 and Chapter 15). Annex 10 Vol II Chapter 8, §8.2 carries the parallel SARPs.

The CPDLC message set (PANS-ATM Appendix 5) is the normative catalogue. Messages are grouped as uplink (UM) and downlink (DM) elements. Key message categories:

• UM0-UM169 uplink messages (ground to air): level, lateral, speed, time, surveillance, information, emergency.
• DM0-DM67 downlink messages (air to ground): responses, position reports, requests, weather deviation, emergency.

Response attributes govern how the dialogue progresses:

• WILCO/UNABLE (WU) — most clearance messages.
• ROGER (R) — information messages.
• NE (not expected) — advisory or notification.
• AFFIRM/NEGATIVE (AN) — specific questions.

The RTA uplink message element (UM155 and variants) carries Required Time of Arrival constraints at named waypoints — the operational mechanism for i4D under ASBU TBO-B2. This is already in the message set (PANS-ATM Appendix 5).

Dialogue management#

The CDA/NDA concept ensures that only one ATSU at a time conducts CPDLC dialogue with a flight. The transferring ATSU sends an NDA message designating the next ATSU; the aircraft acknowledges. Address forwarding passes the aircraft's addressing information to the new CDA. An ATSU that is not the CDA may establish ADS-C contracts (to set up surveillance ahead of accepting the flight) but must not send operational CPDLC clearances.

Thread 2 — ADS-C Surveillance#

ADS-C provides the ground with automated aircraft position and intent data under surveillance contracts. It is the primary surveillance means in oceanic airspace where radar and ADS-B coverage is absent.

Contract types#

• Periodic contract — aircraft reports at a defined time interval (e.g. every 14 minutes in standard NAT operations; can be reduced with PBCS approval).
• Event contract — aircraft reports when a specified event occurs: waypoint change, level range deviation, lateral deviation, speed change.
• Demand contract — single immediate report requested by the ATSU.

Data blocks (PANS-ATM §4.11.5)#

The basic data block is mandatory in every report. Optional blocks (ground vector, air vector, projected profile, met block, EPP) are requested by the ATSU in the contract terms. The extended projected profile (EPP) provides the aircraft's full intended downstream trajectory and is the enabler for TBO conformance monitoring in ASBU Block 2.

PBCS applicability#

RSP 180 governs ADS-C performance for normal surveillance in procedurally separated airspace. RSP 400 applies for satellite voice (SATVOICE) or emerging surveillance. The RSP specification defines the maximum surveillance data delivery time (180 seconds for RSP 180), continuity, availability, and integrity. Post-implementation monitoring of actual surveillance performance (ASP) is required per Doc 9869.

Thread 3 — Sub-network Layer (VDL, HFDL, SATCOM)#

The three subnetworks each occupy a distinct role in the operational data link ecosystem.

VDL Mode 2#

The continental subnetwork for ATN B1. Operates at D8PSK, 31.5 kbit/s effective data rate, CSMA access, 25 kHz channel spacing. The global common signalling channel is 136.975 MHz. VDL Mode 2 SARPs are in Annex 10 Vol III Chapter 6. Ground station infrastructure requires careful frequency planning to avoid adjacent-channel interference with voice operations.

VDL Mode 0/A (ACARS VHF)#

The legacy ACARS VHF subnetwork. Operates at 2400 bit/s on ACARS management unit frequencies (129.125, 136.900 MHz and others). Wide fleet penetration. Shared with AOC (Airline Operational Communications) traffic, so capacity is shared between ATS and non-ATS users.

HFDL#

High Frequency Data Link. Provides coverage in oceanic and polar regions beyond VHF range. 1800 bit/s effective rate. 14 ground stations provide global HFDL coverage. Annex 10 Vol III specifies HFDL SARPs; RTCA DO-265 is the MASPS. Used as primary or alternate subnetwork in NAT HLA where VHF ACARS is out of range.

SATCOM (Inmarsat Classic Aero / Iridium SBD)#

Inmarsat Classic Aero (ARINC 741 / RTCA DO-270) provides L-band satcom over geostationary satellites — global except polar. Iridium Short Burst Data (SBD) extends to polar regions via LEO constellation. Doc 10037 Table 1-1 lists both. SATCOM is used as primary or backup in NAT/APAC oceanic airspace and is the only option for some remote continental and polar routes.

Thread 4 — RCP/RSP Performance and PBCS#

The Performance-based Communication and Surveillance (PBCS) framework specifies how communication and surveillance performance is defined, qualified, and monitored. It decouples the performance requirement from any specific technology.

RCP specification structure (Doc 9869)#

An RCP specification defines:

• Transaction time — the maximum time from initiator action to end-of-transaction (e.g. RCP 240 = 240 seconds).
• Continuity — probability of completing a transaction given that it started (0.999 for RCP 240).
• Availability — proportion of time the service is operational (0.999 for safety; 0.9999 for efficiency for RCP 240).
• Integrity — probability of malfunction (less than 10^-5 per flight hour for RCP 240).

RCP 240 allocations#

The 240-second budget is allocated:

• Controller composition time.
• System uplink transit time (ACTP — actual communication transaction performance, the CSP-controlled element).
• Flight crew response/acknowledgement time.
• Downlink transit time.
• System display time.

The CSP is contractually responsible for the ACTP allocation. ANSP holds the ground system elements. PBCS monitoring tracks ACTP against contract obligations and triggers corrective action if performance degrades.

RSP 180 and 400#

RSP 180 covers standard ADS-C performance. RSP 400 applies for satellite voice as alternative surveillance. The RSP specification follows the same structure as RCP: delivery time, continuity, availability, integrity. RSP 180 maximum surveillance data delivery time is 180 seconds.

Thread 5 — ATN/IPS Migration#

The ATN is migrating from OSI-based protocols (ATN/OSI, specified in Doc 9880) toward Internet Protocol Suite (ATN/IPS, specified in a separate manual referenced in Annex 10 Vol II). ATN/IPS uses IPv6 as the network layer, aligning the aeronautical network with internet standards and enabling SWIM-compatible information exchange.

Annex 10 Vol II Amendment 94 (2 April 2025 applicability) addressed ATN/IPS updates. The PANS-IM (Doc 10199) complements Annex 10 by providing network access provisions for SWIM environment information services over ATN/IPS.

ATN B2 is predicated on ATN/IPS as the network layer. The migration from ATN/OSI to ATN/IPS is a long-term enabler tracked under ASBU COMI-B2 and COMS-B1 (surface/ground communications thread).

Thread 6 — Mandates and Equipage#

State and regional mandates drive equipage rates. Without regulatory pressure, voluntary equipage of data link avionics is commercially rational only if the operational benefits (separation credit, workload reduction) outweigh the certification and installation cost.

EU DLS IR (EC 29/2009)#

Mandates ATN B1 CPDLC above FL285 in EUR airspace for aircraft with a maximum take-off mass greater than 45 500 kg or maximum certificated passenger seating capacity of more than 80. ATN B1 avionics (ED-110B / DO-280B) and flight plan indicator J1 are required.

Monitoring of compliance is by EUROCONTROL Network Manager and national CAAs. Doc 9869 Section 6.1 describes the monitoring obligations for ANSPs under the DLS IR.

NAT PBCS requirement#

The NAT System Planning Group moved toward mandatory PBCS (RCP 240/RSP 180) for NAT HLA operations, phased by year. Operators without FANS-1/A CPDLC/ADS-C compliant to PBCS standards face operational restrictions (e.g. 10-minute rather than 5-minute longitudinal minima).

APAC implementation#

The APAC regional plan (APAC Seamless ATM Plan, tracked by APANPIRG) has progressively mandated FANS-1/A CPDLC and ADS-C for oceanic operations, and promotes ATN B1 deployment for continental segments in high-traffic corridors. Doc 7030 APAC SUPPs specify the airspace and equipage requirements.

Cross-thread dependencies#

• CPDLC (Thread 1) depends on DLIC (part of Thread 1) and on a functioning subnetwork (Thread 3).
• ADS-C (Thread 2) depends on DLIC and on SATCOM or HFDL in oceanic domains (Thread 3).
• PBCS monitoring (Thread 4) requires post-implementation data from both Thread 1 (CPDLC ACTP data) and Thread 2 (ASP data).
• ATN B2 (Thread 5) depends on ATN/IPS ground network maturity and on new avionics that support the extended message set.
• Mandate compliance (Thread 6) drives the equipage penetration that makes the reduced separations enabled by Thread 4 operationally worthwhile.

References#

• Annex 10 Vol II (Communication Procedures), Chapter 8, §8.2 — CPDLC SARPs; CDA/NDA concept; DLIC provisions.
• Annex 10 Vol III (Communication Systems), Chapter 6 — VDL Mode 2 SARPs.
• Doc 4444 (PANS-ATM), Chapter 13 — ADS-C procedures including contract types and data blocks.
• Doc 4444, Chapter 14 — CPDLC procedures; establishment; operational message exchange.
• Doc 4444, Appendix 5 — CPDLC message set; RTA uplink elements for i4D.
• Doc 10037 (GOLD Manual, First Edition, 2017), Table 1-1 — data link system types and standards.
• Doc 9869 (PBCS Manual, Second Edition), Chapter 2, §2.2.1.12-2.2.1.14 — RCP 240 and RCP 400 specifications; §2.4.1.9-2.4.1.11 — RSP 180 and RSP 400.
• Doc 9869, Chapter 6, §6.1 — ANSP monitoring obligations under EC 29/2009 in EUR.
• Regulation (EC) No 29/2009 — DLS IR mandate (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

The unit of analysis: one service, one domain, one technology#

The equivalent of an "ASBU module" for data link is a specific application service operating in a defined airspace with a defined technology. This file uses continental CPDLC over ATN B1 (Link 2000+) as the primary worked example, because it is the most fully mandated and monitored instance globally. A shorter secondary example covers oceanic CPDLC and ADS-C over FANS-1/A in the NAT domain.

Worked Example 1 — Continental CPDLC over ATN B1 (EUR)#

Service identifier#

ATN B1 CPDLC services: ACM (ATC Communications Management), ACL (ATC Clearance), AMC (ATC Microphone Check). Applicable airspace: EUR FIRs and UIRs above FL285 under EC Regulation No 29/2009 (DLS IR).

What changes operationally#

A controller who previously transmitted "LUFTHANSA 456, CLIMB AND MAINTAIN FL 390, DUE TO TRAFFIC" over VHF now sends a structured CPDLC uplink (UM20: CLIMB TO AND MAINTAIN FL390). The aircraft CPDLC display shows the message; the flight crew presses WILCO. The system records the acknowledgement time and computes the transaction duration. The VHF frequency is free for safety-critical exchanges and non-standard situations.

For the ACM service, CPDLC replaces the routine "contact Munich control 133.65" call with a structured ACM message containing the next sector frequency. The flight crew acknowledges; the next sector expects the aircraft to make contact on the received frequency.

Performance requirement: RCP 240#

The applicable performance specification is RCP 240 (Doc 9869 §2.2.1.12): maximum communication transaction time of 240 seconds. The budget covers:

• Controller time to compose and send: allocated controller CWP display time plus input time (human factor element).
• Uplink transit time (ACTP — the CSP/network element): the dominant variable; monitored per VDL Mode 2 ground station area.
• Flight crew response time: WILCO input on CPDLC display.
• Downlink acknowledgement transit time.
• Ground system display of WILCO.

Under VDL Mode 2 in nominal conditions, ACTP for an uplink is typically in the range of 2-10 seconds, leaving most of the 240-second budget for the human factors components. The RCP 240 budget is not tight in practice except when the VDL Mode 2 subnetwork is congested or when the aircraft is at the edge of VDL coverage.

Technology stack#

• Aircraft avionics: ATN B1 compliant (ED-110B / DO-280B); ATCSS (Air Traffic Control Software System) includes CM and CPDLC applications; VHF data radio capable of VDL Mode 2 modulation.
• Subnetwork: VDL Mode 2; ground station network operated by EUROCONTROL VDL Service Provider (VSP) or national ATN VDL network.
• ATSU ground system: ATN B1 ATSU data link server providing CDA/NDA management, CPDLC message routing, and controller working position integration.
• Communication Service Provider (CSP): holds contractual RCP 240 availability obligations; provides ACTP monitoring data to the ANSP.

Procedures: establishment#

Before entering the ATN B1 CPDLC area (typically at a defined fix or when crossing a specific flight level), the aircraft automatically initiates a DLIC logon via the CM application, identifying itself to the downstream ATSU. The ATSU accepts the logon and establishes a CM session. CPDLC is available once the aircraft enters the ATSU's area of responsibility and the ATSU has accepted the CM logon.

On transfer, the transferring ATSU (CDA) sends a CPDLC NDA message to the aircraft identifying the next ATSU's ATN address. The aircraft acknowledges. The transferring ATSU forwards the aircraft's address to the receiving ATSU. The receiving ATSU sends a CM contact and becomes the CDA. The transition is automatic for FANS-1/A - ATN B1 equipped aircraft (ED-154A); others require manual re-logon.

Procedures: failure#

If the CPDLC system or VDL subnetwork fails, the controller reverts to VHF voice using the standard phraseologies in PANS-ATM §12.3.6 and Annex 10 Vol II §8.2.12. Voice readback of CPDLC messages is not normally required (PANS-ATM §4.5.7.5.2.1). Upon CPDLC failure, controllers must announce "ALL STATIONS CPDLC FAILURE" and provide relevant instructions; when restored, "ALL STATIONS RESUME NORMAL CPDLC OPERATIONS."

Enablers required#

• ATN B1 avionics installed and certificated (EASA CS-ACNS or equivalent).
• Aircraft operator obtains operational approval for CPDLC operations.
• J1 included in flight plan Item 10a.
• Controller trained and assessed on CPDLC procedures, failure protocols, and CDA/NDA concepts.
• VDL Mode 2 ground station coverage in the airspace.
• ANSP PBCS monitoring programme active (per EC 29/2009 requirements).

KPIs#

• ACTP (actual communication transaction performance): measured per ground station area; target derived from RCP 240 ACTP allocation.
• Percentage of CPDLC transactions completed within 240 seconds.
• VDL coverage percentage in the mandate area.
• Equipage rate of aircraft operators (percentage of operations by DLS-compliant aircraft).
• Voice transmission count on the sector frequency (proxy for workload reduction benefit).

Worked Example 2 — Oceanic CPDLC and ADS-C over FANS-1/A (NAT)#

Service identifier#

FANS-1/A CPDLC and ADS-C in North Atlantic HLA (High Level Airspace), above FL285, PBCS applicable: RCP 240 for CPDLC, RSP 180 for ADS-C.

What changes operationally#

Without CPDLC, a NAT controller issues level clearances by voice HF to each aircraft individually, and receives position reports the same way. HF voice is affected by radio propagation, accents, and simultaneous transmissions.

With FANS-1/A CPDLC, the controller sends structured uplink messages (level changes, route modifications, speed assignments) and receives confirmations via downlink. The exchange is recorded and timestamped. Communication quality is independent of HF propagation conditions.

With ADS-C periodic contracts at intervals appropriate to the separation minima applied, the controller's system receives automatic position and intent data. Combined with RCP 240/RSP 180, this enables 5 NM longitudinal separation where the legacy without-PBCS minimum was 10 or 15 NM, increasing the capacity of the oceanic track system.

Transaction and ADS-C monitoring#

For FANS-1/A the SATCOM or HFDL subnetwork introduces higher and more variable latency than VDL Mode 2. RCP 240 still applies, but the ACTP allocation must account for satellite propagation delay and ground station uplink scheduling. Post-implementation monitoring of ACTP is performed per Doc 9869 and the regional PBCS monitoring programme.

Procedures: EPP and conformance#

The extended projected profile (EPP) ADS-C block provides the aircraft's intended downstream trajectory. Ground systems compare the EPP against the cleared route. Lateral deviation event contracts trigger an automatic downlink report if the aircraft deviates more than a defined lateral distance (typically 25 NM or less). The controller receives an alert and initiates investigation via CPDLC or voice.

Synthesis: what these examples share#

Both examples follow the same pattern:

1. Session — DLIC logon establishes the aircraft-ATSU session.
2. Dialogue — CPDLC dialogue under CDA governance; structured message elements; mandatory response with timer.
3. Surveillance — ADS-C contracts (oceanic) or radar/ADS-B (continental) for position verification.
4. Performance — RCP 240 / RSP 180 specifications prescribe the end-to-end performance; post-implementation monitoring provides assurance.
5. Fallback — VHF or HF voice; mandatory phraseologies defined.

References#

• Annex 10 Vol II (Communication Procedures), Chapter 8, §8.2 — CPDLC procedures for establishment, message exchange, and failure management.
• Doc 4444 (PANS-ATM), Chapter 14, §14.2 — CPDLC establishment; §14.3 — exchange of operational messages.
• Doc 4444, Chapter 13, §4.11.5 — ADS-C data blocks including EPP.
• Doc 4444, §4.5.7.5.2.1 — voice readback of CPDLC not required.
• Doc 4444, §12.3.6 — CPDLC failure and restoration phraseologies.
• Doc 4444, Appendix 5 — CPDLC message set; RTA uplink elements.
• Doc 10037 (GOLD Manual, First Edition, 2017), Appendix B — EUR continental ATN B1 procedures; Appendix A — FANS-1/A and ATN B1 message element catalogues.
• Doc 9869 (PBCS Manual, Second Edition), §2.2.1.12-2.2.1.14 — RCP 240 specification and ACTP allocation; §2.4.1.9-2.4.1.11 — RSP 180; Chapter 4 — compliance determination and monitoring.
• Regulation (EC) No 29/2009 — DLS IR equipage and monitoring obligations (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

What must be in place before data link can operate#

Data link services require a dense set of infrastructure, regulatory, certification, procedural, and training prerequisites. Missing any one element can prevent an aircraft from using data link services or an ANSP from offering them, even if all other components are in place.

CNS infrastructure enablers#

Ground subnetwork coverage#

VDL Mode 2 (ATN B1 continental): Continuous VDL Mode 2 coverage is required throughout the mandate area. Annex 10 Vol III Chapter 6 specifies VDL Mode 2 SARPs. EUROCONTROL's VDL Service Providers (VSPs) operate the ground station networks in EUR. Coverage gaps at the edges of coverage areas can cause CPDLC message retransmission and ACTP degradation. New ground stations require frequency coordination per Annex 10 Vol III §6.2.4 adjacent-channel power limits.

ACARS VHF / HFDL (FANS-1/A oceanic): The ACARS network is operated by SITA and ARINC (now Collins Aerospace). HFDL is operated by ARINC Datalink. Both provide global-scale coverage; no new ground infrastructure is required for most new state deployments — operators connect as network participants.

SATCOM: Inmarsat and Iridium are commercial satellite networks. ANSPs and operators pay service contracts. Continuity of service is contractual, not state-owned. The CSP is accountable for the ACTP component of RCP 240 compliance.

ATSU data link ground system#

Each ATSU providing CPDLC must have:

• A data link server managing CDA/NDA state and message routing.
• Integration with the flight data processing system (FDPS) for flight plan correlation with logon requests.
• Integration with the controller working position (CWP) for CPDLC display and input.
• Logging and replay capability for incident investigation and PBCS monitoring data extraction.

The DLS IR (EC 29/2009) requires ANSPs to implement compliant ATN B1 ground systems and to maintain PBCS monitoring programmes.

ATN/IPS network backbone (future)#

ATN B2 requires ATN/IPS ground connectivity between ATSUs (replacing or supplementing ATN/OSI). The PANS-IM (Doc 10199) and the ATN/IPS manual provide the network layer specifications. IPv6 connectivity between ATSUs is a ground infrastructure prerequisite for B2.

Avionics and certification enablers#

FANS-1/A avionics (oceanic/remote)#

Aircraft operators must install FANS-1/A avionics that comply with EUROCAE ED-100A / RTCA DO-258A (or FANS-1/A+, adding the message latency monitor per ED-100A Revision A). Installation requires:

• STC (Supplemental Type Certificate) or equivalent from the certifying authority (FAA, EASA, or State of design authority).
• Aircraft maintenance manual update.
• Flight crew operating manual supplement.
• Operational approval from the State of operator.

ATN B1 avionics (continental EUR)#

Aircraft operators flying in the EUR DLS IR mandate area must carry ATN B1-compliant avionics (ED-110B / DO-280B). EASA CS-ACNS (Airborne Communications, Navigation and Surveillance) Certification Specifications provide the certification basis. The ETSI EN 303 214 community specification for the DLS System Community Specification is the industry implementation standard.

Interoperability (FANS-1/A - ATN B1)#

Aircraft needing seamless operation in both domains require compliance with EUROCAE ED-154A / RTCA DO-305A (FANS-1/A - ATN B1 interoperability standard) to benefit from automatic CPDLC transfer. Without it, the aircraft uses manual re-logon procedures on transition.

Procedures and regulatory enablers#

PANS-ATM provisions#

PANS-ATM (Doc 4444) Chapter 14 (CPDLC) and Chapter 13 (ADS-C) carry the procedural provisions that must be implemented by ATSUs and aircraft operators. These include establishment procedures (§14.2), message exchange rules (§14.3), failure protocols, and ADS-C contract management. Section 4.15 covers DLIC (Data Link Initiation Capability).

Regional SUPPs (Doc 7030)#

ICAO Regional Supplementary Procedures specify, for each region:

• Which airspace requires FANS-1/A CPDLC and/or ADS-C.
• The equipage standard required (FANS-1/A, FANS-1/A+, ATN B1).
• The RCP and RSP specifications prescribed (Doc 9869 Appendix B/C tables reference the regional prescription as examples).
• Operational approvals required by operators.

National Aeronautical Information Publications (AIPs)#

PANS-ATM §14.2 requires that information on when and where data link communications shall be established be published in the AIP. ATSUs must also publish their CPDLC logon addresses (PANS-ATM §14.2.1). This is a frequently missed enabler: an aircraft may have data link avionics but be unable to logon if the ATSU logon address is not published or is incorrect.

Operational approvals#

Aircraft operators must obtain operational approval for data link operations from their State of operator (or EASA for EU operators). Approval involves:

• Avionics certification evidence.
• Flight crew training records.
• Operational procedures (Flight Operations Manual supplement).
• PBCS compliance evidence for CPDLC/ADS-C operations (aircraft qualification per Doc 9869 Chapter 4).

Training enablers#

Controller training#

Controllers must be trained in:

• CPDLC establishment and logon management.
• CDA/NDA transfer procedures.
• Message composition and response handling.
• Timer management and expiry procedures.
• CPDLC failure detection and recovery (phraseologies per PANS-ATM §12.3.6 and Annex 10 Vol II).
• Interaction between CPDLC and ADS-C in oceanic environments.
• Interpretation of PBCS alerts from the monitoring system.

Initial licensing endorsement or unit endorsement is typically required. Recurrent training scenarios should include data link system failures and degraded-mode procedures.

Flight crew training#

Flight crew must understand:

• CPDLC logon procedures (automatic and manual).
• Message display, acknowledgement, and response options (WILCO, UNABLE, STANDBY, ROGER).
• CDA/NDA — knowing which ATSU is the CDA and when NDA messages appear.
• Response timer and operational requirements.
• Emergency and urgency procedures over CPDLC.
• Fall-back to voice and re-logon procedures.

Training organisations must include data link operations in type-rating and difference training for relevant aircraft types.

Institutional and organisational enablers#

Communication Service Provider (CSP) contracts#

ANSPs must contract with CSPs for the subnetwork (VDL ground station operation, Inmarsat, HFDL). The CSP is contractually responsible for the ACTP component of RCP 240. SLAs must specify ACTP targets, availability, and reporting obligations consistent with the PBCS monitoring programme.

PBCS monitoring programme#

Doc 9869 Chapter 3 and the regional PBCS guidance require that ANSPs maintain a PBCS monitoring programme collecting ACTP data from CPDLC transactions and ASP data from ADS-C reports. The programme must:

• Identify degradations in ACTP or ASP.
• Trigger investigation and corrective action when thresholds are exceeded.
• Report to the relevant regional authority (e.g. EUROCONTROL, the regional monitoring entity in NAT/APAC).

ANSPs without an active PBCS monitoring programme cannot lawfully apply the reduced separation minima that depend on RCP 240 / RSP 180.

Letters of Agreement (LOAs)#

Adjacent ATSUs must have LOAs governing the data link transfer procedures: NDA designation timing, address forwarding, CPDLC acceptance in the overlap area, and what to do when data link is not available between the two ATSUs. These are routine for European and NAT ANSPs but require establishment before a new ATSU pair initiates data link-based transfers.

References#

• Annex 10 Vol II (Communication Procedures), Chapter 8 — DLIC, CPDLC, and ADS-C SARPs.
• Annex 10 Vol III (Communication Systems), Chapter 6 — VDL Mode 2 SARPs including adjacent-channel power limits.
• Doc 4444 (PANS-ATM), Chapter 14, §14.2.1 — AIP publication of data link establishment information.
• Doc 4444, §12.3.6 — CPDLC failure and restoration phraseologies.
• Doc 10037 (GOLD Manual, First Edition, 2017), Chapter 3 — CPDLC operational procedures; Appendix B and regional procedures.
• Doc 9869 (PBCS Manual, Second Edition), Chapter 3 — applying an RCP/RSP specification; Chapter 4 — compliance, operational approvals, monitoring programmes.
• Regulation (EC) No 29/2009 — DLS IR institutional requirements for ANSPs and operators (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

The performance lens for data link#

Data link services are themselves a performance enabler for ATM — their value is measured by what they allow the ATM system to do better. The PBCS framework (Doc 9869) provides the technical performance specifications (RCP, RSP). The ASBU performance framework (KPAs, KPIs, Performance Objectives) provides the operational performance framing.

The performance chain is:

RCP/RSP specification  --enables--> Separation minima reduction
Separation minima      --delivers-> Capacity, efficiency KPAs
CPDLC workload reduction --delivers-> Capacity, safety KPAs
Accurate surveillance  --delivers-> Safety, predictability KPAs

Key Performance Areas (KPAs) addressed#

Data link services contribute primarily to five KPAs from the Doc 9854 / Doc 9883 set of eleven:

KPA contribution by technology generation#

The matrix below scores each KPA by principal benefit horizon across the three data link technology generations. 1 = some benefit, 2 = clear benefit, 3 = primary driver.

Capacity is the primary benefit throughout all generations, driven by frequency congestion relief and, in oceanic domains, by the reduced separations enabled by PBCS. ATN B2 adds capacity benefits from TBO trajectory synchronisation.

Safety receives a primary driver score in G3 because ATN B2 conformance monitoring (EPP/ADS-C in TBO operations) catches trajectory deviations earlier and with higher certainty than voice-only or periodic- only surveillance.

RCP/RSP specifications as performance requirements#

Doc 9869 defines the numeric performance requirements for data link in procedurally separated airspace. These are operational requirements, not aspirational targets.

These specifications are prescriptive in airspace where they are required for the application of specific separation minima (e.g. 5 NM longitudinal in NAT HLA requires both RCP 240 and RSP 180).

Performance Objectives#

PO-1: Reduce radiotelephony workload in high-density en-route sectors#

Measured by voice transmission count per sector per hour, CPDLC message utilisation rate (percentage of eligible transactions conducted via CPDLC), and controller-assessed workload (SASHA or similar tool). Delivered by ATN B1 CPDLC (Link 2000+ service) in continental EUR and by FANS-1/A CPDLC in oceanic domains.

PO-2: Enable reduced longitudinal separation in oceanic airspace#

PBCS-enabled separation reduction from 10 NM to 5 NM (or equivalent time-based reduction) in oceanic airspace. Measured by percentage of oceanic flights applying 5 NM separation, oceanic track system capacity, and ATFM restrictions imposed due to capacity constraints.

Requires: FANS-1/A CPDLC compliant to RCP 240 and ADS-C compliant to RSP 180; active PBCS monitoring programme; CSP contracts meeting ACTP requirements.

PO-3: Improve surveillance in oceanic/remote airspace#

Replace compulsory voice position reports with ADS-C automatic reporting. Measured by percentage of compulsory reporting points with automated ADS-C coverage, reduction in procedural position report voice calls, and conformance monitoring coverage (percentage of flights with active ADS-C periodic contracts).

PO-4: Support trajectory-based operations (ATN B2)#

Deliver RTA constraints to aircraft FMS via CPDLC (i4D) for ASBU TBO-B2 operations. Measured by percentage of metered flights receiving RTA via CPDLC rather than voice, RTA adherence rate, and vertical/lateral profile efficiency for i4D-managed flights.

Requires: ATN B2-capable avionics; FMS with RTA execution capability; ground CPDLC system able to generate and monitor RTA messages; PBCS performance maintained.

PO-5: Ensure global interoperability (FANS-1/A to ATN B1)#

Seamless CPDLC service delivery across oceanic/continental boundaries. Measured by percentage of transatlantic flights achieving automatic CPDLC transfer (ED-154A compliant) without manual re-logon, and pilot-reported incidents of CPDLC transfer failure on regional boundary crossing.

Key Performance Indicators (KPIs)#

Capacity KPIs#

• CPDLC utilisation rate (percentage of eligible ATC clearances sent via CPDLC rather than voice).
• Voice transmission count per sector per hour on primary frequency.
• Number of simultaneous CPDLC dialogues per controller.

Safety KPIs#

• Rate of CPDLC read-back errors or wrong-aircraft message events.
• CPDLC message misrouting events per million transactions.
• Data link failure rate per flight hour.
• Controller alert rate from CPDLC latency monitor (message latency monitor / LTM in EUR).

PBCS compliance KPIs#

• ACTP (actual communication transaction performance) per ground station area: percentage of CPDLC transactions meeting RCP 240 ACTP allocation.
• ASP (actual surveillance performance) per ADS-C contract period: percentage of reports delivered within RSP 180 surveillance data delivery time.
• VDL Mode 2 coverage percentage in mandate area.
• CSP availability rate per RCP 240 availability specification.

Fleet equipage KPIs#

• Percentage of IFR aircraft operations in mandate area by CPDLC-equipped aircraft (equipage rate).
• Number of exemptions granted under the DLS IR (EUR).
• FANS-1/A+ equipage rate in NAT HLA.

Environment / efficiency KPIs (G3 horizon)#

• Percentage of metered flights receiving RTA via CPDLC (i4D enablement).
• Track-mile efficiency of i4D-managed versus voice-managed flights.

How performance is reported#

• EUR: EUROCONTROL monitors DLS IR compliance. ANSPs report PBCS monitoring data to EUROCONTROL Network Manager and national regulators. EUROCONTROL publishes annual Link 2000+ deployment and performance statistics.
• NAT: The NAT SPG (Systems Planning Group) and regional monitoring entity track PBCS (RCP 240/RSP 180) compliance per operator and per centre.
• APAC: APANPIRG performance monitoring; individual FIR ATC monitoring agencies.
• Global: ICAO ASBU implementation monitoring reports (COMI thread metrics).

References#

• Doc 9854 (Global ATM Operational Concept) — eleven KPAs used throughout ASBU performance framework.
• Doc 9869 (PBCS Manual, Second Edition), Chapter 2, §2.2.1.12-2.2.1.14 — RCP 240 and RCP 400 specifications with numeric values; §2.4.1.9-2.4.1.11 — RSP 180 and RSP 400 specifications.
• Doc 9869, Chapter 3 — applying an RCP/RSP specification; prescribing communication and surveillance capability.
• Doc 10037 (GOLD Manual, First Edition, 2017), Chapter 2 — operational requirements for data link services including RCP/RSP performance framing.
• Regulation (EC) No 29/2009, Article 4 and Annex II — ANSP monitoring obligations for DLS IR compliance (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

Key dates and milestones#

The table below is the authoritative chronology. All dates are verified against primary sources. Programme milestones (Link 2000+, GOLD editions) verified against Doc 10037 and Doc 9869 preambles; EU regulation date from EC 29/2009 text; ICAO document editions from title pages.

How to read this timeline#

Two parallel timelines run through data link history:

1. Standards timeline — ICAO Annex/PANS amendments, GOLD editions, PBCS manual editions. These set the normative baseline.
2. Operational deployment timeline — regional milestones (Link 2000+, NAT PBCS mandate, APAC data link expansion). These are regional decisions driven by the standards but not automatically global.

The two timelines can diverge: PANS-ATM contained CPDLC procedures from 2001, but full operational deployment of CPDLC in continental Europe did not reach critical mass until 2013-2017 under the Link 2000+ programme and DLS IR mandate.

The EU DLS IR mandate timeline#

The EU mandate created a distinct regional sub-timeline:

GOLD Manual edition history#

References#

• Annex 10 Vol II (Communication Procedures), Seventh Edition, 2016 — amendment history table in preliminary pages.
• Annex 10 Vol III (Communication Systems), Second Edition, 2007 — amendment history table.
• Doc 4444 (PANS-ATM) — amendment history table in preliminary pages.
• Doc 10037 (GOLD Manual, First Edition, 2017), Introduction — evolution of GOLD document from regional manuals.
• Doc 9869 (PBCS Manual, Second Edition), Introduction — history of RCP concept development and PBCS framework.
• Regulation (EC) No 29/2009, 16 January 2009 — DLS IR adoption date (authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029).

Primary ICAO documents#

• Annex 10 to the Convention on International Civil Aviation, Volume II — Communication Procedures, Seventh Edition, July 2016. Chapter 1, §1.8: ICAO definitions for CPDLC, ADS-C, DLIC, D-ATIS, and logon address. Chapter 8: SARPs for aeronautical mobile service data link communications, CPDLC procedures, DLIC, and D-ATIS/D-VOLMET.

• Annex 10, Volume III — Communication Systems, Second Edition, July 2007. Chapter 6: VHF Digital Link (VDL) SARPs, including VDL Mode 2 channel spacing, modulation, CSMA access, common signalling channel 136.975 MHz.

• Doc 4444 — Procedures for Air Navigation Services: Air Traffic Management (PANS-ATM). Chapter 14: CPDLC procedures (establishment, message exchange, failure management, phraseologies). Chapter 13: ADS-C procedures and contract types. Section 4.15: DLIC procedures. Appendix 5: CPDLC message set including RTA uplink elements.

• Doc 10037 — Global Operational Data Link (GOLD) Manual, First Edition, 2017. ICAO's operational guidance document for DLIC, ADS-C, and CPDLC. Harmonises APAC FANS-1/A, NAT, and EUR LINK2000+ guidance. Table 1-1: data link system types, standards, and CSP/aircraft equipment requirements. Appendix A: FANS-1/A and ATN B1 message element catalogues. Appendix B: European continental (ATN B1) procedures; DLS IR equipage and flight plan requirements.

• Doc 9869 — Performance-based Communication and Surveillance (PBCS) Manual, Second Edition. Normative framework for RCP and RSP specifications. Chapter 2: RCP 240, RCP 400, RSP 180, RSP 400 specifications with numeric transaction times, continuity, availability, and integrity values. Chapter 3: Applying an RCP/RSP specification. Chapter 4: Compliance, operational approvals, monitoring programmes. Appendix B: RCP specifications. Appendix C: RSP specifications. Section 6: EUR post-implementation monitoring aligned with EC 29/2009.

• Doc 9694 — Manual of Air Traffic Services Data Link Applications. Additional CPDLC guidance; cited in PANS-ATM §5.4.2.6.2.2 note. (Authoritative source — not in local library; see https://store.icao.int/.)

• Doc 9880 — Manual on Detailed Technical Specifications for the ATN using ISO/OSI Standards and Protocols. ATN/OSI technical specifications; ATSMHS application; cross-referenced in Annex 10 Vol II §4.6. (Authoritative source — not in local library; see https://store.icao.int/.)

• Doc 9854 — Global Air Traffic Management Operational Concept. Source of the eleven KPAs. The conceptual basis for ATM performance measurement applied to data link.

• Doc 7030 — Regional Supplementary Procedures. Region-specific equipage requirements and airspace designations for CPDLC and ADS-C.

Industry interoperability standards#

• EUROCAE ED-100A / RTCA DO-258A — FANS-1/A (Generic) interoperability standard; the baseline for oceanic/remote CPDLC and ADS-C.
• EUROCAE ED-110B / RTCA DO-280B — ATN B1 interoperability standard; the baseline for continental EUR CPDLC.
• EUROCAE ED-154A / RTCA DO-305A — FANS-1/A - ATN B1 interoperability standard; enables automatic CPDLC transfer between domains.
• RTCA DO-290 / EUROCAE ED-120 — Continental Safety and Performance Requirements (SPR) standard; performance basis for DLS IR monitoring.
• (Authoritative sources — not in ICAO local library; available from EUROCAE and RTCA.)

Regulatory documents (non-ICAO)#

• Regulation (EC) No 29/2009 of 16 January 2009 (EU Data Link Services Implementing Rule, DLS IR). Mandates ATN B1 CPDLC in EUR airspace above FL285 for qualifying operators. Sets monitoring obligations for ANSPs. (Authoritative source — not in local library; see https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029.)

Live / authoritative sources#

• ICAO OPLINKP page — https://www.icao.int/safety/acp/oplink/Pages/default.aspx — governance of GOLD Manual and PBCS.
• ICAO store — Doc 10037 (GOLD) — https://store.icao.int/en/global-operational-data-link-gold-manual-doc-10037
• ICAO store — Doc 9869 (PBCS) — https://store.icao.int/en/performance-based-communication-and-surveillance-pbcs-manual-doc-9869
• EU DLS IR (EC 29/2009) — https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32009R0029
• EUROCONTROL LINK2000+ — https://www.eurocontrol.int/concept/link2000plus
• SESAR 3 JU — https://www.sesarju.eu/ (ATN B2 / TBO data link R&D)