Appendix 5
a. Academic Training Subjects. Basic source document for data link procedures in Pacific Oceanic areas is the Future Air Navigation System (FANS) Operations Manual (FOM), Part 5.
Policy/Procedures applicable to specific flight information regions (FIR) are in the State Aeronautical Information Publication (AIP) and Notices to Airmen (NOTAM).
(1) AC 120-70B, Operational Authorization Process for use of Data Link Communication System, calls for the following areas to be addressed: Acronyms. Source:
FOM Part 2.
(2) General Concepts of Digital and Analog Communications.
(3) Expected Flightcrew Response.
(4) ATS Coordination.
(5) Aircraft Digital or Analog Communication Equipment Components, Displays, Alerts. Sources:
(a) Aircraft manufacturer documents,
(b) Interface with other aircraft systems,
(c) Aircraft Flight Manual (AFM) information,
(d) Minimum equipment list (MEL) provisions,
(e) Data Link Events Reports,
(f) Data Link Malfunction or Irregularity Reports, and
(g) Human Factors-Lessons learned.
b. Operational Use Training:
(1) General requirement,
(2) Simulators,
(3) Computer-Based Instruction (CBI),
(4) Policy on Initial Pilot Evaluation, and
(5) Recurrent Training and Evaluation.
c. Currency (Recency of Experience).
d. Line Checks and Route Checks.
e. Line-Oriented Flight Training (LOFT).
Appendix 6 APPENDIX 6. DATA LINK SYSTEMS AND OPERATING ENVIRONMENT Table-1 provides the criteria for different types of data link systems and operations based on standards. For each type of data link system, a row is provided to assign a label to a particular aircraft capability, and correlate it to the applicable operating environment. The applicable operating environment is characterized by the type of airspace, the capability of the ATS unit and the use for which that aircraft capability is intended. The aircraft label is used in the rotorcraft/aircraft flight manual (R/AFM) to convey the functional and interoperability aspects of the aircraft data link system needed to support operations.
Use Table-1 to identify the applicable operating environment(s) and intended uses for your specific aircraft data link system. An aircraft data link system may support any combination of aircraft labels in the table. For an aircraft data link system that combines Aeronautical Telecommunications Network (ATN) B1 and Future Air Navigation System (FANS) 1/A capabilities that can be used on the same flight, you will need to develop the interoperability standard per paragraph 3.c. in AC 20-140A, Guidelines for Design Approval of Aircraft Data Communications Systems.
Refer to the ICAO Global Operational Data Link Document (GOLD) for the latest description of the intended data link operations. Special attention must be given to Chapter 2 of the GOLD document.
TABLE-1. DEFINITION FOR DIFFERENT TYPES OF DATA LINK SYSTEMS AND
OPERATIONS Operating Environment Row # Aircraft Data Link System Type of Airspace ATS Unit System Capability and Uses Applicable Standards 1 ATN B1 Continental (Domestic) ATN B1 Supplemental ATC communications:
CM application supports DLIC data link service CPDLC application supports ACM, ACL, and AMC data link services Note 1: DCL, DSC, D-ATIS, and FLIPCY data link services are not supported.
DO-290/ED-120, Chg 1 and Chg 2, Continental SPR Standard DO-280B/ED-110B, ATN B1 INTEROP Standard Sub-network standards for VDL M2 (See Table-1a).
2 FANS 1/A+ Continental (Domestic) ATN B1- FANS 1/A Same as Row 1, except:
Uses AFN application for DLIC data link service For CPDLC application, UM 215, TURN [direction] [degrees] is not supported Same as for Row 1, plus:
DO-305/ED-154, FANS 1/A – ATN INTEROP Standard (Applies only to ATS Unit, except see Note 2) DO-258A/ED-100A, FANS 1/A INTEROP Standard
Appendix 6 Note 2: FANS 1/A aircraft will require use of DM67 [free text] to mimic certain message elements per DO-290/ED-120 Chg 1 and 2. See DO-305/ED-154, paragraph 4.2.13.2.
Note 3: In accordance with DO-290/ED-120, Chg 1 and Chg 2, FANS 1/A aircraft will require use of a message latency timer per DO-258A/ED-100A, paragraph 4.6.6.9 and is denoted by a “+” appended to the “FANS 1/A” label.
(Applies only to aircraft) Sub-network standards for VDL M2 (See Table-1a).
3 FANS 1/A+ or FANS 1/A Oceanic and remote FANS 1/A Normal means of ATC communication uses AFN and CPDLC applications for DCPC Eligible for:
RCP 240 operations via any sub-network listed in Table-1a, except for HFDL RCP 400 operations via any sub-network listed in Table-1a.
No RCP operations via any sub-network listed in Table-1a.
Note 4: Aircraft capability that supports multiple RCP type operations needs to include appropriate indications and/or alerts to enable the flightcrew to notify ATC when aircraft equipment failures result in the aircraft’s ability to no longer meet its criteria DO-306/ED-122, Oceanic SPR Standard DO-258A/ED-100A (or earlier versions), FANS 1/A INTEROP Standard Sub-network standards for selected sub-networks. (See Table-1a).
Note: Allows use of one or more sub-networks. See Capability and Uses column for indications, alerts and sub-networks that are eligible for intended operations.
Appendix 6 for any of the RCP types, per DO-306/ED-122, paragraph 5.2.6.a) and
5.2.6.b).
Uses ADS-C application for automatic position reporting. See required performance for ADS-C application per DO-306/ED-122. ADS-C application over HFDL (See Table-1a) not eligible for reduced longitudinal separation.
4 FANS 1/A+ or FANS 1/A Oceanic and remote CADS No CPDLC application Uses ADS-C application for automatic position reporting. See required performance for ADS-C application per DO-306/ED-122.
DO-306/ED-122, Oceanic SPR Standard DO-258A/ED-100A (or earlier version), FANS 1/A INTEROP Standard (Applies only to aircraft).
CADS Common Specification, Version 2.0, approved ICAO NAT FIG/10, Paris, March 29-April 2, 2004 (Applies only to ATS unit) Sub-network standards same as row 3.
5 FMS WPR Oceanic and remote CFRS No CPDLC application Uses FMS WPR application for automatic position reporting. See required performance for FMS WPR application per DO-306/ED-122.
DO-306/ED-122, Oceanic SPR Standard ARINC 702A, Advanced Flight Management Computer System (Applies only to aircraft).
CFRS Common Specification, Version 2.0, approved ICAO NAT FIG/10, Paris, March 29-April 2, 2004 (Applies only to ATS unit).
Sub-network standards same as row 3.
6 FANS 1/A ADS-C Oceanic and remote FANS 1/A or CADS Same as row 4. DO-306/ED-122, Oceanic SPR Standard DO-258A/ED-100A (or earlier version) FANS 1/A INTEROP Standard (If ATS unit is CADS, applies only to Page 3
Appendix 6 aircraft) CADS Common Specification, Version 2.0, approved ICAO NAT FIG/10, Paris, March 29-April 2, 2004 (Applies only to ATS unit when ATS unit is CADS).
Sub-network standards same as row 3.
7 ACARS Continental /Oceanic and remote ACARS Departure clearance or pre-departure clearance.
Data link – automated terminal information service.
Oceanic clearance.
ED85 ED-89 ED-106 A623 Sub-network standards same as row 3.
Note 5: Allows one or more capability. a) through d) are applicable for selected capabilities and uses.
TABLE-1A. DEFINITIONS FOR SUB-NETWORKS Sub-network designator Applicable sub-network standards VDL M0/A A618-6 for air/ground protocol VDL M2 HFDL a) DO-265 Minimum Aviation System Performance Standard (MASPS)
b) A753-3 SATCOM (Inmarsat) a) DO-270A (MASPS)
b) A741P2-7 SATCOM (Iridium) a) DO-270A (MASPS)
b) A741P2-7
c) A761-2