Local Single Sky ImPlementation (LSSIP) ARMENIA

Transcription

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

2

3

4

5 DOCUMENT IDENTIFICATION SHEET LSSIP for Armenia Infocentre Reference: 14/01/07-02 Document Identifier Edition: Year 2013 LSSIP Year 2013 Armenia Edition Date: 30 Jan 2014 LSSIP Focal Point Samvel Baghdasaryan LSSIP Contact Person - Octavian Cioara samvel.baghdasaryan@armats.am octavian.cioara@eurocontrol.int Head of Technical and Information Provision Services Unit DSS/EIPR Status Intended for Working Draft General Public Draft Agency Stakeholders Proposed Issue Restricted Audience Released Issue Accessible via: Path: Internet ( X:\03 LSSIP\1. LSSIP States\Armenia (AM)\Year_2013\Released\LSSIP Year2013_AM_Released.doc LINKS TO REFERENCE DOCUMENTS 1. LSSIP Guidance Material: 2. ESSIP Plan Edition 2013: 3. ESSIP Report 2012: 4. STATFOR Forecasts: 5. Acronyms and abbreviations: 6. European ATM Master Plan: 7. LSSIP Documents: 8. National AIP: 9. National Performance Plan: Request should be send to staff@armats.am 10. National Business Plan (In Armenian): Request should be send to staff@armats.am LSSIP Year 2013 Armenia Released issue

6

7

8

9 TABLE OF 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 Accident/incident Investigation Body Chapter 2 - En-route Traffic and Capacity Evolution of traffic in Armenia YEREVAN ACC Summer 2013 performance Planning Period /19 - Summer Chapter 3 - ESSIP Report recommendations Chapter 4 - National Projects Chapter 5 - Regional Co-ordination Regional coordination projects Chapter 6 - ESSIP Objective Implementation ANNEXES LSSIP Year 2013 Armenia Released issue

10

11 Executive Summary State Context During 2013 the following changes have been done. The new ATM system <Galaxy> (<AZIMUT> Company, Russian Federation) has been successfully installed with combination of the VCS of the <MULTIFONO M800IP > (<S.I.T.T.I.> Company, Italy) and fully operational. The EAD Briefing Facility system has been installed (Frequentis Company, Austria) and fully operational. ESSIP Objective Implementation The implementation of ECAC wide Objectives progressed significantly in 2013 notably due to the introduction into service of the new ATM system. 7 additional ESSIP objectives were implemented in 2013: AOM20, AOP03, ATC02.2, ATC02.5, ATC02.6, ATC02.7 and ATC12. This leads to an overall of 16 active objectives from the ESSIP Plan edition 2013 already implemented by Armenia. In particular, ARMATS has implemented RNAV1 in Yerevan TMA, RNP APCH with Baro VNAV for RWY09 and RNP APCH for RWY27. The following objectives have been implemented partially: COM09, COM11, ITY-COTR and ITY-FMTP. Full compliance is not yet achieved due to the lack of capabilities in the neighbouring centres. LSSIP Armenia * FOC Date Planned implementation date (see legend at the bottom of the table) State-related ESSIP Objectives <= AOM13.1 AOM19 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling Implement Advanced Airspace Management [E] * [E] * AOM20 Implement ATS Route Network (ARN) - Version 7 [E] * AOM21 Implementation of Free Route Airspace [E] * AOP03 Improve runway safety by preventing runway incursions * ATC02.2 ATC02.5 ATC02.6 ATC02.7 Implement ground based safety nets - Short Term Conflict Alert (STCA) - level 2 Implement ground based safety nets - Area Proximity Warning - level 2 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2 Implement ground based safety nets - Approach Path Monitor - level 2 [E] * [E] * [E] * [E] * ATC07.1 Implement arrival management tools [E] * ATC12 ATC15 Implement automated support for conflict detection and conformance monitoring Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations [E] * [E] * ATC16 Implement ACAS II compliant with TCAS II change 7.1 * ATC17 COM09 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer Migrate ground international or regional X.25 data networks or services to the Internet Protocol (IP) [E] * * LSSIP Year 2013 Armenia 1 Released issue

12 LSSIP Armenia * FOC Date Planned implementation date (see legend at the bottom of the table) COM10 Migrate from AFTN to AMHS * COM11 Implementation of Voice over Internet Protocol (VoIP) in ATM * FCM01 Implement enhanced tactical flow management services [E] * FCM03 Implement collaborative flight planning [E] * FCM04 Implementation of Short Term ATFCM Measures - phase 1 [E] * FCM05 Implementation of interactive rolling NOP [E] * INF04 Implement integrated briefing * ITY-ADQ ITY-AGDL Ensure quality of aeronautical data and aeronautical information Initial ATC air-ground data link services above FL-285 [E] * [E] * ITY-AGVCS2 Implement air-ground voice channel spacing requirements below FL195 * ITY-COTR Implementation of ground-ground automated co-ordination processes [E] * ITY-FMTP Apply a common flight message transfer protocol (FMTP) * ITY-SPI Surveillance performance and interoperability * NAV03 Implementation of P-RNAV [E] * NAV10 Implement APV procedures [E] * SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements * SAF11 Improve runway safety by preventing runway excursions * SRC-CHNG Implementation of Safety Oversight of Changes to ATM by National Supervisory Authorities (NSA) * SRC-RLMK Implement the EUROCONTROL Safety Regulatory Requirements (ESARRs) * SRC-SLRD Safety Levels and Resolution of Deficiencies * LSSIP Year 2013 Armenia 2 Released issue

13 Airport-related ESSIP Objectives <= UDYZ-Yerevan AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual * AOP04.1 AOP04.2 AOP05 ENV01 ENV02 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1 [E] * Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2 * Implement Airport Collaborative Decision Making (CDM) Implement Continuous Descent Operations (CDO) techniques for environmental improvements [E] * * Implement Collaborative Environmental Management (CEM) at Airports * NOTE: The year where the coloured box is placed indicates the Implementation Completion Date as stated in the ESSIP for each objective. The colour-code indicates the Local progress with respect to this date. Understanding the Table Objective Objective Partly Objective Planned No Plan Missing Data (Armenia/Zvarnots Airport does not participate in this objective) Late LSSIP Year 2013 Armenia 3 Released issue

14

15 Introduction The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a five-year plan containing ECAC States actions to achieve the Implementation Objectives as set out by the ESSIP and to improve the performance of their national ATM System. The LSSIP document Year 2013 describes the situation in the State at the end of December The LSSIP documents are structured into 6 chapters to better differentiate the Stakeholder(s) accountable for the information contained in each of them: Chapters 1 to 5 present the key players in the State, and sets the institutional and geographical scenes to help the reader understand the specifics of the State and interpret the rest of the document correctly. It also presents a short description of the main national and regional projects in which the national Stakeholders are involved. Chapter 6 contains high-level information on progress and plans of each ESSIP Objective. The information for each ESSIP Objective is presented in boxes giving a summary of the progress and plans of implementation for each Stakeholder. The conventions used are presented at the beginning of the section. Note: Chapter 6 is completed with a separate document called LSSIP Level 2. This document consists of a set of tables organised in line with the list of ESSIP Objectives. Each table contains all the actions planned by the four national stakeholders to achieve their respective Stakeholder Lines of Action (SLoAs) as established in the ESSIP. LSSIP Year 2013 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 European Common Aviation Area EASA Working Arrangement Annex 1 ATM 2011 ICAO 18 June 1992 JAA 2004 NATO 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 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 2013 Armenia 5 Released issue

18 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 2013 Armenia 6 Released issue

19 Government Council General Department of Civil Aviation Director General General Department of Civil Aviation Consultant Of Director General Assistant Of Director General Deputy Director General Deputy Director General Administrative Group Airworthiness Department Flight Operations Department Aviation Security Department Airtransportati on Regulation Department Accounting Section Aerodromes Certification and ATM Department Legal Section General Section Human Resources Section 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 and Status of GDCA N202-N ANSP Certification GDCA Government Order N744-N (Establishing procedure for granting permission of ANSP) Safety Oversight GDCA GDCA GD Order N14-A (Safety oversight, audit process regulatory requirements) Establishment of Tolerable Safety Levels GDCA Aviation Law and the statute of GDCA Safety Performance Monitoring GDCA Aviation Law and the statute of GDCA Enforcement actions in case of non-compliance with safety regulatory requirements Airspace GDCA GDCA / Ministry of Defence Aviation Law and the statute of GDCA Government Order N825-N (Airspace Management Regulation). Economic GDCA Government of Armenia and Ministry of Finance orders. Environment GDCA Aviation Law. Security GDCA Order N1307-N (Civil Aviation Safety Security in Republic of Armenia) LSSIP Year 2013 Armenia 7 Released issue

20 The roles and responsibilities of the civil and military authorities for airspace management are established by the relevant decision of the Government in accordance with the flexible use of airspace principles 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: Annual Report published: Y Further information is available on the following web-site: ARMATS (ANSP) Name of the ANSP: ARMATS Governance: Joint Stock Company Ownership: 100% State Services provided Y/N Comment ATC en-route ATC approach ATC Airport(s) AIS CNS Y Y Y Y Y MET N Provided by the Aviation Meteorological Centre, a Joint Stock Company reporting to the Ministry of Nature Protection ATCO training Y General and aviation English trainings in GB. Refresh trainings in Prague. Others Additional information: Provision of services in other State(s): N Further information is available on the ARMATS web-site: Annual Report published: Y This is the annual report covering yearly activities of the ANSP. LSSIP Year 2013 Armenia 8 Released issue

21 ATM system in use Specify the manufacturer of the ATC system currently in use: AZIMUT (Russian Company) Major upgrade 1 of the ATC system is performed: 2013 The new generation ATM system Galaxy was installed at Yerevan ATC centre which is deployed by the Russian company AZIMUT. The system GALAXY has a modular architecture according to the EUROCONTROL requirements and uses ASTERIX inside. All subsystems are linked via redundant LAN and all servers have triple redundancy (Active, Hot-standby and Cold-standby). Surveillance Data Processing System combines all traditional RDP functions and ability of connecting with different sensors PSR, (M) SSR, mode S, multilateration (MLAT) and ADS-B. Aircraft derived data are used for surveillance data processing and presentation of additional information in track labels (Indicated Airspeed, Selected Altitude and QNH, Magnetic Heading, Rate of Climb or Descent). All calculations are carried out in WGS-84 model of the Earth FDP system uses real time data from SDPS instead of static FPL route to update aircraft trajectory. Safety Nets processing is compatible with EUROCONTROL Specification for Short Term Conflict Alert (STCA), Minimum Safe Altitude Warning (MSAW), Area Proximity Warning (APW) and Approach Path Monitor (APM). MONA, MTCD, flexible vector, possibility of OLDI with adjacent FIRs, CPDLC, separate QNH areas for flights below transition level, automated update of flight plans and sending of DEP, ARR messages to CFMU are also engaged in the system. The system is also interfaced with European Aeronautical Database EAD (AIXM). Controller Working Position provides an integrated representation of the air situation, combining actual surveillance sensor data and FPL information. Being ready scaleable it can act as a separate working position directly interfacing with sensors (PSR, SSR, mode-s, ADS-B, MLAT, ADF, weather systems and AFTN network) or be a part of ATC system interfacing with SDPS and FDPS modules. GALAXY simulator is used as a back-up system as well. The new IP Voice Communication System (VCS) <MULTIFONO M800IP > (<S.I.T.T.I.> Company, Italy) was installed at Yerevan ATC centre. The radio and telephone VCS fully integrates new IP Network requirements and latest technological achievements with user-friendliness needs at Operator and Maintenance levels. The VCS system combines all up-to-date interfaces such as MFC R2; ATS QSIG; E1 QSIG; and VoIP 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 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 Airport in Gyumri, located at about 100 km northwest of Yerevan. All flights to Europe, Middle East, and other international connections originate exclusively out of Zvartnots. Gyumri Shirak Airport only scheduled serves for CIS countries and charter flights to all destinations. Given the fact that Armenia is completely landlocked, the country relies heavily on its international airports as the main point of entry for both passengers and cargo. 1 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40)) LSSIP Year 2013 Armenia 9 Released issue

22 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: Airport(s) covered by the LSSIP 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 Regulatory role Regulatory framework and rule-making OAT and provision of service for OAT governed 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 Y 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 N ANSP Certification NA ANSP Supervision Y ANSP Supervision NA Aircrew Training Y ESARR applicability NA Aircrew Licensing Additional Information: Military provides only flight control in TSAs Means used to inform airspace users (other than military) about these provisions: Y 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 LSSIP Year 2013 Armenia 10 Released issue

23 Oversight OAT National oversight body for OAT: Air Force 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 Additional information: nil 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 AIS N AIS NA MET Y MET NA SAR Y SAR Y TSA/TRA monitoring Y FIS NA Other: Other: Military ANSP providing GAT services SES certified? Certificate issued by: Additional Information: Armenia is not yet 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 N Both OAT and GAT Y If Military fly OAT-IFR inside controlled airspace, specify the available options: Free Routing N Within specific corridors only Y Within the regular (GAT) national route network Y Under radar control Y Within a special OAT route system Y Under radar advisory service N If Military fly GAT-IFR inside controlled airspace, specify existing special arrangements: No special arrangements N Exemption from Route Charges N Exemption from flow and capacity (ATFCM) measures N Provision of ATC in UHF Y CNS exemptions: RVSM Y 8.33 Y Mode S Y ACAS Y Others: LSSIP Year 2013 Armenia 11 Released issue

24 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 Accident/incident Investigation Body Investigations Investigations following accidents and/or incidents are carried out by the provisional flight safety inspection body, which is subordinated directly to the Director General of the GDCA, moreover in exceptional cases the Government can designate a special investigation committee. The provisional flight safety inspection body is a public institution, it is not an autonomous decision making authority and it is settled as an independent body within the Civil Aviation System; therefore the objectivity of its dealings is assured as requested by Directive 94/56/EC. To guarantee an independent position, the provisional flight safety inspection body has been put under the direct surveillance of the Authority of the Director General of GDCA different from the regulation Deputy Director of GDCA. The provisional flight safety inspection body conducts investigations for Civil Aviation aircraft accidents and serious incidents. In case of non serious incidents they can task the service provider to conduct investigations on behalf of GDCA. In the frame of ARMATS SMS, all ATM related incidents should be investigated by ARMATS internally and relevant corrective actions implemented Collection, Evaluation & Processing of Data The service provider is tasked by the GDCA to collect, evaluate, process and store all ATM related information to civil aviation accidents, incidents and occurrences, as well as to make this information available to others. The investigating bodies issue safety recommendations as appropriate (with the exclusion of accidents and incidents to State aircraft) following its investigations, and/or whenever deemed appropriate conducts studies and surveys aimed at increasing flight safety. In order to carry out this function, TOKAI, the tool developed by EUROCONTROL, is used Civil-Military Accidents/Incidents Investigation of accidents and/or incidents involving Civil and Military are conducted by a joint body composed by experts from the Military Flight Safety Department, the GDCA and ARMATS. LSSIP Year 2013 Armenia 12 Released issue

25 Chapter 2 - En-route Traffic and Capacity 2.1 Evolution of traffic in Armenia Armenia - Annual IFR Movements Armenia - Distribution (Ref. year 2012) IFR flights IFR movements - Actuals Domestic flights 0% Overflights 61% IFR movements - Baseline forecast IFR movements - High forecast IFR movements - Low forecast International Dep/Arr 39% A 2010 A 2011 A 2012 A 2013 F 2014 F 2015 F 2016 F 2017 F 2018 F 2019 F A = Actual F = Forecast STATFOR Medium-Term Forecast (September 2013) IFR flights yearly growth 2010 A 2011 A 2012 A 2013 F 2014 F 2015 F 2016 F 2017 F 2018 F 2019 F H -4,3% 13,9% 8,4% 7,9% 7,3% 7,6% 7,5% Armenia B 9,3% 8,1% -2,0% -5,0% 11,8% 6,2% 6,2% 5,5% 5,8% 5,7% L -5,6% 9,8% 4,3% 4,6% 4,0% 4,2% 4,1% ESRA B 0,8% 3,1% -2,4% -0,9% 1,4% 2,6% 2,7% 2,2% 2,5% 2,5% 2013 En-route traffic in Armenia decreased by 7.1% during Summer 2013 (May to October inclusive), when compared to Summer /19 The STATFOR medium-term forecast (MTF) predicts an average annual traffic growth between 5.2% and 8.8% for the planning period, with an average baseline growth of 6.9%. 2.2 YEREVAN ACC Summer 2013 performance Traffic Evolution 2013 Capacity Baseline En-route Delay (min/flight) Optimum All reasons Without weather Capacity gap -8.4% 25 (0%) No Capacity Plan : Sufficient Capacity to meet demand Comments Summer 2013 performance assessment The ACC capacity baseline was measured with ACCESS. During the measured period, the average peak 1 hour demand was 12 and the average peak 3 hour demand was Planning Period /19 - Summer The planning focuses on the Summer season to reflect the most demanding period of the year from a capacity perspective. This approach ensures consistency with the previous planning cycles. The /19 summer capacity profile and delay breakdown has been derived according to the LSSIP Year 2013 Armenia 13 Released issue

26 following parameters: 2014: capacity requirement profiles based on the delay breakdown per ACC as provided in January /19: Reference value based on the breakdown of a yearly European delay target of 0.5 min/flight UDDDCTA Annual Summer En-route ATFM delay breakdown - Reference Values Capacity Profiles 2013 Profiles (hourly movements and % increase over previous year) ACC baseline H 25 0% 25 0% 25 0% 25 0% 25 0% 27 8% Ref. 25 0% 25 0% 25 0% 25 0% 25 0% 25 0% UDDD 25 L 25 0% 25 0% 25 0% 25 0% 25 0% 25 0% C/R 25 0% 25 0% 25 0% 26 4% 26 0% 26 0% Capacity Plan Year Measures planned Max sectors Capacity increase p.a. Reference profile (ACC) Additional information Sufficient capacity to meet expected demand 0% 0% 0% 0% 0% 0% UDDDCTA - Reference capacity profile and alternative scenarios 30 Capacity profile (movements per hour) Reference Capacity Profile Capacity Profile - Current Routes Capacity Profile - High Capacity Profile - Low Capacity Baseline Plan More information on the methodology related to capacity planning is available at : LSSIP Year 2013 Armenia 14 Released issue

27 Chapter 3 - ESSIP Report recommendations Recommendations issued from the ESSIP Report for 2012 applicable to Armenia for all items that require corrective actions and improvements. Number Recommendation Ownership REC Reply by AM REC Reply by AM REC To ensure that all Stakeholders report the expected completion dates as defined in their National business plans. All States Completion dates reported in the LSSIP are fully aligned with the National Business Plan To ensure correct application of LSSIP guidance material and to implement the results of mandatory LSSIP in-cycle check. All States The LSSIP guidance material is fully applied and the results of the in-cycle check have been fully implemented. To ensure actions for overcoming present delays in the implementation of basic ATSMHS capability (ESSIP objective COM10). AL, AM, AZ, CY, CZ, DK, EE, FI, FR, GR, HR, HU, IT, LU, MAS, MD, MT, NO, SE, SI, UA Reply by AM Armenia will implement ATSMHS in REC Reply by AM States to ensure that appropriate actions are taken for overcoming present delays in the implementation of priority capabilities specified in the ESSIP objective FCM03. BE, UK, SE, NO, FI, LV, PL, HU, UA, AM, TR, MK, FR, PT, MT, RO, HR, BA, AL, SI, IT, CZ, MAS, CY. Priority capabilities of FCM03 have been implemented in the new ATM system put in service in REC States are encouraged to speed up the AFP implementation and to schedule AFP testing with Network Manager. All States Reply by AM AFP has been implemented in the new ATM system put in service in REC ANSPs are encouraged to publish more APV routes. All ECAC ANSPs Reply by AM APV Routes already published for Zvartnots International Airport LSSIP Year 2013 Armenia 15 Released issue

28 Chapter 4 - National Projects The main projects currently ongoing in Armenia are depicted in the table below. Name Schedule Description Scope Status Link with European Master Plan. P3D Expansion and Upgrade From: Mar 2014 To: Dec 2015 Expansion of the infrastructure over the whole territory using new additional receiving stations. Upgrade the architecture of the current two WAM systems by changing it from CT (central timing) to DT (distributed timing). Expected Contribution to the Key Performance Areas 2 Planned ITY-SPI Capacity and safety improvement ATIS From: Jan 2014 To: Dec 2014 AMHS From: Jan 2015 To: Dec 2015 CPDLC From: Jan 2014 To: Dec 2015 NAV Rationalisation ATC technical system From: Jan 2016 To: Dec 2017 From: Sep 2012 To: Apr 2014 QMS From: Jan 2014 to Dec 2016 AIS From: Sep 2014 To: Dec 2017 AIS From: Sep 2014 To: Apr 2017 AIS From: Sep 2014 To: Apr 2017 Procurement and installation of the new ATIS system with D-ATIS possibility. Planned OI Step IS-0401 Safety improvement Procurement and installation of AMHS system. Planned COM 10 Cost-efficiency and safety improvement Implementation of CPDLC Started ITY-AGDL Capacity and safety improvement Rationalisation of the navigation infrastructure. Installation of new DMEs. Installation at the airport a new D-VOR / DME. Aeronautical Data Set for ATC System Using EAD Database document and catalogue preparation. Activation of the implemented quality management system, which will allow to have fully regulated documentation and change management and safety assessment procedures. Transition from aeronautical information service concept (AIS) to aeronautical information management concept (AIM) Monitoring of quality and completeness of the digital aeronautical data. Planned Enabler CTE-N5a Cost-efficiency improvement Started OI Step IS-0204 Safety and cost-efficiency improvement Planned ITY-ADQ Safety and cost-efficiency improvement Planned ITY-ADQ Safety and cost-efficiency improvement Planned ITY-ADQ Safety and cost-efficiency improvement Creation and maintenance of the digital data for charting Planned ITY-ADQ Safety and cost-efficiency improvement 2 Capacity, safety, cost-efficiency and environment as defined in Recital 2 of Regulation (EU) No 691/2010. LSSIP Year 2013 Armenia 16 Released issue

29 Chapter 5 - Regional Co-ordination 5.1 Regional coordination projects To facilitate the harmonisation process within the different ANS Domains in the Caucasus region with the objective of meeting global and European standards and directives, Armenia has for several years enhanced and developed ANS co-operation. The harmonisation approach is based on the assumption that regional and sub-regional planning, development and management is a necessity in order to establish and maintain the future CNS/ATM systems at a safe, productive and cost-effective level, which will be accepted by the airspace users. Operational Letters of Agreement (LoAs) have been signed between Yerevan ACC and all neighbouring countries; non ECAC ACC Tehran ACC and ECAC ACCs Tbilisi ACC, Ankara ACC and Baku ACC. They take into account the implementation of RVSM in European region of ICAO and RNAV Routes. LSSIP Year 2013 Armenia 17 Released issue

30 Chapter 6 - ESSIP Objective Implementation Conventions Two colour codes are used for each ESSIP Objective box : o o one colour code is used to show the Objective Scope in the Objective ID cell, and 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 (By:mm-yyyy) (By:mm-yyyy) (By:mm-yyyy) APO (By:mm-yyyy) high level progress statement high level progress statement high level progress statement APO high level progress statement State Impl. Date APO. Progress (**) APO Impl. Date. Progress (**) Impl. Date. Progress (**) Impl. Date APO. Progress (**) APO Impl. Date (*) Objective Scope Code: (**) Objective/Stakeholder Progress Code: ECAC No Plan EU+ Partly Multi-N Planned Missing Data APT Late LSSIP Year 2013 Armenia 18 Released issue

31 AOM13.1 Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling (By:12/2018) [Essential] No Plan There are established OAT/GAT handling rules and procedures; they are not based on EUROAT. Conformance analysis and possible amendments of the existing rules/procedures will be addressed in 2014/2015.Objective will be reviewed after the conformance analysis. (By: ) There are established OAT/GAT handling rules and procedures; they are not based on EUROAT. Conformance analysis and possible amendments of the existing rules/procedures will be addressed in 2014/2015. Objective will be reviewed after the conformance analysis. No Plan (By: ) There are established OAT/GAT handling rules and procedures; they are not based on EUROAT. Conformance analysis and possible amendments of the existing rules/procedures will be addressed in 2014/2015. Objective will be reviewed after the conformance analysis. No Plan (By: ) There are established OAT/GAT handling rules and procedures; they are not based on EUROAT. Conformance analysis and possible amendments of the existing rules/procedures will be addressed in 2014/2015. Objective will be reviewed after the conformance analysis. No Plan AOM19 Implement Advanced Airspace Management (By:12/2016) [Essential] Planned There is flexible use of airspace based on procedures. The implementation of an automated system is under consideration, will be addressed after /2015 (By: ) There is flexible use of airspace based on procedures. The implementation of an automated system is under consideration, will be addressed after Planned 12/2015 (By: ) There is flexible use of airspace based on procedures. The implementation of an automated system is under consideration, will be addressed after Planned 12/2015 AOM20 Implement ATS Route Network (ARN) - Version 7 (By:10/2013) [Essential] Armenia is involved in RNDSG. ARN version 7 has been implemented. 10/2013 (By: ) The airspace structure change (route/sector and terminal airspace) is the responsibility of ARMATS. 10/2013 (By: ) The airspace structure change (route/sector and terminal airspace) is the responsibility of ARMATS; done through collaboration with Military authorities. 10/2013 AOM21 Implementation of Free Route Airspace (By:12/2017) (Outside Applicability Area) [Essential] Not Applicable Armenia is not in the applicability area of the objective. (By: ) (By: ) (By: ) Armenia is not in the applicability area of the objective. Armenia is not in the applicability area of the objective. Armenia is not in the applicability area of the objective. LSSIP Year 2013 Armenia 19 Released issue

32 AOP01.2 Implement airside capacity enhancement method and best practices based on Eurocontrol capacity and efficiency implementation manual (By:12/2013) UDYZ - Yerevan (Outside Applicability Area) Not Applicable Armenia is not part of the applicability area. No airport capacity problem foreseen within the timeframe covered by present LSSIP. (By: ) APO (By: ) No airport capacity problem foreseen within the timeframe covered by the present LSSIP. Armenia is not part of the applicability area. No airport capacity problem foreseen within the timeframe covered by the present LSSIP. Armenia is not part of the applicability area. AOP03 Improve runway safety by preventing runway incursions (By: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, the ANSP ARMATS and the major aircraft operator. There are procedures related to the runway safety. The SMS of Zvartnots International Airport and ARMATS address also Runway Safety. The runway safety team meets 2 times a year, plus when there is a need for a particular runway safety issue. There is a LoA between ARMATS and the Airport authorities that establishes roles and responsibilities of each stakeholder. 12/2013 (By: ) (By: ) (By: ) APO (By: ) GDCA has decided upon the strategy for implementation at Zvartnots International Airport of specific actions contained in the EAPRI document. Voice communications between the tower and drivers are not conducted in English. Military authorities do not provide ATC service to civil flights. Military flights operate as GAT on Zvarnots airport. The airport SMS is approved by the regulatory body and it is operational. Drivers on the runway do not speak English. 12/ / /2013 LSSIP Year 2013 Armenia 20 Released issue

33 AOP04.1 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level1 (By:12/2011) [Essential] Not Applicable UDYZ - Yerevan (Outside Applicability Area) UDYZ is not 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. There is in average 20 days of bad visibility per year. (By: ) (By: ) (By: ) APO (By: ) When the ANSP and the Airport have decided to implement an ASMGCS system, the regulator will take the required actions. There is in average 20 days per year of bad visibility. Military airports do not provide ATC service to civil flights. 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. 12/2015 AOP04.2 Implement Advanced Surface Movement Guidance and Control System (A-SMGCS) Level 2 (By:12/2017) Not Applicable UDYZ - Yerevan (Outside Applicability Area) Armenia is not part of the applicability area. In average per year bad visibility is about 20 days for CAT II conditions and less than 10 days for CAT III conditions. (By: ) Armenia is not part of the applicability area; however, this objective is under review for its possible implementation. (By: ) Armenia is not part of the applicability area; however, this objective is under review for its possible implementation. APO (By: ) Armenia is not part of the applicability area; however, this objective is under review for its possible implementation. AOP05 Implement Airport Collaborative Decision Making (CDM) (By:01/2016) [Essential] Not Applicable UDYZ - Yerevan (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. (By: ) (By: ) APO (By: ) Armenia is not part of the applicability area. Military airports do not provide service to civil flights. Armenia is not part of the applicability area. LSSIP Year 2013 Armenia 21 Released issue

34 ATC02.2 Implement ground based safety nets - Short Term Conflict Alert (STCA) - level 2 (By:01/2013) [Essential] ATM system Galaxy has the STCA level 2 implemented and operational in Yerevan ACC and Yerevan TMA. Implementation of procedures and training of controllers is done. 12/2013 (By: ) (By: ) (By: ) GDCA has verified the new system. In Yerevan FIR, the ATM system Galaxy has the STCA level 2 implemented and operational. Military ATC units do not provide area radar services. They do not provide ATC service to Civil flights. 12/ /2013 ATC02.5 Implement ground based safety nets - Area Proximity Warning - level 2 (By:12/2016) [Essential] The ATM system Galaxy has the APW level 2 implemented and operational in Yerevan ACC and Yerevan TMA. Implementation of procedures and training of controllers is done. 12/2013 (By: ) (By: ) ARMATS has installed the ATM system with APW level 2 capability. Military do not provide air traffic service to civil flights. 12/2013 ATC02.6 Implement ground based safety nets - Minimum Safe Altitude Warning - level 2 (By:12/2016) [Essential] The ATM system Galaxy has the Minimum Safe Altitude Warning level 2 implemented and operational in Yerevan ACC and Yerevan TMA. 12/2013 (By: ) (By: ) ARMATS has installed the new ATM system with MSAW level 2 capability. Military do not provide air traffic service to civil flights. 12/2013 ATC02.7 Implement ground based safety nets - Approach Path Monitor - level 2 (By:12/2016) [Essential] The ATM system Galaxy has the APM level 2 implemented and operational. 12/2013 (By: ) (By: ) ARMATS has installed the ATM system with APM level 2 capability. Military do not provide air traffic service to civil flights. 12/2013 LSSIP Year 2013 Armenia 22 Released issue

35 ATC07.1 Implement arrival management tools (By:12/2015) (Outside Applicability Area) [Essential] Not Applicable Taking into account the forecast traffic levels over the LSSIP timeframe, no need to implement this Objective has been identified. No benefits identified for the foreseeable future. (By: ) Armenia is not part of the applicability area. ATC12 Implement automated support for conflict detection and conformance monitoring (By:12/2016) [Essential] The ATM system Galaxy has the MTCD and MONA functions implemented and operational. 12/2013 (By: ) The new ATM system has the MTCD and MONA functions implemented and operational 06/2013 (By: ) ARMATS has installed the new ATM system and implemented the MTCD and MONA functions. 12/2013 ATC15 Implement, in En-Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations (By:12/2017) (Outside Applicability Area) [Essential] Not Applicable Taking into account the forecast traffic levels, no need to implement this Objective has been identified. (By: ) (By: ) Taking into account the forecast traffic levels, no need to implement this Objective has been identified. 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 (By:12/2015) Planned It will be implemented in due time. For more details, see the comments at Stakeholder level. 12/2014 (By: ) (By: ) (By: ) Will be implemented in due time. It is implemented. Not applicable as the retrofit is not justified in term of benefits. Planned 12/ /2012 LSSIP Year 2013 Armenia 23 Released issue

36 ATC17 Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer (By:12/2018) [Essential] Planned The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since /2015 (By: ) Planned 01/2015 (By: ) The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC system since Planned 01/2015 COM09 Migrate ground international or regional X.25 data networks or services to the Internet Protocol (IP) (By:12/2014) Partly The current network is based on IP v4. There is a plan to upgrade to IP v6. The new ATC system has the capability of IP v6. 12/2014 (By: ) (By: ) (By: ) The GDCA notified ARMATS of the mandate to migrate to IP v6. Once the IPv6 will be implemented the GDCA will conduct the oversight. The new ATC system has the capability of IP v6. Military do not provide ATC service to civil flights 12/2010 Partly 12/2014 COM10 Migrate from AFTN to AMHS (By:12/2014) Late The ATM system has an AMHS capability. The migration of the AFTN system to AMHS is foreseen through the existing COM centre upgrade. Yet the operational use will be addressed at regional level with connected MTA (Message Transfer Agent). 12/2015 (By: ) (By: ) ARMATS will upgrade the COM centre to implement AMHS. Military authorities do not control Civil flights. Late 12/2015 COM11 Implementation of Voice over Internet Protocol (VoIP) in ATM (By:12/2020) Partly The new VCS system has capability to use Voice over IP. It will be used in case of the neighbour centres will have such capability. 12/2015 (By: ) (By: ) (By: ) The ARMATS new VCS system has capability to use Voice over IP. The ARMATS new VCS system has capability to use Voice over IP. Military do not provide ATC service to Civil flights 12/2013 Partly 12/2015 LSSIP Year 2013 Armenia 24 Released issue

37 ENV01 Implement Continuous Descent Operations (CDO) techniques for environmental improvements (By:12/2013) UDYZ - Yerevan (Outside Applicability Area) CDA is implemented for 24 hours. All airport arrivals are achieving a CDA profile. All airlines are applying CDA. There is no monitoring. All procedures including SIDs and STARs are designed aiming at minimising the environmental impact. CDA approaches are published in the AIP. 12/2009 (By: ) APO (By: ) BCDA procedures are applied in Armenia. BCDA procedures are applied in Armenia. 12/ /2009 ENV02 Implement Collaborative Environmental Management (CEM) at Airports (By:12/2016) UDYZ - Yerevan The Collaborative Environmental Management (CEM) team meets regularly. The team is composed by representatives of the Airport, the ANSP and the major aircraft operator. The team does not have a formal status and a TOR, it meets only when needed to address specific issues. The main task of the Environment unit is the noise abatement and airfield fuel and emissions reduction. 12/2009 (By: ) ARMATS cooperates with the Airport and Aircraft Operators in order to facilitate a joint approach contributing to the minimisation of noise and gaseous emissions resulting from aircraft operations. 12/2009 (By: ) Military airports do not provide ATC service to civil flights. APO (By: ) 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. 12/2009 FCM01 Implement enhanced tactical flow management services (By:12/2006) [Essential] Late Armenia is in the IFPS Zone. The ATC system is not connected to CFMU. The new system will have all the required connections with CFMU. 12/2014 (By: ) (By: ) Armenia migrated to the IFPS Zone on the 21 December The new system will have all the required connections with CFMU. Military do not provide air traffic service to civil flights. Late 12/2014 LSSIP Year 2013 Armenia 25 Released issue

38 FCM03 Implement collaborative flight planning (By:12/2015) [Essential] Planned Armenia is in the IFPS Zone. Currently the connection with CFMU is ensured through the FMP; the ATC system is not connected to CFMU. The new system will have all the required connections with CFMU. 12/2014 Planned (By: ) The new system will have all the required connections with CFMU. Modernisation of YEREVAN ACC 12/2014 (By: ) Military do not provide air traffic service to civil flights. FCM04 Implementation of Short Term ATFCM Measures - phase 1 (By:12/2015) (Outside Applicability Area) [Essential] Not Applicable Armenia is not in the applicability area of the objective. (By: ) Armenia is not in the applicability area of the objective. (By: ) Armenia is not in the applicability area of the objective. FCM05 Implementation of interactive rolling NOP (By:12/2016) [Essential] No Plan Objective not yet reviewed (By: ) (By: ) (By: ) APO (By: ) No Plan No Plan No Plan No Plan INF04 Implement integrated briefing (By:12/2012) 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. It is also accessible through Internet as of March /2007 (By: ) (By: ) The integrated briefing level 5 is implemented. There is only one AIS office in Armenia which is managed by ARMATS. Military are clients of this office. 01/2007 LSSIP Year 2013 Armenia 26 Released issue

39 ITY-ADQ Ensure quality of aeronautical data and aeronautical information (By:07/2017) (Outside Applicability Area) [Essential] Planned Implementation started in 2007; the data integrity guidance material in local working and quality procedures/processes as well as the service level agreements with main actors are implemented. 12/2016 (By: ) The regulator is adopting required documentations for the implementation of ADQ Planned 12/2016 (By: ) ARMATS implemented endtoend integrity of aeronautical data during The implementation of ADQ has started. Planned 12/2016 (By: ) There is only one AIS office in Armenia which is managed by ARMATS. Military are clients of this office. APO (By: ) Airport has quality management system, and is implementing ADQ Planned 12/2016 ITY-AGDL Initial ATC air-ground data link services above FL-285 (By:02/2015) (Outside Applicability Area) [Essential] Planned Armenia is not in the applicability area of the objective. However, the Galaxy ATM system installed In Yerevan ATC centre, has the capability. The testing is planned in The operational use remains dependent on the neighbouring ACCs capabilities. 02/2015 (By: ) (By: ) (By:-) The GDCA will conduct oversight once the system is installed 02 has been delegated to EUROCONTROL. ARMATS plans to implement Air/Ground data link services There is no intention to equip the transporttype State aircraft with data link equipment Planned 02/2015 Planned 02/2015 ITY- AGVCS2 Implement air-ground voice channel spacing requirements below FL195 (By:12/2020) (Outside Applicability Area) Not Applicable Armenia is not in the applicability area of the objective. (By: ) (By: ) (By: ) APO (By: ) Armenia is not in the applicability area of the objective. Armenia is not in the applicability area of the objective. Armenia is not in the applicability area of the objective. Armenia is not in the applicability area of the objective. LSSIP Year 2013 Armenia 27 Released issue

40 ITY-COTR Implementation of ground-ground automated coordination processes (By:02/2015) (Outside Applicability Area) [Essential] Partly The new Galaxy ATM system has the capability. The operational use remains dependent on the neighbouring ACCs capabilities. Currently, none of the neighbouring ACCs is capable. 12/2013 (By: ) 12/2013 (By: ) The new Galaxy ATM system has the capability. The operational use remains dependent on the neighbouring ACCscapabilities. Currently, none of the neighbouring ACCs is capable. Partly 12/2013 (By: ) Military do not provide ATC service to civil flights ITY-FMTP Apply a common flight message transfer protocol (FMTP) (By:12/2014) Partly The new Galaxy ATM system has the capability. Has to be addressed at regional level. The operational use remains dependent on the neighbouring ACCscapabilities. Currently, none is capable. For the time being there are no firm plans for operational use. 12/2014 (By: ) (By: ) (By: ) GDCA will exercise its role in due time. The new Galaxy ATM system has the capability, yet it has to be implemented at regional level. Military do not provide ATC service to civil flights Partly 12/2014 Partly 12/2014 ITY-SPI Surveillance performance and interoperability (By:12/2019) (Outside Applicability Area) Not Applicable The upgrading of TMA and Enroute radars (CAT001, CAT 002), MLAT (CAT034, CAT048) and ATC system by ASTERIX protocols with time stamping was implemented in The ASTERIX protocol CAT062 is implemented on the new Galaxy ATM system. The operational use remains dependent on the neighbouring ACCs capabilities. (By: ) (By: ) (By: ) The upgrading of TMA and Enroute radars (CAT001, CAT 002), MLAT (CAT034, CAT048) and ATC system by ASTERIX protocols with time stamping was implemented in The ASTERIX protocol CAT062 is implemented on the new Galaxy ATM system. The operational use remains dependent on the neighbouring ACCscapabilities. Equipage of military fleet is not economically justified. LSSIP Year 2013 Armenia 28 Released issue

41 NAV03 Implementation of P-RNAV (By:12/2012) [Essential] 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 integrity requirements specified in ICAO Annex /2012 (By: ) Navigation databases are only available from accredited suppliers with suitable quality assurance procedures in place. 12/2009 (By: ) 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 AIP and eaip of the Republic of Armenia / Navigation Aids Modernisation 12/2012 (By: ) Military do not provide ATC service to civil flights NAV10 Implement APV procedures (By:12/2016) [Essential] 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. 12/2012 (By: ) (By: ) (By: ) In 2011 the GDCA has published national regulatory APV procedures, and approved APV safety case and APV operations. 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. Military do not have any plan and agreements with Civil ANSP and Airports to use APV BaroVNAV operations 03/ /2012 SAF10 Implement measures to reduce the risk to aircraft operations caused by airspace infringements (By:12/2011) The European action plan is implemented. 12/2012 (By: ) (By: ) (By: ) GDCA is involved in the development of the implementation plan. All the applicable measures were implemented Military are consulted. 12/ / /2012 LSSIP Year 2013 Armenia 29 Released issue

42 SAF11 Improve runway safety by preventing runway excursions (By:01/2018) No Plan Still under consideration. No implementation plan defined yet. 01/2018 (By: ) (By: ) (By: ) APO (By: ) Still under consideration. Still under consideration. Military authorities do not provide ATC service to civil flights. Still under consideration. No Plan 01/2018 No Plan 12/2014 No Plan 12/2014 SRC- CHNG Implementation of Safety Oversight of Changes to ATM by National Supervisory Authorities (NSA) (By:12/2010) Implemented and amended in /2009 (By: ) (By: ) Implemented and amended in GDCA: Military do not provide ATM service to civil flights and military systems are not used for the provision of services by ARMATS. 12/2009 SRC- RLMK Implement the EUROCONTROL Safety Regulatory Requirements (ESARRs) (By:12/2010) ESARRs are fully implemented at the exception of ESARR 6 that is only partially implemented. 12/2009 (By: ) The GDCA has implemented ESARRs by adopting / transposing into national law and ensures regular updates by introducing new amendments. 12/2009 (By: ) Military do not provide ATM service to civil flights SRC- SLRD Safety Levels and Resolution of Deficiencies (By:12/2010) The mechanism to collect, evaluate process and store occurrences in aviation (including ATM) is implemented and operational but the Just Culture environment is not ensured. (By: ) National regulations have been formally promulgated / published to transpose ESARR 2 into the national legal order. The governmental order 1777 of Jan has been enacted and is based on ICAO Annex 13. A national legislation containing detailed requirements of ESARR 2 has been completed and approved by the GDCA December / /2012 (By: ) Military do not provide ATM service to civil flights LSSIP Year 2013 Armenia 30 Released issue

43 Annexes Annex A Specialists involved in the LSSIP Process LSSIP Co-ordination (and Part State Context) LSSIP Focal Point for Armenia ARMATS Mr. Samvel BAGHDASARYAN LSSIP Focal Point for Airports Zvartnots and Gyumri International Airports Mr. Sergey NALBANDYAN LSSIP Contact Person for Armenia EUROCONTROL Mr. Octavian CIOARA Part - ESSIP Objective Implementation ESSIP Objective EUROCONTROL Objective Owners AOM13.1 R. BUCUROIU, O. MROWICKI, E. REUBER AOM19 AOM20 AOM21 AOP01.2 AOP03 AOP04.1 AOP04.2 AOP05 ATC02.2 ATC02.5 ATC02.6 ATC02.7 ATC07.1 ATC12 ATC15 G. ACAMPORA, O. MROWICKI R. BUCUROIU R. BUCUROIU P. ADAMSON P. JOPPART, T. LICU P. ADAMSON P. ADAMSON P. ADAMSON B. BAKKER, S. DROZDOWSKI B. BAKKER, S. DROZDOWSKI B. BAKKER, S. DROZDOWSKI B. BAKKER, S. DROZDOWSKI P. CONROY, P. TERZIOSKI P. TERZIOSKI P. CONROY, P. TERZIOSKI EUROCONTROL EIPR Objective Coordinator National Stakeholder Specialist(s) A. DYBOWSKA Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN A. DYBOWSKA Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN A. DYBOWSKA Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN A. DYBOWSKA Mr. Arthur PAPOYAN Mr. Sergey DANIELYAN P. VRANJKOVIC Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN P. VRANJKOVIC Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN P. VRANJKOVIC Mr. Gevorg SIMONYAN Mr. Sergey NALBANDYAN P. VRANJKOVIC Mr. Gevorg SIMONYAN Mr. Sergey NALBANDYAN P. VRANJKOVIC Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN I. FEIJT Mr. Samvel BAGHDASARYAN Mr. Harutyun BABAYAN L. DELL ORTO Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN L. DELL ORTO Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN L. DELL ORTO Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN ATC16 S. DROZDOWSKI L. DELL ORTO Mr. Samvel BAGHDASARYAN LSSIP Year 2013 Armenia 31 Released issue

44 ESSIP Objective ATC17 EUROCONTROL Objective Owners S. MORTON EUROCONTROL EIPR Objective Coordinator National Stakeholder Specialist(s) Mr. Aram TUNYAN L. DELL ORTO Mr. Samvel BAGHDASARYAN Mr. Sergey DANIELYAN COM09 L. POPESCU O. ALFARO Mr. Gevorg SIMONYAN COM10 Y. EYUBOGLU A. KOKONA Mr. Gevorg SIMONYAN COM11 L. POPESCU A. KOKONA Mr. Gevorg SIMONYAN ENV01 ENV02 FCM01 FCM03 FCM04 FCM05 P. ADAMSON S. MAHONY, A. WATT H. KOOLEN S. SMIDT M. RICHARD N. AGACDIKEN B. HILL Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN B. HILL Mr. Sergey DANIELYAN Mr. Sergey NALBANDYAN O. CIOARA Mr. Galust Poghosyan Mr. Arthur PAPOYAN O. CIOARA Mr. Galust Poghosyan Mr. Arthur PAPOYAN O. CIOARA Mr. Galust Poghosyan Mr. Arthur PAPOYAN O. CIOARA Mr. Galust Poghosyan Mr. Arthur PAPOYAN INF04 P. MATERN A-P. FRANGOLHO Mr. Simon ASATRYAN ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Mr. Simon ASATRYAN ITY-AGDL S. DISSING A. KOKONA Mr. Gevorg SIMONYAN ITY-AGVCS2 TBD O. ALFARO Mr. Arthur PAPOYAN Mr. Gevorg SIMONYAN ITY-COTR S. MORTON L. DELL ORTO Mr. Samvel BAGHDASARYAN ITY-FMTP L. POPESCU O. ALFARO Mr. Gevorg SIMONYAN ITY-SPI M. BORELY, R. STEWART O. CIOARA Mr. Gevorg SIMONYAN NAV03 NAV10 F. PAVLICEVIC R. FARNWORTH A. KOKONA Mr. Artur ALAVERDYAN Mr. Partev MAMIKONYAN A. KOKONA Mr. Artur ALAVERDYAN Mr. Partev MAMIKONYAN SAF10 T. LICU I. FEIJT Mr. Aram TUNYAN SAF11 S. LAWRENCE I. FEIJT Mr. Aram TUNYAN SRC-CHNG M. DEBOECK A. DYBOWSKA Mr. Aram TUNYAN SRC-RLMK M. DEBOECK A. DYBOWSKA Mr. Aram TUNYAN SRC-SLRD M. DEBOECK A. DYBOWSKA Mr. Aram TUNYAN LSSIP Year 2013 Armenia 32 Released issue

45 Annex B National Stakeholders Organisation Charts Aviation Joint Stock Companies Aviation Training Centre State Enterprise Avia-Medical Centre State Enterprise ARMATS Air Operators (ARM. Reg) ARMATS LSSIP Year 2013 Armenia 33 Released issue