FAA DDLS Technical Overview Of Program 2026-12-08.pdf
PDF 6 MB Posted
- Solicitation number
- 693KA8-26-R-DDLSID
About this file
Technical Overview of the Current Data Comm Program
This document is a technical briefing prepared by the Federal Aviation Administration dated December 8, 2026, providing a comprehensive overview of the Domestic Controller Pilot Data Link Communications (CPDLC) program. The presentation details the program's development from its inception in September 2006 through current operational status, including key milestones, implementation achievements, network architecture, and performance metrics. Tower Services (Departure Clearance) achieved operational capability at 65 airports by December 2016, delivered 29 months ahead of schedule and $71.84 million under budget. En Route Initial Services have been deployed to 20 operational centers with an Initial Operational Capability achieved in November 2019. Full Services deployment was restructured in August 2022 into three increments based on training requirements and avionics compatibility, with Increment 1 operational at 20 centers and Increment 2 operational at 6 centers as of the briefing date, while Increment 3 remains deferred due to avionics issues.
The Data Communications Integrated Services (DCIS) Contract, awarded in September 2012, provides air-to-ground network service through two Commercial Service Providers utilizing VHF VDL Mode 2 protocol and satellite communications. The contract, currently in year 15 with an end date of September 30, 2029, includes a 7-year base period and ten 1-year options. Key network requirements include nationwide coverage for surface and en route operations across 20 Air Route Traffic Control Centers, with performance standards specifying 99.99 percent Reliability, Maintainability, and Availability (RMA) for most en route coverage and latency requirements for uplink and downlink messages. Current operational performance demonstrates a national average uplink success rate of 99.39 percent over a 14-day moving average, with approximately 3.7 million successful controller-initiated uplinks recorded over a recent 28-day period. The briefing identifies opportunities for performance improvement in specific geographic areas, including Salt Lake City arrivals and international arrivals within Boston Air Route Traffic Control Center airspace involving satellite-to-VDL-2 handoff procedures. The program maintains engagement with extensive industry stakeholders through the Data Communications Implementation Team (DCIT), which has convened multiple times annually since January 2011 and includes participation from airlines, aircraft manufacturers, avionics providers, Communication Service Providers, labor unions, trade associations, and standards organizations.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Federal Aviation Administration
Technical Overview of the Current Data Comm
Program
December 8, 2026
2Federal Aviation
Topics
• Current Status of the Program
– Key Milestones of the Domestic CPDLC Program
– Current Implementation Status
• Tower Services (DCL)
• En Route Services (CPDLC)
• About the DCIS Contract
• Protocol, Architecture, and Infrastructure
• Use and Performance of Domestic CPDLC
• Examples of Problems Encountered
• CPDLC Stakeholders and Industry Engagement
3Federal Aviation
Current Status of the Program
4Federal Aviation
Key Milestones of the Program
• 09/2006: Program starts investigating alternatives for restarting Domestic Data Comm
• 07/2008: Program gets authority to start the preliminary planning for a selected alternative
• 05/2012: Agency commits funding for Tower Services (Departure Clearance)
• 09/2012: Data Communications Integrated Services (DCIS) Contract is Awarded
• 10/2014: Agency commits funding for the initial set of En Route CPDLC messages (Initial
Services)
• 08/2016: Agency commits funding to the remaining set of En Route CPDLC messages (Full
Services)
• 08/2022: Strategy Update: En Route Full Services deployment is broken into 3 increments:
– Increment 1: messages involving less extensive training,
– Increment 2: messages requiring classroom training,
– Increment 3: deferred messages requiring avionics fixes
5Federal Aviation
Status S1P1 Implementation
Site Name Site
ID
ARTCC
ID
IOC Site Name Site
ID
ARTCC
ID
IOC Site Name Site
ID
ARTCC
ID
IOC Site Name Site
ID
ARTCC
ID
IOC
Boise (Non-CPDLC) BOI ZLC 06/10/15 New Orleans MSY ZHU 01/21/16 Louisville SDF ZID 02/10/16 Newark EWR ZNY 02/12/16 KS1: Salt Lake City SLC ZLC 08/07/15 Austin AUS ZHU 02/04/16 Indianopolis IND ZID 03/07/16 J F Kennedy JFK ZNY 02/25/16 KS2: Houston Intcl IAH ZHU 09/03/15 San Antonio SAT ZHU 02/19/16 Memphis MEM ZME 03/25/16 La Guardia LGA ZNY 03/14/16 KS3: Houston Hobby HOU ZHU 09/10/15 Los Angeles LAX ZLA 03/10/16 Nashville BNA ZME 04/13/16 Teterboro TEB ZNY 03/24/16 NAP-NAP Intgr Compl N/A ZLC/ZTL 09/30/15 Las Vegas LAS ZLA 03/25/16 Adams Field (Non-CPDLC) LIT ZME 04/17/16 Westchester HPN ZNY 04/12/16
San Diego SAN ZLA 04/07/16 Denver DEN ZDV 05/03/16 Philadelphia PHL ZNY 04/22/16 John Wayne SNA ZLA 04/25/16 Atlanta ATL ZTL 05/19/16 Boston BOS ZBW 05/13/16 Burbank BUR ZLA 05/06/16 Charlotte CLT ZTL 06/02/16 Providence (Non-CPDLC) PVD ZBW 05/13/16 Ontario ONT ZLA 05/18/16 Greensboro (Non-CPDLC) GSO ZTL 06/07/16 Bradley BDL ZBW 06/10/16 San Francisco SFO ZOA 06/08/16 Orlando MCO ZJX 06/30/16 Albany (Non-CPDLC) ALB ZBW 06/15/16 Oakland OAK ZOA 06/23/16 Miami MIA ZMA 07/29/16 Detroit DTW ZOB 06/30/16 San Jose SJC ZOA 07/06/16 Ft Lauderdale FLL ZMA 08/12/16 Cleveland CLE ZOB 07/13/16 Sacramento SMF ZOA 07/20/16 Tampa TPA ZMA 08/29/16 Pittsburgh PIT ZOB 07/29/16 Phoenix PHX ZAB 08/10/16 St Louis STL ZKC 09/29/16 Baltimore/Washington BWI ZDC 08/16/16 El Paso (Non-CPDLC) ELP ZAB 08/29/16 Kansas City MCI ZKC 10/11/16 Washington Dulles IAD ZDC 08/30/16 Portland PDX ZSE 09/14/16 Tulsa (Non-CPDLC) TUL ZKC 10/17/16 Washington Reagan DCA ZDC 09/14/16 Seattle SEA ZSE 09/15/16 Minneapolis St Paul MSP ZMP 11/03/16 Chicaco Midway MDW ZAU 10/19/16 Albuquerque ABQ ZAB 09/21/16 Eppley Field (Non-CPDLC) OMA ZMP 11/09/16 Chicaco O'Hare ORD ZAU 10/28/16 Dallas Love DAL ZFW 10/10/16 San Juan SJU ZMA 12/09/16 Raleigh/Durham RDU ZDC 11/02/16 Dallas Ft Worth DFW ZFW 10/18/16 Columbus CMH ZID 04/10/18 Milwaukee MKE ZAU 12/08/16 Will Rogers (Non-CPDLC) OKC ZFW 10/24/16 Fort Meyers (New TDLS) RSW ZMA 04/25/18 Andrews ADW ZDC 11/08/17 Honolulu (Non-CPDLC) HNL 12/06/16 Charleston (New TDLS) CHS ZJX 05/09/18 Buffalo BUF ZOB 05/21/18 Anchorage (Non-CPDLC) ANC 12/12/16 Cincinnati CVG ZID 11/16/21
Operational Reno RNO ZOA 02/20/18 Jacksonville JAX ZJX 02/17/22 Operational (PDC Only) Van Nuys (New TDLS) VNY ZLA 08/21/18 Palm Peach PBI ZMA 07/18/22
Key Sites Group A Group B Group C
TDLS Sites Color Key
Acquisition Program Baseline (APB) Milestones APB Date Actual Date
ERAM Preliminary Design Review (PDR) September 2011 September 2011
ERAM Critical Design Review (CDR) March 2012 March 2012
FID: Final Investment Decision for ERAM & TDLS May 2012 May 2012
DCIS Contract Award July 2012 September 2012
TDLS Preliminary Design Review (PDR) December 2012 October 2012
TDLS Critical Design Review (CDR) August 2013 July 2013
ERAM Initial Test Release (ITR) June 2014 April 2014
Operational Test (OT&E) November 2015 March 2015
First-Site Initial Operational Capability (IOC) March 2016 August 2015
In-Service Decision (ISD) December 2016 December 2015
Operational Readiness Decisions (ORD) April 2017 September 2015
Last-Site IOC May 2019 December 2016
Delivered CPDLC to 55 airports 29 months ahead of schedule and $71.84M million under budget
• Used some underrun to deliver CPDLC to an additional 7 airports (62 total)
• Used some underrun to upgrade air to ground RF services at 10 airports with enhanced availability / redundancy
• After completion of the baseline including all the added scope the program still returned $17.8M
• Received additional funding to deploy at 3 more airports after baseline concluded
65 Operational Airports
DJT/
6Federal Aviation
Status S1P2 Initial Services
20 Operational Centers
APB Milestone APB Date Actual Date
ERAM Data Comm Contract Definitization March 2015 March 2015
Contractor Detailed Design Complete December 2016 May 2016
Order DCNS Network Service Volume for Keysite December 2017 April 2017
Development Test and Evaluation Complete June 2018 September 2017
First-Site Initial Operational Capability (IOC)* July 2019* November 2019
In-Service Decision (ISD) March 2020 January 2020
Last-Site IOC** February 2021** May 2025
* The First-Site IOC date was changed from July 2019 to March 2020 due to the government shutdown ** The Last-Site IOC date was changed from February 2021 to September 2021 due to the government shutdown.
Key Uplink Messages Supported FANS MSG ID Category FANS Message Element
UM19
Altitudes
MAINTAIN [altitude] UM20 CLIMB TO AND MAINTAIN [altitude] UM23 DESCEND TO AND MAINTAIN [altitude] UM36 EXPEDITE CLIMB TO [altitude] UM37 EXPEDITE DESCENT TO [altitude] UM38 IMMEDIATELY CLIMB TO [altitude] UM39 IMMEDIATELY DESCEND TO [altitude]
UM49
Crossing Restrictions
CROSS [position] AT AND MAINTAIN [altitude] UM55 CROSS [position] AT [speed] UM56 CROSS [position] AT OR LESS THAN [speed] UM57 CROSS [position] AT OR GREATER THAN [speed] UM61 CROSS [position] AT AND MAINTAIN [altitude] AT [speed]
UM74
Route Clearances
PROCEED DIRECT TO [position] UM79 CLEARED TO [position] VIA [route clearance] UM80 CLEARED [route clearance] UM83 AT [position] CLEARED [route clearance]
UM117 Comm Mgmt CONTACT [icao unit name][frequency] UM120 MONITOR [icao unit name][frequency] *same sector frequency change only* UM135 Report CONFIRM ASSIGNED ALTITUDE
Shaded are currently turned off or used in a limited setting
Multiple government shutdowns and COVID-19 had a substantial impact on facility training activities and consequently the deployment. Declaration of IOC was substantially delayed due to performance issues.
7Federal Aviation
Status S1P2 Full Services Milestone Baseline Date Actual Date
ERAM Data Comm Contract Modification June 2017 June 2017 Contractor Detailed Design Complete December 2018 November 2017 Contractor Software Development Complete – Transition to Contractor Test
December 2019 October 2019
Development Test and Evaluation Complete November 2020 November 2020 Training Development Complete November 2021 November 2023 First-Site Initial Operating Capability (IOC)* March 2022* November 2025 Last-Site IOC* December 2023* Likely Winter ’28
* The First-Site and Last-Site IOC dates have been delayed to COVID-19 and multiple government shutdowns.
Increment 2 8 Operational Centers – 7 IOC
FANS MSG ID Category FANS Message Element
UM75
Route Clearances
WHEN ABLE PROCEED DIRECT TO [position] UM77 AT [position] PROCEED DIRECT TO [position] UM78 AT [altitude] PROCEED DIRECT TO [position] UM82 CLEARED TO DEVIATE UP TO [distance offset] [direction] OF ROUTE
UM91
Holding HOLD AT [position] MAINTAIN [altitude] INBOUND TRACK [degrees] [direction] TURNS [leg type]
UM92 HOLD AT [position] AS PUBLISHED MAINTAIN [altitude] UM93 EXPECT FURTHER CLEARANCE AT [time]
UM127 Report REPORT BACK ON ROUTE UM169 Advisories [Full Services Advisory Free Text] [or] [free text]
Increment 1 – Operational at 20 Centers Increment 2 – Operational at 6 Centers
No IOC required
Key Uplink Messages Supported
FANS MSG ID Category FANS Message Element
UM30
Block Altitudes
MAINTAIN BLOCK [altitude] TO [altitude] UM31 CLIMB TO AND MAINTAIN BLOCK [altitude] TO [altitude] UM32 DESCEND TO AND MAINTAIN BLOCK [altitude] TO [altitude]
UM106
Speeds
MAINTAIN [speed] UM108 MAINTAIN [speed] OR GREATER UM109 MAINTAIN [speed] OR LESS
UM116 RESUME NORMAL SPEED
UM134 Report CONFIRM SPEED
Increment 3 – Deferred due to Avionics Issues Consists of Crossing Restrictions involving Time Pilot requested routes / clearances
8Federal Aviation
About the Current DCIS Contract
9Federal Aviation
Contract Structure
• Term
– Awarded at the end of FY2012
– 7-year base period
– Ten 1-year options
– Currently in contract year 15
– Contract ends September 30, 2029
• Work Scope
– Administer an Equipage Initiative
• No longer active: used during the base period of the contract
– Assist in the Integration of the end-to-end system
• No longer active: used during initial deployment of Tower
Services and Initial Services
– Provide Air-to-Ground Network Service
• Providing the network service is now the primary focus
Key Network Requirements
• Operational Data: Functional Requirements
– Message routing and forwarding
• FANS Protocol
– Nationwide coverage by each CSP
• Surface: Movement and nonmovement areas
• En Route:
– For 20 ARTCCs
– 16K MSL and above with additional regions above TDLS airports with
DCL enabled
• Operational Data: Performance Requirements
– Latency
• Requirements on the distribution are imposed for 95th and 99th percentiles
• Uplink and Downlink latency requirements are specified
– RMA
• 99.99% for most En Route coverage and high-volume airports
– Throughput
• Defined for a volume of airspace
• Monitoring Data: Functional and Performance
– Detection
– Reporting
• Service Certification Capability
The DCIS Contract and Key Requirements
10Federal Aviation
Protocol, Architecture, and Infrastructure
11Federal Aviation
VHF VDL Mode 2
VD
L-
VD
L-
VD
L-
VD
L-
What do transmissions look like?
The protocol entails a carrier sense multiple access (CSMA) transmission approach. Transmitters wait until they hear a clear channel before transmitting. (The Party Line)
This protocol is a connection- oriented protocol. The aircraft forms a connection with a ground station. As the aircraft transits the airspace, it connects to ground stations along its path with strong signals and then disconnects.
(Make before Break)
Aircraft can fly out of coverage and not immediately know that the link to the ground station was lost.
Aircraft can be sent to a different frequency / ground station (GRAIHO) (Go-there) by a transmission through the currently connected ground station.
Aircraft can also be beckoned to a ground station (GIHO) (Come- here) by a transmission from that ground station.
Links established carry both AOC and ATS messages
The Protocol
12Federal Aviation
Main Functional Components
1. En Route application resides in
ERAM at 20 centers and utilizes 2 NAP facilities at ZTL and ZLC
2. Surface application resides at 65 airports and utilizes 2 hubs TIMS East and TIMS West
3. The operational traffic subsystem in
DCNS
4. The monitoring traffic subsystem in
DCNS
5. Network Operation Centers
6. Aircraft Avionics Configurations
The Current Architecture
MCDU
VHF Subnetwork
CMU
FMS
HF Subnetwork (Oceanic Aircraft)
Satellite Subnetwork (Oceanic aircraft)
Federated Avionics Suite
AID
EFB
Integrated Modular Avionics Architecture
ERAM: En Route Automation Modernization TIMS: Tower Information Management System NAP: National Application Processor
TDLS: Tower Data Link System BEP: Back End Processor FEP: Fron End Processor
NESG: National Enterprise Services Gateway
13Federal Aviation
A/G Infrastructure
CSP1 VDL-2 Infrastructure
CSP2 VDL-2 Infrastructure
Each ground station does not necessarily have radios for all frequencies.
Note that while many, but not all uplinks are limited to VDL-2, downlinks have no such restriction
Common Signaling Channel shared by ARINC and SITA: 136.975 MHz
Source: FCC Universal Licensing System, Active Licenses
14Federal Aviation
Use and Performance of Domestic CPDLC
15Federal Aviation
What Does a Flight with CPDLC Look Like?
• A Flight from LAX to SEA in 2025
• Filed Flight Plans
• KLAX.SUMMR2.SCTRR..SNS..RBL..L
MT.HAWKZ8.KSEA/0209
• KLAX.SUMMR2.SCTRR..SNS..RBL..L
MT.HAWKZ8.KSEA/0657
• KLAX./.VTU139013..SCTRR..SNS..R
BL..LMT.HAWKZ8.KSEA/0657
• The last flight plan was used for the flight, and Clearance Delivery sent the aircraft a Cleared as Filed (CAF) clearance for the flight
Filed
Actual
16Federal Aviation
Functional Use of Data Comm
Message Type Number Percentage All 3,737,443 100.00%
TOCs 2,855,094 76.39%
Altitudes 320,864 8.59%
Direct-To Route [UM74] 201,988 5.40%
Crossing Restrictions 73,755 1.97%
Speeds (FS Inc1) 56,083 1.50%
Full Route [UM80] 40,493 1.08%
Cleared-To Route [UM79] 29,214 0.78%
Report* 3,232 0.09%
Advisories (FS Inc2) 1,846 0.05%
Holding (FS Inc2) 361 0.01%
Add’l FS Routes (FS Inc2) 315 0.01%
Block Altitudes (FS Inc1) 50 0.00%
Other 154,148 4.12%
Successful Controller Initiated Uplinks over a recent 28-day period
* Confirm Assigned Altitude & Confirm Speed
Routes disabled in ZNY during this period
17Federal Aviation
Overall Performance
USR: Uplink Success Rate A controller issues an uplink & there is proof that the aircraft received the uplink.
Recent national average over the past year: 99.39% (14 day moving average)
Uplink Volume The number of controller-initiated uplinks.
Uplink Failures:
No proof exists that the uplink reached the aircraft
18Federal Aviation
Successes and Failures over a One-week Period
Successful Controller Initiated Uplinks
Up to 8610 uplinks / week
Failed Controller Initiated Uplinks
Up to 60 failures / week
19Federal Aviation
Opportunities for Improving Performance
20Federal Aviation
• ZLC airspace has 2 arrival routes to SLC airport and one departure route with recurring failed messages
– The SPANE EIGHT arrival involving one of these areas is depicted at left. Aircraft are descending from FL250 to around 15,000 MSL on arrival into SLC from the southeast
• While terrain is one factor, redundant coverage exists for both VDL-2 Communication Service Providers
• When aircraft are connected to a ground station in the future route of flight with coverage, the success is quite high
Opportunity 1: SLC Arrivals
Red aircraft denote unsuccessful controller-initiated uplinks. All others are successful. Uplinks span a recent 1-week period.
CSP1 CSP2
Statistics on Controller-Initiated Uplinks to aircraft on SPANE EIGHT Arrival
Ground Station
Fail Success Total USR % of uplinks
CSP1-GS1 12 12 100.0% 12.5%
CSP1-GS3 19 19 100.0% 19.8%
CSP1-GS4 1 1 2 50.0% 2.1%
CSP1-GS5 12 41 53 77.4% 55.2%
CSP1 - SAT2 2 2 100.0% 2.1%
CSP1-GS7 1 1 100.0% 1.0%
CSP1-GS8 5 5 100.0% 5.2%
CSP1-GS9 1 1 100.0% 1.0%
CSP1-GS10 1 1 100.0% 1.0%
Subtotal 13 83 96 86.5% 100.0%
One Week Ground Station
Fail Success Total USR % of uplinks
CSP2-GS1 1 1 0.0% 0.4%
CSP2-GS2 1 1 100.0% 0.4%
CSP2-GS3 2 7 9 77.8% 4.0%
CSP2-GS4 79 79 100.0% 35.3%
CSP2-GS5 2 2 100.0% 0.9%
CSP2-GS6 2 2 100.0% 0.9%
CSP2-GS7 6 1 7 14.3% 3.1%
CSP2-GS8 1 1 100.0% 0.4%
CSP2-GS9 121 121 100.0% 54.0%
CSP2 - SAT3 1 1 100.0% 0.4%
Subtotal 9 215 224 96.0% 100.0%
One Week
21Federal Aviation
Opportunity 2: International Arrivals within ZBW Airspace
• Domestic inbound aircraft encounter errors by failing to switch to VDL-2 from satellite
• Coverage is not an issue for most of the errors
• ZBW has good coverage; however, it has a high percentage of errors involving the switch from satellite
Red aircraft denote unsuccessful controller-initiated uplinks. Uplinks span a recent 4-week period.
Failures from both CSPs are presented
• Looking at two different weeks of combined CSP performance within this period indicates different failure profiles involving satellite communications for weeks with very similar traffic patterns
• Several questions arise based on this information
Week 1 Week 2
22Federal Aviation
• A closer examination of week- by-week uplink messages, successes, failures, and satellite related failures indicate that by focusing on 8 aircraft types, the program will address
– 76% of the satellite failures that occur on a weekly basis
– Investigate aircraft that account for 50% of the failures on a weekly basis and
– Account for only 25% of the successful transactions
• Through outreach to one air-carrier, the program understands a large percentage of underlying issues and identifies opportunities for improvement
Opportunity 2 Continued
Focusing on 8 aircraft types tackles a substantial part of the problem
• Failures are depicted
• Bolded represent failed transactions last on satellite
23Federal Aviation
CPDLC Stakeholders and Industry Engagement
24Federal Aviation
Industry Engagement Data Communications Implementation Team (DCIT)
• During the formation of the program, leadership recognized the large number of interested and impacted stakeholders for the CPDLC system
– Also, their many different perspectives on the technology and application we were planning to implement
– Needs were to establish direction, alignment and commitment
– As models, Europe had the Link 2000+ Integration team (LIT) and in the Oceanic Environment there was the FANS Integration Team (FIT)
• The DCIT has been met multiple times per year since the first meeting on Jan 20, 2011 An early stakeholder graphic
25Federal Aviation
Thank you for your attention
| Technical Overview of the Current Data Comm Program |
| Topics |
| Current Status of the Program |
| Key Milestones of the Program |
| Status S1P1 Implementation |
| Status S1P2 Initial Services |
| Status S1P2 Full Services |
| About the Current DCIS Contract |
| The DCIS Contract and Key Requirements |
| Protocol, Architecture, and Infrastructure |
| VHF VDL Mode 2 |
| The Current Architecture |
| A/G Infrastructure |
| Use and Performance of Domestic CPDLC |
| What Does a Flight with CPDLC Look Like?� |
| Functional Use of Data Comm |
| Overall Performance |
| Successes and Failures over a One-week Period |
| Opportunities for Improving Performance |
| Opportunity 1: SLC Arrivals |
| Opportunity 2: International Arrivals within ZBW Airspace |
| Opportunity 2 Continued |
| CPDLC Stakeholders and Industry Engagement |
| Industry Engagement�Data Communications Implementation Team (DCIT) |
| Thank you for your attention |
File details come from the government source that posted it. Updated .