Local Single Sky ImPlementation (LSSIP) ARMENIA · 2019-02-18 · capabilities are not in operational use because the neighbouring centres are not ready yet. Due to this, these objectives

EUROCONTROL

Year 2015 - Level 1

Local Single Sky ImPlementation (LSSIP) ARMENIA

LSSIP Year 2015 Armenia Released Issue

DOCUMENT IDENTIFICATION SHEET

LSSIP for Armenia

Infocentre Reference: 16/01/29-54

Document Identifier Edition: Year 2015

LSSIP Year 2015 Armenia Edition Date: 17 Feb 2016

LSSIP Focal Point - Samvel Baghdasaryan E-mail: [email protected]

Head of ATM SM Service

LSSIP Contact Person - Octavian Cioara E-mail: [email protected]

Unit DPS/PEPR

Status Intended for

Working Draft General Public

Draft Agency Stakeholders

Proposed Issue Restricted Audience

Released Issue

Accessible via: Internet (www.eurocontrol.int)

Path: Y:\03 LSSIP\1. LSSIP States\Armenia (AM) - OC\Year_2015\Released\LSSIP Year 2015_Armenia_Released.docx

LINKS TO REFERENCE DOCUMENTS

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

2 ESSIP Plan Edition 2015 www.eurocontrol.int/pepr

3 European ATM Portal Working - https://www.eatmportal.eu/working

Public - https://www.atmmasterplan.eu/ 4 ESSIP Report 2014 www.eurocontrol.int/pepr

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

6 Acronyms and abbreviations

http://www.eurocontrol.int/articles/glossaries

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

9 National AIP http://armats.com/eng/aviation/aip.htm

10 National Performance Plan Request should be send to e-mail: [email protected]

11 National Business Plan (In Armenian)

Request should be send to e-mail: [email protected]


APPROVAL SHEET

The following authority(ies) have approved all parts of LSSIP Year 2015 document and their signature confirms the correctness of the reported information and reflects their commitment to implement the actions laid down in the European Single Sky ImPlementation (ESSIP) Plan – Edition 2015.


TABLE OF CONTENTS

Executive Summary ................................................................................................................................. 1

Introduction .............................................................................................................................................. 4

National ATM Environment ................................................................................................... 5 Chapter 1 -1.1 Geographical Scope ................................................................................................................. 5

1.1.1 International Membership ..................................................................................................... 5 1.1.2 Geographical description of the FIR(s) ................................................................................ 5 1.1.3 Airspace Classification and Organisation ............................................................................ 5

1.2 National Stakeholders .............................................................................................................. 6 1.2.1 Civil Regulator(s) .................................................................................................................. 7 1.2.2 ARMATS (ANSP) ................................................................................................................. 8 1.2.3 Airports ................................................................................................................................. 9 1.2.4 Military Authorities .............................................................................................................. 10

Traffic and Capacity ............................................................................................................ 12 Chapter 2 -2.1 Evolution of traffic in Armenia ................................................................................................ 12 2.2 YEREVAN ACC ..................................................................................................................... 12

2.2.1 Summer 2015 performance ............................................................................................... 12 2.2.2 Planning Period 2016-2020 ................................................................................................ 13

ESSIP Report recommendations ........................................................................................ 15 Chapter 3 -

National Projects ................................................................................................................. 16 Chapter 4 -

Regional Co-ordination ....................................................................................................... 17 Chapter 5 -5.1 Regional cooperation ............................................................................................................. 17

ESSIP Objective Implementation ........................................................................................ 18 Chapter 6 -6.1 Conventions ........................................................................................................................... 18 6.2 ESSIP Objectives Implementation progress .......................................................................... 19 6.3 Alignment of PCP with ESSIP Objectives and related progress ............................................ 32

ANNEXES

LSSIP Year 2015 Armenia 1 Released Issue

Executive Summary

National ATM Context

In 2015 the following was done:

- implementation of APM system in Yerevan “Zvartnots” airport in accordance with EUROCONTROL Specifications

- signing of the agreement and the testing for the implementation of the basic OLDI (ABI, ACT, REV, PAC, MAC, LAM) via FMTP with Tbilisi FIR (North). The final connection is expected in 2016.

- procurement and installation of the new ATIS system with D-ATIS possibility.

- expansion and upgrade of the EVN and GYU P3D WAM systems (cat19,cat20,cat21,cat34,cat48) from CT (central timing) architecture to DT (distributed timing) architecture with additional receiving stations to improve the coverage and accuracy in the Armenian airspace and beyond.

- installation of a new “Galaxy” ATC system in Gyumri TWR.

- ARMATS (ATS, CNS, AIS) QMS re-certification by insurance UK limited company BSI.

- an audit of the Republic of Armenia by ICAO with excellent results. This audit was carried out from the 15th to the 25th of June, 2015 by an ICAO audit team in accordance with the guidelines and principles set forth in the ICAO Universal Safety Oversight Audit Programme Continuous Monitoring Manual (USOAP CMA) (Doc 9735) as well as in conformity with the ISO 9001:2008 series of quality management standards. For more details see http://www.icao.int/safety/pages/usoap-results.aspx.

- Since 2010 the Republic of Armenia has begun work on the PBN concept in accordance with resolution A37-11. The PBN concept was implemented for Yerevan “Zvartnots” international aerodrome in 2012, for Gyumri “Shirak” aerodrome PBN procedures are planned to be implemented in 2016, so far the A37-11 resolution has partially been completed.

- Procurement of a new DVOR/DME and replacement of the existing VOR/DME in “Zvartnots” airport are planned in 2016-2017

- Procurement and maintenance of the aeronautical database in the AIXM 5.1 format, as well as the software updates for generating eAIP are planned in 2016.

Traffic and Capacity

Traffic in Armenia decreased by -13.9% during Summer 2015 (May to October inclusive), when compared to Summer 2014. However, on medium term, the STATFOR medium-term forecast (MTF) predicts an average annual traffic growth between 3.3% and 8.8% for the planning period (2016-2020), with an average baseline growth of 6.2%.

ESSIP Objective Implementation

In 2015 a major milestone has been reached, with the full implementation of the FCM01 objective and in particular the distribution of Correlated Position Reports to the NM. This has represented another important step toward the further integration of the Armenian ATM within the European Air Traffic Management Network. It should be also noted that for a number of objectives (COM11, ITY-COTR, ITY-FMTP, ITY-SPI) the technical capability is fully implemented in the ATM system, however these capabilities are not in operational use because the neighbouring centres are not ready yet. Due to this, these objectives appear only as “Partly Completed”. It is expected that once Basic OLDI, over FMTP, will be implemented with Tbilisi FIR and used operationally (in 2016), these objectives to be turned into “Completed”.


LSSIP 2015 - Armenia * FOC Date

█ Planned implementation date (see legend at the bottom of the table)

State-related ESSIP Objectives

<=

2009

2010

2011

2012

2013

2014

2015

2016

2017

2018

2019

2020

2021

2022

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

*

AOM19 Implement Advanced Airspace Management *

AOM21.1 Implementation of Direct Routing [PCP]

[E] *

AOM21.2 Implement Free Route Airspace [PCP]

[E] *

AOP03 Improve runway safety by preventing runway incursions *

ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2

*

ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2

*

ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2

*

ATC12.1 Implement automated support for conflict detection, resolution support information and conformance monitoring

*

ATC15 Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations

ATC16 Implement ACAS II compliant with TCAS II change 7.1 *

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

*

COM10 Migrate from AFTN to AMHS *

COM11 Implementation of Voice over Internet Protocol (VoIP) in ATM

*

FCM01 Implement enhanced tactical flow management services *

FCM03 Implement collaborative flight planning *

FCM04 Implementation of Short Term ATFCM Measures - phase 1

FCM05 Implementation of interactive rolling NOP [PCP]

[E] *

FCM06 Traffic Complexity Assessment [PCP]

[E]

INF04 Implement integrated briefing *

INF07 Electronic Terrain and Obstacle Data (TOD) *

ITY-ACID Aircraft identification

ITY-ADQ Ensure quality of aeronautical data and aeronautical information

ITY-AGDL Initial ATC air-ground data link services above FL-285

ITY-AGVCS2 Implement air-ground voice channel spacing requirements below FL195

ITY-COTR Implementation of ground-ground automated co-ordination processes

ITY-FMTP Apply a common flight message transfer protocol (FMTP) *

ITY-SPI Surveillance performance and interoperability

NAV03 Implementation of P-RNAV

NAV10 Implement APV procedures *

SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements

*

SAF11 Improve runway safety by preventing runway excursions *


Airport-related ESSIP Objectives

<=

2009

2010

2011

2012

2013

2014

2015

2016

2017

2018

2019

2020

2021

2022

UDYZ-Yerevan Airport

AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1

AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2

AOP05 Implement Airport Collaborative Decision Making (CDM)

AOP10 Time Based Separation [PCP]

[E] AOP11 Initial Airport Operations Plan

[PCP] [E] *

AOP12 Improve runway and airfield safety with ATC clearances monitoring

[PCP] [E]

ATC07.1 Implement AMAN tools and procedures

ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements

*

ENV02 Implement Collaborative Environmental Management (CEM) at Airports

Understanding the Table

Objective Completed No Plan

Objective Partly Completed Missing Data

Objective Planned Not Applicable (Armenia/Zvartnots Airport does not participate in this obj.)

Late

E= Essential – Master Plan Reference PCP = Pilot Common Project

NOTE: The year where the coloured box is placed indicates the ‘Implementation Completion Date’ as stated in the ESSIP for each objective. The colour-code indicates the Local progress with respect to this date.


Introduction

The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a short/medium term implementation plan containing ECAC States’ actions to achieve the Implementation Objectives as set out by the ESSIP and to improve the performance of their national ATM System. The LSSIP document – Year 2015 describes the situation in the State at the end of December 2015.

The LSSIP documents are structured into 6 chapters to better differentiate the Stakeholder(s) accountable for the information contained in each of them:

Chapter 1 provides an overview of the ATM institutional arrangements within the State, the membership of the State in various international organizations, the organizational structure of the main ATM players - civil and military - and their responsibilities under the national legislation. In addition, an overview of the Airspace Organization and Classification, the ATC Units, the ATM systems operated by the main ANSP are also provided in this chapter.

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 recommendations extracted from the ESSIP Report which are relevant to the state/stakeholders concerned. The state reports how they have handled those recommendations and the actions taken during the year to address the concerns expressed by those recommendations;

Chapter 4 provides a set of the main ATM national projects which contribute directly to the implementation of the ATM MP OIs and/or Enablers and ESSIP related Objectives. The description, timescale, progress made and expected contribution to the ATM Key Performance Areas are provided by the states per each project included in this chapter;

Chapter 5 deals with the ATM Regional Coordination. It provides an overview of the FAB cooperation and Projects and also all other regional initiatives and Projects 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 high-level information on progress and plans of each ESSIP Objective. The information for each ESSIP 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.

Note: Chapter 6 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 ESSIP 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 ESSIP.

Note: 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.


National ATM Environment Chapter 1 -

1.1 Geographical Scope

1.1.1 International Membership

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

Organisation Since

ECAC December 1996

EUROCONTROL 1 March 2006

European Union

EASA Working Arrangement 2009, Annex 1 ATM 2011

ICAO 18 June 1992

NATO

ITU 30 June 1992

1.1.2 Geographical description of the FIR(s)

The geographical scope of this document addresses the YEREVAN FIR in Armenia.

Adjacent FIRs:

The Yerevan FIR is bordered by the following FIRs:

ECAC FIR: Georgia: Tbilisi FIR (North), Turkey: Ankara FIR (West), and Azerbaijan: Baku FIR (East).

Non ECAC FIRs: Iran: Tehran FIR (South)

The way across North to South is ~340Km and East to West is ~200Km.

1.1.3 Airspace Classification and Organisation

Armenian airspace consists of a single FIR, which is divided into lower and upper airspace. The Division Flight Level (DFL) separating upper from lower ATS airspace is FL 195. Classification of the airspace is Class “C” between FL 195 and FL 660 according with the EUROCONTROL requirements.


1.2 National Stakeholders

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

- General Department of Civil Aviation (GDCA);

- Armenian Air Traffic Services (ARMATS);

- Armenian International Airports (AIA);

- Air Force;

- The Aviation Meteorological Centre (Ministry of Nature Protection).

Their activities (GDCA) are detailed in the following subchapters and their relationships are shown in the diagram below.


1.2.1 Civil Regulator(s)

1.2.1.1 General information

Civil aviation in Armenia is the responsibility of the GDCA (General Department of Civil Aviation at the Government of Republic of Armenia). GDCA is the State Regulatory body under the authority of the Prime Minister and the Government. The different national entities having regulatory responsibilities in ATM are summarised in the table below. The GDCA is further detailed in the following sections.

Activity in ATM: Organisation responsible

Legal Basis

Rule-making GDCA Aviation Law and Status of GDCA N202-N 13.02.2003

Safety Oversight GDCA Government Order N744-N 19.06.2008 (Establishing procedure for granting permission of ANSP), GDCA GD order 238A/06.10.2014 Safety oversight of ANSP.

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

GDCA Aviation Law, Government Order N744-N 19.06.2008 (Establishing procedure for granting permission of ANSP), GDCA GD order 238A/06.10.2014 Safety oversight of ANSP.

Airspace GDCA Aviation Law and Government Order №825N 03.07.2003 ”Airspace management regulation”

Economic GDCA / Ministry of Defence

Government of Armenia and Ministry of Finance orders.

Environment GDCA Aviation Law.

Security GDCA Order N1307-N 02.10.2003 (Civil Aviation Safety Security in Republic of Armenia).

Accident investigation GDCA Government Order 1777N, 2003, Accident and Serious Incident investigation, classification and registration manual.

1.2.1.2 GDCA

Civil aviation in Armenia is the responsibility of the GDCA, Governmental body having ministerial status.

By its decree of 3 March 1993 the Government of Armenia has established the GDCA, as a State Regulatory body in the field of civil aviation, reporting directly to the Government. Afterwards, in 2002 the Aviation Law has instituted the main tasks and responsibilities of the GDCA.

The General Department of Civil Aviation of the Republic of Armenia implements the State policy, State regulatory and economic regulatory functions and exercises State administration and supervision with regard to the use of the airspace and civil aviation operations in Armenia.

The GDCA is the National Supervisory Authority.

The GDCA is a State administration Institution under the authority of the Prime Minister and the Government, financed from the State budget.

The Government has approved a regulation enabling the GDCA to become financially self-sufficient and capable of funding its regulatory and oversight activities. It allows having certain inputs from user charges.

The GDCA is institutionally separated from the ANSP.

Further information is available on the GDCA web-site: http://www.aviation.am

Annual Report published: Y

Further information is available on the following web-site: http://aviation.am/index.php/en/legislation/hashv


1.2.2 ARMATS (ANSP)

1.2.2.1 Services provided

Name of the ANSP: ARMATS

Governance: Joint Stock Company Ownership: 100% State

Services provided Y/N Comment

ATC en-route Y

ATC approach Y

ATC Airport(s) Y

AIS Y

CNS Y

MET N Provided by the Aviation Meteorological Centre, a Joint Stock Company reporting to the Ministry of Nature Protection

ATCO training Y General and aviation English trainings in UK. Refresh trainings in Prague.

Others

Additional information:

Provision of services in other State(s):

N

Further information is available on the ARMATS web-site: http://www.armats.com

Annual Report published: Y http://armats.com/arm/activity/reports.htm This is the annual report covering yearly activities of the ANSP.

1.2.2.2 ATC systems in use

FDPS

Specify the manufacturer of the ATC system currently in use: AZIMUT (Russian Company)

Upgrade1 of the ATC system is performed or planned? Performed in 2013

Replacement of the ATC system by the new one is planned? --

ATC Unit Yerevan ACC, Yerevan APP, Yerevan TWR, Gyumri TWR

SDPS

Specify the manufacturer of the ATC system currently in use: AZIMUT (Russian Company)

Upgrade1 of the ATC system is performed or planned? Performed in 2013

Replacement of the ATC system by the new one is planned? --

ATC Unit Yerevan ACC, Yerevan APP, Yerevan TWR, Gyumri TWR

The new generation ATM system “GALAXY” deployed by the Russian company “AZIMUT” in 2013 is installed at Yerevan ATC centre. The system “GALAXY” has a modular architecture according to the EUROCONTROL requirements and uses “ASTERIX inside”. All subsystems are linked via redundant LAN and all servers have triple redundancy (Active, Hot-standby and Cold-standby).

Surveillance Data Processing System combines all traditional RDP functions and ability of connecting with different sensors PSR, (M) SSR, mode S, multilateration (MLAT) and ADS-B. Aircraft derived data is used for surveillance data processing and presentation of additional information in track labels (Indicated Airspeed, Selected Altitude and QNH , Magnetic Heading, Rate of Climb or Descent). All calculations are carried out in WGS-84 model of the Earth

1 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))


FDP system uses real time data from SDPS instead of static FPL route to update aircraft trajectory. Safety Nets processing is compatible with EUROCONTROL Specification for Short Term Conflict Alert (STCA), Minimum Safe Altitude Warning (MSAW), Area Proximity Warning (APW) and Approach Path Monitor (APM). MONA, MTCD, flexible vector, possibility of OLDI with adjacent FIRs, CPDLC, separate QNH areas for flights below transition level, automated update of flight plans and sending of DEP, ARR messages to CFMU are also engaged in the system. The system is also interfaced with European Aeronautical Database EAD (AIXM).

Controller Working Position provides an integrated representation of the air situation, combining actual surveillance sensor data and FPL information. Being ready scalable it can act as a separate working position directly interfacing with sensors (PSR, SSR, mode-S, ADS-B, MLAT, ADF, weather systems and AFTN network) or be a part of ATC system interfacing with SDPS and FDPS modules.

“GALAXY” simulator is used as a back-up system as well.

The new IP Voice Communication System (VCS) <MULTIFONO® M800IP > (<S.I.T.T.I.> Company, Italy) was installed at Yerevan ATC centre. The radio and telephone VCS fully integrates new IP Network requirements and latest technological achievements with user-friendliness needs at Operator and Maintenance levels. The VCS system combines all up-to-date interfaces such as MFC R2; ATS QSIG; E1 QSIG; and VoIP.

ATC units

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

ATC Unit Number of sectors Associated FIR(s) Remarks

En-route TMA

YEREVAN ACC 1 YEREVAN FIR 3 is the total number of sectors of Yerevan ATC (including TWR) YEREVAN APP 1 YEREVAN FIR

Gyumri APP 1 YEREVAN FIR

1.2.3 Airports

1.2.3.1 General information

There are two international airports in Armenia:

• Yerevan “Zvartnots” International Airport, the main gateway to Armenia, located 12 km southwest of Yerevan;

• “Shirak” Airport in Gyumri, located at about 100 km northwest of Yerevan.

All flights to Europe, Middle East, and other international connections originate exclusively out of “Zvartnots”.

Gyumri “Shirak” Airport only scheduled services for CIS countries and charter flights to all destinations.

Given the fact that Armenia is completely landlocked, the country relies heavily on its international airports as the main point of entry for both passengers and cargo.

“Zvartnots” International Airport is the main International Airport of Armenia, it provides full airport services.

“Zvartnots” International Airport and the Gyumri “Shirak” Airport are operated by Armenian International Airport Company.

ARMATS operates the joint approach and Tower units of “Shirak” Airport.

Further information is available on the AIA web-site: http://www.aia-zvartnots.aero

1.2.3.2 Airport(s) covered by the LSSIP

Referring to the List of Airports in the ESSIP Plan – Part I Section 4, it is up to the individual State to decide which additional airports will be reported through LSSIP for those objectives.

Based on this, Yerevan “Zvartnots” International Airport is the only Armenian airport covered by the LSSIP Year 2015.


1.2.4 Military Authorities

The Military Authorities in Armenia are composed of:

- Air Force,

- Air Defence.

They report to the Ministry of Defence.

Their regulatory, service provision and user role in ATM are detailed below.

1.2.4.1 Regulatory role

Regulatory framework and rule-making

Oversight

1.2.4.2 Service Provision role

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: Aviation Law, Rules of the Air and Air Force Regulations.

Level of such legal provision: NA

Authority signing such legal provision: Minister of Defence and Chief of Air Force

Authority signing such legal provision: NA

These provisions cover: These provisions cover:

Rules of the Air for OAT Y

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

OAT/GAT Coordination Y OAT/GAT Coordination Y

ATCO Training Y ATCO Training NA

ATCO Licensing Y ATCO Licensing NA

ANSP Certification Y ANSP Certification NA

ANSP Supervision Y ANSP Supervision NA

Aircrew Training Y ESARR applicability NA

Aircrew Licensing Y

Additional Information: Military provides only flight control in TSAs

Additional Information: Military do not provide air traffic control service to GAT flights.

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 Y National AIP Y

National Military AIP NA National Military AIP NA

EUROCONTROL eAIP Y EUROCONTROL eAIP Y

Other: NA Other: NA

OAT GAT

National oversight body for OAT: Ministry of Defence Air Force

National Supervisory Authority (as per SES reg. 550/2004) for GAT services provided by the military: GDCA (there is no Military NSA).

Additional information: nil Additional information: nil

OAT GAT

Services Provided: Services Provided:

En-Route Y En-Route NA

Approach/TMA Y Approach/TMA NA

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


Military ANSP providing GAT services SES certified?

NA If YES, since: Duration of the Certificate:

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

Additional Information: Armenia is not an EU member State.

1.2.4.3 User role

1.2.4.4 Flexible Use of Airspace (FUA)

AIS N AIS NA

MET Y MET NA

SAR Y SAR Y

TSA/TRA monitoring Y FIS NA

Other: Other:

Additional Information: nil Additional Information: nil

IFR inside controlled airspace, Military aircraft can fly?

OAT only N GAT only N Both OAT and GAT Y

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

Free Routing N Within specific corridors only Y

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 N

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

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

Others:

Military in Armenia applies FUA requirements as specified in the Regulation No 2150/2005: Y

FUA Level 1 implemented: Y




Traffic and Capacity Chapter 2 -

2.1 Evolution of traffic in Armenia

2015 Traffic in Armenia decreased by -13.9% during Summer 2015 (May to October inclusive), when compared to Summer 2014.

2016-2020

The STATFOR medium-term forecast (MTF) predicts an average annual traffic growth between 3.3% and 8.8% for the planning period, with an average baseline growth of 6.2%.

2.2 YEREVAN ACC

2.2.1 Summer 2015 performance

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

gap Ref value Actual

-13.9% 40 (0%) 0.01 0.0 No

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

Capacity Plan: Sufficient Capacity to meet demand Comments

Summer 2015 performance assessment

The ACC capacity baseline was estimated at 40. During the measured period, the average peak 1 hour demand was 11 and the average peak 3 hour demand was 8.

0

10.000

20.000

30.000

40.000

50.000

60.000

70.000

80.000

2011 A 2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F

IFR

flig

hts

Armenia - Annual IFR Movements

IFR movements - Actuals

IFR movements - Baseline forecast

IFR movements - High forecast

IFR movements - Low forecast A = ActualF = Forecast

2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F

H -9.9% 12.4% 8.2% 8.0% 7.7% 7.7% 6.9%

B -2.0% -6.6% -3.4% -10.6% 8.1% 5.7% 6.0% 5.7% 5.6% 5.0%

L -11.5% 1.8% 2.9% 4.2% 3.7% 3.6% 3.0%

ESRA08 B -2.4% -1.1% 1.7% 1.6% 2.3% 2.3% 2.3% 2.2% 2.7% 1.8%

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

Armenia


2.2.2 Planning Period 2016-2020

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.

Capacity Plan

2016 2017 2018 2019 2020

Free Route Airspace Night FRA 24H FRA Airspace Management

Advanced FUA

Airport & TMA Network Integration

Cooperative Traffic Management

Airspace New ATS route P130 REBLO-

ELSIV

Procedures Staffing

Technical

Capacity

Significant Events

Max sectors 1 1 1 1 1

Capacity increase p.a. Sufficient capacity to meet expected demand

Reference profile 0% 0% 0% 0% N/A

Additional information

2016 2017 2018 20190.01 0.01 0.01 0.010.01 0.01 0.01 0.01

En-route ATFM delay breakdown - Reference Values

AnnualSummer

UDDDCTA

H 40 0% 40 0% 40 0% 40 0%

Ref. 40 0% 40 0% 40 0% 40 0%

L 40 0% 40 0% 40 0% 40 0%

Open 40 0% 40 0% 40 0% 40 0%

C/R 40 0% 40 0% 40 0% 40 0%

ACC2015

baseline 2016 2017 2018 2019

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

UDDD 40


2014 2015 2016 2017 2018 2019 2020

2016‐2019 Reference Capacity Profile 40 40 40 40

Capacity Profile ‐ Shortest Routes (Open) 40 40 40 40

Capacity Profile ‐ Current Routes 40 40 40 40

Capacity Profile ‐ High 40 40 40 40

Capacity Profile ‐ Low 40 40 40 40

Capacity Baseline 40 40

2016 ‐ 2020 Plan 40 40 40 40 40

0

5

10

15

20

25

30

35

40

45

Cap

acity profile (movements per hour)

UDDDCTA - Reference capacity profile and alternative scenarios

2016-2020 Planning Period Outlook

No problems are foreseen for Yerevan ACC in the coming planning cycle.


ESSIP Report recommendations Chapter 3 -

Recommendations issued from the ESSIP Report for 2014 applicable to Armenia for all items that require corrective actions and improvements.

Reference number

Recommendation 2014 Ownership

REC-2014-2

Local Stakeholders that declared delays in implementation of FCM01, AOP04.1, SAF10, INF04, NAV03, AOP03, ENV01, ITY-AGDL, ITY-ADQ, COM09, COM10, ITY-FMTP and ITY-COTR, to take corrective measures to reduce the implementation delays.

Local Stakeholders

Corrective actions taken:

Yes.

Description:

FCM01 – objective has been completed in November 2015 and the ARMATS system is now connected to the NM systems;

ITY-AGDL – Armenia is not in the applicability area of the objective. Implementation is done on a voluntary basis. The ARMATS system has the data link capability; however a data link communication service provider has not yet been selected. The selection is on hold, pending the clarification of the technical aspects of the data link deployment;

ITY-FMTP, ITY-COTR – the two objectives are partly completed as the ARMATS system is fully OLDI and FMTP capable. The operational use is dependent on the establishment of the connection with Georgia, expected to be put in place in 2016.

COM10 – implementation is planned for 2016, in relation to the upgrade of the COM centre.

ITY-ADQ – Armenia is not in the applicability area of the objective. Implementation is done on a voluntary basis and is planned for 2016. The data integrity guidance material in local working and quality procedures/processes as well as the service level agreements with main actors are implemented.


National Projects Chapter 4 -

The main projects currently ongoing in Armenia are depicted in the table below.

Organisations Name Code Description Implementation Planning

EATM Links Status Performance Contribution2

Cooperation Activities

ARMATS AMHS

Procurement and installation of AMHS system.

From: Jan 2016

To: Dec 2016

COM 10 Planned Cost-efficiency and safety improvement

ARMATS Contingency

Room Construction and equipping of

the new Contingency Room

outside airport location.

From: Sep 2015

To: Feb 2016

Other: EC Regulation 1035/2011

Under operational

tests

Capacity: Seamless operation Safety: Improved safety

ARMATS OLDI The agreement has been signed and the testing has been done for the implementation of the basic OLDI via FMTP with Tbilisi FIR (North). The final connection is planned in 2016.

From: Jan 2016

To: Dec 2016

ITY-COTR

ITY-FMTP

Started Capacity: Seamless operation

Safety: Improved safety

With Georgia.

ARMATS DVOR/DME Procurement of a new DVOR/DME and replacement of the existing VOR/DME in “Zvartnots” airport are planned.

From: Jan 2016

To: Dec 2017

NAV Planned Safety and cost-efficiency improvement

ARMATS (AIS) AIS Transition from aeronautical information service concept (AIS) to aeronautical information management concept (AIM)

From: Sep 2014

To: Dec 2017

ITY-ADQ Started Safety and cost-efficiency improvement

ARMATS (AIS) AIS There is a plan to purchase and maintain the aeronautical database in a AIXM 5.1 format as well as update the software for generating eAIP.

From: Jan 2016

To: Dec 2017

ITY-ADQ Planned Safety improvement

ARMATS Free Route Implementation of Free Route Airspace, at night time as form 2017 followed by 24H Free Route in 2018.

From: Jan 2016

To: Dec 2018 (with initial deployment in 2017)

AOM21.2 Planned Capacity and cost-efficiency

2 Capacity, safety, cost-efficiency and environment – as defined in recital 25 of Commission Implementing Regulation (EU) No 390/2013


Regional Co-ordination Chapter 5 -

5.1 Regional cooperation

To facilitate the harmonisation process within the different ANS Domains in the Caucasus region with the objective of meeting global and European standards and directives, Armenia has for several years enhanced and developed ANS co-operation. The harmonisation approach is based on the assumption that regional and sub-regional planning, development and management is a necessity in order to establish and maintain the future CNS/ATM systems at a safe, productive and cost-effective level, which will be accepted by the airspace users.

Operational Letters of Agreement (LoAs) have been signed between Yerevan ACC and all neighbouring countries; non ECAC ACC Tehran ACC and ECAC ACCs Tbilisi ACC, Ankara ACC and Baku ACC. They take into account the implementation of RVSM in European region of ICAO and RNAV Routes.

The agreement has been signed and the testing has been done for the implementation of the basic OLDI (ABI, ACT, REV, PAC, MAC, LAM) via FMTP with Tbilisi FIR (North). The final connection is planned in 2016.


ESSIP Objective Implementation Chapter 6 -

6.1 Conventions

Two colour codes are used for each ESSIP Objective ‘box’:

o a colour code is used to show the Objective Scope in the Objective ID cell, and

o another colour code is used to show the Objective Progress in the State and for each national stakeholder.

Obj. ID (*) Obj. Title (By mm/yyyy of overall objective, inc non-State SloAs) Obj. Progress (**)

State’s high level progress statement State Impl. Date

REG (By:mm-yyyy) REG high level progress statement

APO. Progress (**)

APO Impl. Date ASP (By:mm-yyyy) ASP high level progress statement

ASP. Progress (**)

ASP Impl. Date MIL (By:mm-yyyy) MIL high level progress statement

MIL. Progress (**)

MIL Impl. Date APO (By:mm-yyyy) APO high level progress statement

APO. Progress (**)

APO Impl. Date

(*) Objective Scope Code: (**) Objective/Stakeholder Progress Code:

ECAC Completed No Plan

EU+ Partly Completed Not Applicable

Multi-N Planned Missing Data

APT Late


6.2 ESSIP Objectives Implementation progress

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

No Plan

‐

There are established OAT/GAT handling rules and procedures; they are not based on EUROAT. Conformance analysis and possible amendments of the existing rules/procedures will be addressed in 2016.Objective will be reviewed after the conformance analysis.

‐

REG (By:12/2018)

GDCA ‐ ‐ No Plan

‐

Mil. Authority

There are established OAT/GAT handling rules and procedures; they are not based on EUROAT. Conformance analysis and possible amendments of the existing rules/procedures will be addressed in 2016. Objective will be reviewed after the conformance analysis.

‐

No Plan

‐

ASP (By:12/2018)

Mil. Authority


‐

No Plan

‐

ARMATS ‐ ‐ No Plan

‐

MIL (By:12/2018)

Mil. Authority


‐

No Plan

‐

AOM19

Implement Advanced Airspace Management

Timescales:


Not Applicable

‐

There is flexible use of airspace based on procedures. ‐

ASP (By:12/2016)

ARMATS There is flexible use of airspace based on procedures. ‐ Not Applicable

‐

Mil. Authority The displaying position of the ATM ‐Galaxy‐ system is installed in military authority in 2014.

‐ Not Applicable

‐

AOM21.1

Implementation of Direct Routing

Timescales:

Initial Operational Capability: 01/01/2015 Full Operational Capability: 31/12/2017

[PCP]

[Essential] Not Applicable

‐

All ATS routes are direct in Armenian airspace and Armenia is going to implement full free route in 2017. ‐

ASP (By:12/2017)

ARMATS All ATS routes are direct in Armenian airspace. ‐ Not Applicable

‐


AOM21.2

Implement Free Route Airspace

Timescales:


[PCP]

[Essential] Planned

‐

Armenia plans to implement night time Free Route Airspace in 2017, followed by 24H Free Route Airspace in 2018.

31/12/2017

ASP (By:12/2021)

ARMATS Armenia plans to implement night time Free Route Airspace in 2017, followed by 24H Free Route Airspace in 2018.

Free Route Planned

31/12/2017

AOP03

Improve runway safety by preventing runway incursions

Timescales:


Completed

‐

The runway safety team is established and operational. Not all drivers on the runway speak English. The team is composed by representatives of the Zvartnots International Airport and the ANSP ARMATS. There are procedures related to the runway safety. The SMS of Zvartnots International Airport and ARMATS address also Runway Safety. The runway safety team meets 2 times a year, plus when there is a need for a particular runway safety issue. There is a LoA between ARMATS and the Airport authorities that establishes roles and responsibilities of each stakeholder.

31/12/2013

REG (By:12/2013)

GDCA GDCA has decided upon the strategy for implementation at Zvartnots International Airport of specific actions contained in the EAPRI document.

‐ Completed

31/12/2013

ASP (By:12/2013)

ARMATS Voice communications between the tower and drivers are not conducted in English.

‐ Completed

31/12/2013

APO (By:12/2013)

YEREVAN Zvartnots Airport

The airport SMS is approved by the regulatory body and it is operational. Drivers on the runway do not speak English.

‐ Completed

31/12/2013


AOP04.1

Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level1

Timescales:

‐ not applicable ‐

Not Applicable

UDYZ ‐ Yerevan Airport

(Outside Applicability Area)

There is in average 20 days of bad visibility per year. Due to the level of traffic, the deployment of A‐SMGCS Level 1 is not yet justified therefore UDYZ is not considered to be within the applicability area of the objective. However the deployment of A‐SMGCS based on multilateration may be considered in the future. The installation of a primary surveillance is not foreseen

‐

REG (By:12/2010)

GDCA When the ANSP and the Airport have decided to implement an A‐SMGCS system, the regulator will take the required actions.

‐ Not Applicable

‐

ASP (By:12/2011)

ARMATS There is in average 20 days per year of bad visibility. ‐ Not Applicable

‐

APO (By:12/2010)


There is in average 20 days per year of bad visibility for CAT II conditions and less then 10 days per year for CAT III conditions.

‐ Not Applicable

31/12/2015

AOP04.2

Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level 2

Timescales:


Not Applicable



In average per year bad visibility is about 20 days for CAT II conditions and less than 10 days for CAT III conditions. Due to the level of traffic, the deployment of A‐SMGCS Level 2 is not yet justified therefore UDYZ is not considered to be within the applicability area of the objective.

‐

ASP (By:12/2017)

ARMATS Due to the level of traffic, the deployment of A‐SMGCS Level 2 is not yet justified therefore UDYZ is not considered to be within the applicability area of the objective.

‐ Not Applicable

‐

APO (By:12/2017)


Armenia is not part of the applicability area; however, this objective is under review for its possible implementation.

‐ Not Applicable

‐


AOP05

Implement Airport Collaborative Decision Making (CDM)

Timescales:


Not Applicable



Zvartnots Airport is not a busy airport. There are ideas to implement an automated system for the exchange of messages between ARMATS and Zvartnots Airport.

‐

ASP (By:12/2016)

ARMATS Armenia is not part of the applicability area. ‐ Not Applicable

‐

APO (By:12/2016)


Armenia is not part of the applicability area. ‐ Not Applicable

‐

AOP10

Time Based Separation

Timescales:


[PCP]




UDYZ is not within the applicability area of the objective and there are no operational needs for implementation due to the levels of traffic.

‐

REG (By:12/2023)

GDCA ‐ ‐ Not Applicable

‐

ASP (By:12/2023)

ARMATS ‐ ‐ Not Applicable

‐

AOP11

Initial Airport Operations Plan

Timescales:

Initial Operational Capability: 01/01/2015 Full Operational Capability: 31/12/2021

[PCP]

[Essential] No Plan


Objective not reviewed yet ‐

ASP (By:12/2021)

ARMATS ‐ ‐ No Plan

‐

APO (By:12/2021)


‐ ‐ No Plan

‐


AOP12

Improve runway and airfield safety with ATC clearances monitoring

Timescales:


[PCP]




UDYZ is not within the applicability area of the objective and there are no operational needs for implementation due to the levels of traffic.

‐

ASP (By:12/2020)


‐

APO (By:12/2020)


‐ ‐ Not Applicable

‐

ATC02.5

Implement ground based safety nets ‐ Area Proximity Warning ‐ level 2

Timescales:


Completed

‐

The ATM system ‐Galaxy‐ has the APW level 2 implemented and operational in Yerevan ACC and Yerevan TMA. Implementation of procedures and training of controllers is done.

31/12/2013

ASP (By:12/2016)

ARMATS ARMATS has installed the ATM system with APW level 2 capability. ‐ Completed

31/12/2013

ATC02.6

Implement ground based safety nets ‐ Minimum Safe Altitude Warning ‐ level 2

Timescales:


Completed

‐

The ATM system ‐Galaxy‐ has the Minimum Safe Altitude Warning level 2 implemented and operational in Yerevan ACC and Yerevan TMA.

31/12/2013

ASP (By:12/2016)

ARMATS ARMATS has installed the new ATM system with MSAW level 2 capability. ‐ Completed

31/12/2013

ATC02.7

Implement ground based safety nets ‐ Approach Path Monitor ‐ level 2

Timescales:


Completed

‐

The ATM system ‐Galaxy‐ has the APM level 2 implemented and operational. 31/12/2013

ASP (By:12/2016)

ARMATS ARMATS has installed the ATM system with APM level 2 capability. ‐ Completed

31/12/2013


ATC07.1

Implement AMAN tools and procedures

Timescales:


Not Applicable



Taking into account the forecast traffic levels over the LSSIP timeframe, no need to implement this Objective has been identified. No benefits identified for the foreseeable future.

‐

ASP (By:12/2015)

ARMATS Armenia is not part of the applicability area. ‐ Not Applicable

‐

ATC12.1

Implement automated support for conflict detection, resolution support information and conformance monitoring

Timescales:


Completed

‐

The ATM system has the MTCD and MONA functions implemented and operational. Taking into account the low traffic level in Armenian airspace no need to implement the conflict resolution (CORA).

31/12/2013

ASP (By:12/2021)

ARMATS

The ATM system has the MTCD and MONA functions implemented and operational. Taking into account the low traffic level in Armenian airspace no need to implement the conflict resolution (CORA).

‐

Completed

31/12/2013

ATC15

Implement, in En‐Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations


Timescales:


Not Applicable

‐

Taking into account the forecast traffic levels, no need to implement this Objective has been identified. ‐

ASP (By:12/2017)

ARMATS Taking into account the forecast traffic levels, no need to implement this Objective has been identified.

‐ Not Applicable

‐


ATC16

Implement ACAS II compliant with TCAS II change 7.1

Timescales:


Late

‐

It will be implemented in 2016 according to ICAO Annex 6 and Annex 10. For more details, see the comments at Stakeholder level.

31/12/2016

REG (By:12/2015)

GDCA Will be implemented in 2016 according to ICAO Annex 6 and Annex 10. ‐ Late

31/12/2016

ASP (By:03/2012)

ARMATS It is implemented. ‐ Completed

31/01/2012

MIL (By:12/2015)

Mil. Authority Not applicable as the retrofit is not justified in term of benefits. The pilots are trained and know what to expect from the equipped aircraft, if they fly in their vicinity.

‐ Not Applicable

‐

ATC17

Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer

Timescales:


No Plan

‐

The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since 2013.The agreement has been signed and the testing has been done for the implementation of the basic OLDI via FMTP with Tbilisi FIR (North). The final connection is planned in 2016. Currently there are no precise plans with regard the implementation and the operational use of the messages covered by ATC17.

31/01/2017

ASP (By:12/2018)

ARMATS

The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since 2013. The agreement has been signed and the testing has been done for the implementation of the basic OLDI via FMTP with Tbilisi FIR (North). The final connection is planned in 2016.

‐

No Plan

31/01/2017

COM10

Migrate from AFTN to AMHS

Timescales:


Late

‐

The ATM system has an AMHS capability. The migration of the AFTN system to AMHS is foreseen through the existing COM centre upgrade. Yet the operational use will be addressed at regional level with connected MTA (Message Transfer Agent).

31/12/2016

ASP (By:12/2014)

ARMATS ARMATS will upgrade the COM centre to implement AMHS. AMHS Late

31/12/2016


COM11

Implementation of Voice over Internet Protocol (VoIP) in ATM

Timescales:


Partly Completed

‐

The new VCS system has capability to use Voice over IP. It will be used in case of the neighbour centres will have such capability.

31/12/2017

ASP (By:12/2020)

ARMATS The ARMATS new VCS system has capability to use Voice over IP. ‐

Partly Completed

31/12/2017

ENV01

Implement Continuous Descent Operations (CDO) techniques for environmental improvements

Timescales:


Completed


CDA is implemented for 24 hours. All airport arrivals are achieving a CDA profile. All airlines are applying CDA. There is no monitoring. All procedures including SIDs and STARs are designed aiming at minimising the environmental impact. CDA approaches are published in the AIP.

31/12/2009

ASP (By:12/2013)

ARMATS BCDA procedures are applied in Armenia. ‐ Completed

31/12/2009

APO (By:12/2013)


BCDA procedures are applied in Armenia. ‐ Completed

31/12/2009

ENV02

Implement Collaborative Environmental Management (CEM) at Airports

Timescales:


Completed



The Collaborative Environmental Management (CEM) team meets regularly. The team is composed by representatives of the Airport, the ANSP and the major aircraft operator. The team dose not have a formal status and a TOR, it meets only when needed to address specific issues. The main task of the Environment unit is the noise abatement and airfield fuel and emissions reduction.

31/12/2009

ASP (By:12/2016)

ARMATS ARMATS cooperates with the Airport and Aircraft Operators in order to facilitate a joint approach contributing to the minimisation of noise and gaseous emissions resulting from aircraft operations.

‐ Completed

31/12/2009

APO (By:12/2016)


The airport has an Environment Manager with clearly defined action plan. The main task of the Environment unit is the noise abatement and airfield fuel and emissions reduction.

‐ Completed

31/12/2009


FCM01

Implement enhanced tactical flow management services

Timescales:


Completed

‐

Armenia is in the IFPS Zone. The new ATC system is connected to the NM. The installation of the Entry Node was done in 2015.The FSA and CPR messages are sent to the NM.

31/12/2015

ASP (By:07/2014)

ARMATS Armenia migrated to the IFPS Zone on the 21 December 2006. The new system is connected to the NM. The installation of the Entry Node was done in 2015.The FSA and CPR messages are sent to the NM.

‐ Completed

31/12/2015

FCM03

Implement collaborative flight planning

Timescales:


Planned

‐

Armenia is in the IFPS Zone. Currently the connection with CFMU is ensured through the FMP; the ATC system is not connected to CFMU. The processing of ADEXP format will be implemented after the installation of AMHS.

31/12/2016

ASP (By:12/2017)

ARMATS The processing of ADEXP format will be implemented after the installation of AMHS.

‐ Planned

31/12/2016

FCM04

Implementation of Short Term ATFCM Measures ‐ phase 1


Timescales:


Not Applicable

‐

Armenia is not in the applicability area of the objective. ‐

ASP (By:12/2015)

ARMATS Armenia is not in the applicability area of the objective. ‐ Not Applicable

‐

FCM05

Implementation of interactive rolling NOP

Timescales:


[PCP]


‐

Due to the level of traffic and airspace configuration, here is no operational need for ASM systems (e.g. AOM19) therefore there is nothing to integrate with NM related to data exchanges in AIXM5.1

‐

ASP (By:12/2017)


‐

Mil. Authority ‐ ‐ Not Applicable

‐

APO (By:12/2021)


‐ ‐ Not Applicable

‐


FCM06

Traffic Complexity Assessment


Timescales:


[PCP]


‐

Armenia is not in the applicability area of the objective. The ATM system has the Sector Load Monitor (with graphic presentation for ACC, APP, and TWR and en‐ route TLM presentation) and Point TLM functions.

‐

ASP (By:12/2021)

ARMATS The ATM system has the Sector Load Monitor (with graphic presentation for ACC, APP, and TWR and en‐ route TLM presentation) and Point TLM functions.

‐ Not Applicable

‐

INF04

Implement integrated briefing

Timescales:


Completed

‐

The implementation of level 3 and 4 was done on time and it is operational; the level 5 is operational since January 2007. Terminal and Integrated Briefing function at international airports of Armenia are provided. It is also accessible through Internet as of March 2007.

31/01/2007

ASP (By:12/2012)

ARMATS The integrated briefing level 5 is implemented. ‐ Completed

31/01/2007

INF07

Electronic Terrain and Obstacle Data (TOD)

Timescales:


Planned

‐

The ATM system‐Galaxy‐ has the TOD implemented and operational in 15/11/2013. In accordance with ICAO requirements the TOD policy and implementation programme is established. The state will establish the regulatory framework procedures at the end of 2016.

30/11/2016

REG (By:05/2018)

GDCA In accordance with ICAO requirements the TOD policy and implementation programme is established. The state will establish the regulatory framework procedures at the end of 2016.

‐

Partly Completed

30/11/2016

ASP (By:05/2018)

ARMATS The Terrain Data and Obstacles for all Areas were published in Nov of 2015 according to ICAO Annex 15 and are used in ATM system.

‐

Partly Completed

30/11/2016

APO (By:05/2018)


The Terrain Data and Obstacle for all Areas were published in Nov of 2015 according to ICAO Annex 15 and are used in ATM system.

‐

Partly Completed

30/11/2016


ITY‐ACID

Aircraft identification


Timescales:


Completed

‐

Armenia is not part of the applicability area. Hoverer, the ATM system ‐Galaxy‐ has the aircraft identification implemented and operational.

15/11/2013

ASP (By:01/2020)

ARMATS ARMATS has implemented the aircraft identification using WAM and ADS‐B.

‐ Completed

15/11/2013

ITY‐ADQ

Ensure quality of aeronautical data and aeronautical information


Timescales:


Planned

‐

Armenia is outside the applicability area of the objective, Voluntary implementation started in 2007; the data integrity guidance material in local working and quality procedures/processes as well as the service level agreements with main actors are implemented.

31/12/2016

REG (By:06/2017)

GDCA The regulator is adopting required documentations for the implementation of ADQ

‐ Completed

31/12/2015

ASP (By:06/2017)

ARMATS ARMATS implemented end‐to‐end integrity of aeronautical data during 2009. The implementation of ADQ has started.

AIS_1 / AIS_2 Planned

31/12/2016

APO (By:06/2017)


Airport has quality management system, and is implementing ADQ ‐ Planned

31/12/2016

ITY‐AGDL

Initial ATC air‐ground data link services above FL‐285


Timescales:


Planned

‐

Armenia is not in the applicability area of the objective. However, the ‐Galaxy‐ ATM system installed In Yerevan ATC centre, has the Data Link capability. The full benefits of the operational use remains dependent on the neighbouring ACCs‐ capabilities. Moreover the contract with the data link communications service provider is not signed yet. The implementation is on hold pending clarification of the technical solutions.

31/12/2017

REG (By:02/2018)

GDCA The GDCA will conduct oversight once the system is installed REG02 has been delegated to EUROCONTROL.

‐ Planned

31/12/2017

ASP (By:02/2018)

ARMATS ARMATS plans to implement Air/Ground data link services. The ‐Galaxy‐ ATM system installed In Yerevan ATC centre, has the data link capability.

‐ Planned

31/12/2017

MIL (By:01/2019)

Mil. Authority There is no intention to equip the transport‐type State aircraft with data link equipment

‐ Not Applicable

‐


ITY‐AGVCS2

Implement 8,33 kHz air‐ground voice channel spacing below FL195


Timescales:


Not Applicable

‐

Armenia is not in the applicability area of the objective. ‐

REG (By:12/2018)

GDCA Armenia is not in the applicability area of the objective. ‐ Not Applicable

‐

ASP (By:12/2018)

ARMATS Armenia is not in the applicability area of the objective. ‐ Not Applicable

‐

MIL (By:12/2020)

Mil. Authority Armenia is not in the applicability area of the objective. ‐ Not Applicable

‐

APO (By:12/2018)


Armenia is not in the applicability area of the objective. ‐ Not Applicable

‐

ITY‐COTR

Implementation of ground‐ground automated co‐ordination processes


Timescales:


Partly Completed

‐

The new ‐Galaxy‐ ATM system has the capability. The operational use remains dependent on the neighbouring ACCs‐ capabilities. The agreement has been signed and the testing has been done for the implementation of the basic OLDI with Tbilisi FIR (North). The final connection is expected in 2016.

31/12/2013

ASP (By:02/2018)

ARMATS

The new ‐Galaxy‐ ATM system has the capability. The operational use remains dependent on the neighbouring ACCs‐ capabilities. The agreement has been signed and the testing has been done for the implementation of the basic OLDI with Tbilisi FIR (North). The final connection is expected in 2016.

OLDI

Partly Completed

31/12/2013

MIL (By:12/2012)

Mil. Authority Military do not provide ATC service to civil flights ‐ Not Applicable

‐


ITY‐FMTP

Apply a 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

Partly Completed

‐

The new 'Galaxy' ATM system has the capability. Has to be addressed at regional level. The agreement has been signed and the testing has been done for the implementation of the basic OLDI (ABI, ACT, REV, PAC, MAC, LAM) via FMTP with Tbilisi FIR (North). The final connection is expected in 2016.

31/12/2014

ASP (By:12/2014)

ARMATS The new 'Galaxy' ATM system has the capability, yet it has to be implemented at regional level.

OLDI

Partly Completed

31/12/2014

MIL (By:12/2014)

Mil. Authority Military do not provide ATC service to civil flights ‐ Not Applicable

‐

ITY‐SPI

Surveillance performance and interoperability


Timescales:


Partly Completed

‐

The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002) and MLAT (CAT‐19, CAT‐20, CAT‐21, CAT‐034, CAT‐048) with time stamping, ATM system by ASTERIX protocols (CAT‐62) was implemented within the period of 2008‐2015. The operational use remains dependent on the neighbouring ACCs‐ capabilities.

31/12/2013

REG (By:02/2015)

GDCA Done in the context of the deployment of the new ATM system. ‐ Completed

31/12/2013

ASP (By:02/2015)

ARMATS

The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002) and MLAT (CAT‐19, CAT‐20, CAT‐21, CAT‐034, CAT‐048) with time stamping, ATM system by ASTERIX protocols (CAT‐62) was implemented within the period of 2008‐2015. The operational use remains dependent on the neighbouring ACCs‐ capabilities.

P3D Expansion and Upgrade

Partly Completed

31/12/2013

MIL (By:06/2020)

Mil. Authority Equipage of military fleet is not economically justified. ‐ Not Applicable

‐


NAV03

Implementation of P‐RNAV

Timescales:


Completed

‐

The implementation was done in 2012. In summer 2007, B‐RNAV was implemented in the upper airspace (Above FL 195) of Armenia. All co‐ordinates for the publication in the AIP are prepared in WGS‐84 format, in line with the accuracy and integrity requirements specified in ICAO Annex 15.

31/12/2012

ASP (By:12/2023)

ARMATS

All co‐ordinates for the publication in the AIP are prepared in WGS‐84 format, in line with the accuracy and integrity requirements specified in ICAO Annex 15. The implementation of P‐RNAV was completed in 2012.

DVOR/DME

Completed

31/12/2012

NAV10

Implement APV procedures

Timescales:


Completed

‐

The APV Baro‐VNAV procedures at Zvartnots airport is already implemented, the safety case was developed and submitted to NSA, the subsequent approval has been given.

31/12/2012

REG (By:04/2016)

GDCA In 2011 the GDCA has published national regulatory APV procedures, and approved APV safety case and APV operations.

‐ Completed

31/03/2011

ASP (By:12/2016)

ARMATS The APV Baro‐VNAV procedures at Zvartnots airport is already implemented, the safety case was developed and submitted to NSA, the subsequent approval has been given.

DVOR/DME Completed

31/12/2012

SAF10

Implement measures to reduce the risk to aircraft operations caused by airspace infringements

Timescales:


Completed

‐

The European action plan is implemented. 31/12/2012

REG (By:12/2011)

GDCA GDCA is involved in the development of the implementation plan. ‐ Completed

31/12/2012

ASP (By:12/2011)

ARMATS All the applicable measures were implemented ‐ Completed

31/12/2012

MIL (By:12/2011)

Mil. Authority Military are consulted. ‐ Not Applicable

31/12/2012


SAF11

Improve runway safety by preventing runway excursions

Timescales:


Planned

‐

The EAPPRE recommendations applicable to ARMATS and Zvartnots airport are implemented (RWY information, meteo data, AIP publications, ATS operations and so on).

31/01/2018

REG (By:01/2018)

GDCA Implementation planned. ‐ Planned

31/01/2018

ASP (By:12/2014)

ARMATS The EAPPRE recommendations are implemented (RWY information, meteo data, AIP publications, ATS operations and so on).

‐ Completed

31/12/2014

APO (By:12/2014)


The applicable EAPPRE recommendations are implemented ‐ Completed

31/12/2014


6.3 Alignment of PCP with ESSIP Objectives and related progress


Annexes

Annex A – Specialists involved in the LSSIP Process

LSSIP Co-ordination

LSSIP Focal Points Organisation Name

LSSIP Focal Point for Armenia ARMATS Mr. Samvel BAGHDASARYAN

LSSIP Focal Point for ANSP ARMATS Mr. Samvel BAGHDASARYAN

LSSIP Focal Point GDCA GDCA Mr. Galust POGOSYAN

LSSIP Focal Point for Airport Zvartnots and Gyumri International Airports

Mr. Sergey NALBANDYAN

LSSIP Focal Point for Military MIL Mr. Alik SARGSYAN

EUROCONTROL LSSIP Support

Function Directorate Name

LSSIP Contact Person for Armenia DPS/PEPR Mr. Octavian CIOARA

ESSIP Objective Implementation

ESSIP Objective

EUROCONTROL Objective Owners EUROCONTROL PEPR Objective Coordinator

National Stakeholder Specialist(s)

AOM13.1 R. BUCUROIU, O. MROWICKI, C. LUCCIOLI, E. REUBER

A. DYBOWSKA Mr. Arthur PAPOYAN

Mr. Sergey DANIELYAN

AOM19 G. ACAMPORA, O. MROWICKI



AOM21.1 R. BUCUROIU



AOM21.2 R. BUCUROIU



AOP03 T. LICU

P. VRANJKOVIC Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN

AOP04.1 P. ADAMSON

P. VRANJKOVIC Mr. Gevorg SIMONYAN Mr. Sergey NALBANDYAN

AOP04.2 P. ADAMSON

P. VRANJKOVIC Mr. Gevorg SIMONYAN Mr. Sergey NALBANDYAN

AOP05 P. ADAMSON


AOP10 M. BIRENHEIDE

B. HILL Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN

AOP11 M. BIRENHEIDE


AOP12 M. BIRENHEIDE


ATC02.5 B. BAKKER, S. DROZDOWSKI

I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN


I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN


I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Harutyun BABAYAN

ATC07.1 P. CONROY, P. TERZIOSKI

L. DELL’ORTO Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN


ESSIP Objective

EUROCONTROL Objective Owners EUROCONTROL PEPR Objective Coordinator

National Stakeholder Specialist(s)

ATC12.1 P. TERZIOSKI


ATC15 P. CONROY, P. TERZIOSKI


ATC16 S. DROZDOWSKI

L. DELL’ORTO Mr. Samvel BAGHDASARYAN Mr. Aram TUNYAN

ATC17 S. MORTON

L. DELL’ORTO Mr. Samvel BAGHDASARYAN


COM10 Y. EYUBOGLU A. KOKONA Mr. Gevorg SIMONYAN

COM11 L. POPESCU A. KOKONA Mr. Gevorg SIMONYAN

ENV01 C. FABER


ENV02 S. MAHONY, A. WATT


FCM01 H. KOOLEN

O. CIOARA Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN

FCM03 TBD


FCM04 P. HOP


FCM05 I. MENDES


FCM06 P. HOP

O. ALFARO Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN

INF04 P. MATERN A-P. FRANGOLHO Mr. Gevorg HARUTYUNYAN

INF07 A. PETROVSKY

A-P. FRANGOLHO Mr. Galust POGHOSYAN

Mr. Gevorg HARUTYUNYAN

ITY-ACID A. DESMOND-KENNEDY O. CIOARA Mr. Sergey DANIELYAN

ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Mr. Gevorg HARUTYUNYAN

ITY-AGDL S. DISSING A. KOKONA Mr. Gevorg SIMONYAN

ITY-AGVCS2 J POUZET

O. ALFARO Mr. Arthur PAPOYAN

Mr. Gevorg SIMONYAN

ITY-COTR S. MORTON L. DELL’ORTO Mr. Samvel BAGHDASARYAN

ITY-FMTP L. POPESCU O. ALFARO Mr. Gevorg SIMONYAN

ITY-SPI M. BORELY, R. STEWART O. CIOARA Mr. Gevorg SIMONYAN

NAV03 F. PAVLICEVIC

A. KOKONA Mr. Artur ALAVERDYAN Mr. Partev MAMIKONYAN

NAV10 R. FARNWORTH A. KOKONA Mr. Artur ALAVERDYAN

SAF10 T. LICU I. FEIJT Mr. Aram TUNYAN

SAF11 S. LAWRENCE I. FEIJT Mr. Aram TUNYAN


Annex B – National Stakeholders Organisation Charts

ARMATS

Aviation Joint Stock Companies

Aviation Training Centre

State Enterprise

Avia-Medical Centre

State Enterprise

ARMATS Air Operators

(ARM. Reg)

ATS Director Financial Director Director of Ground Handling and Audit

General meeting of Company Stakeholders

Management Board

General Director

Technical Director

Building and Constructions

Operation Department

Aviation Security Department

Audit

Flight Safety Department

Transport Department

Planning and

Procurement Service

Collegial Executive Body

Accountancy “Yerevan” ATC

Center

“Yerevan” ATC

Tower

Financial Economical

Service

Legal Service

Aeronautical Information

Service

Quality Management and

Monitoring Department

Training

Department Technical Monitoring

Department

Power Supply Service

“Gyumri” ATS

Service

ATM Systems Management Service

Surveillance Service

Navigation Service

Communication Service

Operational Control

Department

“Gyumri” ATC

Tower

Auxiliary Department

Administration Staff

ATS planning

Service

IT Department


ZVARTNOTS AND SHIRAK AIRPORTS ADMINISTRATION (AIA) - ORGANIZATION CHART

Operation Manager (1) Security Manager (1) Maintenance Manager (1)

Shift Manager & Land Side (5)

Safety & Quality Control Manager (1)

Ground Handling Manager (1) ()()( )

Check in Manager (1) Training & License (1)

Resource Allocator (4)

Ramp Control & Follow Me (8)

Radio Ground (4)

Operative Information Office (5)

General Manager


Annex C – Glossary of Abbreviations

Specific abbreviations for Armenia:

AIA – Armenian International Airports

ARMATS – Armenian Air Traffic Services

GDCA – General Department of Civil Aviation