APA TF/3 – IP/02 (Revised) Agenda Item 5 25/04/17

International Civil Aviation Organization

THE THIRD MEETING OF ASIA/PACIFIC ATS INTER-FACILITY DATA COMMUNICATION (AIDC) IMPLEMENTATION TASK FORCE Ministry Of Transportation (APA TF/3) OF APANPIRG Republic of Indonesia

Makassar, Indonesia, 26 – 28April 2017

Agenda Item 5: Sharing of experience on AIDC implementation and update the implementation status

PROGRESS OF AIDC IMPLEMENTATION (Presented by China)

SUMMARY

This paper presents the AIDC implementation and plan in China with

adjacent ATSUs and the issues during the implementation.

1. INTRODUCTION

In order to make transfer of aircraft more efficient and more accurate, and reduce the controllers’ workload, minimize Large Height Deviations (LHD), China continue to facilitate the AIDC implementation between domestic ATSUs and with adjacent ATSUs by using of Asia/Pacific Regional ICD for AIDC. China usually adopt ABBREV AIDC mode, mainly use core messages.

2. DISCUSSION

Between Sanya ACC and Hong Kong ACC

2.1 The AIDC between Sanya ACC and Hong Kong ACC implemented in 2007.

Between Guangzhou ACC and Taibei ACC

2.2 The AIDC between Guangzhou ACC and Taibei ACC implemented in 2013.

Between Shanghai ACC and Taibei ACC

2.3 The AIDC between Shanghai ACC and Taibei ACC implemented in 2013.

Between Dalian ACC and Incheon ACC

APA TF/3 – IP/02 (Revised) - 2 - Agenda Item 5 25/04/17

2.4 China and Republic of Korea started AIDC tests between Dalian ACC and Incheon ACC in 2014. China and Republic of Korea held several meetings to discuss the technical solution.

2.5 The AIDC implementation between Dalian ACC and Incheon ACC completed in November 2016.

Between Beijing ACC and Ulaanbaatar ACC

2.6 China - Mongolia AIDC exchange meeting was held at Ulaanbaatar in November 2014.The meeting discussed implementation procedure of AIDC between Beijing ACC and Ulaanbaatar ACC and its plan.

2.7 In June 2015, AFTN connection testing between Beijing ACC and Ulaanbaatar ACC was conducted. We configure the AFTN system and ATC Test platform. The EST message was sent and received successfully.

2.8 The Software and Hardware Upgrade of Beijing ACC ATM system was completed in April 2016, The ATM system support AIDC V2.0 capability and part of AIDC V3.0 capability.

2.9 China and Mongolia had previously conducted technical trials in November 2016 to test AIDC messages and identify potential issues. A software defect of Beijing ACC ATM system was encountered. The third item in the AOC message header is missing. The manufacturer nvestigated and provided software patch in April 2017. Software patch will be installed in May 2017.

Between Kunming ACC and Yangon ACC

2.10 China - Myanmar AIDC exchange meeting was held at Yangon in February 2017.The meeting discussed implementation procedure of AIDC between Kunming ACC and Yangon ACC and its plan.

2.11 AIDC initial tests between Kunming ACC and Yangon ACC had been carried out in March 2017. The tests were not successful. The EST messages from Kunming to Yangon were rejected by Yangon system due to Error messages 57 (No ASSOCIATED FPL or FPL NOT PREAC). Both sides are investigating.

2.12 There is potential latency issue of existing AFTN network, AFTN Latency Issues observed at times.

Between Kunming ACC and Vientiane ACC

2.13 China - Lao PDR AIDC exchange meeting was held at Vientiane in February 2017.The meeting discussed implementation procedure of AIDC between Kunming ACC and Vientiane ACC and its plan.

2.14 China and Lao PDR both agree to create a dedicated Line between Kunming ACC and Vientiane ACC in 2017.

- 3 - APA TF/3 – IP/02 (Revised) Agenda Item 5 25/04/17

Location of Correspond Technical Planed AIDC Media Remarks AIDC end ent location Test date of messages used system commence Implement used ment ation Sanya ACC Hong Kong 2007 EST,ACP,T AFTN ACC OC,AOC,LR M,LAM Guangzhou Taibei ACC 2013 EST,ACP,T Dedicated ACC OC,AOC,LR Line M,LAM Shanghai Taibei ACC 2013 EST,ACP,T Dedicated ACC OC,AOC,LR Line M,LAM Dalian ACC Incheon 2014 November ABI,EST,AC Dedicated ACC 2016 P,TOC,AOC, Line LRM,LAM Beijing Ulaanbaatar November TBD EST,ACP,T AFTN ACC ACC 2016 OC,AOC,LR M,LAM Kunming Yangon March TBD ABI,EST,AC AFTN ACC ACC 2017 P,TOC,AOC, LRM,LAM Shanghai Fukuoka 2017 TBD TBD TBD ACC ACC Guangzhou Hong Kong TBD TBD TBD TBD ACC ACC Shenyang Khabarovsk April 2017 TBD TBD TBD ACC ACC Kunming Vientiane TBD TBD TBD Dedicated ACC ACC Line

The issues during the implementation

2.15 In some cases, two ATSUs transfer of control according a level, not a point in bilateral agreement. So we meet some difficulties by conducting AIDC between these ATSUs.

2.16 AFTN latency in AIDC messages is not acceptable by controllers. With the increase of the number of flights, the latency will be much longer. If we more use of dedicated lines, the structure of network between ATM systems are more complicated. So we will accelerate the implementation of ATN.

3. ACTION REQUIRED BY THE MEETING

3.1 The meeting is invited to:

a) note the information contained in this papers; and

b) discuss any relevant matters as appropriate.

______