CHAPTER 1. GENERAL
1.1 Purpose of this Advisory Circular (AC). This AC provides guidance for aircraft eligibility and operational use of data link communications in the United States and in oceanic and remote continental airspace. This document also provides explanations of data link systems to inform those who may be new to using digital aircraft communication and surveillance systems. This AC provides new guidance associated with updated and/or new operational authorization. The regulatory source basis for this AC is Title 14 of the Code of Federal Regulations (14 CFR) part 91, § 91.123. For more information, see paragraph 1.11.
1.1.1 AC Terms. The term “must” is used in this AC to indicate a mandatory requirement driven by regulation or required for a system to operate properly. The term “should” is used to indicate a recommendation. The term “operator” refers to the certificate holder, program manager, and operator/company. Future Air Navigation System (FANS) 1/A(+) is used to denote both FANS 1/A and/or FANS 1/A+.
1.1.2 Alternative Method of Compliance. In lieu of following the guidance in this AC without deviation, operators may elect to follow an alternative method, provided the alternative method is found to be acceptable to the Federal Aviation Administration (FAA). This AC does not change, add, or delete regulatory requirements or authorize deviations from regulatory requirements.
1.2 Applicability. This AC applies to operators under 14 CFR parts 91, 91 subpart K (part 91K), 121, 125, 129, and 135 conducting data link communications operations in the United States or in oceanic and remote continental airspace. This AC also applies where the foreign authority has adopted International Civil Aviation Organization (ICAO) data link communication standards.
Note: Part 91 operators do not require operational authorization for the use of data link in the United States. For data link operations in oceanic and remote continental airspace and/or foreign countries requiring specific data link approval, part 91 operators may apply to their responsible Flight Standards office for a letter of authorization (LOA). Pilots using “J” codes for U.S. domestic data link en route require a data link authorization prior to entering oceanic and remote continental airspace. Part 91 operators filing J codes for U.S. domestic data link services must have a data link authorization to file J5–J7 in oceanic and remote continental airspace (see Appendix D, Flight Planning).
1.3 Where You Can Find This AC. You can find this AC on the FAA’s website at http://www.faa.gov/regulations_policies/advisory_circulars.
1.4 What This AC Cancels. AC 120-70C, Operational Authorization Process for Use of Data Link Communication System, dated August 3, 2015, is cancelled.
1-1
1.5 Scope. The scope of this AC is limited to the interoperability designators listed in Table 2-2, Interoperability Designators and Descriptions. Aeronautical Information Services (AIS) and Meteorological Information (METI) Services are excluded from the scope of this AC.
1.6 AC Format. Chapter 2, Data Link Communication Overview, is intended to inform those not familiar with data link communications. Chapters 3-8 provide aircraft eligibility and operational guidance with the following topics:
• Chapter 3, Aircraft Eligibility,
• Chapter 4, Communication Service Providers (CSP),
• Chapter 5, Operational Use of Data Link Communications,
• Chapter 6, Performance Monitoring,
• Chapter 7, Training, and
• Chapter 8, Reports.
1.7 Version References. The most current version of a document is designated by parentheses “( )” placed at the end of the number designation. Specific versions are indicated by a letter. If no letter appears after the document designation, then all versions of the document are applicable. As a convenience, most references are hyperlinked to a website containing the most current document. The most current ACs or Technical Standard Orders (TSO) are available by clicking the following links:
1. ACs.
2. TSOs.
1.8 FAA Document References. This AC, along with AC 20-140( ), provides all the information necessary for data link communication compliance in the United States and in oceanic and remote continental airspace and should be considered the “source documents” for the operational use of data link by U.S. operators and pilots. ICAO documents are referenced in this document as a convenience to the operator.
1.9 References (current editions).
1. Title 14 CFR Parts 21, 23, 25, 27, 29, 43, 91, 91K, 121, 125, 129, and 135.
2. ACs:
• AC 20-140, Guidelines for Design Approval of Aircraft Data Link Communication Systems Supporting Air Traffic Services (ATS).
• AC 20-160, Onboard Recording of Controller Pilot Data Link Communication in Crash Survivable Memory.
1-2
3. TSOs:
• TSO-C160a, Very High Frequency (VHF) Digital Link (VDL) Mode 2 Communications Equipment.
• TSO-C177( ), Data Link Recorder Equipment.
4. ICAO Documents:
• Annex 6, Operation of Aircraft, Part I, International Commercial Air Transport.
• Annex 6, Operation of Aircraft, Part II, International General Aviation.
• Annex 10, Aeronautical Telecommunications, Volume II, Communication Procedures including those with PANS status.
• Annex 10, Aeronautical Telecommunications, Volume III, Communication Systems, Part 1, Digital Data Communications Systems.
• Annex 11, Air Traffic Services.
• Annex 15, Aeronautical Information Services.
• Annex 19, Safety Management.
• Document 4444, Procedures for Air Navigation Services - Air Traffic Management.
• Document 7030, Regional Supplementary Procedures.
• Document 8400, Procedures for Air Navigation Services, ICAO Abbreviations and Codes.
• Document 8585, Designators for Aircraft Operating Agencies, Aeronautical Authorities and Services.
• Document 9694, Manual of Air Traffic Services Data Link Applications.
• Document 9869, Performance-Based Communication and Surveillance (PBCS) Manual.
• Document 10037, Global Operational Data Link (GOLD) Manual, ICAO Global Guidelines for Data Link Operations.
• Document 10063, Manual on Monitoring the Application of Performance-Based Horizontal Separation Minima.
• North Atlantic Document 007, North Atlantic Operations and Airspace Manual.
This document is published on behalf of the North Atlantic Systems Planning Group by the European and North Atlantic Office of ICAO and includes data link material.
• North Atlantic Oceanic Errors Safety Bulletin (OESB).
1-3
5. RTCA and European Organization for Civil Aviation Equipment (EUROCAE) Documents:
• DO-219, Minimum Operational Performance Standard (MOPS) for ATC Two-Way Data Link Communications, dated August 27, 1993.
• DO-258A/ED-100A, Interoperability Requirements for ATS Applications Using ARINC 622 Data Communications, dated April 7, 2005.
• DO-264/ED-78A, Guidelines for Approval of the Provision and Use of Air Traffic Services Supported by Data Communications, dated December 14, 2000.
• DO-280B Change 1/ED-110B Change 1, Volumes 1 and 2, Interoperability Requirements Standard for Aeronautical Telecommunication Network Baseline 1 (ATN B1 Interop Standards), dated March 18, 2014.
• DO-290 Changes 1 and 2/ED-120 Changes 1 and 2, Safety and Performance Requirements Standard for Air Traffic Data Link Services in Continental Airspace (Continental SPR Standard), dated April 29, 2004.
• DO-305A/ED-154A, Future Air Navigation System 1/A - Aeronautical Telecommunication Network Interoperability Standard (FANS 1/A - ATN B1 Interop Standard), dated March 21, 2012.
• DO-306 Change 1/ED-122 Change 1, Safety and Performance Standard for Air Traffic Data Link Services in Oceanic and Remote Airspace (Oceanic SPR Standard), dated March 2011.
• DO-350A, Safety and Performance Requirements Standard for Baseline 2 ATS Data Communications (Baseline 2 SPR Standard), Volumes 1 and 2.
• ED-85A, DLASD for the Departure Clearance Data-Link Service.
• ED-89A, DLASD for the ATIS Data-link Service.
• ED-93, Minimum Aviation System Performance Standard for CNS/ATM Message Recording Systems-Amendment 1, dated November 23, 1998.
• ED-106A, DLASD for the Oceanic Clearance Data-link Service.
6. Data Communications Network Service (DCNS) Alternative Media Description. The DCNS Alternative Media Description defines the qualification requirements for any media proposed to be used for domestic en route air traffic control (ATC) operations.
7. NAS Data Communications Guide. This document introduces operators to data link communications operations within the United States National Airspace. It discusses Controller-Pilot Data Link Communication–Departure Clearance (CPDLC-DCL) and outlines the roles of the Airline Operations Center, clearance delivery controllers, and pilots. The document describes the general procedures for logging on/notifying, loading the flight plan, receiving the CPDLC-DCL, responding to the CPDLC-DCL message, and disconnecting/logging off. Examples of different types of revised CPDLC-DCLs are provided with guidance for reviewing, processing, 1-4
and responding to the clearances. Additionally, this guide provides general information on the use of data link communications during en route operations.
8. Data Link Communication Compliance Guide. This guide expedites the compliance process as it condenses into one location the information required for data link operations.
1.10 Airworthiness. For airworthiness guidance for new aircraft and systems, refer to AC 20-140( ).
1.11 Regulatory Basis for Data Link Communication. CPDLC is an acceptable method of delivering and accepting an ATC clearance in accordance with part 91, § 91.123.
With data link communication technology, both digital and voice communication are available to ATC and the pilot. Depending on the operation, data link communication may be the most suitable method of communication as deemed necessary for ATC and pilot purposes.
1.11.1 CPDLC Compliance and Voice Communication. CPDLC is not sufficient as a means of compliance to the voice communication equipment requirements as per §§ 91.129,
91.130, 91.131, 91.135, 91.205, and 91.511; part 121, §§ 121.99 and 121.122; and part 135, § 135.165, and is not required by these rules. For data link communications, two-way radio voice communication or other means of communication approved by the FAA must also be available.
1.11.2 Flight Plan Filing and Data Link Communication Capability. Pilots and operators must file an accurate flight plan in accordance with §§ 91.169 and 91.153(a)(9). The Air Traffic Service Unit (ATSU) evaluates flight plan designator(s) to provide filed services.
Pilots and operators should use the guidance in this AC and other appropriate documents to determine the data link communication designator(s) for their route (see Appendix D).
1.11.3 Cockpit Voice Recorder (CVR) and Flight Data Recorder (FDR). Operators must comply with the CVR and FDR requirements of §§ 91.609(j), 121.359(k), and 135.151(h), and part 125, § 125.227(i). FAA Information for Operators (InFO) 16004 provides additional guidance concerning the applicability of these regulations.
1.12 AC Feedback Form. For your convenience, the AC Feedback Form is the last page of this AC. Note any deficiencies found, clarifications needed, or suggested improvements regarding the contents of this AC on the Feedback Form.
1-5
CHAPTER 2. DATA LINK COMMUNICATION OVERVIEW
2.1 Introduction. This chapter is intended to be informative for those not familiar with data link communication. For those already knowledgeable, Chapters 3 through 8 of this AC are devoted to data link eligibility and use.
2.2 What Are Data Link Communications? “Data link” is a generic term encompassing different types of data link systems and subnetworks. Figure 2-1, Overview Data Link System, provides an overview of a data link system, including subnetworks. While many data link capable aircraft have access to very high frequency (VHF) data link (VDL), not all aircraft have access to additional satellite and/or high frequency (HF) data link capability. Similarly, not all communication service providers (CSP) have HF data link capability.
Figure 2-1. Overview Data Link System
2.2.1 Aircraft Communication Addressing and Reporting System (ACARS) and Aeronautical Telecommunications Network (ATN). There are ACARS-based applications and ATN-based applications. The VDL Digital Link Mode 2 subnetwork supports both ACARS-based and ATN-based applications. The other subnetworks listed in this section support ACARS-based applications only. Controller Pilot Data Link Communication (CPDLC) and Automatic Dependence Surveillance-Contract (ADS-C) can be Future Air Navigation System (FANS) 1/A(+) or ATN-based. The FANS 1/A-based services are used over the ACARS networks and the ATN-based services are used over the 2-1
ATN networks. The ACARS and ATN networks are not compatible. This AC concentrates on CPDLC and ADS-C using FANS 1/A(+) unless specifically denoted as ATN.
2.2.2 Data Link Subnetwork. Data link systems send messages over several communication subnetworks:
• VDL Mode 0/A (i.e., ACARS),
• VDL Mode 2,
• Satellites, and/or
• High Frequency Data Link (HFDL).
2.2.3 Data Link Systems. Data link communications is a means of transmitting and receiving digital information. ATS data link systems include the following:
• FANS 1/A(+),
• ATN Baseline 1 (B1),
• Baseline 2 (B2), and
• ACARS Air Traffic Service (ATS).
2.3 FANS. FANS 1/A is ACARS-based and provides direct data link communication between the pilot and the air traffic controller via FANS 1/A avionics and FANS 1/A ground end systems. In the early 1980s, International Civil Aviation Organization (ICAO) began an effort to establish data link architecture under its FANS structure.
Boeing developed FANS 1 to DO-219 and ARINC 745 using ARINC 622 binary character data format followed by Airbus with its FANS A. These two systems are referred to as FANS 1/A. The “+” at the end of FANS 1/A indicates an updated system version that includes a message latency monitor to detect old messages that may no longer apply. FANS messages can be sent over a variety of subnetworks depending on:
• Aircraft equipment,
• Configuration/media management, and
• Subnetwork availability.
2.4 CPDLC and ADS-C.
2.4.1 CPDLC. CPDLC is a means of communication between controller and pilot, using data link for air traffic control (ATC) communications. Messages from an aircraft to the Air Traffic Service Unit (ATSU) may follow a standard format or may be free text.
Messages from a controller normally follow a standard format and usually require a response from the pilot (see Appendix F, Controller Pilot Data Link Communication 2-2
(CPDLC) Uplink and Downlink Tables, for uplink message (UM) and downlink message (DM) sets).
2.4.2 ADS-C. ADS-C is an automated surveillance information system that sends position and other flight reports to the ATSU. After initial logon/notification, a link is established between the ground system and the aircraft. Without pilot input, the oceanic ATSU/Aeronautical Operational Control (AOC) can establish a “contract” with the aircraft to receive reports of aircraft identification, aircraft position, altitude, Mach number, vertical rate, true track, magnetic heading, ground speed, navigation waypoints, and meteorological data.
2.4.2.1 ADS-C Contract Types. Depending on the aircraft type, there can be up to five separate connections to different ground facilities (i.e., ATSU/AOC) at any one time. Each connection can have one Periodic contract, one Event contract, and one Demand contract.
1. Periodic. The ATSU can set or alter the update rate or time interval as needed (a higher update rate is usually required in high traffic areas or associated with reduced separation).
2. Event. The aircraft system will communicate an event as established by the ATSU if there is a change in waypoint, vertical rate, lateral deviation or altitude. An event contract remains in effect until the ATSU cancels it or until the event(s) used to trigger the report occurs. The waypoint change event contract will trigger a report for all waypoint changes. All other event contracts will trigger a report on the first occurrence and then, if necessary, the ATSU will need to request a new event contract indicating all desired event types. (See Figure 2-2, ADS-C Event Sequence.)
3. Demand. The ATSU can request a single update as needed. This does not affect an existing contract preset rate.
Figure 2-2. ADS-C Event Sequence
2-3
2.4.2.2 ADS-C Emergency. An ADS-C emergency can be triggered by the pilot by the following means:
1. Manually, by selecting the ADS-C emergency function;
2. Indirectly, by triggering another type of emergency alerting system
(e.g., transmission of a CPDLC emergency message or selection of a Secondary Surveillance Radar (SSR) emergency code); and
3. Covertly (The availability of that functionality may vary between aircraft types).
Note: Once an ADS-C emergency has been triggered, under normal circumstances, the avionics will continue to transmit ADS-C emergency periodic reports until the pilot de-selects the ADS-C emergency function.
2.5 ATN. ATN is an inter-network architecture permitting ground, air-ground, and avionics data subnetworks to exchange digital data for the safety of air navigation and for the regular, efficient, and economic operation of ATS. ATN is in limited use in Europe, but not available in U.S. domestic airspace. The system is terrestrial based and not available over oceanic and remote continental areas.
2.5.1 ATN B1. ATN B1 consists of the following:
• Context management (CM) application for Data Link Initiation Capability (DLIC) service; and
• CPDLC application for ATC Communication Management (ACM), ATC Clearance (ACL), and ATC Microphone Check (AMC) services.
2.6 B2. B2 is ATN-based and will enable extended capabilities not possible with ATN B1 or FANS 1/A(+) as shown in Table 2-2, Interoperability Designators and Descriptions.
The FAA plans to implement the B2 CM, CPDLC, and ADS-C ATN-based applications over the Internet Protocol Suite. B2 will provide additional services such as:
1. CPDLC:
• Initial Four-Dimensional (4-D) Trajectory Data Link (4DTRAD),
• Dynamic Required Navigation Performance (DRNP), and
• Advanced flight Interval Management (IM).
2. ADS-C:
• Extended Projected Profile (EPP) information provided in ADS-C reports supporting Information Exchange and Reporting (IER), 4DTRAD, and DRNP services.
2-4
2.7 FANS 1/A(+) and ATN. Some avionics implementations support both the FANS 1/A(+)-based applications and associated protocols and the ATN-based applications and protocols. Depending on the system used by the ATSU, pilots may be required to logoff/disconnect any existing CPDLC or ADS-C session(s) and reestablish contact to another ground system when seamless transfer is not possible.
2.8 ACARS ATS. ACARS is a digital data link system for transmitting short, relatively simple messages between aircraft and ground stations via VHF, HF, or satellite.
Note: The ACARS network also carries FANS 1/A(+) messages.
2.8.1 Background. ARINC designed the ACARS protocol to replace VHF voice service in 1978. Later, Société International de Télécommunications Aeronautiques (SITA) added additional radio stations to augment this service. Airlines introduced ACARS in the late 1980s to reduce crew workload and improve data integrity. Although the term ACARS is often thought to encompass only a single data link system installed on the aircraft, it actually refers to a complete air and ground system.
2.8.2 Aircraft and Ground ACARS Systems. The aircraft portion of ACARS system consists of an avionics computer called an ACARS management unit (MU) and a control display unit (CDU). On the ground, the ACARS system is made up of a network of radio transceivers to receive (or transmit) data link messages and route them to various airlines on the network.
2.8.3 ACARS ATS Supported Applications Include:
• Departure Clearance (DCL) (not to be confused with CPDLC-DCL),
• Oceanic clearance (OCL),
• Terminal Weather Information for Pilots (TWIP), and
• Digital Automatic Terminal Information Service (D-ATIS).
2.9 Tower Data Link System (TDLS). The TDLS automates tower-generated information for transmission to aircraft via data link communication for both CPDLC-DCL and Pre-Departure Clearance (PDC). The TDLS interfaces with sources of local weather data and flight data in order to provide pilots with PDC, D-ATIS, and CPDLC-DCL services.
Note: The term PDC refers to the U.S. ATS of DCL. The DCL includes flight plan route, climb via, and/or initial/requested altitude, beacon code assignment, and departure frequency.
2.10 CPDLC-DCL. CPDLC-DCL is available at various airports in U.S. domestic airspace using FANS 1/A(+) via VDL Mode 0/A and/or Mode 2 for departure clearance services.
2.10.1 Dispatch or Flight Following Systems. For operators with a dispatch center, flight following system, or other base of operations, copies of all data link 2-5
communications may be routed to, and stored by, the operator. Contact the FAA Data Communications Program Office (refer to their website) to coordinate.
2.10.2 CPDLC-Departure Clearance Service (CPDLC-DCL). CPDLC-DCL provides a means for requesting and delivering initial and revised DCLs. These CPDLC messages include departure procedure, flight plan route, initial and requested altitude, beacon code, departure frequency, and other non-route information.
Note 1: CPDLC-DCL is different than international DCL operations.
International systems use the ACARS ATS DCL application via ARINC 623/European Organization for Civil Aviation Equipment (EUROCAE) ED-85A, not the FANS CPDLC application.
Note 2: At participating airports, PDC services may be available for non-FANS equipped aircraft.
2.10.3 CPDLC Specified on the Airport Diagram. To differentiate what communication services are available at each facility, refer to the airport diagram, Standard Instrument Departures (SID), and other terminal procedures pages. See Figure 2-3, Data Link Communication Services on Departure Procedure, for the CPDLC annotation on a departure procedure.
Figure 2-3. Data Link Communication Services on Departure Procedure (CRSON4.CRSON) 17117 SL-253 (FAA)
CRSON FOUR DEPARTURE (RNAV) MEMPHIS INTL (MEM) MEMPHIS, TENNESSEE D-ATIS 127.75 TOP ALTITUDE: HUMMS CINC DEL 5000
125.2 CPDIC
GND CON
121.0 379.2 (Rwy 9-27)
121.9 379.2 (Rwys 18C-36C, T8t- CRSON
121.65 379.2 (Rwy 18R-36L)
MEMPHIS TOWER
118.3 257.8 (Rwy 9-27)
119.7 257.8 (Rwys 18C-36C, 18L-36R) CPDLC Services Available
128.425 257.8 (Rwy 18R-36L)
MEMPHIS DEP CON
124.15 385.45 TAKEOFF MINIMUMS:
Ruys 9, 18L/C/R, 27, 36L/C/R:
Standard with minimum climb of 500' per NM to 860.
2-6
2.10.3.1 CPDLC-DCL logon/notification (see paragraph 5.3). “KUSA” is the National Single Data Authority (NSDA) for all CPDLC logons/notifications in the United States. Pilots activate the data link communication system anytime during preflight by logging on to/notifying KUSA with ATC. Within 30 minutes of the proposed departure time, an “ATC Connection Established” message will be received if the following conditions are met:
1. Logon/notification information was correctly formatted;
2. An ATC-filed flight plan is on file;
3. Flight plan indicates the aircraft is CPDLC-DCL capable; and
4. ATC controller has approved the DCL.
2.10.3.2 Once a successful ATC connection has been established and the CPDLC-DCL has been approved by the controller, the CPDLC-DCL will be automatically sent to the aircraft. Pilots do not have to request a clearance. After the clearance is received and verified, pilots should:
1. Review the clearance and verify that no clarification from ATC is required (Reject/Unable);
2. Confirm the appropriate runway, if assigned, departure procedure, and transition with no discontinuities; and then
3. Acknowledge (ROGER (DM3)/WILCO (DM0) or UNABLE (DM1)) the message.
Note 1: If it becomes necessary to revert to voice after receiving a clearance, pilots should respond with Reject/Unable to the uplinked clearance.
Note 2: For CPDLC-DCL ground operations only, pilots can expect an automated ATC-initiated logoff/disconnect 5 to 10 minutes after takeoff.
2.10.3.3 If changes in tower or en route conditions occur (e.g. weather) the ATSU may amend the clearance information and transmit a revised CPDLC-DCL. Pilots should follow the same procedure for revised clearances.
2.11 PDC. PDC is a subscriber based service to provide an effective and efficient means of delivering a text-based electronic departure clearance prior to taxi. Data link communication technologies are utilized via a PDC in which ATC clearances are sent to a subscriber’s dispatch center, flight followers, or base of operations. The clearance is made available to the pilot with the following formats:
1. Internet access,
2. Airline gate terminal, 2-7