report on the fourth ats coordination meeting of … report bobasio 4.pdfthe fourth ats coordination...

REPORT ON THE FOURTH ATS COORDINATION

MEETING OF THE BAY OF BENGAL, ARABIAN SEA AND

INDIAN OCEAN BOBASIO/4

22 -24 SEPTEMBER 2014

AIRPORTS AUTHORITY OF INDIA

RAJIV GANDHI BHAWAN

SAFDARJUNG AIRPORT

NEW DELHI. 110003

BOBASIO/4

03/10/2014 P a g e | 2

The Fourth ATS Coordination Meeting of Bay of Bengal, Arabian Sea and Indian Ocean Region

Kolkata, India, 22nd –24th September 2014 Contents 1. HISTORY OF THE MEETING ……………………………………………………………………………………………..5

1.1 Introduction ................................................................................................................. 5

1.2. Officers, Secretariat and Participants ......................................................................... 5

1.3 Opening of the Meeting ............................................................................................... 5

1.4 Documentation and Working Language ..................................................................... 6

1.5 The plan for the meeting ............................................................................................. 6

1.6 Commencement of the meeting ................................................................................... 6

2. REPORT OF THE MEETING………………………………………………………………….7

2.1 AGENDA ITEM NO. 1 – ADOPTION OF AGENDA .................................................. 7

2.1.1 WP/01: Agenda, Timetable and Working Arrangements. .......................................... 7

2.2 AGENDA ITEM 2 -REVIEW OF PROGRESS ON ACTION ITEMS OF BOBASIO/3.7

2.2.1 WP/02: Review of progress of action items of BOBASIO/3 ................................. 8

2.3. AGENDA ITEM 3: REVIEW OF APAC SEAMLESS ATM PLAN AND ITS

IMPLEMENTATION ............................................................................................................. 8

2.3.1 WP/08: PBN Implementation in the region through collaboration: ................... 8

2.4 AGENDA ITEM 4 -STRATEGIC ATM PLANS OF PARTICIPATING STATES ...... 9

2.4.1 IP/05: Traffic Flow in Oceanic Airspace of Mumbai FIR, Evaluation of FLAS

and its Review……………… ................................................................................................... 9

2.4.2 IP/06: Flexible Use of Airspace- FUA Manual India......................................... 11

2.4.3 IP/07: Sharing Indian Experience in the Implementation of GBAS ................ 12

2.4.4 WP/07: Airspace Capacity enhancement in BOBASIO Region ........................ 13

2.4.5 IP/04: GAGAN/SBAS services for the Region ................................................... 15

2.5 AGENDA ITEM 5 - C Y B E R SECURITY- PREPARATION OF ROAD MAP ....... 17

2.5.1 WP/05: Cyber security for Air Navigation Systems. ......................................... 17

2.6 AGENDA ITEM 6 - AIS AND SAR AGREEMENTS ................................................ 19

2.6.1 WP/09: Search and Rescue agreements ............................................................ 19

BOBASIO/4

03/10/2014 P a g e | 3


Kolkata, India, 22nd –24th September 2014 2.6.2 WP 11: SAR Agreement between India and Maldives ..................................... 21

2.6.3 WP 12: SAR Agreement between Maldives and Mauritius ............................. 21

2.7 AGENDA ITEM 7 - ATM CONTINGENCY PLAN- LEVEL 2 AND PBN AND RNP

ROUTES. .............................................................................................................................. 21

2.7.1 WP/04: PBN Implementation in India .............................................................. 21

2.7.2 IP/01: Implementation of PBN based RNAV 1 (GNSS) SID and STAR at GOA

airport (Civil Military Cooperation in implementation of PBN. ......................................... 22

2.7.3 WP/13: ATM contingency plan for MALE FIR, Maldives ................................. 23

2.7.4 IP/02: ATM Contingency Plan- India ................................................................ 24

2.8 AGENDA ITEM 8 - ATN/AMHS AND AIDC IMPLEMENTATION: ................ 25

2.8.1 WP/03- ATS/DS coordination between Mumbai and Mogadishu FIC. ............. 25

2.8.2 WP/06: ATS Inter Facility Data Communication (AIDC) implementation in

India & with adjacent ATS units in the sub-region and the issues thereof. ...................... 26

2.9 AGENDA ITEM 9 - ANY OTHER BUSINESS ..................................................... 27

2.9.1 IP/10: Upper Airspace Harmonisation (UAH) of Kolkata Airspace. ................ 27

2.9.2 IP/09: ADS-B Data Sharing ............................................................................... 28

2.9.3 IP/08: Update on Implementation of ASBU Block 0 Modules .......................... 28

2.9.4 IP/03: Study of HF Coverage in Arabian Sea .................................................... 28

2.9.5 WP/10: Provision of Airspace Safety Monitoring Data by Member States to

BOBASMA ............................................................................................................................ 29

2.9.6 WP/14: Safety oversight of RVSM operation in BOBASIO airspace. ............... 30

2.9.7 Sideline Working Groups (SWGs) meetings: .................................................... 31

2.10 AGENDA ITEM 10: FUTURE MEETINGS ......................................................... 39

3. CLOSING OF THE MEETING:…………………………………………………………………………………………..40

APPENDIX A ....................................................................................................................... 41

APPENDIX B ....................................................................................................................... 42

APPENDIX C ....................................................................................................................... 44

APPENDIX D ....................................................................................................................... 46

BOBASIO/4

03/10/2014 P a g e | 4


Kolkata, India, 22nd –24th September 2014 APPENDIX E ....................................................................................................................... 49

APPENDIX F........................................................................................................................ 54

APPENDIX G ....................................................................................................................... 61

BOBASIO/4

03/10/2014 P a g e | 5


Kolkata, India, 22nd –24th September 2014 1. HISTORY OF THE MEETING

1.1 Introduction

1.1.1 The Fourth ATS Coordination Meeting of the Bay of Bengal Arabian Sea and

Indian Ocean (BOBASIO) Region was held at Hotel Swissotel, Kolkata, India from

22nd to 24th September, 2014.

1.2. Officers, Secretariat and Participants

1.2.1 The inaugural session was chaired by Mr. Ram Lal, Executive Director (Air Traffic

Management), Airports Authority of India. Various sessions were moderated by Mr.

A. K. Dutta, Executive Director (ATM); Mr. Owin Wilson, ATS Expert (Operations)

Somalia FISS; Ms. Esmee Samson, General Manager (ANS) Seychelles; Mr. Michael

Shee, ATC Manager (ATM OPS Planning) CAA Singapore and Mr. Jayanta Dasgupta

GM (ATM) Mumbai. Mr. Rakesh Bhatnagar, Joint General Manager (ATM), Airports

Authority of India acted as the Secretary to the meeting.

1.2.2 The meeting was attended by 53 participants including 21 international delegates

from Bangladesh, Indonesia, M a l d i v e s , M y a n m a r , Thailand, Seychelles,

Singapore, Somalia and UAE. A list of participants is attached in Appendix-E.

1.3 Opening of the Meeting

1.3.1 Welcome address was delivered by Regional Executive Director, Easter Region AAI

and he mentioned that BOBASIO is providing a platform for propagating seamless

Air Traffic Services across the BOBASIO States.

1.3.2 Mr. Ram Lal, Executive Director (Air Traffic Management), Airports Authority of

India (AAI), welcomed the participants from BOBASIO States for the Fourth ATS

Coordination Meeting of BOBASIO Region. He reiterated to the participants, the

BOBASIO subgroup objective of ‘Harmonized application of ATM procedures and

systems for seamless ATM services across member states and sharing the latest ANS

developments in the region’, He also informed the participants about new agenda

items such as Cyber security. He wished all the success for the meeting and expected

BOBASIO/4

03/10/2014 P a g e | 6


Kolkata, India, 22nd –24th September 2014 that all the members will benefit from the result oriented deliberations during these

three days.

1.3.3 The General Manager (ATM) Kolkata, Mr. Chandan Sen proposed a vote of thanks at

the end of the inaugural session. The Secretariat of this meeting placed on record the

excellent logistics support from the Kolkata team, without which this meeting would

not have been as successful.

1.4 Documentation and Working Language

1.4.1 The meeting was conducted and the documentation prepared in English. Fourteen

(14) Working Papers (WPs) and Ten (10) Information Papers (IPs) were presented

to the meeting. A list of the papers presented in the meeting is provided in Appendix-

B.

1.5 The plan for the meeting

1.5.1 The meeting was divided into 7 sessions over a period of two days, followed by the

adoption of draft report, which was scheduled for the third day. The agenda items

(refer Appendix-A) were as appended below:

1. Adoption of Agenda

2. Review of progress of action items on BOBASIO/3

3. Review of APAC Seamless ATM Plan and its Implementation

4. Strategic ATM plans of participating states

5. Cyber Security- Preparation of Road Map

6. AIS and SAR Agreements

7. ATM contingency Plan- Level 2 and PBN and RNP routes

8. ATN/AMHS and AIDC implementation

9. Any Other Business

10. Future Meetings

The meeting was conducted as per order of business given in Appendix- C.

1.6 Commencement of the meeting

1.6.1 The first session was chaired by Mr. Ram Lal, Executive Director (ATM). At the end

BOBASIO/4

03/10/2014 P a g e | 7


Kolkata, India, 22nd –24th September 2014 of the introduction session, the Chair mentioned that the attendance, especially

from international delegates from both within the BOBASIO region and beyond,

was a pointer to the seriousness and purposefulness of the deliberations days. He

introduced the session and handed over the responsibility of taking the session

forward to the Secretary of the meeting.

1.6.2 The Secretary of the meeting, Mr. Rakesh Bhatnagar, informed the house that like

the previous meetings, the order of business was tailored to provide discussions in

various sessions to include working papers and information papers which had a

common thread, albeit under different agenda items. The Secretary informed the

meeting that information pertaining to BOBASIO/4 including the Working Papers

and Information Papers were available on the web portal www.aaians.org

1.6.3 The Secretary expressed confidence that the participants will appreciate the

importance of time management and deliberate business with utmost focus. The

participating States and Organizations have some expectations from the meeting

and he said that a positive outcome was expected from the discussions so that

everyone could take home some successful outcomes from the deliberations.

2. REPORT OF THE MEETING

2.1 AGENDA ITEM NO. 1 – ADOPTION OF AGENDA

2.1.1 WP/01: Agenda, Timetable and Working Arrangements.

2.1.1.1 The first working paper entitled “Adoption of Agenda”, was proposed by the

BOBASIO/4 Secretariat. The working paper included the ‘Order of Business’ and

‘Order of Discussions’ outlining the sequence of working and information papers to be

presented. The Secretary also informed the participants of two proposed side line

meetings between States/ANSPs sharing common boundaries; with an objective of

discussing and resolving matters of bilateral/multilateral agreements. The meeting

unanimously adopted the agenda, paving way to further discussions as planned,

proposed and adopted.

2.2 AGENDA ITEM 2 -REVIEW OF PROGRESS ON ACTION ITEMS OF BOBASIO/3.

http://www.aaians.org/

BOBASIO/4

03/10/2014 P a g e | 8


Kolkata, India, 22nd –24th September 2014 2.2.1 WP/02: Review of progress of action items of BOBASIO/3

2.2.1.1 The second working paper “Review of progress on action items of BOBASIO/3”

was presented by Mr. Kanhaya Lal General Manager (ATM) AAI and taken up for

discussion. This paper presented a brief review along with outcome of the Third

Meeting of Bay Of Bengal, Arabian Sea and Indian Ocean Region (BOBASIO/03) held

at Hyderabad, India.

2.2.1.2 The meeting noted the outcome of the third ATS coordination meeting BOBASIO/3.

The meeting agreed to have a tracking mechanism for follow up of action items. It was

agreed that updates on action items would be provided by the

States/ANPs/Organizations as proceedings would progress. Status of action items of

BOBASIO/3 is at APPENDIX E.

2.3. AGENDA ITEM 3: REVIEW OF APAC SEAMLESS ATM PLAN AND ITS

IMPLEMENTATION

2.3.1 WP/08: PBN Implementation in the region through collaboration:

2.3.1.1 Paper presented by Mr. Sambath Kumar, Joint General Manager (ATM) of AAI

described India’s willingness to collaborate in developing and implementing PBN in

en-route and terminal airspaces of neighboring States. Specific potential benefit areas

are identified, however, the paper emphasized that much is desirable in terms of

collaboration in joint design activities to take the plans forward.

2.3.1.2 The paper suggested that, since the safety and efficiency of flights transcend national

borders and airspace boundaries, therefore, Seamless ATM is possible, if and only if,

there is close regional/sub-regional collaboration among States, their ANSPs and all

stakeholders. The paper also highlighted Performance Based Navigation (PBN) as

one of ICAO’s highest air navigation priorities and stressed that potential benefits

achievable through creation of additional capacity with PBN implementation are

countless. Therefore, in order to achieve Seamless Air Traffic Management and

introduce more optimum routes through contiguous airspace(s), inter-regional

coordination and collaboration is essential. In BOBASIO/3 India presented a Working

paper on Implementation in the sub-region through collaboration and invited member

States of the sub-group to work closely to form a seamless network of routes and

procedures by jointly developing PBN RNAV-5 routes and arrival/departure

procedures. The paper informed that in BOASIO/3 meeting, India detailed its RNAV

BOBASIO/4

03/10/2014 P a g e | 9


Kolkata, India, 22nd –24th September 2014 2 plans and extended an invitation to its neighbors to create a joint mechanism for

designing an efficient cross border PBN route structure. India also proposed joint

development of RNAV5 routes between Dhaka/Kolkata, Colombo/Chennai, Colombo

Thiruvananthapuram and Colombo Madurai.

2.3.1.3 The paper informed the meeting that in the CANSO Asia Pacific Conference, in

Colombo, Sri Lanka between the 5th and the 7th May 2014, India urged Sri Lanka in

a sideline meeting to take its proposals forward.

2.3.1.4 The paper also informed that in the first Meeting of Bangladesh, India, Myanmar,

Thailand (BIMT) ATM Coordination Group, attended by Malaysia and Indonesia as

observers, it was agreed to prioritize the reduction of longitudinal separation minima

on L301 and L507 routes, with ICAO RSO serving as the main coordinator.

2.3.1.5 Through this working paper, meeting was informed that India has also been pursuing

with Civil Aviation Authority Bangladesh (CAAB), the introduction of an

International Route connectivity between Guwahati and Bangkok, via GGT VOR-

B593 – CML (COMILLA) VOR – ONEKA – G463 – CTG (CHITTAGONG) VOR – B465

– YANGON – further to Bangkok, by creating an ATS Route (segment) between CML

and ONEKA.

2.3.1.6 The paper proposed that; consistent with the Seamless ATM Principles: 9 (Cross-

border/FIR cooperation for use of aeronautical facilities and airspace, collaborative

data sharing, airspace safety assessment and ATM Contingency planning) and 15

(Collaboration by ANSPs for evaluation and planning of ATM facilities) neighbouring

States should share airspace change proposals at the design level to facilitate

seamless and safe airspace across borders.

2.3.1.7 The paper underlined the fact that in order to transform ideas into reality it is

important for neighboring States to identify the Key Result areas (KRAs) and prepare

time bound action plans.

2.4 AGENDA ITEM 4 -STRATEGIC ATM PLANS OF PARTICIPATING STATES

2.4.1 IP/05: Traffic Flow in Oceanic Airspace of Mumbai FIR, Evaluation of FLAS and its

Review

2.4.1.1 The information paper presented by Mr. A.B. Joshi, Joint General Manager (ATM),

BOBASIO/4

03/10/2014 P a g e | 10


Kolkata, India, 22nd –24th September 2014 AAI; informed the meeting about the traffic flow, the review of traffic flow

management in the form of Flight Level Allocation Scheme and the efforts made by

AAI to make optimum flight levels available to flights to so as to reduce fuel burn and

emissions.

2.4.1.2 Through the IP, AAI informed that as a result of promulgation of RNP 10 routes in

the year 2003 and later implementation of RVSM in Mumbai FIR; traffic flow

management in the form of Flight Level Allocation Scheme was introduced to ensure

separation between crossing traffic and to ensure that reasonably efficient flight

levels are available for the Africa and South East Asia traffic flow. FLAS also ensured

safe transition from RVSM levels to CVSM levels as some of neighbouring FIRs were

still using CVSM.

2.4.1.3 The paper highlighted that gradually as all the neighbouring FIRs have converted to

RVSM airspaces and many wide body long haul aircraft have started operating in the

airspace it has been reported that the FLAS and conventional longitudinal

separations are restricting the flights to use less than optimum flight levels.

2.4.1.4 Airports Authority of India, through this Information paper informed the meeting

measures implemented as follows, that would increase the availability of optimum

levels resulting in more efficient traffic flows:

a) the reduced longitudinal separation of 50 Nm on all RNP 10 routes for suitably

equipped aircraft in the first phase of three phased plan proposed by ICAO

APAC for the region.

b) establishing ASIO UPR zone through the INSPIRE partnership

c) FLAS is suspended for periods of less density of north south traffic i.e. 0530 to

0930 UTC.

d) The reduced longitudinal separation of 30 nm has been introduced on 4 ATS

route N571, P574, M300 and P570 between suitably equipped aircraft from 13th

September 2014.

e) The FLAS though restricts usage of certain levels on certain routes but does not

prohibit the usage if traffic permits. Accordingly, traffic permitting Mumbai

ATC was allotting optimum levels as far as practicable. In past months a

sensitization programme was launched for ATC controllers to encourage them

to use FLAS only as last resort. Instructions have been issued to accept CPDLC

BOBASIO/4

03/10/2014 P a g e | 11


Kolkata, India, 22nd –24th September 2014 capable flights on ATS routes A474, B459 and G424 at Non FLAS levels.

2.4.1.5 The paper outlined AAI’s following three phased programme to remove FLAS to ensure

safety at all times.

a) In the first phase the FLAS will be removed in the UPR zone. The trials for this

have already commenced and instructions have been issued to accept

ADS/CPDLC capable aircraft on routes A474, G424 and B459 at current flight

plan levels.

b) In the second phase the FLAS for all west bound flights will be abolished

c) In the final and most difficult to achieve phase the FLAS will be totally

eliminated.

2.4.1.6 The paper invited the meeting to suggest measures that could be implemented to

improve the efforts.

2.4.2 IP/06: Flexible Use of Airspace- FUA Manual India

2.4.2.1 The Information paper presented by Mr. Sambath Kumar, Joint General Manager

(ATM), AAI, showcased a milestone achievement in FUA implementation in India

with the preparation of FUA Manual V 1.0 and its acceptance by India’s National

High Level Airspace Policy Body (NHLAPB). This was a follow up of India’s detailed

working paper (WP 14) in BOBASIO/3.

2.4.2.2 The meeting was informed through this paper that on 8th March, 2013, the Cabinet

Committee on Security constituted the National High Level Airspace Policy Body

(NHLAPB) for implementing Flexible Use of Airspace in India. NHLAPB constituted

the National Airspace Management Advisory Committee (NAMAC) which will also

function as Airspace Management Steering Group.

2.4.2.3 A Sub-committee, with representatives from the FUA Secretariat (AAI), IAF (ATS),

IAF (AD), Indian Navy (ATS) and DGCA (ANS) was also constituted by NHLAPB

which was vested with the responsibly of preparing a draft FUA Manual which shall

be the mother document providing detailed guidelines on FUA implementation at all

three levels of ASM [ASM Level 1 (strategic), Level 2 (pre-tactical) and Level 3

(tactical)]

2.4.2.4 A draft FUA Manual was prepared by the FUA Secretariat (AAI). The FUA

Secretariat, thereafter, prepared a detailed comments matrix on receiving comments

BOBASIO/4

03/10/2014 P a g e | 12


Kolkata, India, 22nd –24th September 2014 from the FUA Manual Subcommittee members from IAF, Indian Navy, DGCA and

Airline operators.

2.4.2.5 A meeting of the National Airspace Management Committee (NAMAC) with members

drawn from AAI (ASM), IAF, Indian Navy, DGCA, ISRO (Indian Space Research

Organization) and Airlines and the FUA Manual Subcommittee, reviewed each and

every comment and came to mutual agreement on the revisions to the draft FUA

Manual.

2.4.2.6 The Draft Manual was placed before the NHLAPB in its fourth meeting on the 20th

of August, 2014. The FUA Manual was adopted unanimously by the members of the

NHLAPB.

2.4.2.7 The meeting was informed that the FUA Manual India Version 1.0 contains seven

chapters and includes details on the Implementation of FUA in India, the constitution

of national bodies and their terms of reference, ASM Levels 1,2 and 3, Information

management, Air Defence Requirements and Interoperability of Civil-Military

systems.

2.4.2.8 The paper informed that a pilot project to validate the FUA Manual is proposed to be

planned and executed by September/October 2014 and the manual is subject to

periodic review taking into consideration the outcomes of FUA implementation.

2.4.2.9 The paper also informed the committee that NHLAPB has also constituted a sub-

committee for preparing a report containing a “Gap Analysis” for system integration,

a route chart including the details of harmonizing Integration Protocols and Interface

Control Documents (ICD) to ensure civil military systems interoperability.

2.4.3 IP/07: Sharing Indian Experience in the Implementation of GBAS

2.4.3.1 The Information paper was presented by Mr. M. L. Chakravarty GM (CNS), AAI. The

paper stated that Airports Authority of India and Director General of Civil Aviation,

India are working together towards implementation of first Ground based

Augmentation System at Chennai airport, as a part of extended GNSS initiatives.

2.4.3.2 The paper informed the meeting that the GBAS at Chennai is taken up as a pilot

project and based upon its success Airports Authority of India will evaluate the

requirement of GBAS systems for other Indian airports. Once implemented, it will

meet the GNSS requirements stated in ICAO Annex 10, Vol. –I.

BOBASIO/4

03/10/2014 P a g e | 13


Kolkata, India, 22nd –24th September 2014

2.4.3.3 Physical installation of GBAS Equipment has been completed and the system is

allowed to run in test mode. This GBAS will support up to 26 approaches for all

runway ends, provided the middle point of GPS receiver antennas is within 6 km. of

the decision height of each of the runway approaches, it is to serve.

2.4.3.4 The paper stated that in order to detect the types of ionospheric activity, the receivers

must be installed forming a triangular geometry, with a baseline of between 1 and 10

km. Placement of receivers in a triangular geometrical configuration provides the

ability to detect and measure ionospheric fronts in all directions, hence, three GPS

receivers were installed at Chennai Airport in November 2014 at three locations viz.

Localizer-25, Localizer-07 and Remote receiver site, thereby maintaining baseline of

less than 5 Km. Data collected using these receivers is continuously being analyzed.

2.4.3.5 The paper discussed the Anomalous behavior of the ionosphere and its downside effect

on GNSS performance over equatorial region and stated that under nominal

conditions (without ionospheric storms), ionospheric delays on GPS Pseudorange

measurements are highly correlated over the short distance, therefore, differential

GBAS user errors, caused by ionospheric delays are very small and do not affect

system performance. In general the rate of change of Total Electron Content (TEC)

over short distance (∼100 km) is very small. However presence of ionospheric storms

can cause ionosphere to behave quite differently. Therefore, the effect of large

ionospheric gradients in which Total Electron content (TEC) can change by tens of

meters in just a few minutes, thereby causing significant difference in TEC

experienced by users at short distances (even less than 45 km) is of major concern and

of particularly important in context of GBAS.

2.4.3.6 The paper discussed the result of study of the 92 days data processed and through the

meeting invited States, interested in the implementation of GBAS in their region to

take up similar studies to gauge the efforts required for GBAS implementation.

2.4.3.7 Through the meeting the paper invited the ICAO led Ionospheric Study Task Force to

study the issues involved in the implementation of GBAS in equatorial region and

suggest the solution.

2.4.4 WP/07: Airspace Capacity enhancement in BOBASIO Region

2.4.4.1 This working paper presented by Mr. Sambath Kumar Joint General Manager (ATM),

AAI outlined the details of enhancement of airspace capacity through application of

BOBASIO/4

03/10/2014 P a g e | 14


Kolkata, India, 22nd –24th September 2014 RHS and the plans and proposals for uniform application of these separation minima

in the BOBASIO region to multiply manifold benefits to the airspace users.

2.4.4.2 The paper stated that though EMARSSH routes employing RNP 10 operations had

capability to reduce longitudinal separation to 50NM, but BOBASIO States could not

utilize them to reap the expected benefits from it.

2.4.4.3 The paper discussed the formation of Bay Of Bengal Reduced Horizontal Separation

Task Force (BOB-RHS/TF) in 2009 for implementing Reduced Horizontal Separation

in the Bay of Bengal Arabian Sea Indian Ocean and its decision to implement 50 NM

Reduced Longitudinal Separation in a phased manner along RNP10 routes in the

BOBASIO airspace.

2.4.4.4 In the year 2011, India established an Enroute Monitoring Agency to meet the ICAO

provisions for implementing 50NM longitudinal separation. Accordingly, India

introduced the application of 50NM longitudinal separation minima between RNP 10

approved aircraft meeting Direct Controller Pilot Communication (DCPC)

requirements through CPDLC or two way VHF communication in two phases on those

segments of the RNAV (RNP10) Routes which fall within the Chennai, Mumbai,

Kolkata and Delhi FIRs.

2.4.4.5 The paper mentioned about India’s initiative to introduce 13 RNAV-5 city pair routes

connecting cities of Delhi and Mumbai/Ahmadabad/Vadodara/Udaipur/ Jaipur;

Mumbai and Trivandrum/ Cochin/ Calicut/ Mangalore/ Coimbatore; Mumbai and

Chennai/ Bangalore & between Chennai and Kolkata.

2.4.4.6 The paper highlighted the data link capability of Yangon, Kuala Lumpur, Chennai,

Kolkata, and Mumbai that enables continuous surveillance for FANS1/A aircraft and

also uninterrupted Radar coverage from Muscat FIR to the west of Mumbai FIR right

up to and beyond the common boundary with Mumbai FIR.

2.4.4.7 The paper mentioned Asia/Pacific Seamless ATM Plan Version 1.0, June 2013

published by the ICAO Asia and Pacific Office, Bangkok which recommends RNP 4,

RNP 10 (RNAV 10) (other acceptable navigation specifications – RNP 2 oceanic) for

Category R Airspace.

2.4.4.8 The paper informed that in a side meeting during the Combined Fourth Meeting of

the South Asia/Indian Ocean ATM Coordination Group (SAIOACG/4) and Twenty-

First Meeting of the South-East Asia ATS Coordination Group (SEACG/21);

BOBASIO/4

03/10/2014 P a g e | 15


Kolkata, India, 22nd –24th September 2014 Indonesia, Malaysia, India and Sri Lanka agreed to revise LOA for the

implementation of 30NM longitudinal separation after publication of AIP Supp.

2.4.4.9 In the First Meeting of Bangladesh, India, Myanmar, Thailand ATM Coordination

Group attended by Malaysia and Indonesia as observers, the limitations for further

enhancement of airspace through RNP10 routes was noted. ATM Coordination Group

meeting also agreed India’s position that FLAS, act as a safety net for crossing routes,

and any revision requires traffic analysis and safety assessment. With ICAO RSO

serving as the main coordinator, supporting the actions leading to reduced separation

minima on L301 and L507 ATM Coordination group meeting agreed to prioritize the

reduction of longitudinal separation minima on L301 and L507 routes.

2.4.4.10 The paper stated that India has implemented 30 NM Longitudinal Separation

between RNP4 approved aircraft on opportunity basis on four ATS routes viz., N571,

M300, P570 and P574 w.e.f 18th September, 2014 and stressed on airspace capacity

enhancement in the region through RHS.

2.4.4.11 Through this paper AAI, invited the meeting to work closely together to identify and

prioritize ATS routes for implementation of RHS and decide on a suitable AIRAC date

for implementation of RHS. The paper also invited the meeting to identify point of

contacts and coordinators for the task.

2.4.5 IP/04: GAGAN/SBAS services for the Region

2.4.5.1 The paper presented by Mr. S.V. Satish, GM (ATM-GAGAN), AAI and Mr. C.R.

Sudhir, GM (CNS) AAI is continuation of India’s efforts in establishing certified SBAS

services through the implementation of GAGAN signals over Asia Pacific Region.

Advantages of GAGAN within BOBASIO states was presented in BOBASIO-3 as one

of the GNSS enabler for ICAO ASBU.

2.4.5.2 Through this paper, AAI informed that GAGAN system has successfully passed

through phase I certification for RNP0.1 en-route services on 30th December 2013 and

is working towards achieving Approach with Vertical Guidance (APV1.0) terminal

capability by February 2015. GPS Aided Geo Augmentation Navigation (GAGAN) –

the Indian Satellite Based Augmentation System (SBAS) Programme is unique

because of the implementation of ISRO-MLDF IONOSPHERIC ALGORITHM to

meet the ionospheric challenges posed in Indian sub-continent and other Equatorial

Ionospheric Anomaly regions.

BOBASIO/4

03/10/2014 P a g e | 16



2.4.5.3 In the BOBASIO/3 meeting, India presented the status paper on GAGAN with

strategic objective to enhance global civil aviation safety and environmental

protection and sustainable development of air transport. During the discussion, India

urged States to consider the early implementation of GAGAN signals through a

collaborative approach. India presented the Operation Test and evaluation tools

developed by India for assessing GAGAN signal-in-space compliance. The point of

contact (POC) for coordination related to GAGAN services from BOBASIO Member

States was also established.

2.4.5.4 The paper informed the meeting that India is under the process of establishing APV

1 services by the first quarter of 2015.

2.4.5.5 The paper highlighted a study of RNP 0.1 coverage using 15 Indian Reference Stations

conducted in collaboration with Raytheon (System Integrator). The region that was

studied included the SAARC countries; Afghanistan, Bangladesh, Bhutan, India,

Maldives, Nepal, Pakistan, and Sri Lanka. Other countries considered were Saudi

Arabia and Oman and the eastern area towards the Philippines. The coverage as on

6th August (as shown in figure 1) clearly indicates near 100% availability of RNP 0.1

services beyond the Indian Flight Information Region and the availability can rapidly

increase if sufficient number of reference stations are placed on the edge of the

coverage volumes providing for a harmonious airspace development within the region.

2.4.5.6 The paper discussed expansion of GAGAN/SBAS services in the region through

collaborative approach. As common coverage of GAGAN GEOs (GSAT 8 and GSAT

10) extends from middle of Africa to Australia addition of reference stations in

GAGAN architecture will allow service to more number of Ionospheric Grid points,

thereby extending the GAGAN services to neighbouring FIRs. Therefore,

neighbouring countries, without making additional expenditure on huge SBAS

infrastructure can draw advantage from existing GAGAN signals. Through suitable

enhancements, in terms of adding new reference stations and modification in GAGAN

software to map additional Ionospheric grid points, GAGAN has the capability to

extend its precision and dependable navigation services outside Indian boundary.

2.4.5.7 Through this information paper, India explained the advantage of coverage of

GAGAN signals in adjacent FIRs to the Air Navigation Service Provider (ANSP) in

using the satellite based navigation (SATNAV) as A SATNAV user only and a

SATNAV service enhancer. India offered its help in various areas like satellite

visibility study, selection of suitable sites for establishment of reference stations, RF

and Multipath interference surveys, site survey results analysis and

BOBASIO/4

03/10/2014 P a g e | 17


Kolkata, India, 22nd –24th September 2014 recommendation, reference station installation, performance analysis etc.to the

interested states and invited the meeting to consider and indicate willingness to use

GAGAN signal in space for implementation of GAGAN within states of the Asia

Pacific Region where both footprint and service volume can be made available for

mutual benefit.

Figure 1: Availability of RNP 0.1 services beyond the Indian Flight Information Region

2.5 AGENDA ITEM 5 - C Y B E R SECURITY- PREPARATION OF ROAD MAP

2.5.1 WP/05: Cyber security for Air Navigation Systems.

2.5.1.1 The information paper was presented by Mr. Anurag Sharma Joint General Manager

(CNS) which stressed the need for establishing a cyber-security framework for the

ANSPs in view of growing demand for more information sharing through increased

use of commercially available information technology, shared network and computing

infrastructures, and network-centric architectures which has become imminent for

enhanced efficiency of operations. The paper emphasized that the threat is both real

BOBASIO/4

03/10/2014 P a g e | 18


Kolkata, India, 22nd –24th September 2014 and serious as increased use of information technology means greater exposure to

cyber-attack therefore, ANSPs need to develop and execute security strategies and

plans to ensure continuation of operations despite this threat.

2.5.1.2 The paper informed the meeting that ICAO Council, on 17 November 2010, adopted

Amendment 12 to Annex 17 which required States to include ATSPs in the National

Civil Aviation Security Programme (NCASP) and to ensure that they implement

appropriate security provisions to meet the requirements of the NCASP.

2.5.1.3 The paper informed the meeting about recommendations of AN-Conf/12, vide

Recommendation 2/3 – Security of air navigation systems, has also recommended

ICAO to establish as a matter of urgency, an appropriate mechanism including States

and industry to evaluate the extent of the cyber security issues and develop a global

air traffic management architecture taking care of cyber security issues.

APANPIRG/24 vide its conclusion 24/4 has urged states to take follow-up action as

appropriate on the recommendation. As a result, ICAO has identified the importance

of cyber security for various CNS/ATM systems.

2.5.1.4 Meeting was apprised of Guidance material available on Cyber security provided in

various documents such as; Aviation Security Manual (Doc 8973 Eighth edition), Air

Traffic Management Security Manual (Doc 9985 AN/492), “CANSO Cyber Security

and Risk Assessment Guide” and Global Air Traffic Management Operational

Concept (ICAO Doc. 9854).

2.5.1.5 The paper outlined following objectives of Cyber Security identified to support

continuation of safe operations of Air Navigation Services

Confidentiality

Integrity and Accuracy

Availability

Longevity and traceability

Non-repudiation and imputablility

2.5.1.6 Mr Anurag Sharma informed the meeting, that, Civil Aviation in India has been

identified as a critical information infrastructure and Airports Authority of India has

taken appropriate measures for incorporating cyber-security in CNS/ATM systems.

BOBASIO/4

03/10/2014 P a g e | 19



• Centralized cyber operations • Detection monitoring and

analysis • Shared knowledge of cyber

threats

• Contingency planning and business continuity

• Multi stakeholder cooperation

• Training and awareness

• Investment periodization • Legacy system compliance • Leverage emerging

technologies

• Agile architecture & design strategies

• Enterprise-wide information system security (ISS) solutions

• ISS Governance and policy

Protect Plan

Respond Detect

Organization specific cyber-security policy in line with ICAO and national framework

is under preparation. Numbers of teams have been identified to propagate awareness

among CNS/ATM professionals of the vulnerabilities and mitigation measures.

2.5.1.7 The paper highlighted a model shown diagrammatically in figure 2 below; with four

complementary areas: Plan, Protect, Detect and Respond that ANSPs can adopt to

achieve effective cyber security.

Figure 2: Model to effectively achieve cyber security

2.5.1.8 The paper invited the meeting to Share information among states, as appropriate, on

strategies being adopted to establish Cyber-Security framework so as to ensure

protection of CNS/ATM infrastructure against cyber-threats in the region.

2.6 AGENDA ITEM 6 - AIS AND SAR AGREEMENTS

2.6.1 WP/09: Search and Rescue agreements

2.6.1.1 The paper presented by Mr. S.K. Oberoi, GM (ATM-SAR), AAI stressed on the need

for establishment of Search and Rescue agreements with the Neighboring States for

cooperation on SAR services under the provisions of the Standards and Recommended

Practices contained in Annex. 12. First meeting of the Asia/Pacific Regional Search

BOBASIO/4

03/10/2014 P a g e | 20


Kolkata, India, 22nd –24th September 2014 and Rescue Task Force meeting held in February 2013, emphasized that the

implementation of SAR Agreements be facilitated as early as possible, as, SAR

Agreement between the regional SAR neighbours would improve the coordination and

awareness of SAR asset availability.

2.6.1.2 First ATS Coordination meeting of Bay of Bengal, Arabian Sea and Indian Ocean

Region (BOBASIO/1) Delhi emphasized the need of SAR agreements between the

States in the region. As there has not been expected achievement in establishing the

agreements, therefore, it is considered to further take up the matter so as to formalize

the required SAR agreements as early as possible.

2.6.1.3 The paper highlighted India’s initiative to achieve the required cooperation in the

region having commenced yearly Bay of Bengal, Arabian Sea and Indian Ocean

Region ATS Coordination meeting which gives ample opportunity to all the

participants of the neighboring states to discuss various issues pertaining to

cooperation required between the states. Mr. Oberoi informed the meeting that

Government of India has already established such arrangement with Govt. of Bhutan

for the cooperation of SAR services.

2.6.1.4 The paper proposed establishment of SAR agreements with neighbouring

states Nepal, Bhutan, Bangladesh, Myanmar, Kuala Lumpur, Male, Indonesia, Sri

Lanka, Thailand, Oman, Seychelles, Mauritius, and Sanaa Yemen with whom India

is sharing FIR boundaries.

2.6.1.5 The paper outlined the points that the agreement is expected to cover, as follows:

Critical activities near border areas for rescue operations.

Identify the resources which are available near the Search and Rescue area.

International cooperation at the quickest possible time.

Sharing of SAR resources.

Mutual exchange of SAR personnel.

Joint exercises both over marine and land areas.

2.6.1.6 The paper invited the meeting to review the enclosed draft Letter of Agreement and

take initiatives to formalize the Letter of Agreements on mutually agreed basis to set

in motion the requirement of providing SAR services for mutual assistance between

BOBASIO/4

03/10/2014 P a g e | 21


Kolkata, India, 22nd –24th September 2014 the BOBASIO states and establish working arrangements, within the respective

adjacent RCC/RSC’s for effective SAR process, based on Letter of Agreements.

2.6.2 WP 11: SAR Agreement between India and Maldives

2.6.2.1 This paper presented by Maldives informed the meeting that it already has SAR

Agreements between Australia and Sri Lanka and has drafted and is ready to discuss

and sign a similar agreement with India, in order to foster an effective co-operation

between India and Maldives in the provision of SAR services. Draft Letter of

Agreement is attached to the working paper as Annexure.

2.6.3 WP 12: SAR Agreement between Maldives and Mauritius

2.6.3.1 The paper presented by Maldives informed the meeting that it has drafted and is

ready to discuss and sign SAR agreement with Mauritius, in order to foster an

effective co-operation between Maldives and Mauritius in the provision of SAR

services. Draft Letter of Agreement is attached to the working paper as Annexure .

2.7 AGENDA ITEM 7 - ATM CONTINGENCY PLAN- LEVEL 2 AND PBN AND RNP

ROUTES.

2.7.1 WP/04: PBN Implementation in India

2.7.1.1 The paper presented by Mr. V. K. Mishra, Joint General Manager (ATM), AAI

informed the meeting that India has developed a “Robust” roadmap for

implementation in harmony with the APAC Regional PBN Implementation Plan.

2.7.1.2 Paper highlighted PBN implementation in India and its overall objective of improving

airspace and airport capacity and at the same time improve aviation operational

safety and benefits by reducing operational costs. PBN implementation promotes

Greener operations in all phases of flight. PBN implementation and its success is

directly linked to airline operator’s capability. Thus, fleet analysis is one of the most

important task in PBN implementation process.

2.7.1.3 Mr. Mishra discussed the key tasks in PBN implementation and informed the meeting

that AAI has developed in-house PBN flight procedures design and route planning

capability and has been developing PBN SIDs/STARs, LNAV/VNAV approach

procedures, RNP-AR procedures, Helicopter PinS and is in the process of developing

LP/LPV and GLS approach procedures.

BOBASIO/4

03/10/2014 P a g e | 22



2.7.1.4 The paper informed that as part of the PBN implementation programme, AAI has

been conducting workshops and seminars for industry-wide awareness about PBN

concepts, its implementation and benefits of the stakeholders. Airline operators and

defense authorities are regularly associated during various stages of PBN procedure

development and implementation at airport.

2.7.1.5 Paper highlighted AAI’s role in providing PBN training to the ATCOs, Flight crew &

Flight operations personnel and mentioned one such training conducted by AAI at

Doha for Qatar Airway Flight Operations personnel under the auspice of ASIOASG.

It also mentioned about AAI’s assistance in validating the PBN routes of Maldives

2.7.1.6 Mr. Mishra, informed the meeting that as part of PBN Implementation RNAV/RNP-

1 SIDs and Stars have been implemented at 10 busiest airports, viz, Delhi, Mumbai,

Bengaluru, Kolkata, Chennai, Hyderabad, Ahmedabad, Cochin, Trivandrum and

Guwahati; PBN based SID and STAR are also being implemented at 7 airports

including common use Military airport; RNP-APCH procedure has been implemented

at Cochin and 13 RNAV-5 city pair routes comprising of separate arrival and

departure routes have been implemented between major cities, resulting in increased

airspace capacity to accommodate more aircraft at preferred level.

2.7.1.7 The benefits achieved are reduced controller – pilot communication, better situational

awareness for the pilots, which also enhances safety apart from the most tangible

benefit of fuel saving and reduced CO2 emission.

2.7.2 IP/01: Implementation of PBN based RNAV 1 (GNSS) SID and STAR at GOA

airport (Civil Military Cooperation in implementation of PBN.

2.7.2.1 The Paper was presented by Mr. V. K. Mishra, Joint General Manager (ATM), AAI

and informed the need for a mechanism that could permit efficient utilization of

airspace at defense airport where scheduled civil flights also operate. A proposal for

implementation of Performance based Navigation Procedures was initiated by

Airports Authority of India to military authorities and all along included defense

authorities as a stakeholder during implementation thereby facilitating knowledge

and information sharing in respect of benefits and information of Performance Based

Navigation implementation.

2.7.2.2 AAI’s proposal to defense authorities intended to capitalize on the accuracy,

predictability and repeatability of PBN trajectories to manage arrivals and

BOBASIO/4

03/10/2014 P a g e | 23


Kolkata, India, 22nd –24th September 2014 departures so as to use limited airspace for this purpose, thereby permitting

simultaneous segregated military operations, if required, in the remaining airspace.

The design, development and implementation of the PBN procedures at defense

airports will be a collaborative effort.

2.7.2.3 PBN Implementation Project at Dabolim airport commenced with a conduct of PBN

seminar involving all stake holders. Thereafter detailed consultation with Navy

resulted in the development of common airspace concept where in airspace

constraints, availability of navigation infrastructure, modes of civil-military operation

were assessed. This analysis resulted in the collaborative development of concept

PBN procedures for promoting Continuous Climb Operations/Continuous Descent

Operations.

2.7.2.4 Establishment of structured arrival and departure flows not only results in conflict

resolution but facilitates in sequencing arrivals to reduce delays. Track-miles

reduction and optimized trajectories lead to fuel savings and emission reduction. All

these are achieved with reduction in controller workload.

2.7.2.5 Due to accurate and predictable trajectories of aircraft carrying out PBN procedure,

management of military movements is facilitated, thereby promoting efficiency of the

airspace from military perspective. In light of the benefits that are accruable due to

PBN procedures, Indian Navy envisages collaborative implementation of PBN

procedures at other common use naval airports.

2.7.2.6 In order to support the PBN implementation at Dabolim airport, AAI will undertake

to complete following other tasks-

PBN Training (Classroom & simulator) of the Indian Navy Air Traffic

Controllers

Validation and Safety Assessment

Regulatory approvals

Implementation of the procedures

Post implementation review

2.7.3 WP/13: ATM contingency plan for MALE FIR, Maldives

2.7.3.1 The paper presented by Maldives states that Air Traffic Management Contingency

Plan for Male’ FIR needs to be developed in close co-operation and collaboration with

BOBASIO/4

03/10/2014 P a g e | 24


Kolkata, India, 22nd –24th September 2014 the civil aviation authorities responsible for the adjacent FIRs.

2.7.3.2 ATM contingency plan to be implemented with the knowledge of the representatives

of the users of the airspace, to permit international flights to transit the Male’ FIR

without disruption, in the event of a natural disaster, man-made disaster or any other

event which makes the air traffic and supporting services normally undertaken by

the Male’ Area Control Centre (ACC) are partially or totally unavailable.

2.7.4 IP/02: ATM Contingency Plan- India

2.7.4.1 The paper presented by Mr V. K. Mishra informed the meeting of the status of ATM

Contingency Plan of Indian FIRs that aims at advance preparedness and

instantaneous response to a contingency arising due to disruption of Air Traffic

Services with an objective of providing safe and orderly passage to the over flying

traffic through Indian FIR . This is the second edition of the Indian Air Traffic

Management (ATM) Contingency Plan for Air Traffic Services (ATS) for the Upper

Airspace of the 4 Indian FIRs.

2.7.4.2 India, which is a member of the RACPTF (Regional ATM Contingency Plan Task

Force), brought to the notice of the meeting during BOBASIO-3 held at Hyderabad

from 22nd to 24th October 2013 that the Level 1 Contingency Plan of India was deemed

by the Taskforce to be robust, whereas the Level 2 plan, which was discussed in

BOBASIO/2 lacked the interfacing with the Level 2 contingency plan of the neighbors

and therefore relegated to a lower status of “incomplete” during the RACP/TF/2

(Bangkok, Thailand, 12 – 15 March 2013).

2.7.4.3 ATM Contingency Routings for geographical region was prepared by the Sub Working

Group (SWG) comprising of India, Bangladesh and Nepal during RACP/TF 2 meeting

in Bangkok and was presented by India during the BOBASIO-3 meeting, for east

bound departure from Nepal via ATS route R344 / A 201 with FLAS F310 and east

bound departure from Dhaka via G463/B465 with FLAS F 270.

2.7.4.4 Contingency routes promulgated in Indain ATM contingency plan provides

connectivity to all neighbouring states, therfore, paper suggested that these routes

may be agreed for Regional ATM Contingency plan (Level 2) and may consider the

same route to include in level 1 ATM contingency plan of the state.

BOBASIO/4

03/10/2014 P a g e | 25


Kolkata, India, 22nd –24th September 2014 2.7.4.5 The paper invited the meeting to adopt the Indian ATM contingency plan and

proposed Contingency Routes between India, Nepal and Bangladesh as Sub Regional

ATM Contingency plan as per decision of RACP TF/2.

2.8 AGENDA ITEM 8 - ATN/AMHS AND AIDC IMPLEMENTATION:

2.8.1 WP/03- ATS/DS coordination between Mumbai and Mogadishu FIC.

2.8.1.1 The paper presented by Somalia states that there are operational challenges between

Mumbai and Mogadishu relating to coordination of traffic between the two FIRs. Item

7.1 of the letter of agreement (LOA) between Mumbai Oceanic Control Centre (OCC)

and Mogadishu Flight Information Centre (FIC) LOA describes primary means of

communications for ATC coordination shall be International Direct Dialing (IDD via

public switching telephone network (PSTN) which does not meet operational

requirements and lack of it is a contributor to safety concerns between the two FIRs.

This mode of communications does not meet the minimum requirement of ATS/DS

connectivity which require establishment of direct speech services. Currently there is

no ATS/DS connectivity between Mumbai and Mogadishu FIC.

2.8.1.2 Mogadishu FIC implemented ATS/DS circuits to all its adjacent FIRs in 1998 through

a regional North AFI VSAT Network (NAFISAT) which has been operating with 99%

availability. However, Mumbai circuit remained dormant due to unavailability of

suitable connection at Mumbai.

2.8.1.3 The paper proposed that Mumbai implement this circuit or provide alternative mode

of connection that meet or exceed the proposed NAFISAT connectivity.

2.8.1.4 Paper also proposed to implement ATS Interfaculty Data Communication (AIDC)

between Mumbai and Mogadishu. This new requirement is possible if Mumbai can

provide the ICD of the installed AIDC at their end to facilitate interconnectivity with

Mogadishu AMHS currently in the final stages of implementation.

2.8.1.5 Whereas Mogadishu recognizes major improvements in coordination since BOBASIO

3 meeting, it is noted that there is still need to differentiate between requirements

under item 6.1 of the LOA and under item 6.5

BOBASIO/4

03/10/2014 P a g e | 26



2.8.1.6 The paper strongly recommends activation of ATS/DS circuit between Mumbai OCC

and Mogadishu FIC due to delayed response by either unit because of congestion in

the network or some other factors in use of PSTN.

2.8.2 WP/06: ATS Inter Facility Data Communication (AIDC) implementation in India &

with adjacent ATS units in the sub-region and the issues thereof.

2.8.2.1 The paper presented by Mr Anurag Sharma, AAI, summarised the present status of

AIDC implementation in India & with adjacent ATSU units in the sub Region. The

paper also tried to highlight the major issues involved in the implementation of AIDC.

2.8.2.2 Implementation of AIDC in India is being seriously pursued and extensive trials have

been carried out between dissimilar automations systems available at various ATS

units and the results have been quite encouraging. During trials within India several

interoperability and operational issues were encountered between dissimilar ATS

Automation Systems which have been mostly resolved. Some of the pending

operational and technical issues are being examined and will be resolved shortly.

2.8.2.3 India is having boundaries with adjacent ATSUs of MID and AFI Region states and

thus plans to establish AIDC with ATS units of different states viz. Bangladesh,

Myanmar, Pakistan, Nepal, Seychelles, Malaysia, Indonesia, Sri Lanka, Kenya,

Oman and Maldives.

2.8.2.4 Compatibility with existing Automation system using OLDI, replacement of OLDI

with PAN Regional ICD or co-existence of OLDI and AIDC applications are key issues

that may have to be addressed by some of the states for harmonized AIDC

implementation.

2.8.2.5 Successful trials have been carried out between Chennai- Kuala Lumpur and

Ahmedabad-Karachi. Teething issues were experienced during trials with Kuala

Lumpur and Karachi. Some of the issues were due to incorrect calculation of

checksum by the Kuala Lumpur system and due to route errors and mismatch in the

coordination timing.

BOBASIO/4

03/10/2014 P a g e | 27


Kolkata, India, 22nd –24th September 2014 2.8.2.6 The successful trials vindicate the need for close bilateral cooperation between the

concerned States for expeditious and successful implementation of AIDC. Further

AIDC trials are in pipeline between Delhi – Karachi and Delhi – Lahore. Subject to

readiness of adjacent ATSUs trials are also planned between Mumbai – Muscat,

Kolkata – Dhaka and Varanasi – Kathmandu.

2.8.2.7 Given the need to minimize the coordination errors, states involved are required to plan

their activities concurrently and exchange and coordinate their plan and modalities

bilaterally with concerned states to achieve harmonious AIDC implementation in the

Region. Bi-lateral agreements must be in place through MOUs or LOAs between the

member states and may be reviewed to meet the intended objectives.

2.9 AGENDA ITEM 9 - ANY OTHER BUSINESS

2.9.1 IP/10: Upper Airspace Harmonisation (UAH) of Kolkata Airspace.

2.9.1.1 The paper presented by Mr. Chandan Sen, GM (ATM), Kolkata, highlighted the on-

going Upper Airspace Harmonization program in Kolkata FIR.

2.9.1.2 The upper Airspace of Kolkata FIR above FL255 is being restructured as a single

continuum of airspace with the introduction of advanced ATS automation system

along with integration of 9 Radars & 8 ADS-B stations. The new technique of cross

coupling of VHF facilitates creation of multiple sectors to be operated dynamically.

ATS Inter Facility Data Communication (AIDC) permits automatic exchange of

aeronautical data among ATC units thereby reducing ATS coordination significantly.

2.9.1.3 Kolkata airspace is divided into 6 upper area control and one Oceanic control sectors.

The airspace has acquired some of the airspace from Delhi and Mumbai FIR with the

consideration of providing seamless ATC. There will be 8 lower area control centers

containing CTRs and TWRs which will handle traffic from ground level to FL255.

2.9.1.4 Kolkata will also have an efficient VHF network with cross coupling technique to

provide VHF coverage throughout the airspace even at lower levels. The Kolkata VHF

network is employing IP Radio and IP based VCS system for the first time in the

country and will be one of the largest networks using IP based system in the world.

2.9.1.5 Benefits of the Upper airspace harmonization include harmonized ATM procedures,

Reduction in separation between aircraft resulting in increased airspace capacity

BOBASIO/4

03/10/2014 P a g e | 28


Kolkata, India, 22nd –24th September 2014 utilization and enabling aircraft to get User Preferred Flight Profile, Even

Distribution of workload reducing controllers’ stress and fatigue, effective utilization

of Manpower by consolidating and deconsolidating Sectors dynamically depending on

Traffic density.

2.9.2 IP/09: ADS-B Data Sharing

2.9.2.1 The paper presented by Maldives described the implementation of ADS-B Out within

Male’ FIR to provide cost effective surveillance services over the areas where there is

no radar coverage, enhance the existing surveillance capability and support future

increase in airspace capacity.

2.9.2.2 Four ADS-B Receiver units have now been installed (November 2012) at 3 locations;

Male’ (2 receive-only ground-station units), Fuvahmulah and Kulhudhuffushi (1

ground-station each).

2.9.2.3 Through this paper Maldives proposed to share the ADS-B data with India and Sri

Lanka to improve efficiency and harmonization of airspace and seamless operations.

2.9.3 IP/08: Update on Implementation of ASBU Block 0 Modules

2.9.3.1 Paper presented by Mr. Sylvester Israel, General Manager (ATM), highlighted an

update on implementation of ASBU Block 0 Modules in India. India has updated the

national Air Navigation Plan in line with the ASBU role out keeping in mind the

ICAO strategic objectives of safety, capacity, efficiency and environmental

considerations. India is pursuing an aggressive implementation of Block Zero

Modules with emphasis on the critical Block-0 elements, to ensure regional and

global seamless Air Navigation Services over a crucial airspace connecting three

ICAO regions.

2.9.3.2 An update on the initiatives in implementation of Block Zero Modules being

undertaken by India is attached as Appendix A to this paper.

2.9.4 IP/03: Study of HF Coverage in Arabian Sea

2.9.4.1 The paper presented by Mr. Ajay Kapoor, Joint General Manager (ATM), AAI gave

an update on study of HFRT coverage in Arabian Sea in Mumbai FIR. It was observed

that the performance of HFRT communication for MWARA is better at FIR boundary

BOBASIO/4

03/10/2014 P a g e | 29


Kolkata, India, 22nd –24th September 2014 points as compared to other reporting points away from the FIR. The readability of

HFRT communication increases as the aircraft approaches the Mumbai FIR.

2.9.4.2 Paper also informed the meeting that on an average Mumbai is experiencing

approximately 35000 contacts in the MWARA routes in a month and attempts are

being made to further improve the performance of HFRT communication in the

oceanic airspace of Arabian Sea.

2.9.4.3 Meeting was informed that based on the study carried out in this regard,

infrastructure is being augmented by deploying more number of receivers and new

antenna system. Besides, diversity of operation is also envisaged for better

performance of HFRT communication.

2.9.5 WP/10: Provision of Airspace Safety Monitoring Data by Member States to

BOBASMA

2.9.5.1 The paper presented by Mr. A. P. Udayanarayan, Joint General Manager (ATM), AAI

provided a summary of the data required by EMA/RMA and being provided/not

provided by member states of BOBASMA. The Paper also presented the non-

compliance by member states of the various provisions contained in the EMA

Handbook and APANPIRG/23 Conclusion.

2.9.5.2. The paper informed that BOBASMA web page was created in August 2011for the

stake holders to view updates and download various templates. The web page can be

viewed at http://www.aai.aero/public_notices/aaisite_test/bobasma_index.jsp.

2.9.5.3 By regional agreement, as recorded in APANPIRG Conclusion 16/4, Traffic Sample

Data (TSD) within the Asia/Pacific Region is to be collected by all Member States for

the month of December each year for purposes of RVSM monitoring. During 2009,

APANPIRG/20 expanded the usage of this data by En-route Monitoring Agencies to

support regional implementations.

2.9.5.4 The Paper showed that except for Yangon FIR TSD data from other FIRs outside

India is not being provided to BOBASMA, instead the data is collected from RMA

(MAAR).

http://www.aai.aero/public_notices/aaisite_test/bobasma_index.jsp

BOBASIO/4

03/10/2014 P a g e | 30


Kolkata, India, 22nd –24th September 2014 2.9.5.5 The paper also highlighted summary of the Gross Navigational Error (LLD & LLE)

data received for the 24 month period from September 2012 to August 2014.

2.9.5.6 The paper stated that experience have shown that LLDs and LLEs have significant

influence on the outcome of safety assessments both before and after implementation

of PBN based separations. With the Regional PBN Plan establishing RNP2 as

‘preferred’ and RNAV2/RNP4/RNAV10 as ‘acceptable’ for oceanic and remote

continental airspace in the medium term (2013-2016), it is imperative that the ANSPs

in the region establish the means to detect and report the occurrence of large

horizontal plane deviations to the EMA for successful implementation of regional

initiatives.

2.9.5.7 Through this paper, BOBASMA urged the member states to collect and provide the

required data to BOBASMA.

2.9.6 WP/14: Safety oversight of RVSM operation in BOBASIO airspace.

2.9.6.1 The paper by Mr. A.P. Udayanarayan, Joint General Manager (ATM), AAI presented

a safety review of RVSM operations in the BOBASIO airspace and the need to

undertake risk mitigation measures to reduce the operational risk in the airspace.

The Paper also presented the need to expedite implementation of AIDC between the

different ATS units in the region and sharing of VHF/Surveillance data.

2.9.6.2 The Monitoring Agency for Asia Region (MAAR) conducts the safety oversight for the

RVSM operations in the BOBASIO airspace based on the LHD reports filed by the

ANSPs and/or Operators in the region. Airports authority of India had mandated

BOBASMA to be the nodal point for collecting, processing and submitting of reports

on the occurrences of Large Height Deviation (LHD) within the four Indian Flight

Information Regions to the Regional Monitoring Agency MAAR (Monitoring Agency

for Asia Region).BOBASMA continuously collects LHD reports from the four Indian

FIRs and submits the same to MAAR as well as receives the report of LHDs filed by

other adjoining FIRs like Yangon, Kuala Lumpur etc., involving Indian FIRs through

MAAR for further investigation.

BOBASIO/4

03/10/2014 P a g e | 31


Kolkata, India, 22nd –24th September 2014 2.9.6.3 The summary of all the LHD reports received by BOBASMA for the 12 month period

July 2013 to June 2014 showed that out of a total 175 reports received during this

period Category E accounts for 167 reports, which is about 95% of the total.

2.9.6.4 The paper also highlighted the initiatives taken on measures to mitigate the safety

risks as identified in a Special Coordination Meeting between India, Malaysia,

Myanmar and Indonesia in August 2014 RASMAG/19 meeting.

2.9.6.5 The paper stated that under-reporting of LHD occurrences in some of the major FIRs

like Mumbai and Delhi is a matter of concern. Given the fact that both these FIRs

account for more traffic than that in Chennai and Kolkata and also use only manual

voice coordination for coordinating flight data with adjacent ATS units, it is expected

that the reporting ratio will at least remain the same if not more than that in Chennai

or Kolkata FIRs. The overall reporting ratio for the BOBASIO airspace increased from

1:26,917 flight hours in 2012 to 1:11,540 flight hours in 2013.

2.9.7 Sideline Working Groups (SWGs) meetings:

2.9.7.1 In order to resolve coordination issues among BOBASIO States, four Sideline

Working Groups (SWGs) comprising of following States/Organizations were formed:

1 SWG-A: Airports Authority of India (Mumbai, Delhi and CHQ) &, Somalia,

ICAO expert-ICAO Somalia, Seychelles, Maldives

2 SWG-B: Airports Authority of India (Kolkata, Chennai and CHQ), Myanmar,

Bangladesh,

3 SWG-C: Airports Authority of India (Chennai and CHQ), Maldives, Indonesia

4 SWG-D: Airports Authority of India (CHQ), Indonesia, Singapore, Thailand and

others

2.9.7.2 All four groups intensively deliberated on various issues of mutual interests during

last sessions of 22.09.2014 and 23.09.2014.

2.9.7.3 Report on SWG-A Meeting:

2.9.7.3.1 SWG-A was divided into two subgroups. One subgroup was comprised of AAI (Mumbai)

& Somalia and other subgroup was comprised of AAI (Mumbai/CHQ), Maldives &

Seychelles.

BOBASIO/4

03/10/2014 P a g e | 32



2.9.7.3.1.1 Subgroup Meeting between Mumbai & Somalia:

2.9.7.3.1.1.1 ATS/DS circuit: The WP/03 presented by Somalia identified the need for ATS/DS for

better coordination. The paper suggested for an NAFISAT terminal at Mumbai. AAI

informed that due to regulations VSAT connectivity is not possible, however AAI will

assess the requirement of DSC.

2.9.7.3.1.1.2 Human factors in coordination on existing IDD hotline: It was pointed out by Mumbai

and Mogadishu that there are some human factors issues during coordination which

need to be looked into. The representatives were briefed about issues and it was

agreed that sensitization would be carried out to sort out the same.

2.9.7.3.1.1.3 Coordination issues: After deliberation on coordination issues, it was agreed that the

possibility of additional telephone terminals at Mumbai will be assessed. It was also

agreed that Mumbai shall sensitize controllers to adopt call back procedure in case

controllers are not able to immediately accept the call due to existing traffic on hand.

2.9.7.3.1.1.4 AIDC implementation: It was decided that on completion of ATM automation system

at Mogadishu the AIDC trials could be discussed. The contact details were exchanged

for the same. ICAO ASIA/PAC ICD version 3.0 being used in Indian automation

system has been forwarded via e-mail to representative of Mogadishu for briefing

their supplier.

2.9.7.3.1.2 Subgroup Meeting of Mumbai/CHQ/Delhi), Maldives & Seychelles:

2.9.7.3.1.2.1 Flight Level Allocation Scheme in Mumbai FIR

Seychelles pointed out that the FLAS applicable in Mumbai FIR is not contributing

towards economical operation due to highly restrictive flight level allocation. Flights

are being requested to lose as much as 10,000 feet in certain instances eg; to descend

from FL 370 to even FL270. Seychelles impressed that should there be a necessity to

descend aircraft Mumbai has ample distance and time to do so in their own FIR before

any conflicting routes. Mumbai informed the meeting that as already presented in

IP/05, Mumbai has already conducted sensitisation programme that FLAS is to be

BOBASIO/4

03/10/2014 P a g e | 33


Kolkata, India, 22nd –24th September 2014 used as last resort. As presented in paper the efforts have yielded positive results and

in August 2014. 74 percent data link capable flights were accepted at Non FLAS

levels. It was agreed that this is an encouraging result and Seychelles and Mumbai

will both collect data for the month of October 2014 and share the data and conduct

discussions during ASIOACG/9 in November 2014.

2.9.7.3.1.2.2 Human factors in coordination

Seychelles and Maldives pointed out that there are some human factors issues during

coordination which need to be looked into. The representatives were briefed about

issues and it was agreed that sensitisation would be carried out to sort out the same.

It was also agreed that if a controller exchange programme is initiated this will help

the controllers in appreciating each other’s working environment and go a long way

in resolving the human factors issues. It was agreed that the human factors issues

will be coordinated through emails. Contact details were exchanged for the same.

2.9.7.3.1.2.3 AIDC implementation

The AIDC trials between Mumbai and Maldives were conducted and had seen some

success. Mumbai informed that for last few days AIDC has been switched off for

software upgrades and by this weekend the talks can again resume. The contact

numbers were exchanged by Mumbai and Maldives for AIDC. Seychelles informed the

meeting that they were looking into the possibility of implementing AIDC in the near

future.

2.9.7.3.1.2.4. Coordination issues

Seychelles and Mumbai agreed that the instances of mis-coordination need to be

investigated and addressed on priority. The contact details were exchanged for the

same.

Following remedial actions were agreed:

a) Mumbai and Seychelles to conduct sensitization programme for controllers,

b) Mumbai and Seychelles to collect data on FLAS for month of October 2014 .

c) Mumbai and Seychelles to conduct sensitisation of controllers on Human Factors

issues

BOBASIO/4

03/10/2014 P a g e | 34


Kolkata, India, 22nd –24th September 2014 d) Mumbai and Seychelles agreed for exchange programme for Controllers to visit

ATC centres

e) AIDC trials between Male and Mumbai to resume at the earliest.

f) Addressing mis-coordination issues on priority

2.9.7.4 Report of SWG-B Meeting:

2.9.7.4.1 Subgroup Meeting between Kolkata -Myanmar:

2.9.7.4.1.1 Kolkata expressed its difficulty due to the last minute level change to east-bound

flight on route L 507. In order to mitigate risk due to last minute level changes, it was

agreed by Myanmar to adhere the provision contained in para 9.6 of LOA between

Myanmar and Kolkata.

2.9.7.4.1.1.1 Myanmar reported that Kolkata was not applying uniform separation standards at

MABUR. It was agreed that the provision of para 8.3 of LOA between Kolkata and

Myanmar should be adhered to. Any deviation from LOA shall be intimated to the

ATS Incharge concerned by email for analysis and remedial action.

2.9.7.4.1.1.2 Exchange of ATS messages via AFTN between Kolkata and Myanmar shall be done

on trial basis during lean period with prior coordination.

2.9.7.4.1.1.3 Data sharing with respect to surveillance and VHF link as well as AIDC issue will be

taken up by Myanmar.

2.9.7.4.1.1.4 It was agreed by Myanmar that separation over LSO shall continue to be provided by

Myanmar. Any non-compliance from this procedure shall be coordinated for analysis

and necessary action by the ATS Incharge concerned.

2.9.7.4.2 Subgroup Meeting between Kolkata -Bangladesh:

2.9.7.4.2.1 Unidirectional route between CEA and AAT was discussed between Bangladesh and

Kolkata. India should send such proposal to Bangladesh.

BOBASIO/4

03/10/2014 P a g e | 35


Kolkata, India, 22nd –24th September 2014 2.9.7.4.2.2 Creation of connector ATS route between CML and ONEKA to facilitate traffic

between Guwahati and Bangkok was discussed. When such connector ATS route

established, an addendum to existing LOA would be exchanged and signed.

2.9.7.4.2.3 Representative of Bangladesh expressed difficulty in following the provisions of LOA

with respect to coordination with Kolkata. However, Dhaka would positively

coordinate the boundary estimate with Kolkata for the east-bound departing from

airports within Dhaka FIR and transiting through Kolkata FIR (as per para 8.2 of

LOA). For other cases, Dhaka would ask aircrafts to contact next ATS unit at least 05

minutes before TCP (clear of traffic).

2.9.7.4.3 Subgroup Meeting between Chennai/Kolkata -Myanmar:

2.9.7.4.3.1 Yangon informed that Chennai OCC at times not responding to calls on DSC. The

Chennai representative was of the view that such grievances do exist on both sides

and hence the only way forward is to identify specific instances and bring it to the

notice of appropriate authorities of the adjacent unit so that remedial action could be

taken. The contact e-mail address of senior officials on both sides was exchanged.

2.9.7.4.3.2 Chennai informed that Yangon had been regularly allotting lower levels FL290 or

FL310 to eastbound traffic on P762 which was making difficult for Chennai OCC to

descent aircraft from higher levels such as FL370 or FL390 (normally levels

maintained by long haul flights from South Africa) due to crossing routes N877, L510

and P628. Yangon assured to look into matter and take appropriate action.

2.9.7.4.3.3 Chennai requested Yangon that information on any deviations to the west by traffic

operating on L759, more particularly westbound traffic that deviate to the left should

be informed to Chennai Oceanic as such traffic conflict with those operating on P628

with Chennai. For west-bound traffic via L759 deviating left, Yangon shall coordinate

with Kolkata and Chennai along with north deviation of aircraft via P628. South of

track deviation via P628 shall be coordinated with Chennai only. In case no contact

on DSC/Telephone, information regarding deviation can be coordinated through

AFTN with Kolkata DSC/Telephone shall be the mode of coordination except unusual

circumstances.

BOBASIO/4

03/10/2014 P a g e | 36


Kolkata, India, 22nd –24th September 2014 2.9.7.4.3.4. BOBASMA representative also briefed Yangon delegates on the requirements to send

data to BOBASMA. Yangon was also requested that prior to filing LHD report with

the RMA they should send information within a reasonable time period to the

involved Indian ACC for investigation and taking appropriate remedial actions.

2.9.7.5 Report on SWG-C Meeting:

2.9.7.5.1 Subgroup Meeting between Chennai - Male:

2.9.7.5.1.1 On AIDC Implementation Male informed that they are using AIDC ICD Version 3.0

in their SELEX ATM automation system and they would be configuring Chennai

AIDC address in their AIDC application by last week of October 2014. The AIDC

address of Chennai and Male was exchanged. It was agreed that trial operation could

commence by 1st week of November 2014.

2.9.7.5.1.2 On sharing of ADS-B data it was agreed to first exchange the ADS-B coverage

diagram of Trivandrum/Cochin of India and that of Kulhudufushi of Male, then decide

which ADS-B data needs to be shared. Chennai would send the requirements for

AIDC and the message sets and other technical requirements to Male by end of

September, 2014. Chennai would also to send a template of the agreement to Male for

approval by 15th October 2014. It was also agreed that in addition to sharing of ADS-

B, VHF data needs to be shared for effective control of air traffic.

2.9.7.5.1.3 Male also informed the meeting about complaints from aircraft about the difficulty in

contacting Trivandrum because of the low VHF coverage on R329. Male informed that

this could be resolved with the sharing of VHF data of VHF ground transceiver at

Hanimaadhoo International airport with India.

2.9.7.5.1.4 With regard to provision of data to the En-route Monitoring Agency BOBASMA, the

representative of BOBASMA apprised Male about the need to provide data on Large

Lateral Deviation (LLD) and Large Longitudinal Errors (LLE), data on PBN and data

link approvals of aircraft registered with Male and the annual one month (December)

Traffic Sample Data (TSD). Point of Contact (PoC) information of senior officials of

Male and BOBASMA was exchanged. A demonstration of the BOBASMA website and

the contents of the webpage was provided to the Male representative.

BOBASIO/4

03/10/2014 P a g e | 37



2.9.7.5.2 Subgroup Meeting between AAI (Chennai) – Indonesia (Jakarta):

2.9.7.5.2.1 On AIDC implementation, Jakarta informed that they have to first upgrade their

ATM automation system and increase the Bandwidth for provision of AIDC. As per

Jakarta the procurement process has already started and they expect that they would

be able to upgrade their system by July 2015. Further, Jakarta informed that work

for increasing bandwidth is in progress. It was proposed to have a bilateral meeting

between India and Indonesia at an early date convenient to both India and Indonesia

to discuss and finalize AIDC implementation.

2.9.7.5.2.2 Regarding sharing of Surveillance/VHF data it was agreed that both India and

Indonesia first share coverage diagram of the proposed Car Nicobar ADS- B ground

station and that of MSSR/ADS- B ground station at Banda aceh. Since it is expected

that Indian ADS-B at Car Nicobar would be commissioned by June 2015, it was

proposed to take up further discussion during the proposed bilateral meeting. It was

also agreed that both sharing of ADS-B data and sharing of VHF should take place

simultaneously.

2.9.7.5.2.3 Chennai and Jakarta agreed to coordinate for conducting ADS/CPDLC bench test in

coordination with the CRA Boeing to test various interoperability issues related to

auto handoff of FANS 1A aircraft between the two ACCs. ACARS address and Login

address of Chennai ADS/CPDLC ground station was provided to Jakarta.

2.9.7.5.2.4 Both Chennai and Jakarta were of view that it would be more efficient if through a

tripartite dialogue between India, Malaysia and Indonesia, P574 is included as

part of Jakarta FIR. At present the route passes through Kuala Lumpur for a very

short distance after exiting Chennai FIR and before entering Jakarta FIR. Kuala

Lumpur does not have both VHF and surveillance coverage in the area whereas

Jakarta has excellent VHF and Surveillance coverage in that area. This will also

reduce the LHD occurrences in this area. It was decided to further deliberate

on this issue during the proposed bilateral meeting.

2.9.7.5.2.5 Jakarta also informed that Chennai should allot minimum FL320 for westbound

aircraft on N563. Chennai representative informed that the matter will be taken up

BOBASIO/4

03/10/2014 P a g e | 38


Kolkata, India, 22nd –24th September 2014 with higher authorities at Chennai/CHQ, since this might require revisiting the LOA

between Chennai and Jakarta. Further discussion and review of LOA to be taken up

in the bilateral meeting.

2.9.7.5.2.6 With regard to provision of data to the En-route Monitoring Agency BOBASMA the

representative of BOBASMA apprised Jakarta about the need to provide data on

Large Lateral Deviation (LLD) and Large Longitudinal Errors (LLE), data on PBN

and data link approvals of aircraft registered with Indonesia and the annual one

month (December) Traffic Sample Data (TSD). Point of Contact (PoC) information of

senior officials of Indonesia and BOBASMA was exchanged. A demonstration of the

BOBASMA website and the contents of the webpage was provided to the Jakarta

representatives.

2.9.7.5.3 Subgroup Meeting between Chennai/Kolkata -Myanmar:

2.9.7.5.3.1 Yangon informed that Chennai OCC at times was not responding to calls on DSC. The

Chennai representative was of the view that such grievances do exist on both sides

and hence the only way forward is to identify specific instances and bring it to the

notice of appropriate authorities of the adjacent unit so that remedial action could be

taken. The contact e-mail address of senior officials on both sides was exchanged.

2.9.7.5.3.2 Chennai informed that Yangon had been regularly allotting lower levels FL290 or

FL310 to eastbound traffic on P762 which was making it difficult for Chennai OCC to

descent aircraft from higher levels such as FL370 or FL390 (normally levels

maintained by long haul flights from South Africa) due to crossing routes N877, L510

and P628. Yangon assured to look into matter and take appropriate action.

2.9.7.5.3.3 Chennai requested Yangon that information on any deviations to the west by

traffic operating on L759, more particularly westbound traffic that deviate to the

left should be informed to Chennai Oceanic as such traffic conflict with those

operating on P628 within Chennai. For west-bound traffic via L759 deviating left,

Yangon shall coordinate with Kolkata and Chennai. In case no contact on

DSC/Telephone, information regarding deviation may be coordinated through AFTN

provided the receipt of the information is confirmed over DSC/Telephone at the

earliest possible time.

2.9.7.5.3.4 BOBASMA representative also briefed Yangon delegates on the requirement to send

data to BOBASMA. Yangon was requested that prior to filing LHD report with

BOBASIO/4

03/10/2014 P a g e | 39


Kolkata, India, 22nd –24th September 2014 the RMA they should send information within a reasonable time period to the

involved Indian ACC for investigation and to take appropriate remedial actions.

2.9.7.6. Report on SWG-D Meeting: SWG-D:

2.9.7.6.1 As agreed in BOBSIO/3 Meeting: Indonesia and India agreed on Letter of

Coordination Agreement LOCA regarding airspace reservation for rocket launching

activity. The LOCA was signed and exchanged between two States-Indonesia and

India.

2.10 AGENDA ITEM 10: FUTURE MEETINGS

2.10.1 Electing Chairperson and Member Secretary for BOBASIO Meetings: As agreed in

BOBASO/3 meeting, delegates attending BOBASIO/4 meeting elected India as

Chairperson and Secretary for BOBASIO meetings for next two years (BOBASIO/5

and BOBASIO/6) so that action items could be meticulously and purposefully tracked.

2.10.2 LOGO for BOBASIO Meetings:

2.10.2.1 It was expressed by delegates that BOBASIO should have own Logo in place of having

logo of any individual State/Organisation.

2.10.2.2 A Logo designed by Mr Balakrishnan K Anat, Assistant General Manager (ATM) from

AAI, was unanimously accepted by the meeting. The logo is as appended below:

Figure 3: BOBASIO Logo adopted by the meeting

BOBASIO/4

03/10/2014 P a g e | 40



2.10.2.3 In logo, the part of the globe featuring the BOBASIO States is embraced by the

SMOOTH GREEN ring.

2.10.2.4 The smoothness denotes the seamless operation.

2.10.2.5 The GREEN colour features the environmental benefits brought out by the

BOBASIO Meetings.

2.10.2.6 The safety, efficiency and environmental benefits are symbolically highlighted by

the aircraft in the green ring embracing the globe.

3. CLOSING OF THE MEETING:

3.1 At the end of the meeting, Mr Kanhaya Lal, General Manager (ATM), AAI, discussed

the status of action items of BOBASIO/3 and impressed on the members to identify

the Point of Contact from each member state for coordination and follow up of ongoing

action items.

3.2 Secretary of the meeting presented the action items of BOBASIO/4 and assured the

meeting that a follow up mechanism will be worked out to keep the members updated

on various action items from BOBASIO/3 and BOBASIO/4. The Meeting adopted the

action items proposed by the Secretary.

3.3 A Letter of Agreement was signed between Airports Authority of India and DGCA,

Indonesia on “Notification of Activities Requiring Temporary Airspace Restriction”.

3.4 Chairman of the meeting Mr Ram Lal, declared the meeting closed with his address

and concluded that the objective of the meeting has been met still there is a

substantial work to do and urged the members that there is a need for maximizing

interactions between the meetings to complete the ongoing action items.

3.5 Mr Chandan Sen, GM (ATM), Kolkata gave vote of thanks.

BOBASIO/4

03/10/2014 P a g e | 41


Kolkata, India, 22nd –24th September 2014 APPENDIX A

AGENDA ITEMS

Agenda Topic

Item 1 Adoption of Agenda

Item 2 Review of progress on action items of BOBASIO/3

Item 3 Review of APAC Seamless ATM Plan and its implementation

Item 4 Strategic ATM Plans of participating States

Item 5 Cyber security- Preparation of Road map

Item 6 AIS and SAR agreements

Item 7 ATM Contingency Plan- Level 2 and PBN and RNP routes

Item 8 ATN/AMHS and AIDC Implementation

Item 9 Any other Business

Item 10 Future meetings

BOBASIO/4

03/10/2014 P a g e | 42


Kolkata, India, 22nd –24th September 2014 APPENDIX B

SUMMARY OF WORKING PAPERS AND INFORMATION PAPERS

WP no. Topic Presented By

WP/01 Agenda, time table and working arrangements Secretariat

WP/02 Review of progress of action items of BOBASIO/3 Secretariat

WP/03 ATS/DS Coordination Between Mumbai and Mogadishu FIC Somalia

WP/04 PBN Implementation in India

Airports

Authority of

India

WP/05 Cyber Security for Air Navigation Systems

Airports

Authority of

India

WP/06

ATS Inter-facility Data Communication (AIDC)

implementation in India & with adjacent ATS units in the

sub-region and the issues thereof.

Airports

Authority of

India

WP/07 Airspace Capacity Enhancement in BOBASIO Region Airports

Authority of

India

WP/08 PBN Implementation in the Region through Collaboration

Airports

Authority of

India

WP/09 Search and Rescue

Airports

Authority of

India

WP/10 BOBASMA/Occurrences of LLDS and LLES

Airports

Authority of

India

WP/11 SAR agreement between India and Maldives Maldives

WP/12 SAR agreement between Maldives and Mauritius Maldives

WP/13 ATM contingency plan for Male FIR, Maldives Maldives

WP/14 Safety Oversight of RVSM Operation in BOBASIO airspace Airports Authority

of India

BOBASIO/4

03/10/2014 P a g e | 43


Kolkata, India, 22nd –24th September 2014 APPENDIX B (Contd)

SUMMARY OF WORKING PAPERS AND INFORMATION PAPERS

IP no. Topic Presented By

IP/01 Implementation of PBN Based RNAV 1 (GNSS) SID

And STAR At Goa Airport (Civil Military Cooperation

In Implementation of PBN)

Airports

Authority of

India

IP/02 ATM Contingency Plan India Airports

Authority of

India

IP/03 Study of HF Coverage in Arabian Sea Airports

Authority of

India

IP/04 GAGAN/ S-BAS Services for The Region Airports

Authority of

India

IP/05 Traffic Flow In Oceanic Airspace Of Mumbai FIR,

Evaluation of FLAS and its Review

Airports

Authority of

India

IP/06 Flexible Use of Airspace FUA Manual India Airports

Authority of

India

IP/07 Ground Based Augmentation System (GBAS) Airports

Authority of

India

IP/08 Aviation System Block Upgrade (ASBU) Update India Airports

Authority of

India

IP/09 ADS B Data Sharing Maldives

IP/10 Upper Airspace Harmonisation (UAH) of Kolkata

Airspace

Airports

Authority of

India

BOBASIO/4

03/10/2014 P a g e | 44


Kolkata, India, 22nd –24th September 2014 APPENDIX C

ORDER OF BUSINESS

Monday, 22 September, 2014

Tuesday, 23 September, 2014

Time Program

0830-0930 Registration

0930-1000 Inaugural Session

1000-1030 Photo session followed by Tea/Coffee Break

1030-1300 Discussions on Agenda Items

1300-1400 Lunch


1500-1530 Tea/Coffee Break

1530-1700 Side Line meeting -1

Time Program




1300-1400 Lunch



1530-1700 Side Line meeting -2

BOBASIO/4

03/10/2014 P a g e | 45


Kolkata, India, 22nd –24th September 2014 APPENDIX C (Contd.)

Wednesday, 24 September, 2014

Time Program

0930-1030 Review of Draft Report


1100-1200 Adoption of Report

1200-1300 Closing of Meeting

1300-1400 Lunch

BOBASIO/4

03/10/2014 P a g e | 46


Kolkata, India, 22nd –24th September 2014 APPENDIX D

ORDER OF DISCUSSIONS

Monday, 22 September, 2014

TIME SESSION AGENDA

ITEM

WP/IP

NO

SUBJECT

PRESENTED

BY

1030-1300 Session 1

1 WP/01 Proposed Agenda Secretariat

2 WP/02 Review of action items of

BOBASIO 3

Secretariat

9 IP/10

Upper Airspace Harmonisation

(UAH) of Kolkata Airspace

Airports

Authority of

India

4 IP/05

Traffic flow in oceanic airspace of

Mumbai FIR, Evaluation of FLAS

and its Review

Airports

Authority of

India

7 WP/04 PBN Implementation in India

Airports

Authority of

India

9 IP/09 ADS B data Sharing Maldives

1300-1400 Lunch Break

1400-1500 Session 2

7 IP/01

Implementation of PBN Based

RNAV 1 (GNSS) SID and STAR at

Goa Airport (Civil Military

cooperation in Implementation of

PBN)

Airports

Authority of

India

5 WP/05

Cyber Security for Air Navigation

Systems

Airports

Authority of

India

4 IP/06 Flexible Use of Airspace (FUA)

Airports

Authority of

India

8 WP/03 ATS/DS Coordination Between

Mumbai and Mogadishu FIC

Somalia


1530-1700 Session 3 Side Line meeting –I

BOBASIO/4

03/10/2014 P a g e | 47


Kolkata, India, 22nd –24th September 2014 APPENDIX D (Contd.)

ORDER OF DISCUSSIONS

Tuesday, 23 September, 2014

TIME SESSION AGENDA

ITEM

WP/I

P NO

SUBJECT

PRESENTED BY

0930-1100 Session 1

8 WP/0

6

ATS Inter-facility Data

Communication (AIDC)

implementation in India & with

adjacent ATS units in the sub-region

and the issues thereof.

Airports Authority

of India

4 IP/07 Ground Based Augmentation System

(GBAS)

Airports Authority

of India

4 WP/0

7

Airspace Capacity Enhancement in

BOBASIO Region

Airports Authority

of India

7 WP/1

3

ATM contingency plan for Male FIR,

Maldives

Maldives

7 IP/02 ATM Contingency Plan INDIA Airports Authority

of India


1130-1300 Session 2

6 WP/0

9

Search and Rescue Airports Authority

of India

6 WP/1

1

SAR agreement between India and

Maldives

Maldives

6 WP/1

2

SAR agreement between Maldives

and Mauritius

Maldives

9 IP/08 Aviation System Block Upgrade

(ASBU)

Airports Authority

of India

4 IP/04 GAGAN/ S-BAS Services for the

Region

Airports Authority

of India

1300-1400 Lunch Break

1400-1500 Session 3

3 WP/0

8

PBN Implementation in the Region

through Collaboration

Airports Authority

of India

9 IP/03 Study of HF Coverage in Arabian

Sea

Airports Authority

of India

9 WP/1

0

BOBASMA/Occurrences of LLDs and

LLEs

Airports Authority

of India

BOBASIO/4

03/10/2014 P a g e | 48



Wednesday, 24 September, 2014

9

WP/1

4

Safety Oversight of RVSM Operation

in BOBASIO airspace

Airports Authority

of India

10 - Future Meetings

Airports Authority

of India


1530-1700 Session 4 Side Line meeting –II

TIME SESSION ITEM

0930-1030 Session 1 Review of Draft report


1100-1200

Session 2

Adoption of report

1200-1300 Closing of meeting

1300 -1400 Lunch Break

1400

Onwards Local Sight seeing Tour

BOBASIO/4

03/10/2014 P a g e | 49


Kolkata, India, 22nd –24th September 2014 APPENDIX E

LIST OF PARTICIPANTS

Name (Mr./Ms.) Title/Designation E-mail ID/ Tel No

1

. BANGLADESH

1. Shamsul Haque

Director, ATS

& Aerodrome

CAAB [email protected]

[email protected]

2.

Md. Masud Khan

Asstt. Director, ATS


+8801199097646

3. Md. Shakhawat

Hossain


+8801718167345

2. INDONESIA

1 Elfi Amir

Deputy Director of

ATM, DGCA

DGCA [email protected]

2 Edwin Arif Wibowo

Air Nav. Inspector DGCA

[email protected]

3 Ahmad Setiawan

ACC Manager FIR

Jakarta

AirNav [email protected]

+628174805236

4

Teguh Harnomo

ATFM Manager AirNav

[email protected]

+6281281700310

mailto:[email protected]








BOBASIO/4

03/10/2014 P a g e | 50



Name (Mr./Ms.) Title/Designation E-mail ID/ Tel No

3 MALDIVES

1 Mohamed Athuhar

Supervisor, Male

ACC

Maldives Airports [email protected]

[email protected]

+960 333 1711

2 Ibrahim Imran

Engineer, Air

Traffic Electronics

Maldives Airports [email protected]

[email protected]

+960 333 1711

4 MYANMAR

1.

Ohnmar Tun

Manager(ATM)

DCA [email protected],

[email protected],

[email protected]

+95 1 533040

[email protected]

2.

Phyu Phyu Win

Shein

Manager (ATM)

DCA Email: [email protected]

Tel: +95949341292

5 SEYCHELLES

1.

E. Samson

General Manager

(ANS)

CAA [email protected]

+ 248 252 72 06

2.

Louis Mancienne

Manager (ATS)


+ 248 2513 566

6 SINGAPORE

1.

Michael Shee

ATC Manager

(ATM OPS

Planning)


(65) 6541 2454

2.

Jimit Singh

Tech. Officer

(ATM OPS

Planning)


(65) 6595 6055














BOBASIO/4

03/10/2014 P a g e | 51


Kolkata, India, 22nd –24th September 2014 Name (Mr./Ms.) Title/Designation

E-mail ID/ Tel No

7 SOMALIA

1

Wilson Owino

ATS Expert

(Operations)

FISS [email protected]

+254-20-7622890

2

Ali Abdulle Gutale

ATS Officer


[email protected]

+254-20-7622785

3

Moses Lusambili

Airport

Maintenance

Engineer


+254-20-7622495

8 THAILAND

1.

Suvichan

Sthitgitpichead

Director network

operation,

ATM centre

AEROTHAI

Thailand

[email protected],

[email protected], [email protected]

+95 1 533040

[email protected]

9 EMIRATES AIRLINES, UAE

1. Mr. Faisal Al

Khaja

GCAA [email protected]

10 INDIA( Other than Airports Authority of India)

1.

Comdt. R. Nath,

TM Chief Staff

Officer(Aviation)

India Coast

Guard

[email protected]

+918902497493

2.

Cdr. Manmohan

Bugalia

SATCO, Goa

Indian Navy [email protected]

+91-9766531818

3.

Habibur Rahaman

Biswas

Scientist-D,

Director I/C AMO

Kolkata

India IMD [email protected]

+91-9433125951

4. Suresh Ram

Scientist-E

India IMD [email protected]

+91-9868851165














BOBASIO/4

03/10/2014 P a g e | 52



E-mail ID/ Tel No

10 INDIA( Other than Airports Authority of India)

5. Wg. Cdr. Ashesh

Kumar

Indian Air Force [email protected]

+91-7702185105

11. Airports Authority of India

1.

Ram Lal, ED (ATM) [email protected]

[email protected]

2.

P.K.

Bandopadhya

ED (CNS-P) [email protected]

3.

A.K. Dutta ED(ATM) [email protected]

4.

S.K. Oberoi GM (ATM), [email protected]

5.

S.V. Sathish GM (GAGAN) [email protected]

6.

S. Chadha GM (ATM-ATS) [email protected]

[email protected]

7.

A.P. Gajbe GM (ATM-IL) [email protected]

+91-9650555192

8.

Kanhaya Lal GM (SQMS) [email protected]

+91-9650596385

9.

Sylvester Israel GM (ATM-SR),

Chennai

[email protected]

[email protected]

9444389021

10.

J. Dasgupta GM (ATM),

Mumbai

[email protected]

[email protected]

9870363692

11.

M.C. Dangi GM (ATM), IGIA,

N. Delhi.

[email protected]

[email protected]

12.

M.L. Chakravarty GM (CNS), CHQ [email protected]

13.

Pan Singh GM (NAV-

CMC),CNS, CHQ [email protected]

14.

P. Mondal GM(CNS),

Mumbai

[email protected]

+91-9869057512

15.

C.R.

Sudhir

GM(CNS)

Bengaluru [email protected]

16. V.K. Mishra Jt. GM (ATM) [email protected]

17.

Sambath Kumar Jt. GM (ATM) [email protected]

+91-9910065943

mailto:%20%[email protected]























BOBASIO/4

03/10/2014 P a g e | 53



E-mail ID/ Tel No

11. Airports Authority of India

18.

Rakesh Bhatnagar Jt. G.M. (ATM) [email protected]

+919650077447

19.

Dr. G. Manish Jt. GM (ATM), IGIA Delhi. [email protected]

[email protected]

9968697800

20. Udayanarayan Jt. GM (ATM) Chennai [email protected]

[email protected]

21. Chandan Sen, GM(ATM) [email protected]

+91-9433053247

22. Kalyan Choudhury Jt.GM(SQMS) [email protected]

+91-9433053247

23. Purbita T Sinha Jt.GM(ATM-Trng.) [email protected]

+91-9007007268

24. S Ghosh GM(CNS) [email protected]

+91-8902499903

25. Sisir De Jt.GM(CNS) [email protected]

+91-9433007222

26. S P. Lahari Jt.GM(CNS) [email protected]

+91-9163610598

27. A B Joshi Jt.GM(ATM) [email protected]

+91-9820138296













BOBASIO/4

03/10/2014 P a g e | 54


Kolkata, India, 22nd –24th September 2014 APPENDIX F RREVIEW OF ACTION ITEMS OF BOBASIO/3

Action

Item

ID

Description Responsible

State/

Organisation

Status Remarks

3/1 BOBASIO States to study

the Seamless ATM Plan

and in accordance with the

requirements outlined in

the plan, review version

1.0 of the Asia/Pacific

Seamless ATM Plan,

utilize the regional plan to

develop a State plan with

implementation timelines

for applicable Seamless

ATM elements and also

ensure that relevant

decision-makers are

briefed on the State

Seamless ATM Plan,

further, based on

consultation, submit the

first Regional Seamless

ATM reporting form to the

ICAO Regional Office by

the 1st March 2014.

Concerned

States India,

Bangladesh and

Singapore have

submitted

Regional

Seamless ATM

reporting form to

the ICAO

India requested

other States to

submit

Asia/Pacific

Seamless ATM

Plan to ICAO

Regional Office.

Open

States agreed

to share

update on

ASBU

implementatio

n plan in

BOBASIO 5

meeting

3/2 States to consider

declaring airspace

corresponding to its ATM

capability and consider

non-exclusive type of

airspace classification, to

allow for utilization of such

airspace by aircraft not

meeting the requirements.

BOBASIO

States

States requested

ICAO APAC

regional Office to

provide guidance

material

Open

3/3 India to follow up the task

of joint routes design with

India and

neighbouring

States

Ongoing

BOBASIO/4

03/10/2014 P a g e | 55


Kolkata, India, 22nd –24th September 2014 neighbouring States for

mutual benefit.

3/4 India, Malaysia, Indonesia

and other BOBASIO

States to collaborate, to

establish RNP 4 routes in

the Bay of Bengal to

support 30/30 NM

separation.

India,

Malaysia

Indonesia

and other

BOBASIO

States

India introduced

30NM Reduced

Longitudinal

Separation wef 18th

September 2014 on

4 ATS Routes.

Other States to

collaborate.

Indonesia will be

ready by March,

2015

Revised timeline

from Malaysia, and

Muscat awaited

3/5 IATA to sensitize airline

operators to equip aircraft

with FANS/1A data link

capability

IATA Open IATA did not

attend

meeting.

3/6 Indonesia to provide

details of the actual (not

theoretical circular

200NM) range of ADS-B

located in Banda-Aceh, so

that the requirement of

data sharing between

Indonesia and India can be

explored.

Indonesia ADB-B has 200 NM

in W and NW of

Banda Aceh

towards Chennai

FIR

Completed

3/7 Malaysia and India to

provide an update on

possibility of sharing of

Port Blair ADS-B data

with Malaysia and enable

seamless transfer of

communication at the FIR

Malaysia and

India

Revised timeline

March 2015

BOBASIO/4

03/10/2014 P a g e | 56


Kolkata, India, 22nd –24th September 2014 boundary for

implementation of 50-50

NM separation, at the

SAIOACG meeting in

February 2014.

3/8 All BOBASIO States to

report occurrences of LLDs

and LLEs to BOBASMA in

timely manner. They

should sensitize their

controllers to report the

occurrences of LLDs and

LLE.

States

obliged to

submit data

to

BOBASMA

Ongoing

3/9 Indonesia to issue an

Aeronautical Information

Circular (AIC) as soon as

possible to alert aircraft

operators of their intention

to issue an ADS-B

mandate in 2016 or any

later year, with a suitable

prescribed lead time.

Indonesia Completed

3/10 Mumbai OCC to submit a

study on traffic pattern

to/from AFI regions in

terms of time of operation

and density to facilitate the

evaluation of the FLAS

and its review.

India Mumbai submitted

study report

An ongoing

process for

evaluation of

FLAS

3/11 Mumbai to conduct a

sensitization programme

for OCC controllers, with

an emphasis on employing

FLAS as a last resort for

level allocation and

avoiding its adoption as a

routine tool.

India Achieved results

from 46% to 64 %

Mumbai and

Seychelles are

jointly working

out modalities

to achieve 100

%

3/12 AAI to conduct a study on

performance of HF in

Arabian Sea airspace and

India Completed

BOBASIO/4

03/10/2014 P a g e | 57


Kolkata, India, 22nd –24th September 2014 submit its findings to

pertinent adjacent FIR

Controlling authority for

optimization.

3/13 To ensure required level of

position reporting by

Kenya Airways and flight

crew of other AFI region

based airlines, ICAO

EASAF Office shall

coordinate with concerned

airlines. These airlines to

be sensitized regarding

significance, safety and

regulatory provisions of

establishing and

maintaining listening

watch on appropriate

frequency and timely

position reporting to ATC

e.g. The flight crew of

aircraft operating from

AFI region and

subsequently entering in

Mumbai FIR to be

reminded of the

requirement to contact

Mumbai FIC at least 10

minutes before crossing

Mumbai –

Mogadishu/Seychelles FIR

boundary

ICAO

Nairobi

Office

Mogadishu

Seychelles

FIR

Controlling

ANSPs

IATA

ICAO EASAF

Office coordinated

with Kenya

Airways for

position reporting

and sensitizing

pilots for

maintaining

listening watch and

requirement

position reports.

Completed

IATA did not

attend

meeting.

3/14 LOA between Kolkata ACC

and Yangon ACC to be

signed by Appropriate

Authority of Yangon and

sent to Airports Authority

of India.

Yangon Open

3/15 Draft agreement on

sharing of ADS-B data to

India and

Yangon

Likely to be signed

in November 2014

BOBASIO/4

03/10/2014 P a g e | 58


Kolkata, India, 22nd –24th September 2014 be exchanged between

India and Myanmar.

Open

3/16 Coordination Procedures

between Chennai OCC and

Kuala Lumpur ACC to be

signed by the appropriate

authorities of Malaysia

and India.

India and

Malaysia

LOAs exchanged

but not signed

Open

Malaysia did

attend the

meeting

3/17 LOA/Coordination

Procedures for AIDC data

exchange between Chennai

and Kuala Lumpur to be

finalized

India and

Malaysia

Open

Trials are Ongoing

3/18 Development of ATM

Contingency Plan Level 2/3

(Note: ATMTF meeting

scheduled in the 3rd week of

Nov, 2013 and is being

attended by India)

BOBASIO

States

Open

Discussion ongoing

for developing ATM

Contingency Plan

3/19 Neighbouring States to

expedite execution of SAR

agreement(s), providing

details of the responsibility

of States and their

agencies, especially in

Cross Border Areas.

BOBASIO

States

On going

(Update from the

states required)

3/20 BOBASIO States which

are planning A-CDM to

ensure the “Business

Rules”; terminology and

procedures were aligned

regionally to ensure that

user interfaces with

various A-CDM systems

are common.

BOBASIO

States

ICAO RSO has

circulated the

Template for the

states to Comply

with the Business

rules

3/21 Neighboring

Centers adjacent

India to share their

plan with India for

Neighbouring

BOBASIO

States to

India

Open

Target date of

implementation

Mogadishu AIDC

may be

BOBASIO/4

03/10/2014 P a g e | 59


Kolkata, India, 22nd –24th September 2014 AIDC

implementation in

a time bound

manner.

implemented by

Dec, 2014

Myanmar Jan

2015

Indonesian Oct

2015

Draft LOA

exchanged

between

Myanmar and

India

3/22 ICAO to

standardize single

ICD version within

APAC region and

all the regions of

ICAO to achieve

harmonious

implementation.

ICAO

Regional

Office

Completed in

APANPIRG25

3/23 India to coordinate

through POC for further

feasibility studies on

GAGAN and feedback from

the member States.

India Ongoing

3/24 A more robust Agenda of

BOBASIO in line with the

SAIOACG meeting is to be

finalized based on a

structured approach

BOBASIO/4 Completed

3/25 The BOBASIO meeting to

consider election of

Chairperson and Secretary

for BOBASIO meetings

and their continuity for

two years so that action

items could be

meticulously and

purposefully tracked

BOBASIO/4 India will be

Chairperson and

Secretary for next

two years

3/26 The Member States other

than India to consider

hosting the meetings for

All

BOBASIO

States

Indonesia after

consultation with

Management will

BOBASIO/4

03/10/2014 P a g e | 60


Kolkata, India, 22nd –24th September 2014 better participation and

greater involvement

inform member

secretary for

hosting 2015

meeting.

3/27 The meeting report to be

submitted to ATM

subgroup so that issues

may further be discussed

at ATMSG meeting.

Regional

officer ATM,

APAC

Completed and

ICAO has

presented the same

in ATM/SG03

3/28 Indonesia and India to

evaluate the draft Letter

of Coordination

Agreement LOCA

regarding airspace

reservation for rocket

launching activity for

approval and signing.

Indonesia

and India

Open

Consultation in

progress

BOBASIO/4

03/10/2014 P a g e | 61


Kolkata, India, 22nd –24th September 2014 APPENDIX G

ACTION ITEMS OF BOBASIO/4

Action

Item

ID

Description Responsible

State/

Organisation

Target Remarks

4/1 Establishing POC for

follow up actions of

BOBASIO Meetings

All BOBASIO

States

Oct, 2014

POC to be

forwarded to

BOBASIO

Secretary

rbhatnagar@aai.

aero

4/2 ICAO - Ionospheric Study

Task Force to study the

issues involved in the

implementation of GBAS

in equatorial region and

suggest the solution

BOBASIO

Secretary

Draft conclusion

to be sent to

ICAO ATM

Subgroup

4/3 BOBASIO States to share

information on strategies

being adopted to establish

Cyber security framework

All BOBASIO

States

BOBASIO/5

4/4 Identification and

prioritization ATS routes

for implementation of

RHS (50/50 and 30/50)

Meeting to identify point

of contacts and

coordinators for the task.

Muscat

Bangladesh

Indonesia

Malaysia

Myanmar

Pakistan

Sri Lanka

Maldives

Indonesia will

be ready by

March, 2015

Response from

other States

awaited

4/5 Review the draft letter of

agreement and formalize

SAR LOAs with adjacent

RCCs

All BOBSIO

States

Dec, 2014

State should be

ready with the

agreements before

the next SAR TF-

4/6 Maldives, India, Sri Lanka

and Mauritius to

All affected

States

Dec 2014 State should be

ready with the

BOBASIO/4

03/10/2014 P a g e | 62


Kolkata, India, 22nd –24th September 2014 collaborate for ATM

Contingency Plan.

Maldives to establish POC

for other affected FIR

Maldives

agreements before

the next RACP

TF/4 (Jan 26-30

2015)

4/7 BOBASIO States in APAC

Region to share required

data with BOBASMA

All concerned

States

Comply with

the Periodical

reporting

4/8 AAI to assess the

requirement of ATS/DS

between Mumbai and

Somalia

India and

Somalia

Dec, 2014 Assessment Study

to be submitted to

BOBASIO

secretary

4/9 Sensitization of controllers

at Mumbai, Maldives,

Seychelles and Mogadishu

on human factors with

respect to coordination

with adjacent FIR/ATC

Centres

India,

Maldives.

Seychelles

and

Somalia

Oct, 2014

4/10 Mumbai shall sensitize

controllers to adopt call

back procedure in case

controllers are not able to

immediately accept the call

due to existing traffic on

hand.

GM (ATM)

Mumbai

Oct, 2014

4/11 Seychelles and Mumbai to

investigate the instances

of violation of coordination

procedures and address

them on priority.

India and

Seychelles

As and when

required

4/12 Controller exchange

programme between

Seychelles and Mumbai for

understanding the other’s

India and

Seychelles

Sep, 2015

BOBASIO/4

03/10/2014 P a g e | 63


Kolkata, India, 22nd –24th September 2014 working environment

which will help in resolving

the human factors issues

4/13 The introduction of an

International Route

connectivity between

Guwahati and Bangkok,

via GGT VOR- B593 –

CML (COMILLA) VOR –

ONEKA – G463 – CTG

(CHITTAGONG) VOR –

G463-BGO

VOR(YANGON)-Bangkok

India

Bangladesh

July 2015

4/14 Exchange of ATS messages

via AFTN between Kolkata

and Myanmar to be done

on trial basis during lean

period with prior

coordination.

India and

Myanmar

Commence of

trial by 31st Oct,

2014.

4/15 Data sharing with respect

to surveillance and VHF

link as well as ADS-B with

Myanmar.

India and

Myanmar

Nov 2014 Both the States

are expected to

sign the MOU in

upcoming ADS-B

meeting Nov, 2014

4/16 India to send proposal to

Bangladesh for

unidirectional route

between CEA and AAT

and Bangladesh to

respond on proposal

India

Bangladesh

Dec, 2014

4/17 India and Male to explore

the VHF extended range to

cater aircraft operating on

R329 through sharing of

VHF communication data.

Maldives and

India

Dec, 2014

4/18 Chennai and Jakarta

agreed to coordinate for

conducting ADS/CPDLC

India

Indonesia

Dec, 2014

BOBASIO/4

03/10/2014 P a g e | 64


Kolkata, India, 22nd –24th September 2014 bench test in coordination

with the CRA Boeing to

test various

interoperability issues

related to auto handoff of

FANS 1A aircraft between

the two ACCs.

4/19 Jakarta and Chennai to

review the no pre-

coordinated for westbound

traffic on N563

Indonesia

and India

During

proposed

bilateral

meeting