Radar Vectors
Advisory Circular Current Issued Oct 3, 2017 AFS-400 157 pages Copy saved Nov 18, 2026

AC 90-117 Data Link Communications

This advisory circular (AC) applies to all pilots, certificate holders, operators, and/or program managers conducting data link communication operations and to those providing data communication services on behalf of operators to meet Federal Aviation Administration (FAA) and International Civil Aviation Organization (ICAO) requirements. The AC provides guidance for data link communications eligibility and compliance using Future Air Navigation Systems (FANS) 1/A(+) and Aeronautical Telecommunications Network (ATN). It defines performance concepts, data link systems, and data link services available within the National Airspace System (NAS) and international operations. This AC addresses Automatic Dependent Surveillance – Contract (ADS-C) and Controller-Pilot Data Link Communication (CPDLC). ADS-C provides a direct connection between the aircraft automation and ground automation, to exchange status information concerning the flight including automated pilot position reports. CPDLC provides efficient digital communication without frequency congestion or misunderstandings and misinterpretations common to voice communication. CPDLC – Departure Clearance (CPDLC-DCL) service provides automated DCLs with the capability to amend clearances prior to departure. Pre-Departure Clearances (PDC) and Aircraft Communications Addressing and Reporting System (ACARS) are discussed as part of the overall data link services. Guidance is also provided for performance monitoring and problem reporting.

Official source ↗ Open PDF

AC 90-117_FAA Web › The AC provides an overview of data link communication operations for…

U.S. Department of Transportation Federal Aviation Administration

Advisory Circular

Subject: Data Link Communications Date: 10/3/17 AC No: 90-117 Initiated by: AFS-400 Change:

This advisory circular (AC) applies to all pilots, certificate holders, operators, and/or program managers conducting data link communication operations and to those providing data communication services on behalf of operators to meet Federal Aviation Administration (FAA) and International Civil Aviation Organization (ICAO) requirements.

The AC provides an overview of data link communication operations for U.S. domestic operations and in oceanic and remote continental airspace. It includes operational use guidance, minimum performance and services of communication service provider (CSP), performance monitoring, training requirements, and discrepancy reporting. Michael ZenkovichMichael Zenkovich Deputy Executive Director, Flight Standards Service

CONTENTS Paragraph Page

Chapter 1. General … 1-1

1.1 Purpose of this Advisory Circular (AC) … 1-1

1.2 Applicability … 1-1

1.3 Where You Can Find This AC … 1-1

1.4 What This AC Cancels … 1-1

1.5 Scope … 1-2

1.6 AC Format … 1-2

1.7 Version References … 1-2

1.8 FAA Document References … 1-2

1.9 References (current editions) … 1-2

1.10 Airworthiness … 1-5

1.11 Regulatory Basis for Data Link Communication … 1-5

1.12 AC Feedback Form … 1-5

Chapter 2. Data Link Communication Overview … 2-1

2.1 Introduction … 2-1

2.2 What Are Data Link Communications? … 2-1

2.3 FANS … 2-2

2.4 CPDLC and ADS-C … 2-2

2.5 ATN … 2-4

2.6 B2 … 2-4

2.7 FANS 1/A(+) and ATN … 2-5

2.8 ACARS ATS … 2-5

2.9 Tower Data Link System (TDLS) … 2-5

2.10 CPDLC-DCL … 2-5

2.11 PDC … 2-7

2.12 Data Authority … 2-9

2.13 ATSUs and Aircraft Interoperability … 2-10

2.14 Performance-Based Communication and Surveillance (PBCS) Concept … 2-17

2.15 RCP and RSP Specifications Supporting ATM Operations … 2-18

2.16 Required Surveillance Performance (RSP) … 2-23

ii

2.17 High Frequency Data Link (HFDL) … 2-28

2.18 Future U.S. Domestic Airspace Data Link Communication Services … 2-29

2.19 Data Communication Services Strategy … 2-30

Chapter 3. Aircraft Eligibility … 3-1

3.1 Introduction … 3-1

3.2 Aircraft Eligibility … 3-1

3.3 Statement of Compliance (SOC) … 3-1

3.4 Configuration Control … 3-3

3.5 Maintenance … 3-4

Chapter 4. Communication Service Providers (CSP) … 4-1

4.1 CSP for Oceanic and Remote Continental Operations … 4-1

4.2 RCP 240 CSP Allocations … 4-2

4.3 RCP 400 CSP Allocations … 4-3

4.4 RSP Allocation Requirements … 4-4

4.5 Alternate Means of Compliance … 4-5

4.6 CSP for U.S. Operations … 4-5

4.7 CSP Monitoring … 4-8

Chapter 5. Operational Use Of Data Link Communications … 5-1

5.1 Operational Use … 5-1

5.2 Data Link Operational Guidance … 5-2

5.3 Logon/Notification … 5-2

5.4 En Route … 5-4

5.5 Voice Monitoring … 5-5

5.6 Free Text Messages … 5-6

5.7 Data Link Communication Failures … 5-6

5.8 ADS-C … 5-6

5.9 Exiting CPDLC and ADS-C Areas … 5-7

5.10 Logoff/Disconnect … 5-7

Chapter 6. Performance Monitoring … 6-1

6.1 Performance Monitoring … 6-1

6.2 Oceanic and Remote Continental Airspace … 6-1

iii

6.3 Performance Website … 6-2

6.4 Substandard Performance … 6-2

6.5 Corrective Aircraft Action … 6-2

6.6 Data Link Performance Eligibility … 6-2

6.7 Procedures to Report Problems … 6-2

6.8 Performance Monitoring in U.S. Domestic Airspace … 6-2

Chapter 7. Training … 7-1

7.1 Training Documentation … 7-1

7.2 Objectives … 7-1

7.3 Ground and Flight Training … 7-1

7.4 Pilot Knowledge Subject Areas … 7-2

7.5 Pilot Procedural Training Items … 7-3

7.6 Dispatcher Training … 7-4

7.7 Maintenance Training … 7-5

Chapter 8. Reports … 8-1

8.1 Introduction … 8-1

8.2 Common Reasons to Report … 8-1

8.3 Oceanic and Remote Continental Problem Reporting … 8-1

8.4 U.S. Domestic Airspace Problem Reporting … 8-1

8.5 Problem Reporting Process … 8-1

Appendix A. Foreign Operators … A-1

A.1 General … A-1

A.2 Title 14 CFR Part 129 … A-1

A.3 Application Process … A-1

A.4 Unique Address … A-1

A.5 U.S. Interoperability Requirements … A-1

A.6 Training … A-2

A.7 Unsafe Performance or Conditions … A-2

A.8 U.S. Domestic Airspace … A-2

Appendix B. Data Link Communications Minimum Equipment List (MEL) and

Master Minimum Equipment List (MMEL) Provisions … B-1

B.1 Inoperative Equipment … B-1

iv

Appendix C. Summary of Airspace Requirements … C-1

C.1 Summary of Airspace Requirements … C-1

Appendix D. Flight Planning … D-1

D.1 Filing Required Communication Performance (RCP)/Required Surveillance

Performance (RSP) Capabilities … D-1

D.2 Regulatory Basis … D-1

D.3 Example … D-2

D.4 Item 10a Descriptors … D-2

D.5 Item 10b Descriptors … D-3

D.6 Item 18 RSP Specification … D-3

D.7 Field 18/DAT for CPDLC or Pre-Departure Clearance (PDC) … D-4

Appendix E. Voice Phraseology … E-1

Appendix F. Controller-Pilot Data Link Communication (CPDLC) Uplink and

Downlink Tables … F-1

Appendix G. Terminology and Acronyms … G-1

G.1 Terminology … G-1

G.2 Acronyms … G-5

v

List of Figures

Figure 2-1. Overview Data Link System … 2-1

Figure 2-2. ADS-C Event Sequence … 2-3

Figure 2-3. Data Link Communication Services on Departure Procedure … 2-6

Figure 2-4. Next Data Authority Notification … 2-10

Figure 2-5. Air Traffic Service Unit (ATSU) and Aircraft Interoperability

Designators … 2-11

Figure 2-6. Performance-Based CNS/ATM Model … 2-17

Figure 2-7. Actual Communications Performance (ACP) … 2-19

Figure 2-8. RCP 240 Illustration … 2-20

Figure 2-9. RCP 400 Illustration … 2-22

Figure 2-10. RSP 180 Illustration … 2-25

Figure 2-11. RSP 400 Performance … 2-27

Figure 2-12. Data Communication Services Strategy … 2-29

List of Tables

Table 2-1. PDC vs. CPDLC-DCL … 2-9

Table 2-2. Interoperability Designators and Descriptions … 2-12

Table 2-3. Types of Data Link Systems and Operations … 2-16

Table 2-4. RCP 240 Transaction Time and Continuity Allocations—CPDLC … 2-21

Table 2-5. RCP 240 Availability Criteria (Aircraft System) … 2-21

Table 2-6. RCP 240 Integrity Criteria (Aircraft System) … 2-21

Table 2-7. RCP 400 Transaction Time and Continuity Allocations—CPDLC … 2-23

Table 2-8. RCP 400 Availability Criteria (Aircraft System) … 2-23

Table 2-9. RCP 400 Integrity Criteria (Aircraft System) … 2-23

Table 2-10. RSP 180 Surveillance Data Delivery and Continuity Allocations—ADS-C … 2-26

Table 2-11. RSP 180 Availability Criteria (Aircraft System) … 2-26

Table 2-12. RSP 180 Integrity Criteria (Aircraft System) … 2-26

Table 2-13. RSP 400 Surveillance Data Delivery and Continuity Allocations—ADS-C … 2-28

Table 2-14. RSP 400 Availability Criteria (Aircraft System) … 2-28

Table 2-15. RSP 400 Integrity Criteria (Aircraft System) … 2-28

Table 4-1. RCP 240 Transaction Time and Continuity Allocations to CSP … 4-2

Table 4-2. RCP 240 CSP Availability and Outages Parameters … 4-2

Table 4-3. RCP 400 Transaction Time and Continuity to CSP Allocation … 4-3

Table 4-4. RCP 400 Availability and Outages Parameters … 4-3

vi

Table 4-5. RSP 180 Data Delivery Time and Continuity Criteria … 4-4

Table 4-6. RSP 180 Availability and Outages Parameters … 4-4

Table 4-7. RSP 400 Data Delivery Time and Continuity Criteria … 4-5

Table 4-8. RSP 400 Availability and Outages Parameters … 4-5

Table 4-9. Data Communications Network Services (DCNS) Performance Baseline … 4-7

Table 5-1. CPDLC Connection Failure Responses … 5-5

Table B-1. Minimum Equipment List Example … B-1

Table B-2. Example of a Data Link Communication MMEL Provision … B-2

Table C-1. Summary of Airspace Requirements … C-1

Table C-2. Subnetwork Designators … C-3

Table C-3. Preferred Original Equipment Manufacturer Annotation … C-3

Table D-1. Item 10a Flight Plan COM Descriptors … D-3

Table D-2. Item 10b Flight Plan Descriptors for Surveillance Equipment … D-3

Table D-3. PDC and Departure Clearance (DCL) … D-4

Table D-4. PDC and En Route Data Link Clearances … D-5

Table D-5. PDC Only and En Route Data Link … D-6

Table D-6. En Route Data Link Clearances Only … D-6

Table E-1. Voice Phraseology Related to Controller-Pilot Data Link Communication

(CPDLC) From Pilot … E-1

Table E-2. Voice Phraseology Related to CPDLC From the ATSU … E-2

Table F-1. Color Key … F-1

Table F-2. Response Attribute of CPDLC Message Element for Uplink Messages … F-1

Table F-3. Response Attribute of CPDLC Message Element for Downlink Messages … F-2

Table F-4. Route Uplink Message Elements (RTEU) … F-3

Table F-5. Route Downlink Message Elements (RTED) … F-7

Table F-6. Lateral Uplink Message Elements (LATU) … F-8

Table F-7. Lateral Downlink Message Elements (LATD) … F-11

Table F-8. Level Uplink Message Elements (LVLU) … F-13

Table F-9. Level Downlink Message Elements (LVLD) … F-20

Table F-10. Crossing Constraint Uplink Messages (CSTU) … F-24

Table F-11. Speed Uplink Messages (SPDU) … F-28

Table F-12. Speed Downlink Messages (SPDD) … F-31

Table F-13. Air Traffic Advisory Uplink Messages (ADVU) … F-32

Table F-14. Air Traffic Advisory Downlink Messages (ADVD) … F-36

Table F-15. Voice Communication Uplink Messages (COMU) … F-37

vii

Table F-16. Voice Communication Downlink Messages (COMD) … F-39

Table F-17. Spacing Uplink Messages (SPCU) … F-40

Table F-18. Spacing Downlink Messages (SPCD) … F-42

Table F-19. Emergency/Urgency Uplink Messages (EMGU) … F-44

Table F-20. Emergency/Urgency Downlink Messages (EMGD) … F-45

Table F-21. Standard Response Uplink Messages (RSPU) … F-46

Table F-22. Standard Response Downlink Messages (RSPD) … F-47

Table F-23. Supplemental Uplink Messages (SUPU) … F-48

Table F-24. Supplemental Downlink Messages (SUPD) … F-49

Table F-25. Free Text Uplink Messages (TXTU) … F-49

Table F-26. Free Text Downlink Messages (TXTD) … F-50

Table F-27. System Management Uplink Messages (SYSU) … F-51

Table F-28. System Management Downlink Messages (SYSD) … F-53

Table F-29. FANS 1/A Uplink Messages Not Recommended for Use … F-54

Table F-30. FANS 1/A Downlink Messages Not Recommended for Use … F-57

Table F-31. ATN B1 Uplink Messages Not Recommended for Use … F-58

Table F-32. ATN B1 Downlink Messages Not Recommended for Use … F-58

viii

CHAPTER 1. GENERAL

Chapter 1. GENERAL › 1.4 What This AC Cancels.

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.

Chapter 1. GENERAL › 1.9 References (current editions).

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.

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).

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,

Chapter 1. GENERAL › 1.12 AC Feedback Form.

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.

2.2 What Are Data Link Communications? › 2.2.1 Aircraft Communication Addressing and Reporting System (ACARS)…

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.4 CPDLC and ADS-C. › 2.4.1 CPDLC.

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.4.2 ADS-C. › 2.4.2.1 ADS-C Contract Types.

(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

Chapter 2. Data Link Communication Overview › 2.6 B2.

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.10 CPDLC-DCL. › 2.10.1 Dispatch or Flight Following Systems.

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.10 CPDLC-DCL. › 2.10.3 CPDLC Specified on the Airport Diagram.

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

Chapter 2. Data Link Communication Overview › 2.11 PDC.

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,

3. Airline operations area terminal,

4. Fixed-Base Operator (FBO) terminal, and

5. ACARS.

2.11.1 PDC Communication. It is not necessary for an aircraft to be equipped with data link communication avionics for a flight to participate in the PDC service. It is only necessary for the pilot to be able to obtain a printed or electronically displayed copy of the PDC message prior to taxi (may be printed at the FBO terminal, the airline gate, etc.). The contents of the PDC message are relayed to the aircrew without modification, omission, or alteration. PDC is at the discretion of the clearance delivery controller. If the controller determines that issuing a PDC could introduce confusion, the controller will issue a verbal clearance to the aircrew. If the pilot is uncertain of the clearance, the PDC must not be used and the pilot must contact clearance delivery via voice (telephone or radio) and obtain their clearance.

2.11 PDC. › 2.11.2 PDC vs.

2.11.2 PDC vs. CPDLC-DCL. The primary difference between the PDC and CPDLC-DCL services is the PDC service depends on the operator or other third party to deliver the PDC to the aircraft whereas CPDLC-DCL service is a direct connection after logon/notification from the tower automation to the flight deck avionics of FANS-equipped aircraft. See Table 2-1, PDC vs. CPCLC-DCL, below for a side-by-side comparison.

2.12 Data Authority. › 2.12.2 Data Authority Transfer.

Table 2-1. PDC vs. CPDLC-DCL

PDC CPDLC-DCL

No Logon/Notification Required Logon/Notification Required

Sent to AOC or other Operator prescribed location Automatically sent directly to FANS 1/A(+) equipped aircraft over data link communication equipment after crew logon/notification

Delivered to the pilot by various means (i.e., over ACARS, to the FBO terminal, to the airline gate)

Delivered over data link communication directly to the aircraft within 30 minutes of proposed ETD

Depending on the delivery method, may require a printed copy to be delivered to the aircraft

Never requires a paper copy to be delivered to the aircraft

Does not require data link communication equipment to be installed in the aircraft

Requires data link communication systems on the aircraft

Does not support revised clearances. Revisions must be transmitted via voice frequency

Revised clearances can be delivered directly to the aircraft when necessary without restrictions

A specific call sign can only be used once in an adaptable time period of 12–18 hours at a specific airport

Only one call sign for a given tail can be in use for CPDLC-DCL clearances at any given time

Requires manual input by the pilot or may be uploaded from an AOC

Clearance can be sent to the avionics system which may enable “push to load” via a load prompt

2.12 Data Authority. “KUSA” is the national data authority for all U.S. domestic CPDLC logons/notifications. Figure 2-12, Data Communication Services Strategy, describes the current and planned data communication services to be available in the domestic en route environment. CPDLC en route operations in U.S. domestic airspace will use FANS 1/A(+) equipped aircraft with multi-frequency VDL Mode 2 radios. For an alternate subnetwork, see paragraph 4.6.2.

2.12.1 Current Data Authority (CDA). When an aircraft system accepts a CPDLC connection, this active connection initiates the exchange of messages between the ATSU and the aircraft as the ATSU becomes the CDA. The CDA typically initiates address forwarding to permit a downstream or adjacent ATSU (next data authority (NDA)) to establish an inactive CPDLC connection and/or an Automatic Dependent Surveillance (ADS) contract for monitoring purposes.

2.12.2 Data Authority Transfer. When the active CPDLC connection is terminated, the aircraft will activate any inactive connection. In this case, the next data authority becomes the CDA and is now able to exchange CPDLC messages with the aircraft. Figure 2-4, Next Data Authority Notification, illustrates the transfer from the CDA to the NDA.

Chapter 2. Data Link Communication Overview › 2.13 ATSUs and Aircraft Interoperability.

Figure 2-4. Next Data Authority Notification

2.13 ATSUs and Aircraft Interoperability. Figure 2-5, Air Traffic Service Unit (ATSU) and Aircraft Interoperability Designators, shows different ATSU ground systems and interoperable aircraft systems. The diagram shows the CSP and its Centralized ADS-C System (CADS). CSP’s CADS enables an ATSU without FANS 1/A capability to receive ADS-C reports from any FANS 1/A, FANS 1/A(+) or FANS 1/A ADS-C aircraft. A designator is assigned to each type of ATSU and aircraft data link system. Explanations of each interoperability designator are provided below in Table 2-2. Table 2-3, Types of Data Link Systems and Operations, provides an overview of the operational capabilities that are supported by each of the different data link systems.

Figure 2-5. Air Traffic Service Unit (ATSU) and Aircraft Interoperability Designators

Table 2-2. Interoperability Designators and Descriptions

Interoperability Designator Description

ACARS ATS ATS applications, DCL, OCL, TWIP, and D-ATIS supported by ACARS.

Note: The term DCL used internationally is similar to the term PDC used in the United States.

ATSU CADS CSP’s CADS enables an ATSU without FANS 1/A capability to receive ADS-C reports from any FANS 1/A, FANS 1/A(+) or FANS 1/A ADS-C aircraft.

FANS 1/A Initial FANS 1/A ATSU applications, ATSU Facilities Notifications (AFN), CPDLC, and ADS-C supported by FANS 1/A.

Note: FANS 1/A typically involves communication (CPDLC), navigation (Area Navigation (RNAV)/Required Navigation Performance (RNP)) and surveillance (ADS-C). This document refers to the FANS 1/A for the data link system, which includes the CPDLC and ADS-C applications. Refer to ICAO Doc 9613 for guidance material on navigation (RNAV/RNP) qualification and use.

FANS 1/A ADS-C ATSU applications AFN and ADS-C supported by FANS 1/A. FANS 1/A ADS-C comply with AFN and ADS-C applications, but do not include CPDLC application.

FANS 1/A+ Same as FANS 1/A, except with additional features, such as the message latency timer function, described in DO-258A/ED-100A.

Note 1: FANS 1/A(+) aircraft is interoperable with FANS 1/A and FANS 1/A(+) ground stations. However, message latency capability is only available when FANS 1/A(+) ground stations interoperates with FANS 1/A(+) aircraft.

Note 2: Seamless transition of ATSU data link service occurs between ATN B1 and FANS 1/A(+) ground stations when:

• Aircraft equipped with ATN B1 and FANS 1/A(+) data link system also incorporates interoperability requirement IR-207, IR-209, IR-210, IR-211, IR-212, IR-214, and IR-215 of DO-305A/ED-154A. • ATN B1 ground station incorporates interoperability requirement IRec-1 and IR-213 of DO-305A/ED-154A. • FANS 1/A(+) ground station incorporates interoperability requirement IR-208 of DO-305A/ED-154A.

Otherwise, the pilot will lose their data link service requiring the pilot to manually perform a logon/notification to reestablish ATSU data link service.

Interoperability Designator Description

Note 3: Seamless transition of ATSU data link service occurs between B2 and FANS 1/A(+) ground stations when:

• Aircraft equipped with B2 and FANS 1/A(+) data link system also incorporates interoperability requirement NIR-153, NIR-155, NIR-156, NIR-157, NIR-158, NIR-160, and NIR-161 of DO-352A/ED-229A. • B2 ground station incorporates interoperability requirement NIRec-3 and NIR-159 of DO-352A/ED-230A. • FANS 1/A(+) ground station incorporates interoperability requirement NIR-154 of DO-352A/ED-229A.

Otherwise, the pilot will lose their data link service requiring the pilot to manually perform a logon/notification to reestablish ATSU data link service.

Note 4: To allow a FANS 1/A(+) data communication system on an aircraft to communicate with an ATN B1 data communication system at an ATSU, the ATSU ground system needs to accommodate the FANS 1/A(+) aircraft by incorporating the interoperability requirements of DO-305A/ED-154A.

Note 5: To allow a FANS 1/A(+) data communication system on an aircraft to communicate with a B2 data communication system at an ATSU, the ATSU ground system needs to accommodate the FANS 1/A(+) aircraft by incorporating the interoperability requirements of DO-352A/ED-230A.

ATN B1 ATS applications CM and CPDLC supported by ATN B1:

a) CM is a data link application providing DLIC.

b) CPDLC (Version 1) for ACM, ACL, and AMC.

Note 1: Interoperability for DCL, downstream clearance (DSC), D-ATIS, and flight plan consistency data link services, which are defined in DO-280B/ED-110B are not supported.

Note 2: Seamless transition of ATS data link service between ATN B1 and FANS 1/A+ ground stations when:

• Aircraft equipped with ATN B1 and FANS 1/A+ data link system also incorporates interoperability requirement IR-207, IR-209, IR-210, IR-211, IR-212, IR-214, and IR-215 of DO-305A/ED-154A. • ATN B1 ground station incorporates interoperability requirement IRec-1 and IR-213 of DO-305A/ED-154A. • FANS 1/A+ ground station incorporates interoperability requirement IR-208 of DO-305A/ED-154A.

Otherwise, the pilot will lose their service requiring the pilot to manually perform a logon/notification to reestablish ATS data link service.

Interoperability Designator Description

Note 3: To allow a FANS 1/A+ data communication system on an aircraft to communicate with an ATN B1 data communication system at an ATSU, the ATSU ground system needs to accommodate the FANS 1/A+ aircraft by incorporating the interoperability requirements of DO-305A/ED-154A.

Note 4: To allow an ATN B1 data communication system on an aircraft to communicate with a B2 data communication system at an ATSU, the ATSU ground system needs to accommodate the ATN B1 aircraft by incorporating the interoperability requirements of DO-353A/ED-231A.

Note 5: To allow a B2 data communication system on an aircraft to communicate with an ATN B1 data communication system at an ATSU, the B2 data communication system on the aircraft needs to accommodate the ATN B1 ground system by incorporating the interoperability requirements of DO-353A/ED-231A.

B2 Version of the Baseline 2 Data Communication system described in this section. The United States plans to use B2, as defined in AC 20-140C, as part of FAA’s NextGen initiative. An aircraft equipped with B2 is fully interoperable with any B2 ground station. Aircraft equipped with a version of B2 other than that defined by AC 20-140C are not eligible for the B2 interop designator. B2 is comprised of the following data link applications and data link services.

a) CM is a data link application supporting the following data link service: DLIC.

b) CPDLC (Version 3) is a data link application supporting the following data link services: ACM, Clearance Request and Delivery (CRD), AMC, DCL, Data Link Taxi (D-TAXI), Oceanic Clearance Delivery (OCD), 4DTRAD, IER, In-Trail Procedures (ITP), IM, and DRNP.

c) ADS-C (Version 2) is a data link application supporting the following data link services: 4DTRAD, IER, Position Reporting (PR), IM, and DRNP.

Note 1: To allow a FANS 1/A+ data communication system on an aircraft to communicate with a B2 data communication system at an ATSU, the ATSU ground system needs to accommodate the FANS 1/A+ aircraft by incorporating the interoperability requirements of DO-352A/ED-230A.

Note 2: To allow an ATN B1 data communication system on an aircraft to communicate with a B2 data communication system at an ATSU, the ATSU ground system needs to accommodate the ATN B1 aircraft by incorporating the interoperability requirements of DO-353A/ED-231A.

Interoperability Designator Description

Note 3: To allow a B2 data communication system on an aircraft to communicate with an ATN B1 data communication system at an ATSU, the B2 data communication system on the aircraft needs to accommodate the ATN B1 ground system by incorporating the interoperability requirements of DO-353A/ED-231A.

Table 2-3. Types of Data Link Systems and Operations

Aircraft Equipment and

Capability

ACARS ATS

(ATSU Ground Data Link System)

CADS or

AOC (ATSU Ground Data Link System)

FANS 1/A (ATSU Ground Data Link System)

ATN B1 (ATSU Ground Data Link System)

FANS 1/A–

ATN B1 (ATSU Ground Data Link System)

ACARS ATS ATC communication

• DCL or PDC • OCL Flight information • D-ATIS

N/A N/A N/A N/A

FANS 1/A ADS-C

N/A Surveillance

• ADS-C (CADS)

Surveillance

• ADS-C N/A N/A

FANS 1/A N/A Surveillance

• ADS-C (CADS)

ATC communication

• CPDLC Surveillance • ADS-C

N/A ATC communication

• CPDLC for ACM, ACL, and AMC data link services

FANS 1/A+ N/A Surveillance

• ADS-C (CADS)

ATC communication

• CPDLC Surveillance • ADS-C

N/A ATC communication

• CPDLC for ACM, ACL, and AMC data link services

ATN B1 N/A N/A N/A ATC communication

• CPDLC for ACM, ACL, and AMC data link services

ATC communication

• CPDLC for ACM, ACL, and AMC data link services

FANS 1/A– ATN B1

N/A Surveillance

• ADS-C (CADS)

ATC communication

• CPDLC Surveillance • ADS-C

ATC communication

• CPDLC for ACM, ACL, and AMC data link services

ATC communication

• CPDLC for ACM, ACL, and AMC data link services

Note: B2 will be included at a later date.

2.14 Performance-Based Communication and Surveillance (PBCS) Concept. › 2.14.2 Communication, Navigation, and Surveillance (CNS)/ATM Model.

2.14 Performance-Based Communication and Surveillance (PBCS) Concept. The PBCS concept provides objective operational criteria to evaluate different and emerging communication and surveillance technologies and is intended for evolving Air Traffic System Management (ATM) operations. Once these criteria have been set and accepted, a specific implementation of an ATM operation including its technical and human performance may have its viability assessed against these operational criteria. ATS system changes based on communication and/or surveillance performance align with the PCBS concept (refer to ICAO Doc 9869).

2.14.1 Aligned with Performance-Based Navigation (PBN). The PBCS concept is aligned with the concept of PBN. While the PBN concept applies RNP and RNAV specifications to the navigation element, the PBCS concept applies required communication performance (RCP) and required surveillance performance (RSP) specifications to communication and surveillance elements, respectively. Each RCP/RSP specification includes allocated criteria among the components of the communication and surveillance systems involved.

2.14.2 Communication, Navigation, and Surveillance (CNS)/ATM Model. Where beneficial, RCP, RNP/RNAV, and RSP specifications are applied to communication, navigation, and surveillance elements to ensure the operational system and its components perform in accordance with the specifications. Figure 2-6, Performance-Based CNS/ATM Model, provides an overview of the performance-based CNS/ATM model, which characterizes the relationship of the performance-based specifications among CNS elements supporting an ATM operation.

Note: Similar to the PBN concept, security is beyond the scope of the PBCS concept. However, in some cases, the RCP and RSP specifications may include criteria to support mitigations from security threats.

Figure 2-6. Performance-Based CNS/ATM Model

2.14.3 PBCS and PBN Differences. There are some differences between the PBCS concept and PBN concept:

2.15 RCP and RSP Specifications Supporting ATM Operations. › 2.15.2 RCP Parameters. The following describes the RCP parameters:

1. The PBCS concept applies RCP and RSP specifications, which allocate criteria to ATS provision, including communication services, aircraft capability, and the aircraft operator. The PBN concept applies RNP/RNAV specifications which allocate criteria only to the aircraft capability and the aircraft operator; and

2. The PBCS concept includes post-implementation monitoring programs, on a local and regional basis, with global exchange of information. The PBN concept includes real-time monitoring and alerting functionality in the aircraft capability.

Note: PBCS includes real-time alerts (e.g., when a communication transaction expires or a position report is overdue) that are conceptually different than the PBN alerts (e.g., RNP UNABLE).

2.15 RCP and RSP Specifications Supporting ATM Operations. To perform ATM operations within a performance-based airspace, the standards specify functional, safety and performance criteria for the applicable CNS elements. RCP and RSP specifications, in conjunction with RNP/RNAV specifications, provide these criteria and are intended to facilitate the development of standards for ATM operations. This approach is essential to the evolution of operational concepts that use emerging technologies. For example, within the organized track system (OTS) in North Atlantic High Level Airspace (NAT HLA), the Reduced Lateral Separation Minima (RLatSM) include the following requirements:

• RNP 4;

• CPDLC with RCP 240; and

• ADS-C with RSP 180.

2.15.1 RCP Specifications. An RCP specification represents operational parameters for the complete communication transaction. It is identified by a designator (e.g., RCP 240 or RCP 400) in order to simplify the designator naming convention and to make the RCP Expiration Time (ET) readily apparent to airspace planners, aircraft manufacturers, and operators. The designator represents the value for the communication ET after which the initiator is required to revert to an alternative procedure. The RCP specifications are applied to achieve the performance required of the communication process and may support aircraft separation minima.

2.15.2 RCP Parameters. The following describes the RCP parameters:

1. RCP Transaction Time. An RCP parameter that specifies the maximum time for the completion of a proportion of operational communication transactions after which the initiator should revert to an alternative procedure. Two values are specified:

• RCP Transaction Time (TT). The maximum nominal time within which 95 percent of operational communication transactions is required to be completed; and

• RCP (ET). The maximum time for the completion of the operational communication transaction, after which the initiator is required to revert to an alternative procedure.

2. RCP Continuity (RCP C). The minimum proportion of operational communication transactions to be completed within the specified RCP transaction time, given the service was available at the start of the transaction.

3. RCP Availability (RCP A). The required probability that an operational communication transaction can be initiated.

4. RCP Integrity (RCP I). The required probability that an operational communication transaction is completed with no undetected errors.

Note: While RCP I is defined in terms of the “goodness” of the communications capability, it is specified in terms of likelihood of occurrence of malfunction on a per flight hour basis (e.g., 10-5), consistent with RNAV/RNP specifications.

Figure 2-7. Actual Communications Performance (ACP)

2.15 RCP and RSP Specifications Supporting ATM Operations. › 2.15.3 RCP Framework and Actual Communication Performance (ACP).

2.15.3 RCP Framework and Actual Communication Performance (ACP). In Figure 2-7, Actual Communications Performance (ACP), the combined uplink and downlink performance of ground systems, communication service, and aircraft systems is the Actual Communication Technical Performance (ACTP). Pilots and controllers should respond as soon as possible as part of the overall human performance. Human performance combined with ACTP results in ACP. ACP is an indicator of the operational performance of a communication system which includes the human and technical components. Human performance considers such factors as training, procedures, and human-machine interface (HMI). Technical performance comprises the installed elements of communication performance operating together to meet the intended function. ACP is assessed in the same terms and parameters as an RCP specification, its allocations, and other relevant operational criteria provided by an RCP specification. Operationally, an appropriate level of communication performance is required for aircraft systems, communications networks, and ground systems.

Note: In ICAO documentation, pilot response time is called Pilot Operational Response Time (PORT).

Figure 2-8. RCP 240 Illustration

2.15.4 RCP 240 Illustration. As illustrated in Figure 2-8, RCP 240 Illustration, the controller sends a data link communication message through the ATSU via the CSP to the aircraft. The Required Communication Technical Performance (RCTP) is the overall time for the communication to travel from the ATSU to the flight deck and return excluding human response time. RCTP should be less than or equal to 150 seconds for 99.9 percent of the operational time (ET) and must be less than or equal to 120 seconds for 95 percent of the nominal time (TT). The message arrives at the flight deck and the pilot should respond as soon as possible (i.e., ROGER (DM3)/WILCO (DM0), UNABLE (DM1), or STANDBY (DM2)). The pilot responds to the message and it travels back to the ATSU.

2.15 RCP and RSP Specifications Supporting ATM Operations. › 2.15.5 RCP 240 Specification Tables.

2.15.5 RCP 240 Specification Tables. Table 2-4, RCP 240 Transaction Time and Continuity Allocations–CPDLC, shows Transaction Time and Continuity allocations from the sender (controller) to responder (pilot) and back to sender (controller). RCTP consists of the ATSU system, network, and the aircraft system. Table 2-5, RCP 240 Availability Criteria (Aircraft System), provides the aircraft system availability criteria. Table 2-6, RCP 240 Integrity Criteria (Aircraft System), provides the integrity criteria for the aircraft system.

Table 2-4. RCP 240 Transaction Time and Continuity Allocations—CPDLC

ACP Controller ATSU system

Network Aircraft

system

Pilot Response

Aircraft

system

Network ATSU system

Controller

99.9% (ET) PC/ATSU (30) PATSU(15) PNET(120) PAIR(15) 60 PAIR(15) PNET(120) PATSU(15) PC/ATSU (30)

95% (TT) PC/ATSU (30) PATSU(10) PNET(100) PAIR(10) 60 PAIR(10) PNET(100) PATSU(10) PC/ATSU (30)

Table 2-5. RCP 240 Availability Criteria (Aircraft System)

Availability Parameter Efficiency Safety Compliance Means

Availability – aircraft (AAIR) N/A 0.999 Analysis, architecture, design, pre-implementation demonstration

Table 2-6. RCP 240 Integrity Criteria (Aircraft System)

Integrity Parameter Integrity Value Compliance Means

Integrity (I) Malfunction = 10-5 per flight hour

Analysis, safety requirements, development assurance level (e.g. Level C software) commensurate with integrity level, pre-implementation demonstration.

2.15 RCP and RSP Specifications Supporting ATM Operations. › 2.15.7 RCP 400 Specification Tables.

Figure 2-9. RCP 400 Illustration

2.15.6 RCP 400 Illustration. As illustrated in Figure 2-9, RCP 400 Illustration, the controller sends a data link communication message through the ATSU through the CSP to the aircraft. The RCTP is the overall time for the communication to travel from the ATSU to the flight deck and return excluding human factors. RCTP should be less than or equal to 310 seconds for 99.9 percent of the operational time (ET) and must be less than or equal to 260 seconds for 95 percent of the nominal time (TT). The message arrives at the flight deck and the pilots should respond as soon as possible (i.e., ROGER (DM3)/WILCO (DM0), UNABLE (DM1), or STANDBY (DM2)). The pilot responds to the message and it travels back to the ATSU.

2.15.7 RCP 400 Specification Tables. Table 2-7, RCP 400 Transaction Time and Continuity Allocations—CPDLC, shows Transaction Time and Continuity allocations from the sender (controller) to responder (pilot) and back to sender (controller). RCTP consists of the ATSU system, network, and the aircraft system. Table 2-8, RCP 400 Availability Criteria (Aircraft System), provides the availability criteria for the aircraft system. Table 2-9, RCP 400 Integrity Criteria (Aircraft System), provides the integrity criteria for the aircraft system.

2.16 Required Surveillance Performance (RSP). › 2.16.2 RSP Concept.

Table 2-7. RCP 400 Transaction Time and Continuity Allocations—CPDLC

ACP Controller ATSU system

Network Aircraft

system

Pilot Response

Aircraft

system

Network ATSU system

Controller

99.9% (ET)

PC/ATSU (30) PATSU(15) PNET(280) PAIR(15) 60 PAIR(15) PNET(280) PATSU(15) PC/ATSU (30)

95% (TT)

PC/ATSU (30) PATSU(10) PNET(240) PAIR(10) 60 PAIR(10) PNET(240) PATSU(10) PC/ATSU (30)

Table 2-8. RCP 400 Availability Criteria (Aircraft System)

Availability Parameter Efficiency Safety Compliance Means

Availability – aircraft (AAIR) N/A 0.999 Analysis, architecture, design, pre-implementation demonstration

Table 2-9. RCP 400 Integrity Criteria (Aircraft System)

Integrity parameter Integrity value Compliance means

Integrity (I) Malfunction = 10-5 per flight hour

Analysis, safety requirements, development assurance level (e.g. Level C software) commensurate with integrity level, pre-implementation demonstration.

2.16 Required Surveillance Performance (RSP).

2.16.1 Background. In the past, surveillance over oceanic and remote continental areas was limited to pilot position reports via HF radio. When crossing a compulsory reporting point, the pilot would contact the ATSU via a radio operator and report: identification, position, time, altitude, next PR point, name of succeeding reporting point, and remarks. Once the aircraft entered a radar environment, pilot reports were eliminated. Today, along with voice pilot position reports, surveillance in oceanic and remote continental airspace is accomplished much more accurately through the use of ADS-C. As with CPDLC, ADS-C requires certain performance requirements for operational surveillance in support of specific ATM functions. This includes the transmission of aircraft position, velocity and intent with a specified precision, accuracy and update rates. In combination with RCP and RNP, RSP enables the efficient use of airspace by allowing reduced lateral and along-track separation of aircraft by supplying accurate and frequent updates of aircraft position.

2.16.2 RSP Concept. The concept of RSP relates to the surveillance component and complements RNP and RCP. A collective set of performance measures are established to ensure overall communication transactions and surveillance data deliveries are suitable for certain surveillance related goals. For example, the surveillance goal may be to achieve 30 nautical miles (NM) lateral and 30 NM along-track separation in oceanic

2.16 Required Surveillance Performance (RSP). › 2.16.4 RSP Parameters.

airspace. RSP is operationally derived and not based on any specific techniques, aircraft technologies, or architecture.

2.16.3 RSP Specification. An RSP specification is identified by a designator (e.g., RSP 180) in order to simplify the designator naming convention and to make the RSP Data Operational Overdue Time (OT) readily apparent to airspace planners, aircraft manufacturers and operators. The designator represents the value for the surveillance data delivery time when the surveillance data delivery is considered overdue. RSP specifications are applied to airspace based on specific objectives (e.g., the performance required of the surveillance process used to support particular separation minima). The RSP specification is a set of requirements/operational parameters for ATS provision and associated ground equipment, aircraft capability, and operations needed to support performance-based surveillance. Surveillance performance requirements are included and allocated to system components (Required Surveillance Technical Performance (RSTP)). It includes surveillance data delivery time, continuity, availability, integrity, and safety. A specified RSP specification is intended to define the surveillance performance required of a surveillance process to support a particular ATM function. RSP specification is applied to the airspace, route, or procedure based on the most stringent RSP specification of the required ATM functions.

2.16.4 RSP Parameters. RSP include the accuracy of the reported position, the latency in reporting the position to the controller, and the integrity, availability, and continuity of the surveillance data. The following describes the RSP parameters:

1. RSP Surveillance Data Transit Time. The maximum time for the reception of the surveillance data after which the controller should revert to an alternative procedure.

2. RSP Continuity. The minimum proportion of surveillance data delivery to be completed within the specified RSP surveillance data delivery time, given the service was available at the start of the delivery.

3. RSP Availability. The required probability that surveillance data can be provided.

4. RSP Integrity. The required probability that surveillance data delivery is completed with no undetected errors.

2.16 Required Surveillance Performance (RSP). › 2.16.6 RSP 180 Specification Tables.

Figure 2-10. RSP 180 Illustration

2.16.5 RSP 180 Illustration. In Figure 2-10, RSP 180 Illustration, the ATSU establishes an event contract with the aircraft with specific allocations described below:

1. From 1 to 2 (Aircraft). The aircraft reaches the particular event and is required to respond within 5 seconds or less 99.9 percent of the operational time (OT) and less than or equal to 3 seconds 95 percent of the nominal delivery time (DT).

2. From 2 to 3 (CSP). The signal is then transmitted through the communication service provider (CSP) network. This action must occur within 170 seconds or less for 99.9 percent of the OT and less than or equal to 84 seconds 95 percent of the DT.

3. From 3 to 4 (ATSU). From the (CSP) this message is sent through the ATSU which has a required performance of less than or equal to 5 seconds for 99.9 percent of the time and less than or equal to 3 seconds for 95 percent of the time. The total communication from the event to the controller must be less than or equal to 180 seconds with 99.9 percent probability (OT) and less than or equal to 90 seconds with 95 percent probability (DT).

2.16.6 RSP 180 Specification Tables. Table 2-10, RSP 180 Surveillance Data Delivery and Continuity Allocations—ADS-C, shows allocations for Required Surveillance Monitoring Performance/Required Surveillance Technical Performance (RSMP/RSTP) consisting of the aircraft system, network and ATSU. Table 2-11, RSP 180 Availability Criteria (Aircraft System), provides the availability criteria for the aircraft system.

Table 2-12, RSP 180 Integrity Criteria (Aircraft System) provides the integrity criteria for the aircraft system.

Table 2-10. RSP 180 Surveillance Data Delivery and Continuity Allocations—ADS-C

RSMP/RSTP Aircraft system Network ATSU

99.9% (OT) 5 170 5

95% (DT) 3 84 3

Table 2-11. RSP 180 Availability Criteria (Aircraft System)

Availability Parameter Efficiency Safety Compliance Means

Availability – aircraft (AAIR) N/A 0.999 Analysis, architecture, design, pre-implementation demonstration

Table 2-12. RSP 180 Integrity Criteria (Aircraft System)

Integrity parameter Integrity value Compliance means

Integrity (I) Malfunction = 10-5 per flight hour

Analysis, safety requirements, development assurance level (e.g. Level C software) commensurate with integrity level, pre-implementation demonstration.

2.16 Required Surveillance Performance (RSP). › 2.16.8 RSP 400 Specification Tables.

Figure 2-11. RSP 400 Performance

2.16.7 RSP 400 Illustration. In Figure 2-11, RSP 400 Performance, the ATSU establishes an event contract with the aircraft with specific allocations described below.

1. From 1 to 2 (Aircraft). The aircraft reaches the particular event and is required to respond within 30 seconds or less 99.9 percent of the OT and less than or equal to 15 seconds 95 percent of the DT.

2. From 2 to 3 (CSP). The signal is then transmitted through the CSP network. This action must occur within 340 seconds or less for 99.9 percent of the OT and less than or equal to 270 seconds 95 percent of the DT.

3. From 3 to 4 (ATSU). From the CSP this message is sent through the ATSU which has a required performance of less than or equal to 30 seconds for 99.9 percent of the time and less than or equal to 15 seconds for 95 percent of the time. The total communication from the event to the controller must be less than or equal to 400 seconds with 99.9 percent probability (OT) and less than or equal to 300 seconds with 95 percent probability (DT).

2.16.8 RSP 400 Specification Tables. Table 2-13, RSP 400 Surveillance Data Delivery and Continuity Allocations—ADS-C, shows allocations for Required Surveillance Monitoring Performance/Required Surveillance Technical Performance (RSMP/RSTP) consisting of the aircraft system, network and ATSU. Table 2-14, RSP 400 Availability Criteria (Aircraft System), provides the availability criteria for the aircraft system. Table 2-15, RSP 400 Integrity Criteria (Aircraft System), provides the integrity criteria for the aircraft system.

2.17 High Frequency Data Link (HFDL). › 2.17.1 HFDL Applications.

Table 2-13. RSP 400 Surveillance Data Delivery and Continuity Allocations—ADS-C

RSMP/RSTP Aircraft system Network ATSU

99.9% (OT) 30 340 30

95% (DT) 15 270 15

Table 2-14. RSP 400 Availability Criteria (Aircraft System)

Availability Parameter Efficiency Safety Compliance Means

Availability – aircraft (AAIR) N/A 0.999 Analysis, architecture, design, pre-implementation demonstration

Table 2-15. RSP 400 Integrity Criteria (Aircraft System)

Integrity parameter Integrity value Compliance means

Integrity (I) Malfunction = 10-5 per flight hour

Analysis, safety requirements, development assurance level (e.g. Level C software) commensurate with integrity level, pre-implementation demonstration. The aircraft end system shall be capable of detecting errors that would result in corruption, introduced by the communication service.

2.17 High Frequency Data Link (HFDL). Over the past few decades HF has provided an effective means of voice communication over long distance in oceanic and remote continental airspace. HF communication is no longer restricted to voice and provides another means of sending and receiving digital communication. HFDL augments existing VHF and satellite communications (SATCOM) (i.e., CPDLC and ADS-C) data link communication systems. A subnetwork of 15 HFDL ground stations extends worldwide communication coverage beyond that of VHF data link communication subnetworks.

2.17.1 HFDL Applications. HFDL subnetwork provides communication to both ATSU and AOC in oceanic and remote continental airspace and can be used for:

1. Non-SATCOM equipped aircraft with a long-range, cost-effective data link communication capability,

2. Data link communication in polar regions where geostationary satellite connections may not exist or be degraded, and

3. A back-up means of data link communication for SATCOM (CPDLC and ADS-C) equipped aircraft.

Chapter 2. Data Link Communication Overview › 2.18 Future U.S. Domestic Airspace Data Link Communication Services.…

2.17.2 Ionosphere HF Disturbance and Reliability. HF is subject to temporary signal distortion due to changes in the ionosphere layer shape and density. Because of multiple HFDL ground stations, ionosphere disturbances are less frequent than in the early days of HF voice. Modern aircraft HFDL systems automatically search for the best available frequency from all HFDL operational ground station frequencies. Once a suitable frequency is found, the aircraft establishes a connection by sending a logon/notification message to the ground station. A logon/notification confirmation uplink is established enabling the pilot to send data.

Note: Monitoring data have shown that HFDL does not meet RCP 240/RSP 180.

2.18 Future U.S. Domestic Airspace Data Link Communication Services. Figure 2-12 depicts future plans for data link communication services. Though this planning diagram is subject to change, it generally provides a preview of expanding data link services in the next few years. This is added to the AC to enable operators planning upgrades in pace with future technology and upcoming data link communication services.

Figure 2-12. Data Communication Services Strategy

2.19 Data Communication Services Strategy. › 2.19.2 Speeds.

2.19 Data Communication Services Strategy. Segment 1 in Figure 2-12 consists of two phases.

2.19.1 Tower Services and En Route Services. Segment 1, Phase 2 (S1P2) services will be delivered in two stages, “initial” services and “full” services. S1P2 en route services are expected to begin in 2019 and are planned to leverage existing Phase 1 FANS 1/A aircraft and expand Phase 1 infrastructure to deliver CPDLC services in the U.S. domestic en route airspace. Listed below are en route initial and full services:

1. En Route Initial Services. The initial services in S1P2 will include the following:

• Transfer of communications,

• Initial check-in,

• Altimeter settings,

• Altitudes,

• Speed (limited),

• Crossing Restrictions (limited),

• Airborne reroutes/go button,

• Controller initiated reroutes (limited), and

• Direct-to-fix (initial).

2. En Route Full Services. With the continuation of S1P2, en route full services will include (see the following paragraphs for descriptions of some initial and full service features):

• Controller initiated routes,

• Crossing restrictions,

• Direct-to-fix,

• Advisory messages, and

• Holding instructions.

Note: The full services of speed, stuck microphone, adapted arrivals, and beacon codes are deferred until further notice.

2.19.2 Speeds.

1. Initial Services. The controller can issue UM61 CROSS (position) AT AND MAINTAIN (altitude) AT (speed).

2. Full Services (Deferred). The controller will be able to:

• Issue speed clearance providing the pilot with instructions to maintain a speed in Mach number or indicated airspeed,

2.19 Data Communication Services Strategy. › 2.19.8 Adapted Arrivals (Deferred).With full service, the controller…

• Assign speeds of greater than or less than specific values, and

• Instruct the pilot to resume normal speed or to maintain present speed. The pilot will be able to request a speed clearance.

2.19.3 Crossing Restrictions. Initially, the controller will be able to use two crossing restriction message elements to instruct the pilot to cross a specific fix at a specific altitude and, if desired, at a specific speed. With full service, the controller will have considerably more flexibility in composing crossing restriction clearances. For example, the controller will be able to clear an aircraft to cross a specific fix at a specific time and have the option of entering a crossing restriction.

2.19.4 Routes. Initially, the pilot will be able to DM22 REQUEST DIRECT TO (position). The controller will be able to issue route clearances, such as UM74 PROCEED DIRECT TO (position), UM79 CLEARED TO (position) VIA (route clearance), UM80 CLEARED (route clearance), and UM83 AT (position) CLEARED (route clearance). With full service, the controller’s workstation will be enhanced to support entry from the Radar (R) and Radar Associate (RA) positions and permit entry of route offsets with additional message elements.

2.19.5 Advisory. Air Traffic personnel issue advisory messages to aircraft on a routine basis. Examples include dynamic airport information (runway closures, runway visual range, braking action, etc.), convective significant meteorological information (SIGMET), Central Weather Advisories (CWA), Pilot Weather Reports (PIREP), weather displayed on the controller’s scope, and current ride reports. CPDLC will allow the controller to send a limited set of advisory messages to the aircraft on a case-by-case basis or to all aircraft with which the controller has a CPDLC connection. Advisory messages such as SIGMETs and CWAs, which must be broadcast to all aircraft on frequency, will still need to be verbally broadcast in a mixed equipage environment. However, advisory messages that are issued to individual aircraft, such as dynamic airport information, displayed weather, PIREPS, and current ride reports are excellent candidates for automating. S1P2 CPDLC services will only support ride reports and free text messages created at the sector. The messages will be provided to the controller to send to the appropriate aircraft. In addition to freeing the controller from verbally delivering the advisory, CPDLC also allows positive confirmation that affected aircraft have received the information.

2.19.6 Holding Instructions. The controller may be directed to hold all arrivals for a particular airport. With full service, the controller will be able to send a CPDLC message UM91 HOLD AT (position) MAINTAIN (altitude) INBOUND TRACK (degrees) (direction) TURN LEG TIME (leg type).

2.19.7 Stuck Microphone (Deferred). With full service, the controller will be able to instruct the pilot to check their microphones.

2.19.8 Adapted Arrivals (Deferred).With full service, the controller and pilot will be able to use CPDLC to execute adapted arrival procedure. The adapted procedure contains both lateral and vertical aircraft maneuvers and provides greater efficiency for users.

2.19 Data Communication Services Strategy. › 2.19.9 Beacon Codes (Deferred).

2.19.9 Beacon Codes (Deferred). As aircraft transition in U.S. domestic airspace from one facility to another, there is the possibility of beacon code duplication. Often this happens when there is significant traffic and/or delays in the system. It is also prevalent at facilities which border foreign airspace. Today, when this conflict occurs, En Route Automation Modernization (ERAM) will assign the aircraft a new code and notify the controller, who then verbally issues it to the pilot. With CPDLC, the FAA ground system will automatically send a UM with the new code to the aircraft at the appropriate time with no controller involvement. The controller will also be able to manually compose and send a beacon code message if needed.

Chapter 3. AIRCRAFT ELIGIBILITY › 3.3 Statement of Compliance (SOC).

CHAPTER 3. AIRCRAFT ELIGIBILITY

3.1 Introduction. This chapter provides guidance on how operators can determine if their aircraft data link system is compliant and eligible for operational use. This AC does not address design approval or installation of data link systems. For airworthiness guidance, refer to AC 20-140( ), Guidelines for Design Approval of Aircraft Data Link Communication Systems Supporting Air Traffic Services (ATS).

3.2 Aircraft Eligibility. The Airplane Flight Manual (AFM) should identify the following for data link communication eligibility:

1. Interoperability,

2. Subnetwork, and

3. Aircraft performance.

Note: Descriptions of the data link services are provided for a given airspace or operation. For example, in the United States, departure clearance (Controller-Pilot Data Link Communication–Departure Clearance (CPDLC-DCL)) service requires the aircraft to be interoperable with Future Air Navigation Systems (FANS)-1/A(+), to use either the Very High Frequency (VHF) Data Link (VDL) Mode 0/A or VDL Mode 2 subnetwork, and to not have any prescribed aircraft performance requirements. Operators should refer to the requirements defined by the Air Traffic Service Unit (ATSU) for each operation. A summary of typical operational requirements is provided in Chapter 5, Operational Use of Data Link Communications, of this AC.

3.3 Statement of Compliance (SOC). Due to the complexity of the criteria to determine eligibility, the operator must obtain a statement of compliance from the entity that owns the design approval for their data link installation. This may be the aircraft manufacturer, the operator, the manufacturer of the data link system, or another party. The statement of compliance should be provided in the AFM, AFM Supplement, or other acceptable document. Table C-3, Preferred Original Equipment Manufacturer Annotation, provides an example of a statement of compliance. The statement of compliance must indicate the aircraft data link system meets the aircraft-allocated requirements of Required Communication Performance (RCP) and Required Surveillance Performance (RSP) specifications.

Note: For a FANS 1/A CPDLC and Automatic Dependent Surveillance-Contract (ADS-C) aircraft system, RTCA DO-306/European Organization for Civil Aviation Equipment (EUROCAE) ED-122, Safety and Performance Standard for Air Traffic Data Link Services in Oceanic and Remote Airspace (Oceanic SPR Standard), is equivalent to RCP 240, RCP 400, RSP 180, and RSP 400 specifications. For an Aeronautical Telecommunications Network (ATN) Baseline 1 (B1) or FANS 1/A CPDLC aircraft system, RTCA DO-290/ED-120, Safety and Performance Requirements Standard for Air Traffic Data Link

3.3 Statement of Compliance (SOC). › 3.3.3 Subnetwork.

Services in Continental Airspace (Continental SPR Standard), provides performance criteria for the EUR Region.

3.3.1 Alternate Means of Compliance for No SOC. In lieu of the SOC stated in the AFM, AFM Supplement, or other acceptable documentation, operators may provide a detailed submission to the FAA validating that the aircraft’s current system meets the RCP/RSP applicable requirements. As a minimum, this submission should include information on avionics continuity, integrity, availability, and safety and monitoring/alerting requirements (refer to RTCA DO-306/ED-122). Equipment manufacturer support should be solicited to acquire suitable documentation.

3.3.2 Interoperability. The operator must confirm the interoperability of their aircraft data link system (interoperability requirements standards (INTEROP) designators are described in Table 2-2, Interoperability Designators and Descriptions). The statement of compliance must indicate the INTEROP and a reference to the definition of that INTEROP. Aircraft Communications Addressing and Reporting System (ACARS) ATS, FANS 1/A, FANS 1/A+, and ATNB1 INTEROP designators, and/or the compliance statement, must reference AC 20-140 or later revision. For the ATN Baseline 2 (B2) INTEROP designator, the compliance statement must reference AC 20-140C or later revision.

3.3.2.1 In U.S. domestic en route airspace, for operations supported by FANS 1/A(+) data link communication systems, the avionics system must have “push to load” capability into the navigation system whenever a routing change (e.g., uplink message (UM)79, UM80, and UM83) is received.

Note: Operators using an alternate means of compliance for “push to load” will not be permitted once full services are implemented. “Full services” require fully integrated (“push to load”) avionics. For a description of “Full Services,” see Figure 2-12, Data Communication Services Strategy.

3.3.3 Subnetwork. The operator must confirm the subnetwork capability of their aircraft (subnetworks are described in paragraph 2.2.2). The statement of compliance must indicate the subnetworks that are supported and a reference to the definition of the subnetworks. The compliance statement must reference AC 20-140 or later for any of the following subnetworks:

• VDL M0/A,

• VDL M2,

• High Frequency Data Link (HFDL),

• Inmarsat, and

• Satellite communications (SATCOM) Iridium (Short Burst Data (SBD)).

Note: For aircraft utilizing Inmarsat (SwiftBroadband (SBB)), the SOC must reference AC 20-140C or later.

Chapter 3. AIRCRAFT ELIGIBILITY › 3.4 Configuration Control.

3.3.4 VDL M2 Requirements for U.S. Domestic En Route. The VDL M2 requirements include aircraft that are equipped with VDL Mode 2 equipment approved to Technical Standard Order (TSO)-C160a, Very High Frequency (VHF) Digital Link (VDL) Mode 2 Communications Equipment, (see Note 1 below for details) or later that is capable of tuning to more than one VDL M2 channel.

Note 1: Minimum performance standard of TSO-C160 does not include the capability for the Communications Management Unit (CMU) (Avionics Architecture Class W and Z) or VDL M2 Radio (Avionics Architecture Class X) to tune to more than one VDL M2 channel. The above equipment is capable of tuning to only one VDL M2 channel (i.e., 136.975 MHz). The minimum performance standard of TSO-C160 for VDL M2 Radio (Avionics Architecture Class V or Y) contains the capability to support VDL Mode 2 multi-frequency operation when integrated with a CMU (Avionics Architecture Class W and Z) that supports VDL M2 multi-frequency according to TSO-C160a.

Note 2: The FAA accepts the use of VDL M0/A en route when VDL M2 communications are lost, if the aircraft is equipped with a properly functioning VDL M2 radio before starting the flight or dispatching. An alternate subnetwork may be used provided it complies with paragraph 4.6.2. Table C-1, Summary of Airspace Requirements, provides a summary of airspace requirements.

3.3.5 Performance Data for Compliance. The operator should evaluate the demonstrated performance of their aircraft data link system as provided by the FAA and other Air Navigation Services Providers (ANSP) as part of the ANSP monitoring programs. FAA monitoring data is available for initial and continuous compliance and operator data may be acceptable for initial data link eligibility. Actual Communications Performance (ACP) of the CPDLC two-way communications and Actual Surveillance Performance (ASP) of the ADS-C are evaluated against respective RCP and RSP specification standards. This data should be included to quantify support of the aircraft performance portion of the data link eligibility. If no performance data is available, then initial compliance for applicable airspace will be based on the SOC with performance being monitored as data is collected. (See Chapter 6, Performance Monitoring.)

Note 1: For fleet aircraft, records for every tail number are not necessary provided that all the aircraft have the same data link communication configuration. Operators with a single aircraft may meet the above requirement using records of other aircraft with the same make, model, and series (M/M/S) and the same data link communication configuration.

Note 2: RCP and RSP performance data is not required for aircraft operating only in U.S. domestic airspace.

3.4 Configuration Control. Operators should maintain their aircraft in an avionics configuration which has been shown to provide acceptable data link communication performance. A list of recommended avionics is available at http://dcis.harris.com/newoperator-documents.

3.5 Maintenance. › 3.5.2 Subnetwork Configuration for Route Coverage.

3.5 Maintenance. The operator is responsible for all maintenance of data link communication systems. Maintenance procedures for data link communications are approved or accepted as part of an operator’s initial maintenance manual approval or as a revision to that manual.

Note: Maintenance facilities conducting Supplemental Type Certificate (STC) modifications must coordinate Master Minimum Equipment List (MMEL)/minimum equipment list (MEL) changes that include all data communications equipment with the Aircraft Evaluation Group (AEG). The Original Equipment Manufacturer (OEM) or the holder of installation approval for the aircraft (e.g., STC holder) must demonstrate compliance with the criteria in this AC. An STC for additional installed items must document any applicable MEL relief.

3.5.1 System Alteration (Including Software Updates). Operators must evaluate alterations to the aircraft and identify any changes to aircraft eligibility. The owner of the design approval for the alteration must confirm the alteration did not affect the data link system. If the alteration affected the data link system, the owner of the design must provide a statement of compliance to the associated INTEROP, subnetworks and performance standards. Operators must determine aircraft eligibility after each alteration.

3.5.2 Subnetwork Configuration for Route Coverage. The operator must ensure communication coverage capability of their aircraft’s subnetwork for the route to be flown (see paragraph 4.1.3). For adequate coverage, operators may have to adjust their aircraft’s media management parameters (e.g., where the system automatically switches from VDL to SATCOM). Operators have experienced unacceptable performance transitioning airspace with marginal VDL coverage because the aircraft tries to maintain or reestablish a VDL connection. Some States may also limit the subnetworks that can be used for operation.

4.1.2 CSP and Operator Arrangements. › 4.1.2.4 RCP Allocation Requirements.

CHAPTER 4. COMMUNICATION SERVICE PROVIDERS (CSP)

4.1 CSP for Oceanic and Remote Continental Operations. For oceanic and remote continental operations using data link communications, operators are responsible for ensuring their CSP meets the minimum specifications of this chapter. The operator/CSP agreement must include these requirements in addition to monitoring their performance as addressed in Chapter 6, Performance Monitoring.

4.1.1 Substandard Performance. If a CSP fails to satisfy the allocated requirements, the operator should not file or use the associated performance standard until the problem is resolved. An exception is allowed for performance below the 99.9 percent operational transaction time which permits the operator to continue to operate at the 95 percent nominal transaction time or greater while investigating the issue for corrective action.

4.1.2 CSP and Operator Arrangements. Operators must ensure the services they have arranged with their CSP(s) include:

1. Failure notification,

2. Recording data link messages,

3. CSP integrity,

4. Compliance with CSP allocations for Required Communication Performance (RCP)/Required Surveillance Performance (RSP), and

5. Adequate subnetwork coverage for the route flown.

4.1.2.1 Failure Notification. The CSP should notify the operator and any affected Air Traffic Service Units (ATSU) of any failure condition that may impact data link communication operations (such as coverage or performance). This includes when a CSP holds an agreement with an aircraft operator but not with the affected ATSU.

4.1.2.2 Recording Data Link Messages. The operator should ensure that they have access to communication and surveillance data sent or received to their aircraft for at least 30 days. The CSP(s) should retain records for at least 30 days to allow for accident/incident investigation purposes. The operator or CSP should make these records available for air safety investigative purposes on request.

4.1.2.3 CSP Integrity. The CSP must pass messages without manipulating the information protected by error detection codes used by the aircraft system and the ATSU. In particular, the CSP must not reconstitute or regenerate any of the error detection codes.

4.1.2.4 RCP Allocation Requirements. The operator must ensure the CSP satisfies the allocated requirements for any RCP used by the operator. The CSP has two points of demarcation with an ATSU domain consisting of ground router to ground router interface and two signal in space points of demarcation with

4.2 RCP 240 CSP Allocations. › **TT is Transaction Time

aircraft’s data link communication system. The downlink message enters the CSP domain at the first emission of the first bit of the first frame from the aircraft’s data link communication system. For uplink message (UM), it exits the CSP domain at the last emission of the last bit of the last frame to the aircraft’s data link communication system. The Required Communication Technical Performance (RCTP)CSP is the two-way transfer delay from when a message (e.g., UM) is received from the ATSU at the CSP point of demarcation (e.g., enters from the ground domain) until its successful arrival at the CSP’s signal in space point of demarcation. When the message is answered, it arrives at the signal in space CSP point of demarcation and continues the CSP’s ground router to ground router interface back to the ATSU. It includes delay such as propagation delay and retransmissions, as well as subnetwork delays resulting from queueing/flow control, segmentation, processing, ground-network transmission, routing, etc.

4.2 RCP 240 CSP Allocations. The CSP must meet the performance requirements described in Table 4-1, RCP 240 Transaction Time and Continuity Allocations to CSP, and Table 4-2, RCP 240 CSP Availability and Outages Parameters, where RCP 240 has been prescribed on the routes flown by the operator.

Table 4-1. RCP 240 Transaction Time and Continuity Allocations to CSP

Transaction Time Parameter

*ET (sec) 99.9% of messages less than:

(sec)

**TT (sec) C = 95% of

messages less than:

(sec)

Compliance Means

RCTPCSP 120 100 Contract/service agreement terms. See also paragraph 4.1.2.

*ET is Expiration Time **TT is Transaction Time

Table 4-2. RCP 240 CSP Availability and Outages Parameters

Availability Parameter Safety Compliance Means

Availability – CSP (ACSP) 0.999 Contract/service agreement terms

Unplanned outage duration limit (minutes) 10 Contract/service agreement terms

Maximum number of unplanned outages 48 Contract/service agreement terms

Maximum accumulated unplanned outage time (minutes/year)

520 Contract/service agreement terms

Unplanned outage notification delay (minutes) 5 Contract/service agreement terms

4.3 RCP 400 CSP Allocations. The CSP must comply with the performance described in Table 4-3, RCP 400 Transaction Time and Continuity to CSP Allocation, and Table 4-4, RCP 400 Availability and Outages Parameters, along the route to be flown by the operator.

4.3 RCP 400 CSP Allocations. › **TT is Transaction Time

Table 4-3. RCP 400 Transaction Time and Continuity to CSP Allocation

Transaction Time Parameter

*ET (sec) C = 99.9%

of messages less than:

(sec)

**TT (sec) C = 95%

of messages less than:

(sec)

Compliance Means

RCTPCSP 280 240 Contract/service agreement terms See also paragraph 4.1.2.

*ET is Expiration Time **TT is Transaction Time

Table 4-4. RCP 400 Availability and Outages Parameters

Availability Parameter Requirement Compliance Means

Availability – CSP (ACSP) 0.999 Contract/service agreement terms

Unplanned outage duration limit (minutes) 20 Contract/service agreement terms

Maximum number of unplanned outages 24 Contract/service agreement terms

Maximum accumulated unplanned outage time (minutes/year)

520 Contract/service agreement terms

Unplanned outage notification delay (minutes) 10 Contract/service agreement terms

4.4 RSP Allocation Requirements. › 4.4.2 RSP 400 CSP Allocations.

4.4 RSP Allocation Requirements. The operator must ensure the CSP satisfies the allocated requirements for any RSP used by the operator. The Required Surveillance Technical Performance (RSTP)CSP is the one-way transfer delay from when a message is received at the CSP’s signal in space point of demarcation until its successful arrival at the other CSP’s ground router to ground router point of demarcation to the ATSU. It includes delay such as propagation delay and retransmissions, as well as subnetwork delays resulting from queueing/flow control, segmentation, processing, ground-network transmission, routing, etc. Delay is measured from the first bit emission of the first bit of the first frame/data packet from the aircraft’s Data Link Radio to the last bit exiting the CSP domain when it is received by the ground domain (ATSU).

4.4.1 RSP 180 CSP Allocations. The CSP must comply with the performance described in Table 4-5, RSP 180 Data Delivery Time and Continuity Criteria, and Table 4-6, RSP 180 Availability and Outages Parameters.

Table 4-5. RSP 180 Data Delivery Time and Continuity Criteria

Data Delivery Time Parameter

*OT (sec) C = 99.9% of messages

less than:

(sec)

**DT (sec) C = 95% of

messages less than:

(sec)

Compliance Means

RSTPCSP 170 84 Contract/service agreement terms. Pre-implementation demonstration.

*OT is data overdue time (associated with operational continuity) **DT is Delivery Time

Table 4-6. RSP 180 Availability and Outages Parameters

Availability Parameter Safety Compliance Means

Availability – CSP (ACSP) 0.999 Contract/service agreement terms

Unplanned outage duration limit (minutes) 10 Contract/service agreement terms

Maximum number of unplanned outages 48 Contract/service agreement terms

Maximum accumulated unplanned outage time (minutes/year)

520 Contract/service agreement terms

Unplanned outage notification delay (minutes) 5 Contract/service agreement terms

4.4.2 RSP 400 CSP Allocations. The CSP must comply with the performance described in Table 4-7, RSP 400 Data Delivery Time and Continuity Criteria, and Table 4-8, RSP 400 Availability and Outages Parameters.

Chapter 4. Communication Service Providers (CSP) › 4.6 CSP for U.S. Operations. The FAA provides Very High Frequency (VHF)…

Table 4-7. RSP 400 Data Delivery Time and Continuity Criteria

Data Delivery Time Parameter

OT (sec) C = 99.9% of messages

less than:

(sec)

DT (sec) C = 95% of

messages less than:

(sec)

Compliance Means

RSTPCSP 340 270 Contract/service agreement terms. Pre-implementation demonstration.

*OT is data overdue time (associated with operational continuity) **DT is Delivery Time

Table 4-8. RSP 400 Availability and Outages Parameters

Availability Parameter Safety Compliance Means

Availability – CSP (ACSP) 0.999 Contract/service agreement terms

Unplanned outage duration limit (minutes) 20 Contract/service agreement terms

Maximum number of unplanned outages 24 Contract/service agreement terms

Maximum accumulated unplanned outage time (minutes/year)

520 Contract/service agreement terms

Unplanned outage notification delay (minutes) 10 Contract/service agreement terms

4.5 Alternate Means of Compliance. A Performance-based Communication and Surveillance (PBCS) Charter is available as an alternate means of compliance to validate the operator/CSP agreement for performance and services stated in this AC. Operators and CSPs need only to become charter members by following the instructions at http://www.fans-cra.com/. Operators who are seeking an Operations Specification (OpSpec)/Management Specification (MSpec)/Letter of Authorization (LOA) A056, Data Link Communications, authorization and are charter members satisfy their responsibility of ensuring their CSP meets the minimum specifications of this chapter provided that their CSP is also a charter member. Charter members using this alternate means of compliance must remain as charter members or notify their responsible Flight Standards office of their change in status.

Note: A change of charter membership status will affect operational authorization.

4.6 CSP for U.S. Operations. The FAA provides Very High Frequency (VHF) Data Link (VDL) Mode 2 for all data link operations within the domestic United States (except oceanic and remote continental areas, which fall under paragraph 4.1). In addition, the FAA has authorized the use of VDL M0/A for CPDLC-DCL application. Operators

4.6 CSP for U.S. Operations. The FAA provides Very High Frequency (VHF)… › 4.6.2 Alternate Subnetworks.

can use the VDL Mode 2 subnetwork or may participate in CPDLC-DCL using VDL M0/A with no additional responsibilities. If the operator’s aircraft is equipped with a properly-functioning VDL M2 radio before starting the flight or dispatching, the FAA accepts the use of VDL M0/A en route when VDL M2 communications are lost.

4.6.1 Initial CSP Qualification. A CSP planning to offer an alternate subnetwork for data link communications in the United States should contact the FAA Data Communications Program Office. The CSP needs to provide substantiating information to demonstrate their subnetwork satisfies the requirements allocated to the CSP and will need to enter into an agreement with the FAA on the sharing of data, notification of outages, security of communication, and other detailed characteristics. For further information refer to the Data Communications Network Services (DCNS) Alternative Media Description.

4.6.2 Alternate Subnetworks. The FAA allows operators to select an alternate subnetwork other than VDL M2, provided the subnetwork satisfies the required performance allocation and the operator/CSP enters into an agreement to ensure the performance is achieved and maintained. The FAA identifies accepted alternate subnetworks by listing on the Performance-Based Flight Systems Branch (AFS-470) Data Communications (DataComm) website. CSPs will be notified of changes to this list. CSPs must comply with the alternate media performance specifications for VDL Mode 2 shown in Table 4-9, Data Communications Network Services (DCNS) Performance Baseline.

4.6.3 Operator Agreement with CSP. › 4.6.3.2 Data Integrity.

Table 4-9. Data Communications Network Services (DCNS) Performance Baseline

Performance Metric System Requirements

Packet Error Rate (Network Service) 10(-5)

Availability – Reliability, Maintainability, and Availability (Network Service)

0.9999

Mean Time Between Outages (MTBO) – Reliability, Maintainability, and Availability (Network Service)

1,344 Hours

Network Service Restoral Time – Reliability, Maintainability, and Availability

30 Seconds*

En Route Capacity 0.0010 bps per km3

One-Way Latency at 95% (uplink or downlink) < 10 sec

One-Way Latency at 99% (uplink or downlink) < 45 sec

*Reliability, maintainability, and availability restoral time applies except for catastrophic processor failures and force major events, in which case the maximum restoration time must be within 3 minutes.

4.6.3 Operator Agreement with CSP. Operators using an alternate subnetwork qualified by the FAA have similar responsibilities as when using data link communications for oceanic and remote continental operations. The CSP must meet the specifications in paragraphs 4.6.3.1 through 4.6.3.3.

4.6.3.1 Transfer Delay.

1. The CSP uplink transfer delay must be less than or equal to 10 seconds for 95 percent of all ATSU data messages.

2. The CSP downlink transfer delay must be less than or equal to 10 seconds for 95 percent of all ATSU data messages.

3. The CSP uplink transfer delay must be less than or equal to 45 seconds for 99 percent of all ATSU data messages.

4. The CSP downlink transfer delay must be less than or equal to 45 seconds for 99 percent of all ATSU data messages.

4.6.3.2 Data Integrity. The Packet Error Rate at the CSP Network Service Delivery Point (SDP) must be less than 1x10-5. The packet error rate is the number of incorrectly received data packets divided by the number of received packets. A packet is declared incorrectly received if at least one bit is erroneous or if it is delivered to an incorrect recipient. This metric excludes packets lost in transmission due to connection failure or excessive latency, as those are accounted by other metrics.

4.7 CSP Monitoring. › 4.7.1 U.S. Domestic Data Communications. If the CSP performance fails…

4.6.3.3 Reliability, Maintainability, and Availability. The reliability, maintainability, and availability performance requirements presented in this section apply to the specific CSP subnetwork seeking qualification and should not take into account the availability of additional subnetworks in order to achieve the required performance levels. A network service thread includes all equipment between the CSP SDP and aircraft users, excluding any aircraft components. This would include the relevant emitting or receiving ground station antenna(s) as well as transmitting/receiving the necessary radio frequency (RF) signal levels across the entire ordered service volume in question. Signal levels need to account for terrain impacts, as applicable to the service volume in question. For the purposes of availability, utilization of diverse ground station sites and other means of redundancy are included to provide the required level of availability for the ordered service volume.

1. The service availability for each network service thread must be at least 0.9999.

2. The minimum calculated service availability must be measured over the latest 12-month period. Availability is calculated as follows:

• Available Time: Total time during the latest 12-month period the service was under contract.

• Total Outage Time: The total unapproved service interruption or degradation time during the Available Time. It includes any unapproved degradation in which the service failed to meet all performance requirements of this specification. It includes any length of time exceeding the duration of a FAA-approved interruption or degradation.

4.7 CSP Monitoring. For oceanic and remote continental operations and for the use of alternate subnetworks for U.S. data communications, the operator must be aware of their CSP performance. The operator and CSP agreement should address performance monitoring and the performance data as necessary to remain in compliance.

4.7.1 U.S. Domestic Data Communications. If the CSP performance fails to satisfy the allocated requirements, the FAA will notify the CSP and operators. In this case, the alternate subnetwork authorization for operations is suspended and the operator should not file or use the associated performance standard (if prescribed) until the FAA indicates the alternate subnetwork performance is compliant.

Continue reading ↓ 120 of 275 passages shown