EUROCONTROL

Local Single Sky ImPlementation (LSSIP) LATVIA

Year 2015 - Level 1

DOCUMENT IDENTIFICATION SHEET

LSSIP for Latvia

Infocentre Reference: 16/01/29-75

Document Identifier Edition: Year 2015

LSSIP Year 2015 Latvia Edition Date: 25/04/16

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

LSSIP Contact Person - Luca DELL’ ORTO E-mail: Unit DPS/PEPR [email protected]

Status Intended for

Working Draft  General Public 

Draft  Agency Stakeholders 

Proposed Issue  Restricted Audience 

Released Issue 

Accessible via: Internet (www.eurocontrol.int)

Path: Y:\03 LSSIP\1. LSSIP States\Latvia (LV) - LDO\Year 2015\Released\LSSIP Year 2015_Latvia Released.docx

LINKS TO REFERENCE DOCUMENTS

1 LSSIP Guidance Material http://www.eurocontrol.int/articles/lssip 2 ESSIP Plan Edition 2015 http://www.eurocontrol.int/pepr 3 European ATM Portal Working - https://www.eatmportal.eu/working Public - https://www.atmmasterplan.eu/ 4 ESSIP Report 2014 http://www.eurocontrol.int/pepr 5 STATFOR Forecasts http://www.eurocontrol.int/statfor 6 Acronyms and http://www.eurocontrol.int/articles/glossaries abbreviations 7 LSSIP Documents http://www.eurocontrol.int/articles/lssip 8 AIP of Latvia https://ais.lgs.lv/Latvian%20eAIP 9 FAB Performance Plan https://www.eurocontrol.int/articles/ses-performance-scheme-reference-period-2- 2015-2019

LSSIP Year 2015 Latvia Released Issue

APPROVAL SHEET

The following authorities have approved all parts of LSSIP Year 2015 document and their signature confirms the correctness of the reported information and reflects their commitment to implement the actions laid down in the European Single Sky ImPlementation (ESSIP) Plan. – Edition 2015.

LSSIP Year 2015 Latvia 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 ...... 6 1.2 National Stakeholders ...... 6 1.2.1 Civil Regulator(s) ...... 7 1.2.2 Air Navigation Service Provider ...... 8 1.2.3 Airports ...... 9 1.2.4 Military Authorities ...... 9 Chapter 2 - 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 2011-2020 ...... 13 2.2.2 Summer 2015 performance ...... 13 2.2.3 Planning Period 2016-2020 - Summer ...... 14 Chapter 3 - ESSIP Report recommendations ...... 16 Chapter 4 - National Projects ...... 17 Chapter 5 - Regional Co-ordination ...... 22 5.1 FAB Co-ordination ...... 22 5.2 FAB Projects ...... 22 5.3 Regional cooperation ...... 23 5.3.1 Regional Cooperation Initiatives ...... 23 5.3.2 Regional Projects ...... 23 Chapter 6 - ESSIP Objective Implementation ...... 25 6.1 Conventions ...... 25 6.2 ESSIP Objectives Implementation progress ...... 26 6.3 Alignment of PCP with ESSIP Objectives and related progress ...... 44

ANNEXES Annex A – Specialists involved in the LSSIP Process 45 Annex B – National Stakeholders Organisation Charts 47 Annex C – Glossary of Abbreviations 50

LSSIP Year 2015 Latvia Released Issue

Executive Summary

National ATM Context In November 2015, Latvia, along with the rest of NEFAB states implemented Free Route Airspace above FL95, to facilitate environment friendly and more efficient flight trajectories.

Traffic and Capacity Latvia has no issues with capacity. Traffic in Latvia increased by 0.1% during summer 2015 (May to October inclusive) when compared to summer 2014. No problem of capacity is foreseen in Riga ACC in the 2016-2020 planning period. Medium forecast predicts an average annual air traffic growth between 0.1% and 5.0%.

ESSIP Objective Implementation Based on the 2015 ESSIP Objective implementation data in Latvia, overall implementation of the the ESSIP Objectives is either in planning phase, completed or not applicable. The following objectives have yet to be completed: ATC07.1 (EVRA), COM10 and FCM01. Implementation of ground-ground automated co-ordination processes of the ITY-COTR objective was completed by 2015, with the exception of those services based on the use of Data Link. These are planned for implementation in 2018, in accordance with the requirements in the amended DLS regulation.

LSSIP Year 2015 Latvia 1 Released Issue

* FOC Date LSSIP 2015 - Latvia █ Planned implementation date (see legend at the bottom of the table)

State-related ESSIP Objectives 2015 2016 2010 2011 2012 2013 2014 2017 2018 2019 2020 2021 2022 2023 <=2009

Harmonise Operational Air Traffic (OAT) and General Air AOM13.1 Traffic (GAT) handling *

AOM19 Implement Advanced Airspace Management * [PCP] AOM21.1 Implementation of Direct Routing [E] * [PCP] AOM21.2 Implement Free Route Airspace [E] *

AOP03 Improve runway safety by preventing runway incursions * Implement ground based safety nets - Area Proximity ATC02.5 Warning - level 2 * Implement ground based safety nets - Minimum Safe ATC02.6 Altitude Warning - level 2 * Implement ground based safety nets - Approach Path ATC02.7 Monitor - level 2 * Implement automated support for conflict detection, ATC12.1 resolution support information and conformance monitoring * Implement, in En-Route operations, information exchange ATC15 mechanisms, tools and procedures in support of Basic * AMAN operations

ATC16 Implement ACAS II compliant with TCAS II change 7.1 * Electronic Dialogue as Automated Assistance to Controller ATC17 during Coordination and Transfer *

COM10 Migrate from AFTN to AMHS * Implementation of Voice over Internet Protocol (VoIP) in COM11 ATM *

FCM01 Implement enhanced tactical flow management services *

FCM03 Implement collaborative flight planning *

FCM04 Implementation of Short Term ATFCM Measures - phase 1

[PCP] FCM05 Implementation of interactive rolling NOP [E] * [PCP] FCM06 Traffic Complexity Assessment [E] *

INF04 Implement integrated briefing *

INF07 Electronic Terrain and Obstacle Data (TOD) *

ITY-ACID Aircraft identification

Ensure quality of aeronautical data and aeronautical ITY-ADQ information *

ITY-AGDL Initial ATC air-ground data link services above FL-285 *

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

Implement 8,33 kHz air-ground voice channel spacing ITY-AGVCS2 below FL195 * Implementation of ground-ground automated co-ordination ITY-COTR processes *

ITY-FMTP Apply a common flight message transfer protocol (FMTP) *

ITY-SPI Surveillance performance and interoperability *

NAV03 Implementation of P-RNAV *

NAV10 Implement APV procedures * Implement measures to reduce the risk to aircraft operations SAF10 caused by airspace infringements *

SAF11 Improve runway safety by preventing runway excursions *

Airport-related ESSIP Objectives 2015 2016 2010 2011 2012 2013 2014 2017 2018 2019 2020 2021 2022 2023 <=2009 EVRA-Riga Airport Implement Advanced Surface Movement Guidance and AOP04.1 Control System (A-SMGCS) Level1 * Implement Advanced Surface Movement Guidance and AOP04.2 Control System (A-SMGCS) Level 2 *

AOP05 Implement Airport Collaborative Decision Making (CDM)

[PCP] AOP10 Time Based Separation [E] [PCP] AOP11 Initial Airport Operations Plan [E] * Improve runway and airfield safety with ATC clearances [PCP] AOP12 monitoring [E]

ATC07.1 Implement AMAN tools and procedures * Implement Continuous Descent Operations (CDO) ENV01 techniques for environmental improvements Implement Collaborative Environmental Management ENV02 (CEM) at Airports

Understanding the Table

Objective Completed No Plan

Objective Partly Completed Missing Data

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

Late

E= Essential – Master Plan Reference PCP = Pilot Common Project

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

LSSIP Year 2015 Latvia 3 Released Issue

Introduction

The Local Single Sky ImPlementation documents (LSSIPs), as an integral part of the ESSIP/LSSIP mechanism, constitute a short/medium term implementation plan containing ECAC States’ actions to achieve the Implementation Objectives as set out by the ESSIP and to improve the performance of their national ATM System. The LSSIP document – Year 2015 describes the situation in the State at the end of December 2015.

The LSSIP documents are structured into 6 chapters to better differentiate the Stakeholder(s) accountable for the information contained in each of them:

 Chapter 1 provides an overview of the ATM institutional arrangements within the State, the membership of the State in various international organizations, the organizational structure of the main ATM players - civil and military - and their responsibilities under the national legislation. In addition, an overview of the Airspace Organization and Classification, the ATC Units, the ATM systems operated by the main ANSP are also provided in this chapter.

 Chapter 2 provides a comprehensive picture of the situation of Air Traffic, Capacity and ATFM Delay per each ACC in the State. It shows the evolution of Air Traffic and Delay in the last five years and the forecast for the next five years. It gives also the achieved performance in terms of delay during the summer season period and the planned projects assumed to offer the required capacity which will match the foreseen traffic increase and keep the delay at the agreed performance level;

 Chapter 3 provides a set of recommendations extracted from the ESSIP Report which are relevant to the state/stakeholders concerned. The state reports how they have handled those recommendations and the actions taken during the year to address the concerns expressed by those recommendations;

 Chapter 4 provides a set of the main ATM national projects which contribute directly to the implementation of the ATM MP OIs and/or Enablers and ESSIP related Objectives. The description, timescale, progress made and expected contribution to the ATM Key Performance Areas are provided by the states per each project included in this chapter;

 Chapter 5 deals with the ATM Regional Coordination. It provides an overview of the FAB cooperation and Projects and also all other regional initiatives and Projects which are out of the FAB scope. The content of this chapter generally is developed and agreed in close cooperation between the states concerned;

 Chapter 6 contains high-level information on progress and plans of each ESSIP Objective. The information for each ESSIP Objective is presented in boxes giving a summary of the progress and plans of implementation for each Stakeholder. The conventions used are presented at the beginning of the section.

Note: Chapter 6 is completed with a separate document called LSSIP Level 2. This document consists of a set of tables organised in line with the list of ESSIP Objectives. Each table contains all the actions planned by the four national stakeholders to achieve their respective Stakeholder Lines of Action (SLoAs) as established in the ESSIP.

Note: The information contained in Chapter 6 is deemed sufficient to satisfy State reporting requirements towards ICAO in relation to ASBU (Aviation System Block Upgrades) monitoring.

LSSIP Year 2015 Latvia 4 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 EASA  1 May, 2004 ICAO  13 July, 1992 NATO  1 May, 2004 ITU  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 Sweden. 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 2015 Latvia 5 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 2015 Latvia 6 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 Legal Basis responsible Rule-making Cabinet of Ministers Constitution Safety Oversight LCAA Law on Aviation Enforcement actions in case of LCAA Law on Aviation non-compliance with safety regulatory requirements Airspace LCAA Law on Aviation , Cabinet of Ministers regulation N° 507(28.06.2011.) Economic Department of Law on Aviation , Air Transport (MoT) Cabinet of Ministers regulation N° 991 (5.12.2006.) Environment LCAA Law on Aviation , Cabinet of Ministers regulation N° 487 (20.06.2006.) and N° 1041 (27.12.2005) Security LCAA Law on Aviation , Cabinet of Ministers regulation N° 397 (27.04.2010.) Accident investigation Transport Accident and Law on Aviation , Investigation Bureau Law on accident and incident investigation in civil aviation

LSSIP Year 2015 Latvia 7 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 LCAA, is nominated as the National Supervisory Authority (NSA). The LCAA is 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. LCAA is 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 http://www.caa.lv/upload/userfiles/files/Publiskais%20p%C4%81rskats%202 014.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

1.2.2.1 Services provided

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); Other training for ATM staff (Development Training; Classroom Instructors and ATM Management Staff Training). Others Y FIS (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 2015 Latvia 8 Released Issue

1.2.2.2 ATC systems in use

FDPS

Specify the manufacturer of the ATC system currently in use: SiATM (Sweden) Upgrade1 of the ATC system is performed or planned? 2015 Replacement of the ATC system by the new one is planned? No, next upgrade is planned for 2017 ATC Unit RIGA ACC

SDPS

Specify the manufacturer of the ATC system currently in use: SiATM (Sweden) Upgrade1 of the ATC system is performed or planned? 2015 Replacement of the ATC system by the new one is planned? No, next upgrade is planned for 2017 ATC Unit RIGA ACC

1.2.2.3 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 below FL095 in Western part of FIR

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 Referring to the List of Airports in the ESSIP Plan – Part I Section 4, it is up to the individual State to decide which additional airports will be reported through LSSIP for those objectives. According to these criteria the airport covered in this LSSIP is Riga 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;

1 Upgrade is defined as any modification that changes the operational characteristics of the system (SES Framework Regulation 549/2004, Article 2 (40))

LSSIP Year 2015 Latvia 9 Released Issue - 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

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:N/A Additional information: N/A

LSSIP Year 2015 Latvia 10 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 2015 Latvia 11 Released Issue Chapter 2 - Traffic and Capacity

2.1 Evolution of traffic in Latvia

Latvia - Annual IFR Movements

350.000

300.000

250.000

200.000

IFR flights 150.000 IFR movements - Actuals

100.000 IFR movements - Baseline forecast IFR movements - High forecast 50.000 IFR movements - Low forecast A = Actual F = Forecast 0 2011 A 2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F

EUROCONTROL Seven-Year Forecast (September 2015) IFR flights yearly growth 2012 A 2013 A 2014 A 2015 F 2016 F 2017 F 2018 F 2019 F 2020 F 2021 F H 1.3%5.4%5.2%4.6%4.6%5.1%4.1% Latvia B -1.0% 1.3% 2.8% 0.7% 2.0% 2.3% 2.3% 2.5% 2.6% 1.9% L 0.1% -2.0% 0.0% 0.4% 0.9% 1.0% 0.5% ESRA08 B -2.4% -1.1% 1.7% 1.6% 2.3% 2.3% 2.3% 2.2% 2.7% 1.8%

2015 Traffic in Latvia increased by 0.1% during Summer 2015 (May to October inclusive), when compared to Summer 2014.

2016-2020

The STATFOR medium-term forecast (MTF) predicts an average annual traffic growth between 0.1% and 5.0% throughout the planning cycle, with a baseline growth of 2.3%.

LSSIP Year 2015 Latvia 12 Released Issue 2.2 RIGA ACC

2.2.1 Traffic and en-route ATFM delays 2011-2020

EVRRACC - Traffic and en-route ATFM delays

1000 1.0

900 0.9

800 0.8

700 0.7

600 0.6

500 0.5

400 0.4 IFR flights (Daily Average) (Daily flights IFR 300 0.3 Enroute Delay (minutes per flight) per (minutes Delay Enroute

200 0.2

100 0.1

0 0.0 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 Peak Day Traffic 819 833 831 841 843 Summer Traffic 716 704 714 738 739 Yearly Traffic 639 634 642 659 662 Summer Traffic Forecast 740 751 771 791 812 High Traffic Forecast - Summer 755 795 838 878 921 Low Traffic Forecast - Summer 712 718 727 733 737 Summer enroute delay (all causes) 0.00 0.00 0.00 0.00 0.00 Yearly enroute delay (all causes) * 0.00 0.00 0.00 0.00 0.00

*From 01/01/2015 to 31/10/2015

2.2.2 Summer 2015 performance

En-route Delay (min/flight) - Summer Capacity Traffic Evolution 2015 Capacity Baseline Ref value Actual gap + 0.1 % 85 (0%) 0.06 0.00 No The average en-route delay per flight remained at zero minutes per flight in Summer 2015.

Capacity Plan Sufficient capacity to meet demand Achieved Comments Various ATM system improvements Yes Maximum configuration: 3 + 2 APP Yes 4 sectors were opened Summer 2015 performance assessment The capacity baseline was estimated at the same level as in 2014. The average peak 1 hour demand was 64 and the peak 3 hour demand was 58 flights during the measured period, indicating that the ACC offered sufficient capacity to meet the demand.

LSSIP Year 2015 Latvia 13 Released Issue

2.2.3 Planning Period 2016-2020 - 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. En-route ATFM delay breakdown - Reference Values EVRRCTA 2016 2017 2018 2019 Annual 0.03 0.04 0.03 0.03 Summer 0.05 0.05 0.05 0.05

Capacity Profiles 2015 Profiles (hourly movements and % increase over previous year) ACC baseline 2016 2017 2018 2019 H 85 0% 86 1% 89 3% 95 7% Ref. 85 0% 85 0% 86 1% 87 1% EVRR 85 L 85 0% 85 0% 85 0% 85 0% Open 86 1% 86 0% 87 1% 88 1% 86 1% 86 0% 87 1% 88 1% C/R Capacity Plan 2015 2016 2017 2018 2019 Free Route Airspace Airspace Management

Advanced FUA Airport & TMA Network

Integration Cooperative Traffic

Management Airspace Procedures Staffing Technical Various ATM system improvements Capacity Significant Events Max sectors 3 + 2 APP 3 + 2 APP 3 + 2 APP 3 + 2 APP 3 + 2 APP Capacity increase p.a. Sufficient capacity to meet demand Reference profile 0% 0% 1% 1% N/A

Additional information

LSSIP Year 2015 Latvia 14 Released Issue EVRRCTA - Reference capacity profile and alternative scenarios 100

90 hour) 80 per

70 (movements

profile

60 Capacity

50

40 2014 2015 2016 2017 2018 2019 2020 2016‐2019 Reference Capacity Profile 85 85 86 87 Capacity Profile ‐ Shortest Routes (Open) 86 86 87 88 Capacity Profile ‐ Current Routes 86 86 87 88 Capacity Profile ‐ High 85 86 89 95 Capacity Profile ‐ Low 85 85 85 85 Capacity Baseline 85 85 2016 ‐ 2020 Plan 86 86 89 95 95

2016-2020 Planning Period Outlook No problems are foreseen for Riga ACC during the planning period.

LSSIP Year 2015 Latvia 15 Released Issue Chapter 3 - ESSIP Report recommendations

Recommendations issued from the ESSIP Report for 2014 applicable to Latvia for all items that require corrective actions and improvements.

Reference Recommendation 2014 Ownership number Local Stakeholders that declared delays in implementation of FCM01, AOP04.1, SAF10, INF04, NAV03, AOP03, ENV01, ITY- Local REC-2014-2 AGDL, ITY-ADQ, COM09, COM10, ITY-FMTP and ITY-COTR, to Stakeholders take corrective measures to reduce the implementation delays. Corrective actions taken: YES

Description: LGS: FCM01-ASP02 is late. Provision of Standard Correlated Position Data is expected by 30/04/2016.

LGS: COM10-ASP03 Enhance AMHS capability (Extended ATSMHS) is late. LGS has signed a contract with manufacturer on system upgrade by 31/12/2016.

LGS: Currently no delay is expected by other objectives and SloAs. REC-2014-06 The ANSPs within a FAB should coordinate their system renewal (equal to REC- and capability evolution more closely in order to deliver larger FAB ANSPs 2013-15) scale performance improvements to customers. Corrective actions taken: YES

Description: LGS: ATM system modernisation in the frame of FRA implementation was coordinated together with NEFAB and Borealis partners. FRA was implemented successfully within NEFAB airspace. Data link implementation is a subject of close coordination and partnership with NEFAB and Borealis alliance.

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

Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas Other references LGS (LV) ATRACC - The title ATRACC (Air Traffic Riga Area November Project is in progress. The ESSIP:AOM21.2, Capacity: CPDLC: Increased capacity through 2014+ (RP- Control Centre) comprises an ATM 2013 / June ATM modernization is ITY-ADQ, ITY-AGDL, both reduction of voice congestion and increase AD/PLN-01/57 system for tower, approach and area 2016 moving smoothly as ITY-COTR, ITY- of controller efficiency. (2013)) control of the Riga FIR. The system has prescribed by the Project FMTP FRA: The implementation of free route airspace been designed and produced by the Management Plan. OI-Steps: AOM- brings significant flight efficiency benefits to Swedish company Systemintegrering AB. Corresponding software 0401, AOM-0402, airspace users due to user preferred routes. As a The system is based on multi-sensor modules for CPDLC and AOM-0501, AOM- step to full trajectory based operations the FRA tracking, advanced flight plan data Free Route Airspace 0502, AUO-0301, concept brings increased flight predictability, processing, predicted flight trajectories, functionality were developed CM-0102-A, CM- reduced uncertainty for the Network which in turn OLDI (On-Line Data Interchange), silent in time. Interface to LARA 0201, IS-0202, IS- can lead to capacity increase for ATM which will co-ordination and paperless HMI. system is developed. 0204 also benefit the user. From the functional point of view, the DMAN: Improved airport / TMA capacity. Other: - system consists of two main components: Safety: CPDLC: Through the delivery of Primary System, providing the full set of standard and unambiguous messages (entailing functionalities described above, and significant error and fatigue reduction), the Radar Bypass System as a backup if the provision of a communications back up and the primary system failed. possibility of immediate message retrieval, data This open architecture system can easily link communications are a major safety be expanded. It comprises more than 15 enhancement. working positions intended for operators FRA: Some enhancement through reduction in with different operational roles, specifically controller workload. TWR (tower), ACC (Area Control), APP DMAN: The same or improved safety. (Approach Control), ARCC (Area Rescue AUTOMATED AERONAUTICAL DATA INPUT: Co-ordination Centre), FDA (Flight Data Improved consistency, reliability and integrity of Assistant), HIST (History, Recording and data. Playback), OSUP (Operational Supervisor) and TSUP (Technical Environment: FRA: The free route airspace Supervisor). implementation brings significant flight efficiency The system has experienced some benefits namely: reductions in emissions through modernization stages. Current the use of optimal routes and preferred flight modernization project named ATRACC – profiles. 2014+ aims system upgrade for: DMAN: A positive environmental effect in terms • CPDLC functionalities; of noise and fuel usage due to reduced holding • Free Route Airspace and low level vectoring. implementation (this part is coordinated Cost-Efficiency: CPDLC: Data link is a cost- with NEFAB); effective capacity increase enabler through

LSSIP Year 2015 Latvia 17 Released Issue Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas Other references • Departure Manager (D-MAN); sector productivity increase and delay cost • New tower working positions savings. ANSPs savings derived from staff cost implementation (TWR Supervisor & avoidance. Aircraft operators will benefit of en Clearance Delivery); route cost savings and reduction of delays. • Automated aeronautical data FRA: The implementation of free route airspace input; brings significant flight efficiency benefits to • Others. airspace users due to user preferred routes. As a step to full trajectory based operations the FRA CPDLC module of ATM system concept brings increased flight predictability, modernization is a subject of CPDLC reduced uncertainty for the Network which in turn Implementation Project as well. can lead to capacity increases for ATM which will also benefit the user. DMAN: Reduced costs through reduction in delays. AUTOMATED AERONAUTICAL DATA INPUT: Avoidance of repair, correction and re-work activities at data provider and data user level as a necessary step towards the implementation of system wide information management. CPDLC THE PROJECT OBJECTIVE January 2014 PROGRESS ESSIP:ITY-AGDL Capacity: Increased capacity through both Implementati The project objective is implementation of 2014 / Within 2014 the main efforts OI-Steps: AUO-0301 reduction of voice congestion and increase in on in the CPDLC services in accordance with February are focused on two controller efficiency. RIGA FIR (RP- COMMISSION REGULATION (EC) No 2018 packages: the ATM System Other: It is a transversal project Safety: Through the delivery of standard and AD/PLN-01/2 29/2009 of 16 January 2009 laying down Upgrade and the Data Link unambiguous messages (entailing significant (2014)) requirements on data link services for the Communication with ATRACC 2014+ . error and fatigue reduction), the provision of a single European sky. It means a Infrastructure. The ATM communications back up and the possibility of compliance with all applicable ICAO modernization is moving immediate message retrieval, data link standards, corresponding community smoothly as prescribed by communications are a major safety specifications as well as user needs. the Project Management enhancement. Plan. In contrast the Data Environment: - TRANSVERSAL PROJECT Link Communication Cost-Efficiency: Data link is a cost-effective Inside LGS the project crosses with the Infrastructure package capacity increase enabler through sector “ATRACC 2014+” project. The last one is experienced some productivity increase and delay cost savings. a separate complex project focused on: disturbances. In June 2014 ANSPs savings derived from staff cost Free Route Airspace Implementation; the EC has acknowledged avoidance. Aircraft operators will benefit of en- Departure Manager and some other the technical problems with route cost savings and reduction of delays. features. CPDLC module is just a part of data link services. LGS was the ATRACC 2014+ project (CPDLC forced to put the project on a related functions; HMI; others). On the temporary hold, to await the EC decision. In July LGS

LSSIP Year 2015 Latvia 18 Released Issue Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas Other references other hand the modernization of ATM Board decided to postpone system is an absolute pre-requisite for a discussion of the contract CPDLC successful implementation. with SITA and ARINC. This pause will help LGS to take THE PROJECT STAKEHOLDERS into account all new 1. Customer: LGS; requirements of the 2. Target group: airspace users; European Commission if 3. Subject of EC Regulation : any. However the CPDLC Republic of Latvia; implementation project is not 4. SES dimension: NEFAB + IDP; closed. LGS is eager to 5. Sponsorship: EC (INEA former continue based on a new TEN-T Agency); clear roadmap. Currently 6. Communication Service Providers: LGS continues SITA & ARINC; modernisation of ATM 7. Developer of ATM System: system preparing the SiATM. platform for CPDLC implementation.

THE PROJECT COMPRISES 8 WORKING PACKAGES: 2015 PROGRESS 1. Project Management; Within 2015 the Project 2. Data Link Communication Management Plan was Infrastructure; reviewed as per the 3. ATM System Upgrade; Regulation (EU) 2015/310. 4. Provision of Initial Operations; The project mangement 5. Training of LGS Staff; team is awaiting results and 6. Validation; new technical solutions (if 7. Assessment of the Fleet any) from the SJU study. All Equipage; appropriate activities for the 8. Coordination with neighbours. TEN-T funding closure to be completed by March 2016. Communicati The project objective is enhancement of December The project is ongoing. LGS ESSIP:COM10 Capacity: - on Project existing AMHS functionality adding new 2016 has signed a contract with OI-Steps: - Safety: A harmonised set of safety functions according to the requirements of manufacturer to upgrade requirements. the ESSIP (COM10-ASP03) and ATM AFTN/AMHS system and Other: - Master Plan (CTE-C10). One of the new implement AMHS Extended Environment: Reduction of power consumption system components is going to be "AMHS functionality. and heating emission. to SWIM Connector" providing SWIM. Cost-Efficiency: Use of COTS messaging systems. Support exchange of any kind of message format including new binary data. Cost reduction of messaging services at the end.

LSSIP Year 2015 Latvia 19 Released Issue Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas Other references PBN Analysis of the existing airspace structure March 2013 During 2015 PBN Project ESSIP:COM10, Capacity: 1. Increase airspace capacity. Implementati of Riga FIR, development, validation and / November Team created technical ENV01, NAV03, 2. Increase of traffic compared to 2013. on Project implementation of PBN air space 2016 specification and rules of a NAV10 3. Reduction of flight time in TMA. (RP-AD/PLN- elements and procedures. tender. The tender was OI-Steps: AOM- Safety: 1. Reduction of numbers of incidents 01/6 (2013)) issued to all interested 0601, AOM-0602, related to airspace design and volume. parties globally. There were AOM-0604, AOM- 2. Reduction of known interface challenges in 5 bidders who expressed 0701 specific areas. their interest and submitted Other: - 3. Segregation of air routes and de-conflicting of requested documentation to SIDs/STARs. the Tender Committee. 3. Improvement of safety compared to a 2008 Currently Tender Committee baseline. performs evaluation of selected candidates. Environment: 1. Reduction of CO2 emissions and noise by means of new airspace and route design. 2. The target is 5% reduction of CO2 emissions per flight Cost-Efficiency: 1. Increase of traffic with the same staff. 2. Increase of revenues and reduction of unit rates. 3. The airports will be given incentives for growth and increase of revenues. LGS (LV), RIGA Airport (LV) A-SMGCS A-SMGCS modernization with „Follow- May 2012 / System upgrade was ESSIP:AOP04.2 Capacity: 1. Increase of capacity compared to Modernisatio the-Green” concept. November completed successfully. OI-Steps: AO-0102, 2013 due to reduced taxing time on the ground. n (RP- 2017 Transition to the upgraded AO-0201 Safety: 1. Reduction of incidents related to RWY AD/PLN-01/20 system is planned within Other: - incursions. (2012)) 2016. Besides of hardware 2. An integrated system processing the data and software upgrade the from ATM and A - SMGCS systems. The system system comprises a bunch will provide ATCOs with reliable data on air and of new functionalities for ground situation. instance "stop - bar" 3. Improved safety compared to the 2008 monitoring and control. baseline. Environment: Reduction of CO2 emissions and noise due to better traffic management on the ground. Cost-Efficiency: 1. Increase of capacity as well as improvements of the service provision.

LSSIP Year 2015 Latvia 20 Released Issue Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas Other references 2. Increased traffic with the same staff number. 3. Increase of revenues and reduction of unit rates. 4. The airports will be given incentives for growth and increase of revenues. Collaborative The project aims increase capacity of the September The working group was ESSIP:AOP05 Capacity: 1. Traffic increase due to CDM (2013 Decision RIGA International Airport by means of A- 2012 / established in September OI-Steps: AO-0501, baseline). Making (CDM) CDM implementation. Initial steps assume November 2012. Memorandum of AO-0601, AO-0602, 2. Reduction of flight time on the ground. Implementati investigation of problems and 2019 Understanding between AO-0603 3. Increase airspace capacity on in Riga development of Implementation Plan. stakeholders (LGS; RIX and Other: - Safety: 1. Airport operators, aircraft operators, Airport (RP- AirBaltic Company) was ground handlers and air traffic control use real AD/PLN-01/43 signed. The working group time data sharing. Due to this an accurate and (2012)) has started development of timely information will provide more safe and A-CDM operational efficient flights. procedures. Environment: 1. Reduction of flight time on the ground. Cost-Efficiency: 1. Reduction of flight time on the ground. 2. Increased traffic with the same staff number. 3. Increase of revenues and reduction of unit rates. 4. The airports will be given incentives for growth and increase of revenues.

LSSIP Year 2015 Latvia 21 Released Issue Chapter 5 - Regional Co-ordination

5.1 FAB Co-ordination North European Functional Airspace Block ‐ NEFAB

NEFAB was established by Estonia, Finland, Latvia and Norway in 2012. NEFAB ANSPs have established a programme with the objective of managing projects and initiatives among the ANSPs in the cooperation. The NEFAB Programme regularly develops and maintains 5 year business plans, and on that basis develops the annual business plans for use by NEFAB ANSPs in order to follow up NEFAB Programme projects and activities. The latest 5 year business plan is covering the period 2016 - 2020 with the annual plan and budget for 2016. 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 concrete activities planned for each year with defined deliverables and milestones. In November 2015 The NEFAB Target Concept Scenario 6 was implemented. The Target Concept is defined in the NEFAB Network Plan, composed of key elements being Free Route Airspace, Service Provision, ASM and FUA concepts as well as rules, procedures and ATM functionalities supporting the concept. The FRA is composed of three volumes being Estonia, Finland and Latvia as one seamless FRA above FL95, and Norway above FL135. FRA in Bodø Oceanic will be implemented above FL195 in accordance with the formal ICAO NAT procedures in summer 2016. In June 2016 NEFAB FRA will be further developed by implementation of Scenario 8, i.e. NEFAB FRA to be one seamless FRA volume connected seamless with the Danish/Swedish FAB (see 5.3.1 Regional Cooperation Initiatives). The individual ANSP´s in the FAB-cooperation will implement the required operational changes and technical support to enable the concept described in the NEFAB Target Concept.

5.2 FAB Projects

Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas * Other references AVINOR AS (NO), EANS (EE), FINAVIA (FI), LGS (LV) NEFAB Implement seamless FRA volume across Target date: Active, on-time. ESSIP:AOM19, Capacity: Present or additional capacity Target all NEFAB States. 23. June AOM21.2 Safety: Present or improved safety Concept 2016 OI-Steps: AOM- (Scenario 8) Environment: Present or improved, depending 0201, AOM-0202, on airspace users AOM-0205, AOM- 0401, AOM-0402, Cost-Efficiency: For the airspace users: AOM-0501, AOM- improved cost efficiency 0502, CM-0102-A, DCB-0203

LSSIP Year 2015 Latvia 22 Released Issue 5.3 Regional cooperation

5.3.1 Regional Cooperation Initiatives North European Free Route Airspace (NEFRA) programme NEFAB is closely cooperating with DK SE FAB with an agreed concept to implement a continuous an seamless FRA from a user perspective across the two FABs (North European Free Route Airspace (NEFRA) Programme). The NEFRA concept is implementation of a seamless interface in Scenario 8 between the two FABs above FL285 (Danish-Swedish FAB FRA is above FL285). In November 2015 the first milestone of NEFRA Phase 1 (Scenario 6) was implemented with harmonized FPL rules for FRA operations across the two FABs. Scenario 8 with seamless operations across the two FABs is planned to be implemented in June 2016. Borealis Alliance The Borealis Alliance Framework Agreement (AFA) is a legal document that sets up a framework for the business co-operation between 9 European ANSPs LFV (Sweden), Finavia (Finland), Avinor (Norway), ISAVIA (Iceland), Naviair (Denmark), EANS (Estonia), IAA (Ireland), LGS (Latvia) and NATS (UK). The vision of Borealis is to be the leading ANSP Alliance that enables its Members to drive better performance for stakeholders through business collaboration. The objective of the Alliance is to enable joint initiatives to improve flight efficiency and reduce environmental impact, delivered across the whole area in a move which will also streamline cost of services and operational/technical infrastructure. In 2015 Borealis Alliance initiated the Free Route Airspace (FRA) Programme to implement a multi-FAB FRA covering 3 FABs (NEFAB, DK-SE FAB and UK-IRL FAB) and Iceland. The Borealis concept of operation is based on the NEFRA concept, i.e. to connect the FRA volumes of 9 States seamlessly, so that these appear as one FRA volume to our customers (airspace users).

5.3.2 Regional Projects

Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas * Other references AVINOR Air Navigation Services (NO), EANS (EE), FINAVIA (FI), LFV (SE), LGS (LV), Naviair (DK) Borealis FRA Implementation of FRA in Scottish FIR, End 2018 Active, on-time ESSIP:AOM19, Capacity: Present or additional capacity Interface with NEFAB and DK/SE FAB AOM21.2 Safety: Present or improved safety FRAs. OI-Steps: AOM- Environment: Present or improved, depending 0201, AOM-0202, on airspace users AOM-0205, AOM- 0401, AOM-0402, Cost-Efficiency: For the airspace users: AOM-0501, AOM- improved cost efficiency 0502, CM-0102-A, DCB-0203 Other: - Borealis FRA Implementation of FRA in London FIR, End 2021 Active, on time ESSIP:AOM19, Capacity: Present or additional capacity

LSSIP Year 2015 Latvia 23 Released Issue Name / Code Description - Scope Schedule Status Link with ATM Expected Contribution to the Key Master Plan / Performance Areas * Other references Interface with neighbouring FRA volumes AOM21.2 Safety: Present or improved safety Implementation of FRA in Icelandic OI-Steps: AOM- Environment: Present or improved, depending Airspace, Interface with neighbouring FRA 0201, AOM-0202, on airspace users volumes AOM-0205, AOM- Cost-Efficiency: For the airspace users: 0401, AOM-0402, improved cost efficiency AOM-0501, AOM- 0502, CM-0102-A, DCB-0203 Other: - NEFRA phase Implementation of seamless interface of 23 June, Active, on-time ESSIP:AOM19, Capacity: Present or additional capacity 1 (Scenario 8) NEFAB FRA and DK/SE FAB FRA above 2016 AOM21.2 Safety: Present of improved safety FL285 OI-Steps: AOM- Environment: Present or improved, depending 0201, AOM-0202, on airspace users AOM-0205, AOM- 0401, AOM-0402, Cost-Efficiency: For the airspace users: AOM-0501, AOM- improved cost efficiency 0502, CM-0102-A, DCB-0203 Other: - NEFRA phase ATM systems upgrade and IFPS End 2017 Active, on time ESSIP:AOM19, Capacity: Present or additional capacity 2 (Scenario 8) integration AOM21.2 Safety: Present or improved safety OI-Steps: AOM- Environment: Present or improved, depending 0201, AOM-0202, on airspace users AOM-0205, AOM- 0401, AOM-0402, Cost-Efficiency: For the airspace users: AOM-0501, AOM- improved cost efficiency 0502, CM-0102-A, DCB-0203 Other: -

LSSIP Year 2015 Latvia 24 Released Issue Chapter 6 - ESSIP Objective Implementation

6.1 Conventions

Two colour codes are used for each ESSIP Objective ‘box’: o a colour code is used to show the Objective Scope in the Objective ID cell, and o another colour code is used to show the Objective Progress in the State and for each national stakeholder.

Obj. ID (*) Obj. Title (By mm/yyyy of overall objective, inc non-State SloAs) Obj. Progress (**) State’s high level progress statement State Impl. Date REG APO. Progress (**) REG high level progress statement (By:mm-yyyy) APO Impl. Date ASP ASP. Progress (**) ASP high level progress statement (By:mm-yyyy) ASP Impl. Date MIL MIL. Progress (**) MIL high level progress statement (By:mm-yyyy) MIL Impl. Date APO APO. Progress (**) APO high level progress statement (By:mm-yyyy) APO Impl. Date

(*) Objective Scope Code: (**) Objective/Stakeholder Progress Code: ECAC Completed No Plan EU+ Partly Completed Not Applicable Multi-N Planned Missing Data APT Late

LSSIP Year 2015 Latvia 25 Released Issue 6.2 ESSIP Objectives Implementation progress

Harmonise Operational Air Traffic (OAT) and General Air Traffic (GAT) handling

AOM13.1 Timescales: Not Applicable

Initial operational capability: 01/01/2012 Full operational capability: 31/12/2018 AAMS‐10a(EN), AIMS‐19b(EN), AOM‐0301(OI) ‐ 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 service to GAT traffic only. There is no military ATC 31/12/2018 providing services to OAT in Latvia. [Objective coordinated with FAB partners: ‐] REG (By:12/2018) State aircraft are handled as GAT outside of restricted areas or Not Applicable TSAs.Mixing of OAT and GAT air traffic is not authorized. Civil ATC CAA provides service to GAT traffic only. EUROAT document has been formally ‐ introduced to the military for consideration. There is no military ATC 31/12/2018 providing services to OAT in Latvia. ASP (By:12/2018) Not Applicable LGS Currently state aircraft are handled as GAT except specified areas (TSAs). ‐ 31/12/2018 MIL (By:12/2018) Military flying in the airspace under GAT rules, they fly OAT only in TSAs Not Applicable and in predefined specific areas. OAT is authorized to operate only under Mil. Authority ‐ military fighter control in segregated airspace.No plans to develop 31/12/2018 military ATC for OAT by 2018.

Implement Advanced Airspace Management Timescales: AOM19 Planned Initial operational capability: 01/01/2011 Full operational capability: 31/12/2016 AAMS‐11(EN), AOM‐0201(OI), AOM‐0202(OI), AOM‐0205(OI), AOM‐0401(OI), DCB‐0203(OI) ‐ FUA is implemented at all three levels. Advanced ASM / ATFCM process is under implementation in 31/12/2016 accordance with Eurocontrol Guidance materials. [Objective coordinated with FAB partners: FI,NO] ASP (By:12/2016) Borealis FRA / Partly Borealis FRA / Completed NEFAB Target Concept Advanced ASM process is under implementation in accordance with (Scenario 8) / LGS Eurocontrol Guidance materials. NEFRA phase 1 (Scenario 8) 31/12/2016 / NEFRA phase 2 (Scenario 8) Advanced ASM process is under implementation in accordance with Planned Mil. Authority ‐ Eurocontrol Guidance materials. 31/12/2016

LSSIP Year 2015 Latvia 26 Released Issue

Implementation of Direct Routing Timescales: [PCP] AOM21.1 Not Applicable Initial Operational Capability: 01/01/2015 [Essential] Full Operational Capability: 31/12/2017 AOM‐0401(OI), AOM‐0402(OI), AOM‐0500(OI) [E] ‐ Free route airspace in Latvia along with the rest of the NEFAB states has been implemented on November ‐ 12, 2015. [Objective coordinated with FAB partners: ‐] ASP (By:12/2017) Not Applicable LGS Latvia has already implemented FRA over FL095. ‐ ‐

Implement Free Route Airspace Timescales: [PCP] AOM21.2 Completed Initial operational capability: 01/01/2015 [Essential] Full operational capability: 31/12/2021 AOM‐0401(OI), AOM‐0402(OI), AOM‐0501(OI) [E], AOM‐0502(OI) [E], CM‐0102‐A(OI) [E] ‐ Latvia has implemented free route airspace above FL095 along with the other NEFAB member states on 12/11/2015 November 12, 2015. [Objective coordinated with FAB partners: FI,LV,NO] ASP (By:12/2021) ATRACC ‐ Completed 2014+ / Borealis FRA / Borealis FRA / NEFAB Target FRA over FL095 has been implemented in coordination with the NM and Concept LGS FAB partners. (Scenario 8) / 12/11/2015 NEFRA phase 1 (Scenario 8) / NEFRA phase 2 (Scenario 8)

LSSIP Year 2015 Latvia 27 Released Issue

Improve runway safety by preventing runway incursions Timescales: AOP03 Completed Initial operational capability: 01/04/2003 Full operational capability: 31/12/2013 AO‐0101(OI) ‐ The runway safety team is operational. LGS and the Riga airport have implemented the EAPPRI 31/12/2013 requirements. [Objective coordinated with FAB partners: ‐] REG (By:12/2013) The CAA issued an order to invite all involved stakeholders to create a Completed runway safety team and implement the specific recommendations from CAA ‐ the EAPRI (European Action plan for the prevention of runway 31/12/2006 incursions). ASP (By:12/2013) The runway safety team is operational. LGS has implemented all EAPPRI Completed LGS ‐ requirements. 31/12/2006 APO (By:12/2013) The runway safety team is operational. LGS and the Riga airport have Completed RIGA Airport implemented most of EAPRI requirements. All communications ‐ associated with runway operations are conducted using aviation English. 31/12/2013

Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level1

AOP04.1 Timescales: Completed

Initial operational capability: 01/01/2007 Full operational capability: 31/12/2011 AO‐0201(OI), CTE‐S02b(EN), CTE‐S03b(EN), CTE‐S04b(EN) EVRA ‐ Riga Airport A‐SMGCS Level 1 system is operational from 2007. The A‐SMGCS is composed by a surface movement 30/06/2007 radar and a multilateration system based on Mode A/C and Mode S. [Objective coordinated with FAB partners: ‐] REG (By:12/2010) LCAA has approved A‐SMGCS Level 1 operating procedures and the Completed CAA installations at Riga airport. Appropriate information has been published ‐ in the AIP EVRA AD 2‐20. Local Traffic regulations. 30/06/2007 ASP (By:12/2011) Completed LGS A‐SMGCS Level 1 system is operational at Riga International Airport. ‐ 30/06/2007 APO (By:12/2010) Completed RIGA Airport A‐SMGCS Level 1 system is operational at Riga International Airport. ‐ 31/12/2007

LSSIP Year 2015 Latvia 28 Released Issue

Implement Advanced Surface Movement Guidance and Control System (A‐SMGCS) Level 2

AOP04.2 Timescales: Completed

Initial operational capability: 01/01/2007 Full operational capability: 31/12/2017 AO‐0102(OI), AO‐0201(OI), CTE‐S02b(EN), CTE‐S03b(EN), CTE‐S04b(EN) EVRA ‐ Riga Airport A‐SMGCS Level 2 is fully implemented at the Riga International Airport. 31/12/2008 [Objective coordinated with FAB partners: ‐] ASP (By:12/2017) A‐SMGCS Completed A‐SMGCS Level 2 system is operational at Riga International Airport. LGS Modernisatio Approach controllers have the A‐SMGCS picture in view mode. n 31/12/2008 APO (By:12/2017) A‐SMGCS Completed RIGA Airport A‐SMGCS Level 2 is fully implemented at the Riga International Airport. Modernisatio n 31/12/2008

Implement Airport Collaborative Decision Making (CDM)

AOP05 Timescales: Not Applicable

‐ not applicable ‐ AO‐0501(OI), AO‐0601(OI), AO‐0602(OI), AO‐0603(OI) EVRA ‐ Riga Airport (Outside Applicability Area) The objective is not applicable to Riga International Airport. ‐ [Objective coordinated with FAB partners: ‐] ASP (By:12/2016) Collaborative Not Applicable Decision The objective is not applicable to Riga International Airport. As initial step Making to A‐CDM LGS and RIX have implemented data exchange between LGS (CDM) automated ATC system and Airport Flight Information Processing System. Implementati 31/12/2011 Agreement on data exchange is signed. on in Riga Airport APO (By:12/2016) Collaborative Not Applicable Decision As initial step to A‐CDM LGS and RIX have implemented data exchange Making between automated ATC system and Flight Planning Management System RIGA Airport (CDM) of RIX to provide silent coordination. Agreement on data exchange is Implementati ‐ signed. on in Riga Airport

LSSIP Year 2015 Latvia 29 Released Issue

Time Based Separation [PCP] AOP10 Timescales: Not Applicable [Essential] ‐ not applicable ‐ AO‐0303(OI) [E] EVRA ‐ Riga Airport (Outside Applicability Area) Latvian airports are not in applicability area ‐ [Objective coordinated with FAB partners: ‐] REG (By:12/2023) ASP (By:12/2023) Not Applicable LGS ‐ ‐ ‐

Initial Airport Operations Plan Timescales: [PCP] AOP11 Not Applicable Initial Operational Capability: 01/01/2015 [Essential] Full Operational Capability: 31/12/2021 AO‐0801‐A(OI) [E] EVRA ‐ Riga Airport ‐ ‐ [Objective coordinated with FAB partners: ‐] ASP (By:12/2021) Not Applicable LGS ‐ ‐ ‐ APO (By:12/2021) Not Applicable RIGA Airport ‐ ‐ ‐

Improve runway and airfield safety with ATC clearances monitoring [PCP] AOP12 Not Applicable Timescales: [Essential] ‐ not applicable ‐ AERODROME‐ATC‐36(EN), AO‐0104‐A(OI) [E] EVRA ‐ Riga Airport (Outside Applicability Area) ‐ ‐ [Objective coordinated with FAB partners: ‐] ASP (By:12/2020) Not Applicable LGS ‐ ‐ ‐ APO (By:12/2020)

LSSIP Year 2015 Latvia 30 Released Issue

Implement ground based safety nets ‐ Area Proximity Warning ‐ level 2

ATC02.5 Timescales: Completed

Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016 CM‐0801(OI) ‐ Area Proximity Warning function is used operationally from 2001. Corresponding procedures and 31/12/2013 instructions for operational and engineering staff are established. [Objective coordinated with FAB partners: ‐] ASP (By:12/2016) Area Proximity Warning function is used operationally from 2001. Completed LGS Corresponding procedures and instructions for operational and ‐ engineering staff are established. 31/12/2013

Implement ground based safety nets ‐ Minimum Safe Altitude Warning ‐ level 2

ATC02.6 Timescales: Completed

Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016 CM‐0801(OI) ‐ Minimum Safe Altitude Warning function is implemented in the automated ATC system and it is operational from 2001. Corresponding procedures and instructions for operational and engineering staff 31/12/2013 are established. [Objective coordinated with FAB partners: ‐] ASP (By:12/2016) Minimum Safe Altitude Warning function is used from 2001. Completed LGS Corresponding procedures and instructions for operational and ‐ engineering staff are established. 31/12/2013

Implement ground based safety nets ‐ Approach Path Monitor ‐ level 2

ATC02.7 Timescales: No Plan

Initial operational capability: 01/01/2009 Full operational capability: 31/12/2016 CM‐0801(OI) ‐ LGS will plan the APM implementation if the local needs will be identified and upon readiness of the 31/12/2016 Eurocontrol Specification. [Objective coordinated with FAB partners: ‐] ASP (By:12/2016) No Plan LGS LGS will plan the APM implementation if the local needs will be identified. ‐ 31/12/2016

LSSIP Year 2015 Latvia 31 Released Issue

Implement AMAN tools and procedures Timescales: ATC07.1 Late Initial operational capability: 01/01/2007 Full operational capability: 31/12/2015 TS‐0102(OI) EVRA ‐ Riga Airport Implementation of AMAN tools is planned for first half of 2016. The automated ATC system is already 01/06/2016 prepared to support AMAN. [Objective coordinated with FAB partners: ‐] ASP (By:12/2015) LGS plans implementation of basic arrival management tools. The Late LGS ‐ automated ATC system is already prepared to support AMAN. 01/06/2016

Implement automated support for conflict detection, resolution support information and conformance monitoring

ATC12.1 Timescales: Completed

Initial operational capability: 01/01/2015 Full operational capability: 31/12/2021 CM‐0202(OI), CM‐0203(OI), CM‐0205(OI), CM‐0207‐A(OI) ‐ ‐Automated support for conflict detection, resolution and support information and conformance 31/12/2008 monitoring objective has been implemented [Objective coordinated with FAB partners: ‐] ASP (By:12/2021) MTCD and Conformance Monitoring functions are implemented. The Completed LGS ‐ ATCOs are trained accordingly. 31/12/2008

Implement, in En‐Route operations, information exchange mechanisms, tools and procedures in support of Basic AMAN operations ATC15 Planned Timescales: Initial operational capability: 01/01/2012 Full operational capability: 31/12/2017 TS‐0305(OI) ‐ Implementation of AMAN support functionality for en‐route operations is planned. 31/12/2017 [Objective coordinated with FAB partners: ‐] ASP (By:12/2017) Implementation of AMAN support functionality for en‐route operations is Planned LGS ‐ planned. 31/12/2017

LSSIP Year 2015 Latvia 32 Released Issue

Implement ACAS II compliant with TCAS II change 7.1 Timescales: ATC16 Completed Initial operational capability: 01/03/2012 Full operational capability: 31/12/2015 PRO‐AC‐21(EN) ‐ Respective nationaly registered aircraft have been equipped with enhanced ACAS II version 7.1 and ANSP staff has been approapriately trained in order to further reduce the risk of mid‐air collisions in European 31/01/2015 airspace. [Objective coordinated with FAB partners: ‐] REG (By:12/2015) Airworthiness certification and operational approval for ACAS II version Completed CAA 7.1 equipped aircraft has been issued for Latvian registered aircraft. ‐ Appropriate oversight of the ANSP staff training has been performed. 31/01/2015 ASP (By:03/2012) All the personnel concerned have been trained accordingly. ACAS Completed LGS performance monitoring system is established as a part of ATS safety ‐ monitoring. 31/12/2012 MIL (By:12/2015) National armed forces do not operate fixed wing transport type aircraft. Not Applicable Mil. Authority Appropriate training to the helicopter flight crew operating in the ‐ airspace with other aircraft equipped with ACAS II, has been provided. 31/12/2015

Electronic Dialogue as Automated Assistance to Controller during Coordination and Transfer

ATC17 Timescales: Planned

Initial operational capability: 01/01/2013 Full operational capability: 31/12/2018 CM‐0201(OI) ‐ Upgrade of coordination and transfer through automated assistance of electronic dialogue is planned by 31/12/2018 the end of 2018. [Objective coordinated with FAB partners: ‐] ASP (By:12/2018) LGS and supplier have discussed a draft specification with regard to Planned electronic dialog. This specification is a subject of the automated ATC LGS ‐ system modernisation project "ATRACC 2014+". Implementation 31/12/2018 timeframe will be defined together with the neghbouring ANSPs.

Migrate from AFTN to AMHS Timescales: COM10 Late Initial operational capability: 01/12/2011 Full operational capability: 31/12/2014 CTE‐C06c(EN) ‐ The migration is planned by 31/12/2016. A contract with manufacturer on system upgrade is signed. 31/12/2016 [Objective coordinated with FAB partners: ‐] ASP (By:12/2014) Communicati Late LGS has two operational AMHS connections with Bratislava and Frankfurt. on Project / LGS LGS has signed a contract with manufacturer on system upgrade up to PBN Enhanced AMHS capability. Implementati 31/12/2016 on Project

LSSIP Year 2015 Latvia 33 Released Issue Implementation of Voice over Internet Protocol (VoIP) in ATM Timescales: COM11 Planned Initial operational capability: 01/01/2013 Full operational capability: 31/12/2020 CTE‐C05a(EN) ‐ Latvia plans to implement VoIP by the end of 2017 31/12/2020 [Objective coordinated with FAB partners: ‐] ASP (By:12/2020) Planned LGS LGS plans to implement Voice over IP in ATM. ‐ 31/12/2020

Implement Continuous Descent Operations (CDO) techniques for environmental improvements ENV01 Not Applicable Timescales: ‐ not applicable ‐ AOM‐0701(OI) EVRA ‐ Riga Airport (Outside Applicability Area) The implementation of this objective will be addressed after PBN implementation in Riga TMA. ‐ [Objective coordinated with FAB partners: ‐] ASP (By:12/2013) PBN Not Applicable The implementation of this objective will be addressed after PBN LGS Implementati implementation in Riga FIR. on Project ‐ APO (By:12/2013) Riga International Airport has implemented noise monitoring system Not Applicable RIGA Airport around aerodrome area. Noise footprint map is developed yearly ‐ including average day and night noise level. ‐

Implement Collaborative Environmental Management (CEM) at Airports ENV02 Not Applicable Timescales: ‐ not applicable ‐ AO‐0703(OI), AO‐0705(OI), AO‐0706(OI) EVRA ‐ Riga Airport (Outside Applicability Area) Riga International Airport is not in the related list of airports. ‐ [Objective coordinated with FAB partners: ‐] ASP (By:12/2016) Not Applicable LGS Riga International Airport is not in the list of airports. ‐ ‐ APO (By:12/2016) Not Applicable RIGA Airport Riga International Airport is not in the related list of airports. ‐ ‐

LSSIP Year 2015 Latvia 34 Released Issue

Implement enhanced tactical flow management services Timescales: FCM01 Late Initial operational capability: 01/08/2001 Full operational capability: 31/12/2006 IS‐0102(OI) ‐ Implementation of the objective is expected during first half of 2016 30/04/2016 [Objective coordinated with FAB partners: ‐] ASP (By:07/2014) Late LGS Implementation of CPR messages is expected by 30/04/2016. ‐ 30/04/2016

Implement collaborative flight planning Timescales: Partly FCM03 Initial operational capability: 01/01/2000 Completed Full operational capability: 31/12/2017 IS‐0102(OI) ‐ Flight plan messages, at Riga ATCC, are processed in ICAO 2012 Format. Automatic sending of AFP 31/12/2017 messages is planned for 12/2017. [Objective coordinated with FAB partners: ‐] ASP (By:12/2017) Partly LGS needs accurate definitions and clear rules from the NM to implement LGS ‐ Completed the ASP09. 31/12/2017

Implementation of Short Term ATFCM Measures ‐ phase 1 (Outside Applicability Area) FCM04 Not Applicable Timescales: ‐ not applicable ‐ DCB‐0205(OI) ‐ Latvia is outside of applicability area. ‐ [Objective coordinated with FAB partners: ‐] ASP (By:12/2015) Not Applicable LGS Latvia is outside of applicability area. ‐ ‐

LSSIP Year 2015 Latvia 35 Released Issue

Implementation of interactive rolling NOP Timescales: [PCP] FCM05 Planned Initial operational capability: 01/09/2013 [Essential] Full operational capability: 31/12/2021 AOM‐0202(OI), AOM‐0205(OI), DCB‐0102(OI), DCB‐0103‐A(OI) [E], IS‐0901‐A(OI) [E] ‐ Latvia plans to implement interactive rolling NOP by December 2016 31/12/2016 [Objective coordinated with FAB partners: ‐] ASP (By:12/2017) Planned LGS Implementation of ASM support system LARA is in progress. ‐ 31/12/2016 Planned Mil. Authority ‐ ‐ 31/12/2016 APO (By:12/2021) Not Applicable RIGA Airport Riga airport has no plans to transition to coordinated slots. ‐ 31/12/2016

Traffic Complexity Assessment Timescales: [PCP] FCM06 Planned Initial operational capability: 01/01/2015 [Essential] Full operational capability: 31/12/2021 CM‐0101(OI), CM‐0103‐A(OI) [E], IS‐0102(OI) ‐ Implementation of the traffic load management tool is planned. 31/12/2021 [Objective coordinated with FAB partners: ‐] ASP (By:12/2021) Planned LGS Planned ‐ 31/12/2021

Implement integrated briefing Timescales: INF04 Completed Initial operational capability: 01/07/2002 Full operational capability: 31/12/2012 IS‐0201(OI) ‐ Integrated briefing is provided by Briefing Facility of Frequenties Company according with the Eurocontrol 31/12/2012 Specification. [Objective coordinated with FAB partners: ‐] ASP (By:12/2012) Integrated briefing is provided by Briefing Facility of Frequenties Completed LGS ‐ Company according with the Eurocontrol Specification. 31/12/2012

LSSIP Year 2015 Latvia 36 Released Issue

Electronic Terrain and Obstacle Data (TOD) Timescales: INF07 Planned Initial operational capability: 01/11/2014 Full operational capability: 31/05/2018 AIMS‐16(EN) ‐ The existing policy documents will be reviewed and updated as necessary by 2018. It is planned to implement airport TOD management in accordance with the national policy. From an ANSP perspective, 31/05/2018 terrain and obstacle data are partly implemented. [Objective coordinated with FAB partners: ‐] REG (By:05/2018) The existing policy documents will be reviewed and updated as necessary Planned CAA ‐ by 2018. 31/05/2018 ASP (By:05/2018) The National TOD Policy is not published. The required activities for the Late collection, management and provision of TOD will be planned right after implementation of INF07‐REG01 and INF07‐REG02. However for terrain LGS data the objective is implemented for Area 1 as well as at RIX for Area 2 ‐ and Area 4. For obstacle data it is implemented for Area 1 as well as at 31/05/2018 RIX for Area 2 and Area 4. Implementation of TOD for Area 3 is expected within 2016. APO (By:05/2018) It is planned to implement airport TOD management in accordance with Planned RIGA Airport ‐ national policy by 2018 31/05/2018

Aircraft identification Timescales: Entry into force of the Regulation: 13/12/2011 ITY‐ACID Planned System capability: 02/01/2020 Possible deferred compliance, only for services provided by military units or under military supervision, subject to conditions:: 02/01/2025 GSURV‐0101(EN) ‐ Latvia plans to implement the regulatory requirement to have the capability of downlinking the aircraft 02/01/2020 identification in order to improve the continuous and unambiguous IFR GAT aircraft identification. [Objective coordinated with FAB partners: ‐] ASP (By:01/2020) The appropriate surveillance systems have been upgraded. LGS has Planned deployed and put into operations Mode S radars as well as WAM. The systems are capable to identify individual aircraft by means of the downlinked unique aircraft identification number. However flight data LGS processing system and surveillance data processing system still use ‐ discrete SSR codes in compliance with the requirements laid down in the 02/01/2020 Annex III of the Regulation 1206/2011. Implementation of the appropriate capabilities for the whole cooperative surveillance chain as identified by the Regulation is planned.

LSSIP Year 2015 Latvia 37 Released Issue Ensure quality of aeronautical data and aeronautical information Timescales: Entry into force of the regulation: 16/02/2010

ITY‐ADQ Article 5(4)(a), Article 5(4)(b) and Article 6 to 13 to be Planned implemented by: 30/06/2013 Article 4, Article5(1) and Article 5(2), Article 5(3) and Article 5(4)(c) to be implemented by: 30/06/2014 All data requirements implemented by: 30/06/2017 IS‐0202(OI), IS‐0204(OI) ‐ Latvia plans to ensure quality of aeronautical data and aeronautical information in accordance with 30/06/2017 Regulation (EU) No 73/2010 of 26 January 2010 [Objective coordinated with FAB partners: ‐] REG (By:06/2017) Safety assessments are to be supervised, and compliance with data Planned CAA ‐ quality requirements monitored. 30/06/2017 ASP (By:06/2017) LGS plans to implement all the requirements ensuring quality of ATRACC ‐ Planned LGS aeronautical data and aeronautical information. 2014+ 30/06/2017 APO (By:06/2017) It is planned to implement all the requirements ensuring quality of Planned RIGA Airport ‐ aeronautical data and aeronautical information in time. 30/06/2017

Initial ATC air‐ground data link services above FL‐285 Timescales: ITY‐AGDL Planned ATS unit operational capability: 05/02/2018 Aircraft capability: 05/02/2020 AUO‐0301(OI), CTE‐C02b(EN) ‐ Currently there is no ATN/VDL2 coverage over Riga FIR. 04/02/2018 [Objective coordinated with FAB partners: FI,LV] REG (By:02/2018) Planned CAA Currently there is no ATN/VDL2 coverage over Riga FIR. ‐ 04/02/2018 ASP (By:02/2018) ATRACC ‐ Planned 2014+ / LGS plans implementation of initial ATC air‐ground data link services CPDLC LGS above FL‐195. Data link implementation is a subject of BOREALIS and Implementati NEFAB cooperation. 04/02/2018 on in the RIGA FIR MIL (By:01/2019) Military is not providing any ATM/ANS services. Military operates SAR Not Applicable Mil. Authority ‐ helicopters only, not able to operate above FL285. 04/02/2015

LSSIP Year 2015 Latvia 38 Released Issue Implement 8,33 kHz air‐ground voice channel spacing below FL195 Timescales: Entry into force: 07/12/2012 New and upgraded radio equipment: 17/11/2013

ITY‐AGVCS2 New or upgraded radios on State aircraft: 01/01/2014 Planned Interim target for freq. conversions: 31/12/2014 All radio equipment: 31/12/2017 All frequencies converted: 31/12/2018 State aircraft equipped, except those notified to EC: 31/12/2018 State aircraft equipped, except those exempted [Art 9(11)]: 31/12/2020 CTE‐C01a(EN) ‐ Planned in accordance with EC regulation 1079/2012 31/12/2018 [Objective coordinated with FAB partners: ‐] REG (By:12/2018) Planned CAA Planned in accordance with EC regulation 1079/2012 ‐ 31/12/2018 Planned Mil. Authority ‐ ‐ 31/12/2018 ASP (By:12/2018) Partly LGS LGS plans to convert frequencies to 8,33 kHz by the implementation date. ‐ Completed 31/12/2018 Partly LGS is going to implement 8,33 kHz channel spacing below FL195. Voice Mil. Authority ‐ Completed communication system is upgraded. Appropriate personnel are trained. 31/12/2018 MIL (By:12/2020) Existing plans includes acquisition of new aircraft fully and appropriately Planned Mil. Authority ‐ equipped to comply with EC reg. 1079/2012. 31/12/2018 APO (By:12/2018) Planned Mil. Authority ‐ ‐ 31/12/2017 Airport plans to implement the 8,33 kHz channel spacing by the end of Planned RIGA Airport ‐ 2017. 31/12/2017

LSSIP Year 2015 Latvia 39 Released Issue

Implementation of ground‐ground automated co‐ordination processes Timescales: Entry into force of Regulation: 27/07/2006 For putting into service of EATMN systems in respect of Partly ITY‐COTR notification and initial coordination processes: 27/07/2006 For putting into service of EATMN systems in respect of Revision Completed of Coordination, Abrogation of Coordination, Basic Flight Data and Change to Basic Flight Data: 01/01/2009 To all EATMN systems in operation by 12/2012: 31/12/2012 Systems serving ACCs providing services above FL285 in the airspace defined in Regulation (EU) 2015/310: 05/02/2018 CM‐0201(OI) ‐ Flight data processing and exchange systems are implemented. Advanced functions are subject of further 04/02/2018 development. [Objective coordinated with FAB partners: ‐] ASP (By:02/2018) Flight data processing and exchange systems are implemented. ATC Partly system is fully compliant with the finalisation criteria. ATC personnel are Completed ATRACC ‐ LGS trained properly with regard to operational use of implemented 2014+ functions. The Logon Forward and the Next Authority Notified processes 05/02/2018 are planned for implementation by 2018. MIL (By:12/2012) Military does not provide ANS/ATM services and there is no electronic Not Applicable Mil. Authority ‐ flight data provision to civil ATC. 28/02/2015

Apply a common flight message transfer protocol (FMTP) Timescales: Entry into force of regulation: 28/06/2007

ITY‐FMTP All EATMN systems put into service after 01/01/09: 01/01/2009 Completed All EATMN systems in operation by 20/04/11: 20/04/2011 Transitional arrangements: 31/12/2012 Transitional arrangements when bilaterally agreed between ANSPs: 31/12/2014 CTE‐C06(EN) ‐ Modernization of the FMTP has been completed as planned. 31/12/2014 [Objective coordinated with FAB partners: ‐] ASP (By:12/2014) Communication systems are ready. To support information exchange via Completed FMTP between FDPS(s) for the purpose of notification, coordination and transfer of the flights between ATC units LGS has signed a Contract with Eurocontrol and SITA for PENS services (ANSP applications: FMTP and ATRACC ‐ LGS AMHS) supporting IPv4/IPv6 dual stack. Corresponding IP addresses were 2014+ received from Eurocontrol. NSA is notified properly. 31/12/2014 Currently IPV6 connection is operational with ACC Malmo where PENS is used for OLDI. Mid February 2016 is a target date for Stokholm ACC as well. MIL (By:12/2014) Not Applicable Mil. Authority Military does not provide services to general air traffic ‐ ‐

LSSIP Year 2015 Latvia 40 Released Issue Surveillance performance and interoperability Timescales: Entry intro force of regulation: 13/12/2011 ATS unit operational capability: 12/12/2013 ITY‐SPI Planned New aircraft capability: 08/06/2016 ELS in transport‐type State aircraft : 07/12/2017 EHS and ADS‐B Out in transport‐type State aircraft : 07/06/2020 Ensure training of MIL personnel: 07/06/2020 Retrofit aircraft capability: 07/06/2020 GSURV‐0101(EN) ‐ Objectives for surveillance performance and interoperability have been implemented on the civil side. 31/12/2019 Military plans to complete the appropriate tasks by the end of 2019. [Objective coordinated with FAB partners: ‐] REG (By:02/2015) Formal acceptance of the ANSP safety assessments has been performed Completed CAA ‐ and communicated to the ANSP. 31/12/2012 ASP (By:02/2015) All surveillance data transferred from LGS ground‐based surveillance Completed systems to other air navigation service providers are in ASTERIX data format. It allows identification of the data source and the type of data. LGS The data are time‐stamped as coordinated universal time (UTC). Safety ‐ assessment for all existing systems is developed and delivered to the 05/02/2015 Latvian CAA. The personnel affected by the changes have been trained properly. MIL (By:06/2020) Planned Mil. Authority It's planned to equip the military helicopters in due time. ‐ 31/12/2017

Implementation of P‐RNAV Timescales: Partly NAV03 Initial operational capability: 01/01/2001 Completed Full operational capability: 31/12/2023 AOM‐0601(OI), AOM‐0602(OI), CTE‐N08(EN) ‐ Implementation of P‐RNAV procedures based on PBN Concept is planned for 2016 Navaids sites were assessed against the P‐RNAV requirements and needs for additional DMEs were identified. All co‐ordinate 31/12/2023 data are published in AIP with reference to the WGS‐84 standard and meet the quality requirements of ICAO Annex 15. [Objective coordinated with FAB partners: ‐] ASP (By:12/2023) LGS plans implementation of RNAV procedures based on National PBN Partly Concept and corresponding National PBN Implementation Plan. Both PBN Completed LGS national documents are not ready yet. Initial implementation is expected Implementati in 2016. All co‐ordinate data are published in AIP with reference to the on Project 31/12/2018 WGS‐84 standard and meet the quality requirements of ICAO Annex 15.

LSSIP Year 2015 Latvia 41 Released Issue

Implement APV procedures Timescales: NAV10 Planned Initial operational capability: 01/06/2011 Full operational capability: 31/12/2016 AOM‐0602(OI), AOM‐0604(OI), CTE‐N06a(EN), CTE‐N06b(EN) ‐ Latvia plans to move from NPA to APV procedures by the end 2016 31/12/2016 [Objective coordinated with FAB partners: ‐] REG (By:04/2016) Appropriate EASA material has been applied to local national oversight Completed CAA ‐ activities. 30/04/2011 ASP (By:12/2016) PBN Late LGS plans implementation of APV procedures. Initial implementation is LGS Implementati expected in 2016. on Project 31/12/2016

Implement measures to reduce the risk to aircraft operations caused by airspace infringements

SAF10 Timescales: Completed

Initial operational capability: 01/06/2008 Full operational capability: 31/12/2011 CM‐0801(OI) ‐ The objective has been implemented. 31/12/2015 [Objective coordinated with FAB partners: ‐] REG (By:12/2011) Competent Authority safety oversight tasks have been performed with Completed CAA regard to ANSP safety changes for reduction of airspace infringement ‐ numbers . 31/12/2015 ASP (By:12/2011) Completed LGS All corresponding components of the Action Plan are implemented. ‐ 31/12/2015 MIL (By:12/2011) Completed Mil. Authority Military will implement the objective together with LCAA and LGS. ‐ 31/12/2015

LSSIP Year 2015 Latvia 42 Released Issue

Improve runway safety by preventing runway excursions Timescales: SAF11 Completed Initial operational capability: 01/09/2013 Full operational capability: 31/01/2018 PRO‐006a(EN) ‐ The appropriate parts of the European Action Plan for the Prevention of Runway Excursions have been 31/12/2013 implemented by the involved parties. [Objective coordinated with FAB partners: ‐] REG (By:01/2018) The appropriate parts of the European Action Plan for the Prevention of Completed Runway Excursions are implemented. Safety oversight program with CAA audits and inspections covers runway safety. Participation of the CAA ‐ representatives at the Runway Safety Team discussions is ensured for 31/12/2013 consultation purposes. ASP (By:12/2014) The appropriate parts of the European Action Plan for the Prevention of Completed LGS Runway Excursions are implemented. Local airlines are involved in the ‐ Runway Safety Team activities. 31/12/2013 APO (By:12/2014) Airport operators regularly and upon necessity enact the necessary safety Completed RIGA Airport ‐ initiatives through Runway safety team actions. 31/12/2013

LSSIP Year 2015 Latvia 43 Released Issue 6.3 Alignment of PCP with ESSIP Objectives and related progress

LSSIP Year 2015 Latvia 44 Released Issue

Annexes

Annex A – Specialists involved in the LSSIP Process

LSSIP Co-ordination LSSIP Focal Points Organisation Name LSSIP Focal Point for Latvia CAA of Latvia Ērika Neimane LSSIP Focal Point for NSA/CAA 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 LSSIP Focal Point for Military National Armed Forces, Joint Maj Indulis Cepurītis HQ

EUROCONTROL LSSIP Support Function Directorate Name LSSIP Contact Person for Latvia DPS/PEPR Luca Dell’Orto

ESSIP Objective Implementation ESSIP EUROCONTROL Objective Owners EUROCONTROL PEPR National Stakeholder Specialist(s) Objective Objective Coordinator AOM13.1 R. BUCUROIU, O. MROWICKI, C. A. DYBOWSKA Jurijs BAZULEVS – LGS LUCCIOLI, E. REUBER AOM19 G. ACAMPORA, O. MROWICKI A. DYBOWSKA Mihails HAVKUNOVS – LGS AOM21.1 R. BUCUROIU A. DYBOWSKA Vadims VORONOVS – LGS AOM21.2 R. BUCUROIU A. DYBOWSKA Vadims VORONOVS – LGS 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. ADAMSON P. VRANJKOVIC not applicable AOP10 M. BIRENHEIDE B. HILL not applicable AOP11 M. BIRENHEIDE B. HILL not applicable AOP12 M. BIRENHEIDE P. VRANJKOVIC not applicable 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 P. CONROY, P. TERZIOSKI L. DELL’ORTO Vladislavs CASCINS – LGS ATC12.1 P. TERZIOSKI L. DELL’ORTO Igors NEMAHOVS – LGS ATC15 P. CONROY, P. TERZIOSKI L. DELL’ORTO Vladislavs CASCINS – LGS ATC16 S. DROZDOWSKI L. DELL’ORTO Jurijs BAZULEVS – LGS ATC17 S. MORTON L. DELL’ORTO Igors NEMAHOVS – LGS COM10 Y. EYUBOGLU A. KOKONA Ainars SNEPSTS – LGS

LSSIP Year 2015 Latvia 45 Released Issue ESSIP EUROCONTROL Objective Owners EUROCONTROL PEPR National Stakeholder Specialist(s) Objective Objective Coordinator COM11 L. POPESCU A. KOKONA Ainars SNEPSTS – LGS ENV01 C. FABER B. HILL not applicable ENV02 S. MAHONY, A. WATT B. HILL not applicable FCM01 H. KOOLEN O. CIOARA Sergejs OVSJANIKOVS – LGS FCM03 TBD O. CIOARA Sergejs OVSJANIKOVS – LGS FCM04 P. HOP O. CIOARA not applicable FCM05 I. MENDES O. CIOARA Mihails HAVKUNOVS – LGS FCM06 P. HOP O. ALFARO Sergejs OVSJANIKOVS – LGS INF04 P. MATERN A-P. FRANGOLHO Vadims TUMARKINS – LGS INF07 A. PETROVSKY A-P. FRANGOLHO Vadims TUMARKINS – LGS ITY-ACID O. CIOARA Aleksejs JAVORSKIS – LGS A. DESMOND-KENNEDY Igors NEMAHOVS – LGS ITY-ADQ M. UNTERREINER A-P. FRANGOLHO Vadims TUMARKINS – LGS ITY-AGDL A. KOKONA Vadims STROITELEVS – LGS S. DISSING Ainars SNEPSTS – LGS ITY-AGVCS2 O. ALFARO Ainars SNEPSTS – LGS J POUZET Igors NEMAHOVS – LGS Jurijs BAZULEVS – LGS ITY-COTR S. MORTON L. DELL’ORTO Igors NEMAHOVS – LGS ITY-FMTP L. POPESCU O. ALFARO Igors NEMAHOVS – LGS ITY-SPI O. CIOARA Alvis VILKS – LGS M. BORELY, R. STEWART Aleksejs JAVORSKIS – LGS NAV03 F. PAVLICEVIC A. KOKONA Janis LAPINS – LGS NAV10 R. FARNWORTH A. KOKONA Janis LAPINS – LGS SAF10 T. LICU I. FEIJT Alvis VILKS – LGS SAF11 S. LAWRENCE I. FEIJT Vadims ULJANOVSKIS – LGS

LSSIP Year 2015 Latvia 46 Released Issue Annex B – National Stakeholders Organisation Charts

LSSIP Year 2015 Latvia 47 Released Issue

SJSC “LATVIJAS GAISA SATIKSME” STRUCTURE

LSSIP Year 2015 Latvia 48 Released Issue LSSIP Year 2015 Latvia 49 Released Issue Annex C – Glossary of Abbreviations

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

AF ATM Functionality ATRACC Air Traffic Control System for Riga Area Control Centre FT Fast Track LCAA Civil Aviation Agency of Latvia LFV Luftfartsverket LGS Latvijas Gaisa Satiksme NEFAB North European Functional Airspace Block NEFRA North European Free Route Airspace PCP Pilot Common Project PDP Preliminary Deployment Programme S-AF Sub ATM Functionality TAIIB Transport Accident and Incident Investigation Bureau

LSSIP Year 2015 Latvia 50 Released Issue