SATELLITE DATA-LINK COMMUNICATION REQUIREMENTS AND ISSUES

1. SATELLITE DATA-LINK COMMUNICATION REQUIREMENTS AND ISSUES ICAO APAC Office 8 February, 2012

2. STRUCTURE • Background • FANS Inter-operability Team (FIT) Outcome • ICAO NATSPG/47 Outcome • APANPIRG Outcome • Conclusion SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

3. ACARS • Data Link for Aviation Started in 1978 with ACARS • Initial data-link applications included Departure Clearance, ATIS etc. • ACARS expanded to use INMARSAT AMSS in 1990 • ACARS extended to IRIDIUM Satellites since 2007 through Short Burst Data transmission

4. ICAO DATA-LINK SERVICES • ICAO ANC created FANS Committee in 1980s and FANS Committee recommended use of data links and satellite for CNS • Installation FANS 1 by Boeing and FANS A by AIRBUS defined CPDLC and ADS-C • ICAO AMSS Standards adopted in 1994. Standards specify standard ITU protocols for the provision of voice and data link services.

5. FANS INTEROPERABILITY TEAM • Lessons learnt after investigating Performance Deficiencies: • Pilots: avoid sending multiple elements in downlink messages, avoid using free-text, continue to monitor HF • Air Traffic Controllers:priority for messages containing “DUE TO WEATHER”, avoid sending multiple elements • System Performance Lessons Learnt: Performance requirements include • Message Delay: <60 seconds 95% time • Integrity: Undetected bit errors< 10-6 per hour • CPDLC System availability: > 99.9% • Reliability: message delivery success rate > 99%

6. RECOMMENDATIONSPACIFIC DATA LINK OPERATORS CPDLC Procedures a) Communication initiated on voice to be completed on voice b) Include only single request in each CPDLC clearance request c) Free text to supplement formatted message only d) Pilot not to expect controller response to position report e) Conflict in messaged to be resolved using voice f) Read-back of clearance/instruction on CPDLC not reqd. g) For relay messages i) only a free text message to be used ii) First word of the message should be ‘Relay’

7. FIT/18 OUTCOME • Network availability improved • Performance measured against GOLD • ANSPs improved their Automation systems • Recommend ISPACG develop performance based framework for Comm./Surveillance • All ANSPs encouraged to support system performance monitoring outlined in GOLD • Current configuration, flight crew cannot cancel or modify crew reminder. • Typing errors in logon request may result flight crew waiting for 10 minutes before airplane function times out Project title (Insert, Header & Footer)

8. INMARSAT IRIDIUM • FAA agrees that IRIDIUM that meets appropriate requirements be allowed CPDLC/ADS-C • Approval of IRIDIUM SATCOM for use CPDLC/ADS-C still pending • AIRBUS informed IRIDIUM SATCOM tested for voice/data. Results promising • Some interference with INMARSAT • Voice calls good quality • IRIDIUM “NEXT” initial launch 2015, Operational 2017. SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

9. NATSPG • NATSPG Conclusion 46/02 endorsing draft proposal to amend NAT SUPPs mandating carriage/use of CPDLC & ADS-C • NAT DLMA providing service, but needs data in format from ATSUs for becoming operational • Noted Satellite data-link met 95% criteria for RCP 240 • SBB & oceanic safety trials planned for 2012 • INMARSAT clarified I-3 Classic Aero equipped aircraft will gradually begin utilizing I4 network. SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

10. APANPIRG • SAT DATA-LINK performance issues raised in APANPIRG Sub-Groups in 2008 • APANPIRG/19 asks ICAO to organize meeting of stake-holders to develop solutions • SOCM/1 organized from 26 to 28 August, 2009 • 56 participants from 13 States, International Organizations, Industry attended • 5 Working and 16 Information papers were presented and several presentations were made SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

11. SOCM/1 OUTCOME • Communication and Surveillance specifications included in the GOLD as Appendices B and C • States and IATA urged to provide information for Appendices E and F of the GOLD Document • Satellite data-link critical requirement for the implementation of RNP-4 -- IATA • ICAO views that multiple redundant connectivity has potential of improving availability SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

12. QUESTIONS RAISED • Options available for Satellite data-link considering business model • Service life left on I3 Network to recover investment after implementing upgrades • PARC CWG investigating use of IRIDIUM Satellite Short Burst Data (SBD) • Requirement of performance specs to support “longer term” operational initiatives. SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

13. SOCM/2 Following issues were recommended in SOCM/1 for discussion in SOCM/2 • Review Status of Satellite Data-link Communication in the Region • Develop common Outage/Maintenance Reporting Template for STATEs/ANSPs/CRAs • Develop a common service level agreement between CSPs and States/ANSPs • Mid/Long Term Strategy for Satellite Communication beyond 2016 Project title (Insert, Header & Footer)

14. DATALINK PERFORMANCE • Data-link performance significantly improved, safety target being achieved, efficiency target to be met • APANPIRG/22 noting the pre- and post-implementation system performance monitoring requirements, urged States in the APAC Region to ensure that the appropriate data link performance monitoring is undertaken and reported to CRAs/FITs, as required, in a timely manner. (APANPIRG Conclusion 22/12) SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

15. CONCLUSION • Safety targets for RNP-4 met, Efficiency target yet to be met • ICAO recommends use of two or more autonomous systems • Mid/Long Term strategy to be developed in view of end of lifetime of satellites SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING

16. THANK YOU SECOND SATELLITE OPERATIONAL DATA-LINK CONTINUITY MEETING