Local Single Sky ImPlementation (LSSIP) ARMENIA

Transcription

1 EUROCONTROL Local Single Sky ImPlementation (LSSIP) ARMENIA Year Level 1

2

3

4

5 Document Title LSSIP Year 2016 for Armenia Infocentre Reference 17/01/30/102 Date of Edition 24/03/2017 LSSIP Focal Point S.Baghdasaryan LSSIP Contact Person O. Cioara Status Released Intended for Agency Stakeholders Available in Reference Documents LSSIP Documents LSSIP Guidance Material Master Plan Level 3 Plan Edition 2016 Master Plan Level 3 Report Year 2015 European ATM Portal STATFOR Forecasts Acronyms and abbreviations National AIP National Performance Plan National Business Plan (In Armenian) and Request should be send to staff@armats.am Request should be send to staff@armats.am LSSIP Year 2016 Armenia Released Issue

6

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

8

9 CONTENTS Executive Summary... 1 Introduction... 4 Chapter 1 National ATM Environment Geographical Scope International Membership Geographical description of the FIR(s) Airspace Classification and Organisation National Stakeholders Civil Regulator(s) ARMATS (ANSP) Airports Military Authorities Chapter 2 Traffic and Capacity Evolution of traffic in Armenia YEREVAN ACC Summer2016performance Planning Period Summer Chapter 3 Master Plan Level 3 Implementation Report recommendations Chapter 4 National Projects Chapter 5 Regional Co-ordination Regional cooperation Regional Projects Chapter 6 Implementation Objectives Progress State View Overall Objective Implementation Objective Progress per SESAR Key Feature ICAO ASBU Implementation Detailed Objectives Implementation progress Annexes LSSIP Year 2016 Armenia Released Issue

10

11 Executive Summary National ATM Context In 2016 the following was done: - Procurement of a new DVOR/DME and replacement of the existing VOR/DME in Zvartnots airport. - 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 expected in Procurement, installation and testing of AMHS system. The final operation of the AMHS is planned in Construction and equipping of the new Contingency Room outside airport location. - Procurement and maintenance of the aeronautical database in the AIXM 5.1 format, as well as the software updates for generating eaip. - Full implementation of ICAO A37-11 resolution (PBN). Armenia plans to implement night time Free Route Airspace above FL285 in winter Traffic and Capacity Traffic in Armenia decreased by 3% during Summer 2016 (May to October inclusive), when compared to Summer 2015, indicating a slowdown of the decrease (from 13.9% in the previous reporting cycle). However, on medium term, the STATFOR medium-term forecast (MTF) predicts an average annual traffic growth between 4.7 % and 9.1% for the planning period ( ), with an average baseline growth of 6.8%. Implementation Objectives Overview Progress distribution for applicable Implementation Objectives 2; 10% Completed 2; 10% Ongoing 4; 20% 12; 60% Planned Late No Plan Missing Data Undefined LSSIP Year 2016 Armenia 1 Released Issue

12 In 2016 a number of objectives have been completed, in particular in the field of GAT/OAT harmonisation (Objective AOM13.1) as well as in the field of safety (ATC16). 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 Ongoing. It is expected that once Basic OLDI, over FMTP, will be implemented with Tbilisi FIR and used operationally (in 2017), these objectives to be turned into Completed. Progress per SESAR Phase The figure below shows the progress made so far in the implementation of the SESAR baseline and the PCP elements. The percentage is calculated as an average of the relevant objectives as shown in Chapter (PCP objectives are marked as such, the rest are considered SESAR baseline); note that three objectives AOM19.1, FCM05 and NAV03 are considered as both part of the SESAR baseline and PCP so their progress contributes to the percentage of both phases. The objectives declared Achieved in previous editions (up to, and including, ESSIP Edition ) are also taken into account for as long as they were linked to the Level 2 of the ATM Master Plan and implemented by the State. SESAR Baseline Implementation PCP Implementation % % Progress per SESAR Key Feature and Phase The figure below shows the progress made so far, per SESAR Key Feature, in the implementation of the SESAR baseline and the PCP elements. The percentages are calculated as an average, per Key Feature, of the same objectives as in the previous paragraph. Optimised ATM Network Services Advanced Air Traffic Services High Performing Airport Operations Enabling Aviation Infrastructure 99% 98% 100 % 89% 55% n/a n/a 21% LSSIP Year 2016 Armenia 2 Released Issue

13 ICAO ASBUs Progress Implementation The figure below shows the progress made so far in the implementation of the ICAO ASBUs for Block 0. The percentage is calculated as an average of the relevant Objectives contributing to each of the relevant ASBUs; this is explained in Chapter Block % LSSIP Year 2016 Armenia 3 Released Issue

14

15 Introduction The Local Single Sky ImPlementation (LSSIP) documents, as an integral part of the Master Plan (MP) Level 3 (L3) / LSSIP mechanism, constitute a short/medium term implementation plan containing ECAC States actions to achieve the Implementation Objectives as set out by the MP Level 3 and to improve the performance of their national ATM System. This LSSIP document describes the situation in the State at the end of December 2016, together with plans for the next years. Chapter 1 provides an overview of the ATM institutional arrangements within the State, the membership of the State in various international organisations, the organisational structure of the main ATM players - civil and military - and their responsibilities under the national legislation. In addition, an overview of the Airspace Organisation and Classification, the ATC Units, the ATM systems operated by the main ANSP are also provided; Chapter 2 provides a comprehensive picture of the situation of Air Traffic, Capacity and ATFM Delay per each ACC in the State. It shows the evolution of Air Traffic and Delay in the last five years and the forecast for the next five years. It gives also the achieved performance in terms of delay during the summer season period and the planned projects assumed to offer the required capacity which will match the foreseen traffic increase and keep the delay at the agreed performance level; Chapter 3 provides a set of recommendations extracted from the MP L3 Implementation Report 2015 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 the main ATM national projects which contribute directly to the implementation of the MP Operational Improvements and/or Enablers and Implementation Objectives. The description, timescale, progress made and expected contribution to the ATM Key Performance Areas are provided by the State 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 aggregated information at State level covering the overall level of implementation, implementation per SESAR Key Feature and implementation of ICAO ASBUs. In addition the highlevel information on progress and plans of each Implementation Objective is presented. The information for each Implementation Objective is presented in boxes giving a summary of the progress and plans of implementation for each Stakeholder. The conventions used are presented at the beginning of the section. Chapter 6.2 is completed with a separate document called LSSIP Level 2. This document consists of a set of tables organised in line with the list of Implementation Objectives. Each table contains all the actions planned by the four national stakeholders to achieve their respective Stakeholder Lines of Action (SLoAs) as established in the European ATM Master Plan L3 Implementation Plan Edition 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 2016 Armenia 4 Released Issue

16

17 Chapter 1 National ATM Environment 1.1. Geographical Scope 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 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. LSSIP Year 2016 Armenia 5 Released Issue

18 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 2016 Armenia 6 Released Issue

19 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 2016 Armenia 7 Released Issue

20 1.2.1 Civil Regulator(s) 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, Charter and structure of GDCA N202- N Safety Oversight GDCA Government Order N744-N (Establishing procedure for granting permission of ANSPs), GDCA DG order 238A/ Safety oversight of ANSPs. Enforcement actions in case of non-compliance with safety regulatory requirements GDCA Aviation Law, Government Order N744-N (Establishing procedure for granting permission of ANSP), GDCA GD order 238A/ Safety oversight of ANSP. Airspace GDCA Aviation Law and Government Order 825N Airspace management regulation Economic GDCA / Ministry of Economic Development and Investments Environment GDCA Aviation Law. Government of Armenia and Ministry of Economic Development and Investments Security GDCA Order N1307-N (Civil Aviation Security in Republic of Armenia). Accident investigation GDCA Government Order 1777N, 2003, Accident and Incident investigation, classification and registration manual. 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 (last update in 2015). 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. LSSIP Year 2016 Armenia 8 Released Issue

21 The ANSPs are institutionally separated from the GDCA. The ANSPs were certified by GDCA in 2013 according to the SES package requirements and continuously oversight is implemented. Further information is available on the GDCA web-site: Annual Report published: Y Further information is available on the following web-site: ARMATS (ANSP) Services provided Name of the ANSP: ARMATS Governance: Joint Stock Company Ownership: 100% State Services provided Y/N Comment ATC en-route Y ATC approach Y ATC Airport(s) Y AIS Y CNS Y MET N Provided by the Aviation Meteorological Centre, a Joint Stock Company reporting to the Ministry of Nature Protection ATCO training Y General and aviation English trainings in UK. Refresh trainings in Prague. Others Additional information: Provision of services in other State(s): N Annual Report published: Y This is the annual report covering yearly activities of the ANSP. Further information is available on the ARMATS web-site: ATC systems in use Main ANSP part of any technology alliance 1 N --- FDPS Specify the manufacturer of the ATC system currently in use: AZIMUT (Russian Company) Upgrade 2 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 1 Technology alliance is an alliance with another service provider for joint procurement of technology from a particular supplier (e.g. COOPANS alliance) 2 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40)) LSSIP Year 2016 Armenia 9 Released Issue

22 SDPS Specify the manufacturer of the ATC system currently in use: AZIMUT (Russian Company) Upgrade 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, SDPS and FDPS 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 FDP system uses real time data from SDPS instead of static FPL route to update aircraft trajectory. Safety Nets processing is compatible with EUROCONTROL Specification for Short Term Conflict Alert (STCA), Minimum Safe Altitude Warning (MSAW), Area Proximity Warning (APW) and Approach Path Monitor (APM). MONA, MTCD, flexible vector, possibility of OLDI with adjacent FIRs, CPDLC, separate QNH areas for flights below transition level, automated update of flight plans and sending of DEP, ARR messages to CFMU are also engaged in the system. The system is also interfaced with European Aeronautical Database EAD (AIXM). Controller Working Position provides an integrated representation of the air situation, combining actual surveillance sensor data and FPL information. Being ready scalable it can act as a separate working position directly interfacing with sensors (PSR, SSR, mode-s, ADS-B, MLAT, ADF, weather systems and AFTN network) or be a part of ATC system interfacing with SDPS and FDPS modules. GALAXY simulator is used as a back-up system as well. The new IP Voice Communication System (VCS) <MULTIFONO M800IP > (<S.I.T.T.I.> Company, Italy) was installed at Yerevan ATC centre. The radio and telephone VCS fully integrates new IP Network requirements and latest technological achievements with user-friendliness needs at Operator and Maintenance levels. The VCS system combines all up-to-date interfaces such as MFC R2; ATS QSIG; E1 QSIG; and VoIP. ATC Units The ATC units in the Armenian airspace, which are of concern to this LSSIP, are the following: ATC Unit Number of sectors Associated FIR(s) Remarks En-route TMA YEREVAN ACC 1 YEREVAN FIR 3 is the total number of sectors of YEREVAN APP 1 YEREVAN FIR Yerevan ATC (including TWR) Gyumri TWR 1 YEREVAN FIR LSSIP Year 2016 Armenia 10 Released Issue

23 1.2.3 Airports 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 International Airport in Gyumri, located at about 100 km northwest of Yerevan. Zvartnots and Shirak International Airports are certified by GDCA in accordance with ICAO standards. 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 and Shirak International Airports are operated by Armenia International Airports CJSC Company. Further information is available on the AIA web-site: Airport(s) covered by the LSSIP Referring to the List of Airports in the Annex E of the European ATM Master Plan Level 3 Implementation Plan Edition 2016, 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 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. LSSIP Year 2016 Armenia 11 Released Issue

24 Regulatory role Regulatory framework and rule-making OAT OAT and provision of service for OAT governed Y by national legal provisions? Level of such legal provision: Aviation Law, Rules of the Air and Air Force Regulations. Authority signing such legal provision: Minister of Defence and Chief of Air Force These provisions cover: Rules of the Air for OAT Y GAT Provision of service for GAT by the Military governed by national legal provisions? Level of such legal provision: NA Authority signing such legal provision: NA These provisions cover: Organisation of military ATS for OAT Y Organisation of military ATS for GAT NA OAT/GAT Coordination Y OAT/GAT Coordination Y ATCO Training Y ATCO Training NA ATCO Licensing Y ATCO Licensing NA ANSP Certification Y ANSP Certification NA ANSP Supervision Y ANSP Supervision NA Aircrew Training Y ESARR applicability NA Aircrew Licensing Y Additional Information: Military provides only flight control in TSAs Means used to inform airspace users (other than military) about these provisions: 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: National AIP Y National AIP Y National Military AIP NA National Military AIP NA EUROCONTROL eaip Y EUROCONTROL eaip Y Other: NA Other: NA N Oversight OAT National oversight body for OAT: Ministry of Defence Air Force Additional information: nil GAT 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 LSSIP Year 2016 Armenia 12 Released Issue

25 Service Provision role OAT GAT Services Provided: Services Provided: En-Route NA En-Route Y Approach/TMA NA Approach/TMA Y Airfield/TWR/GND NA Airfield/TWR/GND Y AIS NA AIS Y MET Y MET Y SAR Y SAR Y TSA/TRA monitoring Y FIS Y Other: Other: Additional Information: nil Additional Information: nil Military ANSP providing GAT services SES certified? Certificate issued by: Additional Information: Armenia is not an EU member State. NA If YES, since: Duration of the Certificate: If NO, is this fact reported to the EC in accordance with SES regulations? User role IFR inside controlled airspace, Military aircraft can fly? OAT only N GAT only Y Both OAT and GAT N 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: Flexible Use of Airspace (FUA) Military in Armenia applies FUA requirements as specified in the Regulation No 2150/2005: FUA Level 1 implemented: Y FUA Level 2 implemented: Y FUA Level 3 implemented: Y Y LSSIP Year 2016 Armenia 13 Released Issue

26 Chapter 2 Traffic and Capacity 2.1. Evolution of traffic in Armenia Armenia - Annual IFR Movements IFR flights IFR movements - Actuals IFR movements - Baseline forecast IFR movements - High forecast IFR movements - Low forecast 2012 A 2013 A 2014 A 2015 A 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F 2022 F A = Actual F = Forecast EUROCONTROL Seven-Year Forecast (September 2016) IFR flights yearly growth 2013 A 2014 A 2015 A 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F 2022 F H -6.8% 20.3% 6.5% 5.9% 6.8% 6.1% 6.3% Armenia B -6.6% -3.4% -16.5% -7.3% 17.5% 3.9% 4.0% 4.6% 4.2% 4.4% L -7.9% 14.8% 1.5% 2.3% 2.7% 2.3% 2.5% ECAC B -1.1% 1.7% 1.6% 2.7% 1.4% 2.1% 2.1% 2.4% 1.9% 2.1% 2016 Traffic in Armenia decreased by 3.0% during Summer 2016 (May to October inclusive), when compared to Summer The EUROCONTROL Seven-Year forecast predicts an average annual traffic growth between 4.7% and 9.1% for the planning period, with an average baseline growth of 6.8%. LSSIP Year 2016 Armenia 14 Released Issue

27 2.2. YEREVAN ACC Summer 2016 performance Traffic Evolution 2016 Capacity Baseline Enroute Delay (min/flight) Summer Ref value Actual Capacity gap +3% 40 (0%) No The average enroute delay per flight remained at zero in Summer Capacity Plan: Sufficient Capacity to meet demand Achieved Comments New ATS route P130 REBLOELSIV Yes Implemented 7/1/2016 Summer 2016 performance assessment The ACC capacity baseline was estimated at 40. During the measured period, the average peak 1 hour demand was 9 and the average peak 3 hour demand was Planning Period 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. Capacity Profiles ACC 2016 Profiles (hourly movements and % increase over previous baseline H 40 0% 40 0% 40 0% Ref. 40 0% 40 0% 40 0% UDDD 40 L 40 0% 40 0% 40 0% Open 40 0% 40 0% 40 0% C/R 40 0% 40 0% 40 0% Capacity Plan Free Route Airspace Night FRA 24H FRA Airspace Management Advanced FUA Airport & TMA Network Integration Cooperative Traffic Management Airspace Procedures Staffing Technical Capacity Significant Events Max sectors Planned Annual Capacity Increase Sufficient capacity to meet expected demand Reference Profile Annual % Increase 0% 0% 0% N/A N/A Difference Capacity Plan v. Reference Sufficient capacity to meet expected demand Profile Annual Reference Value (min) N/A N/A Summer reference value (min) N/A N/A Additional information LSSIP Year 2016 Armenia 15 Released Issue

28 Sectors available Summer 2017 WD Sectors available Summer 2017 WE :00 02:00 04:00 06:00 08:00 10:00 12:00 14:00 16:00 18:00 20:00 22:00 00:00 02:00 04:00 06:00 08:00 10:00 12:00 14:00 16:00 18:00 20:00 22:00 UDDDCTA - Reference capacity profile and alternative scenarios Capacity profile (movements per hour) Reference Capacity Profile Capacity Profile Shortest Routes (Open) Capacity Profile Current Routes Capacity Profile High Capacity Profile Low Capacity Baseline Plan Planning Period Outlook No problems are foreseen for Yerevan ACC in the coming planning cycle. LSSIP Year 2016 Armenia 16 Released Issue

29 Chapter 3 Master Plan Level 3 Implementation Report recommendations Recommendations issued from the European ATM Master Plan Level 3 Implementation Report 2015 applicable to Armeniafor all items that require corrective actions and improvements. Reference number REC-2015/1 Recommendation 2015 Operational stakeholders should ensure that the pace of implementation of pre-sesar elements is increased, or at least kept at the same level to ensure timely delivery of SESAR baseline. Ownership All operational stakeholders Corrective actions taken: Yes Description: Most of the pre-sesar elements are already implemented in Armenia or are not-applicable. The few remaining ones have been implemented in 2016 or are dependent on the capabilities of the systems of the neighbouring States REC-2015/2 Local Stakeholders that declared delays in implementation of AOM19, FCM04, ATC07.1, ATC15, NAV10, ENV01, AOP04.1, ITY-ADQ, ITY-FMTP, INF07, COM10to take corrective measures to reduce the implementation delays, or at least ensure that these delays are not increased. Local Stakeholders Corrective actions taken: Yes Description: 3 of these objectives (NAV10, ENV01 and SAF10), were already implemented at the beginning of the LSSIP cycle, 5 are not-applicable (AOM19, FCM04.1, ATC07.1, ATC15 and AOP04.1) while the remaining ones have been implemented in REC-2015/7 ANSPs should use the momentum created by PCP funding opportunities to secure and achieve full interoperability in line with Master Plan Level 1 vision. ANSPs benefiting from EU funding Corrective actions taken: No Description: Armenia is not within the coverage of the PCP Regulation and is not benefiting from EU funding. LSSIP Year 2016 Armenia 17 Released Issue

30 Chapter 4 National Projects The main projects currently ongoing in Armenia are depicted in the tables below. AIS_1 Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Sep 2014 To: Dec 2019 Status: Description: Link and references ATM MP links: started Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution Transition from aeronautical information service concept (AIS) to aeronautical information management concept (AIM) ITY-ADQ Safety: ++ - Environment: - Capacity: - Cost-efficiency: - Operational efficiency: - - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - - AIS_2 Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Jan 2016 To: Dec 2016 Status: Description: Link and references ATM MP links: Finalised Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution Procurement and maintenance of the aeronautical database in the AIXM 5.1 format, as well as the software updates for generating eaip were done. ITY-ADQ Safety: - Environment: - Capacity: - Cost-efficiency: - Operational efficiency: - - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - - LSSIP Year 2016 Armenia 18 Released Issue

31 AMHS Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Jan 2016 To: Dec 2017 Status: Description: Link and references ATM MP links: Started Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution Procurement, installation and testing of AMHS system. The final operation of the AMHS is planned in COM10 - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - Safety: ++ Benefits resulting from the application of a harmonised set of safety requirements Environment: - Capacity: - Cost-efficiency: +++ use of de-facto COTS messaging systems will reduce the cost of messaging services and support any kind of message format Operational efficiency: - - Contingency Room Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Sep 2015 To: Feb 2016 Status: Description: Link and references finalised ATM MP links: - Construction and equipping of the new Contingency Room outside airport location. Other links: EC Regulation 1035/2011 Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution Safety: Environment: - Capacity: Cost-efficiency: - Operational efficiency: - - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - Improved safety Seamless operation - LSSIP Year 2016 Armenia 19 Released Issue

32 DVOR/DME Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Jan 2016 To: Dec 2016 Status: Description: Link and references ATM MP links: Finalised Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution Procurement of a new DVOR/DME and replacement of the existing VOR/DME in Zvartnots airport was done. NAV03, NAV10 Safety: - Environment: - Capacity: - Cost-efficiency: - Operational efficiency: - - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - - Free Route Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Jan 2016 To: Dec 2018 (with initial deployment in 2017) Status: Description: Link and references ATM MP links: Started Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution Implementation of Free Route Airspace, at night time as form 2017 followed by 24H Free Route in AOM21.2 Safety: - Environment: - - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - Capacity: +++ Increased through the better airspace utilisation to enhance productivity and reduce controller workload Cost-efficiency: ++ Savings in route distances as well as better fuel efficiency through increased use of preferred flight profiles and improved sectorisation. Operational efficiency: - - LSSIP Year 2016 Armenia 20 Released Issue

33 P3D Expansion and Upgrade Organisation(s): ARMATS (AM) Type of project: National Schedule: From: Mar 2014 To: Dec 2015 Status: Description: Link and references ATM MP links: Finalised Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution 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). ITY-SPI - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - Safety: +++ increased safety through better surveillance coverage Environment: - Capacity: - Cost-efficiency: - Operational efficiency: - - LSSIP Year 2016 Armenia 21 Released Issue

34 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 Regional Projects OLDI Organisation(s): ARMATS (AM), SAKAERONAVIGATSIA (GE) Type of project: Regional Schedule: From: Jan 2016 To: Dec 2017 Status: Description: Link and references ATM MP links: Started Other links: - Project included in RP2 Performance Plan: Project included in DP2016: Performance contribution 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 ITY-FMTP - Name/Code in RP2 Performance Plan: - Name/Code in DP2016: - Safety: + Improved safety Environment: - Capacity: ++ Seamless operation Cost-efficiency: - Operational efficiency: - Cooperation Activities: with Georgia - LSSIP Year 2016 Armenia 22 Released Issue

35 Chapter 6 Implementation Objectives Progress 6.1. State View Overall Objective Implementation Progress distribution for applicable Implementation Objectives 2; 10% Completed 2; 10% Ongoing 4; 20% 12; 60% Planned Late No Plan Missing Data Undefined In 2016 a number of objectives have been completed, in particular in the field of GAT/OAT harmonisation (Objective AOM13.1) as well as in the field of safety (ATC16). 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 Ongoing. It is expected that once Basic OLDI, over FMTP, will be implemented with Tbilisi FIR and used operationally (in 2017), these objectives to be turned into Completed. It is also expected that the implementation of AMHS will allow the closure of objective FCM03 as well which currently is implemented at a level of 98%. LSSIP Year 2016 Armenia 23 Released Issue

36 6.1.2 Objective Progress per SESAR Key Feature Legend: ## % = Expected completion / % Progress 100% = Objective completed = Implementation Objective timeline (different colour per KF) = Completion beyond Implementation Objective timeline Optimised ATM Network Services Average implementation progress: 99% AOM13.1 AOM19.1 (PCP) AOM19.2 (PCP) AOM19.3 (PCP) FCM01 FCM03 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling ASM support tools to support AFUA ASM Management of realtime airspace data ASM Management of realtime airspace data Enhanced tactical flow management services Collaborative flight planning FCM04.1 STAM Phase 1 FCM04.2 (PCP) STAM Phase 2 FCM05 (PCP) Interactive rolling NOP < n/a n/a n/a 100% n/a n/a n/a 100% 98% FCM06 (PCP) Traffic Complexity Assessment n/a LSSIP Year 2016 Armenia 24 Released Issue

37 Advanced Air Traffic Services Average implementation progress: 88% < AOM21.1 (PCP) AOM21.2 (PCP) Direct Routing Free Route Airspace ATC02.2 STCA Level 2 ATC02.8 Groundbased Safety Nets n/a 100% 100% 10% ATC07.1 AMAN tools and procedures ATC12.1 ATC15.1 ATC15.2 (PCP) UDYZ Yerevan Airport Automated support for conflict detection, resolution support information and conformance monitoring Implement, in enroute operations, information exchange tools & procedures in support of basic AMAN Arrival Management extended to enroute airspace ATC16 ACAS II compliant with TCAS II change 7.1 ATC17 Electronic dialogue as automated assistance to controller during coordination and transfer n/a n/a n/a 100% 88% 100% ENV01 Continuous Descent Operations ITYCOTR NAV03 (PCP) RNAV 1 UDYZ Yerevan Airport Groundground automated coordination processes 100% 82% 100% NAV10 APV procedures 100% LSSIP Year 2016 Armenia 25 Released Issue

38 High Performing Airport Operations Average implementation progress: 67% < AOP04.1 ASMGCS Level 1 UDYZ Yerevan Airport n/a AOP04.2 ASMGCS Level 2 UDYZ Yerevan Airport n/a AOP05 Airport CDM UDYZ Yerevan Airport n/a AOP10 (PCP) TimeBased Separation UDYZ Yerevan Airport n/a AOP11 (PCP) Initial Airport Operations Plan AOP12 (PCP) AOP13 (PCP) UDYZ Yerevan Airport Improve runway and airfield safety with ATC clearances monitoring UDYZ Yerevan Airport Automated assistance to Controller for Surface Movement Planning and Routing UDYZ Yerevan Airport n/a n/a 0% ENV02 Collaborative Environmental Management SAF11 UDYZ Yerevan Airport Improve runway safety by preventing runway excursions 100% 100% LSSIP Year 2016 Armenia 26 Released Issue

39 Enabling Aviation Infrastructure Average implementation progress: 81% < COM10 Migrate from AFTN to AMHS 52% COM11 Voice over Internet Protocol (VoIP) 83% FCM08 (PCP) INF04 INF07 Extended Flight Plan Integrated briefing Electronic Terrain and Obstacle Data (etod) n/a 100% 100% ITYACID ITYADQ ITYAGDL ITYAGVCS2 ITYFMTP ITYSPI Aircraft identification Ensure quality of aeronautical data and aeronautical information Initial ATC airground data link services 8,33 khz airground voice channel spacing below FL195 Common Flight Message Transfer Protocol Surveillance performance and interoperability n/a 63% 92% 100% 53% 82% LSSIP Year 2016 Armenia 27 Released Issue

40 6.1.3 ICAO ASBU Implementation Legend: = Completed (during 2016 or before) = Missing planning date = Progress achieved in 2016 = Not applicable < B0APTA Optimization of Approach Procedures including vertical guidance 100% B0SURF Safety and Efficiency of Surface Operations (ASMGCS Level 12) B0FICE Increased Interoperability, Efficiency and Capacity through GroundGround Integration 87% 100% B0DATM B0ACAS Service Improvement through Digital Aeronautical Information Management ACAS Improvements 100% 82% 100% B0SNET Increased Effectiveness of GroundBased Safety Nets 100% B0ACDM Improved Airport Operations through B0RSEQ Improved Traffic flow through Runway sequencing (AMAN/DMAN) B0FRTO Improved Operations through Enhanced En Route Trajectories 100% B0NOPS B0ASUR B0CDO Improved Flow Performance through Planning based on a NetworkWide view Initial capability for ground surveillance Improved Flexibility and Efficiency in Descent Profiles (CDO) 99% 100% 82% 100% 100% B0TBO Improved Safety and Efficiency through the initial application of Data Link EnRoute 53% 100% LSSIP Year 2016 Armenia 28 Released Issue

41 6.2. Detailed Objectives Implementation progress Two colour codes are used for each Implementation 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. (*) Objective Scope Code: (**) Objective/Stakeholder Progress Code: ECAC Completed No Plan EU+ Ongoing Multi-N Planned Missing Data APT Late AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling 100% Completed Initial operational capability: 01/01/2012 Full operational capability: 31/12/2018 There are established OAT/GAT handling rules and procedures; they are based on EUROAT. 31/12/2016 REG (By:12/2018) GDCA 100% Completed 31/12/2016 Mil. Authority There are established OAT/GAT handling rules and procedures; Completed 100% they are based on EUROAT. 31/12/2016 ASP (By:12/2018) Mil. Authority There are established OAT/GAT handling rules and procedures; they are based on EUROAT. 100% ARMATS 100% MIL (By:12/2018) Mil. Authority AOM19.1 (PCP) There are established OAT/GAT handling rules and procedures; they are based on EUROAT. ASM support tools to support AFUA not applicable 100% Completed 31/12/2016 Completed 31/12/2016 Completed 31/12/2016 % There is flexible use of airspace based on procedures. ASP (By:12/2018) ARMATS There is flexible use of airspace based on procedures. % LSSIP Year 2016 Armenia 29 Released Issue

42 AOM19.2 (PCP) ASM Management of RealTime Airspace Data Initial operational capability: 01/01/2017 Full operational capability: 31/12/2021 % There is flexible use of airspace based on procedures. ASP (By:12/2021) ARMATS There is flexible use of airspace based on procedures. % AOM19.3 (PCP) Full rolling ASM/ATFCM process and ASM information sharing Initial operational capability: 01/01/2014 Full operational capability: 31/12/2021 % There is flexible use of airspace based on procedures. ASP (By:12/2021) ARMATS There is flexible use of airspace based on procedures. % AOM21.1 (PCP) Direct Routing not applicable All ATS routes are direct in Armenian airspace. Armenia plans to implement night time Free Route Airspace in winter , followed by 24H Free Route Airspace in ASP (By:12/2017) ARMATS All ATS routes are direct in Armenian airspace. % % AOM21.2 (PCP) Free Route Airspace Initial operational capability: 01/01/2015 Full operational capability: 31/12/2021 Armenia plans to implement night time Free Route Airspace in the upper airspace in winter , followed by 24H Free Route Airspace in ASP (By:12/2021) ARMATS Armenia plans to implement night time Free Route Airspace in 2017, followed by 24H Free Route Airspace in Free Route 10% 10% Ongoing 31/12/2018 Ongoing 31/12/2018 LSSIP Year 2016 Armenia 30 Released Issue

43 AOP04.1 Advanced Surface Movement Guidance and Control System (ASMGCS) Level1 % not applicable UDYZ Yerevan Airport There is in average 20 days of bad visibility per year. Due to the level of traffic, the deployment of ASMGCS Level 1 is not yet justified therefore UDYZ is not considered to be within the applicability area of the objective. However the deployment of ASMGCS 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 GDCA ASMGCS system, the regulator will take the required actions. ASP (By:12/2011) % ARMATS There is in average 20 days per year of bad visibility. % APO (By:12/2010) YEREVAN Zvartnots Airport 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. % AOP04.2 Advanced Surface Movement Guidance and Control System (ASMGCS) Level 2 % not applicable UDYZ Yerevan Airport 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 ASMGCS 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 ASMGCS Level 2 is ARMATS not yet justified therefore UDYZ is not considered to be within the applicability area of the objective. APO (By:12/2017) YEREVAN Zvartnots Airport Armenia is not part of the applicability area; however, this objective is under review for its possible implementation. % % Airport Collaborative Decision Making (CDM) AOP05 not applicable UDYZ Yerevan Airport Zvartnots Airport is not a busy airport. There are ideas to implement an automated system for the exchange of messages between ARMATS and Zvartnots Airport. ASP (By:12/2016) ARMATS Armenia is not part of the applicability area. % APO (By:12/2016) YEREVAN Zvartnots Airport Armenia is not part of the applicability area. % % LSSIP Year 2016 Armenia 31 Released Issue

44 Time Based Separation AOP10 (PCP) not applicable UDYZ Yerevan Airport UDYZ is not within the applicability area of the objective and there are no operational needs for implementation due to the levels of traffic. REG (By:12/2023) GDCA % ASP (By:12/2023) ARMATS % % AOP11 (PCP) Initial Airport Operations Plan not applicable 0% Planned UDYZ Yerevan Airport There are plans for implementation 31/12/2021 ASP (By:12/2021) There are plans for implementation, in cooperation with ARMATS Zvartnots airport APO (By:12/2021) YEREVAN Zvartnots Airport 0% Objective not reviewed yet 0% Improve runway and airfield safety with ATC clearances monitoring AOP12 (PCP) not applicable UDYZ Yerevan Airport 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) ARMATS % APO (By:12/2020) YEREVAN Zvartnots Airport % Automated assistance to Controller for Surface Movement Planning and Routing AOP13 (PCP) not applicable UDYZ Yerevan Airport UDYZ is not within the applicability area of the objective and there are no operational needs for implementation due to the levels of traffic. REG (By:12/2023) GDCA % ASP (By:12/2023) ARMATS % Planned 31/12/2021 Planned 31/12/2021 % % LSSIP Year 2016 Armenia 32 Released Issue

45 ATC02.2 Implement ground based safety nets Short Term Conflict Alert (STCA) level 2 100% Completed Initial operational capability: 01/01/2008 Full operational capability: 31/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. 31/12/2013 ASP (By:01/2013) ARMATS In Yerevan FIR, the ATM system Galaxy has the STCA level 2 implemented and operational. 100% Completed 31/12/2013 ATC02.8 Groundbased Safety Nets Initial operational capability: 01/01/2009 Full operational capability: 31/12/ % Completed The ground based safety nets (former Objectives ATC02.5 on APW, ATC02.6 on MSAW and ATC02.7 on APM) were implemented in the new ATM System Galaxy and are in operational use. 31/12/2013 ASP (By:12/2016) ARMATS The ground based safety nets (former Objectives ATC02.5, ATC02.6 and ATC02.7) were implemented in the new ATM System Galaxy and are in operational use. 100% AMAN tools and procedures ATC07.1 not applicable UDYZ Yerevan Airport 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/2019) ARMATS Armenia is not part of the applicability area. % Completed 31/12/2013 % ATC12.1 Automated support for conflict detection, resolution support information and conformance monitoring 100% 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 there is no need to implement the conflict 31/12/2013 resolution (CORA). ASP (By:12/2021) ARMATS The ATM system has the MTCD and MONA functions implemented and operational. Taking into account the low traffic level in Armenian airspace there is no need to implement the conflict resolution (CORA). 100% Completed 31/12/2013 LSSIP Year 2016 Armenia 33 Released Issue

46 ATC15.1 Implement, in enroute operations, information exchange mechanisms, tools and procedures in support of basic AMAN % not applicable Taking into account the forecast traffic levels, no need to implement this Objective has been identified. ASP (By:12/2017) ARMATS ATC15.2 (PCP) Taking into account the forecast traffic levels, no need to implement this Objective has been identified. Arrival Management extended to enroute Airspace not applicable % % Taking into account the forecast traffic levels, no need to implement this Objective has been identified. ASP (By:12/2023) ARMATS Taking into account the forecast traffic levels, no need to implement this Objective has been identified. % ATC16 Implement ACAS II compliant with TCAS II change 7.1 Initial operational capability: 01/03/ % Completed Full operational capability: 31/12/2015 It has been implemented in 2016 according to ICAO Annex 6 and Annex 10. For more details, see the comments at Stakeholder level. 31/12/2016 REG (By:12/2015) Has been implemented in 2016 according to ICAO Annex 6 and GDCA Annex 10. ASP (By:03/2012) 100% ARMATS It is implemented. 100% MIL (By:12/2015) Mil. Authority Not applicable as the retrofit is not justified in term of benefits. The pilots are trained and know what to expect from the equipped aircraft, if they fly in their vicinity. % Completed 31/12/2016 Completed 31/03/2012 ATC17 Electronic Dialogue as automated assistance to controller during coordination and transfer 88% Ongoing 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 /12/2017 Out of the remaining OLDI messages identified in ATC17, only PAC is being implemented. For the rest of the messages, no operational need has been identified yet. ASP (By:12/2018) The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since The ARMATS agreement has been signed and the testing has been done for 88% the implementation of the basic OLDI via FMTP with Tbilisi FIR (North). The final connection is planned in Ongoing 31/12/2017 LSSIP Year 2016 Armenia 34 Released Issue

47 COM10 Migrate from AFTN to AMHS Initial operational capability: 01/12/2011 Full operational capability: 31/12/ % Ongoing The ATM system has an AMHS capability. Procurement, installation and testing of AMHS system have done. The final operation is planned in /12/2017 ASP (By:12/2018) ARMATS ARMATS upgraded the COM centre to implement AMHS. AMHS 52% Ongoing 31/12/2017 COM11 Voice over Internet Protocol (VoIP) Initial operational capability: 01/01/2013 Full operational capability: 31/12/ % Ongoing The new VCS system has capability to use Voice over IP. It will be used if the neighbouring centers have such capability. 31/12/2018 ASP (By:12/2020) ARMATS The ARMATS new VCS system has capability to use Voice over IP. 83% Ongoing 31/12/2018 ENV01 Continuous Descent Operations (CDO) Initial operational capability: 01/07/ % Completed 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) ARMATS BCDA procedures are applied in Armenia. 100% APO (By:12/2013) YEREVAN Zvartnots Airport BCDA procedures are applied in Armenia. 100% Completed 31/12/2009 Completed 31/12/2009 ENV02 Airport Collaborative Environmental Management 100% Completed not applicable UDYZ Yerevan Airport 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. 31/12/2009 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 facilitate a joint approach contributing to the ARMATS minimisation of noise and gaseous emissions resulting from aircraft operations. APO (By:12/2016) YEREVAN Zvartnots Airport 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. 100% 100% Completed 31/12/2009 Completed 31/12/2009 LSSIP Year 2016 Armenia 35 Released Issue

48 FCM01 Implement enhanced tactical flow management services Initial operational capability: 01/08/ % Completed 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 Node was done in 2015.The FSA and CPR messages are sent to the NM. 31/12/2015 ASP (By:07/2014) ARMATS Armenia migrated to the IFPS Zone on the 21 December 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. 100% Completed 31/12/2015 FCM03 Collaborative flight planning Initial operational capability: 01/01/2000 Full operational capability: 31/12/ % Late 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/2018 CFMU. The processing of ADEXP format will be implemented after the installation of AMHS. ASP (By:12/2017) ARMATS The processing of ADEXP format will be implemented after the installation of AMHS. 98% Late 31/12/2018 FCM04.1 Short Term ATFCM Measures (STAM) phase 1 % not applicable Armenia is not in the applicability area of the objective. ASP (By:10/2017) ARMATS Armenia is not in the applicability area of the objective. % FCM04.2 (PCP) Short Term ATFCM Measures (STAM) phase 2 not applicable Armenia is not in the applicability area of the objective and there are not many ATFCM regulations in Armenia. ASP (By:12/2021) ARMATS There are not many ATFCM regulations in Armenia. % % LSSIP Year 2016 Armenia 36 Released Issue

49 FCM05 (PCP) Interactive rolling NOP not applicable % Due to the level of traffic and airspace configuration, there is no operational need for ASM systems (e.g. AOM19.x) therefore there is nothing to integrate with NM related to data exchanges in AIXM5.1 ASP (By:12/2021) ARMATS % APO (By:12/2021) YEREVAN Zvartnots Airport % FCM06 (PCP) Traffic complexity assessment 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) ARMATS The ATM system has the Sector Load Monitor (with graphic presentation for ACC, APP, and TWR and en route TLM presentation) and Point TLM functions. % Extended Flight Plan FCM08 (PCP) not applicable Armenia is not in the applicability area of the objective. Moreover, there are no plans to move the capabilities of ATM system towards FFICE/1. ASP (By:12/2021) ARMATS There are no plans to move the capabilities of ATM system towards FFICE/1. % % INF04 Implement integrated briefing Initial operational capability: 01/07/2002 Full operational capability: 31/12/ % Completed The implementation of level 3 and 4 was done on time and it is operational; the level 5 is operational since January Terminal and Integrated Briefing function at international airports of Armenia are provided. 31/01/2007 It is also accessible through Internet as of March ASP (By:12/2012) ARMATS The integrated briefing level 5 is implemented. 100% Completed 31/01/2007 LSSIP Year 2016 Armenia 37 Released Issue

50 INF07 Electronic Terrain and Obstacle Data (etod) Initial operational capability: 01/11/ % Completed Full operational capability: 31/05/2018 The ATM systemgalaxy has the TOD implemented and operational in 15/11/2013. In accordance with ICAO requirements the TOD policy and implementation programme is established. 31/12/2016 REG (By:05/2018) In accordance with ICAO requirements the TOD policy and GDCA implementation programme is established. ASP (By:05/2018) The Terrain Data and Obstacles for all Areas were published in ARMATS Nov of 2015 according to ICAO Annex 15 and are used in ATM system. APO (By:05/2018) YEREVAN Zvartnots Airport The Terrain Data and Obstacle for all Areas were published in Nov of 2015 according to ICAO Annex 15 and are used in ATM system. 100% 100% 100% Completed 31/12/2016 Completed 31/12/2016 Completed 31/12/2016 Aircraft identification ITYACID not applicable Armenia is not part of the applicability area. Hoverer, the ATM system Galaxy has the aircraft identification implemented and operational. ASP (By:01/2020) ARMATS ARMATS has implemented the aircraft identification using WAM and ADSB. 100% 100% Completed 15/11/2013 Completed 15/11/2013 ITYADQ Ensure quality of aeronautical data and aeronautical information 63% Ongoing not applicable Armenia is outside the applicability area of the objective, Voluntary implementation started in 2007; the data integrity guidance material in local working and quality 31/12/2017 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 GDCA implementation of ADQ ASP (By:06/2017) ARMATS implemented endtoend integrity of aeronautical data ARMATS during The implementation of ADQ has started. APO (By:06/2017) YEREVAN Zvartnots Airport Airport has quality management system, and is implementing ADQ 10% AIS_1 / AIS_2 87% 60% Ongoing 31/12/2017 Ongoing 30/06/2017 Ongoing 31/07/2013 LSSIP Year 2016 Armenia 38 Released Issue

51 ITYAGDL Initial ATC airground data link services not applicable 53% Ongoing 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/2018 communications service provider is not signed yet. The implementation is on hold pending clarification of the technical solutions. REG (By:02/2018) GDCA The GDCA will conduct oversight once the system is installed Ongoing 33% REG02 has been delegated to EUROCONTROL. 31/12/2018 ASP (By:02/2018) ARMATS plans to implement Air/Ground data link services. The ARMATS Galaxy ATM system installed In Yerevan ATC centre, has the data link capability. MIL (By:01/2019) Mil. Authority There is no intention to equip the transporttype State aircraft with data link equipment 63% % Ongoing 31/12/2018 ITYAGVCS2 8,33 khz airground voice channel spacing below FL195 % not applicable Armenia is not in the applicability area of the objective. However, the radios installed In Yerevan com centre have the 8.33 capability. The implementation is on hold pending the decision. REG (By:12/2018) GDCA Armenia is not in the applicability area of the objective. % ASP (By:12/2018) ARMATS Armenia is not in the applicability area of the objective. % MIL (By:12/2020) Mil. Authority Armenia is not in the applicability area of the objective. % APO (By:12/2018) YEREVAN Zvartnots Airport Armenia is not in the applicability area of the objective. % LSSIP Year 2016 Armenia 39 Released Issue

52 ITYCOTR Implementation of groundground automated coordination processes 82% Ongoing not applicable The new Galaxy ATM system has the capability. The operational use remains dependent on the neighbouring ACCs capabilities. The agreement has been signed and the testing has been done for the implementation of the basic OLDI with Tbilisi FIR (North). The 31/12/2017 operational use is expected in ASP (By:12/2012) The new Galaxy ATM system has the capability. The operational use remains dependent on the neighbouring ARMATS ACCs capabilities. The agreement has been signed and the testing has been done for the implementation of the basic OLDI with Tbilisi FIR (North). The operational use is expected in MIL (By:12/2012) 82% Ongoing 31/12/2017 Mil. Authority Military do not provide ATC service to civil flights % ITYFMTP Common Flight Message Transfer Protocol (FMTP) Entry into force of regulation: 28/06/2007 All EATMN systems put into service after 01/01/09: 01/01/2009 All EATMN systems in operation by 20/04/11: 20/04/ % Late 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 the implementation of the basic OLDI (ABI, ACT, REV, PAC, MAC, LAM) via FMTP with Tbilisi FIR (North). The 31/12/2017 final connection is expected in ASP (By:12/2014) The new 'Galaxy' ATM system has the capability, yet it has to be ARMATS implemented at regional level. MIL (By:12/2014) OLDI 92% Mil. Authority Military do not provide ATC service to civil flights % Late 31/12/2017 LSSIP Year 2016 Armenia 40 Released Issue

53 ITYSPI Surveillance performance and interoperability 82% Ongoing not applicable The upgrading of TMA and Enroute radars (CAT001, CAT 002) and MLAT (CAT19, CAT20, CAT21, CAT 034, CAT048) with time stamping, ATM system by ASTERIX protocols (CAT62) was implemented within the period of /12/2013 The operational use remains dependent on the neighbouring ACCs capabilities. REG (By:02/2015) GDCA Done in the context of the deployment of the new ATM system. 100% ASP (By:02/2015) The upgrading of TMA and Enroute radars (CAT001, CAT 002) and MLAT (CAT19, CAT20, CAT21, CAT034, CAT048) with ARMATS time stamping, ATM system by ASTERIX protocols (CAT62) was implemented within the period of The operational use remains dependent on the neighbouring ACCs capabilities. MIL (By:06/2020) P3D Expansion and Upgrade Mil. Authority Equipage of military fleet is not economically justified. % 78% Completed 31/12/2013 Ongoing 31/12/2013 NAV03 (PCP) RNAV 1 Initial operational capability: 01/01/2001 Full operational capability: 31/12/ % Completed The implementation was done in In summer 2007, BRNAV was implemented in the upper airspace (Above FL 195) of Armenia. All coordinates for the publication in the AIP are prepared in WGS84 format, in line with the accuracy and 31/12/2012 integrity requirements specified in ICAO Annex 15. ASP (By:12/2023) ARMATS All coordinates for the publication in the AIP are prepared in WGS84 format, in line with the accuracy and integrity requirements specified in ICAO Annex 15. The implementation of PRNAV was completed in DVOR/DME 100% APV procedures NAV10 Initial operational capability: 01/06/2011 Full operational capability: 31/12/2016 The APV BaroVNAV procedures at Zvartnots airport is already implemented, the safety case was developed and submitted to NSA, the subsequent approval has been given. REG (By:04/2016) In 2011 the GDCA has published national regulatory APV GDCA procedures, and approved APV safety case and APV operations. ASP (By:12/2016) ARMATS The APV BaroVNAV procedures at Zvartnots airport is already implemented, the safety case was developed and submitted to NSA, the subsequent approval has been given. 100% DVOR/DME 100% Completed 31/12/ % Completed 30/09/2012 Completed 31/03/2011 Completed 30/09/2012 LSSIP Year 2016 Armenia 41 Released Issue

54 Improve runway safety by preventing runway excursions SAF11 Initial operational capability: 01/09/2013 Full operational capability: 31/01/2018 The EAPPRE recommendations applicable to ARMATS and Zvartnots airport are implemented (RWY information, meteo data, AIP publications, ATS operations and so on). REG (By:01/2018) GDCA Implementation planned. 100% ASP (By:12/2014) ARMATS The EAPPRE recommendations are implemented (RWY information, meteo data, AIP publications, ATS operations and so on). 100% APO (By:12/2014) YEREVAN Zvartnots The applicable EAPPRE recommendations are implemented 100% Airport 100% Completed 31/12/2016 Completed 31/12/2016 Completed 31/12/2014 Completed 31/12/2014 LSSIP Year 2016 Armenia 42 Released Issue

55 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 NSA/CAA GDCA Mr. Galust POGOSYAN LSSIP Focal Point for ANSP ARMATS Mr. Samvel BAGHDASARYAN LSSIP Focal Point for Airport Zvartnots and Gyumri International Airports Mr. Sergey NALBANDYAN LSSIP Focal Point for Military MIL Mr. Alik SARGSYAN EUROCONTROL LSSIP Support Function Directorate Name LSSIP Contact Person for Armenia DPS/PEPR Mr. Octavian CIOARA Implementation Objectives Implementation Objective EUROCONTROL Objective Owners EUROCONTROL PEPR Objective Coordinator AOM13.1 O. MROWICKI A. DYBOWSKA AOM19.1 G. ACAMPORA O. ALFARO AOM19.2 G. ACAMPORA O. ALFARO AOM19.3 G. ACAMPORA O. ALFARO AOM21.1 C. BRAIN A. DYBOWSKA AOM21.2 C. BRAIN A. DYBOWSKA AOP04.1 M. BIRENHEIDE P. VRANJKOVIC AOP04.2 M. BIRENHEIDE P. VRANJKOVIC AOP05 M. BIRENHEIDE F. ROOSELEER AOP10 M. BIRENHEIDE F. ROOSELEER National Stakeholder Specialist Mr. Galust POGHOSYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Gevorg SIMONYAN Mr. Sergey NALBANDYAN Mr. Gevorg SIMONYAN Mr. Sergey NALBANDYAN Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN LSSIP Year 2016 Armenia 43 Released Issue

56 AOP11 M. BIRENHEIDE L. DELL ORTO AOP12 M. BIRENHEIDE P. VRANJKOVIC AOP13 M. BIRENHEIDE P. VRANJKOVIC ATC02.8 B. BAKKER F. ROOSELEER ATC07.1 P. TERZIOSKI L. DELL ORTO ATC12.1 P. TERZIOSKI L. DELL ORTO ATC15.1 P. CONROY L. DELL ORTO ATC15.2 P. HOP L. DELL ORTO ATC17 S. MORTON L. DELL ORTO Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN COM10 Y. EYUBOGLU J. PINTO Mr. Khoren SISAKYAN COM11 L. POPESCU J. PINTO Mr. Gevorg SIMONYAN ENV01 M. BIRENHEIDE B. HILL ENV02 S. MAHONY B. HILL FCM03 C. BOUMAN O. CIOARA FCM04.1 P. HOP O. CIOARA FCM04.2 P. HOP O. CIOARA FCM05 I. MENDES VIDEIRA O. CIOARA FCM06 P. HOP F. ROOSELEER FCM08 K. BREIVIK O. CIOARA INF07 A. PETROVSKY A-P. FRANGOLHO Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN Mr. Galust POGHOSYAN Mr. Gevorg HARUTYUNYAN ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Mr. Gevorg HARUTYUNYAN ITY-AGVCS2 J. POUZET B. HILL Mr. Arthur PAPOYAN Mr. Gevorg SIMONYAN ITY-FMTP L. POPESCU O. ALFARO Mr. Gevorg SIMONYAN ITY-ACID A. DESMOND-KENNEDY O. CIOARA Mr. Sergey DANIELYAN ITY-SPI M. BORELY O. CIOARA Mr. Gevorg SIMONYAN ITY-AGDL S. DISSING B. HILL Mr. Gevorg SIMONYAN NAV03 F. PAVLICEVIC P. VRANJKOVIC Mr. Artur ALAVERDYAN NAV10 R. FARNWORTH P. VRANJKOVIC Mr. Artur ALAVERDYAN SAF11 S. LAWRENCE F. ROOSELEER Mr. Galust POGHOSYAN Mr. Aram TUNYAN LSSIP Year 2016 Armenia 44 Released Issue

57 Annex B - National Stakeholders Organisation charts Aviation Joint Stock Companies Aviation Training Centre State Enterprise Aviamedical Centre State Enterprise ARMATS Air Operators (ARM Reg) MET Armenia International Airports ARMATS General council of Company Stakeholders Management Board General Director Collegial Executive Body ATS Director Yerevan ATC Center Yerevan ATC Tower Gyumri ATC Tower Technical Director Communication Service Navigation Service Surveillance Service ATM Systems Management Service Financial Director Accountancy Financial Economical Service Planning and Procurement Service Director of Personnel and Affairs Management Human Recourses Management Department General Office Affairs ManagementBoard Flight Safety and Quality Management Department Aeronautical Information Service Aviation Security Department Legal Service ATS planning Service Gyumri ATS Service IT Department Power Supply Service Technical Monitoring Department Operational Control Department LSSIP Year 2016 Armenia 45 Released Issue