local single sky implementation lssip 2017 - azerbaijan€¦ · document title lssip year 2017 for...

Level 1 - Implementation Overview

Local Single Sky ImPlementation LSSIP 2017 - AZERBAIJAN

EUROCONTROL

LSSIP Year 2017 Azerbaijan Released Issue

Document Title LSSIP Year 2017 for Azerbaijan

Infocentre Reference 18/02/26/07

Date of Edition 05/09/18

LSSIP Focal Point Agabek Balabekov – [email protected]

LSSIP Contact Person Predrag Vranjkovic ‐ [email protected]

Status Released Issue

Intended for Agency Stakeholders

Available in http://www.eurocontrol.int/articles/lssip

Reference Documents

LSSIP Documents http://www.eurocontrol.int/articles/lssip

LSSIP Guidance Material http://www.eurocontrol.int/articles/lssip

Master Plan Level 3 – Plan Edition 2017

http://www.eurocontrol.int/articles/european‐atm‐master‐plan‐level‐3‐implementation‐plan

Master Plan Level 3 – Report Year 2016

http://www.eurocontrol.int/articles/european‐atm‐master‐plan‐level‐3‐implementation‐report

European ATM Portal https://www.eatmportal.eu and http://www.atmmasterplan.eu/

STATFOR Forecasts http://www.eurocontrol.int/statfor

Acronyms and abbreviations http://www.eurocontrol.int/articles/glossaries


APPROVAL SHEET

The following authorities have approved all parts of the LSSIP Year 2017 document and their signature confirms the correctness of the reported information and reflects their commitment to implement the actions laid down in the European ATM Master Plan Level 3 Implementation Plan – Edition 2017 (also known as the ESSIP Plan).


CONTENTS

1. National ATM Environment ............................................................. 6 Geographical Scope .............................................................................................6 1.1. National Stakeholders .........................................................................................8 1.2.

2. Traffic and Capacity ....................................................................... 17 Evolution of traffic in Azerbaijan ...................................................................... 17 2.1. ACC BAKU ......................................................................................................... 18 2.2.

3. Master Plan Level 3 Implementation Report conclusions ............. 20

4. Implementation Projects ............................................................... 21 National projects .............................................................................................. 21 4.1. Regional projects .............................................................................................. 23 4.2.

5. Cooperation activities .................................................................... 24 FAB Co‐ordination ............................................................................................ 24 5.1. Regional cooperation ....................................................................................... 24 5.2.

6. Implementation Objectives Progress ............................................. 25 State View......................................................................................................... 25 6.1. Detailed Objectives Implementation progress ................................................ 30 6.2.

Annexes

LSSIP Year 2017 Azerbaijan 1 Released Issue

Executive Summary

National ATM Context

Azerbaijan is the farthest ECAC Member State to the east of Europe bordering with Kazakhstan, Turkmenistan and Russia to the North and East, Islamic Republic of Iran to the South and Georgia, Armenia and Turkey to the West.

Azerbaijan is among the former USSR countries with the highest economic development characteristics in the area. Azerbaijan’s economy is dynamically evolving and supporting a liberalised political, economic and social system. Oil and gas production, the chemical industry, agriculture and tourism have become the backbone for this swift advance.

Since November 17, 2011, all countries of the former USSR bordering Azerbaijan have switched to a reduced minimum of vertical separation (RVSM), which has significantly increased the capacity of the air routes through the region and reduced the risks of errors. The transition has eliminated the need for switching between feet system of separation to metric system and back. The airways over the Azerbaijan allowed significantly reduced the way from Europe to the countries of South – East Asia, as well as from the Middle East to Europe and the USA.

In August 2017, within the State Civil Aviation Administration, was created a State Inspection for the Safety all of the aviation activities in Azerbaijan. The main function of State Safety Inspection is the put into practice of safety oversight.

The following legislation documents were developed and implemented by SCAA in 2017 “AAR – ATC PEL’ and will be implemented in 2018 “AAR – aeronautical charts”; “AAR – AIS”.

Azerbaijan is playing a proactive role in the regional and international co‐operation in ATM. In addition to ICAO and ECAC membership, Azerbaijan has joined CANSO.

Traffic and Capacity

Traffic in Azerbaijan increased by 4.6% during Summer 2017 (May to October), when compared to the same period during 2016.


8; 29%

7; 25%5; 18%

4; 14%

4; 14%

Completed

Ongoing

Planned

Late

No Plan

Not Applicable

Missing Data

Undefined

Implementation Objectives Overview

The figure on the left shows the progress made so far in the implementation of the pre‐SESAR and PCP elements. The percentage is calculated as an average of the relevant objectives as shown in Chapter 6.1.2 ‐ PCP objectives are marked as such, the rest except AOP14, ATC02.9, ATC18 and NAV12 are considered pre‐SESAR. The four aforementioned objectives are neither pre‐SESAR nor PCP and will be part of an overall future indicator covering the SESAR 1 phase.

Note that two objectives – AOM19.1 and FCM05 – are considered as both part of the pre‐SESAR and PCP so their progress contributes to the percentage of both phases.

The objectives declared ‘Achieved’ in previous editions (up to, and including, ESSIP Edition 2011‐2015) are also taken into account for as long as they were linked to the Level 2 of the ATM Master Plan and implemented by the State.

Progress distribution for applicable Implementation Objectives

The overall progress of implementation in Azerbaijan is very good. Only 4 implementation objectives are currently delayed in implementation. The rest are progressing on time towards the planned deadlines.

Progress per SESAR Phase

The figure below shows the progress made so far in the implementation of the pre‐SESAR and PCP elements. The percentage is calculated as an average of the relevant objectives as shown in Chapter 6.1.2 ‐ PCP objectives are marked as such, the rest except AOP14, ATC02.9, ATC18 and NAV12 are considered pre‐SESAR. The four aforementioned objectives are neither pre‐SESAR nor PCP and will be part of an overall future indicator covering the SESAR 1 phase.

Note that two objectives – AOM19.1 and FCM05 – are considered as both part of the pre‐SESAR and PCP so their progress contributes to the percentage of both phases.

The objectives declared ‘Achieved’ in previous editions (up to, and including, ESSIP Edition 2011‐2015) are also taken into account for as long as they were linked to the Level 2 of the ATM Master Plan and implemented by the State.

Pre‐SESAR Implementation

2010 2019

70%

PCP Implementation

2015 2023

11%


Progress per SESAR Key Feature and Phase

The figure below shows the progress made so far, per SESAR Key Feature, in the implementation of the pre‐SESAR and the PCP elements. The percentages are calculated as an average, per Key Feature, of the same objectives as in the previous paragraph.

ICAO ASBUs Progress Implementation

The figure below shows the progress made so far in the implementation of the ICAO ASBUs both for Block 0 and Block 1. The percentage is calculated as an average of the relevant Objectives contributing to each of the relevant ASBUs; this is explained in Chapter 6.1.3.

Block 0 2010 2018

67%

Block 1 2015 2022

13%

n/a 5% 30% 1%

Pre‐SESAR

75%

100%

90%

19%

Pre‐SESAR

Pre‐SESAR

Pre‐SESAR

PCP

PCP

PCP

PCP

Optimised ATM Network Services

Advanced Air Traffic Services High Performing

Airport Operations

Enabling Aviation Infrastructure


ATM Deployment Outlook

● State objec ves

Deployed in 2016‐2017: ‐ MTCD & CORA [ATC12.1] 100% progress ‐ Collaborative Flight Planning [FCM03] 100% progress

‐ Coordination and transfer [ATC17] 92% progress ‐ RNAV 1 for TMA Operations [NAV03.1] 88% progress ‐ Voice over IP [COM11] 75% progress ‐ Ground‐Based Safety Nets [ATC02.8] 75% progress ‐ APV Procedures [NAV10] 72% progress ‐ eTOD [INF07] 48% progress ‐ OAT and GAT handling [AOM13.1] 43% progress ‐ Direct Routing [AOM21.1] 10% progress ‐ Interactive Rolling NOP [FCM05] 5% progress ‐ ASM Tools [AOM19.1] 0% progress ‐ ETFMS [FCM01] 0% progress ‐ Low‐Level IFR Routes for Rotorcraft [NAV12] % progress

‐ Enhanced STCA for TMAs [ATC02.9] 0% progress

‐ Extended Flight Plan [FCM08] 0% progress

● Airport objec ves ‐ UBBB ‐ Baku ‐ Heydar Aliyev International Airport

Deployed in 2016‐2017:

‐ CCOs [ENV03] 50% progress ‐ Remote Tower [AOP14] 0% progress

By 12/2018 By 12/2019 By 12/2020 2021+

By 12/2018 By 12/2019 By 12/2020 2021+


Introduction

The Local Single Sky ImPlementation (LSSIP) documents, as an integral part of the Master Plan (MP) Level 3 (L3) / LSSIP mechanism, constitute a short/medium term implementation plan containing ECAC States’ actions to achieve the Implementation Objectives as set out by the MP Level 3 and to improve the performance of their national ATM System. This LSSIP document describes the situation in the State at the end of December 2017, together with plans for the next years.

Chapter 1 provides an overview of the ATM institutional arrangements within the State, the membership of the State in various international organisations, the organisational structure of the main ATM players ‐ civil and military ‐ and their responsibilities under the national legislation. In addition, an overview of the Airspace Organisation and Classification, the ATC Units, the ATM systems operated by the main ANSP are also provided;

Chapter 2 provides a comprehensive picture of the situation of Air Traffic, Capacity and ATFM Delay per each ACC in the State. It shows the evolution of Air Traffic and Delay in the last five years and the forecast for the next five years. It gives also the achieved performance in terms of delay during the summer season period and the planned projects assumed to offer the required capacity which will match the foreseen traffic increase and keep the delay at the agreed performance level;

Chapter 3 provides a set of conclusions extracted from the MP L3 Implementation Report 2016 which are relevant to the State/stakeholders concerned. The State reports how they have handled those conclusions and the actions taken during the year to address the concerns expressed by those conclusions;

Chapter 4 provides the main Implementation Projects (at national, FAB and regional level) which contribute directly to the implementation of the MP Operational Improvements and/or Enablers and Implementation Objectives. Level 1 document covers high level list of the projects showing the applicable links. All other details like description, timescale, progress made and expected contribution to the ATM Key Performance Areas provided by the State per each project are available in Level 2 document;

Chapter 5 deals with other cooperation activities beyond Implementation Projects. It provides an overview of the FAB cooperation and also all other regional initiatives which are out of the FAB scope. The content of this chapter generally is developed and agreed in close cooperation between the States concerned;

Chapter 6 contains aggregated information at State level covering the overall level of implementation, implementation per SESAR Key Feature and implementation of ICAO ASBUs. In addition the high‐level information on progress and plans of each Implementation Objective is presented. The information for each Implementation Objective is presented in boxes giving a summary of the progress and plans of implementation for each Stakeholder. The conventions used are presented at the beginning of the section.

Level 1 document is completed with a separate document called LSSIP Level 2. This document consists of a set of tables organised in line with the list of Implementation Objectives. Each table contains all the actions planned by the four national stakeholders to achieve their respective Stakeholder Lines of Action (SLoAs) as established in the European ATM Master Plan L3 Implementation Plan Edition 2016.In addition it covers detailed description of the Implementation Projects for the State as extracted from the LSSIP Data Base.

The information contained in Chapter 6 is deemed sufficient to satisfy State reporting requirements towards ICAO in relation to ASBU (Aviation System Block Upgrades) monitoring.


1. National ATM Environment

Geographical Scope 1.1.

International Membership

Azerbaijan is a Member of the following international organisations in the field of ATM:

Organisation Since

ECAC 2002

EUROCONTROL -

European Union ‐

EASA ‐

ICAO 1992

NATO ATM/CNS Committee

ITU 1992

JAA

Geographical description of the FIR(s)

The geographical scope of this document addresses the single Baku FIR. The FIR boundaries approximate the

state border of Azerbaijan Republic. The region is strategically located at the conjunction of Europe, Central

Asia, and the Middle East. This area has served as a crossroads for centuries, a critical junction in the Silk Road

connecting Europe and Asia.

The following map shows the geographical location of Azerbaijan Republic (indicating the location of main

Airports):


Baku FIR borders the following FIRs/UIRs:

ECAC/EUROCONTROL States:

‐ West: Yerevan FIR/UIR (Armenia).

‐ North‐West: Tbilisi FIR/UIR (Georgia).

Non‐ECAC States:

‐ North: Rostov FIR/UIR (Russia);

‐ North‐East: Aktau FIR/UIR (Kazakhstan);

‐ East: Turkmenbashi FIR/UIR (Turkmenistan);

‐ South: Tehran FIR/UIR (Iran).


Airspace Classification and Organisation

All airspace is divided into Upper Airspace and Lower Airspace. The boundary between them is FL285. The graphical presentation is below.

The re‐organisation of the Baku FIR airspace to ensure a uniform and simplified application of ICAO Air Traffic Service classes Flight Level 285 and below within ECAC airspace has been achieved.

National Stakeholders 1.2.

The main National Stakeholders involved in ATM in Azerbaijan are the following:

‐ Government (Cabinet of the Ministry);

‐ State Civil Aviation Administration (SCAA);

‐ “Azerbaijan Hava Yollari” Closed Joint Stock Company;

‐ AZANS – Azerbaijan Air Navigation Services.

Their activities are detailed in the following subchapters and their relationships are shown in the diagram below. Also there is a figure of preliminary structure State Safety Inspection (source CAA,2017)


GovernmentThe cabinet

CAA Ministry of Defense

“Azerbaijan Hava Yollari”CJSC

Commander of Air ForceAnd Air Defense

Air DefenseAir Force

Aviation SafetyInspection and

Certification Office

Air NavigationServices

Airports National Airlines

Civil Aviation Authority is the responsible body for all civil aviation regulatory matters and reports directly to the government. State inspectorate for civil aviation flight safety is be responsible for oversights (all functions and accountabilities finally are not defined yet).

Issues related to military aviation matters are dealt with through the Ministry of Defence.

Azerbaijan became a member of the International Civil Aviation Organisation (ICAO), the Interstate Aviation Committee (IAC) in 1992 and a member of ECAC since 2002. All Azerbaijan Airlines flights are in compliance with international laws and regulations.

The CAA is directed in its operation by Air Codex, by decrees and orders of the President of Azerbaijan, by decrees and orders of the Government of Azerbaijan, by the SARPs adopted by ICAO, and by other legislative acts. The authority and responsibilities of the CAA are assigned in its Order, affirmed by the Government of Azerbaijan. Acting within its authority, the CAA produces legal documents and oversees other ministries, departments, enterprises, organisations and personnel which regulate the operation of civil aviation in Azerbaijan. The Director of the CAA and his deputies are assigned by decree of the President of Azerbaijan.

Air navigation services, airports authorities, aviation security and national airline are managed by “Azerbaijan Hava Yollari” which is a Closed Joint Stock Company.

Contained within “Azerbaijan Hava Yollari” is “Azeraeronavigation” (AZANS) which is responsible for the provision of air traffic services. AZANS is also responsible for provision of the meteorological and Aeronautical Information Service.

Civil Regulator(s)

General Information

Civil Aviation in Azerbaijan is the responsibility of the Civil Aviation Authority. The different national entities having regulatory responsibilities in ATM are summarised in the table below.


Activity in ATM: Organisation responsible Legal Basis

Rule‐making CAA / AHY CJSC Aviation Law

Safety Oversight CAA State Safety Programme

Enforcement actions in case of non‐compliance with safety regulatory requirements

Formal procedures for enforcement have yet to be established

Will be established in new edition of State Safety Programme

Airspace CAA Aviation Law

Economic Azerbaijan Hava Yollari CJSC

Aviation Law

Environment CAA Aviation Law

Security CAA/ Azerbaijan Hava Yollari CJSC

Aviation Law

Accident investigation CAA Aviation Law

The creation of a National Supervisory Authority as per the SES Service Provision Regulation has not been implemented in Azerbaijan. The CAA fulfils the role of the NSA.

CAA

The Civil Aviation Authority is responsible for:

‐ Supervision of utilisation of the airspace of Azerbaijan Republic;

‐ Certification of airports, aircraft and equipment;

‐ Supervision of the aviation safety;

‐ Licensing;

‐ Investigation of incidents.

The organisational chart of the CAA is shown in the Annex B of this document.

Annual Report published: N CAA is not yet producing the Annual Report.

Web: www.caa.gov.az


AZANS (Azerbaijan Air Navigation Services)

Azeraeronavigation (AZANS) is the only ANS provider within Azerbaijan Republic.

AZANS has one FIR for the whole upper airspace of Azerbaijan Republic, six TMA’s at Baku, Ganja, Nakhchivan, Lankaran, Zagatala, Gabala , Yevlakh aerodromes and a CTR at Zabrat heliport. There are also other aerodromes which are not permanently manned by AZANS staff due to lack of traffic.

AZANS is responsible for:

‐ provision of air traffic services;

‐ development of air traffic management system;

‐ maintenance of ATC technical facilities;

‐ modernisation of ATC technical facilities;

‐ provision of aeronautical information service;

‐ provision of meteorological service.

Service provided

Governance: Subdivision of CJSC Ownership: CJSC “Azerbaijan Hava Yollari”

Services provided Y/N Comment

ATC en‐route Y Baku ACC (East and West) Nakhichevan ACC (South)

ATC approach Y Baku APP, Nakhichevan APP/TWR, Ganja APP/TWR, Lankaran APP/TWR , Gabala APP/TWR , Yevlakh APP/TWR

ATC Aerodrome(s) Y Baku TWR , Nakhichevan APP/TWR, Ganja APP/TWR, Lankaran APP/TWR, Zabrat TWR, Zagatala TWR, Gabala TWR, Yevlakh APP/TWR

AIS Y AIP, NOTAMs, AIC, PIB

CNS Y All type of services for all International airports in Azerbaijan

MET Y All type of services for all International airports in Azerbaijan

ATCO training Y National Aviation Academy/AZANS/Outsourcing

Others

Additional information:

Provision of services in other State(s):

N

Annual Report published: N AZANS is still not yet producing Annual Report.

Remark: APP/TWR means combined unit.

Number of air traffic controllers 171

Supervisors 25

ACC 38

APP 32

TWR 95 (including 29 ATCO of heliport)

The organisational chart of AZANS is shown in the Annex B of this document.


ATC systems in use

Main ANSP part of any technology alliance1 No

FDPS

Specify the manufacturer of the ATC system currently in use: Air Traffic Automation Control System: Indra AIRCON 2100

Upgrade of the ATC system is performed or planned? 2014

Replacement of the ATC system by the new one is planned? No plans yet

ATC Unit Baku ACC, Baku APP

Specify the manufacturer of the ATC system currently in use: THALES Eurocat C

Upgrade2 of the ATC system is performed or planned? 2016


ATC Unit Nakhichevan ACC, Nakhichevan APP

SDPS

Specify the manufacturer of the ATC system currently in use: Air Traffic Automation Control System : Indra AIRCON 2100




Specify the manufacturer of the ATC system currently in use: Thales MSSR/PSR and SMR




1Technology alliance is an alliance with another service provider for joint procurement of technology from a particular supplier (e.g. COOPANS alliance) 2 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))


ATC Units

The ATC units in the Azerbaijan’s airspace, which are of concern to this LSSIP are the following:

ATC Unit Number of sectors Associated FIR(s) Remarks

En‐route TMA

Baku 2 1 Azerbaijan ACC Baku (West, East)

Ganja 1 Azerbaijan

Nakhichevan 1 1 Azerbaijan ACC Nakhichevan (South)

Zagatala 1 Azerbaijan

Lenkoran 1 Azerbaijan

Gabala 1 Azerbaijan

Yevlakh 1 Azerbaijan

Buffer zones with Russia, Kazakhstan and Turkmenistan were eliminated due to RVSM transition in these

countries.

Airports

General information

Azerbaijan Hava Yollari” CJSC regulates operation of: Heydar Aliyev (Baku), Ganja, Nakhchivan, Zagatala, Naftalan, Gabala, Lankaran, Yevlakh, Sheki airports and Zabrat heliport. This is shown in the picture below. Naftalan, Sheki are not operational due to lack of traffic. Heydar Aliyev (Baku), Ganja, Nakhchivan, Lenkaran, Gabala and Zagatala airports are International.


Airport(s) covered by the LSSIP

Referring to the List of Airports in the European ATM Master Plan Level 3 Implementation Plan Edition 2017 – Annex 2, it is up to the individual State to decide which additional airports will be reported through LSSIP for those Objectives.

This edition of the LSSIP contains information regarding the main national airport, Baku Heydar Aliyev. The EUROCONTROL Public Airport Corner also provides information for the following airport(s): https://ext.eurocontrol.int/airport_corner_public/UBBB

Military Authorities

The Military Authorities in Azerbaijan are comprised of:

‐ Ministry of Defence;

‐ Commander of Air Forces and Air Defence;

They report to the Cabinet.

The Commander of Air Forces and Air Defence is the responsible body for military aviation matters in the Azerbaijan Republic. Military authorities provide air traffic services at military aerodromes and designated zones for military training flights and exercises.

There is a military co‐ordination unit established in OPS room of Baku ACC responsible for operational co‐ordination. Although Flexible Use of Airspace (FUA) is not formally defined most of the principles of FUA are in place and the co‐ordination procedures are at very good level.

Regulatory role

Regulatory framework and rule‐making

OAT GAT

OAT and provision of service for OAT governed by national legal provisions?

Y Provision of service for GAT by the Military governed by national legal provisions?

N

Level of such legal provision: Ministry of Defence – Air Law for Air Defence

Level of such legal provision: ‐

Authority signing such legal provision: Minister of Defence

Authority signing such legal provision:

Cabinet of the Ministry

These provisions cover: These provisions cover:

Rules of the Air for OAT Y


Oversight

Service Provision role

Military ANSP providing GAT services SES certified?

N If YES, since: Duration of the Certificate:

Certificate issued by: N If NO, is this fact reported to the EC in accordance with SES regulations?

Organisation of military ATS for OAT Y Organisation of military ATS for GAT N

OAT/GAT Co‐ordination Y OAT/GAT Co‐ordination Y

ATCO Training N ATCO Training N

ATCO Licensing N ATCO Licensing N

ANSP Certification N ANSP Certification N

ANSP Supervision N ANSP Supervision N

Aircrew Training N ESARR applicability N

Aircrew Licensing N

Additional Information: Additional Information:

Means used to inform airspace users (other than military) about these provisions:

Means used to inform airspace users (other than military) about these provisions:

National AIP N National AIP Y

National Military AIP N National Military AIP N

EUROCONTROL eAIP N EUROCONTROL eAIP N

Other: National VFR Manual ‐ Other: National Regulatory Documents Y

OAT GAT

National oversight body for OAT: Ministry of Defence

No military oversight role

Additional information:

OAT GAT

Services Provided: MIL Services Provided: None

En‐Route N En‐Route N

Approach/TMA N Approach/TMA N

Airfield/TWR/GND Y Airfield/TWR/GND Y

AIS N AIS N

MET N MET N

SAR N SAR N

TSA/TRA monitoring N FIS N

Other: Other:

Additional Information: Additional Information:


User role

Flexible Use of Airspace (FUA)

IFR inside controlled airspace, Military aircraft can fly?

OAT only GAT only X Both OAT and GAT

If Military fly OAT‐IFR inside controlled airspace, specify the available options:

Free Routing Y Within specific corridors only X

Within the regular (GAT) national route network Y Under radar control Y

Within a special OAT route system Y Under radar advisory service N

If Military fly GAT‐IFR inside controlled airspace, specify existing special arrangements:

No special arrangements N Exemption from Route Charges X

Exemption from flow and capacity (ATFCM) measures N Provision of ATC in UHF N

CNS exemptions: RVSM N 8.33 N Mode S N ACAS N

Others: * If there is request from the military, and radar control is not possible, ATC close the route until the military aircraft has passed through it.

Military in AZ applies FUA requirements as specified in the Regulation No 2150/2005: N

FUA Level 1 implemented: : N

FUA Level 2 implemented: N

FUA Level 3 implemented: N


2. Traffic and Capacity

Evolution of traffic in Azerbaijan 2.1.

2017 Traffic in Azerbaijan increased by 4.6% during Summer 2017 (May to October), when compared to the same period during 2016.

2018‐2022

The EUROCONTROL Seven‐Year forecast predicts an average annual traffic growth between 2.8% and 6.4%, with an average baseline growth of 4.5% throughout the planning cycle.

0

50,000

100,000

150,000

200,000

250,000

2013 A 2014 A 2015 A 2016 A 2017 F 2018 F 2019 F 2020 F 2021 F 2022 F 2023 F

IFR

flig

hts

Azerbaijan - Annual IFR Movements

IFR movements - Actuals

IFR movements - Baseline forecast

IFR movements - High forecast

IFR movements - Low forecast A = ActualF = Forecast

2014 A 2015 A 2016 A 2017 F 2018 F 2019 F 2020 F 2021 F 2022 F 2023 F

H 5.5% 8.3% 6.0% 6.4% 5.5% 5.8% 5.7%

B -1.2% 1.4% 5.1% 4.9% 6.5% 4.0% 4.2% 3.8% 4.0% 4.1%

L 4.4% 4.7% 2.0% 2.8% 2.2% 2.5% 2.5%

ECAC B 1.7% 1.6% 2.8% 4.5% 2.8% 2.1% 1.9% 1.5% 1.7% 1.7%

EUROCONTROL Seven-Year Forecast (September 2017)IFR flights yearly growth

Azerbaijan


ACC BAKU 2.2.

Summer 2017 performance

Traffic Evolution 2017 Capacity Baseline En-route Delay (min/flight) - Summer Capacity

gap Ref value Actual

+4.6% 65 (0%) 0.01 0.0 No

The average en-route delay per flight remained at zero in Summer 2017.

Capacity Plan: Sufficient Capacity to meet demand Achieved Comments

ATS route network optimisation - an on-going process in co-operation with neighboring States

Yes

Maximum configuration: 5 + 3APP Yes

Summer 2017 performance assessment

The ACC capacity baseline was estimated at 65. During the measured period, the average peak 1 hour demand was 33 and the average peak 3 hour demand was 24.

Planning Period 2017‐2021 ‐ Summer

The planning focuses on the Summer season to reflect the most demanding period of the year from a capacity perspective. This approach ensures consistency with the previous planning cycles.

Summer Capacity Plan

2017 2018 2019 2020 2021

Free Route Airspace

Airspace Management Advanced FUA

Airport & TMA Network Integration

Cooperative Traffic Management

Airspace ATS route network optimisation - an on-going process in co-operation with neighboring States Procedures

Staffing

Technical

Capacity

Significant Events

Max sectors 5 + 3APP 5 + 3APP 5 + 3APP 5 + 3APP 5 + 3APP

Planned Annual Capacity Increase Sufficient capacity to meet expected demand

Reference profile Annual % Increase 0% 0% 0% N/A N/A

Difference Capacity Plan v. Reference Profile

Sufficient capacity to meet expected demand

Annual Reference Value (min) 0.01 0.01 0.01 N/A N/A

Summer reference value (min) 0.01 0.01 0.01 N/A N/A

Additional information

H 65 0% 65 0% 65 0%

Ref. 65 0% 65 0% 65 0%

L 65 0% 65 0% 65 0%

Open 65 0% 65 0% 65 0%

C/R 65 0% 65 0% 65 0%

2018 2019

UBBA 65

ACC2016

baseline 2017

Capacity ProfilesProfiles (hourly movements and % increase over previous year)


Up to 5 ACC and 3 APP sectors could be open. However, with the current levels of traffic, 3 ACC + 3 APP are sufficient.

0

1

2

3

4

5

6

7

8

00:00

02:00

04:00

06:00

08:00

10:00

12:00

14:00

16:00

18:00

20:00

22:00

Sectors available ‐ Summer 2018 ‐WD

0

1

2

3

4

5

6

7

8

00:00

02:00

04:00

06:00

08:00

10:00

12:00

14:00

16:00

18:00

20:00

22:00

Sectors available ‐ Summer 2018 ‐WE

2015 2016 2017 2018 2019 2020 2021

2017‐2019 Reference Capacity Profile 65 65 65

Capacity Profile ‐ Shortest Routes (Open) 65 65 65

Capacity Profile ‐ Current Routes 65 65 65

Capacity Profile ‐ High 65 65 65

Capacity Profile ‐ Low 65 65 65

Capacity Baseline 65 65

2017 ‐ 2021 Plan 65 65 65 65 65

0

10

20

30

40

50

60

70

Cap

acity profile (movements per hour)

UBBACTA - Reference capacity profile and alternative scenarios

2018‐2022 Planning Period Outlook

No problems are foreseen for Azerbaijan during the current planning cycle.


3. Master Plan Level 3 Implementation Report conclusions

Conclusions issued from the European ATM Master Plan Level 3 Implementation Report 2016 applicable to Azerbaijan for all items that require corrective actions and improvements.

Conclusion Applicable to VERY GOOD PROGRESS IN IMPLEMENTATION OF BOTH FREE ROUTE AND DIRECT

ROUTING.

THIS MOMENTUM SHOULD BE KEPT AND SUPPORTED BY ALL INVOLVED STAKEHOLDERS.

(page 14 of the Report)

All State that are

implementing

AOM21.1 and

AOM21.2 State’s action planned for this conclusion: YES

Description of the planned action: Azerbaijan is implementing direct routing on its territory. Implementation

of the FRA concept is not being implemented at this stage due to complexity of the airspace and issue of

restricted flight zone at its territory.

Conclusion Applicable to ADQ IMPLEMENTATION ISSUES HAVE TO BE ADDRESSED AS SOON AS POSSIBLE AS THEY

CAN IMPACT ON SWIM IMPLEMENTATION. (page 25 of the Report) All States + EC

State’s action planned for this conclusion: YES

Description of the planned action: ADQ regulation is not applicable in AZ. However, AZ is following all trends in this area and much functionality related to ADQ is already available. Moreover, roadmap in AIM area is

established to implement these functionalities.


4. Implementation Projects

National projects 4.1.

Name of project: Organisation(s): Schedule: Status: ATM MP Links:

Implement full back‐up ATC system at Baku ACC (BCUP‐ACC)

AZANS (AZ) 2018 Ongoing ‐

Implementation of Airspace Efficiency, Strategy and Development Center (ASEC) (FLOW)

AZANS (AZ) 2018 Ongoing L3: FCM05, FCM06, FCM08

Implementation of VSAT Communication System (VSAT)

AZANS (AZ) 2018 Ongoing L2: CNS‐0001‐A

Implementation of complete AIS to AIM system (AIS‐AIM)

AZANS (AZ) 2018 Ongoing L3: INF07, ITY‐ADQ

Implementation of the Virtual Tower with remote control on Chilov Island (RTWR_Chilov)

AZANS (AZ) February 2018 ‐ December 2018

Planned L3: AOP14

Installation of METEO radars (METEO AZ)

AZANS (AZ), Ganja Airport (AZ), Nakhchivan Airport (AZ)

2018 Ongoing L3: ITY‐ADQ

Installlation of new satelite connection system with adjecent ATS centres (SAT_AZ)


MSSR Radar instalation at Yevlakh Airport (MSSR‐UBEE)

Yevlakh Airport (AZ) 2018 Ongoing L3: ITY‐ACID, ITY‐SPI

Modernisation of ILS at Baku Airport (ILS‐Baku)

AZANS (AZ), BAKU ‐ Heydar Aliyev International Airport (AZ)

2019 Planned L2: CNS‐0001‐A


Name of project: Organisation(s): Schedule: Status: ATM MP Links:

Runway extension and ATC system renewal at Zaqatala International Airport (RWY‐UBBY)


The second phase of installation of ADS‐B and WAM system (Phase II ADS‐B)

AZANS (AZ) 2018 Ongoing L3: ITY‐ACID, ITY‐SPI

Upgrade of the Nakhchivan Airport runway and navigation AIDS (ATM‐UBBN)

Nakhchivan Airport (AZ)

2018 Ongoing ‐

Implementation of the ATC Contingency System in Baku ASEC building

AZANS (AZ) 2018 Ongoing

Implementation of MoC AZANS‐IATA

AZANS (AZ) 2018 Ongoing


Regional projects 4.2.

OLDI system implementation. (OLDI)

Organisation(s): AZANS (AZ) Type of project: Regional

Schedule: 2018

Status: Ongoing

Description: Implementation of OLDI system at Baku ACC center.

Link and references

ATM MP links: L3: ATC17

Other links: ‐

Project included in RP2 Performance Plan:

‐ Name/Code in RP2 Performance Plan:

‐

Project included in DP2016:

‐ Name/Code in DP2016: ‐

Performance contribution

Safety: +++ Enhancing safety of operations through more efficient COMs.

Environment: ‐

Capacity: +++ Creating new capacity in Baku ACC.

Cost‐efficiency: ‐

Operational efficiency: +++ Better operational efficiency through more efficient transfer of

responsibility.

Cooperation Activities: Testing activities with Rostov ongoing. Tbilisi is scheduled after.


5. Cooperation activities

FAB Co‐ordination 5.1.

Not applicable.

Regional cooperation 5.2.

Regional cooperation initiatives

There are no Regional Cooperation Initiatives to which Azerbaijan has joined.


6. Implementation Objectives Progress

State View 6.1.

Objective Progress per SESAR Key Feature

Note: The detailed table of links between Implementation Objectives and SESAR Key Features is available in Annex C.

Legend:

## % = Expected completion / % Progress = Implementation Objective timeline (different colour per KF)

100% = Objective completed = Completion beyond Implementation Objective timeline


<15 15 16 17 18 19 20 21 22 23 24 ≥25

AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling

43%

AOM19.1 (PCP) ASM Support Tools to Support AFUA 0%

AOM19.2 (PCP) ASM Management of Real‐Time Airspace Data 0%

‐

AOM19.3 (PCP) Full rolling ASM/ATFCM Process and ASM Information Sharing

0%

‐

FCM01 Enhanced Tactical Flow Management Services 0%

FCM03 Collaborative Flight Planning 100%

FCM04.1 STAM Phase 1

n/a

FCM04.2 (PCP) STAM Phase 2

n/a

FCM05 (PCP) Interactive Rolling NOP 5%

FCM06 (PCP) Traffic Complexity Assessment 0%


Advanced Air Traffic Services

<15 15 16 17 18 19 20 21 22 23 24 ≥25

AOM21.1 (PCP) Direct Routing 10%

AOM21.2 (PCP) Free Route Airspace

n/a

AOP14 Remote Tower Services Local objective

UBBB ‐ Baku ‐ Heydar Aliyev International Airport 0%

ATC02.2 STCA En‐Route 100%

ATC02.8 Ground‐Based Safety Nets 75%

ATC02.9 Enhanced STCA for TMAs 0%

ATC07.1 AMAN Tools and Procedures

UBBB ‐ Baku ‐ Heydar Aliyev International Airport (Outside Applicability Area)

n/a

ATC12.1 Automated Support for Conflict Detection, Resolution Support Information and Conformance Monitoring

100%

ATC15.1 Information Exchange with En‐route in Support of AMAN

n/a

ATC15.2 (PCP) Arrival Management Extended to En‐route Airspace

n/a

ATC16 ACAS II Compliant with TCAS II Change 7.1 100%

ATC17 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer

92%

ATC18 Multi Sector Planning En‐route ‐ 1P2T Local objective 0%

‐

ENV01 Continuous Descent Operations


100%

ENV03 Continuous Climb Operations Local objective

UBBB ‐ Baku ‐ Heydar Aliyev International Airport 50%

ITY‐COTR Ground‐Ground Automated Co‐ordination Processes

68%

NAV03.1 RNAV 1 in TMA Operations 88%

NAV03.2 (PCP) RNP 1 in TMA Operations 0%

‐

NAV10 APV procedures 72%

NAV12 Optimised Low‐Level IFR Routes in TMA for Rotorcraft

Local objective 0%


High Performing Airport Operations

<15 15 16 17 18 19 20 21 22 23 24 ≥25

AOP04.1 A‐SMGCS Level 1


100%

AOP04.2 A‐SMGCS Level 2


100%

AOP05 Airport CDM


n/a

AOP10 (PCP) Time‐Based Separation


n/a

AOP11 (PCP) Initial Airport Operations Plan


n/a

AOP12 (PCP) Improve Runway and Airfield Safety with ATC Clearances Monitoring


n/a

AOP13 (PCP) Automated Assistance to Controller for Surface Movement Planning and Routing


n/a

ENV02 Collaborative Environmental Management


n/a

SAF11 Improve Runway Safety by Preventing Runway Excursions

100%



<15 15 16 17 18 19 20 21 22 23 24 ≥25

COM10 Migrate from AFTN to AMHS 100%

COM11 Voice over Internet Protocol (VoIP) 75%

COM12 (PCP) NewPENS

n/a

FCM08 (PCP) Extended Flight Plan 0%

INF04 Integrated Briefing 100%

INF07 Electronic Terrain and Obstacle Data (eTOD) 48%

ITY‐ACID Aircraft Identification 100%

ITY‐ADQ Ensure Quality of Aeronautical Data and Aeronautical Information

83%

ITY‐AGDL Initial ATC Air‐Ground Data Link Services 10%

ITY‐AGVCS2 8,33 kHz Air‐Ground Voice Channel Spacing below FL195

n/a

ITY‐FMTP Common Flight Message Transfer Protocol 100%

ITY‐SPI Surveillance Performance and Interoperability 100%


ICAO ASBU Implementation

The following table shows, for each of the ASBU Block 0 modules, the overall status, the final date foreseen for completion and the percentage of progress achieved in the current cycle.

These results were determined using the LSSIP Year 2017 declared statuses and progress of the relevant Implementation objectives in accordance with the mapping approved by ICAO EUR EANPG/59 (European Air Navigation Planning Group).

Legend:

= Completed (during 2017 or before)

= Missing planning date

= Progress achieved in 2017 = Not applicable

<16 16 17 18 19 20 21 22 23 24 ≥25

B0‐APTA Optimization of Approach Procedures including vertical guidance

100%

80%

B0‐SURF Safety and Efficiency of Surface Operations (A‐SMGCS Level 1‐2)

100%

B0‐FICE Increased Interoperability, Efficiency and Capacity through Ground‐Ground Integration

100%

87%

B0‐DATM Service Improvement through Digital Aeronautical Information Management

100%

92%

B0‐ACAS ACAS Improvements 100%

B0‐SNET Increased Effectiveness of Ground‐Based Safety Nets

100%

38%

B0‐ACDM Improved Airport Operations through

B0‐RSEQ Improved Traffic flow through Runway sequencing (AMAN/DMAN)

B0‐FRTO Improved Operations through Enhanced En‐Route Trajectories

100%

37%

B0‐NOPS Improved Flow Performance through Planning based on a Network‐Wide view

100%

50%

B0‐ASUR Initial capability for ground surveillance 100%

B0‐CDO Improved Flexibility and Efficiency in Descent Profiles (CDO)

100%

B0‐TBO Improved Safety and Efficiency through the initial application of Data Link En‐Route

100%

10%


Detailed Objectives Implementation progress 6.2.

Note: The detailed table of applicability area for the Implementation Objectives is available in Annex C.

Objective/Stakeholder Progress Code:

Completed No Plan

Ongoing Not Applicable

Planned Missing Data

Late

Main Objectives

AOM13.1

Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) Handling Timescales: Initial operational capability: 01/01/2012 Full operational capability: 31/12/2018

43% Ongoing

‐

New Air Rule on use of the airspace has been modified and approved by Cabinet of Ministry. Rules were developed in accordance with ICAO and EUROCONTROL requirements. New plans are being considered for further cooperation between CIV and MIL.

31/12/2018

REG (By:12/2018)

State Civil Aviation Administration

New Air Rule on use of the airspace has been modified and approved by Cabinet of Ministry. Rules developed in accordance with ICAO and EUROCONTROL requirements.New plans are being considered for further cooperation between CIV and MIL.

‐ 40%

Ongoing

31/12/2018

ASP (By:12/2018)

AZANS

New Air Rule on use of the airspace has been modified and approved by Cabinet of Ministry. Rules developed in accordance with ICAO and EUROCONTROL requirements. New plans are being considered for further cooperation between CIV and MIL.

‐ 63%

Ongoing

31/12/2018

MIL (By:12/2018)

Mil. Authority

New Air Rule on use of the airspace has been modified and approved by Cabinet of Ministry. Rules developed in accordance with ICAO and EUROCONTROL requirements. New plans are being considered for further cooperation between CIV and MIL.

‐ 32%

Ongoing

31/12/2018

AOM19.1

ASM Support Tools to Support Advanced FUA (AFUA) Timescales: Initial operational capability: 01/01/2011 Full operational capability: 31/12/2018

0% Planned

‐

Azerbaijan is currently building a new center that will include these functions. 01/07/2018

ASP (By:12/2018)

AZANS Azerbaijan is currently building a new center that will include these functions.

‐ 0% Planned

01/07/2018


AOM19.2

ASM Management of Real‐Time Airspace Data Timescales: Initial operational capability: 01/01/2017 Full operational capability: 31/12/2021

0% No Plan

‐

Azerbaijan is currently not in a position to establish ASM management of real‐time airspace data at the European Network level. The objective will be reviewed in the future when circumstances change.

‐

ASP (By:12/2021)

AZANS

Azerbaijan is currently not in a position to establish ASM management of real‐time airspace data at the European Network level. The objective will be reviewed in the future when circumstances change.

‐ 0%

No Plan

‐

AOM19.3

Full Rolling ASM/ATFCM Process and ASM Information Sharing Timescales: Initial operational capability: 01/01/2014 Full operational capability: 31/12/2021

0% No Plan

‐

Azerbaijan is currently not in a position to establish rolling ASM/ATFCM process at the European Network level. The objective will be reviewed in the future when circumstances change.

‐

ASP (By:12/2021)

AZANS

Azerbaijan is currently not in a position to establish rolling ASM/ATFCM process at the European Network level. The objective will be reviewed in the future when circumstances change.

‐ 0%

No Plan

‐

AOM21.1

Direct Routing Timescales: Initial Operational Capability: 01/01/2015 Full Operational Capability: 31/12/2017

10% Late

‐

Azerbaijan is in the process of implementation of this objective. One direct route is already defined for testing. This is not reflected in ERNIP, it is AZANS project solely. In future, AZANS is looking for more cooperation with EUROCONTROL in this area. New Center of Airspace Efficiency, Strategy and Development should help in the promotion in this area.

31/12/2018

ASP (By:12/2017)

AZANS Azerbaijan is in the process of implementation of this objective. One direct route is already defined for testing.

‐ 10% Late

31/12/2018


AOM21.2

Free Route Airspace (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

At this stage, Azerbaijan is unable to implement this objective due to complexity of the airspace and issue of restricted flight zone at its territory.

‐

ASP (By:12/2021)

AZANS At this stage, Azerbaijan is unable to implement this objective due to complexity of the airspace and issue of restricted flight zone at its territory.

‐ % Not Applicable

‐

AOP04.1

Advanced Surface Movement Guidance and Control System A‐SMGCS Surveillance (former Level 1) Timescales: ‐ not applicable ‐

100% Completed


Azerbaijan has completed the implementation of this objective and A‐SMGCS Level 1 is operational at Baku Airport.

31/12/2014

REG (By:12/2010)



‐ 100%

Completed

31/12/2014

ASP (By:12/2011)

AZANS Azerbaijan has completed the implementation of this objective and A‐SMGCS Level 1 is operational at Baku Airport.

‐ 100% Completed

31/12/2014

APO (By:12/2010)

BAKU ‐ Heydar Aliyev International Airport


A‐SMGCS Level I and II

100%

Completed

31/12/2014

AOP04.2

Advanced Surface Movement Guidance and Control System (A‐SMGCS) Runway Monitoring and Conflict Alerting (RMCA) (former Level 2) Timescales: ‐ not applicable ‐

100% Completed


A‐SMGCS Level 2 is implemented and operational at Baku Airport. Control function equipment installed. HITT system used.

31/12/2015

ASP (By:12/2017)

AZANS Azerbaijan has completed the implementation of this objective.

‐ 100% Completed

31/12/2015

APO (By:12/2017)


Azerbaijan has completed the implementation of this objective.

A‐SMGCS Level I and II

100%

Completed

31/12/2015


AOP05 Airport Collaborative Decision Making (A‐CDM) Timescales: ‐ not applicable ‐

% Not

Applicable


Azerbaijan is not within the area of applicability of this airport related objective. ‐

ASP (By:12/2016)

AZANS Azerbaijan is not within the area of applicability of this multi‐national objective.


‐

APO (By:12/2016)


Azerbaijan is not within the area of applicability of this multi‐national objective.

‐ %

Not Applicable

‐

AOP10 Time‐Based Separation Timescales: ‐ not applicable ‐

% Not

Applicable


Azerbaijan is not within the area of applicability of this objective. ‐

REG (By:12/2023)

AZANS ‐ ‐ % Not Applicable

‐

ASP (By:12/2023)


‐

AOP11 Initial Airport Operations Plan Timescales: ‐ not applicable ‐

% Not

Applicable


Azerbaijan is not in the applicability area of the PCP regulation. ‐

ASP (By:12/2021)

AZANS Azerbaijan is not in the applicability area of the PCP regulation.


‐

APO (By:12/2021)


Azerbaijan is not in the applicability area of the PCP regulation.

‐ %

Not Applicable

‐


AOP12

Improve Runway and Airfield Safety with Conflicting ATC Clearances (CATC) Detection and Conformance Monitoring Alerts for Controllers (CMAC) Timescales: ‐ not applicable ‐

% Not

Applicable


Azerbaijan is not in the applicability area of the PCP regulation. ‐

ASP (By:12/2020)


‐

APO (By:12/2020)


‐ ‐ %

Not Applicable

‐

AOP13

Automated Assistance to Controller for Surface Movement Planning and Routing Timescales: ‐ not applicable ‐

% Not

Applicable


Baku Airport is not in applicability area of this objective. ‐

REG (By:12/2023)


‐ ‐ %

Not Applicable

‐

ASP (By:12/2023)


‐

ATC02.8

Ground‐Based Safety Nets Timescales: Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016

75% Late

‐

MSAW and APW functions are fully implemented in AZANS. APM implementation is currently ongoing.

31/12/2018

ASP (By:12/2016)

AZANS MSAW and APW functions are fully implemented in AZANS. APM implementation is currently ongoing.

‐ 75% Late

31/12/2018


ATC02.9

Enhanced Short Term Conflict Alert (STCA) for TMAs Timescales: Initial operational capability: 01/01/2018 Full operational capability: 31/12/2020

0% Planned

‐

‐ 31/12/2020

ASP (By:12/2020)

AZANS ‐ ‐ 0% Planned

31/12/2020

ATC07.1 AMAN Tools and Procedures Timescales: ‐ not applicable ‐

% Not

Applicable


Azerbaijan is not within the area of applicability of this multi‐national objective. Moreover, there is no OPS need. However implementation of AMAN system is discussed in the frame of existing modernization programme.

‐

ASP (By:12/2019)

AZANS No OPS needs, the investment can not be justified Installation of new ATC system

% Not Applicable

‐

ATC12.1

Automated Support for Conflict Detection, Resolution Support Information and Conformance Monitoring Timescales: Initial operational capability: 01/01/2015 Full operational capability: 31/12/2021

100% Completed

‐

MTCD support function exists in the system. CORA function implemented. Procedures are defined. Functionality is operational.

31/12/2017

ASP (By:12/2021)

AZANS MTCD support function exists in the system. Procedures are defined. Functionality is operational.

‐ 100% Completed

31/12/2017

ATC15.1

Information Exchange with En‐route in Support of AMAN (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

There is no operational need for this tool in Azerbaijan. ‐

ASP (By:12/2017)


‐


ATC15.2

Arrival Management Extended to En‐route Airspace (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Not applicable for AZ. ‐

ASP (By:12/2023)


‐

ATC17

Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer Timescales: Initial operational capability: 01/01/2013 Full operational capability: 31/12/2018

92% Ongoing

‐

New ATM system is capable to exchange some OLDI messages. AZANS is in negotiations with adjacent countries. Testing is ongoing with Rostov FIR.

31/12/2018

ASP (By:12/2018)

AZANS New ATM system is capable to exchange basic OLDI messages. AZANS is in negotiations with adjacent countries. Testing is ongoing with Rostov FIR.

OLDI system implementati

on.

92% Ongoing

31/12/2018

COM10

Migrate from AFTN to AMHS Timescales: Initial operational capability: 01/12/2011 Full operational capability: 31/12/2018

100% Completed

‐

Azerbaijan completed the transition to AMHS. System capabilities implemented into the new ACC. However, due to inability of adjacent Rostov FIR system is still working as AFTN.

31/12/2014

ASP (By:12/2018)

AZANS

Azerbaijan completed the transition to AMHS. System capabilities implemented into the new ACC. However, due to inability of adjacent Rostov FIR system is still working as AFTN.

Installation of new ATC system

100%

Completed

31/12/2014

COM11

Voice over Internet Protocol (VoIP) Timescales: Initial operational capability: 01/01/2013 Full operational capability: 31/12/2020

75% Ongoing

‐

AZANS has partly implemented this objective. In some areas the concept is already operational. 31/12/2018

ASP (By:12/2020)

AZANS AZANS has partly implemented this objective. In some areas the concept is already operational.

Installation of new ATC system

75% Ongoing

31/12/2018


COM12

New Pan‐European Network Service (NewPENS) (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

‐ ‐

ASP (By:12/2024)


‐

APO (By:12/2024)

ENV01 Continuous Descent Operations (CDO) Timescales: ‐ not applicable ‐

100% Completed


Procedures developed to decrease C02 emissions at Baku Airport and published. Objective is completed.

31/03/2015

ASP (By:12/2013)

AZANS Procedures developed to decrease C02 emissions at Baku Airport and published. Objective is completed.

‐ 100% Completed

31/03/2015

APO (By:12/2013)


Procedures developed to decrease C02 emissions at Baku Airport and published. Objective is completed.

‐ 100%

Completed

31/03/2015

ENV02 Airport Collaborative Environmental Management Timescales: ‐ not applicable ‐

% Not

Applicable


Azerbaijan is not within the area of applicability of this airport related objective. ‐

ASP (By:12/2016)

AZANS Azerbaijan is not within the area of applicability of this multi‐national objective.


‐

APO (By:12/2016)


Azerbaijan is not within the area of applicability of this multi‐national objective.

‐ %

Not Applicable

‐


FCM03

Collaborative Flight Planning Timescales: Initial operational capability: 01/01/2000 Full operational capability: 31/12/2017

100% Completed

‐

Since early January 2016, associations with IFPS is completed and operational. AIC distributed . All messages exchanged through the system to the extent necessary for AZ being a non EUROCONTROL State.

31/12/2017

ASP (By:12/2017)

AZANS Since early January 2016, associations with IFPS is completed and operational. AIC distributed . All messages exchanged through the system.

Implementation of IFPLS

100% Completed

31/12/2017

FCM04.1

Short Term ATFCM Measures (STAM) ‐ Phase 1 (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Azerbaijan is not in the applicability area of this objective. ‐

ASP (By:10/2017)

AZANS Azerbaijan is not in the applicability area of this objective. ‐ % Not Applicable

‐

FCM04.2

Short Term ATFCM Measures (STAM) ‐ Phase 2 (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Not applicable for AZ. Not in the applicability area. ‐

ASP (By:12/2021)


‐


FCM05

Interactive Rolling NOP Timescales: Initial operational capability: 01/09/2013 Full operational capability: 31/12/2021

5% Ongoing

‐

Objective is planned to be implemented in future with new ATFCM center in Baku. Activity is started already with provision of airport slot info to DDR.

31/12/2018

ASP (By:12/2021)

AZANS Objective is planned to be implemented in future with new ATFCM center in Baku.

Implementation of

Airspace Efficiency, Strategy and Development Center (ASEC)

0%

Planned

31/12/2018

APO (By:12/2021)


Objective implementation started. To be implemented in relations to new ATFCM center in Baku.

‐ 10%

Ongoing

31/12/2018

FCM06

Traffic Complexity Assessment (Outside Applicability Area) Timescales: ‐ not applicable ‐

0% Planned

‐

The objective is being considered for implementation in new flow and capacity management center in Baku.

31/12/2021

ASP (By:12/2021)

AZANS The objective is being considered for implementation in new flow and capacity management center in Baku.

Implementation of


0%

Planned

31/12/2021

FCM08

Extended Flight Plan Timescales: Initial operational capability: 01/01/2016 Full operational capability: 31/12/2021

0% Planned

‐

The objective will be implemented in new flow and capacity management center in Baku. 31/12/2021

ASP (By:12/2021)

AZANS The objective will be implemented in new flow and capacity management center in Baku.

Implementation of


0%

Planned

31/12/2021


INF07

Electronic Terrain and Obstacle Data (eTOD) Timescales: Initial operational capability: 01/11/2014 Full operational capability: 31/05/2018

48% Late

‐

Implementation of e‐TOD was approved by State Civil Aviation Administration. Implementation is considered as part of implementation of ADQ requirements.

31/12/2018

REG (By:05/2018)



‐ 55%

Late

31/12/2018

ASP (By:05/2018)

AZANS Implementation of e‐TOD was approved by State Civil Aviation Administration. Implementation is considered as part of implementation of ADQ requirements.

Implementation of

complete AIS to AIM system

40%

Late

31/12/2018

APO (By:05/2018)



‐ 40%

Late

31/12/2018

ITY‐ACID

Aircraft Identification (Outside Applicability Area) Timescales: ‐ not applicable ‐

100% Completed

‐

Azerbaijan ATM system support this functionality. Mode S is implemented, it functions. No declaration of Mode S is provided to NM, as AZ is not EUROCONTROL State.

31/12/2014

ASP (By:01/2020)

AZANS Azerbaijan ATM system support this functionality.

Mode S implementati

on / The second phase of installation of ADS‐B and WAM system

100%

Completed

31/12/2014


ITY‐ADQ

Ensure Quality of Aeronautical Data and Aeronautical Information (Outside Applicability Area) Timescales: ‐ not applicable ‐

83% Ongoing

‐

Although not applicable to AZ, there are plans and activities towards the implementation of ADQ in AZ. AZANS AIS is ISO 9001/2008 Certified by DQS. Gap analyses for ITY‐ADQ requirements implementation is done. Roadmap for implementation is established.

31/12/2018

REG (By:06/2017)


AZANS AIS is ISO 9001/2008 Certified by DQS. Gap analyses for ITY‐ADQ requirements implementation is done.

‐ 100%

Completed

31/12/2015

ASP (By:06/2017)

AZANS

Although not applicable to AZ, there are plans and activities towards the implementation of ADQ in AZ. AZANS AIS is ISO 9001/2008 Certified by DQS. Gap analyses for ITY‐ADQ requirements implementation is done. Roadmap for implementation is established.

Implementation of

complete AIS to AIM system /

Installation of METEO radars

75%

Ongoing

31/12/2018

APO (By:06/2017)


Airport AIS handled by AZANS. ‐ %

Not Applicable

‐

ITY‐AGDL

Initial ATC Air‐Ground Data Link Services (Outside Applicability Area) Timescales: ‐ not applicable ‐

10% Ongoing

‐

Azerbaijan is not within the area of applicability of this EU+ objective. New ATC Centre includes CPDLC functionality. Connection to SITA to be performed in the future.

31/12/2018

REG (By:02/2018)



‐ 0%

Planned

01/02/2018

ASP (By:02/2018)

AZANS


‐ 13%

Ongoing

31/12/2018

MIL (By:01/2019)

Mil. Authority ‐ ‐ % Not Applicable

‐


ITY‐AGVCS2

8,33 kHz Air‐Ground Voice Channel Spacing below FL195 (Outside Applicability Area) Timescales: ‐ not applicable ‐

% Not

Applicable

‐

Azerbaijan is not in the applicability area of this objective. ‐

REG (By:12/2018)


‐ ‐ %

Not Applicable

‐

ASP (By:12/2018)


‐

MIL (By:12/2020)


‐

APO (By:12/2018)


‐ ‐ %

Not Applicable

‐

ITY‐FMTP

Common Flight Message Transfer Protocol (FMTP) Timescales: Entry into force of regulation: 28/06/2007 All EATMN systems put into service after 01/01/09: 01/01/2009 All EATMN systems in operation by 20/04/11: 20/04/2011 Transitional arrangements: 31/12/2012 Transitional arrangements when bilaterally agreed between ANSPs: 31/12/2014

100% Completed

‐

Functionality completed. FMTP is based on the TCP/IP protocol, IPv4. 31/12/2015

ASP (By:12/2014)

AZANS Functionality completed. FMTP is based on the TCP/IP protocol, IPv4.

‐ 100% Completed

31/12/2015

MIL (By:12/2014)

Mil. Authority Mil systems are not interconnected with Civil ATC. One position of Baku ATC system is dedicated for Mil sector at Baku ACC.


‐


ITY‐SPI

Surveillance Performance and Interoperability (Outside Applicability Area) Timescales: ‐ not applicable ‐

100% Completed

‐

ATC systems is procured from EUROPEAN famous suppliers and correspond to EUROCAE requirements. Airborn equipment or modification is subject to EASA certification. Surveillance data exchanged in ASTERIX format. All actions completed. AZ is not in the applicability area ‐ voluntary implementation.

31/12/2015

REG (By:02/2015)


ATC systems is procured from EUROPEAN famous suppliers and correspond to EUROCAE. Airborn equipment or modification is subject to EASA certification. REG action completed.

‐ 100%

Completed

31/12/2015

ASP (By:02/2015)

AZANS

ATC systems is procured from EUROPEAN famous suppliers and correspond to EUROCAE. All data processing is in ICAO standarts. UTC time coordination is obtained by GPS time systems. ASTERIX formats used (ASTERIX 62, 19, 20, etc.)

MSSR Radar installation at

Yevlakh Airport / Mode S

implementation / The

second phase of installation of ADS‐B and WAM system

100%

Completed

31/12/2015

MIL (By:06/2020)


‐

NAV03.1

RNAV 1 in TMA Operations Timescales: Initial operational capability: 01/01/2001 Full operational capability: 31/12/2023

88% Ongoing

‐

RNAV procedures were approved by SCAA. RNAV arrival and departure procedures are used only in Baku for RNAV approved aircraft. RNAV procedures for other international airports in AZ are ongoing to develop.

31/12/2018

ASP (By:12/2023)

AZANS The P‐RNAV procedures were tested in a Baku terminal area. New P‐RNAV procedures now are used for arrival and departure for all RWY.

‐ 88% Ongoing

31/12/2018


NAV03.2

RNP 1 in TMA Operations Timescales: Initial operational capability: 01/01/2018 Full operational capability: 31/12/2023

0% No Plan

‐

‐ ‐

ASP (By:12/2023)

AZANS ‐ ‐ 0% No Plan

‐

NAV10

APV Procedures Timescales: Initial operational capability: 01/06/2011 Full operational capability: 31/12/2016

72% Late

‐

RNP BARO procedure implemented for one runway end at Baku Airport. It is planned to develop procedures for all runway ends by the end of the year.

31/12/2018

REG (By:04/2016)


AZ is out of EASA remit. However, many standards have been applied.

‐ %

Not Applicable

‐

ASP (By:12/2016)

AZANS RNP BARO procedure implemented for one runway end at Baku Airport. It is planned to develop procedures for all runway ends by the end of 2017.

‐ 72% Late

31/12/2018


SAF11

Improve Runway Safety by Preventing Runway Excursions Timescales: Initial operational capability: 01/09/2013 Full operational capability: 31/01/2018

100% Completed

‐

Azerbaijan has implemented technical measures to prevent runway excursions. The aerodrome service unit is responsible for runway safety issues. The activities of this unit are closely coordinated with other services. A Special team is organised for runway incursion and all objectives have been met.

31/12/2015

REG (By:01/2018)



‐ 100%

Completed

31/12/2015

ASP (By:12/2014)

AZANS


‐ 100%

Completed

31/12/2015

APO (By:12/2014)



‐ 100%

Completed

31/12/2015


Additional Objectives for ICAO ASBU Monitoring

ATC02.2

Implement ground based safety nets ‐ Short Term Conflict Alert (STCA) ‐ level 2 for en‐route operations Timescales: Initial operational capability: 01/01/2008 Full operational capability: 31/01/2013

100% Completed

‐

STCA functions exist and are optimised to the local environment. Existing system has STCA functions. Review of new EUROCONTROL specifications was done during 2010. NEW ATC Centre and ATC Tower has been built and new Modern ATC equipment were installed. Specification has done according to the later EUROCONTROL Requirements. Nowadays New system is working. ATS personnel use new SIDs and STARs.

30/11/2014

ASP (By:01/2013)

AZANS

STCA functions exist and are optimised to the local environment. Existing system has STCA functions. Review of new EUROCONTROL specifications was done during 2010. NEW ATC Centre and ATC Tower has been built and new Modern ATC equipment were installed. Specification has done according to the later EUROCONTROL Requirements. Nowadays New system is working. ATS personnel use new SIDs and STARs

‐ 100%

Completed

30/11/2014

ATC16

Implement ACAS II compliant with TCAS II change 7.1 Timescales: Initial operational capability: 01/03/2012 Full operational capability: 31/12/2015

100% Completed

‐

All aircraft, in accordance with the plan were equipped with TCAS Version 7.1. AZANS system is capable of ACAS II performance monitoring.

31/12/2015

REG (By:12/2015)


All aircraft, in accordance with the plan were equipped with TCAS Version 7.1

‐ 100%

Completed

31/12/2015

ASP (By:03/2012)

AZANS

AZANS systen is capable to perform ACAS II performance monitoring. Acquisition information about TCAS II version 7.1and develop training plan to train ATCO in ACAS II (TCAS II version 7.1) has been completed.

‐ 100%

Completed

31/12/2015

MIL (By:12/2015)

Mil. Authority

MIL has no ATS role. ‐ % Not

Applicable

‐


FCM01

Implement enhanced tactical flow management services Timescales: Initial operational capability: 01/08/2001 Full operational capability: 31/12/2006

0% Planned

‐

Azerbaijan is planning to build new airspace flow efficiency center which will implement tools to enhance tactical flow management. Bilateral agreement with EUROCONTROL addressing ATFCM issues signed in 2015. Status is planned (not LATE) as Azerbaijan was unable to implement this objective earlier as there was no basis to be in the scope of CFMU.

31/12/2018

ASP (By:07/2014)

AZANS

Azerbaijan has built new airspace flow efficiency center which will implement tools to enhance tactical flow management. Bilateral agreement with EUROCONTROL addressing ATFCM issues signed in 2015. Status is planned as Azerbaijan was unable to implement this objective earlier as there was no basis to be in the scope of CFMU.

‐ 0%

Planned

31/12/2018

INF04

Implement integrated briefing Timescales: Initial operational capability: 01/07/2002 Full operational capability: 31/12/2012

100% Completed

‐

Integrated briefing is implemented and operational at Baku Heydar Aliyev Airport. AZANS currently implementing self briefing automated system at Baku Heydar Aliyev Airport.

31/01/2012

ASP (By:12/2012)

AZANS

Integrated briefing is implemented and operational at Baku Heydar Aliyev airport. AZANS currently implementing self briefing automated system at Baku Heydar Aliyev airport.

‐ 100%

Completed

31/01/2012

ITY‐COTR

Implementation of ground‐ground automated co‐ordination processes (Outside Applicability Area) Timescales: ‐ not applicable ‐

68% Ongoing

‐

OLDI is installed in AIRCON system. The Installation of OLDI system continue in the adjacent Centers. Communication through the OLDI system between Baku and Rostov is in test mode.

31/12/2018

ASP (By:12/2012)

AZANS

OLDI is installed in AIRCON system. The Installation of OLDI system continue in the adjacent Centers. Communication through the OLDI system between Baku and Rostov is in test mode.

‐ 68%

Ongoing

31/12/2018

MIL (By:12/2012)

Mil. Authority

Azerbaijan is outside of the applicability of this objective.

‐ % Not

Applicable

‐


Local Objectives

AOP14 Remote Tower Services Applicability and timescale: Local

0% Planned

UBBB ‐ Baku ‐ Heydar Aliyev International Airport

It is planned to create a virtual tower on the island of Chilov in the Caspian Sea for helicopter operations. Note that this Objective refers to Chilov heliport and not Baku airport, which was selected because Chilov was not in our database.

31/12/2018

ATC18 Multi‐Sector Planning En‐route ‐ 1P2T Applicability and timescale: Local

% No Plan

‐

‐ ‐

ENV03 Continuous Climb Operations (CCO) Applicability and timescale: Local

50% Ongoing

UBBB ‐ Baku ‐ Heydar Aliyev International Airport

SIDs PBN has been developed and implemented in the practical at the airport Heydar Aliyev. RNAV arrival and departure procedures are used for P‐RNAV approved aircraft and for all RWY. Training programs are being developed and will be implemented after approved by SCAA.

31/12/2018

NAV12 Optimised Low‐Level IFR Routes in TMA for Rotorcraft Applicability and timescale: Local

% Ongoing

‐

Low‐Level IFR Routes in TMA are developed and will be published in the local AIP 31/12/2018


ANNEXES

ANNEX A ‐ Specialists involved in the LSSIP Process

LSSIP Co‐ordination

LSSIP Focal Points Organisation Name

LSSIP Focal Point for Azerbaijan AZANS Alexander TELEGIN

LSSIP Focal Point for ANSP AZANS Agabek BALABEKOV

EUROCONTROL LSSIP Support

Function Directorate Name

LSSIP Contact Person for Azerbaijan DECMA/PRM Predrag VRANJKOVIC


Implementation Objectives

Implementation Objective

EUROCONTROL PEPR Objective Coordinator

EUROCONTROL Objective Owners

National Stakeholder Specialist

AOM13.1 A. DYBOWSKA O. MROWICKI/ C. LUCCIOLI Vahid GADIROV

AOM19.1 O. ALFARO G. ACAMPORA /

O. MROWICKI


O. MROWICKI


O. MROWICKI

AOM21.1 A. DYBOWSKA C. BRAIN Vahid GADIROV

AOM21.2 A. DYBOWSKA C. BRAIN Vahid GADIROV

AOP04.1 P. VRANJKOVIC R. GRAHAM Safa MAMMADOV

AOP04.2 P. VRANJKOVIC R. GRAHAM Safa MAMMADOV

AOP05 F. ROOSELEER M. BIRENHEIDE

AOP10 F. ROOSELEER R. GRAHAM

AOP11 F. ROOSELEER M. BIRENHEIDE

AOP12 P. VRANJKOVIC R. GRAHAM

AOP13 P. VRANJKOVIC R. GRAHAM

AOP14 A. DYBOWSKA R. GRAHAM / G. ASSIRE

ATC02.8 F. ROOSELEER S. DROZDOWSKI

ATC02.9 F. ROOSELEER S. DROZDOWSKI

ATC07.1 L. DELL’ORTO pending



ATC15.2 L. DELL’ORTO P. HOP

ATC17 L. DELL’ORTO S. MORTON

ATC18 L. DELL’ORTO I. PENDACHANSKI

COM10 J. PINTO Y. EYUBOGLU Safa MAMMADOV

COM11 J. PINTO L. POPESCU Safa MAMMADOV

COM12 J. PINTO W. JANSSENS

ENV01 B. HILL D. BRAIN Aleksandr ESTROV

ENV02 B. HILL S. MAHONY

ENV03 A‐P. FRANGOLHO D. BRAIN

FCM03 O. CIOARA C. BOUMAN/I. PENDACHANSKI

Farhan GULIYEV

FCM04.1 I. MARCETIC P. HOP/I. PENDACHANSKI

FCM04.2 I. MARCETIC P. HOP/I. PENDACHANSKI

FCM05 O. CIOARA I. MENDES VIDEIRA/I. PENDACHANSKI

Farhan GULIYEV

FCM06 F. ROOSELEER P. HOP/I. PENDACHANSKI Farhan GULIYEV

FCM08 O. CIOARA K. BREIVIK/I. PENDACHANSKI Farhan GULIYEV


INF07 A‐P. FRANGOLHO A. PETROVSKY Aleksandr ESTROV

ITY‐ACID O. CIOARA pending Safa MAMMADOV

ITY‐ADQ A‐P. FRANGOLHO M. UNTERREINER Julia DRONOVA

ITY‐AGDL B. HILL D. ISAAC Safa MAMMADOV

ATY‐AGVCS2 B. HILL J. POUZET Safa MAMMADOV

ITY‐FMTP O. ALFARO L. POPESCU Safa MAMMADOV

ITY‐SPI O. CIOARA M. BORELY Safa MAMMADOV

NAV03.1 I. MARCETIC F. PAVLICEVIC

NAV03.2 I. MARCETIC F. PAVLICEVIC

NAV10 I. MARCETIC R. FARNWORTH Aleksandr ESTROV

NAV12 I. MARCETIC B. RABILLER / F. RIQUET

SAF11 F. ROOSELEER pending Alexander TELEGIN


ANNEX B ‐ National Stakeholders Organisation charts


AZANS Organisation Chart


Azerbaijan state inspectorate on Civil Aviation Flight Safety


ANNEX C – Implementation Objectives’ Applicability

Objective SESAR

Key Feature

ICAO ASBU

B0 European ATM Masterplan Level 3 Applicability area

AOM13.1

‐ All ECAC States except Albania, Latvia, Luxembourg, Maastricht UAC and

Moldova.

AOM19.1

B0‐FRTO All ECAC States except Armenia, FYROM, Malta, Luxembourg, and

Moldova

AOM19.2

‐ All ECAC States except Armenia, Luxembourg and Moldova

AOM19.3

‐ All ECAC States except Armenia, Luxembourg and Moldova

AOM21.1

B0‐FRTO 25 ECAC States

AOM21.2

‐ All ECAC States except Azerbaijan, Belgium, Luxembourg and the

Netherlands

AOP04.1

B0‐SURF 25 PCP airports, 22 non‐PCP airports

AOP04.2

B0‐SURF 25 PCP airports, 22 non‐PCP airports

AOP05

B0‐ACDM 25 PCP airports, 21 non‐PCP airports

AOP10

‐ 16 PCP Airports

AOP11

‐ 24 PCP airports, 15 non‐PCP airports

AOP12

‐ 25 PCP airports

AOP13

‐ 25 PCP airports

AOP14

‐ Local: Low to medium complexity aerodromes, subject to local needs

ATC02.2 B0‐SNET Additional for ICAO ASBU monitoring: applicable all ECAC States that did

not yet implement it

ATC02.8

B0‐SNET All ECAC States except the Netherlands

ATC02.9

B0‐SNET TMAs, according to local business needs

ATC07.1

B0‐RSEQ 23 PCP Airports, 8 non‐PCP airports

ATC12.1

‐ All ECAC States except Luxembourg

ATC15.1

B0‐RSEQ

EU States except Cyprus, Greece, Lithuania, Luxembourg, Malta, Slovak

Republic, Slovenia. Plus: Bosnia and Herzegovina, Maastricht UAC,

Norway, Switzerland, Turkey

ATC15.2

‐ ACCs within the extended AMAN horizon, including those adjacent to

TMAs serving/associated to PCP airports

ATC16 B0‐ACAS Additional for ICAO ASBU monitoring: applicable to all ECAC States that

did not yet implement it

ATC17

B0‐FICE All ECAC States except Ireland, Slovak Republic and Ukraine

ATC18

‐ Local: Subject to local needs and complexity

COM10

‐ All ECAC States

COM11

‐ All ECAC States


COM12

‐

‐ Area 1 (ANSPs signatories of the NewPENS Common Procurement

Agreement): 33 ANSPs

‐ Area 2 (Other stakeholders): Stakeholders from all ECAC States not part

of Area 1

ENV01

B0‐CDO 59 Airports

ENV02

‐ 47 Airports

ENV03

B0‐CCO Local: Aerodromes subject to local needs and complexity

FCM01 B0‐NOPS Additional for ICAO ASBU monitoring: applicable to all ECAC States that


FCM03

B0‐NOPS All ECAC States

FCM04.1

B0‐NOPS Austria, Belgium, Croatia, Czech Republic, France, Germany, Italy, Poland,

Spain, Switzerland

FCM04.2

B0‐NOPS All EU+ States

FCM05

B0‐NOPS All ECAC States except Armenia, FYROM, Luxembourg, Maastricht UAC

and Moldova

FCM06

B0‐NOPS All EU+ States

FCM07

‐ All EU+ States

FCM08

‐ All ECAC States

FCM09

‐ All ECAC States

INF04 B0‐DATM Additional for ICAO ASBU monitoring: applicable to all ECAC States that


INF07

‐ All ECAC States except Maastricht UAC

INF08.1

‐ All EU+ States

INF08.2

‐ All EU+ States

ITY‐ACID

‐ All EU+ States

ITY‐ADQ

B0‐DATM All EU+ States except FYROM, Georgia and Maastricht UAC

ITY‐AGDL

B0‐TBO All EU+ States except Georgia, Luxembourg and Netherlands

ITY‐AGVCS2

‐ All EU+ States except Georgia and Moldova

ITY‐COTR B0‐FICE Additional for ICAO ASBU monitoring: applicable all EU+ States that did

not yet implement it

ITY‐FMTP

B0‐FICE All ECAC States

ITY‐SPI

B0‐ASUR All EU+ States

NAV03.1

B0‐CDO,

B0‐CCO All ECAC States except Luxembourg, Maastricht UAC and Slovak Republic

NAV03.2

‐ Mandatory for TMAs listed in section 1.2.1 of the Annex of the PCP

Regulation. For all other ECAC TMAs, according to local business needs

NAV10

B0‐APTA All ECAC States except Maastricht UAC

NAV12

‐ Local: TMAs subject to local needs and complexity

SAF11

‐ All ECAC States except Malta


Legend:

Objective’s link to SESAR Key Feature:


High Performing Airport Operations

Advanced Air Traffic Services



ANNEX D ‐ Glossary of Abbreviations

This Annex mostly shows only the Abbreviations that are specific to the LSSIP Azerbaijan.

Other general abbreviations are in the Acronyms and Abbreviations document in http://www.eurocontrol.int/articles/glossaries

Term Description

ACAS Airborne Collision Avoidance System

ACC Area Control Centre

AIS Aeronautical Information Services

AMC Acceptable means of Compliance

ANS Air Navigation Services

ANSP ANS Provider

AOP Airports Operations (Domain)

APV Approach with Vertical Guidance

ARN ATS Route Network

ATS Air Traffic Services

CAD Civil Aviation Department

CDM Collaborative Decision Making

CNS Communications, Navigation and Surveillance

COM Communications

CTR Control Zone

DFL Division Flight Level

EAD European AIS Database

eAIP European Aeronautical Information Publication

EATM European Air Traffic Management

ECAC European Civil Aviation Conference

ESARR EUROCONTROL Safety Regulation Requirement

ESP European Safety Programme

FDP Flight Data Processing

FIR Flight Information Region

FL Flight Level

FSQA Flight Safety and Quality Assurance

FUA Flexible Use of Airspace

GBAS Ground Based Augmentation System

GNSS Global Navigation Satellite System

HRS Human Resources

HUM Human (Domain)

IFPS Initial Flight‐plan Processing System


IFR Instrument Flight Rules

ISO International Standards Organisation

JAA Joint Aviation Authorities

kHz Kilohertz

LoA Letters of Agreement

MIL Military

NAV Navigation

NM Nautical Mile

NOTAM Notice To Airmen

OLDI On Line Data Interchange

OPS Operations

PSR Primary Surveillance Radar

QMS Quality Management System

REG Regulatory Authorities

RNP Required Navigation Performance

RVSM Reduced Vertical Separation Minimum

SAN Sakaeronavigatsia Ltd (ATM of Georgia)

SBAS Satellite‐Based augmentation systems (SBAS)

SLOA Stakeholder Line of Action

SMQS Safety Management and Quality System

SMS Safety Management System

SRC Safety Regulation Commission

SSR Secondary Surveillance Radar

STCA Short Term Conflict Alert

SUR Surveillance (Domain)

TMA Terminal Manoeuvring Area; Terminal Control Area