EUROCONTROL
Local Single Sky ImPlementation (LSSIP) ARMENIA
Year 2015 - Level 1
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: Head of ATM SM [email protected] Service
LSSIP Contact Person - Octavian Cioara E-mail: Unit DPS/PEPR [email protected]
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 http://www.eurocontrol.int/articles/glossaries abbreviations 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 Request should be send to e-mail: [email protected] Armenian)
LSSIP Year 2015 Armenia Released Issue
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.
LSSIP Year 2015 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 Chapter 2 - Traffic and Capacity ...... 12 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 Chapter 3 - ESSIP Report recommendations ...... 15 Chapter 4 - National Projects ...... 16 Chapter 5 - Regional Co-ordination ...... 17 5.1 Regional cooperation ...... 17 Chapter 6 - ESSIP Objective Implementation ...... 18 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 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 Year 2015 Armenia 1 Released Issue
* FOC Date LSSIP 2015 - Armenia █ Planned implementation date (see legend at the bottom of the table)
State-related ESSIP Objectives 2015 2016 2010 2011 2012 2013 2014 2017 2018 2019 2020 2021 2022 <=2009 Harmonise Operational Air Traffic (OAT) and General Air AOM13.1 Traffic (GAT) handling *
AOM19 Implement Advanced Airspace Management * [PCP] AOM21.1 Implementation of Direct Routing [E] * [PCP] AOM21.2 Implement Free Route Airspace [E] *
AOP03 Improve runway safety by preventing runway incursions * Implement ground based safety nets - Area Proximity ATC02.5 Warning - level 2 * Implement ground based safety nets - Minimum Safe ATC02.6 Altitude Warning - level 2 * Implement ground based safety nets - Approach Path ATC02.7 Monitor - level 2 * Implement automated support for conflict detection, ATC12.1 resolution support information and conformance monitoring * Implement, in En-Route operations, information exchange
ATC15 mechanisms, tools and procedures in support of Basic
AMAN operations
ATC16 Implement ACAS II compliant with TCAS II change 7.1 * Electronic Dialogue as Automated Assistance to Controller ATC17 during Coordination and Transfer *
COM10 Migrate from AFTN to AMHS * Implementation of Voice over Internet Protocol (VoIP) in COM11 ATM *
FCM01 Implement enhanced tactical flow management services *
FCM03 Implement collaborative flight planning *
FCM04 Implementation of Short Term ATFCM Measures - phase 1
[PCP] FCM05 Implementation of interactive rolling NOP [E] * [PCP] FCM06 Traffic Complexity Assessment [E]
INF04 Implement integrated briefing *
INF07 Electronic Terrain and Obstacle Data (TOD) *
ITY-ACID Aircraft identification
Ensure quality of aeronautical data and aeronautical ITY-ADQ information
ITY-AGDL Initial ATC air-ground data link services above FL-285
Implement air-ground voice channel spacing requirements ITY-AGVCS2 below FL195 Implementation of ground-ground automated co-ordination ITY-COTR 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 * Implement measures to reduce the risk to aircraft SAF10 operations caused by airspace infringements *
SAF11 Improve runway safety by preventing runway excursions *
LSSIP Year 2015 Armenia 2 Released Issue Airport-related ESSIP Objectives 2015 2016 2010 2011 2012 2013 2014 2017 2018 2019 2020 2021 2022 <=2009 UDYZ-Yerevan Airport
Implement Advanced Surface Movement Guidance and AOP04.1 Control System (A-SMGCS) Level1 Implement Advanced Surface Movement Guidance and AOP04.2 Control System (A-SMGCS) Level 2
AOP05 Implement Airport Collaborative Decision Making (CDM)
[PCP] AOP10 Time Based Separation [E] [PCP] AOP11 Initial Airport Operations Plan [E] * Improve runway and airfield safety with ATC clearances [PCP] AOP12 monitoring [E]
ATC07.1 Implement AMAN tools and procedures
Implement Continuous Descent Operations (CDO) ENV01 techniques for environmental improvements * Implement Collaborative Environmental Management ENV02 (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.
LSSIP Year 2015 Armenia 3 Released Issue
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.
LSSIP Year 2015 Armenia 4 Released Issue
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 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.
LSSIP Year 2015 Armenia 5 Released Issue
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.
LSSIP Year 2015 Armenia 6 Released Issue 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 Legal Basis responsible 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- GDCA Aviation Law, Government Order N744-N 19.06.2008 compliance with safety regulatory (Establishing procedure for granting permission of requirements 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 Government of Armenia and Ministry of Finance Defence 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
LSSIP Year 2015 Armenia 7 Released Issue 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 N other State(s):
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))
LSSIP Year 2015 Armenia 8 Released Issue 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)
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.
LSSIP Year 2015 Armenia 9 Released Issue 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 Y Provision of service for GAT by the Military N by national legal provisions? governed by national legal provisions? Level of such legal provision: Aviation Law, Rules of the Level of such legal provision: NA Air and Air Force Regulations. Authority signing such legal provision: Minister of Authority signing such legal provision: NA Defence and Chief of Air Force 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 Additional Information: Military do not provide air traffic control in TSAs control service to GAT flights. Means used to inform airspace users (other than Means used to inform airspace users (other than military) about these provisions: 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
OAT GAT National oversight body for OAT: Ministry of Defence National Supervisory Authority (as per SES reg. Air Force 550/2004) for GAT services provided by the military: GDCA (there is no Military NSA). Additional information: nil Additional information: nil
1.2.4.2 Service Provision role
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
LSSIP Year 2015 Armenia 10 Released Issue 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
Military ANSP providing GAT NA If YES, since: Duration of the services SES certified? 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
IFR inside controlled airspace, Military aircraft OAT only N GAT only N Both OAT and GAT Y can fly?
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)
Military in Armenia applies FUA requirements as specified in the Regulation No 2150/2005: Y FUA Level 1 implemented: Y FUA Level 2 implemented: Y FUA Level 3 implemented: Y
LSSIP Year 2015 Armenia 11 Released Issue Chapter 2 - Traffic and Capacity
2.1 Evolution of traffic in Armenia
Armenia - Annual IFR Movements 80.000
70.000
60.000
50.000
40.000 IFR flights IFR IFR movements - Actuals 30.000
IFR movements - Baseline forecast 20.000 IFR movements - High forecast
10.000 IFR movements - Low forecast A = Actual F = Forecast 0 2011 A 2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F
EUROCONTROL Seven-Year Forecast (September 2015) IFR flights yearly growth 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% Armenia 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%
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
En-route Delay (min/flight) - Summer Capacity Traffic Evolution 2015 Capacity Baseline Ref value Actual gap -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.
LSSIP Year 2015 Armenia 12 Released Issue
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.
En-route ATFM delay breakdown - Reference Values UDDDCTA 2016 2017 2018 2019 Annual 0.01 0.01 0.01 0.01 Summer 0.01 0.01 0.01 0.01 Capacity Profiles 2015 Profiles (hourly movements and % increase over previous year) ACC baseline 2016 2017 2018 2019 H 40 0% 40 0% 40 0% 40 0% Ref. 40 0% 40 0% 40 0% 40 0% UDDD 40 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%
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 New ATS route Airspace 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
LSSIP Year 2015 Armenia 13 Released Issue UDDDCTA - Reference capacity profile and alternative scenarios 45
40
35 hour) 30 per
25 (movements 20 profile
15 Capacity 10
5
0 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
2016-2020 Planning Period Outlook No problems are foreseen for Yerevan ACC in the coming planning cycle.
LSSIP Year 2015 Armenia 14 Released Issue Chapter 3 - ESSIP Report recommendations
Recommendations issued from the ESSIP Report for 2014 applicable to Armenia for all items that require corrective actions and improvements.
Reference Recommendation 2014 Ownership number Local Stakeholders that declared delays in implementation of FCM01, AOP04.1, SAF10, INF04, NAV03, AOP03, ENV01, ITY- Local REC-2014-2 AGDL, ITY-ADQ, COM09, COM10, ITY-FMTP and ITY-COTR, to Stakeholders take corrective measures to reduce the implementation delays. 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.
LSSIP Year 2015 Armenia 15 Released Issue Chapter 4 - National Projects
The main projects currently ongoing in Armenia are depicted in the table below.
Organisations Name Code Description Implementation EATM Links Status Performance Cooperation Planning Contribution2 Activities ARMATS AMHS Procurement and installation From: Jan 2016 COM 10 Planned Cost-efficiency and of AMHS system. To: Dec 2016 safety improvement ARMATS Contingency Construction and equipping of From: Sep 2015 Other: EC Under Capacity: Seamless Regulation operational operation Room the new Contingency Room To: Feb 2016 outside airport location. 1035/2011 tests Safety: Improved safety ARMATS OLDI The agreement has been From: Jan 2016 ITY-COTR Started Capacity: Seamless With Georgia. operation signed and the testing has To: Dec 2016 ITY-FMTP been done for the Safety: Improved implementation of the basic safety OLDI via FMTP with Tbilisi FIR (North). The final connection is planned in 2016. ARMATS DVOR/DME Procurement of a new From: Jan 2016 NAV Planned Safety and cost- efficiency DVOR/DME and replacement To: Dec 2017 of the existing VOR/DME in improvement “Zvartnots” airport are planned. ARMATS (AIS) AIS Transition from aeronautical From: Sep 2014 ITY-ADQ Started Safety and cost- information service concept To: Dec 2017 efficiency (AIS) to aeronautical improvement information management concept (AIM) ARMATS (AIS) AIS There is a plan to purchase From: Jan 2016 ITY-ADQ Planned Safety improvement and maintain the aeronautical To: Dec 2017 database in a AIXM 5.1 format as well as update the software for generating eAIP. ARMATS Free Route Implementation of Free Route From: Jan 2016 AOM21.2 Planned Capacity and cost- Airspace, at night time as form To: Dec 2018 (with efficiency 2017 followed by 24H Free initial deployment Route in 2018. in 2017)
2 Capacity, safety, cost-efficiency and environment – as defined in recital 25 of Commission Implementing Regulation (EU) No 390/2013
LSSIP Year 2015 Armenia 16 Released Issue Chapter 5 - Regional Co-ordination
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.
LSSIP Year 2015 Armenia 17 Released Issue Chapter 6 - ESSIP Objective Implementation
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 APO. Progress (**) REG high level progress statement (By:mm-yyyy) APO Impl. Date ASP ASP. Progress (**) ASP high level progress statement (By:mm-yyyy) ASP Impl. Date MIL MIL. Progress (**) MIL high level progress statement (By:mm-yyyy) MIL Impl. Date APO APO. Progress (**) APO high level progress statement (By:mm-yyyy) 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
LSSIP Year 2015 Armenia 18 Released Issue 6.2 ESSIP Objectives Implementation progress
Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling
AOM13.1 Timescales: No Plan
Initial operational capability: 01/01/2012 Full operational capability: 31/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 ‐ 2016.Objective will be reviewed after the conformance analysis. REG (By:12/2018) No Plan GDCA ‐ ‐ ‐ There are established OAT/GAT handling rules and procedures; they are No Plan not based on EUROAT. Conformance analysis and possible amendments Mil. Authority ‐ of the existing rules/procedures will be addressed in 2016. Objective will ‐ be reviewed after the conformance analysis. ASP (By:12/2018) There are established OAT/GAT handling rules and procedures; they are No Plan not based on EUROAT. Conformance analysis and possible amendments Mil. Authority ‐ of the existing rules/procedures will be addressed in 2016. Objective will ‐ be reviewed after the conformance analysis. No Plan ARMATS ‐ ‐ ‐ MIL (By:12/2018) There are established OAT/GAT handling rules and procedures; they are No Plan not based on EUROAT. Conformance analysis and possible amendments Mil. Authority ‐ of the existing rules/procedures will be addressed in 2016. Objective will ‐ be reviewed after the conformance analysis.
Implement Advanced Airspace Management Timescales: AOM19 Not Applicable Initial operational capability: 01/01/2011 Full operational capability: 31/12/2016 ‐ There is flexible use of airspace based on procedures. ‐ ASP (By:12/2016) Not Applicable ARMATS There is flexible use of airspace based on procedures. ‐ ‐ The displaying position of the ATM ‐Galaxy‐ system is installed in military Not Applicable Mil. Authority ‐ authority in 2014. ‐
Implementation of Direct Routing Timescales: [PCP] AOM21.1 Not Applicable Initial Operational Capability: 01/01/2015 [Essential] Full Operational Capability: 31/12/2017 ‐ All ATS routes are direct in Armenian airspace and Armenia is going to implement full free route in 2017. ‐ ASP (By:12/2017) Not Applicable ARMATS All ATS routes are direct in Armenian airspace. ‐ ‐
LSSIP Year 2015 Armenia 19 Released Issue Implement Free Route Airspace Timescales: [PCP] AOM21.2 Planned Initial operational capability: 01/01/2015 [Essential] Full operational capability: 31/12/2021 ‐ Armenia plans to implement night time Free Route Airspace in 2017, followed by 24H Free Route Airspace 31/12/2017 in 2018. ASP (By:12/2021) Armenia plans to implement night time Free Route Airspace in 2017, Planned ARMATS Free Route followed by 24H Free Route Airspace in 2018. 31/12/2017
Improve runway safety by preventing runway incursions Timescales: AOP03 Completed Initial operational capability: 01/04/2003 Full operational capability: 31/12/2013 ‐ 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. 31/12/2013 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. REG (By:12/2013) GDCA has decided upon the strategy for implementation at Zvartnots Completed GDCA ‐ International Airport of specific actions contained in the EAPRI document. 31/12/2013 ASP (By:12/2013) Voice communications between the tower and drivers are not conducted Completed ARMATS ‐ in English. 31/12/2013 APO (By:12/2013) YEREVAN Completed The airport SMS is approved by the regulatory body and it is operational. Zvartnots ‐ Drivers on the runway do not speak English. Airport 31/12/2013
LSSIP Year 2015 Armenia 20 Released Issue
Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level1 AOP04.1 Not Applicable Timescales: ‐ 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) When the ANSP and the Airport have decided to implement an A‐SMGCS Not Applicable GDCA ‐ system, the regulator will take the required actions. ‐ ASP (By:12/2011) Not Applicable ARMATS There is in average 20 days per year of bad visibility. ‐ ‐ APO (By:12/2010) YEREVAN Not Applicable There is in average 20 days per year of bad visibility for CAT II conditions Zvartnots ‐ and less then 10 days per year for CAT III conditions. Airport 31/12/2015
Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level 2 AOP04.2 Not Applicable Timescales: ‐ not applicable ‐ UDYZ ‐ Yerevan Airport (Outside 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. 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) Due to the level of traffic, the deployment of A‐SMGCS Level 2 is not yet Not Applicable ARMATS justified therefore UDYZ is not considered to be within the applicability ‐ area of the objective. ‐ APO (By:12/2017) YEREVAN Not Applicable Armenia is not part of the applicability area; however, this objective is Zvartnots ‐ under review for its possible implementation. Airport ‐
LSSIP Year 2015 Armenia 21 Released Issue
Implement Airport Collaborative Decision Making (CDM)
AOP05 Timescales: Not Applicable
‐ not applicable ‐ UDYZ ‐ Yerevan Airport (Outside Applicability Area) 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) Not Applicable ARMATS Armenia is not part of the applicability area. ‐ ‐ APO (By:12/2016) YEREVAN Not Applicable Zvartnots Armenia is not part of the applicability area. ‐ Airport ‐
Time Based Separation [PCP] AOP10 Timescales: Not Applicable [Essential] ‐ not applicable ‐ UDYZ ‐ Yerevan Airport (Outside Applicability Area) 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) Not Applicable GDCA ‐ ‐ ‐ ASP (By:12/2023) Not Applicable ARMATS ‐ ‐ ‐
Initial Airport Operations Plan Timescales: [PCP] AOP11 No Plan Initial Operational Capability: 01/01/2015 [Essential] Full Operational Capability: 31/12/2021 UDYZ ‐ Yerevan Airport Objective not reviewed yet ‐ ASP (By:12/2021) No Plan ARMATS ‐ ‐ ‐ APO (By:12/2021) YEREVAN No Plan Zvartnots ‐ ‐ Airport ‐
LSSIP Year 2015 Armenia 22 Released Issue
Improve runway and airfield safety with ATC clearances monitoring [PCP] AOP12 Not Applicable Timescales: [Essential] ‐ not applicable ‐ UDYZ ‐ Yerevan Airport (Outside Applicability Area) 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) Not Applicable ARMATS ‐ ‐ ‐ APO (By:12/2020) YEREVAN Not Applicable Zvartnots ‐ ‐ Airport ‐
Implement ground based safety nets ‐ Area Proximity Warning ‐ level 2
ATC02.5 Timescales: Completed
Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016 ‐ The ATM system ‐Galaxy‐ has the APW level 2 implemented and operational in Yerevan ACC and Yerevan TMA. 31/12/2013 Implementation of procedures and training of controllers is done. ASP (By:12/2016) Completed ARMATS ARMATS has installed the ATM system with APW level 2 capability. ‐ 31/12/2013
Implement ground based safety nets ‐ Minimum Safe Altitude Warning ‐ level 2
ATC02.6 Timescales: Completed
Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016 ‐ The ATM system ‐Galaxy‐ has the Minimum Safe Altitude Warning level 2 implemented and operational in 31/12/2013 Yerevan ACC and Yerevan TMA. ASP (By:12/2016) Completed ARMATS ARMATS has installed the new ATM system with MSAW level 2 capability. ‐ 31/12/2013
Implement ground based safety nets ‐ Approach Path Monitor ‐ level 2
ATC02.7 Timescales: Completed
Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016 ‐ The ATM system ‐Galaxy‐ has the APM level 2 implemented and operational. 31/12/2013 ASP (By:12/2016) Completed ARMATS ARMATS has installed the ATM system with APM level 2 capability. ‐ 31/12/2013
LSSIP Year 2015 Armenia 23 Released Issue Implement AMAN tools and procedures
ATC07.1 Timescales: Not Applicable
‐ not applicable ‐ UDYZ ‐ Yerevan Airport (Outside Applicability Area) 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) Not Applicable ARMATS Armenia is not part of the applicability area. ‐ ‐
Implement automated support for conflict detection, resolution support information and conformance monitoring
ATC12.1 Timescales: Completed
Initial operational capability: 01/01/2015 Full operational capability: 31/12/2021 ‐ 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 31/12/2013 resolution (CORA). ASP (By:12/2021) The ATM system has the MTCD and MONA functions implemented and Completed operational. ARMATS ‐ Taking into account the low traffic level in Armenian airspace no need to 31/12/2013 implement the conflict resolution (CORA).
Implement, in En‐Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations ATC15 Not Applicable (Outside Applicability Area) Timescales: ‐ not applicable ‐ ‐ Taking into account the forecast traffic levels, no need to implement this Objective has been identified. ‐ ASP (By:12/2017) Taking into account the forecast traffic levels, no need to implement this Not Applicable ARMATS ‐ Objective has been identified. ‐
LSSIP Year 2015 Armenia 24 Released Issue
Implement ACAS II compliant with TCAS II change 7.1 Timescales: ATC16 Late Initial operational capability: 01/03/2012 Full operational capability: 31/12/2015 ‐ It will be implemented in 2016 according to ICAO Annex 6 and Annex 10. For more details, see the 31/12/2016 comments at Stakeholder level. REG (By:12/2015) Late GDCA Will be implemented in 2016 according to ICAO Annex 6 and Annex 10. ‐ 31/12/2016 ASP (By:03/2012) Completed ARMATS It is implemented. ‐ 31/01/2012 MIL (By:12/2015) Not applicable as the retrofit is not justified in term of benefits. The pilots Not Applicable Mil. Authority are trained and know what to expect from the equipped aircraft, if they ‐ fly in their vicinity. ‐
Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer
ATC17 Timescales: No Plan
Initial operational capability: 01/01/2013 Full operational capability: 31/12/2018 ‐ 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. 31/01/2017 Currently there are no precise plans with regard the implementation and the operational use of the messages covered by ATC17. ASP (By:12/2018) The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are No Plan implemented in the new ATC system since 2013. The agreement has been ARMATS 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 31/01/2017 2016.
Migrate from AFTN to AMHS Timescales: COM10 Late Initial operational capability: 01/12/2011 Full operational capability: 31/12/2014 ‐ 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 31/12/2016 connected MTA (Message Transfer Agent). ASP (By:12/2014) Late ARMATS ARMATS will upgrade the COM centre to implement AMHS. AMHS 31/12/2016
LSSIP Year 2015 Armenia 25 Released Issue
Implementation of Voice over Internet Protocol (VoIP) in ATM Timescales: Partly COM11 Initial operational capability: 01/01/2013 Completed Full operational capability: 31/12/2020 ‐ The new VCS system has capability to use Voice over IP. It will be used in case of the neighbour centres 31/12/2017 will have such capability. ASP (By:12/2020) Partly ARMATS The ARMATS new VCS system has capability to use Voice over IP. ‐ Completed 31/12/2017
Implement Continuous Descent Operations (CDO) techniques for environmental improvements
ENV01 Timescales: Completed
Initial operational capability: 01/07/2007 Full operational capability: 31/12/2013 UDYZ ‐ Yerevan Airport CDA is implemented for 24 hours. All airport arrivals are achieving a CDA profile. All airlines are applying CDA. There is no monitoring. 31/12/2009 All procedures including SIDs and STARs are designed aiming at minimising the environmental impact. CDA approaches are published in the AIP. ASP (By:12/2013) Completed ARMATS BCDA procedures are applied in Armenia. ‐ 31/12/2009 APO (By:12/2013) YEREVAN Completed Zvartnots BCDA procedures are applied in Armenia. ‐ Airport 31/12/2009
Implement Collaborative Environmental Management (CEM) at Airports ENV02 Completed Timescales: ‐ not applicable ‐ UDYZ ‐ Yerevan Airport (Outside Applicability Area) 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 31/12/2009 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. ASP (By:12/2016) ARMATS cooperates with the Airport and Aircraft Operators in order to Completed ARMATS facilitate a joint approach contributing to the minimisation of noise and ‐ gaseous emissions resulting from aircraft operations. 31/12/2009 APO (By:12/2016) YEREVAN The airport has an Environment Manager with clearly defined action plan. Completed Zvartnots The main task of the Environment unit is the noise abatement and airfield ‐ Airport fuel and emissions reduction. 31/12/2009
LSSIP Year 2015 Armenia 26 Released Issue
Implement enhanced tactical flow management services Timescales: FCM01 Completed Initial operational capability: 01/08/2001 Full operational capability: 31/12/2006 ‐ Armenia is in the IFPS Zone. The new ATC system is connected to the NM. The installation of the Entry 31/12/2015 Node was done in 2015.The FSA and CPR messages are sent to the NM. ASP (By:07/2014) Armenia migrated to the IFPS Zone on the 21 December 2006. Completed ARMATS 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. 31/12/2015
Implement collaborative flight planning Timescales: FCM03 Planned Initial operational capability: 01/01/2000 Full operational capability: 31/12/2017 ‐ Armenia is in the IFPS Zone. Currently the connection with CFMU is ensured through the FMP; the ATC system is not connected to 31/12/2016 CFMU. The processing of ADEXP format will be implemented after the installation of AMHS. ASP (By:12/2017) The processing of ADEXP format will be implemented after the Planned ARMATS ‐ installation of AMHS. 31/12/2016
Implementation of Short Term ATFCM Measures ‐ phase 1 (Outside Applicability Area) FCM04 Not Applicable Timescales: ‐ not applicable ‐ ‐ Armenia is not in the applicability area of the objective. ‐ ASP (By:12/2015) Not Applicable ARMATS Armenia is not in the applicability area of the objective. ‐ ‐
Implementation of interactive rolling NOP Timescales: [PCP] FCM05 Not Applicable Initial operational capability: 01/09/2013 [Essential] Full operational capability: 31/12/2021 ‐ 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) Not Applicable ARMATS ‐ ‐ ‐ Not Applicable Mil. Authority ‐ ‐ ‐ APO (By:12/2021) YEREVAN Not Applicable Zvartnots ‐ ‐ Airport ‐
LSSIP Year 2015 Armenia 27 Released Issue Traffic Complexity Assessment (Outside Applicability Area) [PCP] FCM06 Not Applicable Timescales: [Essential] ‐ not applicable ‐ ‐ 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) The ATM system has the Sector Load Monitor (with graphic presentation Not Applicable ARMATS for ACC, APP, and TWR and en‐ route TLM presentation) and Point TLM ‐ functions. ‐
Implement integrated briefing Timescales: INF04 Completed Initial operational capability: 01/07/2002 Full operational capability: 31/12/2012 ‐ The implementation of level 3 and 4 was done on time and it is operational; the level 5 is operational since January 2007. 31/01/2007 Terminal and Integrated Briefing function at international airports of Armenia are provided. It is also accessible through Internet as of March 2007. ASP (By:12/2012) Completed ARMATS The integrated briefing level 5 is implemented. ‐ 31/01/2007
Electronic Terrain and Obstacle Data (TOD) Timescales: INF07 Planned Initial operational capability: 01/11/2014 Full operational capability: 31/05/2018 ‐ The ATM system‐Galaxy‐ has the TOD implemented and operational in 15/11/2013. 30/11/2016 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. REG (By:05/2018) In accordance with ICAO requirements the TOD policy and Partly GDCA implementation programme is established. The state will establish the ‐ Completed regulatory framework procedures at the end of 2016. 30/11/2016 ASP (By:05/2018) Partly The Terrain Data and Obstacles for all Areas were published in Nov of ARMATS ‐ Completed 2015 according to ICAO Annex 15 and are used in ATM system. 30/11/2016 APO (By:05/2018) YEREVAN Partly The Terrain Data and Obstacle for all Areas were published in Nov of 2015 Zvartnots ‐ Completed according to ICAO Annex 15 and are used in ATM system. Airport 30/11/2016
LSSIP Year 2015 Armenia 28 Released Issue
Aircraft identification (Outside Applicability Area) ITY‐ACID Completed Timescales: ‐ not applicable ‐ ‐ Armenia is not part of the applicability area. Hoverer, the ATM system ‐Galaxy‐ has the aircraft 15/11/2013 identification implemented and operational. ASP (By:01/2020) ARMATS has implemented the aircraft identification using WAM and ADS‐ Completed ARMATS ‐ B. 15/11/2013
Ensure quality of aeronautical data and aeronautical information (Outside Applicability Area) ITY‐ADQ Planned Timescales: ‐ not applicable ‐ ‐ Armenia is outside the applicability area of the objective, 31/12/2016 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. REG (By:06/2017) The regulator is adopting required documentations for the Completed GDCA ‐ implementation of ADQ 31/12/2015 ASP (By:06/2017) ARMATS implemented end‐to‐end integrity of aeronautical data during Planned ARMATS 2009. AIS_1 / AIS_2 The implementation of ADQ has started. 31/12/2016 APO (By:06/2017) YEREVAN Planned Zvartnots Airport has quality management system, and is implementing ADQ ‐ Airport 31/12/2016
Initial ATC air‐ground data link services above FL‐285 (Outside Applicability Area) ITY‐AGDL Planned Timescales: ‐ not applicable ‐ ‐ 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 31/12/2017 communications service provider is not signed yet. The implementation is on hold pending clarification of the technical solutions. REG (By:02/2018) The GDCA will conduct oversight once the system is installed Planned GDCA ‐ REG02 has been delegated to EUROCONTROL. 31/12/2017 ASP (By:02/2018) ARMATS plans to implement Air/Ground data link services. The ‐Galaxy‐ Planned ARMATS ‐ ATM system installed In Yerevan ATC centre, has the data link capability. 31/12/2017 MIL (By:01/2019) There is no intention to equip the transport‐type State aircraft with data Not Applicable Mil. Authority ‐ link equipment ‐
LSSIP Year 2015 Armenia 29 Released Issue Implement 8,33 kHz air‐ground voice channel spacing below FL195
ITY‐AGVCS2 (Outside Applicability Area) Not Applicable
Timescales: ‐ not applicable ‐ ‐ Armenia is not in the applicability area of the objective. ‐ REG (By:12/2018) Not Applicable GDCA Armenia is not in the applicability area of the objective. ‐ ‐ ASP (By:12/2018) Not Applicable ARMATS Armenia is not in the applicability area of the objective. ‐ ‐ MIL (By:12/2020) Not Applicable Mil. Authority Armenia is not in the applicability area of the objective. ‐ ‐ APO (By:12/2018) YEREVAN Not Applicable Zvartnots Armenia is not in the applicability area of the objective. ‐ Airport ‐
Implementation of ground‐ground automated co‐ordination processes Partly ITY‐COTR (Outside Applicability Area) Completed Timescales: ‐ not applicable ‐ ‐ The new ‐Galaxy‐ ATM system has the capability. The operational use remains dependent on the neighbouring ACCs‐ capabilities. The agreement has been 31/12/2013 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. ASP (By:02/2018) The new ‐Galaxy‐ ATM system has the capability. Partly The operational use remains dependent on the neighbouring ACCs‐ Completed ARMATS capabilities. The agreement has been signed and the testing has been OLDI done for the implementation of the basic OLDI with Tbilisi FIR (North). 31/12/2013 The final connection is expected in 2016. MIL (By:12/2012) Not Applicable Mil. Authority Military do not provide ATC service to civil flights ‐ ‐
LSSIP Year 2015 Armenia 30 Released Issue
Apply a common flight message transfer protocol (FMTP) Timescales: Entry into force of regulation: 28/06/2007 Partly ITY‐FMTP 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 Completed Transitional arrangements: 31/12/2012 Transitional arrangements when bilaterally agreed between ANSPs: 31/12/2014 ‐ 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 31/12/2014 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. ASP (By:12/2014) Partly The new 'Galaxy' ATM system has the capability, yet it has to be ARMATS OLDI Completed implemented at regional level. 31/12/2014 MIL (By:12/2014) Not Applicable Mil. Authority Military do not provide ATC service to civil flights ‐ ‐
Surveillance performance and interoperability (Outside Applicability Area) Partly ITY‐SPI Timescales: Completed ‐ not applicable ‐ ‐ 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 31/12/2013 the period of 2008‐2015. The operational use remains dependent on the neighbouring ACCs‐ capabilities. REG (By:02/2015) Completed GDCA Done in the context of the deployment of the new ATM system. ‐ 31/12/2013 ASP (By:02/2015) The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002) and Partly MLAT (CAT‐19, CAT‐20, CAT‐21, CAT‐034, CAT‐048) with time stamping, P3D Completed ARMATS ATM system by ASTERIX protocols (CAT‐62) was implemented within the Expansion period of 2008‐2015. The operational use remains dependent on the and Upgrade 31/12/2013 neighbouring ACCs‐ capabilities. MIL (By:06/2020) Not Applicable Mil. Authority Equipage of military fleet is not economically justified. ‐ ‐
LSSIP Year 2015 Armenia 31 Released Issue
Implementation of P‐RNAV Timescales: NAV03 Completed Initial operational capability: 01/01/2001 Full operational capability: 31/12/2023 ‐ The implementation was done in 2012. In summer 2007, B‐RNAV was implemented in the upper airspace (Above FL 195) of Armenia. 31/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. ASP (By:12/2023) All co‐ordinates for the publication in the AIP are prepared in WGS‐84 Completed format, in line with the accuracy and integrity requirements specified in ARMATS DVOR/DME ICAO Annex 15. 31/12/2012 The implementation of P‐RNAV was completed in 2012.
Implement APV procedures Timescales: NAV10 Completed Initial operational capability: 01/06/2011 Full operational capability: 31/12/2016 ‐ The APV Baro‐VNAV procedures at Zvartnots airport is already implemented, the safety case was 31/12/2012 developed and submitted to NSA, the subsequent approval has been given. REG (By:04/2016) In 2011 the GDCA has published national regulatory APV procedures, and Completed GDCA ‐ approved APV safety case and APV operations. 31/03/2011 ASP (By:12/2016) The APV Baro‐VNAV procedures at Zvartnots airport is already Completed ARMATS implemented, the safety case was developed and submitted to NSA, the DVOR/DME subsequent approval has been given. 31/12/2012
Implement measures to reduce the risk to aircraft operations caused by airspace infringements
SAF10 Timescales: Completed
Initial operational capability: 01/06/2008 Full operational capability: 31/12/2011 ‐ The European action plan is implemented. 31/12/2012 REG (By:12/2011) Completed GDCA GDCA is involved in the development of the implementation plan. ‐ 31/12/2012 ASP (By:12/2011) Completed ARMATS All the applicable measures were implemented ‐ 31/12/2012 MIL (By:12/2011) Not Applicable Mil. Authority Military are consulted. ‐ 31/12/2012
LSSIP Year 2015 Armenia 32 Released Issue
Improve runway safety by preventing runway excursions Timescales: SAF11 Planned Initial operational capability: 01/09/2013 Full operational capability: 31/01/2018 ‐ The EAPPRE recommendations applicable to ARMATS and Zvartnots airport are implemented (RWY 31/01/2018 information, meteo data, AIP publications, ATS operations and so on). REG (By:01/2018) Planned GDCA Implementation planned. ‐ 31/01/2018 ASP (By:12/2014) The EAPPRE recommendations are implemented (RWY information, Completed ARMATS ‐ meteo data, AIP publications, ATS operations and so on). 31/12/2014 APO (By:12/2014) YEREVAN Completed Zvartnots The applicable EAPPRE recommendations are implemented ‐ Airport 31/12/2014
LSSIP Year 2015 Armenia 33 Released Issue
6.3 Alignment of PCP with ESSIP Objectives and related progress
LSSIP Year 2015 Armenia 34 Released Issue
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 Mr. Sergey NALBANDYAN International Airports 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 EUROCONTROL Objective Owners EUROCONTROL National Stakeholder Specialist(s) Objective PEPR Objective Coordinator
AOM13.1 R. BUCUROIU, O. MROWICKI, C. A. DYBOWSKA Mr. Arthur PAPOYAN LUCCIOLI, E. REUBER Mr. Sergey DANIELYAN AOM19 A. DYBOWSKA Mr. Arthur PAPOYAN G. ACAMPORA, O. MROWICKI Mr. Sergey DANIELYAN AOM21.1 A. DYBOWSKA Mr. Arthur PAPOYAN R. BUCUROIU Mr. Sergey DANIELYAN AOM21.2 A. DYBOWSKA Mr. Arthur PAPOYAN R. BUCUROIU Mr. Sergey DANIELYAN AOP03 P. VRANJKOVIC Mr. Sergey DANIELYAN T. LICU Mr. Sergey NALBANDYAN AOP04.1 P. VRANJKOVIC Mr. Gevorg SIMONYAN P. ADAMSON Mr. Sergey NALBANDYAN AOP04.2 P. VRANJKOVIC Mr. Gevorg SIMONYAN P. ADAMSON Mr. Sergey NALBANDYAN AOP05 P. VRANJKOVIC Mr. Sergey DANIELYAN P. ADAMSON Mr. Sergey NALBANDYAN AOP10 B. HILL Mr. Sergey DANIELYAN M. BIRENHEIDE Mr. Sergey NALBANDYAN AOP11 B. HILL Mr. Sergey DANIELYAN M. BIRENHEIDE Mr. Sergey NALBANDYAN AOP12 P. VRANJKOVIC Mr. Sergey DANIELYAN M. BIRENHEIDE Mr. Sergey NALBANDYAN ATC02.5 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Sergey DANIELYAN ATC02.6 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Sergey DANIELYAN ATC02.7 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Harutyun BABAYAN ATC07.1 L. DELL’ORTO Mr. Samvel BAGHDASARYAN P. CONROY, P. TERZIOSKI Mr. Sergey DANIELYAN
LSSIP Year 2015 Armenia 35 Released Issue ESSIP EUROCONTROL Objective Owners EUROCONTROL National Stakeholder Specialist(s) Objective PEPR Objective Coordinator ATC12.1 L. DELL’ORTO Mr. Samvel BAGHDASARYAN P. TERZIOSKI Mr. Sergey DANIELYAN ATC15 L. DELL’ORTO Mr. Samvel BAGHDASARYAN P. CONROY, P. TERZIOSKI Mr. Sergey DANIELYAN ATC16 L. DELL’ORTO Mr. Samvel BAGHDASARYAN S. DROZDOWSKI Mr. Aram TUNYAN ATC17 L. DELL’ORTO Mr. Samvel BAGHDASARYAN S. MORTON Mr. Sergey DANIELYAN COM10 Y. EYUBOGLU A. KOKONA Mr. Gevorg SIMONYAN COM11 L. POPESCU A. KOKONA Mr. Gevorg SIMONYAN ENV01 B. HILL Mr. Sergey DANIELYAN C. FABER Mr. Sergey NALBANDYAN ENV02 B. HILL Mr. Sergey DANIELYAN S. MAHONY, A. WATT Mr. Sergey NALBANDYAN FCM01 O. CIOARA Mr. Sergey DANIELYAN H. KOOLEN Mr. Arthur PAPOYAN FCM03 O. CIOARA Mr. Sergey DANIELYAN TBD Mr. Arthur PAPOYAN FCM04 O. CIOARA Mr. Sergey DANIELYAN P. HOP Mr. Arthur PAPOYAN FCM05 O. CIOARA Mr. Sergey DANIELYAN I. MENDES Mr. Arthur PAPOYAN FCM06 O. ALFARO Mr. Sergey DANIELYAN P. HOP Mr. Arthur PAPOYAN INF04 P. MATERN A-P. FRANGOLHO Mr. Gevorg HARUTYUNYAN INF07 A-P. FRANGOLHO Mr. Galust POGHOSYAN A. PETROVSKY 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 O. ALFARO Mr. Arthur PAPOYAN J POUZET 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 A. KOKONA Mr. Artur ALAVERDYAN F. PAVLICEVIC 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
LSSIP Year 2015 Armenia 36 Released Issue Annex B – National Stakeholders Organisation Charts
Aviation Joint Stock Companies
Aviation Training Centre Avia-Medical Centre ARMATS Air Operators
State Enterprise State Enterprise (ARM. Reg)
ARMATS
General meeting of Company Stakeholders
Management Board
General Director Collegial Executive Body
Director of Ground ATS Director Technical Director Financial Director Administration Handling and Audit Staff
Communication “Yerevan” ATC Accountancy Building and Legal Service Service Constructions Center Operation Navigation Service Financial Department Economical Aeronautical “Yerevan” ATC Service Information Service Tower Surveillance Service Aviation Security Department Planning and “Gyumri” ATC ATM Systems Procurement Flight Safety Tower Management Service Service Audit Department
ATS planning “Gyumri” ATS Transport Quality Department Management and Service Service Monitoring Department Auxiliary Power Supply Service Department Training Technical Monitoring Department Department
Operational Control IT Department Department
LSSIP Year 2015 Armenia 37 Released Issue ZVARTNOTS AND SHIRAK AIRPORTS ADMINISTRATION (AIA) - ORGANIZATION CHART
General Manager
Maintenance Manager (1) Operation Manager (1) Security Manager (1)
Safety & Quality Control Manager (1)
Ground Handling Manager (1) Training & License (1) Shift Manager & Land Side (5) Check in Manager (1) ()()( )
Resource Allocator (4) Radio Ground (4)
Ramp Control & Follow Me (8) Operative Information Office (5)
LSSIP Year 2015 Armenia 38 Released Issue Annex C – Glossary of Abbreviations
Specific abbreviations for Armenia:
AIA – Armenian International Airports ARMATS – Armenian Air Traffic Services GDCA – General Department of Civil Aviation
LSSIP Year 2015 Armenia 39 Released Issue