EUROCONTROL
Local Single Sky ImPlementation (LSSIP) ARMENIA
Year 2013 ‑ Level 1
DOCUMENT IDENTIFICATION SHEET
LSSIP for Armenia
Infocentre Reference: 14/01/07-02
Document Identifier Edition: Year 2013
LSSIP Year 2013 Armenia Edition Date: 30 Jan 2014
LSSIP Focal Point – Samvel Baghdasaryan E-mail: Head of Technical and Information [email protected] Provision Services
LSSIP Contact Person - Octavian Cioara E-mail: Unit DSS/EIPR [email protected]
Status Intended for
Working Draft General Public
Draft Agency Stakeholders
Proposed Issue Restricted Audience
Released Issue
Accessible via: Internet (www.eurocontrol.int)
Path: X:\03 LSSIP\1. LSSIP States\Armenia (AM)\Year_2013\Released\LSSIP Year2013_AM_Released.doc
LINKS TO REFERENCE DOCUMENTS
1. LSSIP Guidance Material: http://www.eurocontrol.int/articles/guidance-material 2. ESSIP Plan Edition 2013: www.eurocontrol.int/pepr 3. ESSIP Report 2012: www.eurocontrol.int/pepr 4. STATFOR Forecasts: http://www.eurocontrol.int/forecast-monitoring-analysis 5. Acronyms and abbreviations: http://www.eurocontrol.int/articles/glossaries 6. European ATM Master Plan: https://www.atmmasterplan.eu/ 7. LSSIP Documents: http://www.eurocontrol.int/articles/lssip 8. National AIP: http://armats.com/eng/aviation/aip.htm 9. National Performance Plan: Request should be send to e-mail: [email protected] 10. National Business Plan (In Armenian): Request should be send to e-mail: [email protected]
LSSIP Year 2013 Armenia Released issue
TABLE OF CONTENTS
Executive Summary ...... 1 Introduction ...... 4 Chapter 1 - National ATM Environment ...... 5 1.1 Geographical Scope ...... 5 1.1.1 International Membership ...... 5 1.1.2 Geographical description of the FIR(s) ...... 5 1.1.3 Airspace Classification and Organisation ...... 5 1.2 National Stakeholders ...... 6 1.2.1 Civil Regulator(s) ...... 7 1.2.2 ARMATS (ANSP) ...... 8 1.2.3 Airports ...... 9 1.2.4 Military Authorities ...... 10 1.2.5 Accident/incident Investigation Body ...... 12 Chapter 2 - En-route Traffic and Capacity ...... 13 2.1 Evolution of traffic in Armenia ...... 13 2.2 YEREVAN ACC ...... 13 2.2.1 Summer 2013 performance ...... 13 2.2.2 Planning Period 2014-2018/19 - Summer ...... 13 Chapter 3 - ESSIP Report recommendations ...... 15 Chapter 4 - National Projects ...... 16 Chapter 5 - Regional Co-ordination ...... 17 5.1 Regional coordination projects ...... 17 Chapter 6 - ESSIP Objective Implementation ...... 18
ANNEXES
LSSIP Year 2013 Armenia Released issue
Executive Summary
State Context During 2013 the following changes have been done. The new ATM system
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.
* FOC Date LSSIP 2013 - Armenia █ Planned implementation date (see legend at the bottom of the table)
State-related ESSIP Objectives 2013 2014 2008 2009 2010 2011 2012 2015 2016 2017 2018 2019 2020 <=2007 Harmonise Operational Air Traffic (OAT) and General Air [IDP] AOM13.1 Traffic (GAT) handling [E] * [IDP] AOM19 Implement Advanced Airspace Management [E] * AOM20 Implement ATS Route Network (ARN) - Version 7 [E] * [IDP] AOM21 Implementation of Free Route Airspace [E] *
AOP03 Improve runway safety by preventing runway incursions * Implement ground based safety nets - Short Term Conflict ATC02.2 [E] Alert (STCA) - level 2 * Implement ground based safety nets - Area Proximity ATC02.5 [E] Warning - level 2 * Implement ground based safety nets - Minimum Safe ATC02.6 [E] Altitude Warning - level 2 * Implement ground based safety nets - Approach Path ATC02.7 [E] Monitor - level 2 * ATC07.1 Implement arrival management tools [E] * Implement automated support for conflict detection and ATC12 [E] conformance monitoring * Implement, in En-Route operations, information exchange [IDP] ATC15 mechanisms, tools and procedures in support of Basic [E] * AMAN operations
ATC16 Implement ACAS II compliant with TCAS II change 7.1 * Electronic Dialogue as Automated Assistance to Controller [IDP] ATC17 during Coordination and Transfer [E] * Migrate ground international or regional X.25 data networks COM09 [IDP] or services to the Internet Protocol (IP) *
LSSIP Year 2013 Armenia 1 Released issue * FOC Date LSSIP 2013 - Armenia █ Planned implementation date (see legend at the bottom of the table) COM10 Migrate from AFTN to AMHS * Implementation of Voice over Internet Protocol (VoIP) in COM11 ATM * FCM01 Implement enhanced tactical flow management services [E] * [IDP] FCM03 Implement collaborative flight planning [E] * [IDP] FCM04 Implementation of Short Term ATFCM Measures - phase 1 [E] * [IDP] FCM05 Implementation of interactive rolling NOP [E] *
INF04 Implement integrated briefing * Ensure quality of aeronautical data and aeronautical ITY-ADQ [E] information * [IDP] ITY-AGDL Initial ATC air-ground data link services above FL-285 [E] * Implement air-ground voice channel spacing requirements ITY-AGVCS2 below FL195 * Implementation of ground-ground automated co-ordination ITY-COTR [E] processes * ITY-FMTP Apply a common flight message transfer protocol (FMTP) [IDP] *
ITY-SPI Surveillance performance and interoperability * NAV03 Implementation of P-RNAV [E] * [IDP] NAV10 Implement APV procedures [E] * Implement measures to reduce the risk to aircraft operations SAF10 caused by airspace infringements *
SAF11 Improve runway safety by preventing runway excursions * Implementation of Safety Oversight of Changes to ATM by SRC-CHNG National Supervisory Authorities (NSA) * Implement the EUROCONTROL Safety Regulatory SRC-RLMK Requirements (ESARRs) *
SRC-SLRD Safety Levels and Resolution of Deficiencies *
LSSIP Year 2013 Armenia 2 Released issue
Airport-related ESSIP Objectives 2013 2014 2008 2009 2010 2011 2012 2015 2016 2017 2018 2019 2020 <=2007
UDYZ-Yerevan Implement airside capacity enhancement method and best AOP01.2 practices based on Eurocontrol capacity and efficiency * implementation manual Implement Advanced Surface Movement Guidance and AOP04.1 [E] Control System (A-SMGCS) Level1 * Implement Advanced Surface Movement Guidance and AOP04.2 Control System (A-SMGCS) Level 2 * [IDP] AOP05 Implement Airport Collaborative Decision Making (CDM) [E] * Implement Continuous Descent Operations (CDO) ENV01 [IDP] techniques for environmental improvements * Implement Collaborative Environmental Management ENV02 (CEM) at Airports *
NOTE: The year where the coloured box is placed indicates the ‘Implementation Completion Date’ as stated in the ESSIP for each objective. The colour-code indicates the Local progress with respect to this date.
Understanding the Table
Objective Completed No Plan
Objective Partly Completed Missing Data
Objective Planned Not Applicable (Armenia/Zvarnots Airport does not participate in this objective)
Late
LSSIP Year 2013 Armenia 3 Released issue
Introduction
The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a five-year plan containing ECAC States’ actions to achieve the Implementation Objectives as set out by the ESSIP and to improve the performance of their national ATM System. The LSSIP document – Year 2013 describes the situation in the State at the end of December 2013.
The LSSIP documents are structured into 6 chapters to better differentiate the Stakeholder(s) accountable for the information contained in each of them:
Chapters 1 to 5 present the key players in the State, and sets the institutional and geographical scenes to help the reader understand the specifics of the State and interpret the rest of the document correctly. It also presents a short description of the main national and regional projects in which the national Stakeholders are involved.
Chapter 6 contains high-level information on progress and plans of each ESSIP Objective. The information for each ESSIP Objective is presented in boxes giving a summary of the progress and plans of implementation for each Stakeholder. The conventions used are presented at the beginning of the section.
Note: Chapter 6 is completed with a separate document called LSSIP Level 2. This document consists of a set of tables organised in line with the list of ESSIP Objectives. Each table contains all the actions planned by the four national stakeholders to achieve their respective Stakeholder Lines of Action (SLoAs) as established in the ESSIP.
LSSIP Year 2013 Armenia 4 Released issue
Chapter 1 - National ATM Environment
1.1 Geographical Scope
1.1.1 International Membership Armenia is a Member of the following international organisations in the field of ATM:
Organisation Since ECAC December 1996 EUROCONTROL 1 March 2006 European Union European Common Aviation Area EASA Working Arrangement Annex 1 ATM 2011 ICAO 18 June 1992 JAA 2004 NATO
1.1.2 Geographical description of the FIR(s) The geographical scope of this document addresses the YEREVAN FIR in Armenia. Adjacent FIRs: The Yerevan FIR is bordered by the following FIRs: ECAC FIR: Georgia: Tbilisi FIR (North), Turkey: Ankara FIR (West), and Azerbaijan: Baku FIR (East). Non ECAC FIRs: Iran: Tehran FIR (South) The way across North to South is ~340Km and East to West is ~200Km.
1.1.3 Airspace Classification and Organisation Armenian airspace consists of a single FIR, which is divided into lower and upper airspace. The Division Flight Level (DFL) separating upper from lower ATS airspace is FL 195. Classification of the airspace is Class “C” between FL 195 and FL 660 according with the EUROCONTROL requirements.
LSSIP Year 2013 Armenia 5 Released issue
1.2 National Stakeholders The main National Stakeholders involved in ATM in Armenia are the following: - General Department of Civil Aviation (GDCA); - Armenian Air Traffic Services (ARMATS); - Armenian International Airports (AIA); - Air Force; - The Aviation Meteorological Centre (Ministry of Nature Protection). Their activities (GDCA) are detailed in the following subchapters and their relationships are shown in the diagram below.
LSSIP Year 2013 Armenia 6 Released issue Government
Council General Department of Civil Aviation
Director General General Department of Consultant Assistant Civil Aviation Of Of Director General Director General
Deputy Director Deputy Director Administrative Airworthiness Flight Operations Department General General Group Department
Airtransportati Accounting Aerodromes General Human Aviation Security Section Resources on Regulation Certification and Legal Section Section Department Department Section ATM Department
1.2.1 Civil Regulator(s)
1.2.1.1 General information Civil aviation in Armenia is the responsibility of the GDCA (General Department of Civil Aviation at the Government of Republic of Armenia). GDCA is the State Regulatory body under the authority of the Prime Minister and the Government. The different national entities having regulatory responsibilities in ATM are summarised in the table below. The GDCA is further detailed in the following sections.
Activity in ATM: Organisation Legal Basis responsible Rule-making GDCA Aviation Law and Status of GDCA N202-N 13.02.2003 ANSP Certification GDCA Government Order N744-N 19.06.2008 (Establishing procedure for granting permission of ANSP) Safety Oversight GDCA GDCA GD Order N14-A 02.02.2010 (Safety oversight, audit process regulatory requirements) Establishment of Tolerable GDCA Aviation Law and the statute of GDCA Safety Levels Safety Performance Monitoring GDCA Aviation Law and the statute of GDCA Enforcement actions in case of GDCA Aviation Law and the statute of GDCA non-compliance with safety regulatory requirements Airspace GDCA / Ministry of Government Order N825-N 03.07.2003 (Airspace Defence Management Regulation). Economic GDCA Government of Armenia and Ministry of Finance orders. Environment GDCA Aviation Law. Security GDCA Order N1307-N 02.10.2003 (Civil Aviation Safety Security in Republic of Armenia)
LSSIP Year 2013 Armenia 7 Released issue The roles and responsibilities of the civil and military authorities for airspace management are established by the relevant decision of the Government in accordance with the flexible use of airspace principles.
1.2.1.2 GDCA Civil aviation in Armenia is the responsibility of the GDCA, Governmental body having ministerial status. By its decree of 3 March 1993 the Government of Armenia has established the GDCA, as a State Regulatory body in the field of civil aviation, reporting directly to the Government. Afterwards, in 2002 the Aviation Law has instituted the main tasks and responsibilities of the GDCA. The General Department of Civil Aviation of the Republic of Armenia implements the State policy, State regulatory and economic regulatory functions and exercises State administration and supervision with regard to the use of the airspace and civil aviation operations in Armenia. The GDCA is the National Supervisory Authority. The GDCA is a State administration Institution under the authority of the Prime Minister and the Government, financed from the State budget. The Government has approved a regulation enabling the GDCA to become financially self-sufficient and capable of funding its regulatory and oversight activities. It allows having certain inputs from user charges. The GDCA is institutionally separated from the ANSP.
Further information is available on the GDCA web-site: http://www.aviation.am
Annual Report published: Y Further information is available on the following web-site: http://aviation.am/index.php/en/legislation/hashv
1.2.2 ARMATS (ANSP)
Name of the ANSP: ARMATS Governance: Joint Stock Company Ownership: 100% State Services provided Y/N Comment ATC en-route Y ATC approach Y ATC Airport(s) Y AIS Y CNS Y MET N Provided by the Aviation Meteorological Centre, a Joint Stock Company reporting to the Ministry of Nature Protection ATCO training Y General and aviation English trainings in GB. Refresh trainings in Prague. Others Additional information: Provision of services in N other State(s):
Further information is available on the ARMATS web-site: http://www.armats.com
Annual Report published: Y http://armats.com/arm/activity/reports.htm This is the annual report covering yearly activities of the ANSP.
LSSIP Year 2013 Armenia 8 Released issue 1.2.2.1 ATM system in use
Specify the manufacturer of the ATC system currently in use: AZIMUT (Russian Company) Major upgrade1 of the ATC system is performed: 2013 The new generation ATM system “Galaxy” was installed at Yerevan ATC centre which is deployed by the Russian company “AZIMUT. The system “GALAXY” has a modular architecture according to the EUROCONTROL requirements and uses “ASTERIX inside”. All subsystems are linked via redundant LAN and all servers have triple redundancy (Active, Hot-standby and Cold-standby). Surveillance Data Processing System combines all traditional RDP functions and ability of connecting with different sensors PSR, (M) SSR, mode S, multilateration (MLAT) and ADS-B. Aircraft derived data are used for surveillance data processing and presentation of additional information in track labels (Indicated Airspeed, Selected Altitude and QNH , Magnetic Heading, Rate of Climb or Descent). All calculations are carried out in WGS-84 model of the Earth FDP system uses real time data from SDPS instead of static FPL route to update aircraft trajectory. Safety Nets processing is compatible with EUROCONTROL Specification for Short Term Conflict Alert (STCA), Minimum Safe Altitude Warning (MSAW), Area Proximity Warning (APW) and Approach Path Monitor (APM). MONA, MTCD, flexible vector, possibility of OLDI with adjacent FIRs, CPDLC, separate QNH areas for flights below transition level, automated update of flight plans and sending of DEP, ARR messages to CFMU are also engaged in the system. The system is also interfaced with European Aeronautical Database EAD (AIXM). Controller Working Position provides an integrated representation of the air situation, combining actual surveillance sensor data and FPL information. Being ready scaleable it can act as a separate working position directly interfacing with sensors (PSR, SSR, mode-S, ADS-B, MLAT, ADF, weather systems and AFTN network) or be a part of ATC system interfacing with SDPS and FDPS modules. “GALAXY” simulator is used as a back-up system as well. The new IP Voice Communication System (VCS)
1.2.2.2 ATC units The ATC units in the Armenian airspace, which are of concern to this LSSIP, are the following:
ATC Unit Number of sectors Associated FIR(s) Remarks En-route TMA YEREVAN ACC 1 YEREVAN FIR 3 is the total number of sectors of Yerevan ATC (including TWR) YEREVAN APP 1 YEREVAN FIR
1.2.3 Airports
1.2.3.1 General information There are two international airports in Armenia: • Yerevan “Zvartnots” International Airport, the main gateway to Armenia, located 12 km southwest of Yerevan; • “Shirak” Airport in Gyumri, located at about 100 km northwest of Yerevan. All flights to Europe, Middle East, and other international connections originate exclusively out of “Zvartnots”. Gyumri “Shirak” Airport only scheduled serves for CIS countries and charter flights to all destinations. Given the fact that Armenia is completely landlocked, the country relies heavily on its international airports as the main point of entry for both passengers and cargo.
1 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))
LSSIP Year 2013 Armenia 9 Released issue “Zvartnots” International Airport is the main International Airport of Armenia, it provides full airport services. “Zvartnots” International Airport and the Gyumri “Shirak” Airport are operated by Armenian International Airport Company. ARMATS operates the joint approach and Tower units of “Shirak” Airport.
Further information is available on the AIA web-site: http://www.aia-zvartnots.aero
1.2.3.2 Airport(s) covered by the LSSIP Yerevan “Zvartnots” International Airport is the only Armenian airport covered by the LSSIP Year 2013.
1.2.4 Military Authorities The Military Authorities in Armenia are composed of: - Air Force, - Air Defence. They report to the Ministry of Defence. Their regulatory, service provision and user role in ATM are detailed below.
1.2.4.1 Regulatory role Regulatory framework and rule-making
OAT and provision of service for OAT governed Y Provision of service for GAT by the Military N by national legal provisions? governed by national legal provisions? Level of such legal provision: Aviation Law, Rules of the Level of such legal provision: NA Air and Air Force Regulations. Authority signing such legal provision: Minister of Authority signing such legal provision: NA Defence and Chief of Air Force These provisions cover: These provisions cover: Rules of the Air for OAT Y Organisation of military ATS for OAT Y Organisation of military ATS for GAT NA OAT/GAT Coordination Y OAT/GAT Coordination Y ATCO Training Y ATCO Training NA ATCO Licensing Y ATCO Licensing NA ANSP Certification N ANSP Certification NA ANSP Supervision Y ANSP Supervision NA Aircrew Training Y ESARR applicability NA Aircrew Licensing Y Additional Information: Military provides only flight Additional Information: Military do not provide air traffic control in TSAs control service to GAT flights. Means used to inform airspace users (other than Means used to inform airspace users (other than military) about these provisions: military) about these provisions: National AIP Y National AIP Y National Military AIP NA National Military AIP NA EUROCONTROL eAIP Y EUROCONTROL eAIP Y Other: NA Other: NA
LSSIP Year 2013 Armenia 10 Released issue
Oversight
OAT GAT National oversight body for OAT: Air Force National Supervisory Authority (as per SES reg. 550/2004) for GAT services provided by the military: GDCA (there is no Military NSA).
Additional information: nil Additional information: nil
1.2.4.2 Service Provision role
OAT GAT Services Provided: Services Provided: En-Route Y En-Route NA Approach/TMA Y Approach/TMA NA Airfield/TWR/GND Y Airfield/TWR/GND NA AIS N AIS NA MET Y MET NA SAR Y SAR Y TSA/TRA monitoring Y FIS NA Other: Other:
Military ANSP providing GAT NA If YES, since: Duration of the services SES certified? Certificate: Certificate issued by: If NO, is this fact reported to the EC in accordance with SES regulations? Additional Information: Armenia is not yet an EU member State.
1.2.4.3 User role
IFR inside controlled airspace, Military aircraft OAT only N GAT only N Both OAT and GAT Y can fly?
If Military fly OAT-IFR inside controlled airspace, specify the available options: Free Routing N Within specific corridors only Y Within the regular (GAT) national route network Y Under radar control Y Within a special OAT route system Y Under radar advisory service N
If Military fly GAT-IFR inside controlled airspace, specify existing special arrangements: No special arrangements N Exemption from Route Charges N Exemption from flow and capacity (ATFCM) measures N Provision of ATC in UHF Y CNS exemptions: RVSM Y 8.33 Y Mode S Y ACAS Y Others:
LSSIP Year 2013 Armenia 11 Released issue
1.2.4.4 Flexible Use of Airspace (FUA)
Military in Armenia applies FUA requirements as specified in the Regulation No 2150/2005: Y FUA Level 1 implemented: Y FUA Level 2 implemented: Y FUA Level 3 implemented: Y
1.2.5 Accident/incident Investigation Body
1.2.5.1 Investigations Investigations following accidents and/or incidents are carried out by the provisional flight safety inspection body, which is subordinated directly to the Director General of the GDCA, moreover in exceptional cases the Government can designate a special investigation committee. The provisional flight safety inspection body is a public institution, it is not an autonomous decision making authority and it is settled as an independent body within the Civil Aviation System; therefore the objectivity of its dealings is assured as requested by Directive 94/56/EC. To guarantee an independent position, the provisional flight safety inspection body has been put under the direct surveillance of the Authority of the Director General of GDCA different from the regulation Deputy Director of GDCA. The provisional flight safety inspection body conducts investigations for Civil Aviation aircraft accidents and serious incidents. In case of non serious incidents they can task the service provider to conduct investigations on behalf of GDCA. In the frame of ARMATS SMS, all ATM related incidents should be investigated by ARMATS internally and relevant corrective actions implemented.
1.2.5.2 Collection, Evaluation & Processing of Data The service provider is tasked by the GDCA to collect, evaluate, process and store all ATM related information to civil aviation accidents, incidents and occurrences, as well as to make this information available to others. The investigating bodies issue safety recommendations as appropriate (with the exclusion of accidents and incidents to State aircraft) following its investigations, and/or whenever deemed appropriate conducts studies and surveys aimed at increasing flight safety. In order to carry out this function, TOKAI, the tool developed by EUROCONTROL, is used.
1.2.5.3 Civil-Military Accidents/Incidents Investigation of accidents and/or incidents involving Civil and Military are conducted by a joint body composed by experts from the Military Flight Safety Department, the GDCA and ARMATS.
LSSIP Year 2013 Armenia 12 Released issue Chapter 2 - En-route Traffic and Capacity
2.1 Evolution of traffic in Armenia
Armenia - Annual IFR Movements 100000 Armenia - Distribution (Ref. year 2012)
90000
80000
70000 Overflights 61% 60000 Domestic flights 0% 50000
IFR flights IFR 40000 IFR movements - Actuals
30000 IFR movements - Baseline forecast
20000 IFR movements - High forecast International Dep/Arr IFR movements - Low forecast 10000 39%
0 2009 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 2012.
2014-2018/19
The STATFOR medium-term forecast (MTF) predicts an average annual traffic growth between 5.2% and 8.8% for the planning period, with an average baseline growth of 6.9%.
2.2 YEREVAN ACC
2.2.1 Summer 2013 performance
En-route Delay (min/flight) Capacity Traffic Evolution 2013 Capacity Baseline Optimum All reasons Without weather gap
-8.4% 25 (0%) 0 0 0 No Capacity Plan : Sufficient Capacity to meet demand Comments
Summer 2013 performance assessment The ACC capacity baseline was measured with ACCESS. During the measured period, the average peak 1 hour demand was 12 and the average peak 3 hour demand was 9.
2.2.2 Planning Period 2014-2018/19 - Summer The planning focuses on the Summer season to reflect the most demanding period of the year from a capacity perspective. This approach ensures consistency with the previous planning cycles. The 2014-2018/19 summer capacity profile and delay breakdown has been derived according to the
LSSIP Year 2013 Armenia 13 Released issue following parameters: 2014: capacity requirement profiles based on the delay breakdown per ACC as provided in January 2011 2015-2018/19: Reference value based on the breakdown of a yearly European delay target of 0.5 min/flight
En-route ATFM delay breakdown - Reference Values UDDDCTA 2014 2015 2016 2017 2018 2019 Annual 0.06 0.01 0.01 0.01 0.01 0.01 Summer 0.09 0.01 0.01 0.01 0.01 0.01 Capacity Profiles 2013 Profiles (hourly movements and % increase over previous year) ACC baseline 2014 2015 2016 2017 2018 2019 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 2014 2015 2016 2017 2018 2019
Measures planned
Max sectors 1 1 1 1 1 1 Capacity Sufficient capacity to meet expected demand increase p.a. Reference profile 0% 0% 0% 0% 0% 0% (ACC) Additional
information
UDDDCTA - Reference capacity profile and alternative scenarios
30
25
20
15
10
5
Capacity profile (movements per hour) 0 2012 2013 2014 2015 2016 2017 2018 2019 2014-2019 Reference Capacity Profile 25 25 25 25 25 25 Capacity Profile - Current Routes 25 25 25 26 26 26 Capacity Profile - High 25 25 25 25 25 27 Capacity Profile - Low 25 25 25 25 25 25 Capacity Baseline 25 25 2014 - 2019 Plan 25 25 25 25 25 27
More information on the methodology related to capacity planning is available at : http://www.eurocontrol.int/sites/default/files/content/documents/nm/network‐operations/capacity‐assessment‐ planning‐guidance‐doc‐v2.8final.pdf
LSSIP Year 2013 Armenia 14 Released issue 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
To ensure that all Stakeholders report the expected completion REC-2012-03 All States dates as defined in their National business plans. Completion dates reported in the LSSIP are fully aligned with the National Business Reply by AM Plan 2014-2018. To ensure correct application of LSSIP guidance material and to REC-2012-05 All States implement the results of mandatory LSSIP in-cycle check. The LSSIP guidance material is fully applied and the results of the in-cycle check Reply by AM have been fully implemented. To ensure actions for overcoming present delays in the AL, AM, AZ, CY, CZ, DK, EE, FI, FR, GR, HR, HU, IT, REC-2012-10 implementation of basic ATSMHS capability (ESSIP objective LU, MAS, MD, MT, NO, SE, COM10). SI, UA
Reply by AM Armenia will implement ATSMHS in 2015.
States to ensure that appropriate actions are taken for BE, UK, SE, NO, FI, LV, PL, HU, UA, AM, TR, MK, FR, REC-2012-11 overcoming present delays in the implementation of priority PT, MT, RO, HR, BA, AL, capabilities specified in the ESSIP objective FCM03. SI, IT, CZ, MAS, CY. Priority capabilities of FCM03 have been implemented in the new ATM system put in Reply by AM service in 2013.
States are encouraged to speed up the AFP implementation and REC-2012-22 All States to schedule AFP testing with Network Manager.
Reply by AM AFP has been implemented in the new ATM system put in service in 2013.
ANSPs are encouraged to publish more APV routes. REC-2012-40 All ECAC ANSPs
Reply by AM APV Routes already published for Zvartnots International Airport
LSSIP Year 2013 Armenia 15 Released issue Chapter 4 - National Projects
The main projects currently ongoing in Armenia are depicted in the table below.
Name Schedule Description – Scope Status Link with Expected Contribution to the Key European Master Performance Areas2 Plan. P3D Expansion From: Mar 2014 Expansion of the infrastructure over the whole territory Planned ITY-SPI Capacity and safety improvement and Upgrade To: Dec 2015 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) .
ATIS From: Jan 2014 Procurement and installation of the new ATIS system Planned OI Step IS-0401 Safety improvement To: Dec 2014 with D-ATIS possibility. AMHS From: Jan 2015 Procurement and installation of AMHS system. Planned COM 10 Cost-efficiency and safety improvement To: Dec 2015 CPDLC From: Jan 2014 Implementation of CPDLC Started ITY-AGDL Capacity and safety improvement To: Dec 2015 NAV From: Jan 2016 Rationalisation of the navigation infrastructure. Planned Enabler CTE-N5a Cost-efficiency improvement Rationalisation To: Dec 2017 Installation of new DMEs. Installation at the airport a new D-VOR / DME. ATC technical From: Sep 2012 “Aeronautical Data Set for ATC System Using EAD Started OI Step IS-0204 Safety and cost-efficiency improvement system To: Apr 2014 Database” document and catalogue preparation. QMS From: Jan 2014 Activation of the implemented quality management Planned ITY-ADQ Safety and cost-efficiency improvement to Dec 2016 system, which will allow to have fully regulated documentation and change management and safety assessment procedures. AIS From: Sep 2014 Transition from aeronautical information service concept Planned ITY-ADQ Safety and cost-efficiency improvement To: Dec 2017 (AIS) to aeronautical information management concept (AIM) AIS From: Sep 2014 Monitoring of quality and completeness of the digital Planned ITY-ADQ Safety and cost-efficiency improvement To: Apr 2017 aeronautical data. AIS From: Sep 2014 Creation and maintenance of the digital data for charting Planned ITY-ADQ Safety and cost-efficiency improvement To: Apr 2017
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 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
Chapter 6 - ESSIP Objective Implementation
Conventions Two colour codes are used for each ESSIP Objective ‘box’: o one colour code is used to show the Objective Scope in the Objective ID cell, and o another colour code is used to show the Objective Progress in the State and for each national stakeholder.
Obj. ID (*) Obj. Title (By mm/yyyy of overall objective, inc non-State SloAs) Obj. Progress (**) State’s high level progress statement State Impl. Date REG APO. Progress (**) REG high level progress statement (By:mm-yyyy) APO Impl. Date ASP ASP. Progress (**) ASP high level progress statement (By:mm-yyyy) ASP Impl. Date MIL MIL. Progress (**) MIL high level progress statement (By:mm-yyyy) MIL Impl. Date APO APO. Progress (**) APO high level progress statement (By:mm-yyyy) APO Impl. Date
(*) Objective Scope Code: (**) Objective/Stakeholder Progress Code: ECAC Completed No Plan EU+ Partly Completed Not Applicable Multi-N Planned Missing Data APT Late
LSSIP Year 2013 Armenia 18 Released issue
Harmonise Operational Air Traffic (OAT) and General Air [IDP] No Plan AOM13.1 Traffic (GAT) handling (By:12/2018) [Essential] 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.
There are established OAT/GAT handling rules and procedures; they are No Plan REG not based on EUROAT. Conformance analysis and possible amendments (By:12-2018) of the existing rules/procedures will be addressed in 2014/2015. ‐ Objective will be reviewed after the conformance analysis. There are established OAT/GAT handling rules and procedures; they are No Plan ASP not based on EUROAT. Conformance analysis and possible amendments (By:12-2018) of the existing rules/procedures will be addressed in 2014/2015. ‐ Objective will be reviewed after the conformance analysis. There are established OAT/GAT handling rules and procedures; they are No Plan MIL not based on EUROAT. Conformance analysis and possible amendments (By:12-2018) of the existing rules/procedures will be addressed in 2014/2015. ‐ Objective will be reviewed after the conformance analysis.
Implement Advanced Airspace Management [IDP] Planned AOM19 (By:12/2016) [Essential] There is flexible use of airspace based on procedures. The implementation of an automated system is 12/2015 under consideration, will be addressed after 2014. There is flexible use of airspace based on procedures. The Planned ASP implementation of an automated system is under consideration, will be (By:12-2015) addressed after 2014. 12/2015 There is flexible use of airspace based on procedures. The Planned MIL implementation of an automated system is under consideration, will be (By:12-2015) addressed after 2014. 12/2015
Implement ATS Route Network (ARN) - Version 7 Completed AOM20 (By:10/2013) [Essential]
Armenia is involved in RNDSG. ARN version 7 has been implemented. 10/2013
ASP The airspace structure change (route/sector and terminal airspace) is the Completed (By:10-2013) responsibility of ARMATS. 10/2013 The airspace structure change (route/sector and terminal airspace) is the Completed MIL responsibility of ARMATS; done through collaboration with Military (By:10-2013) authorities. 10/2013
Not Implementation of Free Route Airspace (By:12/2017) [IDP] AOM21 Applicable (Outside Applicability Area) [Essential]
Armenia is not in the applicability area of the objective. ‐
REG Not Applicable Armenia is not in the applicability area of the objective. (By:12-2017) ‐
ASP Not Applicable Armenia is not in the applicability area of the objective. (By:12-2017) ‐
MIL Not Applicable Armenia is not in the applicability area of the objective. (By:12-2017) ‐
LSSIP Year 2013 Armenia 19 Released issue
Implement airside capacity enhancement method and Not
AOP01.2 best practices based on Eurocontrol capacity and Applicable
efficiency implementation manual (By:12/2013) UDYZ - Yerevan (Outside Applicability Area)
Armenia is not part of the applicability area. ‐ No airport capacity problem foreseen within the timeframe covered by present LSSIP. No airport capacity problem foreseen within the timeframe covered by Not Applicable ASP the present LSSIP. (By:12-2011) Armenia is not part of the applicability area. ‐ No airport capacity problem foreseen within the timeframe covered by Not Applicable APO the present LSSIP. (By:12-2011) Armenia is not part of the applicability area. ‐
Improve runway safety by preventing runway incursions Completed AOP03 (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. 12/2013 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.
REG GDCA has decided upon the strategy for implementation at Zvartnots Completed (By:12-2013) International Airport of specific actions contained in the EAPRI document. 12/2013
ASP Voice communications between the tower and drivers are not conducted Completed (By:12-2013) in English. 12/2013
MIL Military authorities do not provide ATC service to civil flights. Not Applicable (By:12-2013) Military flights operate as GAT on Zvarnots airport. ‐
APO The airport SMS is approved by the regulatory body and it is operational. Completed (By:12-2013) Drivers on the runway do not speak English. 12/2013
LSSIP Year 2013 Armenia 20 Released issue
Not Implement Advanced Surface Movement Guidance and AOP04.1 Applicable Control System (A-SMGCS) Level1 (By:12/2011) [Essential]
UDYZ - Yerevan (Outside Applicability Area) UDYZ is not within the applicability area of the objective. However the deployment of A‐SMGCS based on multilateration may be considered in the future. ‐ The installation of a primary surveillance is not foreseen. There is in average 20 days of bad visibility per year.
REG When the ANSP and the Airport have decided to implement an A‐SMGCS Not Applicable (By:12-2010) system, the regulator will take the required actions. ‐
ASP Not Applicable There is in average 20 days per year of bad visibility. (By:12-2011) ‐
MIL Not Applicable Military airports do not provide ATC service to civil flights. (By:12-2010) ‐
APO There is in average 20 days per year of bad visibility for CAT II conditions Not Applicable (By:12-2010) and less than 10 days per year for CAT III conditions. 12/2015
Not Implement Advanced Surface Movement Guidance and AOP04.2 Applicable Control System (A-SMGCS) Level 2 (By:12/2017)
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.
REG Armenia is not part of the applicability area; however, this objective is Not Applicable (By:12-2017) under review for its possible implementation. ‐
ASP Armenia is not part of the applicability area; however, this objective is Not Applicable (By:12-2017) under review for its possible implementation. ‐
APO Armenia is not part of the applicability area; however, this objective is Not Applicable (By:12-2017) under review for its possible implementation. ‐
Not Implement Airport Collaborative Decision Making (CDM) [IDP] AOP05 Applicable (By:01/2016) [Essential]
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.
ASP Not Applicable Armenia is not part of the applicability area. (By:01-2016) ‐
MIL Not Applicable Military airports do not provide service to civil flights. (By:01-2016) ‐
APO Not Applicable Armenia is not part of the applicability area. (By:01-2016) ‐
LSSIP Year 2013 Armenia 21 Released issue
Implement ground based safety nets - Short Term Completed ATC02.2 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. 12/2013 Implementation of procedures and training of controllers is done.
REG Completed GDCA has verified the new system. (By:01-2013) 12/2013
ASP In Yerevan FIR, the ATM system ‐Galaxy‐ has the STCA level 2 Completed (By:01-2013) implemented and operational. 12/2013
MIL Military ATC units do not provide area radar services. Not Applicable (By:01-2013) They do not provide ATC service to Civil flights. ‐
Implement ground based safety nets - Area Proximity Completed ATC02.5 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. 12/2013 Implementation of procedures and training of controllers is done.
ASP Completed ARMATS has installed the ATM system with APW level 2 capability. (By:12-2016) 12/2013
MIL Not Applicable Military do not provide air traffic service to civil flights. (By:12-2016) ‐
Implement ground based safety nets - Minimum Safe Completed ATC02.6 Altitude Warning - level 2 (By:12/2016) [Essential] The ATM system ‐Galaxy‐ has the Minimum Safe Altitude Warning level 2 implemented and operational 12/2013 in Yerevan ACC and Yerevan TMA.
ASP Completed ARMATS has installed the new ATM system with MSAW level 2 capability. (By:12-2016) 12/2013
MIL Not Applicable Military do not provide air traffic service to civil flights. (By:12-2016) ‐
Implement ground based safety nets - Approach Path Completed ATC02.7 Monitor - level 2 (By:12/2016) [Essential]
The ATM system ‐Galaxy‐ has the APM level 2 implemented and operational. 12/2013
ASP Completed ARMATS has installed the ATM system with APM level 2 capability. (By:12-2016) 12/2013
MIL Not Applicable Military do not provide air traffic service to civil flights. (By:12-2016) ‐
LSSIP Year 2013 Armenia 22 Released issue
Not Implement arrival management tools (By:12/2015) ATC07.1 Applicable (Outside Applicability Area) [Essential]
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 Not Applicable Armenia is not part of the applicability area. (By:12-2015) ‐
Implement automated support for conflict detection and Completed ATC12 conformance monitoring (By:12/2016) [Essential]
The ATM system ‐Galaxy‐ has the MTCD and MONA functions implemented and operational. 12/2013
REG The new ATM system has the MTCD and MONA functions implemented Completed (By:12-2016) and operational 06/2013
ASP ARMATS has installed the new ATM system and implemented the MTCD Completed (By:12-2016) and MONA functions. 12/2013
Implement, in En-Route operations, information Not exchange mechanisms, tools and procedures in support [IDP] ATC15 Applicable of Basic AMAN operations (By:12/2017) [Essential]
(Outside Applicability Area)
Taking into account the forecast traffic levels, no need to implement this Objective has been identified. ‐
REG Taking into account the forecast traffic levels, no need to implement this Not Applicable (By:12-2017) Objective has been identified. ‐
ASP Taking into account the forecast traffic levels, no need to implement this Not Applicable (By:12-2017) Objective has been identified. ‐
Implement ACAS II compliant with TCAS II change 7.1 Planned ATC16 (By:12/2015)
It will be implemented in due time. For more details, see the comments at Stakeholder level. 12/2014
REG Planned Will be implemented in due time. (By:12-2015) 12/2014
ASP Completed It is implemented. (By:03-2012) 01/2012
MIL Not Applicable Not applicable as the retrofit is not justified in term of benefits. (By:12-2015) ‐
LSSIP Year 2013 Armenia 23 Released issue
Electronic Dialogue as Automated Assistance to [IDP] Planned ATC17 Controller during Coordination and Transfer [Essential] (By:12/2018) The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are implemented in the new ATC 01/2015 system since 2013.
REG Planned ‐ (By:12-2018) 01/2015
ASP The Basic Procedure Messages ABI, ACT, REV, PAC, MAC and LAM are Planned (By:12-2018) implemented in the new ATC system since 2013. 01/2015
Migrate ground international or regional X.25 data Partly [IDP] COM09 networks or services to the Internet Protocol (IP) Completed
(By:12/2014)
The current network is based on IP v4. There is a plan to upgrade to IP v6. 12/2014 The new ATC system has the capability of IP v6.
Completed REG The GDCA notified ARMATS of the mandate to migrate to IP v6. (By:12-2010) Once the IPv6 will be implemented the GDCA will conduct the oversight. 12/2010
Partly ASP The new ATC system has the capability of IP v6. Completed (By:12-2014) 12/2014
MIL Not Applicable Military do not provide ATC service to civil flights (By:12-2014) ‐
Late COM10 Migrate from AFTN to AMHS (By:12/2014)
The ATM system has an AMHS capability. The migration of the AFTN system to AMHS is foreseen through the existing COM centre upgrade. Yet the operational use will be addressed at regional level with 12/2015 connected MTA (Message Transfer Agent).
ASP Late ARMATS will upgrade the COM centre to implement AMHS. (By:12-2014) 12/2015
MIL Not Applicable Military authorities do not control Civil flights. (By:12-2014) ‐
Partly Implementation of Voice over Internet Protocol (VoIP) in COM11 Completed ATM (By:12/2020)
The new VCS system has capability to use Voice over IP. It will be used in case of the neighbour centres 12/2015 will have such capability.
REG Completed The ARMATS new VCS system has capability to use Voice over IP. (By:12-2018) 12/2013
Partly ASP The ARMATS new VCS system has capability to use Voice over IP. Completed (By:12-2020) 12/2015
MIL Not Applicable Military do not provide ATC service to Civil flights (By:12-2020) ‐
LSSIP Year 2013 Armenia 24 Released issue
Implement Continuous Descent Operations (CDO) [IDP] Completed ENV01 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. 12/2009 All procedures including SIDs and STARs are designed aiming at minimising the environmental impact. CDA approaches are published in the AIP.
ASP Completed BCDA procedures are applied in Armenia. (By:12-2013) 12/2009
APO Completed BCDA procedures are applied in Armenia. (By:12-2013) 12/2009
Implement Collaborative Environmental Management Completed ENV02 (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 12/2009 formal status and a TOR, it meets only when needed to address specific issues. The main task of the Environment unit is the noise abatement and airfield fuel and emissions reduction. ARMATS cooperates with the Airport and Aircraft Operators in order to Completed ASP facilitate a joint approach contributing to the minimisation of noise and (By:12-2016) gaseous emissions resulting from aircraft operations. 12/2009
MIL Not Applicable Military airports do not provide ATC service to civil flights. (By:12-2015) ‐ The airport has an Environment Manager with clearly defined action plan. Completed APO The main task of the Environment unit is the noise abatement and airfield (By:12-2016) fuel and emissions reduction. 12/2009
Implement enhanced tactical flow management services Late FCM01 (By:12/2006) [Essential] Armenia is in the IFPS Zone. The ATC system is not connected to CFMU. The new system will have all the 12/2014 required connections with CFMU.
ASP Armenia migrated to the IFPS Zone on the 21 December 2006. Late (By:12-2006) The new system will have all the required connections with CFMU. 12/2014
MIL Not Applicable Military do not provide air traffic service to civil flights. (By:12-2001) ‐
LSSIP Year 2013 Armenia 25 Released issue
[IDP] Planned FCM03 Implement collaborative flight planning (By:12/2015) [Essential]
Armenia is in the IFPS Zone. Currently the connection with CFMU is ensured through the FMP; the ATC system is not connected to 12/2014 CFMU. The new system will have all the required connections with CFMU.
Planned ASP The new system will have all the required connections with CFMU. Modernisation (By:12-2015) of YEREVAN 12/2014 ACC
MIL Not Applicable Military do not provide air traffic service to civil flights. (By:12-2015) ‐
Implementation of Short Term ATFCM Measures - phase Not [IDP] FCM04 1 (By:12/2015) Applicable [Essential] (Outside Applicability Area)
Armenia is not in the applicability area of the objective. ‐
REG Not Applicable Armenia is not in the applicability area of the objective. (By:12-2015) ‐
ASP Not Applicable Armenia is not in the applicability area of the objective. (By:12-2015) ‐
[IDP] No Plan FCM05 Implementation of interactive rolling NOP (By:12/2016) [Essential]
Objective not yet reviewed ‐
REG No Plan ‐ (By:12-2016) ‐
ASP No Plan ‐ (By:12-2016) ‐
MIL No Plan ‐ (By:12-2016) ‐
APO No Plan ‐ (By:12-2016) ‐
Completed 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 2007. 01/2007 Terminal and Integrated Briefing function at international airports of Armenia are provided. It is also accessible through Internet as of March 2007.
ASP Completed The integrated briefing level 5 is implemented. (By:12-2012) 01/2007
MIL There is only one AIS office in Armenia which is managed by ARMATS. Not Applicable (By:12-2012) Military are clients of this office. ‐
LSSIP Year 2013 Armenia 26 Released issue
Ensure quality of aeronautical data and aeronautical Planned ITY-ADQ information (By:07/2017) [Essential] (Outside Applicability Area) Implementation started in 2007; the data integrity guidance material in local working and quality 12/2016 procedures/processes as well as the service level agreements with main actors are implemented.
REG The regulator is adopting required documentations for the Planned (By:07-2017) implementation of ADQ 12/2016 ARMATS implemented end‐to‐end integrity of aeronautical data during Planned ASP 2009. (By:07-2017) The implementation of ADQ has started. 12/2016
MIL There is only one AIS office in Armenia which is managed by ARMATS. Not Applicable (By:07-2017) Military are clients of this office. ‐
APO Planned Airport has quality management system, and is implementing ADQ (By:07-2017) 12/2016
Initial ATC air-ground data link services above FL-285 [IDP] Planned ITY-AGDL (By:02/2015) [Essential] (Outside Applicability Area) Armenia is not in the applicability area of the objective. However, the ‐Galaxy‐ ATM system installed In Yerevan ATC centre, has the capability. The testing is planned in 2014. 02/2015 The operational use remains dependent on the neighbouring ACCs‐ capabilities.
REG The GDCA will conduct oversight once the system is installed Planned (By:02-2015) REG02 has been delegated to EUROCONTROL. 02/2015
ASP Planned ARMATS plans to implement Air/Ground data link services (By:02-2015) 02/2015
MIL There is no intention to equip the transport‐type State aircraft with data Not Applicable (By:-) link equipment ‐
Implement air-ground voice channel spacing Not ITY- requirements below FL195 (By:12/2020) Applicable AGVCS2 (Outside Applicability Area)
Armenia is not in the applicability area of the objective. ‐
REG Not Applicable Armenia is not in the applicability area of the objective. (By:12-2018) ‐
ASP Not Applicable Armenia is not in the applicability area of the objective. (By:12-2018) ‐
MIL Not Applicable Armenia is not in the applicability area of the objective. (By:12-2020) ‐
APO Not Applicable Armenia is not in the applicability area of the objective. (By:12-2018) ‐
LSSIP Year 2013 Armenia 27 Released issue
Partly Implementation of ground-ground automated co- ITY-COTR ordination processes (By:02/2015) Completed [Essential] (Outside Applicability Area)
The new ‐Galaxy‐ ATM system has the capability. The operational use remains dependent on the neighbouring ACCs‐ capabilities. Currently, none of the 12/2013 neighbouring ACCs is capable.
REG Completed ‐ (By:12-2012) 12/2013
The new ‐Galaxy‐ ATM system has the capability. Partly ASP The operational use remains dependent on the neighbouring ACCs‐ Completed (By:02-2015) capabilities. Currently, none of the neighbouring ACCs is capable. 12/2013
MIL Not Applicable Military do not provide ATC service to civil flights (By:12-2012) ‐
Partly Apply a common flight message transfer protocol [IDP] ITY-FMTP Completed (FMTP) (By:12/2014)
The new Galaxy ATM system has the capability. Has to be addressed at regional level. The operational use remains dependent on the neighbouring ACCs‐ 12/2014 capabilities. Currently, none is capable. For the time being there are no firm plans for operational use.
Partly REG GDCA will exercise its role in due time. Completed (By:12-2014) 12/2014
Partly
ASP The new Galaxy ATM system has the capability, yet it has to be Completed (By:12-2014) implemented at regional level. 12/2014
MIL Not Applicable Military do not provide ATC service to civil flights (By:12-2014) ‐
Surveillance performance and interoperability Not
ITY-SPI (By:12/2019) Applicable
(Outside Applicability Area) The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002), MLAT (CAT‐034, CAT‐048) and ATC system by ASTERIX protocols with time stamping was implemented in 2008. ‐ The ASTERIX protocol CAT‐062 is implemented on the new ‐Galaxy‐ ATM system. The operational use remains dependent on the neighbouring ACCs‐ capabilities.
REG Not Applicable ‐ (By:12-2013) ‐ The upgrading of TMA and En‐route radars (CAT‐001, CAT ‐002), MLAT Not Applicable (CAT‐034, CAT‐048) and ATC system by ASTERIX protocols with time stamping was implemented in 2008. ASP The ASTERIX protocol CAT‐062 is implemented on the new ‐Galaxy‐ ATM (By:02-2015) system. ‐ The operational use remains dependent on the neighbouring ACCs‐ capabilities.
MIL Not Applicable Equipage of military fleet is not economically justified. (By:12-2019) ‐
LSSIP Year 2013 Armenia 28 Released issue
Completed NAV03 Implementation of P-RNAV (By:12/2012) [Essential]
The implementation was done in 2012. In summer 2007, B‐RNAV was implemented in the upper airspace (Above FL 195) of Armenia. 12/2012 All co‐ordinates for the publication in the AIP are prepared in WGS‐84 format, in line with the accuracy and integrity requirements specified in ICAO Annex 15.
REG Navigation databases are only available from accredited suppliers with Completed (By:01-2005) suitable quality assurance procedures in place. 12/2009
Completed All co‐ordinates for the publication in the AIP are prepared in WGS‐84 AIP and eAIP of ASP format, in line with the accuracy and integrity requirements specified in the Republic of (By:12-2012) ICAO Annex 15. Armenia / 12/2012 The implementation of P‐RNAV was completed in 2012. Navigation Aids Modernisation
MIL Not Applicable Military do not provide ATC service to civil flights (By:12-2012) ‐
[IDP] Completed NAV10 Implement APV procedures (By:12/2016) [Essential] The APV Baro‐VNAV procedures at Zvartnots airport is already implemented, the safety case was 12/2012 developed and submitted to NSA, the subsequent approval has been given.
REG In 2011 the GDCA has published national regulatory APV procedures, and Completed (By:04-2016) approved APV safety case and APV operations. 03/2011 The APV Baro‐VNAV procedures at Zvartnots airport is already Completed ASP implemented, the safety case was developed and submitted to NSA, the (By:12-2016) subsequent approval has been given. 12/2012
MIL Military do not have any plan and agreements with Civil ANSP and Not Applicable (By:12-2016) Airports to use APV Baro‐VNAV operations ‐
Implement measures to reduce the risk to aircraft Completed SAF10 operations caused by airspace infringements
(By:12/2011)
The European action plan is implemented. 12/2012
REG Completed GDCA is involved in the development of the implementation plan. (By:12-2011) 12/2012
ASP Completed All the applicable measures were implemented (By:12-2011) 12/2012
MIL Not Applicable Military are consulted. (By:12-2011) 12/2012
LSSIP Year 2013 Armenia 29 Released issue
Improve runway safety by preventing runway excursions No Plan SAF11 (By:01/2018)
Still under consideration. No implementation plan defined yet. 01/2018
REG No Plan Still under consideration. (By:01-2018) 01/2018
ASP No Plan Still under consideration. (By:12-2014) 12/2014
MIL Not Applicable Military authorities do not provide ATC service to civil flights. (By:01-2018) ‐
APO No Plan Still under consideration. (By:12-2014) 12/2014
SRC- Implementation of Safety Oversight of Changes to ATM Completed CHNG by National Supervisory Authorities (NSA) (By:12/2010)
Implemented and amended in 2009. 12/2009
REG Implemented and amended in 2009. Completed (By:12-2010) GDCA: http://www.aviation.am 12/2009
MIL Military do not provide ATM service to civil flights and military systems Not Applicable (By:12-2010) are not used for the provision of services by ARMATS. ‐
SRC- Implement the EUROCONTROL Safety Regulatory Completed RLMK Requirements (ESARRs) (By:12/2010)
ESARRs are fully implemented at the exception of ESARR 6 that is only partially implemented. 12/2009 The GDCA has implemented ESARRs by adopting / transposing into Completed REG national law and ensures regular updates by introducing new (By:12-2010) amendments. 12/2009
MIL Not Applicable Military do not provide ATM service to civil flights (By:12-2010) ‐
SRC- Safety Levels and Resolution of Deficiencies Completed SLRD (By:12/2010) The mechanism to collect, evaluate process and store occurrences in aviation (including ATM) is 12/2012 implemented and operational but the Just Culture environment is not ensured. National regulations have been formally promulgated / published to Completed transpose ESARR 2 into the national legal order. REG The governmental order 1777 of Jan. 2004 has been enacted and is based (By:12-2010) on ICAO Annex 13. A national legislation containing detailed 12/2012 requirements of ESARR 2 has been completed and approved by the GDCA December 2004.
MIL Military do not provide ATM service to civil flights Not Applicable (By:12-2010)
LSSIP Year 2013 Armenia 30 Released issue
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 Mr. Sergey NALBANDYAN International Airports LSSIP Contact Person for Armenia EUROCONTROL Mr. Octavian CIOARA
Part - ESSIP Objective Implementation ESSIP EUROCONTROL Objective Owners EUROCONTROL National Stakeholder Specialist(s) Objective EIPR Objective Coordinator
AOM13.1 R. BUCUROIU, O. MROWICKI, E. A. DYBOWSKA Mr. Arthur PAPOYAN REUBER Mr. Sergey DANIELYAN AOM19 A. DYBOWSKA Mr. Arthur PAPOYAN G. ACAMPORA, O. MROWICKI Mr. Sergey DANIELYAN AOM20 A. DYBOWSKA Mr. Arthur PAPOYAN R. BUCUROIU Mr. Sergey DANIELYAN AOM21 A. DYBOWSKA Mr. Arthur PAPOYAN R. BUCUROIU Mr. Sergey DANIELYAN AOP01.2 P. VRANJKOVIC Mr. Sergey DANIELYAN P. ADAMSON Mr. Sergey NALBANDYAN AOP03 P. VRANJKOVIC Mr. Sergey DANIELYAN P. JOPPART, T. LICU Mr. Sergey NALBANDYAN AOP04.1 P. VRANJKOVIC Mr. Gevorg SIMONYAN P. ADAMSON Mr. Sergey NALBANDYAN AOP04.2 P. VRANJKOVIC Mr. Gevorg SIMONYAN P. ADAMSON Mr. Sergey NALBANDYAN AOP05 P. VRANJKOVIC Mr. Sergey DANIELYAN P. ADAMSON Mr. Sergey NALBANDYAN ATC02.2 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Sergey DANIELYAN ATC02.5 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Sergey DANIELYAN ATC02.6 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Sergey DANIELYAN ATC02.7 I. FEIJT Mr. Samvel BAGHDASARYAN B. BAKKER, S. DROZDOWSKI Mr. Harutyun BABAYAN ATC07.1 L. DELL’ORTO Mr. Samvel BAGHDASARYAN P. CONROY, P. TERZIOSKI Mr. Sergey DANIELYAN ATC12 L. DELL’ORTO Mr. Samvel BAGHDASARYAN P. TERZIOSKI Mr. Sergey DANIELYAN ATC15 L. DELL’ORTO Mr. Samvel BAGHDASARYAN P. CONROY, P. TERZIOSKI Mr. Sergey DANIELYAN ATC16 S. DROZDOWSKI L. DELL’ORTO Mr. Samvel BAGHDASARYAN
LSSIP Year 2013 Armenia 31 Released issue
ESSIP EUROCONTROL Objective Owners EUROCONTROL National Stakeholder Specialist(s) Objective EIPR Objective Coordinator Mr. Aram TUNYAN ATC17 L. DELL’ORTO Mr. Samvel BAGHDASARYAN S. MORTON 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 B. HILL Mr. Sergey DANIELYAN P. ADAMSON Mr. Sergey NALBANDYAN ENV02 B. HILL Mr. Sergey DANIELYAN S. MAHONY, A. WATT Mr. Sergey NALBANDYAN FCM01 O. CIOARA Mr. Galust Poghosyan H. KOOLEN Mr. Arthur PAPOYAN FCM03 O. CIOARA Mr. Galust Poghosyan S. SMIDT Mr. Arthur PAPOYAN FCM04 O. CIOARA Mr. Galust Poghosyan M. RICHARD Mr. Arthur PAPOYAN FCM05 O. CIOARA Mr. Galust Poghosyan N. AGACDIKEN 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 O. ALFARO Mr. Arthur PAPOYAN TBD Mr. Gevorg SIMONYAN ITY-COTR S. MORTON L. DELL’ORTO Mr. Samvel BAGHDASARYAN ITY-FMTP L. POPESCU O. ALFARO Mr. Gevorg SIMONYAN ITY-SPI M. BORELY, R. STEWART O. CIOARA Mr. Gevorg SIMONYAN NAV03 A. KOKONA Mr. Artur ALAVERDYAN F. PAVLICEVIC Mr. Partev MAMIKONYAN NAV10 A. KOKONA Mr. Artur ALAVERDYAN R. FARNWORTH 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
Annex B – National Stakeholders Organisation Charts
Aviation Joint Stock Companies
Aviation Training Centre Avia-Medical Centre ARMATS Air Operators
State Enterprise State Enterprise (ARM. Reg)
ARMATS
LSSIP Year 2013 Armenia 33 Released issue
ZVARTNOTS AND SHIRAK AIRPORTS ADMINISTRATION (AIA) - ORGANIZATION CHART
General Manager
Maintenance Manager (1) Operation Manager (1) Security Manager (1)
Ground Handling Manager(1) Safety Manager (1) Shift Manager & Land Side (5) Check in Manager (1)
Training & License(1)
Resource Allocator (4) Radio Ground (4)
Ramp Control & Follow Me (8) Operative Information Office (5)
LSSIP Year 2013 Armenia 34 Released issue
Annex C – Glossary of Abbreviations
Specific abbreviations for Armenia:
AIA – Armenian International Airports ARMATS – Armenian Air Traffic Services GDCA – General Department of Civil Aviation
LSSIP Year 2013 Armenia 35 Released issue