Local Single Sky ImPlementation (LSSIP) ARMENIA · Enforcement actions in case of non-compliance...

EUROCONTROL

Year 2013 ‑ Level 1

Local Single Sky ImPlementation (LSSIP) ARMENIA

LSSIP Year 2013 Armenia Released issue

DOCUMENT IDENTIFICATION SHEET

LSSIP for Armenia

Infocentre Reference: 14/01/07-02

Document Identifier Edition: Year 2013

LSSIP Year 2013 Armenia Edition Date: 30 Jan 2014

LSSIP Focal Point – Samvel Baghdasaryan

E-mail: [email protected]

Head of Technical and Information

Provision Services

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

Unit DSS/EIPR

Status Intended for

Working Draft General Public

Draft Agency Stakeholders

Proposed Issue Restricted Audience

Released Issue

Accessible via: Internet (www.eurocontrol.int)

Path: X:\03 LSSIP\1. LSSIP States\Armenia (AM)\Year_2013\Released\LSSIP Year2013_AM_Released.doc

LINKS TO REFERENCE DOCUMENTS

1. LSSIP Guidance Material: http://www.eurocontrol.int/articles/guidance-material 2. ESSIP Plan Edition 2013: www.eurocontrol.int/pepr 3. ESSIP Report 2012: www.eurocontrol.int/pepr 4. STATFOR Forecasts: http://www.eurocontrol.int/forecast-monitoring-analysis 5. Acronyms and abbreviations: http://www.eurocontrol.int/articles/glossaries 6. European ATM Master Plan: https://www.atmmasterplan.eu/ 7. LSSIP Documents: http://www.eurocontrol.int/articles/lssip 8. National AIP: http://armats.com/eng/aviation/aip.htm 9. National Performance Plan: Request should be send to e-mail: [email protected] 10. National Business Plan (In Armenian): Request should be send to e-mail: [email protected]

LSSIP Year 2013 Armenia Released issue

TABLE OF CONTENTS

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

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

Chapter 1 - National ATM Environment ..................................................................................................... 5 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 1.2.5 Accident/incident Investigation Body .................................................................................. 12

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

2.2.1 Summer 2013 performance ................................................................................................ 13 2.2.2 Planning Period 2014-2018/19 - Summer ........................................................................... 13

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

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

Chapter 5 - Regional Co-ordination ......................................................................................................... 17 5.1 Regional coordination projects ................................................................................................. 17

Chapter 6 - ESSIP Objective Implementation .......................................................................................... 18

ANNEXES

LSSIP Year 2013 Armenia 1 Released issue

Executive Summary

State Context

During 2013 the following changes have been done. The new ATM system <Galaxy> (<AZIMUT> Company, Russian Federation) has been successfully installed with combination of the VCS of the <MULTIFONO M800IP > (<S.I.T.T.I.> Company, Italy) and fully operational. The EAD Briefing Facility system has been installed (Frequentis Company, Austria) and fully operational.

ESSIP Objective Implementation

The implementation of ECAC wide Objectives progressed significantly in 2013 notably due to the introduction into service of the new ATM system. 7 additional ESSIP objectives were implemented in 2013: AOM20, AOP03, ATC02.2, ATC02.5, ATC02.6, ATC02.7 and ATC12. This leads to an overall of 16 active objectives from the ESSIP Plan edition 2013 already implemented by Armenia. In particular, ARMATS has implemented RNAV1 in Yerevan TMA, RNP APCH with Baro VNAV for RWY09 and RNP APCH for RWY27.

The following objectives have been implemented partially: COM09, COM11, ITY-COTR and ITY-FMTP. Full compliance is not yet achieved due to the lack of capabilities in the neighbouring centres.

LSSIP 2013 - Armenia * FOC Date

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

State-related ESSIP Objectives

<=

2007

20

08

2009

20

10

2011

20

12

2013

20

14

2015

20

16

2017

20

18

2019

20

20

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

[IDP] [E] *

AOM19 Implement Advanced Airspace Management [IDP] [E] *

AOM20 Implement ATS Route Network (ARN) - Version 7 [E] *

AOM21 Implementation of Free Route Airspace [IDP] [E] *

AOP03 Improve runway safety by preventing runway incursions *

ATC02.2 Implement ground based safety nets - Short Term Conflict Alert (STCA) - level 2 [E] *

ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2 [E] *

ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2 [E] *

ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2 [E] *

ATC07.1 Implement arrival management tools [E] *

ATC12 Implement automated support for conflict detection and conformance monitoring [E] *

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

[IDP] [E] *

ATC16 Implement ACAS II compliant with TCAS II change 7.1 *

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

[IDP] [E] *

COM09 Migrate ground international or regional X.25 data networks or services to the Internet Protocol (IP) [IDP] *


LSSIP 2013 - Armenia * FOC Date

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

COM10 Migrate from AFTN to AMHS *

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

FCM01 Implement enhanced tactical flow management services [E] *

FCM03 Implement collaborative flight planning [IDP] [E] *

FCM04 Implementation of Short Term ATFCM Measures - phase 1 [IDP] [E] *

FCM05 Implementation of interactive rolling NOP [IDP] [E] *

INF04 Implement integrated briefing *

ITY-ADQ Ensure quality of aeronautical data and aeronautical information [E] *

ITY-AGDL Initial ATC air-ground data link services above FL-285 [IDP] [E] *

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

ITY-COTR Implementation of ground-ground automated co-ordination processes [E] *

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

ITY-SPI Surveillance performance and interoperability *

NAV03 Implementation of P-RNAV [E] *

NAV10 Implement APV procedures [IDP] [E] *

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

SAF11 Improve runway safety by preventing runway excursions *

SRC-CHNG Implementation of Safety Oversight of Changes to ATM by National Supervisory Authorities (NSA) *

SRC-RLMK Implement the EUROCONTROL Safety Regulatory Requirements (ESARRs) *

SRC-SLRD Safety Levels and Resolution of Deficiencies *


Airport-related ESSIP Objectives

<=

2007

20

08

2009

20

10

2011

20

12

2013

20

14

2015

20

16

2017

20

18

2019

20

20

UDYZ-Yerevan

AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual

*

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

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

AOP05 Implement Airport Collaborative Decision Making (CDM) [IDP] [E] *

ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements [IDP] *

ENV02 Implement Collaborative Environmental Management (CEM) at Airports *

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.

Understanding the Table

Objective Completed No Plan

Objective Partly Completed Missing Data

Objective Planned Not Applicable (Armenia/Zvarnots Airport does not participate in this objective)

Late


Introduction

The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a five-year 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 2013 describes the situation in the State at the end of December 2013.

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

Chapters 1 to 5 present the key players in the State, and sets the institutional and geographical scenes to help the reader understand the specifics of the State and interpret the rest of the document correctly. It also presents a short description of the main national and regional projects in which the national Stakeholders are involved.

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.


Chapter 1 - National ATM Environment

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

European Common Aviation Area

EASA Working Arrangement Annex 1 ATM 2011

ICAO 18 June 1992

JAA 2004

NATO

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

ANSP Certification GDCA Government Order N744-N 19.06.2008 (Establishing procedure for granting permission of ANSP)

Safety Oversight GDCA GDCA GD Order N14-A 02.02.2010 (Safety oversight, audit process regulatory requirements)

Establishment of Tolerable Safety Levels

GDCA Aviation Law and the statute of GDCA

Safety Performance Monitoring GDCA Aviation Law and the statute of GDCA

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

GDCA Aviation Law and the statute of GDCA

Airspace GDCA / Ministry of Defence

Government Order N825-N 03.07.2003 (Airspace Management Regulation).

Economic GDCA 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)

Government

Director General General Department of

Civil Aviation

Administrative

Group

Council General Department of Civil

Aviation

Airworthiness

DepartmentDeputy Director

General Deputy Director

General

Aviation Security

Department

Airtransportation Regulation Department

Flight Operations Department

Consultant Of

Director General

Assistant Of

Director General

Accounting Section

Aerodromes

Certification and

ATM Department

Legal Section

General Section

Human Resources

Section


The roles and responsibilities of the civil and military authorities for airspace management are established by the relevant decision of the Government in accordance with the flexible use of airspace principles.

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)

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 GB. 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.1 ATM system in use

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

Major upgrade1 of the ATC system is performed: 2013

The new generation ATM system “Galaxy” was installed at Yerevan ATC centre which is deployed by the Russian company “AZIMUT. 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 are 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

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 scaleable 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.

1.2.2.2 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

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 serves 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.

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


“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

Yerevan “Zvartnots” International Airport is the only Armenian airport covered by the LSSIP Year 2013.

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

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 N 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


Oversight

1.2.4.2 Service Provision role

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 yet an EU member State.

1.2.4.3 User role

OAT GAT

National oversight body for OAT: 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

AIS N AIS NA

MET Y MET NA

SAR Y SAR Y

TSA/TRA monitoring Y FIS NA

Other: Other:

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:


1.2.4.4 Flexible Use of Airspace (FUA)

1.2.5 Accident/incident Investigation Body

1.2.5.1 Investigations

Investigations following accidents and/or incidents are carried out by the provisional flight safety inspection body, which is subordinated directly to the Director General of the GDCA, moreover in exceptional cases the Government can designate a special investigation committee.

The provisional flight safety inspection body is a public institution, it is not an autonomous decision making authority and it is settled as an independent body within the Civil Aviation System; therefore the objectivity of its dealings is assured as requested by Directive 94/56/EC.

To guarantee an independent position, the provisional flight safety inspection body has been put under the direct surveillance of the Authority of the Director General of GDCA different from the regulation Deputy Director of GDCA.

The provisional flight safety inspection body conducts investigations for Civil Aviation aircraft accidents and serious incidents. In case of non serious incidents they can task the service provider to conduct investigations on behalf of GDCA.

In the frame of ARMATS SMS, all ATM related incidents should be investigated by ARMATS internally and relevant corrective actions implemented.

1.2.5.2 Collection, Evaluation & Processing of Data

The service provider is tasked by the GDCA to collect, evaluate, process and store all ATM related information to civil aviation accidents, incidents and occurrences, as well as to make this information available to others.

The investigating bodies issue safety recommendations as appropriate (with the exclusion of accidents and incidents to State aircraft) following its investigations, and/or whenever deemed appropriate conducts studies and surveys aimed at increasing flight safety.

In order to carry out this function, TOKAI, the tool developed by EUROCONTROL, is used.

1.2.5.3 Civil-Military Accidents/Incidents

Investigation of accidents and/or incidents involving Civil and Military are conducted by a joint body composed by experts from the Military Flight Safety Department, the GDCA and ARMATS.

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

FUA Level 1 implemented: Y




Chapter 2 - En-route Traffic and Capacity

2.1 Evolution of traffic in Armenia

Armenia - Annual IFR Movements

0

10000

20000

30000

40000

50000

60000

70000

80000

90000

100000

2009 A 2010 A 2011 A 2012 A 2013 F 2014 F 2015 F 2016 F 2017 F 2018 F 2019 F

IFR

flig

hts

IFR movements - Actuals

IFR movements - Baseline forecast

IFR movements - High forecast

IFR movements - Low forecast

Armenia - Distribution (Ref. year 2012)

International Dep/Arr

39%

Domestic flights 0%

Overflights 61%

A = ActualF = Forecast

2010 A 2011 A 2012 A 2013 F 2014 F 2015 F 2016 F 2017 F 2018 F 2019 FH -4,3% 13,9% 8,4% 7,9% 7,3% 7,6% 7,5%B 9,3% 8,1% -2,0% -5,0% 11,8% 6,2% 6,2% 5,5% 5,8% 5,7%L -5,6% 9,8% 4,3% 4,6% 4,0% 4,2% 4,1%

ESRA B 0,8% 3,1% -2,4% -0,9% 1,4% 2,6% 2,7% 2,2% 2,5% 2,5%

STATFOR Medium-Term Forecast (September 2013)IFR flights yearly growth

Armenia

2013 En-route traffic in Armenia decreased by 7.1% during Summer 2013 (May to October inclusive), when compared to Summer 2012.

2014-2018/19

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

2.2 YEREVAN ACC

2.2.1 Summer 2013 performance

Traffic Evolution 2013 Capacity Baseline

En-route Delay (min/flight) Capacity

gap Optimum All reasons Without weather

-8.4% 25 (0%) 0 0 0 No

Capacity Plan : Sufficient Capacity to meet demand Comments

Summer 2013 performance assessment

The ACC capacity baseline was measured with ACCESS. During the measured period, the average peak 1 hour demand was 12 and the average peak 3 hour demand was 9.

2.2.2 Planning Period 2014-2018/19 - 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.

The 2014-2018/19 summer capacity profile and delay breakdown has been derived according to the


following parameters: 2014: capacity requirement profiles based on the delay breakdown per ACC as provided in January

2011 2015-2018/19: Reference value based on the breakdown of a yearly European delay target of 0.5

min/flight

2014 2015 2016 2017 2018 20190.06 0.01 0.01 0.01 0.01 0.010.09 0.01 0.01 0.01 0.01 0.01

En-route ATFM delay breakdown - Reference Values

AnnualSummer

UDDDCTA

H 25 0% 25 0% 25 0% 25 0% 25 0% 27 8%Ref. 25 0% 25 0% 25 0% 25 0% 25 0% 25 0%

L 25 0% 25 0% 25 0% 25 0% 25 0% 25 0%C/R 25 0% 25 0% 25 0% 26 4% 26 0% 26 0%

2017 20182015 2016ACC

2013 baseline 2014

UDDD 25

2019

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

Capacity Plan

Year 2014 2015 2016 2017 2018 2019

Measures planned

Max sectors 1 1 1 1 1 1

Capacity increase p.a.

Sufficient capacity to meet expected demand

Reference profile (ACC)

0% 0% 0% 0% 0% 0%

Additional information

UDDDCTA - Reference capacity profile and alternative scenarios

0

5

10

15

20

25

30

Cap

acit

y p

rofi

le (

mo

vem

ents

per

ho

ur)

2014-2019 Reference Capacity Profile 25 25 25 25 25 25

Capacity Profile - Current Routes 25 25 25 26 26 26

Capacity Profile - High 25 25 25 25 25 27

Capacity Profile - Low 25 25 25 25 25 25

Capacity Baseline 25 25

2014 - 2019 Plan 25 25 25 25 25 27

2012 2013 2014 2015 2016 2017 2018 2019

More information on the methodology related to capacity planning is available at :

http://www.eurocontrol.int/sites/default/files/content/documents/nm/network‐operations/capacity‐assessment‐planning‐guidance‐doc‐v2.8final.pdf


Chapter 3 - ESSIP Report recommendations

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

Number Recommendation Ownership

REC-2012-03 To ensure that all Stakeholders report the expected completion dates as defined in their National business plans.

All States

Reply by AM Completion dates reported in the LSSIP are fully aligned with the National Business Plan 2014-2018.

REC-2012-05 To ensure correct application of LSSIP guidance material and to implement the results of mandatory LSSIP in-cycle check.

All States

Reply by AM The LSSIP guidance material is fully applied and the results of the in-cycle check have been fully implemented.

REC-2012-10 To ensure actions for overcoming present delays in the implementation of basic ATSMHS capability (ESSIP objective COM10).

AL, AM, AZ, CY, CZ, DK, EE, FI, FR, GR, HR, HU, IT, LU, MAS, MD, MT, NO, SE,

SI, UA

Reply by AM Armenia will implement ATSMHS in 2015.

REC-2012-11 States to ensure that appropriate actions are taken for overcoming present delays in the implementation of priority capabilities specified in the ESSIP objective FCM03.

BE, UK, SE, NO, FI, LV, PL, HU, UA, AM, TR, MK, FR, PT, MT, RO, HR, BA, AL,

SI, IT, CZ, MAS, CY.

Reply by AM Priority capabilities of FCM03 have been implemented in the new ATM system put inservice in 2013.

REC-2012-22 States are encouraged to speed up the AFP implementation and to schedule AFP testing with Network Manager.

All States

Reply by AM AFP has been implemented in the new ATM system put in service in 2013.

REC-2012-40 ANSPs are encouraged to publish more APV routes.

All ECAC ANSPs

Reply by AM APV Routes already published for Zvartnots International Airport


Chapter 4 - National Projects

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

Name Schedule Description – Scope Status Link with European Master Plan.

Expected Contribution to the Key Performance Areas2

P3D Expansion and Upgrade

From: Mar 2014

To: Dec 2015

Expansion of the infrastructure over the whole territory using new additional receiving stations. Upgrade the architecture of the current two WAM systems by changing it from CT (central timing) to DT (distributed timing) .

Planned ITY-SPI Capacity and safety improvement

ATIS From: Jan 2014

To: Dec 2014

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

Planned OI Step IS-0401 Safety improvement

AMHS From: Jan 2015

To: Dec 2015

Procurement and installation of AMHS system. Planned COM 10 Cost-efficiency and safety improvement

CPDLC From: Jan 2014

To: Dec 2015

Implementation of CPDLC Started ITY-AGDL Capacity and safety improvement

NAV Rationalisation

From: Jan 2016

To: Dec 2017

Rationalisation of the navigation infrastructure. Installation of new DMEs.

Installation at the airport a new D-VOR / DME.

Planned Enabler CTE-N5a Cost-efficiency improvement

ATC technical system

From: Sep 2012

To: Apr 2014

“Aeronautical Data Set for ATC System Using EAD Database” document and catalogue preparation.

Started OI Step IS-0204 Safety and cost-efficiency improvement

QMS From: Jan 2014 to Dec 2016

Activation of the implemented quality management system, which will allow to have fully regulated documentation and change management and safety assessment procedures.

Planned ITY-ADQ Safety and cost-efficiency improvement

AIS From: Sep 2014

To: Dec 2017

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


AIS From: Sep 2014

To: Apr 2017

Monitoring of quality and completeness of the digital aeronautical data.


AIS From: Sep 2014

To: Apr 2017

Creation and maintenance of the digital data for charting Planned ITY-ADQ Safety and cost-efficiency improvement

2 Capacity, safety, cost-efficiency and environment – as defined in Recital 2 of Regulation (EU) No 691/2010.


Chapter 5 - Regional Co-ordination

5.1 Regional coordination projects

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.


Chapter 6 - ESSIP Objective Implementation

Conventions

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

o one 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


AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling (By:12/2018)

[IDP]

[Essential]

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 2014/2015.Objective will be reviewed after the conformance analysis.

‐

REG (By:12-2018)

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 2014/2015. Objective will be reviewed after the conformance analysis.

No Plan

‐

ASP (By:12-2018)


No Plan

‐

MIL (By:12-2018)


No Plan

‐

AOM19 Implement Advanced Airspace Management (By:12/2016)

[IDP]

[Essential] Planned

There is flexible use of airspace based on procedures. The implementation of an automated system is under consideration, will be addressed after 2014.

12/2015

ASP (By:12-2015)


Planned

12/2015

MIL (By:12-2015)


Planned

12/2015

AOM20 Implement ATS Route Network (ARN) - Version 7 (By:10/2013)

[Essential] Completed

Armenia is involved in RNDSG. ARN version 7 has been implemented. 10/2013

ASP (By:10-2013)

The airspace structure change (route/sector and terminal airspace) is the responsibility of ARMATS.

Completed

10/2013

MIL (By:10-2013)

The airspace structure change (route/sector and terminal airspace) is the responsibility of ARMATS; done through collaboration with Military authorities.

Completed

10/2013

AOM21 Implementation of Free Route Airspace (By:12/2017) (Outside Applicability Area)

[IDP]

[Essential]

Not Applicable

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

REG (By:12-2017) Armenia is not in the applicability area of the objective.

Not Applicable

‐

ASP (By:12-2017) Armenia is not in the applicability area of the objective.

Not Applicable

‐

MIL (By:12-2017) Armenia is not in the applicability area of the objective.

Not Applicable

‐


AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual (By:12/2013)

Not Applicable

UDYZ - Yerevan

(Outside Applicability Area)

Armenia is not part of the applicability area. No airport capacity problem foreseen within the timeframe covered by present LSSIP.

‐

ASP (By:12-2011)

No airport capacity problem foreseen within the timeframe covered by the present LSSIP.Armenia is not part of the applicability area.

Not Applicable

‐

APO (By:12-2011)

No airport capacity problem foreseen within the timeframe covered by the present LSSIP.Armenia is not part of the applicability area.

Not Applicable

‐

AOP03 Improve runway safety by preventing runway incursions (By:12/2013)

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, the ANSP ARMATS and the major aircraft operator. 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.

12/2013

REG (By:12-2013)

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

Completed

12/2013

ASP (By:12-2013)

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

Completed

12/2013

MIL (By:12-2013)

Military authorities do not provide ATC service to civil flights.Military flights operate as GAT on Zvarnots airport.

Not Applicable

‐

APO (By:12-2013)

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

Completed

12/2013


AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1 (By:12/2011)

[Essential]

Not Applicable

UDYZ - Yerevan


UDYZ is not 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. There is in average 20 days of bad visibility per year.

‐

REG (By:12-2010)

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) There is in average 20 days per year of bad visibility.

Not Applicable

‐

MIL (By:12-2010) Military airports do not provide ATC service to civil flights.

Not Applicable

‐

APO (By:12-2010)

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

Not Applicable

12/2015

AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2 (By:12/2017)

Not Applicable

UDYZ - Yerevan


Armenia is not part of the applicability area. In average per year bad visibility is about 20 days for CAT II conditions and less than 10 days for CAT III conditions.

‐

REG (By:12-2017)

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

Not Applicable

‐

ASP (By:12-2017)


Not Applicable

‐

APO (By:12-2017)


Not Applicable

‐

AOP05 Implement Airport Collaborative Decision Making (CDM) (By:01/2016)

[IDP]

[Essential]

Not Applicable

UDYZ - Yerevan


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:01-2016) Armenia is not part of the applicability area.

Not Applicable

‐

MIL (By:01-2016) Military airports do not provide service to civil flights.

Not Applicable

‐

APO (By:01-2016) Armenia is not part of the applicability area.

Not Applicable

‐


ATC02.2 Implement ground based safety nets - Short Term Conflict Alert (STCA) - level 2 (By:01/2013)


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

12/2013

REG (By:01-2013) GDCA has verified the new system.

Completed

12/2013

ASP (By:01-2013)

In Yerevan FIR, the ATM system ‐Galaxy‐ has the STCA level 2 implemented and operational.

Completed

12/2013

MIL (By:01-2013)

Military ATC units do not provide area radar services. They do not provide ATC service to Civil flights.

Not Applicable

‐

ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2 (By:12/2016)


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.

12/2013

ASP (By:12-2016) ARMATS has installed the ATM system with APW level 2 capability.

Completed

12/2013

MIL (By:12-2016) Military do not provide air traffic service to civil flights.

Not Applicable

‐

ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2 (By:12/2016)


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

12/2013

ASP (By:12-2016) ARMATS has installed the new ATM system with MSAW level 2 capability.

Completed

12/2013


Not Applicable

‐

ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2 (By:12/2016)


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

ASP (By:12-2016) ARMATS has installed the ATM system with APM level 2 capability.

Completed

12/2013


Not Applicable

‐


ATC07.1 Implement arrival management tools (By:12/2015) (Outside Applicability Area)

[Essential]

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) Armenia is not part of the applicability area.

Not Applicable

‐

ATC12 Implement automated support for conflict detection and conformance monitoring (By:12/2016)


The ATM system ‐Galaxy‐ has the MTCD and MONA functions implemented and operational. 12/2013

REG (By:12-2016)

The new ATM system has the MTCD and MONA functions implemented and operational

Completed

06/2013

ASP (By:12-2016)

ARMATS has installed the new ATM system and implemented the MTCD and MONA functions.

Completed

12/2013

ATC15

Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations (By:12/2017) (Outside Applicability Area)

[IDP]

[Essential]

Not Applicable

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

REG (By:12-2017)

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

Not Applicable

‐

ASP (By:12-2017)

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 (By:12/2015)

Planned

It will be implemented in due time. For more details, see the comments at Stakeholder level. 12/2014

REG (By:12-2015) Will be implemented in due time.

Planned

12/2014

ASP (By:03-2012) It is implemented.

Completed

01/2012

MIL (By:12-2015) Not applicable as the retrofit is not justified in term of benefits.

Not Applicable

‐


ATC17 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer (By:12/2018)

[IDP]

[Essential] Planned

The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since 2013.

01/2015

REG (By:12-2018) ‐

Planned

01/2015

ASP (By:12-2018)

The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since 2013.

Planned

01/2015

COM09 Migrate ground international or regional X.25 data networks or services to the Internet Protocol (IP) (By:12/2014)

[IDP]

Partly Completed

The current network is based on IP v4. There is a plan to upgrade to IP v6. The new ATC system has the capability of IP v6.

12/2014

REG (By:12-2010)

The GDCA notified ARMATS of the mandate to migrate to IP v6.Once the IPv6 will be implemented the GDCA will conduct the oversight.

Completed

12/2010

ASP (By:12-2014) The new ATC system has the capability of IP v6.

Partly

Completed

12/2014

MIL (By:12-2014) Military do not provide ATC service to civil flights

Not Applicable

‐

COM10 Migrate from AFTN to AMHS (By:12/2014)

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).

12/2015

ASP (By:12-2014) ARMATS will upgrade the COM centre to implement AMHS.

Late

12/2015

MIL (By:12-2014) Military authorities do not control Civil flights.

Not Applicable

‐

COM11 Implementation of Voice over Internet Protocol (VoIP) in ATM (By:12/2020)

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.

12/2015

REG (By:12-2018) The ARMATS new VCS system has capability to use Voice over IP.

Completed

12/2013

ASP (By:12-2020) The ARMATS new VCS system has capability to use Voice over IP.

Partly

Completed

12/2015

MIL (By:12-2020) Military do not provide ATC service to Civil flights

Not Applicable

‐


ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements (By:12/2013)

[IDP]

Completed

UDYZ - Yerevan


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.

12/2009

ASP (By:12-2013) BCDA procedures are applied in Armenia.

Completed

12/2009

APO (By:12-2013) BCDA procedures are applied in Armenia.

Completed

12/2009

ENV02 Implement Collaborative Environmental Management (CEM) at Airports (By:12/2016)

Completed

UDYZ - Yerevan

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 does 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.

12/2009

ASP (By:12-2016)

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

12/2009

MIL (By:12-2015) Military airports do not provide ATC service to civil flights.

Not Applicable

‐

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

12/2009

FCM01 Implement enhanced tactical flow management services (By:12/2006)

[Essential] Late

Armenia is in the IFPS Zone. The ATC system is not connected to CFMU. The new system will have all the required connections with CFMU.

12/2014

ASP (By:12-2006)

Armenia migrated to the IFPS Zone on the 21 December 2006.The new system will have all the required connections with CFMU.

Late

12/2014


Not Applicable

‐


FCM03 Implement collaborative flight planning (By:12/2015) [IDP]

[Essential] 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 new system will have all the required connections with CFMU.

12/2014

ASP (By:12-2015) The new system will have all the required connections with CFMU.

Planned

Modernisation of YEREVAN

ACC 12/2014


Not Applicable

‐

FCM04 Implementation of Short Term ATFCM Measures - phase 1 (By:12/2015) (Outside Applicability Area)

[IDP]

[Essential]

Not Applicable



Not Applicable

‐


Not Applicable

‐

FCM05 Implementation of interactive rolling NOP (By:12/2016) [IDP]

[Essential] No Plan

Objective not yet reviewed ‐

REG (By:12-2016) ‐

No Plan

‐

ASP (By:12-2016) ‐

No Plan

‐

MIL (By:12-2016) ‐

No Plan

‐

APO (By:12-2016) ‐

No Plan

‐

INF04 Implement integrated briefing (By:12/2012)

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.

01/2007

ASP (By:12-2012) The integrated briefing level 5 is implemented.

Completed

01/2007

MIL (By:12-2012)

There is only one AIS office in Armenia which is managed by ARMATS. Military are clients of this office.

Not Applicable

‐


ITY-ADQ

Ensure quality of aeronautical data and aeronautical information (By:07/2017) (Outside Applicability Area)

[Essential] Planned

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.

12/2016

REG (By:07-2017)

The regulator is adopting required documentations for the implementation of ADQ

Planned

12/2016

ASP (By:07-2017)

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

Planned

12/2016

MIL (By:07-2017)

There is only one AIS office in Armenia which is managed by ARMATS. Military are clients of this office.

Not Applicable

‐

APO (By:07-2017) Airport has quality management system, and is implementing ADQ

Planned

12/2016

ITY-AGDL

Initial ATC air-ground data link services above FL-285 (By:02/2015) (Outside Applicability Area)

[IDP]

[Essential] Planned

Armenia is not in the applicability area of the objective. However, the ‐Galaxy‐ ATM system installed In Yerevan ATC centre, has the capability. The testing is planned in 2014. The operational use remains dependent on the neighbouring ACCs‐ capabilities.

02/2015

REG (By:02-2015)

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

Planned

02/2015

ASP (By:02-2015) ARMATS plans to implement Air/Ground data link services

Planned

02/2015

MIL (By:-)

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

Not Applicable

‐

ITY-AGVCS2

Implement air-ground voice channel spacing requirements below FL195 (By:12/2020) (Outside Applicability Area)

Not Applicable



Not Applicable

‐


Not Applicable

‐

MIL (By:12-2020) 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 (By:02/2015) (Outside Applicability Area)

[Essential]

Partly Completed

The new ‐Galaxy‐ ATM system has the capability. The operational use remains dependent on the neighbouring ACCs‐ capabilities. Currently, none of the neighbouring ACCs is capable.

12/2013

REG (By:12-2012) ‐

Completed

12/2013

ASP (By:02-2015)

The new ‐Galaxy‐ ATM system has the capability.The operational use remains dependent on the neighbouring ACCs‐ capabilities. Currently, none of the neighbouring ACCs is capable.

Partly

Completed

12/2013


Not Applicable

‐

ITY-FMTP Apply a common flight message transfer protocol (FMTP) (By:12/2014)

[IDP]

Partly Completed

The new Galaxy ATM system has the capability. Has to be addressed at regional level. The operational use remains dependent on the neighbouring ACCs‐ capabilities. Currently, none is capable. For the time being there are no firm plans for operational use.

12/2014

REG (By:12-2014) GDCA will exercise its role in due time.

Partly

Completed

12/2014

ASP (By:12-2014)

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

Partly

Completed

12/2014


Not Applicable

‐

ITY-SPI Surveillance performance and interoperability (By:12/2019) (Outside Applicability Area)

Not Applicable

The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002), MLAT (CAT‐034, CAT‐048) and ATC system by ASTERIX protocols with time stamping was implemented in 2008. The ASTERIX protocol CAT‐062 is implemented on the new ‐Galaxy‐ ATM system. The operational use remains dependent on the neighbouring ACCs‐ capabilities.

‐

REG (By:12-2013) ‐

Not Applicable

‐

ASP (By:02-2015)

The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002), MLAT (CAT‐034, CAT‐048) and ATC system by ASTERIX protocols with time stamping was implemented in 2008. The ASTERIX protocol CAT‐062 is implemented on the new ‐Galaxy‐ ATM system. The operational use remains dependent on the neighbouring ACCs‐ capabilities.

Not Applicable

‐

MIL (By:12-2019) Equipage of military fleet is not economically justified.

Not Applicable

‐


NAV03 Implementation of P-RNAV (By:12/2012)


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.

12/2012

REG (By:01-2005)

Navigation databases are only available from accredited suppliers with suitable quality assurance procedures in place.

Completed

12/2009

ASP (By:12-2012)

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.

Completed

AIP and eAIP of the Republic of

Armenia / Navigation Aids Modernisation

12/2012


Not Applicable

‐

NAV10 Implement APV procedures (By:12/2016) [IDP]


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.

12/2012

REG (By:04-2016)

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

Completed

03/2011

ASP (By:12-2016)

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.

Completed

12/2012

MIL (By:12-2016)

Military do not have any plan and agreements with Civil ANSP and Airports to use APV Baro‐VNAV operations

Not Applicable

‐

SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements (By:12/2011)

Completed

The European action plan is implemented. 12/2012

REG (By:12-2011) GDCA is involved in the development of the implementation plan.

Completed

12/2012

ASP (By:12-2011) All the applicable measures were implemented

Completed

12/2012

MIL (By:12-2011) Military are consulted.

Not Applicable

12/2012


SAF11 Improve runway safety by preventing runway excursions (By:01/2018)

No Plan

Still under consideration. No implementation plan defined yet. 01/2018

REG (By:01-2018) Still under consideration.

No Plan

01/2018

ASP (By:12-2014) Still under consideration.

No Plan

12/2014

MIL (By:01-2018) Military authorities do not provide ATC service to civil flights.

Not Applicable

‐

APO (By:12-2014) Still under consideration.

No Plan

12/2014

SRC-CHNG

Implementation of Safety Oversight of Changes to ATM by National Supervisory Authorities (NSA) (By:12/2010)

Completed

Implemented and amended in 2009. 12/2009

REG (By:12-2010)

Implemented and amended in 2009.GDCA: http://www.aviation.am

Completed

12/2009

MIL (By:12-2010)

Military do not provide ATM service to civil flights and military systems are not used for the provision of services by ARMATS.

Not Applicable

‐

SRC-RLMK

Implement the EUROCONTROL Safety Regulatory Requirements (ESARRs) (By:12/2010)

Completed

ESARRs are fully implemented at the exception of ESARR 6 that is only partially implemented. 12/2009

REG (By:12-2010)

The GDCA has implemented ESARRs by adopting / transposing into national law and ensures regular updates by introducing new amendments.

Completed

12/2009

MIL (By:12-2010) Military do not provide ATM service to civil flights

Not Applicable

‐

SRC-SLRD

Safety Levels and Resolution of Deficiencies (By:12/2010)

Completed

The mechanism to collect, evaluate process and store occurrences in aviation (including ATM) is implemented and operational but the Just Culture environment is not ensured.

12/2012

REG (By:12-2010)

National regulations have been formally promulgated / published to transpose ESARR 2 into the national legal order.The governmental order 1777 of Jan. 2004 has been enacted and is based on ICAO Annex 13. A national legislation containing detailed requirements of ESARR 2 has been completed and approved by the GDCA December 2004.

Completed

12/2012

MIL (By:12-2010) Military do not provide ATM service to civil flights Not Applicable


Annexes

Annex A – Specialists involved in the LSSIP Process

LSSIP Co-ordination (and Part – State Context)

LSSIP Focal Point for Armenia ARMATS Mr. Samvel BAGHDASARYAN

LSSIP Focal Point for Airports Zvartnots and Gyumri International Airports

Mr. Sergey NALBANDYAN

LSSIP Contact Person for Armenia EUROCONTROL Mr. Octavian CIOARA

Part - ESSIP Objective Implementation

ESSIP Objective

EUROCONTROL Objective Owners EUROCONTROL EIPR Objective Coordinator

National Stakeholder Specialist(s)

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

A. DYBOWSKA Mr. Arthur PAPOYAN

Mr. Sergey DANIELYAN

AOM19 G. ACAMPORA, O. MROWICKI



AOM20 R. BUCUROIU



AOM21 R. BUCUROIU



AOP01.2 P. ADAMSON

P. VRANJKOVIC Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN

AOP03 P. JOPPART, T. LICU


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


ATC02.2 B. BAKKER, S. DROZDOWSKI

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

ATC12 P. TERZIOSKI


ATC15 P. CONROY, P. TERZIOSKI


ATC16 S. DROZDOWSKI L. DELL’ORTO Mr. Samvel BAGHDASARYAN


ESSIP Objective

EUROCONTROL Objective Owners EUROCONTROL EIPR Objective Coordinator

National Stakeholder Specialist(s)

Mr. Aram TUNYAN

ATC17 S. MORTON

L. DELL’ORTO Mr. Samvel BAGHDASARYAN


COM09 L. POPESCU O. ALFARO Mr. Gevorg SIMONYAN

COM10 Y. EYUBOGLU A. KOKONA Mr. Gevorg SIMONYAN

COM11 L. POPESCU A. KOKONA Mr. Gevorg SIMONYAN

ENV01 P. ADAMSON

B. HILL Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN

ENV02 S. MAHONY, A. WATT

B. HILL Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN

FCM01 H. KOOLEN

O. CIOARA Mr. Galust Poghosyan Mr. Arthur PAPOYAN

FCM03 S. SMIDT


FCM04 M. RICHARD


FCM05 N. AGACDIKEN


INF04 P. MATERN A-P. FRANGOLHO Mr. Simon ASATRYAN

ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Mr. Simon ASATRYAN

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

ITY-AGVCS2 TBD

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 Mr. Partev MAMIKONYAN

SAF10 T. LICU I. FEIJT Mr. Aram TUNYAN

SAF11 S. LAWRENCE I. FEIJT Mr. Aram TUNYAN

SRC-CHNG M. DEBOECK A. DYBOWSKA Mr. Aram TUNYAN

SRC-RLMK M. DEBOECK A. DYBOWSKA Mr. Aram TUNYAN

SRC-SLRD M. DEBOECK A. DYBOWSKA 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)


ZVARTNOTS AND SHIRAK AIRPORTS ADMINISTRATION (AIA) - ORGANIZATION CHART

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

Shift Manager & Land Side (5) Safety 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

Local Single Sky ImPlementation (LSSIP) ARMENIA · Enforcement actions in case of non-compliance...

Documents

Transcript of Local Single Sky ImPlementation (LSSIP) ARMENIA · Enforcement actions in case of non-compliance...