Data Link Communications AC 90 117 and A

Data Link Communications AC 90 -117 and A 056 Op. Spec/MSpec/LOA Presented to: OSWG By: Mark Patterson, ASI, FAA Date: 8 March, 2017 Federal Aviation Administration

Objectives • Timelines • AC Overview • New Content – – – – – CPDLC-DCL vs. PDC CPDLC CVR/FDR Recording Aircraft Eligibility NAS En route Oceanic and Remote Communication Service Provider (CSP) Performance Monitoring Flight Planning • Supplemental Materials • Questions and Answers Federal Aviation Administration 3

ICAO PBCS Implementation occurs on: 29 March, 2018 PBCS approval will be required to be eligible to participate in the following horizontal separation minima in accordance with ICAO PANS-ATM (Doc 4444): Dimension of separation Lateral RSP requirement Separation Minima RCP Associated requirement navigation requirement 180 42. 6 km (23 NM) Performancebased Longitudinal 5 minutes Performancebased Longitudinal 55. 5 km (30 NM) Performancebased Longitudinal 93 km (50 NM) 240 RNP 4 240 RNP 2 RNP 4 RNP 10 180 240 RNP 2 or RNP 4 240 RNP 4 or RNP 10 180 or or Federal Aviation Administration 4

Timeline: Roadmap Federal Aviation Administration 5

AFS-470 Data Comm Projects - 2017 Date Action 27 April* AC 90 -117 Published 31 May A 056 templates and 8900. 1 guidance published 31 May Upload of Data Link Communication Compliance Guide to AFS-470 data comm website 31 May Upload of NAS Data Communication Guide to AFS-470 data comm website 31 May FAA performance monitoring website goes active 1 July Begin version A for AC 90 -117 Federal Aviation Administration 6

AC 90 -117 Publication Process Date Action 6 March - 5 April Public Comment (30 calendar days) 10 April AFS-470 resolve public / internal comments / finalized document 17 April AFS-400 Manager signature 24 April AFS-1 signature 27 April AC published Federal Aviation Administration 7

AC 90 -117 Format 8 Chapters: • • Ch 1: General Ch 2: Data Link Communications Overview Ch 3: Aircraft Eligibility Ch 4: Communication Service Providers (CSP) Ch 5: Operational Use of Data Link Communications Ch 6: Performance Monitoring Ch 7: Training Ch 8: Reports Chapters 3 thru 8 provides complete data communication guidance. Federal Aviation Administration 8

AC 90 -117 Format 7 Appendices: • • A - Foreign Operators B - MEL and MMEL Provisions C - Summary of Airspace Requirements D - Flight Planning E - Voice Phraseology F - CPDLC uplink and downlink tables G - Terminology and Acronyms Federal Aviation Administration 9

New Content • • CPDLC-DCL vs. PDC CPDLC-DCL & “KUSA” NSDA CVR/ FDR Aircraft Eligibility NAS En Route Oceanic and Remote Continental Communication Service Providers (CSP) • Performance Monitoring • Flight Planning • Numerous Diagrams and Tables Federal Aviation Administration 10

CPDLC-DCL vs. PDC CPDLC-DCL No logon required Logon Required Automatically sent directly to FANS equipped Sent to Aeronautical Operational Control (AOC) aircraft over data link communication equipment or other Operator prescribed location after crew logon Delivered to the flight crew by various means, i. e. Delivered over data link communication directly to over ACARS, to the FBO terminal, to the airline the aircraft gate, etc. Depending on the delivery method, may require Never requires a paper copy to be delivered to the a printed copy to be delivered to the aircraft. Does not require data link communication Requires data link communication systems on the equipment to be installed in the aircraft Does not support revised clearances. Revisions Revised clearances can be delivered directly to the must be transmitted via voice frequency aircraft when necessary without restrictions A specific call sign can only be once in an adaptable time period of 12 -18 hours at a No restrictions specific airport Requires clearance to be manually input in to the Clearance can be sent to the avionics system FMS by the flight crew enabling “push to load” via a load prompt. Federal Aviation Administration 11

CPDLC-DCL and “KUSA” NSDA CPDLC-DCL is available at 55 airports: – FANS 1/A (+) via VDL Mode 0/A and/or Mode 2 – Log in using specific airport code (e. g. KMEM) – Departure Clearance “pushed” to aircraft --no need to request clearance – Jun 2017 - “KUSA” will be the common logon address for all CPDLC logons in the U. S. Federal Aviation Administration 12

CVR/FDR Data Link Recording Operators must comply with: – Cockpit voice recorder(s) and flight data recorder(s) regulations: • 14 CFR Parts 91, 125, and 135: – § 91. 609(j), § 121. 359(k), § 125. 227(i), § 135. 151(h). • See FAA In. FO 16004 Federal Aviation Administration 13

Aircraft Eligibility Operators responsibility to determine… Based on: 1. Interoperability 2. Subnetwork 3. Aircraft Performance Federal Aviation Administration 14

Aircraft Eligibility: INTEROP for A 056 eligibility includes: ‒ FANS 1/A (+) with “push to load” automation ‒ FANS 1/A (+) without “push to load” automation • Not eligible for NAS en route ‒ ATN B 1 ‒ B 2 Federal Aviation Administration 15

Aircraft Eligibility: Subnetwork The following are possible subnetworks: – VDL M 0/A • Not eligible for NAS en route – Alternate means of compliance may be possible through CSP – VDL M 2, Single Freq (TSO-160) • Not eligible for NAS en route – VDL M 2, Multi Freq (TSO-160 a or later) – SATCOM (Iridium) – SATCOM (Inmarsat) – HFDL Oceanic/Remote Continental Federal Aviation Administration 16

Aircraft Eligibility: Performance • Initial Aircraft Eligibility is based on: – A Statement of Compliance (SOC) – Demonstrated performance: https: //www. faa. gov/air_traffic/separation_standards/PBCS_Monit oring/ • SOC not available - demo performance data only may be used • Performance not avail – may use identically-equipped aircraft data • SOCs are accomplished by: – Entity that owns the design approval for the aircraft data link installation Federal Aviation Administration 17

Statement of Compliance - example “The FAA has approved the aircraft data link system to the criteria in AC 20 -140 C for the following data link capabilities: Interop Designators: Subnetworks: Aircraft-Allocated Performance FANS 1/A+ (with automation) ATN B 1 B 2 ACARS ATS VDL M 0/A/2 SATCOM (Classic Aero, SBD, SBB) HFDL ACARS ATS CPDLC: RCP 130, RCP 240, RCP 400 ADS-C: RSP 160, RSP 180, RSP 400 This design approval does not constitute operational authorization. ” Note: Should be provided in the normal section of the airplane flight manual or flight manual supplement Federal Aviation Administration 18

NAS En Route - Eligibility En Route – VDL Mode 2 • Multi-Frequency capability as per TSO-C 160 a or later – “Push to Load” capability for route clearances (i. e. UM 79/80/83) Note: LOA not required for Part 91 operators Federal Aviation Administration 19

Oceanic and Remote Continental: RCP • RCP 240/400 – Requires A 056 – Minimum acceptable performance 95% Federal Aviation Administration 20

Oceanic and Remote Continental: RSP • RSP 180/400 – Requires A 056 – Minimum acceptable performance 95% Federal Aviation Administration 21

CSP • Operators must ensure the services they have arranged with their CSP(s) include: – Failure Notifications (to operator and ANSPs affected along route of flight) – CSP ability to meet their performance allocations associated with RCP and RSP in Table 1 of the Op. Spec/MSpec/LOA – Recording data link messages – CSP Integrity – Adequate subnetwork coverage for the route of flight Federal Aviation Administration 22

Performance Monitoring - oceanic • FAA conducts performance monitoring: – New York, Oakland, Anchorage – Analysis of Actual Communication Performance (ACP) and Actual Surveillance Performance (ASP) – Semi-annual basis with an emphasis on nominal continuity (95%) • Operators must address substandard performance: – Operator’s monitoring process, CSP, FAA, or foreign authority • FAA PBCS monitoring website shows FAA airspace aggregate performance (pass/fail/insufficient data). Respond to a “Fail” by: – Following the website guidance to request additional info and a corrective action plan. May result in: • Operating at a lower performance until corrected • Changing filed flight plan designators for lower performance Federal Aviation Administration 23

Performance Monitoring - oceanic Eligibility for RCP 240 and RSP 180 based on 95% criteria • Initial - Use most recent FAA monitoring report - “Pass” → supports SOC in determining aircraft eligibility - “Fail” → operator provided additional information showing deficient allocations, etc. While correcting deficiency, operator may be approved for lower performance if meeting those allocations - “Insufficient data” → use SOC only and data from identicallyequipped aircraft type - Recurring - Operator/CSP monitor own performance → pro-active engagement - FAA runs semi-annual report - “Pass” → no issues - “Fail” → website directions for additional data/corrective action plan-may result in authorization downgrade to lower performance Federal Aviation Administration 24

Performance Monitoring - domestic • Will be included in first revision Federal Aviation Administration 25

Flight Planning - general When filing RCP/RSP capabilities, operators should ensure: – Planned use will be in accordance with regulations, policies and procedures in control areas for the flight, as published by the applicable States in AIPs (or equivalent publications) – The appropriate info denoting PBCS capabilities is included in the ICAO flight plan Capabilities comprise the following elements: – Presence of appropriate equipment on board the aircraft (and operating) – Equipment and capabilities commensurate with pilot qualifications – When applicable, appropriate authorizations as described in FAA Operations Specifications / Management Specifications / LOAs FAA - Operational approval (A 056) required to file PBCS Capabilities Federal Aviation Administration 26

Item 10 a: Equipment and Capabilities Radio communication equipment and capabilities J-codes P 1 - CPDLC RCP 400 J 1 - CPDLC ATN VDL Mode 2 P 2 - CPDLC RCP 240 J 2 - CPDLC FANS 1/A HFDL P 3 - SATVOICE RCP 400 J 3 - CPDLC FANS 1/A VDL Mode A P 4 -P 9 – reserved for future J 4 - CPDLC FANS 1/A VDL Mode 2 J 5 - CPDLC FANS 1/A SATCOM (INMARSAT) J 6 - CPDLC FANS 1/A SATCOM (MTSAT) J 7 - CPDLC FANS 1/A SATCOM (Iridium) Federal Aviation Administration 27

Item 10 b: Equipment and Capabilities Surveillance equipment and capabilities ADS-C D 1 - ADS-C with FANS 1/A capabilities G 1 - ADS-C with ATN capabilities Federal Aviation Administration 28

Item 18: Other Information DAT/ Indicate data communication equipment and applications or capabilities not specified in 10 a SUR/ Indicate surveillance equipment and capabilities not specified in Item 10 b – Indicate as many RSP specification(s) as apply to the flight, using designator(s) with no spaces • RSP 180 – Multiple RSP specifications are separated by a space • RSP 180 RSP 400. Federal Aviation Administration 29

Flight Plans - examples RCP 240 and RSP 180 • Field 10 → “P 2” and “P 1” and appropriate “J” code • Field 18 → “SUR/RSP 180 RSP 400” RCP 400 and RSP 400 • Field 10 → “P 1” and appropriate “J” code • Field 18 → “SUR/RSP 400” No RCP/RSP The operator may still use CPDLC/ADS-C but not for any services predicated on RCP/RSP • Field 10 → no “P” code • Field 18 → no “SUR/” indicated Federal Aviation Administration 30

AC 90 -117 Div Mgr Sig Coord Copy. pdf Federal Aviation Administration 31

Impact • Operators – New A 056 templates – Mandatory compliance by: March 31, 2018 • Communication Service Providers (CSP) NEW Data Link Qualifications – New customer requirements Federal Aviation Administration 32

Current A 056 holders – adding RCP/RSP - What do I need to do? • Show aircraft eligibility – AFM statement, etc • Show Pilot training for PBCS, etc • Show CSP service agreements – Performance allocations, failure notifications, etc • Show compliant with performance monitoring – “Pass” for performance you are requesting Federal Aviation Administration 33

New A 056 applications? • Follow AC 90 -117 guidance Federal Aviation Administration 34

Questions? ? Federal Aviation Administration 35

A 056, Table 1 Data Link System Airplane M/M/S Subnetworks Manufacturer Model CSP RCP INTEROP Designator Choose all that apply. Choose an item. RSP Limitations (If no limitations, type “N/A”) Choose an item. Federal Aviation Administration

N 8900. A 056 - Draft Notice 8900. A 056. docx Federal Aviation Administration 37

Supplemental Materials • FAA Data Link Communications Compliance Guide is: – Organized method for submitting evidence of compliance – Designed to expedite the compliance process • NAS Data Communication Guide is: – Guidance and procedures (best practices) regarding CPDLC in the NAS Federal Aviation Administration 38

Federal Aviation Administration 39

Back-up Slides Federal Aviation Administration 40

In. FO – “KUSA” Draft INFO 2017 xxxx NSDA Implementation. doc Federal Aviation Administration 41

A 056, Verbiage Part 121 Draft A 056 Part 121 Template. docx Federal Aviation Administration 42

A 056, Verbiage Part 91 Draft A 056 Part 91 Template. docx Federal Aviation Administration 43