INDIA AIDC IMPLEMENTATION STATUS AND ISSUES Presented by Airports Authority of India Mini Seminar AIDC 23rd July 2013

ATM Automation systems in India Raytheon(AT3) Delhi, Mumbai Raytheon (AT3+) Chennai Indra (Aircon2100) at 38 mid/small sized airports Indra (Aircon2100) at Kolkata – Under Installation Selex ATM System at Bengaluru and Hyderabad Kolkata(New ATM system under installation)

AIDC Status Delhi (AT3) AIDC with Mumbai (AT3) AIDC with Ahmedabad (Aircon2100) Nagpur (Aircon2100) Implemented Varanasi (Aircon2100) Mumbai (AT3) AIDC with Chennai (AT3+) Under trial operation Muscat Planned Karachi Planned (initial testing carried out) Chennai (AT3+) AIDC with Mumbai Under trial operation Bengaluru Hyderabad Planned and configured Cochin Kuala Lumpur Male(Maldives) Planned Colombo

AIDC Implementation Issues Diverse ATM systems at ATSUs Some issues in Aircon2100 (under resolution) Non display of NO, CO in radar data block. Generation of MAC msg on termination of FPL. Route terminator "T" to be configured which affects AMAN profile/trajectories of the pairing stations When the actual boundary ETO in an ABI varies from the system calculated ETO (based on the EOBT) of the overflying aircraft, the system rejects the ABI message with an LRM. SSR codes of pairing unit sometimes do not match due to limited available codes.

Challenges in AIDC Implementation Interoperability between diverse ATM Systems. Implementation and system design issues attributed to revision of AIDC ICD versions.

Suggestions HMI for AIDC functionalities may be considered to be included in AIDC Guidance Material. To avoid prohibitive cost of frequent ATM Automation systems upgrade, backward compatibility of ICD versions should be assured. AIDC messages need time bound response within a short span of time for effective operations. Therefore, higher priority than normal flight plan messages may be considered for AIDC messages.

Thanks for Kind Attention