Local Single Sky ImPlementation (LSSIP)

Year 2013 ­­­‑ Level 1

DOCUMENT IDENTIFICATION SHEET

LSSIP for LATVIA

Infocentre Reference: 14/01/07-23

Document Identifier Edition: Year 2013

LSSIP Year 2013 LATVIA Edition Date: 22/05/14

LSSIP Focal Point - Erika NEIMANE E-mail: Head of ATM [email protected] Section

LSSIP Contact Person - Luca DELL’ ORTO 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\Latvia (LV)\Year 2013\Released\LSSIP Year 2013_LV 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: www.eurocontrol.int/statfor 5. Acronyms and abbreviations: http://www.eurocontrol.int/articles/glossaries 6. European ATM Master Plan: www.atmmasterplan.eu 7. LSSIP Documents: http://www.eurocontrol.int/articles/lssip 8. National AIP: https://ais.lgs.lv/Latvian%20eAIP

LSSIP Year 2013 Latvia Released Issue

APPROVAL SHEET

LSSIP Year 2013 Latvia Released Issue

TABLE OF CONTENTS

Executive Summary ...... 1 Introduction ...... 3 Chapter 1 - National ATM Environment ...... 4 1.1 Geographical Scope ...... 4 1.1.1 International Membership ...... 4 1.1.2 Geographical description of the FIR(s) ...... 4 1.1.3 Airspace Classification and Organisation ...... 5 1.2 National Stakeholders ...... 5 1.2.1 Civil Regulator(s) ...... 6 1.2.2 Air Navigation Service Provider ...... 7 1.2.3 Airports ...... 8 1.2.4 Military Authorities ...... 8 1.2.5 Accident/incident Investigation Body ...... 11 Chapter 2 - En-route Traffic and Capacity ...... 12 2.1 Evolution of traffic in Latvia ...... 12 2.2 RIGA ACC ...... 13 2.2.1 Traffic and en-route ATFM delays 2009-2018/19 ...... 13 2.2.2 Summer 2013 performance ...... 13 2.2.3 Planning Period 2014-2018/19 - Summer ...... 13 Chapter 3 - ESSIP Report recommendations ...... 15 Chapter 4 - National Projects ...... 17 Chapter 5 - Regional Co-ordination ...... 19 5.1 FAB Co-ordination ...... 19 5.2 FAB Projects ...... 20 5.3 Other regional coordination projects ...... 20 Baltic Integration ...... 20 The Borealis Alliance Framework Agreement ...... 21 Chapter 6 - ESSIP Objective Implementation ...... 22

ANNEXES

LSSIP Year 2013 Latvia Released Issue

Executive Summary

State Context Since the establishment of the Northern European Functional Airspace Block (NEFAB) in December of 2012, consistent efforts have been contributed towards planned implementation of the free route airspace in NEFAB member states’ airspace in 2015. Implementation of appropriate airspace planning support tools has been initiated to improve airspace use efficiency.

ESSIP Objective Implementation Latvia has completed or plans to complete in the required time frame majority of the objectives. A couple of objectives pertaining to implementation of upgraded versions of the ground safety nets are under consideration and would be included in the planning process during spring 2014.

* FOC Date LSSIP 2013 - Latvia █ 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) * 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] *

LSSIP Year 2013 Latvia 1 Released Issue * FOC Date LSSIP 2013 - Latvia █ Planned implementation date (see legend at the bottom of the table)

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 *

Airport-related ESSIP Objectives

2013 2014 2008 2009 2010 2011 2012 2015 2016 2017 2018 2019 2020 <=2007

EVRA-Riga 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 *

Understanding the Table

Objective Completed No Plan

Objective Partly Completed Missing Data

Objective Planned Not Applicable (Latvia/Riga Airport does not participate in this obj.)

Late

NOTE: The year where the coloured box is placed indicates the ‘Implementation Completion Date’ as stated in the ESSIP for each objective. The colour-code indicates the Local progress with respect to this date.

LSSIP Year 2013 Latvia 2 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 Latvia 3 Released Issue

Chapter 1 - National ATM Environment

1.1 Geographical Scope

1.1.1 International Membership Latvia is a Member of the following international organisations in the field of ATM:

Organisation Since ECAC  1993 EUROCONTROL  1 January, 2011 European Union  1 May, 2004 European Common Aviation Area  1 May, 2004 EASA  1 May, 2004 ICAO  13 July, 1992 JAA  July, 1998 NATO  29 March, 2004

1.1.2 Geographical description of the FIR(s) The geographical scope of this document addresses the RIGA FIR. RIGA FIR is surrounded by FIRs of 5 States, namely Estonia, Russian Federation, Belarus, Lithuania and . Adjacent FIR/UIRs of ECAC States:  North - Tallinn FIR/UIR (Estonia);  West - Malmö and Stockholm FIRs/UIRs (Sweden);  South - Vilnius FIR/UIR (Lithuania). Adjacent FIR/UIRs of non-ECAC States:  East - Sankt-Peterburg FIR/UIR (Russian Federation);  Southeast - Minsk FIR/UIR (Belarus)

LSSIP Year 2013 Latvia 4 Released Issue 1.1.3 Airspace Classification and Organisation The current classification of Latvian airspace is outlined below:  FIR: GND - UNL  RIGA CTA: FL 095 - FL 460

1.2 National Stakeholders The main National Stakeholders involved in ATM in Latvia are the following: • National Supervisory Authorities: - The Department of Air Transport of the Ministry of Transport (MoT); - Civil Aviation Agency of Latvia (LCAA); • Transport Accident and Incident Investigation Bureau; • Air Navigation Services Provider State Joint Stock Company “Latvijas Gaisa Satiksme” (LGS); • Riga International Airport; • The Ministry of Defence (MoD) National Armed Forces; • The Ministry of Internal Affairs (Border Guard). Their activities are detailed in the following sub-chapters and their relationships are shown in the diagram below.

LSSIP Year 2013 Latvia 5 Released Issue

1.2.1 Civil Regulator(s)

1.2.1.1 General information Civil Aviation in Latvia is the responsibility of the Ministry of Transport. The different national entities having regulatory responsibilities in ATM are summarised in the table below. The LCAA is further detailed in the following sections.

Activity in ATM: Organisation responsible Legal Basis Rule-making Cabinet of Ministers Constitution Safety Oversight LCAA Law on Aviation Establishment of Tolerable LCAA CAA Directive N 01-08/974- (20.09.2013.) Safety Levels Safety Performance Monitoring LCAA Law on Aviation Enforcement actions in case of LCAA Law on Aviation non-compliance with safety regulatory requirements Airspace LCAA Cabinet of Ministers regulation N° 507(28.06.2011.) and Law on Aviation Economic Department of Cabinet of Ministers regulation N° 991 Air Transport (MoT) (5.12.2006.) and Law on Aviation Environment LCAA Cabinet of Ministers regulation N° 487 (20.06.2006.) and N° 1041 (27.12.2005) and Law on Aviation Security LCAA Cabinet of Ministers regulation N° 397 (27.04.2010.) and Law on Aviation

LSSIP Year 2013 Latvia 6 Released Issue

1.2.1.2 Department of Air Transport of the MoT and LCAA According to the act “Law on Aviation”, the Department of Air Transport of the Ministry of Transport and Civil Aviation Agency of Latvia (LCAA) implement State policy and exercise State administration in the field of civil aviation. As per SES regulations the Department of Air Transport together with LCAA, were nominated as the National Supervisory Authorities (NSA). Both organizations are responsible for certification of the air navigation services providers in Latvia. LCAA is responsible for safety supervision and approves/certifies/licenses staff, operations and equipment of service provider organisations. Both bodies are institutionally separated from the service providers. The LCAA is an independent governmental Agency subordinated to the Ministry of Transport. LCAA operates as a non-profit organisation, financed from fees from aviation enterprises.

Annual Report published: Y Safety report for 2012. http://www.caa.lv/upload/userfiles/files/DSN_Publikacijas/Drosibas_parskats _par_2012_gadu.pdf 2012 Review. http://www.caa.lv/upload/userfiles/files/Publiskais%20p%C4%81rskats%202 012.pdf

More detailed information is available on the following web sites: - The Ministry of Transport of the Republic of Latvia: http://www.sam.gov.lv - Civil Aviation Agency of Latvia: http://www.caa.lv LCAA Organisational Chart is presented in Annex B.

1.2.2 Air Navigation Service Provider

Name of the ANSP: Latvijas Gaisa Satiksme (LGS) Governance: Ministry of Transport Ownership: 100% State Services provided Y/N Comment ATC en-route Y ATC approach Y ATC Aerodrome(s) Y AIS Y CNS Y MET Y LGS is responsible for the meteo observations at the airports only. ATCO training Y Unit Training (Transitional, Pre-On the Job Training and On the Job Training) Continuation Training (Refresher, Emergency and Conversion) Others Y FIS/AFIS (provided by Liepaja FIC in Western part of FIR) Alerting Services; Pre-tactical and tactical airspace management. Additional information: Provision of services in Y Airspace under the responsibility of Lithuania. Route segment NINTA – other State(s): ADAXA.

Annual Report published: Y http://www.lgs.lv/en/corporate-information/reports/ This is the annual report covering yearly activities of the ANSP.

ANSP website: www.lgs.lv LGS Organisational Chart is presented in Annex B.

LSSIP Year 2013 Latvia 7 Released Issue 1.2.2.1 ATC system in use

Automated ATC system (flight data processing system; surveillance data processing system; and human-machine interface). Manufacturer SiATM (Sweden) Major upgrade of the ATC system is performed: 2013 (next upgrade is planned for 2015)

1.2.2.2 ATC units The ATC units in the Latvian airspace, which are of concern to this LSSIP are the following:

ATC Unit Number of sectors Associated FIR(s) Remarks En-route TMA RIGA ACC 3 RIGA En-route RIGA TMA / APP 2 RIGA LIEPAJA FIC 1 RIGA FIS / AFIS below FL095

1.2.3 Airports

1.2.3.1 General information The main international airport in Latvia is RIGA International Airport. It is fully state owned Joint-Stock Company of the Republic of Latvia. The holder of state capital shares is the Ministry of Transport of the Republic of Latvia. Latvia has some airfields for general aviation as well.

1.2.3.2 Airport(s) covered by the LSSIP APO SloAs are contained in the following objectives: ENV, APO, ITY-ADQ and SAF11. In addition to the Annex B of the ESSIP Plan edition 2013, it is up to the individual State to decide which additional airports will be reported through LSSIP for those objectives. So the following airport is covered in this LSSIP: Riga International Airport.

1.2.4 Military Authorities The Military Authorities (Air Forces) in Latvia are composed of: - Air Forces HQ; - Air Surveillance Squadron; - Aviation Squadron; - Ground based Air Defence Battalion; - Airfield Operations Support Unit. They report to the Ministry of Defence of the Republic of Latvia and Commander of Latvian National Armed Forces. Their regulatory, service provision and user role in ATM are detailed below. Information on the application of FUA is in 1.2.4.4. National Armed Forces website: www.mil.lv

LSSIP Year 2013 Latvia 8 Released Issue

1.2.4.1 Regulatory role Regulatory framework and rule-making

OAT GAT OAT and provision of service for OAT governed Y Provision of service for GAT by the Military N/A by national legal provisions? governed by national legal provisions? Level of such legal provision: Cabinet of Ministers Level of such legal provision: N/A Authority signing such legal provision: Cabinet of Authority signing such legal provision: N/A Ministers These provisions cover: These provisions cover: Rules of the Air for OAT Y Organisation of military ATS for OAT N Organisation of military ATS for GAT N/A OAT/GAT Coordination N OAT/GAT Coordination N/A ATCO Training N ATCO Training N/A ATCO Licensing N ATCO Licensing N/A ANSP Certification N ANSP Certification N/A ANSP Supervision N ANSP Supervision N/A Aircrew Training N ESARR applicability N/A Aircrew Licensing N Additional Information: Bilateral agreement between Additional Information: Military are subject to Civil NATO and the three Baltic States. (NATO Air Policing) Rules 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 N National AIP Y National Military AIP N/A National Military AIP N/A EUROCONTROL eAIP N EUROCONTROL eAIP Y Other: Other:

Oversight OAT GAT National oversight body for OAT: MoD NSA (as per SES reg. 550/2004) for GAT services provided by the military: there is no Military NSA in Latvia. Military does not provide service to GAT. Additional information: Additional information:

LSSIP Year 2013 Latvia 9 Released Issue

1.2.4.2 Service Provision role

OAT GAT Services Provided: NATO (only for air policing) Services Provided: En-Route N En-Route N Approach/TMA N Approach/TMA N Airfield/TWR/GND N Airfield/TWR/GND N AIS N AIS N MET Y MET N SAR Y SAR Y TSA/TRA monitoring Y (NATO) FIS N Other: Other: N Additional Information: There are no TRAs for OAT. Additional Information: The SAR coordination is provided by LGS.

Military ANSP providing GAT N/A 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:

1.2.4.3 User role

IFR inside controlled airspace, Military aircraft OAT only N GAT only Y Both OAT and GAT N* can fly? * “Yes” in case of A - Scramble.

If Military fly OAT-IFR inside controlled airspace, specify the available options: Free Routing N/A Within specific corridors only N/A Within the regular (GAT) national route network N/A Under radar control N/A Within a special OAT route system N/A Under radar advisory service N/A

If Military fly GAT-IFR inside controlled airspace, specify existing special arrangements: No special arrangements Y Exemption from Route Charges Y Exemption from flow and capacity (ATFCM) measures N Provision of ATC in UHF N/A CNS exemptions: RVSM N/A 8.33 N Mode S N ACAS N Others:

1.2.4.4 Flexible Use of Airspace (FUA)

Military in applies FUA requirements as specified in the Regulation No 2150/2005: Y FUA Level 1 implemented: Y FUA Level 2 implemented: Y FUA Level 3 implemented: Y

LSSIP Year 2013 Latvia 10 Released Issue 1.2.5 Accident/incident Investigation Body

1.2.5.1 Technical investigations Investigations following accidents and serious incidents are carried out by the Transport Accident and Incident Investigation Bureau (TAIIB). TAIIB is permanent national civil aviation safety investigation authority which performs its functions independently in compliance with EC Regulation 996/2010 of the European Parliament and of the Council of 20 October 2010 on the investigation and prevention of accidents and incidents in civil aviation and repealing Directive 94/56/EC. The TAIIB conducts investigations for Civil Aviation aircraft accidents and serious incidents. A safety review is published annually at national level and is available on the following website: The Transport Accident and Incident Investigation Bureau (TAIIB) website: http://www.taiib.gov.lv

1.2.5.2 Collection, Evaluation & Processing of Data The LCAA performs collection, evaluation, processing and storing of all information related to accidents, incidents and occurrences, as well as making this information available to the other EU States according to Directive 2003/42/EC. In order to carry out this function, LCAA uses the tools developed in the frame of the programme for the “European Co-ordination Centre for Aviation Incidents Reporting System” (ECCAIRS).

1.2.5.3 Civil-Military Accidents/Incidents The Transport Accidents and Incidents Investigation Bureau will be involved in all civil/military accidents / incidents investigations. If no civilians are involved in the accident / incident then the investigation will be conducted by the MoD.

LSSIP Year 2013 Latvia 11 Released Issue Chapter 2 - En-route Traffic and Capacity

2.1 Evolution of traffic in Latvia

Latvia - Annual IFR Movements 350000 Latvia - Distribution (Ref. year 2012)

300000

250000 Overflights 71%

200000

150000 IFR flights IFR IFR movements - Actuals

IFR movements - Baseline forecast Domestic 100000 International flights 0% IFR movements - High forecast Dep/Arr 29% 50000 IFR movements - Low forecast

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 2,4% 7,2% 5,7% 5,1% 4,8% 4,8% 4,5% Latvia B 4,0% 9,8% -1,0% 1,7% 4,5% 3,0% 2,8% 2,5% 2,7% 2,7% L 1,2% 2,2% 0,8% 1,1% 0,9% 1,1% 1,1% ESRA B 0,8% 3,1% -2,4% -0,9% 1,4% 2,6% 2,7% 2,2% 2,5% 2,5%

2013 Traffic in Latvia increased by 1.6% 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 1.2% and 5.3% throughout the planning cycle, with a baseline growth of 3.0%.

LSSIP Year 2013 Latvia 12 Released Issue 2.2 RIGA ACC

2.2.1 Traffic and en-route ATFM delays 2009-2018/19

EVRRCTA - Traffic and en-route ATFM delays 1200 1.0

0.9 1000 0.8

0.7 800 0.6

600 0.5

0.4 400 0.3 IFR flights (Daily Average) (Daily flights IFR

0.2 flight) per (minutes Delay Enroute 200 0.1

0 0.0 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019

Peak Day Traffic 571 620 819 833 831 Summer Traffic 498 516 716 704 714 Yearly Traffic 460 477 639 634 637 Summer Traffic Forecast 722 743 772 793 814 835 High Traffic Forecast - Summer 740 792 831 871 929 976 Low Traffic Forecast - Summer 709 720 732 742 748 756 Summer enroute delay (all causes) 0.0 0.0 0.0 0.0 0.0 Yearly enroute delay (all causes) * 0.0 0.0 0.0 0.0 0.0

2.2.2 Summer 2013 performance

En-route Delay (min/flight) Capacity Traffic Evolution 2013 Capacity Baseline Optimum All reasons Without weather gap

+1.5 % 85 (+0%) 0.03 0.0 0.0 No As in 2012, Riga ACC did not generate enroute ATFM delay. Capacity Plan: Sufficient to meet demand Achieved Comments Additional APP sector Yes Various ATM system improvements Yes Maximum configuration: 3 + 2 APP Yes Summer 2013 performance assessment The capacity baseline was estimated at the same level as in 2012. The average peak 1 hour demand was 63 and the peak 3 hour demand was 57 flights during the measured period, indicating that the ACC offered sufficient capacity to meet the demand.

2.2.3 Planning Period 2014-2018/19 - Summer The planning focuses on the Summer season to reflect the most demanding period of the year from a capacity perspective. This approach ensures consistency with the previous planning cycles. The 2014-2018/19 summer capacity profile and delay breakdown has been derived according to the following parameters:  2014: capacity requirement profiles based on the delay breakdown per ACC as provided in January 2011  2015-2018/19: Reference value based on the breakdown of a yearly European delay target of 0.5 min/flight

LSSIP Year 2013 Latvia 13 Released Issue En-route ATFM delay breakdown - Reference Values EVRRCTA 2014 2015 2016 2017 2018 2019 Annual 0.05 0.04 0.03 0.04 0.03 0.03 Summer 0.05 0.06 0.05 0.05 0.05 0.05 Capacity Profiles 2013 Profiles (hourly movements and % increase over previous year) ACC baseline 2014 2015 2016 2017 2018 2019 H 85 0% 85 0% 85 0% 85 0% 86 1% 88 2% Ref. 85 0% 85 0% 85 0% 85 0% 85 0% 85 0% EVRR 85 L 85 0% 85 0% 85 0% 85 0% 85 0% 85 0% C/R 85 0% 85 0% 85 0% 85 0% 85 0% 86 1%

Capacity Plan Year 2014 2015 2016 2017 2018 2019

Various ATM system improvements Measures planned

Significant Events Max sectors 3 + 2 APP 3 + 2 APP 3 + 2 APP 3 + 2 APP 3 + 2 APP 3 + 2 APP

Capacity Sufficient capacity to meet expected demand increase Reference 0% 0% 0% 0% 0% 0% profile Additional information

EVRRCTA - Reference capacity profile and alternative scenarios

100

90

80

70

60

50

Capacity profile (movements per hour) 40 2012 2013 2014 2015 2016 2017 2018 2019 2014-2019 Reference Capacity Profile 85 85 85 85 85 85 Capacity Profile - Current Routes 85 85 85 85 85 86 Capacity Profile - High 85 85 85 85 86 88 Capacity Profile - Low 85 85 85 85 85 85 Capacity Baseline 85 85 2014 - 2019 Plan 85 85 85 85 86 88

LSSIP Year 2013 Latvia 14 Released Issue Chapter 3 - ESSIP Report recommendations

Recommendations issued from the ESSIP Report for 2012 applicable to Latvia for all items that require corrective actions and improvements ahead of the 2013 reporting exercise.

Number Recommendation Ownership LV Feed-back

The completion dates were reviewed to mirror To ensure that all Stakeholders report the expected REC-2012- the dates in completion dates as defined in their National All States 03 respective national business plans. plans.

LSSIP guidance has been used as To ensure correct application of LSSIP guidance REC-2012- appropriate and the material and to implement the results of mandatory All States 05 results of LSSIP in- LSSIP in-cycle check. cycle check have been considered. States to ensure that appropriate actions are taken BE, UK, SE, NO, FI, Completion of the REC-2012- for overcoming present delays in the implementation LV, PL, HU, UA, AM, tasks for ESSIP TR, MK, FR, PT, MT, 11 of priority capabilities specified in the ESSIP RO, HR, BA, AL, SI, objective FCM03 is objective FCM03. IT, CZ, MAS, CY. planned on time. Appropriate tasks To ensure actions for overcoming present delays in AL, AZ, BA, BE, BG, at the ANSP and REC-2012- the implementation of remaining SLoAs for CY, DE, EE, ES, GE, State level are GR, HR, HU, IT, LV, 15 implementation of P-RNAV (ESSIP objective ME, MT, NO, PT, RS, planned to ensure NAV03). SI, UA, UK timely implementation. Interim Deployment Programme View

Number Recommendation Ownership

Automatic sending of AFP messages is planned for REC-2012- States are encouraged to speed up the AFP 01/2014. Flight 22 implementation and to schedule AFP testing with All States plan messages, at Network Manager Riga ATCC, are processed in ICAO 2012 Format.

LSSIP Year 2013 Latvia 15 Released Issue

Stakeholders View

Number Recommendation Ownership

LGS plans implementation of APV procedures based on National PBN Concept and corresponding REC-2012- ANSPs are encouraged to publish more APV routes. National PBN All ECAC ANSPs 40 Implementation Plan. Both national documents are not ready yet. Initial implementation is expected by the end of 2014. FAB View

Number Recommendation Ownership

NEFAB ANSPs developed NEFAB a business plan for To update the FABs plans and establish a more a period from 2014 REC-2012- appropriate roadmap to improve the current lack of – 2018, in order to FAB States 41 coordination and ensure a common response to ensure coordinated deployment needs. response to the airspace user needs.

LGS coordinates systems deployment and upgrades as well The ANSPs should coordinate system deployment as implementation (including system upgrades) and capabilities plans together with REC-2012- implementation plans with FAB partner first, and FAB States FAB partners. 42 then follow on with coordination to adjacent FABs North European and ANSPs. Free Route Airspace and CPDLC implementation are the best examples.

Harmonisation of reporting culture would be achieved Ongoing work to harmonize reporting culture REC-2012- through planned between States in the FAB should be continued to FAB States 43 common Safety ensure alignment of reporting principles. management System training of the ANS staff within NEFAB.

LSSIP Year 2013 Latvia 16 Released Issue Chapter 4 - National Projects

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

Name Schedule Description – Scope Status Link with Expected Contribution to the Key European Master Performance Areas1 Plan. Upgrade of On-going The project includes: In progress ATC Safety automated ATC  CPDLC technology implementation; AOM Capacity system  Implementation of FAB free route air space ITY-FMTP (ATRACC) conception; ITY-COTR  Automated Support to ATS – Departure ITY-AGDL manager (DMAN);  Provision of FIS and AFIS in Riga FIR (ATRACC WS);  Riga Tower modernization (ATCO Work Stations);  Back up of A-SMGCS;  Automation of aeronautical data input.  Transition from 2011 - 2016 Development of LGS system for data delivery using In progress ITY-ADQ Safety AIS to AIM standardised formats, which are based on clients’ needs. Modernization of 2012 - 2015 A-SMGCS modernization in the Riga airport includes: In progress AOP04.2 Safety A-SMGCS  Connection of virtual (A-SMGCS) and manual (Riga aerodrome) stop bars to provide synchronized action of manual stop bars with A-SMGCS notifications. This will help to minimise TWR ATCO workload and possible human errors;  Replacement of A-SMGCS software and hardware;  A-SMGCS information provision to a large number of users (Riga airport responsible services). Currently Riga airport is interested in receiving information from A-SMGCS to coordinate activities on the aerodrome while snow cleaning or security provision;  A number of supplements to system functionality taking into consideration users’ demands and raise of traffic in Riga airport;

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

LSSIP Year 2013 Latvia 17 Released Issue  Realization of „Follow-the-green” conception harmonising A-SMGCS and ATRACC systems;  Establishment of integrated system providing ATCOs with the information to perform control in the air and on the ground. The system will process the data from ATRACC and A- SMGCS systems;  Aeronautical data processing.

PBN 2012 - 2016 The project assumes analysis of the existing airspace In progress NAV03 Safety Implementation structure of Riga FIR, development, validation and NAV10 Capacity implementation of PBN air space applications and ENV01 Environment corresponding procedures FIS 2012 - 2014 Currently FIS for all flights within class G airspace is In progress Safety Implementation provided by corresponding sectors of Rīga ATCC or Capacity within RIGA FIR Liepāja FIC (Western part of FIR). The project assumes establishment of FIC in Riga to provide FIS within class G airspace for the whole FIR. The goal is workload reduction of ACC/APP controllers together with prevention of incursion into controlled airspace and service improvement for class G airspace users.

Replacement of 2012 - 2014 Replacement of VHF radios due to the end of life cycle. In progress Safety VHF radios Development of 2013-2014 Runway surface renovation works. Extension of an Planned Safety Airport existing taxi way. Drainage system renovation works on Capacity Infrastructure in .runway strip. Expansion of existing aprons and Airport “Riga” construction of new stands.

LSSIP Year 2013 Latvia 18 Released Issue Chapter 5 - Regional Co-ordination

5.1 FAB Co-ordination North European Functional Airspace Block - NEFAB NEFAB is a functional airspace block created by Estonia, Finland, Latvia and . NEFAB has established a programme with a programme management office (PMO) with the objective of managing projects and initiatives among the ANSPs in the cooperation. In addition there is close cooperation with LFV and Naviair in DK/SE-FAB concerning airspace development. In this cooperation the implementation of a seamless Free Route Airspace above FL 285 across the two airspace blocks is prioritised in the short term with planned implementation towards the end of 2015. The activity is targeted to connect Free Route Airspace in the two FAB´s ensuring a continuous Free Route Airspace. The activity is organised as a project called North European Free Route Airspace – NEFRA. This project is not aimed at airspace developments inside the two airspace blocks. The ANSPs in NEFAB have developed a 5 year business plan, covering the period 2014 – 2018 and an annual plan for 2014. The 5 year business plan describes the strategies for the period with key performance areas and strategic objectives. The annual plan transforms these strategies into activities planned for 2014 with defined deliverables and milestones. In April 2013 two key projects, Airspace 2015 and ATS Provision 2015, delivered the NEFAB Network Plan. The NEFAB Network Plan describes the operational requirements for the establishment of the airspace and service provision within NEFAB in 2015. 2015 is considered an intermediate step towards a performance scenario planned for 2020 and beyond. The individual ANSPs in the FAB-cooperation will implement the required operational changes and technical support to enable the concept described in the NEFAB Target Concept.

Regulatory Co-operation During the establishment of NEFAB there has been close cooperation between the 4 NEFAB NSAs, and this cooperation is now formalised by the NEFAB NSA Committee. There is also established cooperation between the other Nordic NSAs, by the 7-State NSA Cooperation. Meetings between the 4 NEFAB NSAs and representatives from NSA Iceland, Sweden and Denmark have been held, and cooperation are established on areas of common interest. This cooperation will be continued.

Civil-Military Co-ordination NEFAB has established the Civil-Military Committee (CMC) that consists of representatives from CAA and MAA. The function of the committee is to: - define areas of cooperation between the Contracting States within the scope of the NEFAB Agreement as regards military aviation; - enhance the use of airspace in NEFAB, taking account of military aviation needs, including military mission effectiveness; - provide for efficient and consistent application of the concept of ‘flexible use of airspace’ by the Contracting States; - provide for the development of arrangements for military training activities regardless of existing boundaries; For the year of 2013 four meetings have taken place. The committee has been chaired by CAA Latvia and the co-operation has been fruitful.

LSSIP Year 2013 Latvia 19 Released Issue

5.2 FAB Projects

Name Schedule FAB Partner Status Expected Contribution to the Key Performance Areas2 and link to ESSIP NEFAB Dec. 2011 Avinor, EANS, Ongoing according to Resulting in improved capacity Target Finavia and LGS project schedule through improved airspace Nov. 2015 Concept structures and alignment of sectors.

Safety is not considered a specific objective for the project, but safety levels shall be maintained or increased after implementation. The project will enable more effective use of operational resources and contribute to improved cost-efficiency. More efficient airspace and routing options for airspace users will increase flight efficiency and contribute to reduced emissions. NEFRA May 2012 Avinor, EANS, On-going according Capacity and ANSP cost efficiency (North Finavia, LFV, to project schedule are not considered specific objects Nov. 2015 European LGS and Naviair for the project. Capacity levels shall Free Route be maintained or improved and the Airspace) implementation shall not reduce ANSP cost-efficiency. Safety is not considered a specific objective for the project, but safety levels shall be maintained or increased after implementation. More efficient airspace and routing options for airspace users will increase flight efficiency and contribute to reduced emissions.

5.3 Other regional coordination projects Baltic Integration Baltic Integration is stemming from ICAO EANPG/42/2 (December 2000), which established a Task Force (TF) to draft a Memorandum of Understanding and identify priorities for a common Baltic UIR or other type of ATM co-operation over parts of the high seas. Estonia, Latvia, Lithuania and Poland are members of the TF, under the ICAO EUR aegis. To the end of 2002 the Task Force developed ”DRAFT MEMORANDUM OF UNDERSTANDING FOR HARMONIZATION AND INTEGRATION OF COMPONENTS OF THE AIR NAVIGATION SYSTEMS IN THE BALTIC AREA”. The document as well as its Technical Annex was presented to the appropriate National Authorities. Cooperation has crystallized as Baltic CNS/ATM Transition Project Feasibility Study (2001-2004). The project produced a coordinated CNS/ATM Sub-regional Implementation Plan for Latvia, Lithuania and Estonia complying with recommendations of international aviation organisations and defining short-term needs and long-term prospective of air navigation systems in the three contracting states.

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

LSSIP Year 2013 Latvia 20 Released Issue The Borealis Alliance Framework Agreement The Alliance Framework Agreement (AFA) is a business co-operation signed on the 20th of June 2012. The vision of Borealis is to be the leading ANSP Alliance that enables its Members to drive better performance for stakeholders through business collaboration. On the same day the co-operation agreement known as NEAP (North European ANS Providers) was formally ended. The members of Borealis are LFV (Sweden), Finavia (Finland), Avinor (Norway), ISAVIA (Iceland), Naviair (Denmark), EANS (Estonia), IAA (Ireland), LGS (Latvia) and NATS (UK). Borealis has two objectives, the first relates to delivering value through business co-operation between the Members, the second to being collectively more influential by developing and expressing a joint position on common issues. These objectives will be achieved by developing and delivering a joint business plan. The Agreement does not commit the Members to work towards creating a single combined FAB between their respective States sometime in the future, but it does not preclude such an outcome either.

LSSIP Year 2013 Latvia 21 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 Latvia 22 Released Issue

Not Harmonise Operational Air Traffic (OAT) and General Air[IDP] AOM13.1 Applicable Traffic (GAT) handling (By:12/2018) [Essential]

State aircraft are handled as GAT outside of restricted areas or TSAs. Mixing of OAT and GAT air traffic is not authorized in Latvian airspace. Civil ATC provides service12/2018 to GAT traffic only. There is no military ATC providing services to OAT in Latvia. State aircraft are handled as GAT outside of restricted areas or Not

TSAs.Mixing of OAT and GAT air traffic is not authorized. Civil Applicable REG ATC provides service to GAT traffic only. EUROAT document (By:12-2018) has been formally introduced to the military for consideration. 12/2018 There is no military ATC providing services to OAT in Latvia. Currently state aircraft except specified areas (TSA) are Not ASP handled as GAT. There are no military ATC providing services Applicable (By:12-2018) to OAT in Latvia. 12/2018 Military fly in the airspace under GAT rules, they fly OAT only in Not

MIL TSAs and predefined specific areas. OAT is authorized to Applicable (By:12-2018) operate only under military fighter control in segregated airspace. No plans to develop military ATC for OAT by 2018. 12/2018

[IDP] Planned AOM19 Implement Advanced Airspace Management (By:12/2016) [Essential] FUA is implemented at all three levels. Advanced ASM / ATFCM process is under 12/2016 implementation in accordance with Eurocontrol Guidance materials. ASP Advanced ASM process is under implementation in accordance Planned (By:12-2015) with Eurocontrol Guidance materials. 12/2016 Not

MIL Military role is only as an airspace user with regard to Applicable (By:12-2015) ASM/ATFCM processes. 12/2016

Implement ATS Route Network (ARN) - Version 7 Completed AOM20 (By:10/2013) [Essential] ARN Version 7 is implemented. 12/2012 ASP Completed ARN Version 7 is implemented. (By:10-2013) 12/2012 Not

MIL Military does not provide any ATM/ANS services and is not Applicable (By:10-2013) involved in any ATM/ANS safety oversight. -

[IDP] Planned AOM21 Implementation of Free Route Airspace (By:12/2017) [Essential] Latvia plans to implement FRA along with the other NEFAB member states by the 12/2015 end of 2015. REG Safety oversight tasks are planned to be carried out in 2015, Planned (By:12-2017) when FRA would be implemented as a NEFAB wide project. 12/2015 The work is in progress. The local FRA airspace has been Planned ASP identified in coordination with the Network and FAB partners. (By:12-2017) LGS plans to train ATCOs accordingly. 11/2015 National military is not involved in ANS provision. The national Not MIL military does not operate at the altitudes for which FRA is Applicable (By:12-2017) planned to be implemented. 12/2015

LSSIP Year 2013 Latvia 23 Released Issue Improve runway safety by preventing runway incursions Completed AOP03 (By:12/2013) The runway safety team is operational. LGS and the Riga airport have implemented 12/2013 the EAPRI requirements. The CAA issued an order to invite all involved stakeholders to Completed REG create a runway safety team and implement the specific (By:12-2013) recommendations from the EAPRI (European Action plan for 12/2006 the prevention of runway incursions). Completed ASP The runway safety team is operational. LGS has implemented CASCADE / (By:12-2013) all EAPRI requirements. Riga Runway12/2006 Safety Team Currently military airfields in Latvia are not equipped to provide Not MIL service to Civil operations. Military will be involved into the Riga Applicable (By:12-2013) Airport runway safety team. - The runway safety team is operational. LGS and the Riga Completed APO airport have implemented most of EAPRI requirements. All Riga Runway (By:12-2013) communications associated with runway operations are 12/2013 conducted using aviation English. Safety Team

Implement Advanced Surface Movement Guidance and Completed AOP04.1 Control System (A-SMGCS) Level1 (By:12/2011) [Essential] EVRA - Riga A-SMGCS Level 1 system is operational from 2007. The A-SMGCS is composed by a surface movement radar and a multilateration system based on Mode A/C and Mode06/2007 S. LCAA has approved A-SMGCS Level 1 operating procedures Completed REG and the installations at Riga airport. Appropriate information (By:12-2010) has been published in the AIP EVRA AD 2-20. Local Traffic 06/2007 regulations. ASP A-SMGCS Level 1 system is operational at Riga International Completed (By:12-2011) Airport. CASCADE 06/2007 Not MIL Military do not provide service to civil flights. Applicable (By:12-2010) - APO A-SMGCS Level 1 system is operational at Riga International Completed (By:12-2010) Airport. CASCADE 12/2007

Implement Advanced Surface Movement Guidance and Completed AOP04.2 Control System (A-SMGCS) Level 2 (By:12/2017) EVRA - Riga A-SMGCS Level 2 is fully implemented at the Riga International Airport. 12/2008 REG LCAA has approved A-SMGCS Level 2 operating procedures Completed (By:12-2017) and the installations at Riga airport. 12/2008 ASP A-SMGCS Level 2 system is operational at Riga International Completed (By:12-2017) Airport. Approach controllers have the A-SMGCS in view mode.CASCADE 12/2008 APO A-SMGCS Level 2 is fully implemented at the Riga International Completed (By:12-2017) Airport. CASCADE 12/2008

LSSIP Year 2013 Latvia 24 Released Issue

Implement ground based safety nets - Short Term Conflict Completed ATC02.2 Alert (STCA) - level 2 (By:01/2013) [Essential] Advanced STCA functions are implemented in the automated ATC system and they are operational. The automated ATC system is conforming to STCA Level 212/2008 requirements. ATCOs are trained accordingly. LCAA integrated EUROCONTROL Specification for STCA level Completed REG 2 in the national regulation. Safety oversight audits and (By:01-2013) inspections have been conducted. 12/2008 Advanced STCA functions are implemented in the automated Completed ASP ATC system and they are operational. The automated ATC (By:01-2013) system is conforming to STCA Level 2 requirements. ATCOsATRACC 12/2008 are trained accordingly. Not MIL Military do not provide service to civil flights. Applicable (By:01-2013) -

Implement ground based safety nets - Area Proximity Completed ATC02.5 Warning - level 2 (By:12/2016) [Essential] Area Proximity Warning function is implemented in the automated ATC system and it is operational from 2001. Corresponding procedures and instructions for operational12/2013 and engineering staff are established. Area Proximity Warning function is implemented in the Completed ASP automated ATC system and it is operational from 2001. (By:12-2016) Corresponding procedures and instructions for operational andATRACC 12/2013 engineering staff are established. Not MIL Military does not provide any ATM/ANS services. Applicable (By:12-2016) -

Implement ground based safety nets - Minimum Safe Completed ATC02.6 Altitude Warning - level 2 (By:12/2016) [Essential] Minimum Safe Altitude Warning function is implemented in the automated ATC system and it is operational from 2001. Corresponding procedures and instructions12/2013 for operational and engineering staff are established. Minimum Safe Altitude Warning function is implemented in the Completed ASP automated ATC system and it is operational from 2001. (By:12-2016) Corresponding procedures and instructions for operational andATRACC 12/2013 engineering staff are established. Not MIL Military do not provide any ATM/ANS services. Applicable (By:12-2016) -

Implement ground based safety nets - Approach Path No Plan ATC02.7 Monitor - level 2 (By:12/2016) [Essential] LGS will plan the APM implementation if the local needs will be identified and upon 12/2016 readiness of the Eurocontrol Specification. ASP LGS will plan the APM implementation if the local needs will be No Plan (By:12-2016) identified and upon readiness of the Eurocontrol Specification. ATRACC 12/2016 Not MIL Military does not provide any ATM/ANS services Applicable (By:12-2016) -

LSSIP Year 2013 Latvia 25 Released Issue Planned ATC07.1 Implement arrival management tools (By:12/2015) [Essential] Implementation of AMAN tools is planned. The automated ATC system is already 12/2015 prepared to support AMAN. LGS plans implementation of basic arrival management tools. Planned ASP The automated ATC system is already prepared to support (By:12-2015) AMAN. ATRACC 12/2015

Implement automated support for conflict detection and Completed ATC12 conformance monitoring (By:12/2016) [Essential] MTCD and MONA functions are implemented in the ATC system. The ATCOs are 12/2008 trained accordingly. REG MTCD and Conformance Monitoring functions are implemented Completed (By:12-2016) and used operationally in the ATC system. 12/2008 ASP MTCD and Conformance Monitoring functions are implemented Completed (By:12-2016) and used operationally. The ATCOs are trained accordingly. ATRACC 12/2008

Implement, in En-Route operations, information exchange[IDP] Planned ATC15 mechanisms, tools and procedures in support of Basic AMAN operations (By:12/2017) [Essential] Training of ATCOs and implementation of AMAN tools are planned by 2017. 01/2017 REG Planned approval of procedures after review of the proposesd Planned (By:12-2017) safety changes. 01/2017 ASP AMAN functionality (in en-route operations) is planned to be Planned (By:12-2017) implemented. ATRACC 12/2017

Implement ACAS II compliant with TCAS II change 7.1 Planned ATC16 (By:12/2015) Respective nationally registered aircraft are planned to be equipped with enhanced ACAS II version 7.1 and ANSP staff appropriately trained in order to further reduce01/2015 the risk of mid-air collisions in European airspace. Airworthiness certification and operational approval for ACAS II Planned REG version 7.1 equipped aircraft will be caried for Latvian (By:12-2015) registered aircraft. Appropriate oversight of the ANSP staff 01/2015 training is planned. All the personnel concerned have been trained accordingly. Completed ASP ACAS performance monitoring system is established as a part (By:03-2012) of ATS safety monitoring. 12/2012 National armed forces do not operate fixed wing transport type Not

MIL aircraft. Appropriate training to the helicopter flight crew Applicable (By:12-2015) operating in the airspace with other aircraft equipped with ACAS II, has been provided. 12/2015

LSSIP Year 2013 Latvia 26 Released Issue

Electronic Dialogue as Automated Assistance to Controller[IDP] Planned ATC17 during Coordination and Transfer (By:12/2018) [Essential] Upgrade of coordination and transfer through automated assistance of electronic 12/2018 dialogue is planned by the end of 2018. Safety assessment for the Electronic Dialogue changes will be Planned REG be analysed, reviewed and the decision made on the (By:12-2018) acceptance of changes. 06/2018 LGS and supplier have discussed a draft specification with Planned regard to electronic dialog. This specification is a subject of the ASP automated ATC system modernisation project "ATRACC (By:12-2018) 2014+". Implementation timeframe will be defined together with 12/2018 the neghbouring ANSPs.

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

(By:12/2014) LCAA and LGS plans to complete the objective. 12/2014 REG Completed ANSP has been informed about transition of X25 to IP. (By:12-2010) 12/2010 Currently LGS has corresponding IP infrastructure in place. Partly

ASP LGS has connected to PENS which is used operationally for Completed (By:12-2014) the provision of EAD and CFMU services by means of IPv4. IPv6 is planned. 12/2014 Not MIL Military does not provide ANS/ATM services in Latvia. Applicable (By:12-2014) -

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

AMHS activity is coordinated together with neighbouring countries. 12/2014 Partly

ASP LGS AFTN system is upgraded to AMHS functionality. LGS Completed (By:12-2014) made interoperability tests with Moscow COM Centre. 12/2014 Not MIL Military does not provide ANS/ATM services in Latvia. Applicable (By:12-2014) 12/2014

Implementation of Voice over Internet Protocol (VoIP) in Planned COM11 ATM (By:12/2020) Latvia plans to implement VoIP by the end of 2020 12/2020 After formal review decision on acceptance will be Planned REG communicated to the ANSP. Technical files and declarations of (By:12-2018) conformity and suitability for use and declaration for verification 12/2018 reviewd as necessary Partly ASP LGS plans to implement Voice over IP in ATM. Completed (By:12-2020) 12/2020 Not MIL Militar does not provide ATM/CNS services Applicable (By:12-2020) -

LSSIP Year 2013 Latvia 27 Released Issue Implement enhanced tactical flow management services Late FCM01 (By:12/2006) [Essential] Implementation of the objective is expected by 01/2014. 01/2014 LGS and Si ATM company have signed a contract on Late automated ATC system modernization. As a result the system ASP already provides FSA to NM and will be able to send CPR (By:12-2006) messages. Implementation of the objective is expected byATRACC 01/2014 01/2014. Not MIL Military do not provide service to civil flights. Applicable (By:12-2001) -

[IDP] Planned FCM03 Implement collaborative flight planning (By:12/2015) [Essential] Flight plan messages, at Riga ATCC, are processed in ICAO 2012 Format. Automatic 01/2014 sending of AFP messages is planned for 01/2014. LGS and Si ATM company have signed a contract to provide Planned ASP automatic sending of AFP messages. Implementation is (By:12-2015) expected till 01/2014. ATRACC 01/2014 Not MIL Military does not provide any ATM/ANS service Applicable (By:12-2015) -

[IDP] Planned FCM05 Implementation of interactive rolling NOP (By:12/2016) [Essential] Latvia plans to implement interactive rolling NOP. 12/2016 REG Planned Latvia plans to implement interactive rolling NOP. (By:12-2016) 12/2016 ASP Planned Implementation of ASM support system LARA is in progress. (By:12-2016) 12/2016 Not MIL Military does not provide ANS/ATM ar aerodrome services Applicable (By:12-2016) 12/2016 Not APO Riga airport has no plans to transition to coordinated slots. Applicable (By:12-2016) 12/2016

Completed INF04 Implement integrated briefing (By:12/2012)

Integrated briefing is provided by means of EAD Briefing facilities service (INO). 12/2012 ASP Integrated briefing is provided by means of EAD Briefing Completed (By:12-2012) facilities service (INO). 12/2012 Not

MIL There is only one AIS office in Latvia; Military authorities are Applicable (By:12-2012) linked to this office. -

LSSIP Year 2013 Latvia 28 Released Issue

Ensure quality of aeronautical data and aeronautical Planned ITY-ADQ information (By:07/2017) [Essential] Latvia plans to ensure quality of aeronautical data and aeronautical information in 07/2017 accordance with Regulation (EU) No 73/2010 of 26 January 2010 Planned Latvian REG Safety assessments are to be supervised, and compliance withNational Plan for the (By:07-2017) data quality requirements monitored. 07/2017 Transition from AIS to AIM, 2011 Planned Latvian ASP LGS plans to implement all the requirements ensuring quality of National Plan for the (By:07-2017) aeronautical data and aeronautical information in time. 07/2017 Transition from AIS to AIM, 2011 Not

MIL National Armed Forces of Republic of Latvia are not involved in Applicable (By:07-2017) the tasks listed in the regulation (EC) 73/2010, Art 2(1). 07/2017 APO It is planned to implement all the requirements ensuring quality Planned (By:07-2017) of aeronautical data and aeronautical information in time. 07/2017

Initial ATC air-ground data link services above FL-285[IDP] Planned ITY-AGDL (By:02/2015) [Essential] Currently there is no ATN/VDL2 coverage over Riga FIR. 02/2015 REG Planned Currently there is no ATN/VDL2 coverage over Riga FIR. (By:02-2015) 02/2015 ASP LGS plans to implement Initial ATC air-ground data link Planned (By:02-2015) services above FL-285. 02/2015 Military is not providing any ATM/ANS services. Military Not MIL operates SAR helicopters only, not able to operate above Applicable (By:-) FL285. 02/2015

ITY- Implement air-ground voice channel spacing requirements Planned AGVCS2 below FL195 (By:12/2020) Planned in accordance with EC regulation 1079/2012 12/2018 REG Planned Planned in accordance with EC regulation 1079/2012 (By:12-2018) 12/2018 LGS is going to implement 8,33 kHz channel spacing below Partly ASP FL195. Voice communication system is upgraded. Appropriate Completed (By:12-2018) personnel is trained. 12/2018 MIL Existing plans includes acquisition of new aircraft fully and Planned (By:12-2020) appropriately equipped to comply with EC reg. 1079/2012. 12/2018 APO Airport plans to implement the 8,33 kHz channel spacing by the Planned (By:12-2018) end of 2017. 12/2017

LSSIP Year 2013 Latvia 29 Released Issue

Partly Implementation of ground-ground automated co-ordination ITY-COTR Completed processes (By:02/2015) [Essential]

Flight data processing and exchange systems are implemented. Advanced functions 02/2015 are subject of further development. REG Completed Safety oversight activities have been completed. (By:12-2012) 12/2012 Flight data processing and exchange systems are Partly

implemented. ATC system is fully compliant with the finalisation Completed ASP criteria. ATC personnel is trained properly with regard to (By:02-2015) operational use of implemented functions. The Logon Forward and the Next Authority Notified processes are planned forATRACC 02/2015 implementation by 2015. Not

MIL Military does not provide ANS/ATM services and there is no Applicable (By:12-2012) electronic flight data provision to civil ATC. 02/2015

Apply a common flight message transfer protocol (FMTP)[IDP] Planned ITY-FMTP (By:12/2014) The objective is planned. It could be achieved by modernizing of existing ATC 12/2014 system by end of 2014. REG The objective is planned. It could be achieved by modernizing Planned (By:12-2014) of existing ATC system by end of 2014. 12/2014 ASP The objective is planned. FMTP protocol IP V4 is implemented. Planned (By:12-2014) The protocol IP V6 is going to be implemented by end of 2014. ATRACC 12/2014 Not MIL Military does not provide services to general air traffic Applicable (By:12-2014) -

Planned ITY-SPI Surveillance performance and interoperability (By:12/2019)

Objectives for surveillance performance and interoperability have been implemented 12/2019 on the civil side. Military plans to complete the appropriate tasks by the end of 2019. REG Formal acceptance of the ANSP safety assessments has been Completed (By:12-2013) performed and communicated to the ANSP. 12/2012 All surveillance data transferred from LGS ground-based Completed surveillance systems to other navigation service providers are in ASTERIX data format. It allows identification of the data source and identification of the type of data. The data are time ASP stamped and expressed as coordinated universal time (UTC). (By:02-2015) Safety assessment to all existing systems is developed and 12/2012 delivered to the Latvian CAA. The training plans exist and corresponding training materials were provided. All personnel affected by the changes to the surveillance infrastructure have been trained. MIL Planned Its planned to equip the military helicopters in due time. (By:12-2019) 12/2017

LSSIP Year 2013 Latvia 30 Released Issue

Late NAV03 Implementation of P-RNAV (By:12/2012) [Essential] Implementation of P-RNAV procedures based on PBN Concept is planned for 2014 Navaids sites were assessed against the P-RNAV requirements and needs for additional DMEs were identified. All co-ordinate data are published in AIP with12/2014 reference to the WGS-84 standard and meet the quality requirements of ICAO Annex 15. LCAA will ensure suppliers of navigation databases are Late REG accredited with suitable quality assurance procedures; and will (By:01-2005) ensure quality of published Navigation Data. 12/2014 LCAA performs regular quality check. LGS plans implementation of RNAV procedures based on Late National PBN Concept and corresponding National PBN Implementation Plan. Both national documents are not ready ASP yet. Initial implementation is expected within 2014. All co- (By:12-2012) ordinate data are published in AIP with reference to the WGS- 12/2014 84 standard and meet the quality requirements of ICAO Annex 15. Military does not provide any ATM/ANS services or procedure Not

design services. Helicopter crews will be trained in RNAV Applicable MIL procedures, if appropriate helicopter RNAV procedures would (By:12-2012) be planned. Current;y, there are no plans for helicopter RNAV - procedures in RIga TMA.

[IDP] Planned NAV10 Implement APV procedures (By:12/2016) [Essential] Latvia plans to move from NPA to APV procedures by the end 2016 12/2016 REG Appropriate EASA material will be applied to local national Completed (By:04-2016) oversight activities. 04/2011 LGS plans implementation of APV procedures based on Planned ASP National PBN Concept and corresponding National PBN (By:12-2016) Implementation Plan. Both national documents are not ready 12/2016 yet. Initial implementation is expected within 2014. Not MIL Military is not providing any ATM/ANS services. Applicable (By:12-2016) -

Implement measures to reduce the risk to aircraft Late SAF10 operations caused by airspace infringements (By:12/2011) The objective is planned to be implemented by end of 2015. 12/2015 REG Verification and monitoring of the effectiveness of specific Late (By:12-2011) measures. 12/2015 Procedural, technological and training parts of the plan are Late ASP completed. Organizational and technological activities to (By:12-2011) improve provision of FIS in lower airspace are planned. 12/2015 Implementation is expected in 2015. MIL Military will implement the objective together with LCAA and Late (By:12-2011) LGS. 12/2015

LSSIP Year 2013 Latvia 31 Released Issue

Improve runway safety by preventing runway excursions Completed SAF11 (By:01/2018) The appropriate parts of the European Action Plan for the Prevention of Runway 12/2013 Excursions has been implemented by the involved parties. The appropriate parts of the European Action Plan for the Completed Prevention of Runway Excursions are implemented. Safety REG oversight program with audits and inspections covers runway (By:01-2018) safety. Participation of the CAA representatives at the Runway 12/2013 Safety Team discussions is ensured for consultation purposes. The appropriate parts of the European Action Plan for the Completed ASP Prevention of Runway Excursions are implemented. Local (By:12-2014) airlines are involves in the Runway Safety Team activities. 12/2013 Not

MIL Military uses its military aerodrome. Military is informed of any Applicable (By:01-2018) specific relevant safety information, additionally. - Airport operators regularly and upon necessity enact the Completed APO necessary safety initiatives through Runway safety team (By:12-2014) actions. 12/2013

LSSIP Year 2013 Latvia 32 Released Issue

Annexes

Annex A – Specialists involved in the LSSIP Process

LSSIP Co-ordination

LSSIP Focal Point for Latvia CAA of Latvia Ērika Neimane. LSSIP Focal Point for ANSP LGS . Vadims Stroiteļevs. LSSIP Focal Point for airport Riga International Airport Dzintra Jātniece “Riga” LSSIP Contact Person for EUROCONTROL Luca Dell’Orto Latvia

ESSIP Objective Implementation ESSIP EUROCONTROL Objective Owners EUROCONTROL National Stakeholder Specialist(s) Objective EIPR Objective Coordinator AOM13.1 R. BUCUROIU, O. MROWICKI, E. O. CIOARA Jurijs BAZULEVS – LGS REUBER AOM19 G. ACAMPORA, O. MROWICKI O. CIOARA Mihails HAVKUNOVS – LGS AOM20 R. BUCUROIU O. CIOARA Jurijs BAZULEVS – LGS AOM21 R. BUCUROIU O. CIOARA Mihails HAVKUNOVS – LGS AOP01.2 P. VRANJKOVIC Vadims ULJANOVSKIS – LGS P. ADAMSON Dzintra JATNIECE - RIX AOP03 P. VRANJKOVIC Vadims ULJANOVSKIS – LGS T. LICU Dzintra JATNIECE - RIX AOP04.1 P. VRANJKOVIC Vadims ULJANOVSKIS – LGS P. ADAMSON Dzintra JATNIECE - RIX AOP04.2 P. VRANJKOVIC Vadims ULJANOVSKIS – LGS P. ADAMSON Dzintra JATNIECE - RIX AOP05 P. VRANJKOVIC Vadims ULJANOVSKIS – LGS P. ADAMSON Dzintra JATNIECE - RIX ATC02.2 B. BAKKER, S. DROZDOWSKI I. FEIJT Igors NEMAHOVS – LGS ATC02.5 B. BAKKER, S. DROZDOWSKI I. FEIJT Igors NEMAHOVS – LGS ATC02.6 B. BAKKER, S. DROZDOWSKI I. FEIJT Igors NEMAHOVS – LGS ATC02.7 B. BAKKER, S. DROZDOWSKI I. FEIJT Igors NEMAHOVS – LGS ATC07.1 N. GAUTIER L. DELL’ORTO Vladislavs CASCINS – LGS ATC12 N. GAUTIER L. DELL’ORTO Igors NEMAHOVS – LGS ATC15 N. GAUTIER L. DELL’ORTO Vladislavs CASCINS – LGS ATC16 S. DROZDOWSKI L. DELL’ORTO Jurijs BAZULEVS – LGS ATC17 N. GAUTIER L. DELL’ORTO Igors NEMAHOVS – LGS COM09 B. GASZTYCH, J. POUZET O. ALFARO Ainars SNEPSTS – LGS COM10 B. GASZTYCH, J. POUZET A. KOKONA Ainars SNEPSTS – LGS COM11 B. GASZTYCH, J. POUZET A. KOKONA Ainars SNEPSTS – LGS ENV01 P. ADAMSON B. HILL not applicable ENV02 S. MAHONY, A. WATT B. HILL not applicable FCM01 H. KOOLEN O. CIOARA Sergejs OVSJANIKOVS – LGS FCM03 S. SMIDT O. CIOARA Sergejs OVSJANIKOVS – LGS FCM04 M. RICHARD O. CIOARA not applicable

LSSIP Year 2013 Latvia 33 Released Issue ESSIP EUROCONTROL Objective Owners EUROCONTROL National Stakeholder Specialist(s) Objective EIPR Objective Coordinator FCM05 N. AGACDIKEN O. CIOARA Sergejs OVSJANIKOVS – LGS INF04 P. MATERN A-P. FRANGOLHO Vadims TUMARKINS – LGS ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Vadims TUMARKINS – LGS ITY-AGDL E. CERASI, S. DISSING A. KOKONA Ainars SNEPSTS – LGS ITY-AGVCS2 J. ROCA O. ALFARO Ainars SNEPSTS – LGS ITY-COTR S. MORTON L. DELL’ORTO Igors NEMAHOVS – LGS ITY-FMTP B. GASZTYCH, J. POUZET O. ALFARO Igors NEMAHOVS – LGS ITY-SPI M. BORELY, R. STEWART A-P. FRANGOLHO Aleksejs JAVORSKIS – LGS NAV03 F. PAVLICEVIC A. KOKONA Vadims TUMARKINS – LGS NAV10 R. FARNWORTH, F. PAVLICEVIC A. KOKONA Vadims TUMARKINS – LGS SAF10 T. LICU I. FEIJT Alvis VILKS – LGS SAF11 S. LAWRENCE I. FEIJT Vadims ULJANOVSKIS – LGS

LSSIP Year 2013 Latvia 34 Released Issue

Annex B – National Stakeholders Organisation Charts

LSSIP Year 2013 Latvia 35 Released Issue

LSSIP Year 2013 Latvia 36 Released Issue LSSIP Year 2013 Latvia 37 Released Issue Annex C – Glossary of Abbreviations

This Annex only shows the Abbreviations that are specific to the Latvian LSSIP.

ATRACC Air Traffic Control System for Riga Area Control Centre LCAA Civil Aviation Agency of Latvia LFV Luftfartsverket LGS Latvijas Gaisa Satiksme NEFAB North European Functional Airspace Block NEFRA North European Free Route Airspace TAIIB Transport Accident and Incident Investigation Bureau

LSSIP Year 2013 Latvia 38 Released Issue