Appendix B Table B-2. Example of a Data Link Communication MMEL Provision
N ote 1: The provisions and repair category intervals are intended to grant the operator sufficient relief during the initial stages of the data link communication implementation. This is intended to promote the installation process, as well as support the use of a partial system. Both equipment reliability and operational experience will dictate, what, if any, revision to this MMEL relief should be considered after the installation phase is completed.
Note 2: Operators are responsible for entering the number in the “Number Installed” column of the MEL.
Note 3: Operators are responsible for entering alternate procedures in the MEL comment section or referencing the location of such procedures in their manual system.
Note 4: If MMEL has not been updated for Controller-Pilot Data Link Communication (CPDLC) equipment for aircraft that are issued a Supplemental Type Certificate (STC), the operator is reminded that they must adhere to § 91.213.
Note 5: Special Condition: The MMEL does not provide relief for inoperative data communications equipment at this time and is being reviewed at the Aircraft Evaluation Group (AEG). Should any of the equipment/software fail relative to data link communications, the data equipment/software must be replaced/repaired before the aircraft can take off according to § 91.213(a).
B-2
Appendix C APPENDIX C. SUMMARY OF AIRSPACE REQUIREMENTS C.1 Summary of Airspace Requirements. (Table C-1, Summary of Airspace Requirements.) Each Air Traffic Service Unit (ATSU) providing data link services defines the requirements for their operations (refer to International Civil Aviation Organization (ICAO) Doc 4444, Procedures for Air Navigation Services - Air Traffic Management; ICAO Doc 7030, Regional Supplementary Procedures; ICAO Doc 10037, Global Operational Data Link (GOLD) Manual, ICAO Global Guidelines for Data Link Operations; Aeronautical Information Publications (AIP); and flight information region (FIR) specific bulletins for additional information).
Table C-1. Summary of Airspace Requirements Airspace Service (Operational Use) Aircraft Data Link Communication System (Interoperability) ATSU Provided Subnetwork Operator- Provided Subnetwork Performance Specification U.S.
(Domestic)
CPDLC-DCL service FANS 1/A(+) VDL M2 or VDL M0/A
N/A N/A U.S.
(Domestic) En route data communication services FANS 1/A(+) VDL M2**** VDL M0/A* TBD Continental (Domestic) European data link program ATN B1 VDL M2 N/A N/A Oceanic and Remote Continental Oceanic and remote continental 23 NM lateral or along-track spacing*** FANS 1/A(+) N/A SATCOM (Classic Aero, SBB, or SBD)** RCP 240 RSP 180 Oceanic and Remote Continental 50 NM Longitudinal FANS 1/A(+) N/A SATCOM (Classic Aero, SBB, or SBD)** RCP 240 RSP 180 Oceanic and Remote Continental 30 NM Longitudinal FANS 1/A(+) N/A SATCOM (Classic Aero, SBB, or SBD)** RCP 240 RSP 180 Oceanic and Remote 5 Minute Longitudinal FANS 1/A(+) N/A SATCOM (Classic Aero, SBB, or SBD)** RCP 240 RSP 180 C-1
Appendix C Airspace Service (Operational Use) Aircraft Data Link Communication System (Interoperability) ATSU Provided Subnetwork Operator- Provided Subnetwork Performance Specification Oceanic and Remote Continental N/A FANS 1/A ADS-C N/A SATCOM (Classic Aero, SBB, or SBD)** HFDL N/A Oceanic and Remote Continental/ Domestic N/A ACARS VDL M2 or VDL M0/A SATCOM (Classic Aero, SBB, or SBD)** HFDL N/A Note: Table C-1 asterisks:
* An approval is required to use VDL M0/A for U.S. en route data communications and the operator assumes responsibility for the Communication Service Provider (CSP). The allocation of performance requirements to the CSP is more stringent than the RCP 240 allocation, which is used only to identify the aircraft allocation. See Chapter 4, Communication Service Providers.
** Aircraft typically use VDL M0/A or VDL M2 when in range of ground radios, which is also acceptable. However, an aircraft with only these subnetworks would not be eligible for the oceanic and remote continental operations due to coverage limitations.
*** See ICAO Doc 4444 for more information.
**** Must be tunable (Technical Standard Order (TSO)-C160a or later, Very High Frequency (VHF) Digital Link (VDL) Mode 2 Communications Equipment) with “push to load” capability into the navigation system whenever a routing change is received for operations supported by Baseline 2 (B2) and Future Air Navigation Systems (FANS) 1/A(+) data link communication systems.
C-2
Appendix C Table C-2. Subnetwork Designators Subnetwork Designator Description of Designator VDL M0/A Very high frequency data link – Mode 0/A VDL M2 Very high frequency data link – Mode 2 HFDL High frequency data link SATCOM (Classic Aero) Inmarsat or MT-SAT – Classic Aero satellite communications SATCOM (SBB) Inmarsat – SwiftBroadband satellite communications SATCOM (SBD) Iridium – Short burst data satellite communications Table C-3. Preferred Original Equipment Manufacturer Annotation “The FAA has approved the aircraft data link system to the criteria in AC 20-140C for the following data link capabilities:
Interop Designators: FANS 1/A+ (with automation) ATN B1 B2
ACARS ATS Subnetworks: VDL M0/A/2 SATCOM (Classic Aero, SBD, SBB) HFDL
ACARS ATS Aircraft-Allocated Performance CPDLC: RCP 130, RCP 240, RCP 400 ADS-C: RSP 160, RSP 180, RSP 400 This design approval does not constitute operational authorization.”
C-3
Appendix D APPENDIX D. FLIGHT PLANNING D.1 Filing Required Communication Performance (RCP)/Required Surveillance Performance (RSP) Capabilities. When filing RCP/RSP capabilities, operators must ensure the planned use of associated communication and surveillance capabilities for the flight will be in accordance with regulations, policies, and procedures in control areas for the flight, as published by the applicable States in Aeronautical Information Publications (AIP) (or equivalent publications). Operators should ensure the proper information to denote Performance-based Communication and Surveillance (PBCS) capabilities is included in the International Civil Aviation Organization (ICAO) flight plan.
D.1.1 The following are determinations for proper filing:
1. Presence of relevant serviceable equipment on board the aircraft.
2. Equipment and capabilities commensurate with pilot qualifications.
3. When applicable, appropriate authorizations as described in FAA operations specifications (OpSpec)/management specifications (MSpec)/letters of authorization (LOA).
D.2 Regulatory Basis. Flight planning must be in accordance with the following where applicable:
1. Part 91:
• § 91.169, IFR Flight Plan: Information Required.
• § 91.173, ATC Clearance and Flight Plan Required.
2. Part 121:
• § 121.667, Flight Plan: VFR and IFR: Supplemental Operations.
• § 121.695, Disposition of Load Manifest, Dispatch Release, and Flight Plans:
Domestic and Flag Operations.
• § 121.697, Disposition of Load Manifest, Flight Release, and Flight Plans:
Supplemental Operations.
3. Part 125, § 125.405, Disposition of Load Manifest, Flight Release, and Flight Plans.
D.2.1 Flight Plan Descriptors:
• D1and G1 for Automatic Dependent Surveillance-Contract (ADS-C) (Table D-2, Item 10b Flight Plan Descriptors for Surveillance Equipment);
• J1 through J7 for Controller-Pilot Data Link Communication (CPDLC) (Table D-1, Item 10a Flight Plan COM Descriptors); and
• P1 and P2 for RCP Performance (Table D-1).
D-1
Appendix D Note 1: Refer to ICAO Doc 4444, Procedures for Air Navigation Services – Air Traffic Management, Appendix 2, for flight plan requirements. Also, refer to the FAA Flight Planning Information website.
Note 2: The inclusion of PBCS capability in the filed flight plan indicates that the relevant aircraft equipment comprising the aircraft system is approved and serviceable, the pilot is appropriately trained and qualified, and the operator holds applicable authorization to use the equipment for PBCS operations. If these conditions are not met, then PBCS capability should not be included in the flight plan.
D.3 Example. As a flight plan example, use the following:
If Actual Communications Performance (ACP) meets at least RCP 240 at 95 percent and Actual Surveillance Performance (ASP) meets at least RSP 180 at 95 percent, then the operator approved for RCP 240/RSP 180 may file the following:
• Field 10: “P2.”
• Field 18: “SUR/RSP180.”
D.3.1 If ACP does not meet RCP 240 at 95 percent, then the operator may file for RCP 400 by entering P1 and/or P3 in field 10. If ASP does not meet RSP 180 at 95 percent, then the operator may file for RSP 400 by entering “SUR/RSP400” in field 18.
D.4 Item 10a Descriptors. In Item 10a of the flight plan, operators should insert one of the descriptors, P1-P2, as appropriate, listed in Table D-1, to identify an aircraft’s RCP capability.
D-2
Appendix D Table D-1. Item 10a Flight Plan COM Descriptors Descriptors System E1 FMC WPR ACARS E2 D-FIS ACARS E3 PDC ACARS J1 CPDLC ATN VDL Mode 2 J2 CPDLC FANS 1/A HFDL J3 CPDLC FANS 1/A VDL Mode 0/A J4 CPDLC FANS 1/A VDL Mode 2 J5 CPDLC FANS 1/A SATCOM (Inmarsat) J6 CPDLC FANS 1/A SATCOM (MTSAT) J7 CPDLC FANS 1/A SATCOM (Iridium) P1 CPDLC RCP 400 P2 CPDLC RCP 240 Note: 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.
D.5 Item 10b Descriptors. In Item 10b of the flight plan, operators should insert one of the descriptors, D1 and G1, as appropriate, listed in Table D-2, to identify an aircraft’s RSP capability:
Table D-2. Item 10b Flight Plan Descriptors for Surveillance Equipment Descriptor System D1 ADS-C with FANS 1/A capabilities G1 ADS-C with ATN capabilities D.6 Item 18 RSP Specification. In Item 18 of the flight plan, the aircraft operator should file the RSP capability by inserting the indicator “SUR/” followed by the appropriate RSP specification (e.g., RSP400 or RSP180).
Note: The ATSU unit uses the flight plan information to determine when to apply particular Air Traffic System Management (ATM) operations that are dependent on the capability and to configure the system (e.g., set timer threshold values) for efficient operation when RCP and/or RSP varies.
D-3
Appendix D D.7 Field 18/DAT for CPDLC or Pre-Departure Clearance (PDC). The proposed data link communication “codes” in Field 18/DAT are an optional mechanism for the user to notify FAA automation to generate a CPDLC or PDC.
• Field 10a (Equipage) used to identify aircraft capabilities.
• Field 18 (Other Information) DAT/ codes used to identify flights getting CPDLC or PDC.
• Need to fill in Field 10a in order to get to Field 18 DAT/.
• Field 18 DAT/ codes will include a primary/secondary hierarchy.
Table D-3. PDC and Departure Clearance (DCL) Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations Some aircraft are non-ACARS equipped, and 10a is physical equipage. Still get PDC via other means
(e.g., gate printer).
Optional if currently getting PDC.
PDC only** Not ACARS e quipped but gets PDC via manual means.
Z 1 PDC PDC only** Equipped only for ACARS/PDC. E3 Z 1PDC Optional if currently getting PDC.
PDC only** Equipped for ACARS/PDC and FANS but wants PDC only.
E3J4Jx Z 1PDC Equipped for ACARS/PDC and FANS 1/A or 1/A(+), and possibly other capabilities (Jx).
FANS 1/A & FANS 1/A+ DCL only Equipped for FANS 1/A only for CPDLC-DCL.
E3J4Jx Z 1FANS Identifies U.S. domestic preference for FANS 1/A DCL.
Code number shows priority preference,
(e.g., DCL is primary preference; FANS 1/A DCL is secondary that will be used if primary is unavailable and if feasible).
FANS 1/A & FANS 1/A+ DCL Equipped for ACARS/PDC and FANS with primary/secondary preferences.
E3J4Jx Z 1FANS2PDC * No spaces in actual DAT/ codes.
** No ICAO flight plan change required if user currently gets PDC and does not want DCL. Current PDC designation will be the default.
D-4
Appendix D Table D-4. PDC and En Route Data Link Clearances Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations FANS 1/A & FANS 1/A+ No En Route Arrival Load Issues For flights authorized for en route data link with no en route arrival load issues as well as for ACARS/PDC and
CPDLC-DCL with primary/secondary preferences.
E3J4Jx Z 1FANSE2PDC This code is to be used to obtain CPDLC-DCL and en route clearances with aircraft that have no en route arrival load issues; PDC is secondary that will be used if primary is unavailable and if feasible.
FANS 1/A & FANS 1/A+ With En Route Arrival Load Issues For flights authorized for en route data link with en route arrival load issues as well as for ACARS/PDC and
CPDLC-DCL with primary/secondary preferences.
E3J4Jx Z 1FANSER2PDC This code is to be used to obtain CPDLC-DCL and en route clearances with aircraft that have en route arrival load issues; PDC is secondary that will be used if primary is unavailable and if feasible.
* No spaces in actual DAT/ codes.
D-5
Appendix D Table D-5. PDC Only and En Route Data Link Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations FANS 1/A & FANS 1/A+ No En Route Arrival Load Issues For flights authorized for en route data link with no en route arrival load issues and for PDC service only.
E3J4Jx Z 1PDCFANSE This code is to be used to obtain PDC and CPDLC en route clearances with aircraft that have no en route arrival load issues (No Tower DCL) (see Table D-6).
FANS 1/A & FANS 1/A+ With En Route Arrival Load Issues For flights authorized for en route data link with en route arrival load issues and for PDC service only.
E3J4Jx Z 1PDCFANSER This code is to be used to obtain PDC and CPDLC and en route clearances with aircraft that have en route arrival load issues (No Tower DCL) (see Table D-6).
* No spaces in actual DAT/ codes.
Table D-6. En Route Data Link Clearances Only Operators Using Data Link Communication Capability Field 10a Data Link Communication for Field 18 DAT/* Comments for FANS in U.S. Domestic Operations FANS 1/A & FANS 1/A+ No En Route Arrival Load Issues For flights authorized for en route data link with no en route arrival load issues.
J4
Z FANSE This code is to be used to obtain CPDLC en route clearances with aircraft that have no en route arrival load issues. (No Tower DCL or PDC.)
FANS 1/A & FANS 1/A+ With En Route Arrival Load Issues For flights authorized for en route data link with en route arrival load issues.
J4
Z FANSER This code is to be used to obtain CPDLC en route clearances with aircraft that have en route arrival load issues. (No Tower DCL or PDC.)
* No spaces in actual DAT/ codes.
D-6
Appendix E APPENDIX E. VOICE PHRASEOLOGY Table E-1. Voice Phraseology Related to Controller-Pilot Data Link Communication (CPDLC) From Pilot Condition Voice Phraseology To notify air traffic control (ATC) of a correction to a CPDLC message. (International Civil Aviation Organization.
(ICAO) Doc 4444) DISREGARD CPDLC (message type) MESSAGE, BREAK (correct information or request) To notify ATC of a single CPDLC message failure. (ICAO Doc 4444) CPDLC MESSAGE FAILURE (appropriate information or request) To notify ATC of an aircraft data link system or CPDLC connection failure.
(ICAO Doc 4444) CPDLC FAILURE (requests/notifications) Note: This voice phraseology is included only with the first transmission made for this reason.
Example: CPDLC FAILURE. CONTINUING ON VOICE.
To advise ATC the CPDLC connection is being terminated manually and logon/notification procedure is being initiated with the next Air Traffic Service Unit (ATSU).
DISCONNECTING CPDLC WITH (facility designation). LOGGING ON TO (facility designation) Note: The facility designation is the ICAO four-character facility code or facility name.
To advise ATC that a logon/notification procedure is being initiated following restoration of data link service.
LOGGING ON TO (facility designation) To advise ATC that a delayed CPDLC uplink has been received and to request clarification of the intent of the CPDLC message.
DELAYED CPDLC MESSAGE RECEIVED (requests) E-1
Appendix E Table E-2. Voice Phraseology Related to CPDLC From the ATSU Condition Voice Phraseology To advise all stations or a specific flight of a complete ground system failure and provide further instructions. (ICAO Doc 4444) (ALL STATIONS) CPDLC FAILURE (instructions).
Example:
ALL STATIONS CPDLC FAILURE.
DISCONNECT CPDLC. CONTINUE ON VOICE To instruct the pilot of a single CPDLC message failure. (ICAO Doc 4444) CPDLC MESSAGE FAILURE (appropriate clearance, instruction, information or request) To instruct the pilot of a correction to a CPDLC clearances, instructions, information or requests. (ICAO Doc 4444) DISREGARD CPDLC (message type) MESSAGE, BREAK (correct clearance, instruction, information or request) To instruct all stations or a specific flight to avoid sending CPDLC requests for a limited period of time. (ICAO Doc 4444) (ALL STATIONS) STOP SENDING CPDLC REQUESTS (UNTIL ADVISED) ((reason)) To instruct the pilot to manually initiate a logon/notification to the subsequent ATSU.
DISCONNECT CPDLC THEN LOGON TO (facility designation) Note 1: The (facility designation) is the four character ICAO code.
Note 2: Use this voice phraseology when the CPDLC transfer to an adjacent ATSU has failed.
To advise the pilot prior to the commencement of a CPDLC shutdown and instruct them to continue on voice.
CPDLC WILL BE SHUT DOWN.
DISCONNECT CPDLC. CONTINUE ON VOICE To advise all stations or a specific flight to resume normal CPDLC operations and provide the logon/notification address.
(ALL STATIONS) RESUME NORMAL CPDLC OPERATIONS. LOGON TO (facility designation) E-2