EUROCONTROL

European Route Network Improvement Plan

PART 2 European ATS Route Network - Version 2020-2024

Edition July 2020

Approved by the Network Mangement Board 8 July 2020

FOUNDING MEMBER NETWORK SUPPORTING EUROPEAN AVIATION MANAGER EUROCONTROL Network Management Directorate

DOCUMENT CONTROL

Document Title ERNIP Part 2

Document Subtitle European ATS Route Network - Version 2020 - 2024

Document Reference ERNIPPART2

Edition Number 1.0

Edition Validity Date 08-07-2020

Classification White

Status Final

Author(s) NMD/ACD

Contact Person(s) Razvan Bucuroiu

APPROVAL TABLE

Authority Date Signature

Prepared by: 14 Apr 2020 NMD/ACD

Reviewed and endorsed by: 28 April 2020 RNDSG/100

Reviewed and endorsed by: 15 May 2020 NETOPS/27

Reviewed and endorsed by: 02 June 2020 NDOP/26

Approved by: 08 July 2020 NMB/28

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: i

EUROCONTROL Network Management Directorate

EDITION HISTORY

Edition No. Validity Date Author(s) Reason 0.1 28 Apr 2020 NMD/ACD Proposed Issue RNDSG/100 Proposed Issue NETOPS/27 and 0.2 04 May 2020 NMD/ACD NDOP/26 0.3 02 June 2020 NMD/ACD Proposed Issue to NMB/28 1.0 08 July 2020 NMD/ACD Approved by NMB/28

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: ii

EUROCONTROL Network Management Directorate

TABLE OF CONTENT

DOCUMENT CONTROL ...... I APPROVAL TABLE ...... I EDITION HISTORY ...... II EXECUTIVE SUMMARY ...... 1 ORGANISATION AND CONTENTS ...... 3 1 A CONSOLIDATED EUROPEAN AIRSPACE DEVELOPMENT ...... 4 1.1 Objective, Scope and Timeframe ...... 4 1.2 Demanding Performance Targets ...... 6 Performance - Third Reference Period (RP3) - 2020 - 2024 ...... 6 1.3 European Route Network Improvement Plan - Principles ...... 8 1.4 The Flight Efficiency Plan ...... 9 1.5 Preparation of the ERNIP Part 2 - ARN Version 2020 - 2024 ...... 9 1.6 Functional Airspace Blocks Integration into the ERNIP Part 2 - ARN Version 2020 - 2024 for the RP3 Period ...... 10 1.7 Local Performance Plans and their Relationship to the ERNIP Part 2 - ARN Version 2020 - 2024 for the RP3 ...... 12 Local Performance Plans and their Relation to the European Route Network Improvement Plan for RP3 ...... 13 2 ARN VERSION 2020 - 2024 BENEFITS ...... 15 2.1 Total Expected Benefits - ERNIP PART 2 - ARN Version 2020 - 2024 ...... 15 2.2 Capacity Enhancement Benefits of ERNIP Part 2 - ARN version 2020 - 2024 ...... 16 3 EUROPEAN ROUTE NETWORK DESIGN FUNCTION AND FLIGHT EFFICIENCY ACTION PLANS ...... 17 3.1 European Route Network Design Function ...... 17 3.2 Free Route Airspace ...... 17 3.3 Route Availability Document ...... 19 3.4 Improving TMA Structures ...... 20 3.5 The Flight Efficiency Plan ...... 21 3.6 The Network Manager Flight Efficiency Initiative ...... 21 4 CONCEPT OF OPERATIONS FOR EUROPEAN AIRSPACE DESIGN ...... 24 4.1 Main Principles ...... 24 4.2 ERNIP Part 2 - ARN Version 2020 - 2024 Concept Highlights ...... 25 Introduction ...... 25 Basic Concept ...... 25 European Network Consistency ...... 25 Airspace Continuum ...... 26 ARN Version 2020 - 2024 Components ...... 26 Airspace Classification ...... 27

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: iii

EUROCONTROL Network Management Directorate

Airspace Organisation ...... 27 Airspace Development Approach ...... 27 Operating the ERNIP Part 2 - ARN Version 2020 - 2024 ...... 29 Military Operations ...... 30 Airspace Management (ASM) Solutions...... 31 Impact on Adjacent Areas ...... 34 5 A NETWORK COOPERATIVE DECISION-MAKING PROCESS ...... 34 5.1 A Network Oriented Approach ...... 36 5.2 Airspace Utilisation and Management ...... 37 5.3 Military Requirements ...... 38 6 TRAFFIC DEMAND EVOLUTION AND ASSESSMENT ...... 39 6.1 General...... 39 6.2 Traffic Demand Variation - Comparison 2008/2019 ...... 39 6.3 Week and Week-end disruption ...... 40 6.4 Distribution and Evolution - Short Haul and Medium/Long Haul ...... 42 6.5 Vertical Distribution (Evolving and Cruising Traffic) ...... 43 6.6 Flight Level Distribution ...... 44 6.7 Airport Traffic Increase ...... 44 6.8 Top 50 Airports ...... 45 6.9 Busiest City Pairs ...... 46 6.10 Airspace Users ...... 48 6.11 Aircraft Types ...... 49 7 MAIN PROJECTS INCLUDED IN ERNIP PART 2 - ARN VERSION 2020 - 2024 ...... 50 7.1 Free Route Airspace ...... 51 ANNEXES ...... 54 A. REFERENCE DOCUMENTS ...... 54 B. ACRONYMS AND ABBREVIATIONS ...... 55 C. SUMMARY OF ERNIP PART 2 - ARN VERSION 2020 - 2024 PROPOSALS ...... 57 D. LIST OF ERNIP PART 2 - ARN VERSION 2020 - 2024 PROPOSALS ...... 64

TABLE OF FIGURES

Figure 1 : Route Efficiency KPI per AIRAC cycle ...... 15 Figure 2 : FRA until end 2020 ...... 18 Figure 3 : FRA until end 2024 ...... 18 Figure 4 : ERNIP Part 2 Principles ...... 24 Figure 5 : Network CDM ...... 36 Figure 6 : Network Oriented Approach ...... 37 Figure 7 : Traffic demand variation 2019 vs 2008 ...... 39

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: iv

EUROCONTROL Network Management Directorate

Figure 8 : Week days traffic density (4 days in June 2019) ...... 40 Figure 9 : Week-end traffic density (4 week-end days in June 2019) ...... 41 Figure 10 : Traffic Density Comparison Week <> Weekend ...... 41 Figure 11 : Short-Haul Flights (<400 NM) ...... 42 Figure 12 : Medium Haul Flights (>400 NM) ...... 42 Figure 13 : Areas of High Density Evolving Traffic ...... 43 Figure 14 : Areas of High Density Cruising Traffic ...... 44 Figure 15 : Flight Level Distribution in Europe 2008 / 2019 ...... 44 Figure 16 : Traffic Increase/Decrease for the 200 Busiest European Airports ...... 45 Figure 17 : Free Route Airspace Chart - End 2020 ...... 51 Figure 18 : Free Route Airspace Chart - End 2021 ...... 51 Figure 19 : Free Route Airspace Chart - End 2022 ...... 52 Figure 20 : Free Route Airspace Chart - End 2023 ...... 52 Figure 21 : Free Route Airspace Chart - End 2024 ...... 53

TABLE OF TABLES

Table 1 : ERNIP Part 2 - Preparation ...... 10 Table 2 : KEA reference values for States/ANSPs ...... 14 Table 3 : Top 50 Airports ...... 46 Table 4 : Busiest City Pairs 2007 - 2008 ...... 47 Table 5 : Busiest City Pairs 2018 - 2019 ...... 48 Table 6 : Top 50 Aircraft Operators ...... 49 Table 7 : Top 50 Aircraft Types ...... 50

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: v

EUROCONTROL Network Management Directorate

Executive Summary

This document addresses the requirements set forth in the Commission Implementing Regulation (EU) 2019/123 of 24 January 2019 laying down detailed rules for the implementation of air traffic management (ATM) network functions an repealing Commission Regulation (EU) No 677/2011 and supplemented by the requirements set forth in the Commission Implementing Regulation (EU) 2019/317 of 11 February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing regulation (EU) No 390/2013 and (EU) no 391/2013. The European Route Network Improvement Plan (ERNIP) is a plan developed by the Network Manager in coordination with the operational stakeholders. It includes the result of Network Manager’s operational activities with respect to short and medium-term route network design in accordance with the Network Strategy Plan. The objective of the ERNIP Part 2 - ARN Version 2020 - 2024 is the enhancement of European ATM capacity, flight efficiency and environmental performance through the development and implementation of an improved ATS route network, Free Route Airspace and TMA systems structures supported by corresponding improvements to the airspace structure and the optimal utilisation rules. The ERNIP Part 2 - ARN Version 2020 - 2024 provides a network-consolidated picture of network and local/FAB projects and the evaluation of their expected performance in response to the European network performance targets and local environment reference values. As a result of those evaluations it can be derived that the performance targets of the 3rd Reference Period of the Single European Sky Performance Scheme (RP3) will be met if the proposed NM measures will be implemented and if further improvements take place with respect to flight planning. Nevertheless, some further changes might be included in the next versions of the ERNIP Part 2 to reflect latest updates following COVID situation. The ERNIP Part 2 - ARN Version 2020 - 2024 will ensure the implementation, in cooperation with the ANSPs and the FABs, of the Airspace Vision agreed by the Network Management Board:  a comprehensive cross-border implementation of Free Route Airspace, at least at and above FL310, in the European airspace;  an optimised route structure below FRA ensuring efficient connectivity in/out terminal airspace;  a simplification of the RAD;  a harmonisation of the airspace publications;  more efficient Flexible Use of Airspace procedures and the associated system support to enable a better utilisation of the civil/military airspace structures;  a closer cooperation between the Network Manager, the airspace users and the computer flight plan service providers aimed at ensuring a better utilisation of the available airspace structures. The ERNIP Part 2 - ARN Version 2020 - 2024:  achieves an European Route Network for the safe and efficient operation of air traffic, taking due account of the environmental impact;  keeps operational consistency of the European airspace organisation;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 1

EUROCONTROL Network Management Directorate

 consolidates into a network approach the Functional Airspace Blocks developments, the wide implementation of airspace projects from Free Route Airspace to TMA developments;  facilitates the development of an airspace structure offering the required level of safety, capacity, flexibility, responsiveness, environmental performance and seamless provision of expeditious air navigation services, with due regard to security and defence needs;  ensures regional interconnectivity and interoperability of the European route network within the ICAO EUR Region and with adjacent ICAO Regions.

When calculated over the RP3 period, the full benefits that ENRIP Part 2 - ARN Version 2020 - 2024 would bring in 2024 represent approximately 130 million NMs, i.e. the equivalent of 800 000 tons of fuel saved, or reduced emissions of 2 600 000 tons, or 670 million Euros.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 2

EUROCONTROL Network Management Directorate

Organisation and contents

This document is identified as European Route Network Improvement Plan - ARN Version 2020 - 2024 Catalogue of Airspace Projects. Structure of the Document Chapter 1 Provides an overview of the consolidated European approach to airspace design. Chapter 2 Provides an overview of ARN Version 2020 - 2024 benefits. Chapter 3 Commences with the Airspace Action Plan and depicts its implementation. Chapter 4 Focuses on the consolidated Concept of Operations. Chapter 5 Focuses on the Network Collaborative Decision Making Process. Chapter 6 Provides an assessment of the demand between 2007/2008 and 2018/2019. Chapter 7 Provides a description of the ARN Version 2020 - 2024 layers. Annexes Annex A Reference Documents Annex B Acronyms and Abbreviations Annex C Summary of ARN Version 2020 - 2024 Proposals Annex D List of ARN Version 2020 - 2024 Proposals

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 3

EUROCONTROL Network Management Directorate

1 A Consolidated European Airspace Development

1.1 Objective, Scope and Timeframe

(1) This document addresses the requirements set forth in the Commission Implementing Regulation (EU) 2019/123 of 24 January 2019 laying down detailed rules for the implementation of air traffic management (ATM) network functions an repealing Commission Regulation (EU) No 677/2011 and supplemented by the requirements set forth in the Commission Implementing Regulation (EU) 2019/317 of 11 February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing regulation (EU) No 390/2013 and (EU) no 391/2013. The European Route Network Improvement Plan (ERNIP) is a plan developed by the Network Manager in coordination with the operational stakeholders. It includes the result of Network Manager’s operational activities with respect to short and medium term route network design in accordance with the Network Strategy Plan

(2) The objective of the ERNIP Part 2 - ARN Version 2020 - 2024 is the enhancement of European ATM capacity, flight efficiency and environmental performance through the development and implementation of an improved ATS route network, Free Route Airspace and TMA systems structures supported by corresponding improvements to the airspace structure and the optimal utilisation rules.

(3) The ERNIP Part 2 - ARN Version 2020 - 2024 provides a network consolidated picture of network and local/FAB projects and the evaluation of their expected performance in response to the European network performance targets and local environment reference values. As a result of those evaluations it can be derived that the performance targets of the 3rd Reference Period of the Single European Sky Performance Scheme (RP3) will be met if the proposed NM measures will be implemented and if further improvements take place with respect to flight planning.

(4) Through the ERNIP Part 2, the Network Manager supports the Commission by providing relevant input for the preparation of Union-wide performance targets before the reference periods and for monitoring the achievement of the performance targets during the reference period.

(5) In that respect, a close cooperation and synchronisation was ensured between the Network Manager and all the FABs in the preparation of the Network Operations Plan and the ERNIP Part 2 - ARN Version 2020 - 2024.

(6) The ERNIP Part 2 - ARN Version 2020 - 2024 will contribute to the achievement of the performance targets of the 3rd Reference Periods of the Single European Sky Performance Scheme (RP3).

(7) The ERNIP Part 2 - ARN Version 2020 - 2024 will ensure the implementation, in cooperation with the ANSPs and the FABs, of the Airspace Vision agreed by the Network Management Board:  a comprehensive cross-border implementation of Free Route Airspace, at least at and above FL310, in the European airspace;  an optimised route structure below FRA ensuring efficient connectivity in/out terminal airspace;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 4

EUROCONTROL Network Management Directorate

 a simplification of the RAD;  a harmonisation of the airspace publications;  more efficient Flexible Use of Airspace procedures and the associated system support to enable a better utilisation of the civil/military airspace structures;  a closer cooperation between the Network Manager, the airspace users and the computer flight plan service providers aimed at ensuring a better utilisation of the available airspace structures.

(8) The ERNIP Part 2 - ARN Version 2020 - 2024:  achieves an European Route Network for the safe and efficient operation of air traffic, taking due account of the environmental impact;  keeps operational consistency of the European airspace organisation;  consolidates into a network approach the Functional Airspace Blocks developments, the wide implementation of airspace projects from Free Route Airspace to TMA developments;  facilitates the development of an airspace structure offering the required level of safety, capacity, flexibility, responsiveness, environmental performance and seamless provision of expeditious air navigation services, with due regard to security and defence needs;  ensures regional interconnectivity and interoperability of the European route network within the ICAO EUR Region and with adjacent ICAO Regions.  ensures compliance with the Commission Implementing Regulation No 716/2014 of 27th June 2014 on the establishment of the Pilot Common Project supporting the implementation of the European Air Traffic Management Master Plan.

(9) The ERNIP Part 2 - ARN Version 2020 - 2024 combines airspace design projects developed in a cooperative manner between the Network Manager and its Operational Stakeholders aimed for implementation over the period Autumn 2019 - end of 2024. The implementation started in Autumn 2019 and continues in stages until the end of 2024. Further updates will be brought through subsequent versions of the ERNIP Part 2.

(10) The ERNIP Part 2 - ARN Version 2020 - 2024 includes details on:  Implementation of Free Route Airspace projects;  ATS route network developments;  Re-sectorisation actions;  Actions aimed at simplifying the usage of the ATS route network;  Civil/military airspace structures;  Deployment of the night route network.

(11) The ERNIP Part 2 - ARN Version 2020 - 2024 is derived from the following sources:  Proposals covering a cohesive development of the European Airspace Structure;  Solutions developed inside various FAB initiatives;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 5

EUROCONTROL Network Management Directorate

 Proposals originating at national or sub-regional level;  Aircraft operator’s proposals.

(12) The European Route Network Improvement Plan Part 2 - ARN Version 2020 - 2024 covers a similar geographical area like the Network Operations Plan:  EU member States (, , Bulgaria, , Cyprus, , , Estonia, , , Germany, , Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, ) and the ;  EUROCONTROL member States that are not EU members (Albania, Armenia, Bosnia and Herzegovina, Georgia, Montenegro, North Macedonia, Norway, Republic of Moldova, Serbia, , Turkey, Ukraine);  Non EUROCONTROL member States that have signed a comprehensive with EUROCONTROL (Israel and Morocco).

(13) In addition, the European Route Network Improvement Plan ensures full coherency of the airspace structure at the interface areas, covering many of the States that have an interface with those mentioned above. These include, amongst other States, Azerbaijan, Belarus, , Iceland, Jordan, Kazakhstan, Lebanon, Libya, Russian Federation and Tunisia.

(14) The latest situation of the European route network structure is available and updated at each AIRAC cycle through the publication of EUROCONTROL Regional Charts that could be found at the following link: https://www.eurocontrol.int/service/cartography

1.2 Demanding Performance Targets

Performance - Third Reference Period (RP3) - 2020 - 2024

(1) The COMMISSION IMPLEMENTING REGULATION (EU) 2019/317 of 11th of February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013, details an updated set of Key Performance Indicators (KPIs) that have been set for the 3rd Reference Period (RP3). For the third performance Reference Period starting on 1st January 2020 and ending on 31st December 2024, the European Union-wide performance indicators will be as follows: Environment  average horizontal en-route flight efficiency of the actual trajectory, calculated as follows: o the indicator is the comparison between the length of the en route part of the actual trajectory derived from surveillance data and the achieved distance, summed over IFR flights within or traversing the airspace as defined in Article 1, hereinafter referred to as ‘European airspace’; o ‘en route part’ refers to the distance flown outside a circle of 40 NM around the airports; o where a flight departs from or arrives at an airport outside the European airspace, the entry or exit points of the European airspace are used for

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 6

EUROCONTROL Network Management Directorate

the calculation of this indicator as the origin or destination respectively, rather than the departure or destination airport; o where a flight departs from and arrives at an airport inside the European airspace and crosses a non-European airspace, only the part inside the European airspace is used for the calculation of this indicator; o ‘achieved distance’ is a function of the position of the entry and exit points of the flight into and out of each portion of airspace for all parts of the trajectory. Achieved distance represents the contribution that those points make to the great circle distance between origin and destination of the flight; and, o the indicator is calculated for the whole calendar year and for each year of the reference period, as an average. When calculating this average, the ten highest daily values and the ten lowest daily values are excluded from the calculation. This KPI is applicable at both network and Functional Airspace Block level.

(2) The Regulation also introduces a new environmental indicator for monitoring:  the share of arrivals applying Continuous Descent Operation (CDO), calculated at local level as follows: o this indicator is the ratio between the total number of arrivals performing a CDO from a reference point at a height above ground, defined by the national supervisory authority, and the total number of arrival operations; and, o this indicator is expressed as a percentage, calculated for the whole calendar year and for each year of the reference period. This indicator is applicable at the local level.

(3) It should be noted that this indicator might be used to measure the performance of the part of the descent profile where noise is the principal environmental impact. Whilst the altitude of the reference point to be defined by the national supervisory authority may depend upon local factors such as airspace particularities or the extent of the area of responsibility, the majority of emissions savings can be gained from enabling CDO from top of descent or from higher levels wherever possible. Whilst reference points may be defined according to local requirements, airspace design should still aim to enable CDO from top of descent or from as high a level as possible. Capacity:  The average minutes of en route ATFM delay per flight attributable to air navigation services, calculated as follows: o the en route ATFM delay is the delay calculated by the Network Manager, expressed as the difference between the estimated take-off time and the calculated take-off time allocated by the Network Manager; o for the purposes of this indicator: . ‘estimated take-off time’ means the forecast of time when the aircraft will become airborne calculated by the Network Manager and based on the last estimated off-block time, or target off-block time for those airports covered by airport collaborative decision-

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 7

EUROCONTROL Network Management Directorate

making procedures, plus the estimated taxi-out time calculated by the Network Manager; . ‘calculated take-off time’ means the time allocated by the Network Manager on the day of operation, as a result of tactical slot allocation, at which a flight is expected to become airborne; . ‘estimated taxi-out time’ means the estimated time between off- block and take off. This estimate includes any delay buffer time at the holding point or remote de-icing prior to take off; o this indicator covers all IFR flights and all ATFM delay causes, excluding exceptional events; and, o this indicator is calculated for the whole calendar year and for each year of the reference period. The ERNIP Part 2 - ARN Version 2020 - 2024 also responds to the targets included in the Network Performance Plan (NPP) 2020 - 2024 as described below:  Route extension - last filed flight plan: o Targets: . Achieve 3.78% for NM area for KPI by 2024.  Percentage of Enroute delay savings: o Targets: . Deliver additional operational benefits in terms of en-route delay savings of 10% of total en-route delay.

1.3 European Route Network Improvement Plan - Principles

(1) With the development of the ERNIP Part 2 - ARN Version 2020 - 2024 of the European Route Network Improvement Plan the Network Manager, States, air navigation service providers as part of functional airspace blocks or individually, applied, within the cooperative decision-making process, the following airspace design principles:  the establishment and configuration of airspace structures was based on operational requirements, irrespective of national or functional airspace block borders or FIR boundaries, and was not bound by the division level between upper and lower airspace;  the design of airspace structures was a transparent process showing decisions made and their justification through taking into account the requirements of all users whilst reconciling safety, capacity, environmental aspects and with due regard to military and national security needs;  the present and forecast traffic demand, at network and local level, and the performance targets were used as an input for the ERNIP Part 2 - ARN Version 2020 - 2024 of the European Route Network Improvement Plan with a view to satisfying the needs of the main traffic flows and airports;  vertical and horizontal connectivity, including terminal airspace and the airspace structure at the interface was ensured;  the possibility for flights to operate along, or as near as possible to, user required routes and flight profiles in the en route phase of flight;  the development and inclusion of the vast majority of airspace structures proposals, including Free Route Airspace, multiple route options and CDRs,

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 8

EUROCONTROL Network Management Directorate

received from stakeholders having an operational requirement in the European airspace;  the design of airspace structures including Free Route Airspace and ATC sectors took into account existing or proposed airspace structures designated for activities which require airspace reservation or restriction. To that end only such structures that are in accordance with the application of FUA are included. Such structures were harmonised and made consistent to the largest possible extent across the entire European network;  ATC sector design development was based on the required route or traffic flow alignments within an iterative process that ensured compatibility between routes or flows and sectors;  ATC sectors were designed to enable the construction of sector configurations that satisfy traffic flows and are adaptable and commensurate with variable traffic demand;  agreements on service provision are considered in cases where ATC sectors require, for operational reasons, to be designed across national or functional airspace block borders or FIR boundaries.

(2) With respect to airspace utilisation and capacity management, the following principles apply:  airspace structures shall be planned to facilitate flexible and timely airspace use and management with regard to routing options, traffic flows, sector configuration schemes and the configuration of other airspace structures;  airspace structures should accommodate the establishment of additional route options while ensuring their compatibility (capacity considerations and sector design limitations).

(3) All principles above were fully considered in the development of the ERNIP Part 2 - ARN Version 2020 - 2024 of the European Route Network Improvement Plan.

1.4 The Flight Efficiency Plan IATA, CANSO and EUROCONTROL worked in a close partnership along with airlines, airports and ANSPs to identify solutions and launch operational actions that lead to fuel and emissions savings. The Flight Efficiency Plan was commonly agreed in September 2008. The adoption and the gradual deployment of the Flight Efficiency Plan proved the benefits expected. Since its adoption, in September 2008, in terms of airspace design efficiency (if all flights would have used the route network without any route restrictions and with all CDRs permanently available), the route extension decreased from 3.65% in January 2008 to 2.22% in December 2019. These achievements came as a result of the implementation of previous ARN Versions.

1.5 Preparation of the ERNIP Part 2 - ARN Version 2020 - 2024

(1) The development of the next European Route Network Improvement Plan Part 2 edition will cover a 5-years period (2020 - 2024) to include the entire RP3;  All ANSPs and FABs will be required to provide their airspace plans until 2024;  The Network Manager will provide the list of all known plans until 2024 to all ANSPs and FABs. The Network Manager will provide the environment/flight

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 9

EUROCONTROL Network Management Directorate

efficiency reference values at local level for the period 2020 - 2024, as per the requirement of the Performance Scheme IR;  The following preparation calendar has been followed. This calendar of events require a constant and close cooperation between NM/FABs/ANSPs over the entire period:

Action Date Who Distribution of all known airspace design September 2019 NM plans until 2024 to all States/ANSPs/FABs Comments and updates received from all NM / States/ANSPs/FABs on the initial list of December 2019 Operational airspace projects Stakeholders Preparation of the first version of the NM / European Route Network Improvement February 2020 Operational Plan - Part 2 - ARN Version 2020 - 2024 Stakeholders Comments and updates received from all NM / States/ANSPs/FABs on the list of airspace March 2020 Operational projects Stakeholders Decision on the EU-wide targets April 2020 EC Preparation of the second version of the NM European Route Network Improvement April 2020 /Operational Plan - Part 2 - ARN Version 2020 - 2024 Stakeholders Distribution of final 2020 - 2024 environment/flight efficiency reference May 2020 NM values at local level (based on the final EU- wide target) Initial performance indications at local NM to all level based on the second version of the May - June 2020 Operational European Route Network Improvement Stakeholders Plan - Part 2 - ARN Version 2020 - 2024 European Route Network Improvement NM / Plan - Part 2 - ARN Version 2020 - 2024 May - June 2020 Operational consolidation and approval through the Stakeholders CDM process Publication of European Route Network Improvement Plan - Part 2 - ARN Version July 2020 NM 2020 - 2024

Table 1 : ERNIP Part 2 - Preparation

1.6 Functional Airspace Blocks Integration into the ERNIP Part 2 - ARN Version 2020 - 2024 for the RP3 Period

(1) Since 2007, as part of an overall network development approach, the RNDSG Secretariat worked in close cooperation with all FAB initiatives to provide support to FAB airspace design.

(2) Part of SES II, the establishment of FABs has started several years ahead of the nomination of the Network Manager. The Network Manager started a close

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 10

EUROCONTROL Network Management Directorate

cooperation with all the FABs from the start of the development of their Feasibility Studies. This close cooperation enabled the development of a number of harmonised operational projects that have the potential to contribute to future network performance, when implemented. They respond to the requirements set for the FABs, set forth in the Article 9a of the (EC) Reg. No 550/2004. Namely, those requirements are:  enable optimum use of airspace, taking into account air traffic flows;  ensure consistency with the European route network established in accordance with Article 6 of the airspace Regulation;  ensure compatibility between the different airspace configurations, optimising, inter alia, the current flight information regions;  facilitate consistency with Community-wide performance targets.

(3) The Regulation (EC) No 2019/123, in particular Article 13, sets a framework for an alignment of FAB operation plans with the Network Operations Plan by ensuring the compatibility of the FAB - level measures with those adopted, through the cooperative decision making process, at the Network level.

(4) The NM has established cooperation with most of the FABs to facilitate harmonised developments, operational interconnectivity between the FABs and within the FABs and at European network level.

(5) NM supported a co-ordinated development and, in some cases, deployment of the FAB improvements. This ensured an overall pan-European network consistency, and a uniform application of ASM/ATFCM procedures, a synchronized implementation of new airspace projects or operational concepts and a cohesive view of the performance improvements in relation to the EU-wide targets.

(6) The ERNIP Part 2 - ARN Version 2020 - 2024 includes contributions from a large number of FABs. This consolidated view responds to the Single European Sky requirements for the FABs: to enable optimum use of airspace, taking into account traffic flows and to ensure consistency with the European route network.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 11

EUROCONTROL Network Management Directorate

1.7 Local Performance Plans and their Relationship to the ERNIP Part 2 - ARN Version 2020 - 2024 for the RP3

(1) The NM continues to support a co-ordinated development and, in some cases, deployment of the FAB improvements. This ensures an overall pan-European network consistency, and a uniform application of ASM/ATFCM procedures, a synchronized implementation of new airspace projects or operational concepts and a cohesive view of the performance improvements in relation to the EU-wide targets.

(2) The ERNIP Part 2 - ARN Version 2020 - 2024 includes contributions from a large number of FABs. This consolidated view responds to the Single European Sky requirements for the FABs: to enable optimum use of airspace, taking into account traffic flows and to ensure consistency with the European route network.

(3) The COMMISSION IMPLEMENTING REGULATION (EU) 2019/317 of 11th of February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013 defines, for RP3 and for the Key Performance Environment Area, the actual trajectory as being the Key Performance Indicator at local level.

(4) The COMMISSION IMPLEMENTING REGULATION (EU) 2019/123, in particular Article 13, sets a framework for an alignment of FAB operation plans with the Network Operations Plan by ensuring the compatibility of the FAB - level measures with those adopted, through the cooperative decision making process, at the Network level. In addition, the EC Regulation, for the RP3, in particular Articles 9, 10, 11, 12 and 13 require that local plans are aligned with the Network Operations Plan.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 12

EUROCONTROL Network Management Directorate

(5)

Local Performance Plans and their Relation to the European Route Network Improvement Plan for RP3

(1) The COMMISSION IMPLEMENTING REGULATION (EU) 2019/317 of 11th of February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013 brings another important change compared to RP2. For the Environment Key Performance Area, the local performance plans could be developed at both national and FAB level.

(2) The COMMISSION IMPLEMENTING REGULATION (EU) 2019/317 of 11th of February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013 defines the consistency criteria between the local performance targets and the EU-wide targets for the Environment Key Performance Area, as follows:  Consistency of national performance targets or FAB performance targets with the Union wide performance targets for each calendar year of the reference period, by comparing the national performance targets or FAB performance targets with the en route horizontal flight efficiency reference values set out in latest version of the European Route Network Improvement Plan available at the time of adoption of the Union-wide performance targets.  For the purpose of this paragraph, the ‘en route horizontal flight efficiency reference value’ means the estimated value by the Network Manager of the flight efficiency of the actual trajectory at national level or at the level of functional airspace blocks, for the purpose of ensuring that the Union-wide target on horizontal en route flight efficiency of the actual trajectory is met.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 13

EUROCONTROL Network Management Directorate

(3) The KEA reference values based on the European-wide target for States/ANSPs are:

ANSP 2020 2021 2022 2023 2024 SKEYES 7.09% 7.09% 7.05% 7.05% 7.05% DFS 2.81% 2.73% 2.65% 2.65% 2.65% EUROCONTROL MUAC 1.99% 1.92% 1.85% 1.85% 1.85% EANS 1.33% 1.33% 1.32% 1.32% 1.32% ANS FINLAND 0.97% 0.97% 0.96% 0.96% 0.96% NATS 3.53% 3.39% 3.25% 3.25% 3.25% LVNL 7.22% 7.20% 7.18% 7.18% 7.18% IAA 1.56% 1.54% 1.53% 1.53% 1.53% NAVIAIR 1.21% 1.21% 1.20% 1.20% 1.20% AVINOR 1.43% 1.43% 1.42% 1.42% 1.43% PANSA 1.67% 1.66% 1.64% 1.64% 1.64% LFV 1.26% 1.26% 1.25% 1.25% 1.25% LGS 1.30% 1.30% 1.29% 1.29% 1.29% ORO NAVIGACIJA 1.90% 1.88% 1.85% 1.85% 1.85% ALBCONTROL 1.96% 1.96% 1.95% 1.95% 1.95% BULATSA 1.95% 1.91% 1.87% 1.87% 1.87% CYPRUS DCA 4.10% 4.03% 3.95% 3.95% 3.95% CROATIA CONTROL 1.49% 1.48% 1.47% 1.47% 1.47% ENAIRE 3.23% 3.07% 2.90% 2.90% 2.90% DSNA 2.90% 2.83% 2.75% 2.75% 2.75% HCAA 1.94% 1.83% 1.72% 1.72% 1.72% HUNGAROCONTROL 1.45% 1.44% 1.43% 1.43% 1.43% ENAV 2.83% 2.80% 2.77% 2.77% 2.77% SLOVENIA CONTROL 1.68% 1.68% 1.67% 1.67% 1.67% ANS CZECH REPUBLIC 2.26% 2.21% 2.16% 2.16% 2.16% MATS 1.46% 1,45% 1.44% 1.44% 1.44% AUSTROCONTROL 1.90% 1.88% 1.86% 1.86% 1.86% NAV PORTUGAL 1.76% 1.75% 1.73% 1.73% 1.73% BHANSA 1.22% 1.22% 1.21% 1.21% 1.21% ROMATSA 1.55% 1.48% 1.40% 1.40% 1.40% SKYGUIDE 4.62% 4.53% 4.45% 4.45% 4.45% DHMI 2.97% 2.87% 2.77% 2.77% 2.77% MOLDATSA 1.94% 1.94% 1.93% 1.93% 1.93% M-NAV 1.75% 1.75% 1.75% 1.75% 1.75% SMATSA 1.62% 1.62% 1.61% 1.61% 1.61% LPS SR 2.10% 2.05% 1.99% 1.99% 1.99% ARMATS 2.53% 2.48% 2.43% 2.43% 2.43% SAKAERONAVIGATSIA 2.16% 2.11% 2.06% 2.06% 2.06% UKSATSE 2.56% 2.41% 2.26% 2.26% 2.26%

Table 2 : KEA reference values for States/ANSPs

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 14

EUROCONTROL Network Management Directorate

2 ARN Version 2020 - 2024 Benefits

2.1 Total Expected Benefits - ERNIP PART 2 - ARN Version 2020 - 2024

(1) The ERNIP Part 2 - ARN Version 2020 - 2024 contains, at this stage, approximately 340 (three hundred and fourty) packages of airspace proposals scheduled for implementation for the Summer seasons 2020 - 2024, out of which approximately 110 would have been implemented by April 2020.

(2) Beside others, these proposals include more than 100 ATS route changes, around 35 re-sectorisation plans, more than 40 TMA projects, 15 PBN projects, more than 50 Free Route Airspace projects, 10 civil/military airspace developments as well as around 15 improvement measures eliminating unnecessary RAD restrictions or improving flight efficiency and 5 ATM system upgrades. They were or will be implemented as follows:  approximately 150 proposals for the Summer season 2020;  approximately 110 proposals for the Summer season 2021;  approximately 45 proposals for the Summer season 2022;  approximately 15 proposals for the Summer season 2023;  approximately 20 proposals between Summer season 2023 until end of 2024.

(3) When compared to the start of RP3, the full benefits that ENRIP Part 2 - ARN Version 2020 - 2024 would bring in 2024 represent approximately 130 million NMs, i.e. the equivalent of 800 000 tons of fuel saved, or reduced emissions of 2 600 000 tons, or 670 million Euros.

Figure 1 : Route Efficiency KPI per AIRAC cycle

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 15

EUROCONTROL Network Management Directorate

(4) The implementation of ERNIP Part 2 - ARN Version 2020 - 2024 has the potential to significantly improve flight efficiency if all projects are fully implemented. The route extension due to airspace design (if all flights would have used the route network without any route restrictions and with all CDRs permanently available) is expected to decrease from 2.22% in December 2019 to approximately 1.85% by 2024. The graph below shows the expected evolution of flight efficiency between 2008 and 2024 in terms of extension compared to the great circle.

2.2 Capacity Enhancement Benefits of ERNIP Part 2 - ARN version 2020 - 2024

(1) The ERNIP Part 2 - ARN Version 2020 - 2024 Catalogue contains several re- sectorisation projects in addition to route network solutions that are aiming at reducing the complexity of the airspace structure. Based on fast time simulations of a number of projects, it is expected that the ARN Version 2020 - 2024 would bring an additional 5 - 7% capacity to the European ATM network when fully implemented.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 16

EUROCONTROL Network Management Directorate

3 European Route Network Design Function and Flight Efficiency Action Plans

3.1 European Route Network Design Function

(1) This document contains the ATS Route Network ARN Version 2020 - 2024 Catalogue of Airspace Projects as Part 2 of the European Route Network Improvement Plan (ERNIP). This document addresses the requirements set forth in the COMMISSION IMPLEMENTING REGULATION (EU) 2019/123 of 24 January 2019 on the Implementation of the ATM Network Functions and repealing Commission Regulation (EU) No 677/2011 and supplemented by the requirements set forth in the COMMISSION IMPLEMENTING REGULATION (EU) 2019/317 of 11 February 2019 , laying down a performance and charging scheme in the single European sky and repealing Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013:  The production of the European Route Network Improvement Plan;  Delivering airspace solutions and interfaces required to facilitate operational  interconnectivity between FABs;  monitoring and improvement of the overall capacity and environment/flight efficiency performance of the network from an airspace design and utilisation perspective; and  supporting the different operational stakeholders within the obligations that are put to them in the development and deployment of the European Route Network Improvement Plan and in deploying relevant actions in accordance with the European ATM Master Plan.

3.2 Free Route Airspace

(1) Until Summer 2020 Free Route Airspace would be fully implemented H24 in the following ACCs: Beograd ACC, Bodo ACC, Bratislava ACC, Brindisi ACC, Bucuresti ACC, Budapest ACC, Chisinau ACC, Dnipro ACC, Karlsruhe UAC, Munich ACC, Kyiv ACC, Kobenhavn ACC, Lisboa ACC, L’viv ACC, Ljubljana ACC, Malmo ACC, Malta ACC, Maastricht UAC, Milano ACC, Oslo ACC, Padova ACC, Riga ACC, Roma ACC, Shannon ACC, Skopje ACC, Sofia ACC, Stavanger ACC, Stockholm ACC, Tallinn ACC, Tampere ACC, Tbilisi ACC, Tirana ACC, Vilnius ACC, Warszawa ACC, Wien ACC, Yeveran ACC, Zagreb ACC and Bodo Oceanic FIR.

(2) Free Route Airspace for the night period has been implemented in the following ACCs: Agadir ACC, Athinai ACC, Makedonia ACC, Minsk ACC, Odessa ACC and Karlsruhe UAC West, Karlsruhe UAC South, Bremen ACC East.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 17

EUROCONTROL Network Management Directorate

The following maps show: Free Route Airspace implementation plans until end of 2020.

Figure 2 : FRA until end 2020

Free Route Airspace implementation plans until end of 2024.

Figure 3 : FRA until end 2024

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 18

EUROCONTROL Network Management Directorate

3.3 Route Availability Document RAD Improvements

(1) The actions performed by the Network Manager have facilitated a pragmatic refinement of the RAD, with full cooperation of Operational Stakeholders, aiming to overcome weaknesses in airspace design and ATM system functionality and to ensure an application of the remaining restrictions only where and when required. The major RAD evolutions and developments focused mainly on Network level and covered the entire NM area of responsibility.

(2) The Network Manager provided an input to the States / ANSPs / FABs on the inconsistencies identified in Pan-European Annex and/or individual Appendixes concerning the current allowed DCTs in RAD Appendix 4 and 5, and published terminal procedures versus RAD Appendix 5. The process of resolution of inconsistencies between the NMOC systems and RAD Appendix 7 is ongoing and close to be completed.

(3) The FRA implementations led to a gradual adaptation of the RAD to meet FRA requirements and refinement of restrictions based on airspace volumes. The RAD was further simplified in FRA areas where the ATS route network was withdrawn. The majority of RAD restrictions based on ATS routes were removed or replaced by single RAD restrictions. These new RAD restrictions are based on relevant FRA significant point/s or Airspace Volume/s (ATC Unit, AoR of relevant ATC Unit - CTA/UTA, TMA, CTR or individual control sector/s within an ATC unit) and merged several existing ones. RAD Evolution

(4) The RAD evolution steps approved by the NDOP are: Step I: Re-definition of the CDM process on the acceptance of proposed RAD restrictions in accordance with the justification, assessment results and objective goal of the proposed RAD restrictions:  This step will be supported by an assessment of the need, the effect and traffic impacted by the request to have new RAD restrictions introduced. Step II: Definition of a new process for the “Last minute” changes:  Perform assessment of the proposed RAD restrictions and subsequently proposed “Last minute” changes; o Allow exemptions in the “Last minute” changes eligibility criteria that address mainly exceptional circumstances. Step III: Establishment of a post-ops process to continuously re-evaluate the existing RAD restrictions and if additional justification not provided to ask for those RAD restrictions to be suppressed. Step IV: Propose simplification of the RAD restrictions; Collapse multiple RAD restrictions in one network RAD restrictions with the same effect; Evaluate and propose suppression of RAD restrictions constantly not respected on ATC.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 19

EUROCONTROL Network Management Directorate

Step V: Define network oriented RAD restrictions together with concerned States / FABs / ANSPs, after the provision of clear objective goal and justification for RAD restriction implementation. Step VI: Propose structural airspace changes to eliminate the need for RAD restrictions. Step VII: The final content of any amendment to the RAD shall be positively agreed between the NM RAD Team and State / FAB / ANSP concerned. Step VIII: Define the requirements and gradually implement an enhanced pre-validation process supported by automation to allow better validation and flight planning. Step IX: The new RAD CDM processes defined shall take fully into account the new technical support being implemented through RAD Application tool as from 2019. Step X: Definition of enhanced promulgation processes for the RAD relaxations. RAD Way forward

(5) Considering the above RAD evolution steps the Network Manager proposed concrete actions. The aim is to ensure more flexibility in the way in which the RAD is managed and to achieve significant simplification of the RAD.

(6) The Network Manager in cooperation with States / FABs / ANSPs will further develop these actions and establish relevant RAD development process.

(7) All the required improvements for the identified areas will be implemented within the context of ERNIP Part 2 - ARN Version 2020 - 2024 thus constantly improving flight efficiency with no negative impact on safety or on capacity.

3.4 Improving TMA Structures

(1) Improved Terminal Airspace/ TMA design projects are or will be implemented in the context of the ARN Version 2020 - 2024 at: Al Hoceima (GMTN) TMA, Barcelona TMA, Batumi TMA, Brussels TMA, Canarias TMA, Copenhagen TMA, Istanbul TMA, Jersey TMA, Kharkiv TMA, Kaunas TMA, Kutaisi TMA, Lisboa TMA, London TMA, Madrid TMA, Madeira TMA, Malta TMA, new Nador (GMMW) TMA, Palma TMA, Riga TMA, Tbilisi TMA, Vienna TMA, Vilnius TMA and Warszawa TMA.

(2) In the time frame of ERNIP Part 2 - ARN Version 2020 - 2024 the Istanbul New Airport - LTFM, a 3rd RWY at Istanbul New Airport, a new runway at Istanbul Sabiha Gökcen airport, a new runway at Krakow airport and the new Berlin Brandenburg International airport are planned.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 20

EUROCONTROL Network Management Directorate

3.5 The Flight Efficiency Plan

(1) IATA, CANSO and EUROCONTROL worked in a close partnership along with airlines, airports and ANSPs to identify solutions and launch operational actions that will lead to fuel and emissions savings in the short term to develop a Flight Efficiency Plan that was commonly agreed in September 2008.

(2) The action points of the Flight Efficiency Plan, relevant for the ERNIP Part 2 - ARN Version 2020 - 2024, are: a) Enhancing European en-route airspace design through annual improvements of European ATS route network, high priority being given to:  Implementation of a coherent package of annual improvements and of shorter routes;  Improving efficiency for the most penalised city pairs;  Implementation of additional Conditional Routes for main traffic flows;  Supporting initial implementation of free route airspace. b) Improving airspace utilisation and route network availability through:  Actively support and involve aircraft operators and the computer flight plan service providers in flight plan quality improvements;  Gradually applying route availability restrictions only where and when required;  Improving the utilisation of civil/military airspace structures. c) Efficient TMA design and utilisation, through:  Implementing advanced navigation capabilities;  Implementing Continuous Descent Approaches (CDAs), improved arrival/departure routes, optimised departure profiles, etc.

(3) The vast majority of the improvements considered in the context of the ERNIP Part 2 - ARN Version 2020 - 2024 contribute to the deployment of the Flight Efficiency Plan.

3.6 The Network Manager Flight Efficiency Initiative

(1) A closer cooperation with the airspace users to ensure a better flight planning is essential to ensure the achievement of the RP3 targets. The good progress made over the past years in the airspace design resulted in a European airspace offering, in a dynamic manner, a high number of options for the airspace users. In order to achieve a better utilisation of the European airspace by the airspace users, the network manager launched a Flight Efficiency Initiative that covers the following aspects:  Flight Planning Improvements in the Strategic Phase o An interactive tool was developed to allow all AOs and CFSPs to compare their flight plans with the best filed flight plan accepted by IFPS; o The airspace users and the CFSPs will have the possibility to detect new implemented routes, CDRs available during similar periods of time, etc.; o It is expected that the airspace users and the CFSPs will use this interface to improve their flight planning for the “next” AIRAC cycle;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 21

EUROCONTROL Network Management Directorate

o This tool could also be used to assess individual airline flight plans or to detect possible network performance evolutions.

 Enhanced utilisation of CDRs through the deployment of ASM solutions

o Assessment of traffic demand, ATFM measures, sector configurations and CDRs availability; o Existence of CDRs segments in the FPL; o Route extension compared with the “best option”; flight extension mostly for en route section (avoid extensive arrival/departure situations); o Search for the flights with the shortest planned route for each city pair having at least one CDR in their planned route; o For each city pair assess the CDR availability requirements if all the flights on that city pair would plan the shortest route; o Proposals to AOs for better routes including CDRs; o Possible coordination with military partners, when required, for coordinated availability of CDRs.

 Flight Planning improvements in the Pre-Tactical/Tactical Phases o Enhance the visibility for aircraft operators on other route network utilisation options, post IFPS flight planning with proposals being displayed to the users; the final choice in accepting a more optimised proposal remains with the airspace users. Those actions are based on: . The Group Rerouting Tool (opportunity tool) - an ETFMS feature allowing a re-computation of the profile considering the wind, the last ATFCM situation, simulated operating costs; . Proposals for flight efficiency improvements for invalid flight plans that require manual corrections; . Network impact assessments resulting in re-routing proposals based on CDR2 routes with the direct involvement of MILO/AOLO;

o Most Penalised City Pairs . Further developments to address the Most Penalised City Pairs; . Daily monitoring of the utilisation of the new airspace changes; . Detect improvements based on the latest airspace design or airspace utilisation changes.

o Tactical RAD relaxations . Based on existing Crisis Procedures; . Similar procedures could be implemented during normal operations as comparisons between actual trajectories and flight plans show that the RAD is not systematically followed during tactical operations; . Tactical relaxation of RAD could be also envisaged during the night or during period of low demand.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 22

EUROCONTROL Network Management Directorate

(2) The implementation of this initiative is based on:  A close and continuous cooperation between NM and the airspace users;  A close and continuous cooperation with the computer flight plan service providers;  Appropriate evolutions of the flight planning systems to take into account the past and future evolutions of the airspace concepts.

(3) This initiative will require the strong support and participation of the entire airspace users community. This support is critical for ensuring the achievement of the RP3 environment/flight efficiency target. Without such a support, the positive evolutions made with respect to the European airspace design through co- operative efforts between NM and States/ANSPs/FABs will not provide their full potential.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 23

EUROCONTROL Network Management Directorate

4 Concept of Operations for European Airspace Design

4.1 Main Principles

(1) Successful European airspace design is achieved through:  The implementation of an advanced and consolidated concept of operations;  A pan-European view treating the European airspace as a continuum and a strategic vision of the European ATS Route Network, designed following main traffic flows and airspace users preferred routes and profiles with optimised supporting ATC sectors unconstrained by national or FIR boundaries;  Gradual elimination of bottlenecks and reasons for flight inefficiency;  Optimised procedures for an enhanced use of airspace;  A balanced approach between European network, regional and local requirements;  A co-ordinated and integrated partnership approach for the collective benefit of airspace users, Member States, Air Navigation Service Providers, civil and military authorities deployed through a collaborative planning process.

(2) The diagram below describes the European Route Network Improvement Plan/ ERNIP development.

Figure 4 : ERNIP Part 2 Principles

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 24

EUROCONTROL Network Management Directorate

4.2 ERNIP Part 2 - ARN Version 2020 - 2024 Concept Highlights

Introduction

(1) The performance targets place more demands on the need to enhance the organisation and use of the European ATM network. Additional capacity will need to be delivered, flight efficiency improved and environmental impact reduced, while maintaining or improving safety of operations.

(2) Air traffic diversity is expected to become more complex with the emergence of additional civil and military requirements, which will alter the mix and flight profiles of the airspace users. This will lead to additional diversity in the airspace user requirements

(3) The solution for meeting the safety, capacity, flight efficiency/cost effectiveness and environmental requirements is the strategic planning and design of “packages” of ATS routes of the ARN, Free Route Airspace, Terminal Routes, airspace reservations and ATC sectors, to respond to the requirements of different strategic objectives. These packages are called Airspace Configurations.

(4) The solution for meeting the diversity of user requirements is the effective and dynamic management of airspace configurations through a highly flexible and integrated Cooperative Decision-Making (CDM) process at network, regional, national and local level management of the pre-designed airspace configurations through a highly flexible and integrated CDM process at network, regional, national and local level.

Basic Concept

(1) In both en-route and terminal airspace, an Airspace Configuration refers to the pre- defined and co-ordinated organisation of ATS routes of the ARN and/or Terminal Routes, Free Route Airspace and their associated airspace structures (including temporary airspace reservations, if appropriate) and ATC sectorisation.

(2) In the en-route airspace, airspace configurations are to be comprised of pre-defined fixed and flexible routing options or optimised trajectories and optimum ATC sectorisation capable of being dynamically adapted to traffic demand. Airspace configurations will be activated, through a CDM process, depending upon the driving Strategic Objective(s) for a particular geographic area and/or time period.

(3) In terminal airspace, airspace configurations are contained primarily within terminal airspace structures. Airspace configurations may be activated depending upon the runway configuration in use at one or more airports and the driving Strategic Objective(s) of a particular time period.

(4) The above is based on a coordinated and systematic approach to selecting and changing airspace configurations across the European ATM System.

(5) The ARN Version 2020 - 2024 is built on a close co-operation between airspace design, ATFCM and ASM. It supports a close link between airspace design and airspace utilisation.

European Network Consistency

(1) The overall European Network Consistency is assured across through the consolidated development of the ERNIP Part 2 - ARN Version 2020 - 2024. Co- ordination and consolidation of airspace design, planning and implementation is achieved through Cooperative Decision-Making (CDM) at European network level.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 25

EUROCONTROL Network Management Directorate

(2) The ERNIP Part 2 - ARN Version 2020 - 2024 is based on a European wide collaborative process by which the major traffic flows, combined with major airspace constraints (airports, military areas etc.) are translated into a basic route structure. Built upon agreed planning principles, the resultant structure provides the basis for more detailed development by States and ANSPs at national or regional/FAB level. The scheme will consider the European airspace in its totality, independent of FIR boundaries.

Airspace Continuum

(1) An airspace continuum was envisaged in the development of the ERNIP Part 2 - ARN Version 2020 - 2024. This means that there is no intended division within en- route airspace or between en-route and terminal airspace. However, the different attributes of en-route and terminal airspace drove specific requirements resulted in changes to various interfaces to improve efficiency.

(2) A lateral airspace continuum is ensured through regional airspace configurations in both en-route and Terminal Airspace (e.g. FAB or TAS), where application of various the rules associated with airspace utilisation will be harmonised.

(3) A network continuum was ensured through the development of the overall ERNIP Part 2 - ARN Version 2020 - 2024 where all aspects related to lateral and vertical interconnectivity, including interconnectivity within and between regional airspace configurations, were thoroughly addressed.

ARN Version 2020 - 2024 Components

(1) ATS routes continue to characterise the airspace for the most part in the context of the ERNIP Part 2 - ARN Version 2020 - 2024, while Free Route Airspace will be used in selected airspaces and/or at selected times.

(2) The main characteristic of the ATS routes of the ERNIP Part 2 - ARN Version 2020- 2024 is to offer more routeing options to the airspace users. These routes will be based on principles of route network design and sectorisation independent from national boundaries, adapted to main traffic flows.

(3) An airspace structure built on the basis of an ATS route network and Free Route Airspace is capable of being managed more flexibly to permit operators to choose from several strategically designed airspace structures (ATS routes and Free Route Airspace) of the ERNIP Part 2 - ARN Version 2020 - 2024.

(4) Improvements in the strategic design, planning and management of these 2 components will improve the predictability of the route options. This flexibility is based on principles of the Flexible Use of Airspace Concept.

(5) The requirements of GAT and OAT are accommodated by integrating these into the strategic ARN developments.

(6) ATC sectors of ERNIP Part 2 - ARN Version 2020 - 2024 are adapted to main traffic flows and to an optimum route network and are, when required, independent from national boundaries. More ATC sectors are developed and made available, where required (including vertical divisions), in response to variations in demand and airspace availability. This work was conducted with the full involvement of States and ANSPs as it is their direct responsibility for the final design of ATC sectors supporting the route network structure and Free Route Airspace.

(7) To improve the design and management of terminal routes and ATC sectorisation servicing several airports in close proximity, the fusion of two or more terminal

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 26

EUROCONTROL Network Management Directorate

airspace structures is envisaged where required. This amalgam is described as a Terminal Airspace System (TAS). These TAS could extend across national borders if necessitated by operational requirements.

Airspace Classification

(1) Above FL195, ATS routes, Free Route Airspace and Terminal Routes will be contained within Class C airspace. At and below FL195, ATS routes of the ARN as well as Terminal routes will be contained within airspace where, for safety reasons, there is to be a uniform application of the rules associated with the seven ICAO airspace classes.

(2) At or below FL195, where supplemental rules to the seven ICAO airspace classes are required to respond to operational and safety requirements, additional rules will be created and applied in a safe manner.

Airspace Organisation

(1) The practical airspace organisation features of ERNIP Part 2 - ARN Version 2020 - 2024 are:  Multi-option route choice: New route segments and Free Route Airspace were added to the network. These additional airspace structures are compatible with the overall airspace structure. They include 24 hours choices, but also time limited choices (e.g. time-limited application of Free Route Airspace). In the event of airspace restrictions caused by traffic density and/or ACCs/sector configuration or activation of segregated airspace, suitable alternative options are available. The dynamic capacity/route use will be brought about by collaborative decision-making based on the pre-determined set of routing options.  Modular sectorisation: To the largest possible extent and where required, sectors are established across national borders and in accordance with main traffic flows. They will support the pre-defined airspace structures. Reconfiguration of pre-defined modules of airspace (sector modularity) help to adapt the sector configurations to specific traffic flows.  Efficient Terminal/En-route interface: Efficient structures based on segregated arrival/departure routes extending beyond the Terminal Airspace are part of the ERNIP Part 2 - ARN Version 2020 - 2024. Where incompatibilities arise, priorities were discussed and given depending on operational requirements to the en-route part or to the terminal structure.

Airspace Development Approach

(1) The process for developing an airspace structure was based, in most of the cases on the following sequence:  Determine the Route Network or the Free Route Airspace - improvement of the route network or implementation of Free Route Airspace took into account the users’ preferred routes and inclusion of direct route segments on the largest possible extent whilst meeting the requirements of the military;  Define the Sector Families - areas containing specific air traffic flows and conflict areas which will consist of strongly interdependent sectors;  Define Sectors - definition of the minimum operational elementary volume;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 27

EUROCONTROL Network Management Directorate

 Define Sector configurations - a combination of sectors best placed to satisfy the operational requirements (traffic demand, traffic pattern, staff) and airspace availability;  Define the Modus Operandi

4.2.8.1 Route Network

(1) The objective of ERNIP Part 2 - ARN Version 2020 - 2024 is to provide Aircraft Operators with their preferred trajectories selected from within the route network, whilst ensuring that the safety and capacity targets defined by the sectorisation are met.

(2) The ERNIP Part 2 - ARN Version 2020 - 2024 delivers more route choices to the operators when planning a flight. This involves improved access to the existing route network and the creation of new routes, including predefined direct routes available subject to time limitations or ASM conditions.

(3) The Route Network design criteria took into account the need to create additional routes that did not exist in the previous network as they caused capacity problems at certain times. The ERNIP Part 2 - ARN Version 2020 - 2024 introduced these new routes and made them available for use under specific pre-defined conditions that are made known to all airspace users. As a result, the most direct of the routes choices could be planned at certain times.

(4) In other cases, choices will need to be made by the airspace users between the shortest route but with capacity constraints, a slightly longer route will be made available with no capacity constraints, but involving ASM solutions, or a longer route available with no airspace constraint.

(5) The airspace users will, at a pre-determined time, make the decision on the choice of route based on up to date data on the sector constraint and segregated airspace availability.

(6) The creation of pre-defined direct routes subject to ASM conditions, should provide benefit to the military users as well as it will be possible to better respond to their requirements when the preferred route is available. This in turn lead to the implementation of a larger number of CDRs 1.

4.2.8.2 Free Route Airspace

(1) The ERNIP Part 2 - ARN Version 2020 - 2024 provides an enabling framework for the harmonised implementation of Free Route Airspace in Europe. It is based on the Free Route Airspace Concept developed in the context of the ARN Version-7 and included in ERNIP Part 1 and on the FRA Design Guidelines.

4.2.8.3 Sectorisation

(1) The development of ERNIP Part 2 - ARN Version 2020 - 2024 took into account the need to gradually implement Sector Families of interdependent sectors that can be clustered into logical Family Groups. In all the development, projects aspects related to areas of weak and strong interaction were considered through the utilisation of the supporting airspace design tools.

(2) The criteria for determining Sector Families, Family Groups and elementary sectors were based on:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 28

EUROCONTROL Network Management Directorate

 an optimised route network, integrating direct routes, Free Route Airspace, multiple route options, associated alternatives and military operational requirements;  efficient connectivity with terminal airspace;  design of elementary sectors with strong/complex interaction that necessitate close co-ordination between controllers;  traffic density, conflict density and repartition, traffic profiles, nature of traffic (climbing/descending), crossing flows, close crossing points, etc.  operational considerations for lateral and vertical delineation;  determining variable sizes of sectors with small/specialised low level sectors, deep medium sectors (for evolving traffic) and wider upper sectors;  usage of modular techniques;  time of flying within a sector family;  several combinations of flexible sectors configuration were defined, depending on traffic flows;  enabling sufficient distance for conflict resolution in all routeing options;  maintaining route options, on the largest possible extent within the same sector family;  iterative process for sectorisation considering route network modifications to enable the best possible sectorisation;  the identification of zones of lesser complexity.

4.2.8.4 Modus Operandi

(1) The Modus Operandi of the ERNIP Part 2 - ARN Version 2020 - 2024 includes:  The availability, in terms of time and FL, of route segments (including the direct route segments) or Free Route Airspace in line with the constraints imposed by segregated airspace or by the need to better balance capacity and demand;  The links between-route network, Free Route Airspace and sectorisation including conditions for availability of certain route segments or Free Route Airspace and their dependence on the configuration of ATC sectors to match traffic demand;  Routing scenarios - including all pre-planned alternate routeings to compensate for the temporary unavailability of a certain airspace structures;  Structural constraints - notified constraints, such as, the activation of segregated airspace, sector capacity restrictions, specialised routes for specific traffic flows, profile constraints to skip sectors in a given configuration and modifying capacity depending on the sector configuration;  Recommended practices - proposals derived from operational experience including the process for selecting sector configurations.

Operating the ERNIP Part 2 - ARN Version 2020 - 2024

(1) The rationale for the ERNIP Part 2 - ARN Version 2020 - 2024 was to ensure that the ATS route network, the Free Route Airspace and the ATC sector planning allow for an improved balance between:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 29

EUROCONTROL Network Management Directorate

 freedom for GAT to choose between-route options, and select their preferred one;  offering greater flexibility for OAT users through more efficient allocation of airspace;  capacity management - relying on fine tuning of route adaptation to optimise the use of available capacity where limitations of capacity occur.

(2) Local and Regional/FAB documentation was or will be amended to include the updated rules and procedures. Amongst these are:  National AIPs;  National ATC Regulations;  LoAs;  National ATM Military Documents;  Airspace Management Handbook;  IFPS Users Manual;  ATFM Users Manual.

(3) No change was made to the route description. However, specific description and usage was implemented to facilitate flight planning for the usage of direct segments within Free Route Airspace.

(4) Flight planning procedures were further improved to take into account the flexibility of route selection offered by the ERNIP Part 2 - ARN Version 2020 - 2024. Further initiatives are under way to facilitate improved flight planning and route selection, including FF-ICE/FIXM. Airspace users should expect more flexibility in the FPL handling based on planned IFPS system enhancements to allow for the dynamic choice of route and/or re-routeing process. The ERNIP Part 2 - ARN Version 2020 - 2024 supports the usage of DCT in the FPL within a consolidated concept and approach.

(5) It is expected that operations within the ERNIP Part 2 - ARN Version 2020 - 2024 will be facilitated through the deployment of the Airspace Data Repository that will ensure gradually an automated distribution of airspace availability information in order to provide all interested parties with a clear and accurate picture of the airspace structure situation.

(6) The ERNIP Part 2 - ARN Version 2020 - 2024 enables a more flexible ATFCM system and will ensure the gradual move towards the creation of a system responsive to capacity management. The addition of an optimisation process able to provide routeing alternatives to solve capacity and flight efficiency constraints, while maintaining the balance with the airspace user costs, will enhance the current method of managing airspace capacity.

Military Operations

(1) The ERNIP Part 2 - ARN Version 2020 - 2024 recognises and supports the responsibilities and requirements of Military airspace users. In order that all airspace users gain benefit from ERNIP Part 2 - ARN Version 2020 - 2024, military airspace planners were part of the planning process. An organised collection of military airspace requirements is one of the specific elements that the ERNIP Part 2 - ARN Version 2020 - 2024 took into consideration.

(2) Through the solutions proposed in ERNIP Part 2 - ARN Version 2020 - 2024, the military should be able to have:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 30

EUROCONTROL Network Management Directorate

 freedom to operate in all weather conditions in all areas of the European airspace;  special handling in particular for priority flights and for time-critical missions, but also for military aircraft not fully equipped to the civil standard;  the possibility of operating uncontrolled VFR flights;  temporary airspace reservations (TSAs), situated as close as practicable to the appropriate operating airfield;  airspace restrictions for non-flight related activities;  a more dynamic airspace allocation system with enhanced FUA application.

(3) The ERNIP Part 2 - ARN Version 2020 - 2024 supports these requirements through greater flexibility in airspace use, the efficient allocation of segregated airspace and associated re-routeing of GAT users. With a route network and sectorisation that adapts to the variation in traffic flows there scope for better application of the Flexible Use of Airspace.

Airspace Management (ASM) Solutions

General Principles

(1) The identification and development of the ASM Solutions is a part of the ASM Improvements Initiative. The ASM solutions form an integral part of the ERNIP Part 2 - ARN Version 2020 - 2024. They include:  Reviewing the different availability of CDRs at different stages;  Addressing the potential incompatibility of availability of CDRs on segments of the same route with the stakeholders concerned;  Reviewing and improving the design of CDRs in combination with modular TRA/TSA design;  Improving the definition of ASM Solutions to be used at ASM level 2 and 3.

(2) The main objective of the ASM Solutions development is to identify hidden airspace capacity or flight efficiency directly related to the area of Airspace Management, i.e. civil-military requirement to use the same portion of airspace at the same time. This activity is aimed at improving the existing practices in order to overcome the capacity constraints and provide efficient flight operations of both, civil and military airspace users. It aims at identifying such airspace use scenarios, which will bring benefits to both - civil and military categories of airspace users. It will provide for a credible balance in meeting the requirements of all the partners in airspace use and its management.

(3) To deliver extra capacity and flight efficiency, the current ASM processes and procedures related to a particular TRA/TSA are reconsidered, both in their design and associated airspace planning and allocation processes and procedures. The enhanced ASM processes will consider various levels of flexibility, either in time or in spatial location (vertical or horizontal), that are permissible by the planned civil or military flight operations.

(4) The civil aircraft operators are to achieve more efficient, less costly and delay-free operations in some portions of airspace that today restrict meeting the demand, using different CDR options that are co-located to each sub-modular configuration of a particular temporary reserved or restricted airspace portion.

(5) The military might need to request an enlarged airspace volume to meet the requirements of specific missions. To respond to this request a set of well planned

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 31

EUROCONTROL Network Management Directorate

airspace scenarios that are adapted to different mission requirements concerning the airspace size (lateral and vertical) and timing will be available, thus eliminating any requirement for airspace overbooking.

(6) Air Navigation Service Providers participation in collaborative decision- making on implementation of a particular scenario related to the specific TRA/TSA, will ensure that their needs of sectors’ capacity to accommodate the traffic demand are properly addressed.

(7) The final objective of the ASM Solutions development is to identify concrete and consistent solutions for each identified hot-spot, i.e. an interactive civil-military solution. Next step is to extend the activity at the sub-regional level by coordinating interaction between adjacent local options.

(8) The process of final ASM Solutions development is expected to be carried out by the civil and military partners responsible for a particular TRA/TSA.

(9) At the second stage the coordination is planned to be extended to all those concerned by the interaction in defining and deciding upon different scenarios, resulting in the most suitable sub-regional ASM Scenario.

(10) Last but not least, with this optimised local and sub-regional network response, the task of Network Operations should be focused on the global network solutions that can lead, by judicious selection, to less ATFCM measures. ASM Solutions Methodology

(11) The traffic samples to be used in initial scoping and identification of the potential hot-spots, but equally later in developing concrete ASM Scenario(s) will be based on the historical traffic data. The data on TRA/TSA booking will be derived from AUP/UUP/e-AMI information available and their occupation from various sources like CIAM and PRISMIL, or from national ASM tools.  Future Data Collection and Planning The objective of this particular activity is to continually collect information and data on planned introduction and/or change in ASM-related airspace structures and arrangements, i.e. TRAs, TSAs, CBAs, manageability of D and R areas, cross-border airspace sharing arrangements. The information and data collected will enable the assessment and coordination of any planned introduction or change in collaborative manner, enabling consistent solutions planned among neighbouring States, but also at sub-regional (FABs) and, last but not least, at the European Regional level, thus enhancing the European Network performance. This approach was already agreed and put in place between the parties concerned.

 Identification of areas of interest Identification of Hot-Spots that have a potential for capacity and/or flight efficiency improvements through an interactive civil-military solution will be constantly pursued in order to make use of the options made available through the ERNIP Part 2 - ARN Version 2020 - 2024.

For the purpose of initial scoping and identification of potential benefits the closest to the optimum ATS route traffic sample available will be considered as the reference, i.e. the least constrained by military activity or other events. It will then be put against the traffic sample of the most intense day of civil and military activity.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 32

EUROCONTROL Network Management Directorate

Aircraft Operators that may benefit from the ASM/ATFCM scenarios will be involved at an early stage, to ensure that benefits are realistic and ensure AO utilisation of the scenarios. Once the selected Hot-Spots are identified, the potential benefits will be scoped for different potential solutions based on variation and combination of different parameters:

 Vertical A number of vertical configurations will be examined to identify any potential in dynamical managing of a TRA/TSA concerned. The main principle will be to assess if a vertical move of the military activity will contribute to the airspace capacity in particular area.

 Lateral Similarly to vertical, a number of lateral configurations, based on current and possible future airspace more sub-modular design will be investigated. It will be based on the larger airspace allocated (as appropriate) through activating different set of sub-modules that are sufficient to accommodate military requirements. Through this assessment, it will be confirmed that there is a potential to differently organise airspace planning and allocation in a particular TRA/TSA.

 Time-related Possibility to increase the airspace capacity by accommodating both military and civil demand as close as possible to the planned use of airspace will be investigated.

 Conditional Routes More conditional routes in a particular TRA/TSA will be simulated as a function of different lateral TRA/TSA configurations to increase capacity and to accommodate military and civil requirements at the same time. The main principle will be that, except when the military requirement is to use the whole TRA/TSA, different sub-module scenarios could accommodate both - military activity planned and the civil traffic demand to pass through the TRA/TSA concerned. The main principle being that there is theoretically at least one CDR along the main traffic flow and within a particular TRA/TSA that can accommodate civil traffic. Following the steps described above a comprehensive initial impact assessment will be performed per each identified Hot-Spot candidate. This assessment is to facilitate the decision that the Hot-Spot identified qualifies to be proposed to potential partners for further work on future ASM Solutions in the particular TRA/TSA.

4.2.11.2 Network Enablers

(1) The main enablers for the efficient implementation of the ERNIP Part 2 - ARN Version 2020 - 2024 are:  System Support - Enhancement for the purposes of flight planning and ATFCM;  Procedures - Enhanced procedures where necessary for operations within Free Route airspace and at its interfaces;  Adaptations to airspace structures;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 33

EUROCONTROL Network Management Directorate

 Adaptations to airspace management procedures.

(2) There are no additional equipment requirements identified for aircraft operators. Nevertheless, modifications to the flight planning systems is absolutely required to ensure that full benefit of the Free Route Airspace is achieved.

Impact on Adjacent Areas

(1) The ERNIP Part 2 - ARN Version 2020 - 2024 addresses the interfaces with adjacent areas so that they remain coherent and compatible. Liaison with adjacent States was constantly made at the relevant ICAO groups where the work underway within the RNDSG is presented through working and information papers. Similarly, States, ANSPs and the ICAO secretariat are presenting updates to the RNDSG on the airspace evolutions at the interfaces. This good cooperation at the interfaces of the European airspace is ensuring a consistent airspace structure based on the continuum principle. 5 A Network Cooperative Decision-Making Process

(1) The Network Cooperative Decision-Making Process for the ERNIP Part 2 is described in the Network CDM Processes document approved by the Network Management Board.

High level Process description a) Preparation  Input from NSP, previous NOP, NM Annual Report;  Input from all operational stakeholders and ICAO;  NM to prepare ERNIP proposals;  All operational stakeholders to agree on ERNIP proposals;  NETOPS substructure to review proposals;  NM to prepare draft ERNIP. b) Consultation  Network DOP, for any unresolved issues (if required);  NETOPS to agree on draft ERNIP. c) Approval  ERNIP Part 2 - ARN Version ARN Version 20xx - 20(xx+3/5) will follow the NOP approval process and goes to ICAO for inclusion in ICAO EANP.

ERND Process

(2) In the execution of the European Route Network Design Function, the Network Manager has to develop, through a cooperative decision-making process, the European Route Network Improvement Plan. The European Route Network Improvement Plan will be part of the Network Operations Plan.

(3) The Part 2 of the ERNIP is updated on an annual basis.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 34

EUROCONTROL Network Management Directorate

(4) The following calendar and CDM process was and will be followed by the Network Manager in close cooperation with the operational stakeholders for every update of the ERNIP Part 2: October 20xx Evaluation of the Summer 20xx situation and of the airspace design and utilisation related bottlenecks

October 20xx Presentation of the first version of the ERNIP Part 2 - ARN Version 20xx-20(xx+3/5)

January 20xx+1 distribution of the draft ERNIP Part 2 to RNDSG;

February 20xx+1 discussion on the draft ERNIP Part 2 at RNDSG and NETOPS; further comments requested;

March 20xx+1 comments received and incorporated in the ERNIP Part 2 and new versions distributed to RNDSG and NETOPS;

March 20xx+1 progress report presented to NMB;

April - May 20xx+1 agreement on final version for ERNIP Part 2 by RNDSG;

May - June 20xx+1 seek approval by NETOPS and N-DOP for ERNIP Part 2;

June 20XX+1 seek approval by NMB of ERNIP Part 2.

(5) The Route Network Development Sub-Group (RNDSG) is the co-ordination forum for European rolling airspace design and development, planning and implementation of improved European ATS route network, optimised civil and military airspace structures and ATC sectors. The members of the RNDSG work in a partnership approach and are civil and military experts in airspace design from EUROCONTROL, States, ANSPs, Functional Airspace Blocks, airspace users international organisations, flight planner organisations and other relevant international organisations. Its work is supplemented by other activities, which depending on their nature or complexity, may be under either the auspices of the RNDSG or independent, but bringing their results into the overall network picture through RNDSG processes. Examples are:  Sub-Regional RNDSG Meetings;  Regional co-ordination meetings between States;  Working groups proposing various solutions for specific problem areas;  Special projects (FABs, national re-organisation projects, sub-regional agreements, etc.).

(6) Appropriate links are ensured with the Airspace Management Sub-Group to cover civil-military related aspects and with other specific ATFCM groups.

(7) The consolidation of the entire development process was ensured through the Network Operations Team.

(8) This cooperative planning process responds to the emerging requirements on the setting of cooperative planning and decision-making processes on the development of the European route network.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 35

EUROCONTROL Network Management Directorate

European Network

Network Performance Targets

RNDSG Role FAB Proposals Rolling Improvement Plan Consolidated European Network for the European Network (3 – 5 years) National/Local • Common OPS Concept Proposals • Common Design Principles Planning • Share Best Practice Sub-Reginoal • Network Consolidation Proposals • Network Inter-connectivity Other • Project Synchronisation Stakeholders • Complete Network View Proposals • Support to Development Adjacent Areas • Stakeholders Coordination Annual Deployment Plans Proposals • Stakeholders Commitment • Input to ICAO Short Term Airspace Users Consultation/working arrangements Proposals Meet Network Performance Targets Network Proposals

Figure 5 : Network CDM

5.1 A Network Oriented Approach

(1) The Network Orientated Approach takes an European-wide view and is based upon the need to enhance the overall European ATM capacity and flight efficiency. The process progresses from broad proposals towards specific solutions via a number of steps. Step 1: Identify current and foreseen problems. The planning work highlights the capacity and flight efficiency problem areas and their causes in the airspace structure. Step 2: Build generally improved airspace structure proposals (both route segments and ATC sectors) to accommodate major traffic flows and balance ATC workload. Step 3: Within this defined framework, detailed proposals of airspace structure are elaborated with their “modus operandi”, consolidated and validated through regional expert groups. The result of local studies feeds back into the initial proposals in a dialectical and iterative process. Step 4: A phased implementation programme is agreed and carried out.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 36

EUROCONTROL Network Management Directorate

Figure 6 : Network Oriented Approach

5.2 Airspace Utilisation and Management

(1) The full potential of the European airspace structure, including supporting ATC Sectors, is often hindered by the restrictions that are imposed after the routes are implemented. In order to ensure that these airspace structures are used to their full potential, the way in which they are used should be an integral contributor to the rolling airspace design process.

(2) The ERNIP Part 2 - ARN Version 2020 - 2024 offers a greater number of possible options for its use with airspace configurations combinations facilitating a balanced approach to capacity and flight efficiency. These options were taken into account in the airspace design planning stages. Nevertheless, in order to exploit their full potential, development of appropriate Flight Data Processing Systems, enhanced ATFCM processes, the charging scheme and an enhanced ASM Concept of Operation will need to be applied.

(3) By bringing airspace design and airspace management closer together it will enhance the effectiveness of the overall ATM system. The target should be a structure that allows airspace users to fly their preferred routes and profiles, ANSPs to select the most efficient airspace organisation and ATFCM services to manage overall capacity at its optimum.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 37

EUROCONTROL Network Management Directorate

5.3 Military Requirements

(1) To enable the military forces to carry out many of their tasks, airspace of appropriate size and convenient location needs to be readily available. New tasks and scenarios and a more varied operational repertoire are likely to require fewer but larger airspace training areas with more intensive activity at all flight levels. Airspace design processes should take into full account the need to conduct military operations and exercises ideally in close vicinity to the respective airbases.

(2) Similar to the development of multiple route options within the ATS Route Network, there is also an equivalent military requirement to develop and implement a set of pre-defined multiple airspace options for temporary use, based on close and flexible co-ordination of the use of the airspace. Nevertheless, military operations and training needs have to be safeguarded to ensure unimpaired, safe and efficient performance.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 38

EUROCONTROL Network Management Directorate

6 Traffic Demand Evolution and Assessment

6.1 General

(1) This section will assess1 the traffic demand changes between the start of implementation of ARN Version 6 and the start of implementation of ERNIP Part 2 - ARN Version 2020 - 2024. Significant changes of the traffic patterns could be noted between 2008 and 2019 as a result of the economic downturn. The most impacted areas are located in Western Europe, while traffic in Southern and South Eastern Europe continued to increase.

6.2 Traffic Demand Variation - Comparison 2008/2019

(1) The assessment was made for a busy week 25 in 2019 (17th - 23rd June 2018) during which lower level of delays were recorded. Comparing the variation in traffic demand between 2008 and 2019 (see Figure 1 below), it can be seen that short hall traffic in the Northern, Central and southern part of Europe recorded a traffic decrease, predominantly in Germany, Italy, Scandinavia, Spain and UK. A continued, significant traffic growth is recorded in the Southern and South Eastern part of Europe, predominantly on the South-East Axis and in Turkey but as well on the South-West and North-South Axis.

Figure 7 : Traffic demand variation 2019 vs 2008

1 The traffic analysis for specified periods is conducted with the System for Analysis and Assignment at a Macroscopic level/ SAAM tool. The data in chapter 6.8 - 6.11 are provided by the EUROCONTROL Statistics and Forecast Service/ STATFOR.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 39

EUROCONTROL Network Management Directorate

6.3 Week and Week-end disruption The assessment was made for a busy week 25 in 2019 (17th - 23rd June 2019). The European traffic distribution is similar, with the major part of the traffic concentrated in the North Western part of Europe. The high density areas are concentrating on Central Europe during week-days (see Figure 8 below) and gradually expanding to most of the European airspace and Turkey during weekend traffic (see Fig. 9 below).

Figure 8 : Week days traffic density (4 days in June 2019)

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 40

EUROCONTROL Network Management Directorate

Figure 9 : Week-end traffic density (4 week-end days in June 2019)

(1) The comparison between both (see Figure 10 below) reveals a significant difference between Northern Europe and the South/South-Eastern Europe, as well as the Southern part of UK, the Western part of France and Spain.

Figure 10 : Traffic Density Comparison Week <> Weekend

(2) The map above indicates the following:  Areas where the traffic density is greater during the week are depicted in light to dark blue; o More loaded during week days: - UK, Germany, France, Norway, Sweden, Denmark; - Barcelona - Madrid axis; - Rome - Milano axis; - Antalya - Jerusalem; - Europe - Africa axis via .

 Areas where the traffic density is greater during the week-ends are depicted in green/ yellow to red; o More loaded during week-ends: - “South West Axis”; - “South East Axis”; - Moscow - Southern Europe; - Mediterranean area.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 41

EUROCONTROL Network Management Directorate

6.4 Distribution and Evolution - Short Haul and Medium/Long Haul

(1) The assessment was made for the period 1st July 2007 - 30th June 2008 and 1st July 2018 - 30th June 2019. The short-haul traffic pattern (distances up to 400 NM – see Figure 11 below) shows a decrease of domestic and business traffic for short- haul flights in most of the European airspace, particularly in UK and Germany, in Spain - mainly for the city pair Barcelona-Madrid and in Northern Italy - especially the city pair Milano - Rome. Compared to 2008, a higher density of traffic is noted predominantly in Turkey and the West Jordan as well as along the Portuguese coast, the Riga - Tallinn axis and Aberdeen - Shetland Islands axis.

Figure 11 : Short-Haul Flights (<400 NM)

(2) The medium to long-haul traffic pattern (flight distances over 400 NM – see see Figure 12 below) shows that the traffic further increases in the whole ECAC area and adjacent non ECAC area, significantly on the South-East Axis, South-West Axis, North-South Axis, East-West Axis, parts of the Mediterranean area and a significant increase in Turkey, particularly for Istanbul airport.

Figure 12 : Medium Haul Flights (>400 NM)

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 42

EUROCONTROL Network Management Directorate

6.5 Vertical Distribution (Evolving and Cruising Traffic)

(1) The assessment of the traffic was made for a busy Friday (21st June 2018). The concentration of climbing/descending traffic (see Error! Reference source not f ound. below) is high in the core area where many of the European airports are closely located and around other busy airports in Europe. The areas of evolving traffic are expanding, indicating a continuous increase of traffic complexity across Europe.

(2) Figure 13 : Areas of High Density Evolving Traffic

(3) The distribution of Cruising Traffic (see Error! Reference source not found. below) i s more evenly distributed and increases are noted on the South East - North West axis.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 43

EUROCONTROL Network Management Directorate

Figure 14 : Areas of High Density Cruising Traffic

6.6 Flight Level Distribution

(1) With the implementation of RVSM combined with the performance of new generation aircraft, the vertical distribution of traffic has moved up significantly (FL360/FL410 instead of FL330/FL360) with the most popular flight levels at FL370/FL380. Higher traffic levels at FL180/FL190 and FL230/FL240 could also be noted.

Figure 15 : Flight Level Distribution in Europe 2008 / 2019

6.7 Airport Traffic Increase

(1) The assessment was made for the period 1st July 2007 - 30th June 2008 and 1st July 2018 - 30th June 2019. Error! Reference source not found. below indicates that w ith the exception of airports in Belgium, the Canaries, Latvia, the Mediterranean area, Middle East, Republic of Moldova, North Africa, Norway, Portugal, Romania, Russian Federation, Turkey, Ukraine and some low cost operators airports, all the

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 44

EUROCONTROL Network Management Directorate

other airports in Europe recorded a significant traffic decrease, the largest was accounted to the UK.

Figure 16 : Traffic Increase/Decrease for the 200 Busiest European Airports

6.8 Top 50 Airports

(1) The table below indicates the Top 50 European airports in terms of movements for the period 1st July 2018 - 30th June 2019. Rank Airport Movements % of Total 1 FRANKFURT MAIN 517.359 2,32% 2 SCHIPHOL AMSTERDAM 511.322 2,29% 3 PARIS CH DE GAULLE 499.665 2,24% 4 LONDON/HEATHROW 479.673 2,15% 5 MADRID BARAJAS 418.688 1,87% 6 MUENCHEN 2 416.049 1,86% 7 ISTANBUL-ATATURK 351.870 1,58% 8 BARCELONA 341.163 1,53% 9 ROME FIUMICINO 312.711 1,40% 10 LONDON/GATWICK 287.051 1,28% 11 ZURICH 273.124 1,22% 12 WIEN SCHWECHAT 272.975 1,22% 13 COPENHAGEN KASTRUP 265.344 1,19% 14 OSLO/GARDERMOEN 254.803 1,14% 15 STOCKHOLM-ARLANDA 238.430 1,07% 16 DUBLIN 236.745 1,06% 17 PARIS ORLY 232.204 1,04% 18 BRUSSELS NATIONAL 228.548 1,02% 19 ISTANBUL/SABIHA 227.400 1,02% 20 DUESSELDORF 227.189 1,02% 21 PALMA DE MALLORCA 222.860 1,00% 22 LISBOA 219.407 0,98% 23 ATHINAI E. VENIZELOS 218.008 0,98% 24 MILANO MALPENSA 203.709 0,91% 25 MANCHESTER 202.675 0,91% 26 LONDON/STANSTED 202.112 0,90% 27 TEGEL-BERLIN 198.246 0,89%

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 45

EUROCONTROL Network Management Directorate

28 HELSINKI-VANTAA 194.772 0,87% 29 ANTALYA 193.326 0,87% 30 WARSZAWA/OKECIE 192.157 0,86% 31 GENEVE COINTRIN 180.073 0,81% 32 MOSKVA/SHEREMETYEVO 165.377 0,74% 33 TEL AVIV/BEN GURION 158.777 0,71% 34 HAMBURG 151.174 0,68% 35 PRAHA RUZYNE 150.677 0,67% 36 NICE 145.102 0,65% 37 KOELN-BONN 141.752 0,63% 38 MALAGA 140.640 0,63% 39 LONDON/LUTON 138.494 0,62% 40 STUTTGART 131.701 0,59% 41 EDINBURGH 131.324 0,59% 42 LAS PALMAS 127.159 0,57% 43 OTOPENI-INTL. 123.621 0,55% 44 FERIHEGY-BUDAPEST 117.758 0,53% 45 LYON SATOLAS 116.744 0,52% 46 MILANO LINATE 113.789 0,51% 47 BIRMINGHAM 109.824 0,49% 48 DUBAI 103.872 0,46% 49 ISTANBUL/NEW AIRPORT 103.223 0,46% 50 KIEV - BORISPOL 103.089 0,46% Table 3 : Top 50 Airports

6.9 Busiest City Pairs

(1) The following two tables show the Top 50 busiest city pairs flown in Europe for the periods July 2007 - June 2008 and July 2018 - June 2019.

(2) The table below shows the Top 50 busiest city pairs flown in Europe for the period 1st July 2007 - 30th June 2008. Rank Airport 1 Airport 2 Movements % of Total 1 MADRID BARAJAS BARCELONA 44,913 0.4% 2 ROME FIUMICINO MILANO LINATE 27,542 0.3% 3 ISTANBUL-ATATURK IZMIR-ADNAN-MENDERES 19,723 0.2% 4 PALMA DE MALLORCA BARCELONA 19,105 0.2% 5 TOULOUSE BLAGNAC PARIS ORLY 18,905 0.2% 6 BERGEN/FLESLAND OSLO/GARDERMOEN 18,754 0.2% 7 GUERNSEY JERSEY 18,606 0.2% 8 TRONDHEIM/VAERNES OSLO/GARDERMOEN 17,705 0.2% 9 LONDON/HEATHROW SCHIPHOL AMSTERDAM 17,199 0.2% 10 NICE PARIS ORLY 17,123 0.2% 11 HAMBURG MUENCHEN 2 16,805 0.2% 12 MADRID BARAJAS PALMA DE MALLORCA 16,248 0.2% 13 MAKEDONIA ATHINAI E. VENIZELOS 15,752 0.2% 14 DUESSELDORF MUENCHEN 2 15,716 0.2% 15 STAVANGER/SOLA OSLO/GARDERMOEN 15,548 0.1% 16 KOELN-BONN MUENCHEN 2 15,226 0.1% 17 CATANIA FONTANAROSSA ROME FIUMICINO 15,188 0.1% 18 MADRID BARAJAS VALENCIA 15,008 0.1% 19 MUENCHEN 2 TEGEL-BERLIN 14,780 0.1% 20 LONDON/HEATHROW PARIS CH DE GAULLE 14,649 0.1% 21 ISTANBUL-ATATURK ANTALYA 14,628 0.1% 22 ISTANBUL-ATATURK ANKARA-ESENBOGA 14,515 0.1% 23 FRANKFURT MAIN PARIS CH DE GAULLE 14,438 0.1% 24 LONDON/HEATHROW DUBLIN 14,395 0.1% 25 FUERTEVENTURA LAS PALMAS 14,124 0.1%

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 46

EUROCONTROL Network Management Directorate

26 COPENHAGEN KASTRUP OSLO/GARDERMOEN 14,033 0.1% 27 LAS PALMAS TENERIFE NORTE 14,011 0.1% 28 LONDON/HEATHROW NEW YORK 13,705 0.1% 29 LAS PALMAS ARRECIFE LANZAROTE 13,591 0.1% 30 LA PALMA TENERIFE NORTE 13,496 0.1% 31 PALERMO PUNTA RAISI ROME FIUMICINO 13,138 0.1% 32 LAS PALMAS MADRID BARAJAS 13,080 0.1% 33 PARIS CH DE GAULLE ROME FIUMICINO 12,663 0.1% 34 LONDON/HEATHROW EDINBURGH 12,656 0.1% 35 MADRID BARAJAS PARIS CH DE GAULLE 12,562 0.1% 36 KOELN-BONN TEGEL-BERLIN 12,542 0.1% 37 COPENHAGEN KASTRUP STOCKHOLM-ARLANDA 12,492 0.1% 38 FRANKFURT MAIN TEGEL-BERLIN 12,482 0.1% 39 MADRID BARAJAS MALAGA 12,373 0.1% 40 FRANKFURT MAIN LONDON/HEATHROW 12,341 0.1% 41 HELSINKI-VANTAA STOCKHOLM-ARLANDA 11,879 0.1% 42 MADRID BARAJAS LISBOA 11,831 0.1% 43 COPENHAGEN KASTRUP AALBORG 11,690 0.1% 44 LONDON/HEATHROW GLASGOW 11,592 0.1% 45 DEN HELDER/DE KOOY UNKNOWN 11,427 0.1% 46 STUTTGART TEGEL-BERLIN 11,401 0.1% 47 MARSEILLE PROVENCE PARIS ORLY 11,392 0.1% 48 ATHINAI E. VENIZELOS NIKOS/KAZANTZAKIS 11,272 0.1% 49 SCHIPHOL AMSTERDAM PARIS CH DE GAULLE 11,101 0.1% 50 MUENCHEN 2 PARIS CH DE GAULLE 10,941 0.1% Table 4 : Busiest City Pairs 2007 - 2008

(3) The table below shows the Top 50 busiest city pairs/CPs flown in Europe for the period 1st July 2018 - 30th June 2019.

Rank AP1 AP2 Movements % of Total 1 LAS PALMAS TENERIFE NORTE 19.671 0,18% 2 TRONDHEIM/VAERNES OSLO/GARDERMOEN 18.113 0,16% 3 ISTANBUL/SABIHA IZMIR-ADNAN-MENDERES 17.805 0,16% 4 ISTANBUL/SABIHA ANTALYA 17.391 0,16% 5 MADRID BARAJAS BARCELONA 17.373 0,16% 6 FRANKFURT MAIN TEGEL-BERLIN 17.208 0,15% 7 ISTANBUL/SABIHA ANKARA-ESENBOGA 16.873 0,15% 8 MUENCHEN 2 TEGEL-BERLIN 16.708 0,15% 9 TOULOUSE BLAGNAC PARIS ORLY 16.652 0,15% 10 BERGEN/FLESLAND OSLO/GARDERMOEN 16.594 0,15% 11 PALMA DE MALLORCA BARCELONA 16.217 0,15% 12 LAS PALMAS ARRECIFE LANZAROTE 16.015 0,14% 13 LA PALMA TENERIFE NORTE 15.791 0,14% 14 STAVANGER/SOLA OSLO/GARDERMOEN 14.984 0,13% 15 MADRID BARAJAS PALMA DE MALLORCA 14.762 0,13% 16 HAMBURG MUENCHEN 2 14.370 0,13% 17 NICE PARIS ORLY 14.288 0,13% 18 LONDON/HEATHROW NEW YORK 14.155 0,13% 19 DUESSELDORF MUENCHEN 2 13.981 0,13% 20 CATANIA FONTANAROSSA ROME FIUMICINO 13.773 0,12% 21 LONDON/HEATHROW DUBLIN 13.757 0,12% 22 ISTANBUL-ATATURK IZMIR-ADNAN-MENDERES 13.656 0,12% 23 COPENHAGEN KASTRUP OSLO/GARDERMOEN 13.607 0,12% 24 FUERTEVENTURA LAS PALMAS 13.543 0,12% 25 PORTO LISBOA 13.534 0,12% 26 ROME FIUMICINO MILANO LINATE 13.334 0,12% 27 LONDON/HEATHROW SCHIPHOL AMSTERDAM 13.287 0,12%

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 47

EUROCONTROL Network Management Directorate

28 OSLO/GARDERMOEN STOCKHOLM-ARLANDA 13.146 0,12% 29 COPENHAGEN KASTRUP STOCKHOLM-ARLANDA 12.965 0,12% 30 HELSINKI-VANTAA STOCKHOLM-ARLANDA 12.915 0,12% 31 FRANKFURT MAIN LONDON/HEATHROW 12.798 0,11% 32 MADRID BARAJAS LISBOA 12.604 0,11% 33 KOELN-BONN TEGEL-BERLIN 11.943 0,11% 34 STUTTGART TEGEL-BERLIN 11.934 0,11% 35 ISTANBUL-ATATURK ANKARA-ESENBOGA 11.821 0,11% 36 SANTORINI ATHINAI E. VENIZELOS 11.497 0,10% 37 MAKEDONIA ATHINAI E. VENIZELOS 11.415 0,10% 38 KOELN-BONN MUENCHEN 2 11.267 0,10% 39 DUESSELDORF TEGEL-BERLIN 11.228 0,10% 40 FRANKFURT MAIN HAMBURG 11.061 0,10% 41 PALERMO PUNTA RAISI ROME FIUMICINO 11.050 0,10% 42 PALMA DE MALLORCA IBIZA 10.857 0,10% 43 FRANKFURT MAIN MUENCHEN 2 10.673 0,10% 44 TEGEL-BERLIN ZURICH 10.609 0,09% 45 MUENCHEN 2 LONDON/HEATHROW 10.266 0,09% 46 LONDON/GATWICK BARCELONA 10.202 0,09% 47 TROMSO/LANGNES OSLO/GARDERMOEN 10.097 0,09% 48 LAS PALMAS MADRID BARAJAS 10.010 0,09% 49 ISTANBUL-ATATURK ANTALYA 10.005 0,09% 50 LONDON/HEATHROW EDINBURGH 9.943 0,09% Table 5 : Busiest City Pairs 2018 - 2019

6.10 Airspace Users The table below indicates the Top 50 aircraft operators (AO) using the European airspace between 1st July 2018 - 30th June 2019.

% of Rank Operator Movements Total 1 RYANAIR 783.475 7,01% 2 DEUTSCHE LUFTHANSA, A.G. 541.668 4,85% 3 TURK HAVA YOLLARI (TURKISH AIRLINES CO.) 489.092 4,38% 4 EASYJET AIRLINES CO. LTD 475.456 4,25% 5 AIR FRANCE 325.538 2,91% 6 SCANDINAVIAN AIRLINES 297.635 2,66% 7 BRITISH AIRWAYS 256.591 2,30% 8 KLM ROYAL DUTCH AIRLINES 249.537 2,23% 9 EUROWINGS AG, NURNBERG 243.246 2,18% 10 VUELING AIRLINES 217.110 1,94% 11 ALITALIA -LINEE AEREE ITALIANE, S.P.A. 195.990 1,75% 12 WIZZ AIR HUNGARY LTD 190.061 1,70% 13 PEGASUS HAVA TASIMACILIGI A.S. (PEGASUS) 171.619 1,54% 14 SWISS INTERNATIONAL AIR LINES LTD 149.292 1,34% 15 BRITISH EUROPEAN 143.764 1,29% 16 Unknown OP 140.075 1,25% 17 AUSTRIAN AIRLINES (AUA) 138.304 1,24% 18 TRANSPORTES AEREOS PORTUGUESES, E.P. 134.939 1,21% 19 LOT - POLSKIE LINIE LOTNICZE 131.369 1,18% 20 FINNAIR O/Y 129.466 1,16% 21 NORWEGIAN AIR SHUTTLE AS 129.426 1,16% 22 AEROFLOT - RUSSIAN INTERNATIONAL AIRLINES 121.790 1,09% 23 WIDEROE'S FLYVESELSKAP A/S 115.594 1,03% 24 AIR EUROPA 102.381 0,92% 25 NORWEGIAN AIR INTERNATIONAL 100.109 0,90%

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 48

EUROCONTROL Network Management Directorate

26 IBERIA - LINEAS AEREAS DE ESPANA, S.A. 94.539 0,85% 27 QATAR AIRWAYS COMPANY 89.309 0,80% 28 BRUSSELS AIRLINES 81.904 0,73% 29 AER LINGUS TEORANTA 80.286 0,72% 30 AIR NOSTRUM LINEAS AEREAS DEL MEDITERRANEO, S.A. 79.476 0,71% 31 JET2.COM 78.569 0,70% 32 HOP! 74.508 0,67% 33 EASYJET EUROPE AIRLINE GMBH 74.315 0,66% 34 ROYAL AIR MAROC - COMPAGNIE NATIONALE DE TRANSPORTS AERIENS 72.024 0,64% 35 EMIRATES 71.766 0,64% 36 Unknown OP 69.048 0,62% 37 EUROPEAN AIR TRANSPORT 64.422 0,58% 38 THOMSON AIRWAYS LTD 62.871 0,56% 39 UKRAINE INTERNATIONAL AIRLINES 61.602 0,55% 40 OLYMPIC AIRWAYS S.A. 61.214 0,55% 41 AIR BALTIC CORPORATION SIA 58.717 0,53% 42 TRANSAVIA HOLLAND B.V. 58.468 0,52% 43 NULL USER_CODE FOR ICAO_STATE <> 58.142 0,52% 44 VOLOTEA 57.127 0,51% 45 EASY JET SWITZERLAND SA 55.204 0,49% 46 AEGEAN AVIATION 52.217 0,47% 47 GUNES EKSPRES HAVACILIK A.S. (SUNEXPRESS) 52.216 0,47% 48 NETJETS, TRANSPORTES AEREOS S.A. 48.926 0,44% 49 DELTA AIR LINES, INC. 47.846 0,43% 50 UNITED AIR LINES INC. 47.761 0,43% Table 6 : Top 50 Aircraft Operators

6.11 Aircraft Types

(1) The table below indicates the Top 50 aircraft types using the European airspace between 1st July 2018 - 30th June 2019. Rank Aircraft type Movements % of Total 1 B738 2.143.126 19,18% 2 A320 1.919.996 17,18% 3 A319 896.408 8,02% 4 A321 687.862 6,15% 5 DH8D 322.425 2,88% 6 E190 282.799 2,53% 7 B77W 193.064 1,73% 8 A20N 186.433 1,67% 9 CRJ9 180.545 1,62% 10 B737 172.282 1,54% 11 A332 167.699 1,50% 12 AT75 161.951 1,45% 13 A333 160.040 1,43% 14 AT76 157.637 1,41% 15 E195 128.238 1,15% 16 B763 105.356 0,94% 17 B752 100.504 0,90% 18 B772 100.018 0,89% 19 B789 97.895 0,88% 20 CRJX 93.939 0,84% 21 B788 85.404 0,76% 22 B734 85.400 0,76% 23 B744 81.121 0,73% 24 E75S 75.674 0,68% 25 Unknown AC 69.078 0,62%

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 49

EUROCONTROL Network Management Directorate

26 DH8A 67.270 0,60% 27 A388 65.793 0,59% 28 B733 62.583 0,56% 29 E170 56.466 0,51% 30 A359 56.194 0,50% 31 C56X 55.581 0,50% 32 B77L 52.925 0,47% 33 BE20 52.502 0,47% 34 E145 51.602 0,46% 35 BCS3 51.293 0,46% 36 AT72 51.256 0,46% 37 S92 48.220 0,43% 38 B739 47.284 0,42% 39 A318 45.683 0,41% 40 E75L 43.078 0,39% 41 AT45 42.491 0,38% 42 SF34 42.442 0,38% 43 B38M 40.571 0,36% 44 DA42 40.429 0,36% 45 PC12 39.081 0,35% 46 B735 32.984 0,30% 47 A306 31.699 0,28% 48 A343 31.484 0,28% 49 B712 31.432 0,28% 50 GLEX 30.590 0,27% Table 7 : Top 50 Aircraft Types

7 MAIN PROJECTS INCLUDED IN ERNIP PART 2 - ARN VERSION 2020 - 2024

(1) The ERNIP Part 2 - ARN Version 2020 - 2024 is an integral package of airspace design and utilisation solutions. It was built on the development of new concepts that were transposed in several layers of airspace developments. These layers are properly interconnected at network level to ensure an appropriate and cohesive airspace utilisation:  between various concepts;  over a 24-hours period, and  over various period of the week or of the year.

(2) The further development of the concept of airspace configurations at network level will ensure an enhanced utilisation of these various layers at local, sub-regional, FAB and network levels.

(3) The main direction taken by the ERNIP Part 2 - ARN Version 2020 - 2024 is towards the implementation of Free Route Airspace. The latest situation of the European route network structure is available and updated at each AIRAC cycle through the publication of EUROCONTROL Regional Charts that could be found at the following link: https://www.eurocontrol.int/carto

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 50

EUROCONTROL Network Management Directorate

7.1 Free Route Airspace

(1) The following maps are showing the layer containing the evolution of Free Route Airspace initiatives already in place or planned for implementation year by year, that are currently included in the ERNIP Part 2 - ARN Version 2020 - 2024. This layer is supported by a network operational concept for Free Route Airspace Operations.

Figure 17 : Free Route Airspace Chart - End 2020

The map below shows the Free Route Airspace implementation plans proposed until end of 2021.

Figure 18 : Free Route Airspace Chart - End 2021

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 51

EUROCONTROL Network Management Directorate

(2) The map below shows the Free Route Airspace implementation plans proposed until end of 2022.

Figure 19 : Free Route Airspace Chart - End 2022

(3) The map below shows the Free Route Airspace implementation plans proposed until end of 2023.

Figure 20 : Free Route Airspace Chart - End 2023

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 52

EUROCONTROL Network Management Directorate

(4) The map below shows the Free Route Airspace implementation plans proposed until end of 2024.

Figure 21 : Free Route Airspace Chart - End 2024

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 53

EUROCONTROL Network Management Directorate

Annexes

A. Reference Documents

(1) In the Development and Implementation of ARN Version 2020 - 2024 the following documents, inter alia, are used for reference and guidelines:  Single European Sky II Legislation  EUROCONTROL Airspace Strategy for the ECAC States  ERNIP Part 1  ERNIP Part 3  ERNIP Part 4  Free Route Airspace Design - Guidelines  ICAO Standards, Recommended Practices and Procedures

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 54

EUROCONTROL Network Management Directorate

B. Acronyms and Abbreviations

ACC Area Control Centre AIP Aeronautical Information Publication AIRAC Aeronautical Information Regulation and Control ANSP Airspace Navigation Service Provider AO Aircraft Operator AoR Area of Responsibility ARN ATS Route Network ARR Arrival ASM Airspace Management ASMSG Airspace Management Sub-Group ATC , Air Traffic Control Domain ATFCM Air Traffic Flow and Capacity Management ATFM Air Traffic Flow Management ATM Air Traffic Management ATS Air Traffic Services AUP Airspace Use Plan CANSO Civil Air Navigation Services Organisation CBA Cross-border Area CDA Continuous Descent Approach CDM Cooperative Decision Making CDR Conditional Route CFSP Computer Flight planning Service Provider CIAM Central flow management unit Interface for Airspace Managers CTA Control Area CTR Control Zone D Danger Area DCT Direct DEP Departure e-AMI Electronic ASM Information EANP European Air Navigation Plan ECAC European Civil Aviation Conference ERND European Route Network Design ERNIP European Route Network Improvement Plan ETFMS Enhanced Tactical Flow Management System EU European Union EUROCONTROL European Organisation for the Safety of Air Navigation FAB Functional Airspace Block FIR Flight Information Region FL Flight Level FPL Flight Plan FRA Free Route Airspace FUA Flexible Use of Airspace GAT General Air Traffic IACA International Air Carrier Association IATA International Air Transport Association

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 55

EUROCONTROL Network Management Directorate

ICAO International Civil Aviation Organisation IFPS Initial Flight planning Processing System IFR Instrument Flight Rules IR Implementing Rule kg kilogram KEA Key Performance Environment Indicator based on actual trajectory KEP Key Performance Environment Indicator based on last filed flight planKPI Key Performance Indicators LoA Letter of Agreement min Minute/s NEST Network Strategic Tool NETOPS Network Operations Team NM Network Manager / Nautical Mile NOP Network Operations Plan NPZ No Planning Zone NSP Network Strategy Plan OAT Operational Air Traffic P Prohibited Area PBN Performance Based Navigation PC Provisional Council PRISMIL Pan-European Repository of Information Supporting Military Key Performance Indicators R Restricted Area RAD Route Availability Document RNAV Area Navigation RNDSG Route Network Development Sub-Group RP Reference Period RVSM Reduced Vertical Separation Minimum SAAM System for traffic Assignment and Analysis at Macroscopic level SES Single European Sky SID Standard Instrumental Departure STAR Standard Arrival Route TAS Terminal Airspace System TMA Terminal Control Area TRA Temporary Reserved Area TSA Temporary Segregated Area UAC Upper Area Control Centre UIR Upper Flight Information region UTA Upper Control Area VFR Visual Flight Rules WE Weekend

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 56

EUROCONTROL Network Management Directorate

C. Summary of ERNIP PART 2 - ARN VERSION 2020 - 2024 Proposals

(1) This Annex provides an overview of the major improvement projects implemented or planned for implementation Winter 2019/20 until 2024:

(2) Implemented Projects until (including on) 23rd April 2020  Armenia / Georgia - FRASC Free Route Airspace South Caucasus.  Belgium - Single CDR Category (SCC) - Belgium - Remove 'U' Prefix of ATS routes in Belgium.  Belgium / Germany / Maastricht UAC / Netherlands - FRAM2 - Phase 3.  Bosnia Herzegovina - BH ATM, Phase 2.  Bulgaria / Hungary / Romania - SEE FRA H24 Cross-Border Free Route Airspace within Hungary, Romania and Bulgaria - Phase 1.  Bulgaria / Hungary / Romania / Slovakia - SEEN FRA Phase 3.  Croatia - Central sector Zagreb Phase 2b.  Cyprus / Egypt / Israel - Nicosia ACC - Tel Aviv ACC - Cairo ACC Re-organisation.  Czech Republic - Single CDR Category (SCC) - Czech Republic.  Denmark / Germany / Maastricht UAC / Netherland / Sweden - Cross-border FRA Maastricht UAC, DK/SW FAB.  Estonia - Single CDR Category (SCC) - Estonia.  France - Single CDR Category (SCC) - France - Phase 1. - Single CDR Category (SCC) - France - Phase 2. - Brest ACC re-organisation - Step 4.  Germany - FRA Germany - Step 2a bis (DCTs). - Langen ACC Sector Group 5 re-design - Step 2.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 57

EUROCONTROL Network Management Directorate

- Single CDR Category (SCC) - Germany. - Remove 'U' Prefix of ATS routes in Germany. - Thüringen sector re-design - Munich ACC.  Greece - Hellas FRA - Free Route Airspace Greece - Phase 4a.  Hungary - New Budapest TMA.  Morocco - Free Route Airspace Morocco (MORFRA), Phase 1.  Morocco / Portugal / Spain - Lisboa / Casablanca / Canarias Axis Phase 1a. - Lisboa / Casablanca / Canarias Axis Phase 1b.  Netherland - Remove 'U' Prefix of ATS routes in Netherlands.  Poland - TMA re-organisation Warszawa FIR - Step 1.  Slovakia - Bratislava ACC re-sectorisation - Step 1.  Sweden - New Scandinavian Mountains Airport - ESKS.  Switzerland - Single CDR Category (SCC) - Switzerland - Phase 2. - Remove 'U' Prefix of ATS routes in Switzerland.  UK - Swanwick Airspace Improvement Programme (SAIP) Airspace Deployment - 5. - Farnborough Airspace Re-design Project. - Single CDR Category (SCC) - UK Step 1.  Ukraine - Single CDR Category (SCC) - Ukraine.

(3) 2020: Projects planned or proposed for implementation  Albania / Austria / Croatia / Slovenia / Serbia / Montenegro / Bosnia & Herzegovina - SECSI FRA - FRA ALB Night cross-border FRA.  France - Single CDR Category (SCC) - France - Phase 3.  Germany

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 58

EUROCONTROL Network Management Directorate

- PBN Implementation at EDDH, EDHI, EDHL, EDHK. - Berlin Brandenburg International (BER) airport.  Georgia - Tbilisi TMA.  Greece - Single CDR Category (SCC) Greece.  Italy - Single CDR Category (SCC) - Italy.  Netherland / Belgium / MUAC UAC - Sector 3 re-design Amsterdam ACC  Portugal - Madeira TMA.  Spain - Single CDR Category (SCC) Spain - Phase 1.  Spain / Morocco - Lisboa / Casablanca / Canarias Axis, Phase 1c. - Lisboa / Casablanca / Canarias Axis Phase 1d.  Turkey - New APP Sectors Izmir TMA/ Dalaman TMA. - New Istanbul/ LTFM airport - 3rd runway - Phase 1b. - Istanbul Sabiha Gökcen/ LTFJ airport new parallel runway.  Ukraine - Airspace Structure Improvement Kyiv UIR/Dnipro FIR.

(4) 2021: Projects planned or proposed for implementation  Albania / Austria / Croatia / Slovenia / Serbia / Montenegro / Bosnia & Herzegovina - SECSI FRA - FRA ALB H24 cross-border FRA  Austria - Airspace Re-Structuring Project AoR LOVV 2021.  Bulgaria - Single CDR Category (SCC) - Bulgaria.  Czech Republic - Free Route Airspace Praha/ FRACZECH, Step 4.  France - Brest ACC re-organisation - Step 5. - Free Route Airspace Brest Atlantic - Step 1.0. - Free Route Airspace Paris - Step 1.1.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 59

EUROCONTROL Network Management Directorate

- Free Route Airspace Bordeaux - Step 1.0.  Germany - Langen ACC Sector Group 1 re-design. - Free Route Airspace Germany - Step 2c.  Greece - Airspace re-classification Hellas UIR. - Extension of Hellas UIR Upper limit. - Greek Airspace reorganization - Phase 2. - Greek Airspace reorganization - Phase 3.  Hungary - Budapest TMA and ACC re-organisation.  Ireland - New runway Dublin Airport (EIDW).  Latvia / Lithuania / Estonia - Point Merge Implementation Riga Airport. - JAMP 2020+ Step 1 (East sector vertical split).  Lithuania - Lithuania airspace reconfiguration Project.  Malta - Free Route Airspace Malta - Phase 3c. - INTRAC Phase 2.  Morocco - Free Route Airspace Morocco (MORFRA), Phase 2. - Free Route Airspace Morocco (MORFRA), Phase 3.  Poland - TMA re-organisation Warszawa FIR - Step 2. - ACC Warszawa sector configuration re-organisation (3-layer division) - Step 1. - Krakow airport new runway.  Portugal - Lisboa TMA Point Merge System. - Free Route Airspace Santa Maria FIR - Phase 2.  Romania - Bucuresti ACC re-organisation. - Single CDR Category (SCC) - Romania Step 1. - Single CDR Category (SCC) - Romania Step 2.  Spain

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 60

EUROCONTROL Network Management Directorate

- BAS sector split - Barcelona ACC. - Free Route Airspace Spain - ESFRA Phase 1. - Free Route Airspace Spain - ESFRA Phase 2. - Split ZGZ / TER upper sector.  Switzerland - Free Route Airspace Switzerland.  Turkey - Free Route Airspace Turkey - FRATURK - Phase 1.  UK - Single CDR Category (SCC) - UK Step 2.  Ukraine - FRAU Free Route Airspace Ukraine, Step 1 (Sc 1b) - Phase 3.

(5) 2022: Projects planned or proposed for implementation  Cyprus - Free Route Airspace Cyprus - FRANIC Phase 1.  Czech Republic - New ATM system Praha ACC.  Denmark / Sweden - Copenhagen SIDs/STARs re-design.  Estonia / Finland - FINEST - Cross-border sectorisation.  Greece - PBN SIDs/ STARs Athens TMA.  Lithuania / Poland - Baltic FAB cross-border Free Route Airspace.  Norway - Northern Norway TMAs airspace re-organization.  Poland - ACC Warszawa sector configuration re-organisation (3-layer division) - Step 2. - AMC Poland - FMP Warszawa coordination procedures. - Expansion Radom/ EPRA airport.  Portugal - Removal ‘U’ prefix Lisboa FIR.  Slovakia - Bratislava ACC re-sectorisation - Step 2.  Spain

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 61

EUROCONTROL Network Management Directorate

- Canarias APP sector split. - Canarias ACC ‘NE’ sector. - Barcelona TMA - Phase 2. - Malaga TMA re-design. - Palma TMA Re-organisation - Phase 3 West. - Madrid TMA - Phase 2. - Palma TMA Re-organisation - Phase 1 East. - Third layer TLU and DGU-PAU sectors.  Spain / Portugal / Morocco - Lisboa / Casablanca / Canarias Axis Phase 2.  Turkey - Free Route Airspace Turkey - FRATURK - Phase 2.  UK - Future Airspace Strategy Implementation - North. - Future Airspace Strategy Implementation - North (FASI-N). - Borealis FRA - Step 4 - Scottish Free Route Airspace; (a delay might occur/ new implementation due to COVID-19 crisis). - Borealis FRA - Step 6 (H24 FRA Swanwick ACC AoR).  Ukraine - FRAU Free Route Airspace Ukraine, Step 2 (Sc 2a).

(6) 2023: Projects planned or proposed for implementation  Austria - LOVV 2020 Airspace Re-Structuring.  Denmark / Estonia / Finland / Ireland / Island / Latvia / Lithuania / Norway / Poland / Sweden / UK - FAB DK-SE - Baltic FAB Cross Border Free Route Airspace.  France - Free Route Airspace Brest Continental West- Step 1.2. - Free Route Airspace Reims - Step 2.0. - Free Route Airspace Marseille ACC - Step 2.0. - Airspace Structure Improvement Marseille ACC.  Greece - Hellas FRA - Free Route Airspace Greece - Phase 4b.  Norway - Norway FAS (Future ATM System) - South.  Poland - Lower airspace re-organisation.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 62

EUROCONTROL Network Management Directorate

- ACC Warszawa sector configuration re-organisation (3-layer division) - Step 3.  Slovakia - SEE FRA, Phase 2 (H24 Bratislava FIR).  Spain - Canarias TMA - Phase 2a.  UK - Borealis FRA - Step 7 (H24 FRA certain sectors Prestwick ACC / Swanwick ACC).  Ukraine - FRAU Free Route Airspace Ukraine, Step 2 (Sc 2b).

(7) 2024: Projects planned or proposed for implementation  Belgium - New common ATM system in Belgian airspace.  Bulgaria - FRA based re-sectorisation Sofia ACC  Czech Republic - New sectorisation Praha FIR.  France - ELIXIR Phase 1. - ELIXIR Phase 2. - Free Route Airspace Brest Continental East- Step 1.3. - Airspace Structure Improvement Bordeaux ACC. - Paris ACC re-organisation - Phase 3.  Norway - Norway FAS (Future ATM System) - North.  Poland - ACC Warszawa sector configuration re-organisation (3-layer division) - Step 4.  Spain / France - LUMAS, Phase 2b Marseille FIR - Barcelona FIR.  UK - Borealis FRA - Step 8 (H24 FRA certain sectors Swanwick ACC). - Future Airspace Strategy Implementation - South (FASI-S).

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 63

EUROCONTROL Network Management Directorate

D. List of ERNIP PART 2 - ARN VERSION 2020 - 2024 Proposals

(1) The following pages present detailed information about each of the more than 350 improvement proposals developed within the RNDSG, which are or will be implemented as part of ERNIP Part 2 - ARN Version 2020 - 2024. The description of the proposals is based on the information available from different sources (e.g. AOs, ANSPs and EUROCONTROL). Further changes might be included in the next versions of the ERNIP Part 2 to reflect latest updates following COVID situation.

(2) The table includes:  Proposal number: A reference number to identify each proposal allowing tracing at which RNDSG it was initiated.  Description: A detailed description of the planned improvement proposal.  Objective: A brief description of the purpose of the enhancement measure.  Status: The implementation status defined as Proposed, Planned, Confirmed or Implemented.  Project Group: The Functional Airspace Block Group (FAB), Regional Focus Group (RFG), Sub- Group (SG) or any other Project Group(s) involved directly or indirectly by the proposed enhancement measure.  Project Category: The nature of the proposed enhancement measure defined through Project Categories (e.g. ATC sectors, ATS routes, CDRs, DCTs, Free Route Airspace, RAD, TMA, …).  States and Organisations: The States and/or Organisations involved directly or indirectly by the proposed enhancement measure.  Originator(s): The States, Organisations who have originated the proposal.  Comments: The conditions and/or pre-requisites which have to be met in order to implement the proposal or any other relevant comment(s).

The Annex lists all ARN Version 2020 - 2024 proposals as they stood on 02 June 2020

The latest situation of the European route network structure is available and updated at each AIRAC cycle through the publication of EUROCONTROL Regional Charts that could be found at the following link: https://www.eurocontrol.int/carto

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 64

EUROCONTROL Network Management Directorate

Proposal ID : 97.003 Status: Contributor: Comments: Project Name: RAD Restriction LS2596 Modification Implementation: State(s) and Org:  This modification became possible

Description: Implemented CHE after a trial that showed more than 90% 10 OCT 2019 FAB EC of eligible flights utilizing the CDR at 1. After a successful operational live trial in spring 2018, a partial relaxation of RAD Restriction LS2596 can be Originator(s): flight planning level without being forced to do so. 1. implemented on a permanent basis. CHE  However, unfortunately, this high rate 2. The forcing on a specific CDR (UZ662) will be stopped Project Group: for transit traffic. of CDR utilization is not observed for FAB EC other CDRs. Objective: Project Category: To de-complexify the RAD. RAD Proposal ID : 97.022 Status: Contributor: Comments: Project Name: Several ATS routes replaced by DCT in Implementation: State(s) and Org: Scope and availability of traffic flows will FIR Praha Implemented CZE remain.

Description: 10 OCT 2019 Originator(s): To realign the following existing ATS routes (new waypoint): CZE

a. L993 as VOZ– LIKSA – IVOLI; Project Category: b. Z37 as VEMUT – ETVIS – ABUDO – BUDEX; ATS Routes c. Z205 as LULAR – ABUDO – BUDEX; 2. DCTs d. To withdraw the following ATS route(s): L867, Z650, Z660; e. To change upper limit of ATS routes L617, M984, P31, T78, Z121 to FL095.

Objective: To further improve the flight planning options within FIR Praha. Proposal ID : 97.006a Status: Contributor: Comments:

Project Name: Single CDR category (SCC) - France - Implementation: State(s) and Org: Related proposals: Phase 1 Implemented FRA  97.006b 10 OCT 2019 Description: Originator(s):  97.006c To change all existing CDR Categories into a single CDR FRA 3. category. Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in France. Proposal ID : 88.046 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 1

EUROCONTROL Network Management Directorate

Project Name: 5LNC replacement by United Kingdom Implementation: State(s) and Org:  BARSU is assigned to Germany in Implemented GBR ICARD. Description: To replace existing 5LNC BARSU with new code MIFKO. 10 OCT 2019 Originator(s):  Proposal for replacement is based on "Common Criteria for replacement of 4. Objective: ICAO duplicated 5LNCs" as point is not To avoid 5LNCs duplication within the ECAC area of the EUROCONTROL reserved for United Kingdom. ICAO EUR/NAT region, to improve the aeronautical Project Category:  UK investigating - update at RNDSG information provided and be compliant with ICAO Annex 11. 5LNC 96. Proposal ID : 93.009 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to Implemented ITA take action. Description: To replace 5LNC LEMON. 10 OCT 2019 Originator(s):  This 5LNC is used worldwide for 6 significant points and the Priority State Objective: ICAO identified by ICAO to keep the code is To avoid worldwide 5LNC duplication, to improve the Project Category: 5. USA. aeronautical information provided and be compliant with 5LNC  5LNC exists for 1 significant point ICAO Annex 11. Civil/Military Airspace at/around LIBA military airport.  ITA selected in ICARD 5LNC EVUDO as a replacement to LEMON. Implementation TOctober 2019 Proposal ID : 97.016 Status: Contributor: Comments: Project Name: ATS Route Improvement Kyiv UIR/L'viv Implementation: State(s) and Org: FIR Implemented UKR

Description: 10 OCT 2019 Originator(s): To implement new bidirectional ATS route M983 TADUN – UKR 6. KOVUS (2900 M – FL660). Project Category: Objective: ATS Routes To further improve the ATS route network in Kyiv UIR/L'viv FIR. Proposal ID : 97.017 Status: Contributor: Comments: Project Name: New SIDs/STARs for Boryspil (UKBB) & Implementation: State(s) and Org: Updated composition of FRA Arrival & Zhuliany (UKKK) airports Implemented UKR Departure Connecting Routes for Boryspil

7. Description: 10 OCT 2019 Originator(s): (UKBB) & Zhuliany (UKKK) airports is To introduce new SIDs and STARs for Boryspil (UKBB) & UKR planned for implementation. Zhuliany (UKKK) airports. Project Category:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 2

EUROCONTROL Network Management Directorate

Objective: Airspace Structure To further improve airspace organisation around Boryspil TMA (UKBB) & Zhuliany (UKKK) airports. Proposal ID : 97.005 Status: Contributor: Comments: Project Name: Single CDR category (SCC) - Ukraine Implementation: State(s) and Org: Implemented UKR Description: To change all existing CDR Categories into a single CDR 10 OCT 2019 Originator(s): 8. category. UKR

Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in Ukraine. SCC Proposal ID : 91.004 / 26.008 Status: Contributor: Comments: Project Name: FRASC Free Route Airspace South Implementation: State(s) and Org:  'Double AIRAC procedure’ for AIRAC Caucasus Implemented ARM AIP AMDT publication required for 07 NOV 2019 GEO implementation (ICAO Annex 15 Description: To merge ARMFRA Phase 2 and FRAG Phase 2 into a Serial Number: Originator(s): refers). EUR/NAT 19/08-HS-ARM  ARM: ATS Route Network available. common H24 cross-border South Caucasus FRA area ARM FL195 - FL660. Circulation Letter: GEO  GEO: ATS Route Network available. EUR/NAT 19-0353.TEC of 9 EUROCONTROL  High Seas Coordination (Serial no: Objective: August 2019 Project Group: EUR/NAT 19/08-HS-ARM-GEO) 9. To further improve flight planning options and expand the local FRA areas. Approval Letter: SG BLACK ◦ Circulation letter ref: EUR/NAT 19-

EUR/NAT 19-0403.TEC of 17 0353.TEC of 9 August 2019 - Project Category: deadline on 9 September 2019 September 2019 Free Route Airspace ◦ Approval letter ref: EUR/NAT 19- 0403.TEC of 17 September 2019

Related proposals:  83.030a / 21.003a  83.030b / 21.003b  85.009a / 21.023a Proposal ID : 95.031 / 28.006 Status: Contributor: Comments: Project Name: ATS Route Improvement Azerbaijan - Implementation: State(s) and Org:  AZE: Ready to implement RASAM – Turkmenistan Implemented AZE METKA in AIRAC 07 NOV 2019.

10. Description: 07 NOV 2019 TKM  TKM: Ready to implement. Currently in UZB final approval phase. May be To implement bidirectional ATS routes: implemented by end 2019.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 3

EUROCONTROL Network Management Directorate

a. L88 RASAM - METKA; Originator(s):  UZB: Implemented DARVA-OGOLI on b. B476 METKA - BEGLI - NEBIT - DARVA - OGOLI. UZB 28 FEB 2019.

Objective: Project Group: To further improve the ATS route network at the interface SG MIDASIA

between Azerbaijan, Uzbekistan and Turkmenistan. Project Category: ATS Routes Proposal ID : 98.012 / 31.002 Status: Contributor: Comments: Project Name: ATS Route Network Improvement Baku Implementation: State(s) and Org: FIR / Tbilisi FIR Implemented AZE 07 NOV 2019 GEO Description: To change the lower limit of ATS route segment M737 DISKA Originator(s): 11. - VERCA from FL145 to FL055 or 5500 FT. GEO

Objective: Project Group: To further improve the ATS route network between Baku FIR SG BLACK

and Tbilisi FIR while optimizing the climbing profile for DEP Project Category: UGTB. ATS Routes Proposal ID : 82.033 Status: Contributor: Comments: Project Name: SEE FRA Phase 1 Implementation: State(s) and Org:  'Double AIRAC procedure’ for AIRAC

Description: Implemented BGR AIP AMDT publication required for To implement H24 Cross-Border Free Route Airspace 07 NOV 2019 ROU implementation (ICAO Annex 15 Serial Number: HUN refers). within Hungary, Romania and Bulgaria (9500FT/ FL105/ EUR/NAT 19/04-HS-BGR  HUN: ATS Route Network removed. FL175 - FL660). Originator(s):  ROU: ATS Route Network available. Objective: Circulation Letter: FAB DANUBE  BGR: ATS Route Network available. To allow more efficient flight planning. EUR/NAT 19-0381.TEC of 3 Project Group: September 2019  High Seas Coordination (Serial no: FAB DANUBE 12. Approval Letter: RFG SE EUR/NAT 19/04-HS-BGR/ROU) EUR/NAT 19-0381.TEC of 3 circulation letter ref: EUR/NAT 19-0319 Project Category: of 29 July 2019 circulated with deadline September 2019 Free Route Airspace on 29 August 2019, approval letter ref: High Seas EUR/NAT 19-0381.TEC of 3 September 2019.

Related proposals:  69.052  81.001  90.034

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 4

EUROCONTROL Network Management Directorate

 98.016  98.022 Proposal ID : 97.035 / 30.024 Status: Contributor: Comments: Project Name: ATS Route Improvement Belarus Implementation: State(s) and Org: Implemented BLR Description: To implement new ATS route segments: 07 NOV 2019 Originator(s): a. BLR 13. b. Project Group: Objective: SG BALTIC

To further improve the ATS route network while providing two Project Category: new connecting segments for Minsk arrivals. ATS Routes Proposal ID : 95.033 Status: Contributor: Comments: Project Name: NDBs replaced by 5LNC Praha FIR Implementation: State(s) and Org: Implemented CZE Description: 1. To withdraw NAVAIDs designator HLV, RAK and 07 NOV 2019 Originator(s): TBV (NDBs). CZE

2. To replace in all affected ATS routes and Project Category: SIDs/STARs the three letter designators/ NDBs with the Airspace Structure 14. following 5LNCs (same coordinates): a. HLV by 5LNC UPLAV; b. RAK by 5LNC EROKA; c. TBV by 5LNC TIBLA.

Objective: To enhance the airspace structure within Praha FIR in line with the NAV strategy. Proposal ID : 95.018b Status: Contributor: Comments: Project Name: FRA Germany - Step 2a Implementation: State(s) and Org:  It is a continuous process

Implemented DEU  The proposal is linked to phase 2b Description: 07 NOV 2019 which is pending management decision To permit additional RAD APPENDIX 4 DCTs and implement Originator(s): ATS route changes. DEU Related proposals: 15. Objective: Project Category:  87.005f To prepare the H24 Full FRA implementation - according to DCTs  87.037c PCP requirements - and improve flight efficiency within Free Route Airspace  95.018a Karlsruhe UAC/ FAB EC.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 5

EUROCONTROL Network Management Directorate

Proposal ID : 89.061 Status: Contributor: Comments: Project Name: Swanwick Airspace Improvement Implementation: State(s) and Org: Subject to CAA approval. Programme (SAIP) Airspace Deployment - 5 Implemented GBR High Seas Coordination (Serial no:

Description: 07 NOV 2019 Originator(s): EUR/NAT 19/09-HS-GBR) 1. To establish an ATS routes as follows: Serial Number: GBR Circulation letter ref: EUR/NAT 19- a. Y125 LIPGO - BERUL - RETSI - FITBO (new EUR/NAT 19/09-HS-GBR 0368.TEC of 22 August 2019 - deadline on Project Category: point)as CDR3 for EGLL arrivals; Circulation Letter: 23 September 2019 Airspace Structure Approval letter ref: EUR/NAT 19-0434.TEC b. STAR FITBO (new point) - SOPIT - WCO - BNN for EUR/NAT 19-0368.TEC of 22 ATS Routes EGLL arrivals; August 2019 of 7 October 2019. High Seas c. new RNAV1 ATS Routes N91 (arrivals) and N92 Approval Letter: (departures) for EGBB traffic routeing to/from the EUR/NAT 19-0434.TEC of 7 south-west; 16. October 2019 2. Class C Controlled Airspace to enable traffic arriving EGLL to descend blow FL195 before current controlled airspace boundary for TC Midlands and to protect routes N91 and N92. 3. To extend P155 east from HON to MORAG for Eastbound traffic FL370+; 4. To remove U prefix from a number of routes in the West End Sector Group.

Objective: To provide an offload route for EGLL arrivals, ATS routes for traffic into and out of EGBB and an additional route for transiting the London FIR above FL350. Proposal ID : 97.002 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: not included to be re-lettered:

Description: Implemented GBR  GROVE 1C will become WELIN 1B; 1. To remove the en-route dependency from BIG DVOR 07 NOV 2019 FRA  WILLO 3B will become KIDLI 1G; Serial Number: BEL High Seas Coordination (Serial no: will result in the BIG Hold becoming RNAV'd and some EUR/NAT 19/09-HS-GBR EUR/NAT 19/09-HS-GBR) STARs into those holds being made RNAV5 and Originator(s): 17. designated by their start fix - other STARs will also be Circulation Letter: GBR Circulation letter ref: EUR/NAT 19- 0368.TEC of 22 August 2019 - deadline on amended as follows: EUR/NAT 19-0368.TEC of 22 Project Category: 23 September 2019 a. GODLU 1X will become BEDEK 1C; August 2019 ATS Routes Approval letter ref: EUR/NAT 19-0434.TEC b. GODLU 1C will become KONAN 1C; Approval Letter: High Seas of 7 October 2019. c. GODLU 1D will become SOVAT 1C; EUR/NAT 19-0434.TEC of 7 d. GODLU 1F will become NEVIL 1C; October 2019 e. GODLU 1J will become AVANT 1C;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 6

EUROCONTROL Network Management Directorate

f. WILLO 2H will become BEDEK 1G; g. BIG 4B will become ALESO 1H; h. BIG 3D will become LAM 1X; i. BIG 1E will become TANET 1Z; j. TIMBA 2B will become NEVIL 1G; k. TIMBA 4G will become KUNAV 1G; l. ASTRA 1F, ASTRA 2H, WILLO 1F, WEALD 4B, WEALD 3D, WEALD 1E are all removed. 2. To remove U designator prefix from ATS routes UL6, UL10, UL15, UL607, UL613, UM140, UQ70, UT421, UY311 and UY312. 3. To re-designate ATS route M140 MID - VABIK as L18.

Objective: To remove the en-route dependency on the BIG DVOR. Proposal ID : 90.024 Status: Contributor: Comments: Project Name: Implementation of PBN/SBAS procedures Implementation: State(s) and Org: in ATHINAI FIR. Implemented GRC

Description: 07 NOV 2019 Originator(s): To implement PBN/SBAS procedures for Kos (LGKO) GRC

18. aerodrome. Project Group: Objective: RFG SE

To further improve the airspace structure within Athinai FIR. Project Category: Airspace Structure PBN Proposal ID : 84.043 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  URENA is with double reservation in

Description: Implemented ITA ICARD for Russian Federation and 07 NOV 2019 RUS Italy. To replace existing 5LNC URENA by VURKE. Originator(s):  Proposal for replacement by Italy is 19. Objective: EUROCONTROL based on “Common criteria for To avoid 5LNCs duplication within the ECAC area of the replacement of duplicated 5LNCs” as ICAO EUR/NAT region, to improve the aeronautical ICAO point is used on single ATS route. information provided and be compliant with ICAO Annex 11. Project Category: 5LNC Proposal ID : 92.032 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 7

EUROCONTROL Network Management Directorate

Project Name: ATS Route Improvement Amsterdam FIR Implementation: State(s) and Org: T602, T603, T604, T606, T607. Implemented NLD Description: To implement RNAV Terminal Connecting Routes T602 - 07 NOV 2019 Originator(s): 20. T610 for flights to/from EHLE airport. NLD

Objective: Project Category: To further improve airspace organisation within Amsterdam ATS Routes FIR. Proposal ID : 96.019 / 30.001 Status: Contributor: Comments: Project Name: ATS Route deletion Norway Implementation: State(s) and Org:  Linked to the ATS route deletions

Description: Implemented NOR within NEFAB States. To remove ATS route M185 in Norway. 07 NOV 2019 DNK  Points will be kept. Serial Number: GBR  High Seas Coordination (Serial Objective: EUR/NAT 19/03-HS-NOR ICAO No.:EUR/NAT 19/03-HS-NOR) To further improve the airspace organisation within Norway FAB NEFAB Circulation Letter 19-0247 of 12 June and harmonize with Free Route operations. 21. Originator(s): 2019, Approval Letter 19-0318 of 25 NOR July 2019

Project Group: Related proposals: SG BALTIC  96.021 / 29.030

Project Category:  97.023 ATS Routes  97.030 High Seas Proposal ID : 97.044 Status: Contributor: Comments: Project Name: ATS Route Improvement Norway Implementation: State(s) and Org:  ENGM SIDs adjusted for operational

Description: Implemented NOR reasons. To realign ATS routes P615 and Z125 with adjusted SID 07 NOV 2019 DNK  5LNCD: 585633N 0101343E. ICAO  5LNCB: 612228.37N 0112858.99E procedures from ENGM as follows: a. P615 ARTOR - 5LNCD - TOR - ...; Originator(s): 22. b. Z125 NUVSA - 5LNCB - GIGNI - SOMUB. NOR

Objective: Project Group: To harmonize ATS routes with adjusted SID procedures from FAB NEFAB

ENGM. Project Category: ATS Routes High Seas Proposal ID : 85.030 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 8

EUROCONTROL Network Management Directorate

Project Name: ATS Route Improvement Bucuresti FIR Implementation: State(s) and Org:  TUREC - will be new boundary point Kyiv UIR Implemented UKR between Bucuresti FIR and L’viv 07 NOV 2019 ROU FIR/Kyiv UIR. Description: 1. To implement the following ATS routes: Originator(s):  Sections of ATS routes expected to be a. T/UT490 TUREC - OSTOV southbound (EVEN FLs UKR CDR in Bucuresti FIR, with alternative routing along existing ATS routes via above FL275); Project Category: RUMUK. 23. b. T/UT491 LOMOS - EROMO northbound (ODD FLs ATS Routes above FL275). 2. To implement new FRA unidirectional boundary point TUREC - Bucuresti FIR (E) and L’viv FIR/Kyiv UIR (X).

Objective: To further improve the ATS route network between Kyiv UIR and Bucuresti FIR. Proposal ID : 97.046 Status: Contributor: Comments: Project Name: SECSI FRA - NPZs Austria Implementation: State(s) and Org: In order to avoid short crossing of multiple Implemented AUT ACC airspace, a No Planning Zone/ NPZ is Description: 1. To publish NPZ INSAX within Vienna FIR. 05 DEC 2019 Originator(s): defined as an area within which the planning of DCT trajectories is not allowed. 2. To publish NPZ SUNIS within Vienna FIR. AUT 24. Objective: Project Category: Related proposals: To be compliant with ERNIP Part 1 - Annex 4. Airspace Structure  97.047 Free Route Airspace  97.048 NPZ  97.049 Proposal ID : 98.063 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Belgium Implementation: State(s) and Org: Implemented BEL Description: To change all existing CDR Categories into a single CDR 05 DEC 2019 Originator(s): 1 category. BEL 25. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in SCC Belgium. Proposal ID : 98.032 Status: Contributor: Comments: Project Name: Remove 'U' Prefix of ATS routes in Implementation: State(s) and Org: The routes are : UL608, UT180, UT856, 26. Belgium Implemented BEL UM150, UM170, UM624, UN852, UN853,

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 9

EUROCONTROL Network Management Directorate

Description: 05 DEC 2019 Originator(s): UN872, UN873, UQ50, UQ70, UT853, To remove the ‘U’ prefix of ATS routes in Belgium. BEL UT857, UY18, UY28, UY37, UY180,

Objective: Project Category: UY181, UY862, UY863, UY868, UZ104, Remove 'U' prefix and rationalise the use of Route ATS Routes UZ283, UZ310, UZ717 Designators. Proposal ID : 60.006b Status: Contributor: Comments: Project Name: BH ATM, Phase 2 Implementation: State(s) and Org:  Phase 1: FL325 and below

Description: Implemented BIH successfully implemented 13 NOV To re-organise the airspace structure within Sarajevo FIR 05 DEC 2019 HRV 2014. above FL325. MNE ◦ Re-sectorisation required within SRB Croatia and Serbia. Objective: 27.  Close coordination with the Network To further improve the ATS route network and associated Originator(s): BIH Manager and neighbouring ACC

airspace structure in order to support the establishment of the new ACC within Sarajevo FIR (BH ATM Project, Phase Project Group: Related proposals: 2). RFG SE  60.006a

Project Category:  97.052 Airspace Structure Proposal ID : 89.022 Status: Contributor: Comments: Project Name: Unnamed Significant Points Implementation: State(s) and Org: Detailed information is attached as

Description: Implemented CHE separate doc file in ERNIP. 05 DEC 2019 FRA To remove from ENR 3 in AIPs several unnamed significant Related proposals: points. Originator(s):  89.021 28. EUROCONTROL Objective: To further improve the AIP airspace data publication. Project Category: AIP ATS Routes Proposal ID : 92.024a Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org: Z57 (LAMUR – GUDAX), FL660 – FL155. issues Implemented CHE Related proposals: Description: 05 DEC 2019 Originator(s):  92.023 29. To adapt the lower vertical limit, expressed in FL of ATS EUROCONTROL route Z57 within Switzerland - change of IFR FL to VFR FL. Project Category: Objective: AIP To adapt in State AIP ATS routes vertical limits. ATS Routes

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 10

EUROCONTROL Network Management Directorate

Proposal ID : 89.021 Status: Contributor: Comments: Project Name: Unnamed Significant Points Implementation: State(s) and Org: Detailed information is attached as Implemented CHE separate doc file in ERNIP. Description: To remove from ENR 3 in AIP 6 unnamed significant points. 05 DEC 2019 Originator(s): Related proposals: 30. EUROCONTROL  89.022 Objective: To further improve the AIP airspace data publication. Project Category: AIP ATS Routes Proposal ID : 96.003b Status: Contributor: Comments: Project Name: Single CDR category (SCC) - Switzerland Implementation: State(s) and Org: Interface with AUT and DEU ok, further - Phase 2 Implemented CHE action required for the interface with ITA.

Description: 05 DEC 2019 Originator(s): Related proposals: To change the existing CDR 3 Category into a "Available by CHE  96.003a 31. ATC only". Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in Switzerland. Proposal ID : 98.035 Status: Contributor: Comments: Project Name: To remove 'U' Prefix of ATS routes in Implementation: State(s) and Org: The routes are UL15, UN491, UN850, Switzerland Implemented CHE UN851, UQ341

Description: 05 DEC 2019 Originator(s): 32. To remove the ‘U’ prefix of several ATS routes. CHE

Objective: Project Category: To remove 'U' prefix from ATS routes and to rationalise the ATS Routes use of Route Designators. Proposal ID : 89.025c Status: Contributor: Comments: Project Name: RDs collocation resolution Phase 2 Implementation: State(s) and Org:  Detailed information is attached as Implemented DEU separate doc file in ERNIP. Description: To simplify ATS routes designation and remove RDs 05 DEC 2019 Originator(s):  Linked to Langen 2.0 project. 33. collocation Phase 2. EUROCONTROL  Release RDs: L171, T155, T808, T809, T810, Y211, Y212, Y900, Z727, Z732, Objective: Project Category: Z741, Z742 and Z907. To resolve spotted RDs collocation within Germany. AIP Related proposals:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 11

EUROCONTROL Network Management Directorate

ATS Routes  89.025a  91.038 Proposal ID : 97.012 Status: Contributor: Comments: Project Name: Langen ACC Sector Group 5 re-design - Implementation: State(s) and Org:  No route changes associated to this Step 2 Implemented DEU pure ATC sector re-design.

Description: 05 DEC 2019 Originator(s):  Step 1: 20 JUN 2019 34. To re-design Langen ACC Sector Group 5. DEU  Step 2: 05 DEC 2019.

Objective: Project Category: Related proposals: To level traffic counts and optimize airspace design in Airspace Structure  97.011 Langen ACC for future iCAS implementation. ATC Sectors  97.015 Proposal ID : 96.005 Status: Contributor: Comments: Project Name: Single CDR category (SCC) - Germany Implementation: State(s) and Org: Implemented DEU Description: To change all existing CDR Categories into a single CDR 05 DEC 2019 Originator(s): category. DEU 35. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in SCC Germany. Proposal ID : 97.048 Status: Contributor: Comments: Project Name: SECSI FRA - NPZ Germany Implementation: State(s) and Org: In order to avoid short crossing of multiple Implemented DEU ACC airspace, a No Planning Zone/ NPZ is Description: To publish NPZ MORED within Munich FIR/ Rhein UIR. 05 DEC 2019 Originator(s): defined as an area within which the planning of DCT trajectories is not allowed. AUT 36. Objective: To be compliant with ERNIP Part 1 - Annex 4. Project Category: Related proposals: Airspace Structure  97.046 Free Route Airspace  97.047 NPZ  97.049 Proposal ID : 98.033 Status: Contributor: Comments: Project Name: To remove 'U' Prefix of ATS routes in Implementation: State(s) and Org: Germany Implemented DEU 37. Description: 05 DEC 2019 Originator(s): To remove the ‘U’ prefix of ATS routes UZ28 and UZ29. DEU

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 12

EUROCONTROL Network Management Directorate

Objective: Project Category: To remove 'U' prefix from ATS routes and to rationalise the ATS Routes use of Route Designators. Proposal ID : 93.013b Status: Contributor: Comments: Project Name: Cross-border FRA Maastricht UAC, Implementation: State(s) and Org:  Eligible are flights departing / arriving DK/SW FAB Implemented DNK at aerodromes within the DK-SE FAB -

Description: 05 DEC 2019 SWE FPLs do not require a boundary To expand to H24 (from Night and Weekend) Cross-border DEU waypoint between the respective FRA between Maastricht UAC - DK/SE FAB (FL245/ MUAC ACCs. FL285 - FL660). NLD  Flights overflying DK-SE FAB are not FAB Denmark/Sweden eligible for cross-border FRA with Objective: MUAC - FPLs have to file a boundary To further improve flight planning options between Originator(s): 38. waypoint between the respective ACCs Maastricht UAC and DK/SW FAB. FAB Denmark/Sweden MUAC (same as today).  MUAC: ATS Route Network available. Project Category:  DNK: ATS Route Network available. Free Route Airspace  SWE: ATS Route Network available.

Related proposals:  87.036c  93.013a Proposal ID : 97.025 Status: Contributor: Comments: Project Name: Route Rationalisation DK-SE FAB - Implementation: State(s) and Org: High Seas Coordination (Serial no: Maastricht UAC Implemented DNK EUR/NAT 19-14-HS-DNK)

Description: 05 DEC 2019 MUAC Circulation letter ref: EUR/NAT 19- Circulation Letter: NOR 0464.TEC of 21 October 2019 with deadline To delete the following existing ATS routes and route segments: P615 ALASA - ALSIE, Z711 BAMOR - GESKA, EUR/NAT 19-0464.TEC of 21 Originator(s): for reply on 21 November 2019 39. October 2019 Approval letter ref: EUR/NAT 19-0530.TEC L619, P603, Z700, Z701, Z704, Z705, Z708, Z709, Z710. DNK Approval Letter: of 6 December 2019. Objective: Project Category: To rationalize the existing ATS route network at the interface EUR/NAT 19-0530.TEC of 6 ATS Routes Related proposals: December 2019  97.023 between Maastricht UAC and DK-SE FAB. High Seas  97.030 Proposal ID : 89.027b Status: Contributor: Comments:

Project Name: RDs collocation resolution by France Implementation: State(s) and Org: Related proposals: 40. Implemented FRA Description:  89.027a 05 DEC 2019

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 13

EUROCONTROL Network Management Directorate

To simplify ATS routes designation and remove RDs Originator(s): collocation in Brest for UN741 - UT460 and UZ273 - UM189. EUROCONTROL

Objective: Project Category: To resolve spotted RDs collocation within France. AIP ATS Routes Proposal ID : 97.006b Status: Contributor: Comments: Project Name: Single CDR category (SCC) - France - Implementation: State(s) and Org: Stepped approach. Phase 2 Implemented FRA Related proposals: Description: 05 DEC 2019 Originator(s):  97.006a To change several existing CDR Categories into a single FRA  97.006c 41. CDR category within Reims ACC. Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in France. Proposal ID : 98.037 Status: Contributor: Comments: Project Name: EGGP Airspace Efficiency Implementation: State(s) and Org: Implemented GBR Description: Establish DCT REXAM DCT RETSI for EGGP departures 05 DEC 2019 Originator(s): 42. via N862. GBR

Objective: Project Category: To further improve the flight plannable options and more DCTs accurately reflect the route given tactically/ flown. Proposal ID : 98.038 Status: Contributor: Comments: Project Name: EGNT Airspace Efficiency Implementation: State(s) and Org: Implemented GBR Description: Establish DCT BETAX DCT GOKOV for EGNT arrivals via 05 DEC 2019 Originator(s): 43. L613. GBR

Objective: Project Category: To further improve the flight plannable options and more DCTs accurately reflect the route given tactically/ flown. Proposal ID : 98.039 Status: Contributor: Comments: Project Name: EGCC Airspace Efficiency Implementation: State(s) and Org: 44. Implemented GBR

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 14

EUROCONTROL Network Management Directorate

Description: 05 DEC 2019 Originator(s): Establish DCT SONEX DCT MAMUL for EGCC departures GBR via L603. Project Category: Objective: DCTs To reduce flight plannable track mileage to more accurately reflect tactical routeing given/ flown. Proposal ID : 98.040 Status: Contributor: Comments: Project Name: EGCC Airspace Efficiency Implementation: State(s) and Org: Implemented GBR Description: Establish a DCT KUXEM DCT KARNO for EGCC 05 DEC 2019 Originator(s): 45. departures via N862. GBR

Objective: Project Category: To further improve the flight plannable options and more DCTs accurately reflect the route given tactically/ flown. Proposal ID : 98.041 Status: Contributor: Comments: Project Name: Leeds Airspace Efficiency Implementation: State(s) and Org: Implemented GBR Description: Establish a DCT TIPIL DCT LBA for Leeds arrivals via 05 DEC 2019 Originator(s): 46. TIPIL. GBR

Objective: Project Category: To further improve the flight plannable options and more DCTs accurately reflect the route given tactically/ flown. Proposal ID : 74.064b Status: Contributor: Comments: Project Name: ATS Route Improvement Athinai FIR Implementation: State(s) and Org: Connected to PBN implementation in Implemented GRC Athens TMA. Description: 1. To implement ATS route M749 SKP - ROPOX (crossing 05 DEC 2019 Originator(s): point with northern lateral limits of Athinai TMA) - ATV GRC

with the relevant procedures (SIDs and STARs) for Project Group: 47. LGAV. RFG SE 2. To withdraw ATS route B1 SKP - ABLON - ATV following the implementation of M749. Project Category: ATS Routes Objective: To further improve ATS route network within Athinai FIR / Hellas UIR.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 15

EUROCONTROL Network Management Directorate

Proposal ID : 96.014 Status: Contributor: Comments: Project Name: 5LNC replacement by Iceland - MURTA Implementation: State(s) and Org: On 9 April 2019, Iceland did select RAJOL Implemented ISL as a replacement. Implementation TBA Description: To replace 5LNC MURTA (duplicated worldwide). 05 DEC 2019 Originator(s): 48. ICAO Objective: To avoid 5LNCs duplication within the ICAO EUR/NAT Project Category: region, to improve the aeronautical information provided and 5LNC be compliant with ICAO Annex 11. Proposal ID : 97.049 Status: Contributor: Comments: Project Name: SECSI FRA / FRA-IT - NPZs Italy Implementation: State(s) and Org: In order to avoid short crossing of multiple Implemented ITA ACC airspace, a No Planning Zone/ NPZ is Description: 1. To publish H24 NPZ VEKEN within Milano FIR. 05 DEC 2019 Originator(s): defined as an area within which the planning of DCT trajectories is not allowed. 2. To publish H24 NPZ FRZ within Milano FIR. AUT 49. Objective: Project Category: Related proposals: To be compliant with ERNIP Part 1 - Annex 4. Airspace Structure  97.046 Free Route Airspace  97.047 NPZ  97.048 Proposal ID : 97.050 Status: Contributor: Comments: Project Name: NGT segments in ATS permanent/CDR1 Implementation: State(s) and Org: Previous classification CDR3 0600-2100

Description: Implemented ITA (0500-2100) not necessary anymore. 05 DEC 2019 FAB BLUE MED To change following segments from CDR3 (NGT RTE) in ATS permanent/CDR1: Originator(s): a. L611 SUXAN-ROTAR (ATS permanent/CDR1); ITA

b. M616 ELB-DIRKA (ATS permanent/CDR1); Project Group: c. M621 AOSTA-AMANO (ATS permanent/CDR1); FAB BLUE MED d. M731 TEKSA-OSMAR (ATS permanent); 50. e. N604 DOKAR-INGAB (CDR1) and INGAB-RUTOM Project Category: (ATS permanent/CDR1); CDRs f. Q182 RUVIP-NERAR (ATS permanent/CDR1); Night Routes g. T75 AMSOR-TIGRA (ATS permanent/CDR1); h. T292 GISNU-BRD (ATS permanent); i. T307 DIRAB-BABAG (ATS permanent/CDR1).

Objective: To offer more flight planning options below FRA IT. Proposal ID : 87.036c Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 16

EUROCONTROL Network Management Directorate

Project Name: FRAM2 - Phase 3 Implementation: State(s) and Org:  Some ATS Routes (20%) will be

Description: Implemented MUAC removed. To expand to H24 existing Night and Weekend Free Route 05 DEC 2019 BEL  Linked with H24 Cross-border FRA Airspace above FL245 - FL660 within the Maastricht UAC Serial Number: DEU Maastricht UAC and DK/SW FAB. EUR/NAT 19/07-HS-BEL NLD  High Seas Coordination (Serial no: AoR. EUR/NAT 19/07-HS-BEL/DEU/HOL) Objective: Originator(s): circulation letter ref: EUR/NAT 19-0343 To further improve the Free Route Airspace operations MUAC of 5 August 2019 circulated with 51. within Maastricht UAC. FAB EC deadline on 5 September 2019, Project Group: approval letter ref: EUR/NAT 19-0400 FAB EC of 17 September 2019. Project Category: Related proposals: Free Route Airspace High Seas  87.005f  87.036a  87.036b  93.013b Proposal ID : 98.034 Status: Contributor: Comments: Project Name: To remove 'U' Prefix of ATS routes in the Implementation: State(s) and Org: Except UM617. Netherlands Implemented NLD

Description: 05 DEC 2019 Originator(s): To merge all Upper and Lower ATS routes and remove the NLD 52. ‘U’ prefix. Project Category: Objective: ATS Routes To remove the 'U' prefix from ATS routes and to rationalise the use of Route Designators. Proposal ID : 97.054 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Netherlands Implementation: State(s) and Org: Implemented NLD Description: To change all existing CDR Categories into a single CDR 05 DEC 2019 Originator(s): 1 category. NLD 53. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in the SCC Netherlands. Proposal ID : 97.052 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 17

EUROCONTROL Network Management Directorate

Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org: Related proposals: issues Implemented SRB  60.006b 05 DEC 2019 BIH Description: 1. To withdraw VOR/DME NIS from the ATS route network Originator(s): which affects airways L617 and N131 (L617 VAGEN – SRB

54. NIS – RAVAK; N131 SOSEK – NIS – NISVA) Project Category: 2. NDB NIK FRA relevance change: NIK NDB will become AIP only FRA (D): LYPG, LYTV instead of FRA (DI).

Objective: Required AIP changes caused by the BH Airspace Plan, Phase II implementation. Proposal ID : 97.055 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Slovakia Implementation: State(s) and Org: Implemented SVK Description: To change all existing CDR Categories into a single CDR 05 DEC 2019 Originator(s): 1 category. SVK 55. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in SCC Slovakia. Proposal ID : 97.047 Status: Contributor: Comments: Project Name: SECSI FRA - NPZs Slovenia Implementation: State(s) and Org: In order to avoid short crossing of multiple Implemented SVN ACC airspace, a No Planning Zone/ NPZ is Description: 1. To publish NPZ RUSE within Ljubljana FIR. 05 DEC 2019 Originator(s): defined as an area within which the planning of DCT trajectories is not allowed. 2. To publish NPZ OBUTI within Ljubljana FIR. AUT 56. Objective: Project Category: Related proposals: To be compliant with ERNIP Part 1 - Annex 4. Airspace Structure  97.046 Free Route Airspace  97.048 NPZ  97.049 Proposal ID : 98.005 Status: Contributor: Comments: Project Name: New Scandinavian Mountains Airport - Implementation: State(s) and Org: ESKS Implemented SWE 57. 05 DEC 2019 NOR Description: 1. To implement a new airport in Sweden near the Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 18

EUROCONTROL Network Management Directorate

Norwegian border, referred to as Sälen Trysil Airport. SWE

2. To re-organise the ATS routes and airspace structure Project Category: accordingly. Airspace Structure Objective: To further improve the airspace structure and to accommodate the expected traffic during the winter sport/ ski season. Proposal ID : 98.007 / 31.006 Status: Contributor: Comments: Project Name: ATS Route Network Improvement Turkey Implementation: State(s) and Org:  Extension of N743 from Sofia FIR.

Implemented TUR  Presented and discussed at RDGE/31 Description: To implement eastbound ATS route segment N743 UDROS - 05 DEC 2019 Originator(s): (9 - 13 SEP 2019). ABSAX. Serial Number: TUR  High Seas Coordination (Serial no: EUR/NAT 19/13-HS-TUR EUR/NAT 19/13-HS-TUR). Objective: Project Group: Circulation Letter:  Circulation letter ref: EUR/NAT 19- 58. To further improve the ATS route network while providing a SG BLACK connection for ARR LT** and to separate traffic flows EUR/NAT 19-0432.TEC of 7 0432.TEC of 7 October 2019 - deadline Project Category: on 7 November 2019. towards Yerevan FIR / Tehran FIR. October 2019 ATS Routes Approval Letter:  Approval letter ref: EUR/NAT 19- 0509.TEC of 13 November 2019. EUR/NAT 19-0509.TEC of 13 November 2019 Related proposals:  95.008 / 28.024 Proposal ID : 95.008 / 28.024 Status: Contributor: Comments: Project Name: ATS Route Improvement/ Re-designation Implementation: State(s) and Org:  Majority of old ATS routes before INA Turkey Implemented TUR implementation will be kept in parallel

Description: 05 DEC 2019 Originator(s): with new ones for contingency To re-designate the following ATS routes: Serial Number: TUR purposes. a. T/UT624 DIGTI - BKZ - AMUDU as N/UN644 (release EUR/NAT 19/13-HS-TUR  For some of the new ATS routes new Project Group: RDs were assigned in order to avoid of T624); Circulation Letter: SG BLACK 59. b. T/UT642 GIPDA - ABSAX - BIMVO as T/UT641 EUR/NAT 19-0432.TEC of 7 misleading information. Some of those Project Category: (release of T642); October 2019 RDs need to be replaced by RDs from ATS Routes old ATS routes. c. T/UT644 ABSAX - GAKSU - ODIRA as N/UN743 Approval Letter: (release of T644). Route Redesignation 

EUR/NAT 19-0509.TEC of 13 Objective: November 2019 Related proposals: To adapt the ATS route network to the requirements of the  76.068a Istanbul new Airport.  76.068b  98.007 / 31.006 Proposal ID : 97.053b Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 19

EUROCONTROL Network Management Directorate

Project Name: Airspace reorganisation Praha FIR Implementation: State(s) and Org: AMTEK deleted.

Description: Implemented CZE Related proposals: 30 JAN 2020 POL To re-organize the AMTEK/ REGLI area.  97.053a

60. Objective: Originator(s): CZE To further improve the airspace structure within Praha FIR. Project Category: ATS Routes Proposal ID : 97.026 Status: Contributor: Comments: Project Name: New RNAV STARs at Leipzig/EDDP Implementation: State(s) and Org:  Current Point Merge System does not airport Implemented DEU fulfil the traffic and capacity

Description: 30 JAN 2020 Originator(s): requirements anymore, as it is not Point Merge to be deleted and replaced by a new set of DEU suitable for the planned parallel independent runway operations. RNAV-1 STARs and a set of new ATS route segments to Project Category:  In parallel the existing connections connect the STARs to the ATS route network as follows: ATS Routes T230, T231, T232, T233, T234, T235 a. T950 BEBKU - RAXLI - SAWAZ - LUXBO; PBN and segment ADMOS – LUKOP of b. T951 YAWOY - KUWUS - TEXTI; TMA c. T952 TABAT - GOXLI; T236 will be deleted. d. T953 LASGA - VOCIM; 61. e. T954 PIBAD - VOCIM - GOXLI; f. T955 TAMEB - GOXLI; g. T956 GOXLI - LASTO; h. T957 ESEGU - GOHEG; i. T958 BERDI - GOHEG; j. T959 GOHEG - KENIG - ADMOS.

Objective: To further improve the ATS route network in preparation of the planned parallel, independent runway operations at Leipzig airport. Proposal ID : 96.025 Status: Contributor: Comments: Project Name: 5LNC replacement Germany Implementation: State(s) and Org: GUDOM is replaced by RUFGA Implemented DEU Description: To replace 5LNC waypoint GUDOM. 30 JAN 2020 Originator(s): 62. ICAO Objective: To resolve sound-like problem with waypoint GUDON on FIR Project Category: boundary with Poland. 5LNC

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 20

EUROCONTROL Network Management Directorate

To improve the aeronautical information provided and be compliant with ICAO Annex 11. Proposal ID : 98.026 Status: Contributor: Comments: Project Name: Thüringen sector re-design - Munich ACC Implementation: State(s) and Org: Linked to IPO/ Independent Parallel Implemented DEU Operations at EDDP airport. Description: To provide a new sector structure for airspace Thüringen 30 JAN 2020 Originator(s): Low (EDMMTRGL) and split in North (EDMMTRLN) and DEU 63. South (EDMMTRLS) sector. Project Category:

Objective: Airspace Structure To further improve the airspace structure within Munich ACC ATC Sectors and facilitate the upcoming independent parallel operation at EDDP airport. Proposal ID : 98.055 Status: Contributor: Comments: Project Name: ATS route Improvement Praha ACC - Implementation: State(s) and Org:  Handover for arrivals to EDDB/EDDT München ACC Implemented DEU from Praha ACC to München ACC via 30 JAN 2020 CZE HDO and via RODUX is both done at Description: To re-align ATS route segment T204 BEFRE - TEXTI - Originator(s): FL310. To improve the separation and ABLOX. DEU integration of these flows, route T204 is shifted further to the east via new COP Objective: Project Category: 64. BEFRE instead of RODUX to gain To further improve the ATS route network between Praha 5LNC more spacing. ACC and München ACC while separating two flows of ATS Routes  T206, T405 and P41 (segment DOKEL arrivals to EDDB/EDDT (via HDO and formerly via RODUX). - RODUX) will be deleted. Waypoint RODUX will be deleted.  Connection from Czech Republic to BEFRE will be assured by DCTs. Proposal ID : 50.053a Status: Contributor: Comments: Project Name: Lisboa / Casablanca / Canarias Axis Implementation: State(s) and Org:  Phase 2 of the project - complete re- Phase 1a Implemented ESP organisation of the Interfaces - in line

Description: 30 JAN 2020 PRT with new Canarias TMA re-organisation 65. 1. To review the airspace organisation on the Lisboa / MAR is planned for summer 2022. FAB SW  New FIR boundary point TIGGI was Casablanca / Canarias axis and to permit the utilisation of 5LNC point TIGGI for northbound traffic at Originator(s): implemented by Portugal during Agadir/Lisboa ACC Interface. ESP summer 2019 while by Morocco on 2 JAN 2020. 2. To create new DCT segments as follows: PRT

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 21

EUROCONTROL Network Management Directorate

a. SAMAR - NEVTU (in Agadir ACC); MAR Related proposals: b. NEVTU - TIGGI (in Agadir ACC).  50.053b Project Group: Objective: FAB SW  50.053c To further improve the ATS route network and airspace RFG SW  50.053d

organisation within Canarias FIR/UIR, Casablanca FIR/UIR Project Category:  50.053e and Lisboa FIR. Airspace Structure  60.034b DCTs  73.052  75.022 Proposal ID : 97.051 Status: Contributor: Comments: Project Name: Roma ACC/Malta ACC interface Implementation: State(s) and Org:

Description: Implemented FAB BLUE MED 1. To implement northbound ATS route Q231 ADEXI - 30 JAN 2020 ITA MLT NEVOT - KOVAS. 2. To introduce new REP along FIR bdry (15NM east of Originator(s): LORED) and impelement northbound ATS route XXXXX ITA 66. - ABAKO. MLT

3. To withdraw existing ATS routes Q156 and M616 Project Group: MARON - DIRKA. FAB BLUE MED

Objective: Project Category: Better management of traffic exchange btwn Malta and ATS Routes Roma ACC. Proposal ID : 98.059 Status: Contributor: Comments: Project Name: Vertical Flight Efficiency Implementation: State(s) and Org: The RAD is amended to enable traffic with Implemented GBR destination London Group and Farnborough Description: To remove RAD Appendix 3 FL capping of FL305 over 30 JAN 2020 Originator(s): Group to file inbound via SALCO at 67. SALCO for ARR London Group and Farnborough Group. GBR preferred cruising levels. Previously this traffic had been capped at max FL305. Objective: Project Category: To further improve Vertical Flight Efficiency. RAD Vertical FE Proposal ID : 98.060 Status: Contributor: Comments: Project Name: RAD Review - Trial Implementation: State(s) and Org:  In conjunction with the IAA, it has been

Description: Implemented GBR agreed to trial the temporary relaxation 68. 30 JAN 2020 IRL of a number of RAD restrictions for To lift the eastbound Oceanic RAD restrictions for EH** and ED** traffic, on temporary bases from 30 JAN 2020 until 16 Originator(s): eastbound oceanic traffic inbound to ED/EH.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 22

EUROCONTROL Network Management Directorate

JUL 2020 as follows: IRL  It is hoped that following a successful a. EGEI1009 - point 1 prohibiting EDDH/DL/DT, EHAM, GBR trial period these changes will become

EP** traffic via GISTI from filing BAKUR/SLANY is Project Category: permanent. disabled; RAD b. EGEI1020 - RAD amended to allow EHAM traffic to file via NORLA if either departing EI** or routeing onwards via NORLA M140 SAM; c. EGEI1017 - disabled. Mandatory requirement for EDDF arrivals via NETKI to file via LIPGO/NIBOG is removed; d. EGEI1019 - disabled. Mandatory requirement for EHAM arrivals via NETKI to file via NIBOG is removed.

Objective: To improve flight plannable options for AOs into EH**/ED** airfields through EGTT. Proposal ID : 98.061 Status: Contributor: Comments: Project Name: D201 Extension Implementation: State(s) and Org: Two new direct routeings are implemented

Description: Implemented GBR to circumvent activity in danger area 30 JAN 2020 IRL EGD201F/G. When D201F/G is active To allow the following DCT flight planning options to avoid EG-D201F/Gwhen is active above FL145: Originator(s): above FL145, traffic RFL245+ via KENET a. FOXLA DCT SLANY - traffic to MALOT, NEBIN, GBR N14 and routeing to specific OEPs is DOGAL, VENER, RESNO, ETARI, PIKIL, BILTO, permitted to file via either FOXLA DCT Project Category: SLANY or via FOXLA DCT STU. 69. SUNOT and EI** arrivals (except Dublin Group) DCTs b. FOXLA DCT STU - traffic to MALOT, TOBOR, LIMRI, RAD ADARA, DINIM, RODEL, SOMAX, KOGAD, BEDRA SUNOT and EI** arrivals (except Dublin Group).

Objective: To provide flight plannable re-routes due to activation of D201F/G. Proposal ID : 98.049 Status: Contributor: Comments: Project Name: Tango Routes in Shannon UIR Implementation: State(s) and Org: High Seas Coordination (Serial no: Implemented GBR EUR/NAT 19/20-HS-GBR) Description: To implement the following RNP 2 routes: 30 JAN 2020 Originator(s): Circulation letter ref: EUR/NAT 19- 70. a. T290 GELPO - ADVAT; Serial Number: GBR 0525.TEC of 29 November 2019 circulated b. T9 LASNO - BEGAS. EUR/NAT 19/20-HS-GBR with deadline on 27 December 2019, Project Category: Circulation Letter: Approval letter ref: EUR/NAT 20-0002.TEC Objective: ATS Routes of 2 January 2020. To allow inter European flights that transit Oceanic airspace EUR/NAT 19-0525.TEC of 29 High Seas

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 23

EUROCONTROL Network Management Directorate

within the ‘South East Corner’ to continue without the November 2019

requirement to fit FANS 1/A equipment. Approval Letter: EUR/NAT 20-0002.TEC of 2 January 2020

Proposal ID : 91.020a Status: Contributor: Comments: Project Name: Hellas FRA - Free Route Airspace Greece Implementation: State(s) and Org:  Gradual implementation from JAN - Phase 4a Implemented GRC 2021 till summer 20122.

Description: 30 JAN 2020 Originator(s):  'Double AIRAC procedure’ for AIRAC To implement Night (21:00 - 04:00) Free Route Airspace GRC AIP AMDT publication required for within Hellas UIR FL335 - FL460. FAB BLUE MED implementation (ICAO Annex 15 refers). 71. Objective: Project Category:  ATS Route Network available. To further improve flight planning options within Hellas UIR. Free Route Airspace Related proposals:  91.018a  91.018b  91.019  91.020b Proposal ID : 96.012 Status: Contributor: Comments: Project Name: 5LNC replacement by Hungary Implementation: State(s) and Org:  5LNC TAPIO not assigned to Hungary Implemented HUN in ICARD. Description: To re-name 5LNC TAPIO. 30 JAN 2020 Originator(s):  “TAPIO” replaced with “TAPIOSAP” and serve still for VFR flights (see HUN 72. Objective: ICAO AIP AD 2.22 point 5.2). To avoid 5LNCs duplication within the ICAO EUR/NAT Project Category: region, to improve the aeronautical information provided and 5LNC be compliant with ICAO Annex 11. Proposal ID : 98.008 Status: Contributor: Comments: Project Name: New Budapest TMA Implementation: State(s) and Org: Presented and discussed at RDGE/31 (9 - Implemented HUN 13 SEP 2019). Description: To implement new Budapest TMA and new SIDs/STARs, 30 JAN 2020 Originator(s): 73. TMA entry/exit and FRA intermediate points. HUN

Objective: Project Category: To further improve the airspace structure while making the Airspace Structure TMA organisation more responsive to airspace users TMA needs and reduce ATC workload.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 24

EUROCONTROL Network Management Directorate

Proposal ID : 93.008 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to Implemented ITA take action. Description: To withdraw 5LNC ORION. 30 JAN 2020 Originator(s):  This 5LNC is used worldwide for 7 significant points and the Priority State Objective: ICAO 74. identified by ICAO to keep the code is To avoid worldwide 5LNC duplication, to improve the Project Category: USA. aeronautical information provided and be compliant with 5LNC  5LNC exists for a significant point ICAO Annex 11. Civil/Military Airspace at/around LICZ military airport.  5LNC was released by Italy Proposal ID : 94.009 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to Implemented ITA take action. Description: To replace 5LNC MILAN. 30 JAN 2020 Originator(s):  This 5LNC is used worldwide for 5 significant points and the Priority State Objective: ICAO identified by ICAO to keep the code is To resolve worldwide 5LNCs duplication. Project Category: USA. 5LNC  Not registered in ICARD and Italy was Civil/Military Airspace notified by ICAO DM on 4 APR 2018 to 75. take action.  Real purpose of existence needs to be re-verified.  ITA (MIL) confirmed to ICAO EUR/NAT ICARD Data Manager that MILAN cannot be found on a civilian FMS; therefore the issue is considered closed. Proposal ID : 96.008 / 30.005 Status: Contributor: Comments: Project Name: Raise of Riga FIR upper limit Implementation: State(s) and Org: Achievement of full harmonisation of the Implemented LVA upper limit in Northern Europe. Description: 76. To raise the upper limit of controlled airspace within Riga 30 JAN 2020 Originator(s): FIR from FL460 to FL660. LVA

Objective: Project Category: To further improve the airspace organisation within Riga FIR. Airspace Structure Proposal ID : 97.041 / 30.023 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 25

EUROCONTROL Network Management Directorate

Project Name: Class C and G in Riga FIR (EVRR) Implementation: State(s) and Org: High Seas Coordination (Serial Implemented LVA No.:EUR/NAT 19/05-HS-LVA) Circulation Description: To classify the airspace of Riga FIR (EVRR) as follows: 30 JAN 2020 Originator(s): Letter ref: EUR/NAT 19-0320.TEC of 29 a. GND - FL095: Class “G”; Serial Number: LVA July 2019 circulated with deadline on 29 b. FL095 - FL660: Class “C”; and EUR/NAT 19/05-HS-LVA August 2019, Approval Letter ref: EUR/NAT Project Group: 19-0387.TEC of 4 September 2019. 77. c. FL660 - UNL: Class “G”. Circulation Letter: SG BALTIC EUR/NAT 19-0320.TEC of 29 Objective: Project Category: To further improve airspace structure in Riga FIR. July 2019 Airspace Structure Approval Letter: High Seas EUR/NAT 19-0387.TEC of 4 September 2019

Proposal ID : 96.002 Status: Contributor: Comments: Project Name: DFL355 MUAC BruSG East Implementation: State(s) and Org:

Description: Implemented BEL 27 FEB 2020 MUAC To raise the division level (DFL) between the Maastricht UAC Low and High sectors in the East of the Brussels Originator(s): 78. Sector Group from FL335 to FL355. MUAC

Objective: Project Group: To further improve the airspace structure while reducing the FAB EC

overall delay in the Brussels East sectors through a better Project Category: traffic distribution between the High and Low sectors. Airspace Structure Proposal ID : 98.036 Status: Contributor: Comments: Project Name: SECSI FRA - NPZ Bosnia and Implementation: State(s) and Org: In order to avoid short crossing of multiple Herzegovina Implemented BIH ACC airspace, a No Planning Zone/ NPZ is

Description: 27 FEB 2020 Originator(s): defined as an area within which the To publish NPZ SOMUN in Sarajevo FIR. BIH planning of DCT trajectories is not allowed. 79. Objective: Project Category: To be compliant with ERNIP Part1 - Annex 4. AIP Airspace Structure Free Route Airspace NPZ Proposal ID : 97.053a Status: Contributor: Comments: Project Name: DCTs Praha FIR Implementation: State(s) and Org: Details to be provided by CZE. 80. Implemented CZE

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 26

EUROCONTROL Network Management Directorate

Description: 27 FEB 2020 POL Related proposals:

To replace several ATS routes (route segments) by DCTs in Originator(s):  97.053b Praha FIR. CZE

Objective: Project Category: To further improve the flight planning options within Praha DCTs FIR. Proposal ID : 97.004 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Czech Implementation: State(s) and Org: Republic Implemented CZE

Description: 27 FEB 2020 Originator(s): To change all existing CDR Categories into a single CDR CZE 81. category Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in Czech Republic. Proposal ID : 50.053b Status: Contributor: Comments: Project Name: Lisboa / Casablanca / Canarias Axis Implementation: State(s) and Org:  New FIR boundary point DESUM was Phase 1b Implemented ESP implemented by Spain in AUG 2019

Description: 27 FEB 2020 PRT while by Morocco on 2 JAN 2020. To review the airspace organisation on the Lisboa / MAR  Plans were with opening of DESUM to FAB SW achieve dualisation of point VASTO but Casablanca / Canarias axis by allowing the following Night 06:00 - 22:00 UTC DCT options: Originator(s): due to opposite limitations on allowed a. DESUM DCT AKUDA; ESP DCTs this is not done. b. VASTO DCT NIDEB; PRT  22:00 - 06:00 UTC is MORFRA. 82. c. NIDEB DCT TIGGI. MAR  To suspend UN873 northbound option between SAMAR - BAROK Objective: Project Group: To further improve the ATS route network and airspace FAB SW Related proposals: organisation within Canarias FIR/UIR, Casablanca FIR/UIR RFG SW  50.053a

and Lisboa FIR. Project Category:  50.053c Airspace Structure  50.053d DCTs  50.053e  60.034b  73.052  75.022

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 27

EUROCONTROL Network Management Directorate

Proposal ID : 87.045 Status: Contributor: Comments: Project Name: SID Truncation London FIR Implementation: State(s) and Org: Implemented GBR Description: 1. To truncate EGLL MID SIDs to new points MAXIT 27 FEB 2020 Originator(s): and MODMI. GBR

2. Existing MID SIDs to be removed and replaced by Project Category: MAXIT 1F/1G and MODMI 1J/1K. ATS Routes 83. 3. To extend Y803 from MID to MODMI to replace the portion of the MID SID and amend M185 to route MID - MAXIT - OCK to replace the portion of the MID SID.

Objective: To reduce fuel uplift as a result of a shortened SID for EGLL departures via MID, to rationalize route designation and be ICAO compliant. Proposal ID : 94.056 Status: Contributor: Comments: Project Name: Prestwick Lower Airspace (PLAS) Project Implementation: State(s) and Org: 3c Implemented GBR

Description: 27 FEB 2020 Originator(s): To improve airspace structure at Doncaster airport: GBR a. RNAV 1 replication of existing UPTON SID; 84. Project Category: b. Introduction of a new RNAV 1 ROGAG SID replacing ATS Routes existing SOC (Standard Outbound Clearance); c. RNAV1 replication of existing STARs; d. RNAV 5 arrivals will use existing airways structure.

Objective: To remove en-route dependency in ground base Nav Aids. Proposal ID : 98.001 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Implemented GBR Description: To remove the en-route dependency on the Glasgow/ GOW 27 FEB 2020 Originator(s): DVOR STARs (both BRNAV and Conventional) will be made GBR 85. RNAV5 and redesignated as per below and the LANAK, Project Category: FYNER, STIRA & FOYLE Holds will be made RNAV: ATS Routes a. The LANAK 2A will become RIBEL 1G; b. The LANAK 1B will become APPLE 1G; c. The LANAL 2D will become AGPED 1G;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 28

EUROCONTROL Network Management Directorate

d. The GOW 1A will become BRUCE 1G; e. The GOW 1D will become ERSON 1G; f. The STIRA 1A will become PTH 1S.

Objective: To remove the en-route dependency on GOW DVOR and facilitate the eventual removal of the facility. Proposal ID : 97.045 Status: Contributor: Comments: Project Name: Farnborough Airspace Re-design Project Implementation: State(s) and Org: Implemented GBR Description: To significantly re-design the airspace for traffic into and out 27 FEB 2020 Originator(s): of Farnborough Airport and adjacent airports which will GBR

become known as the Wessex Group and include Project Category: Blackbushe (EGLK), Odiham (EGVO), Fairoaks (EGTF), 5LNC Lasham (EGHL) and Dunsfold (EGTD): AIP 1. Introduce new RNAV1 and RNAV5 STARs as well as Airspace Structure a RNAV Hold (VEXUB) and new 4 RNAV1 SIDs via ATM System HAZEL & GWC (HAZEL 1L/1F and GWC 1L/1F) and ATS Routes the establishment of New Class D & E airspace for an PBN expanded Farnborough CTA. GWC SIDs provide connectivity to N16, Y803, L612, M605, N859 and HAZEL SIDs provide connectivity to L620. New 86. Waypoints will be established as follows: DIXIB, LFE01, ASLAP, LFE02, ESULU, LFS01, ASLAP, LFS04, LFS05,

EVATA, NIDGO, INDOX, LUXIV, VEXUB, IBGON, GOBNU and RIMUP. Full details with coordinates available on request. 2. Standard Departure Routes for traffic ex EGLF will be: a. EGLF: All levels: RNAV1: HAZEL SID – L620 – SAM – Q41 – SILVA; b. EGLF: All levels: RNAV1: HAZEL SID – L620 – SAM – Q41 – PEPIS – Y321 – CPT – Q63 – KENET; c. EGLF: All levels: RNAV1: HAZEL SID – L620 – SAM – Q41 – PEPIS DCT OCK – M185 – KOBBI – M197; d. EGLF: All levels: RNAV1: GWC SID – N859, GWC DCT BOGNA L612 or GWC DCT BOGNA DCT HARDY M605 or GWC N16 or GWC DCT SFD

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 29

EUROCONTROL Network Management Directorate

Y803; e. EGLF: All levels: RNAV1: HAZEL SID – L620. 3. RNAV1 STARS will be given the Identifier 'V' and will be: f. CPT 1V: CPT – GOBNU –INDOX – DIXIB – LFS02 – VEXUB; g. KATHY 1V: KATHY – ABSAV – RUDMO – RIMUP – NIDGO – IBGON – LUXIV – EVATA – LFS03 – VEXUB; h. SOKDU 1V: SOKDU – ABSAV – RUDMO – RIMUP – NIDGO – IBGON – LUXIV – EVATA – LFS03 – VEXUB; i. ELDAX 1V: ELDAX – NOTGI – EVEXU – RIMUP – NIDGO – IBGON – LUXIV – EVATA – LFS03 – VEXUB 4. RNAV5 STARs will be given the Identifier 'P' and will be: j. CPT 1P: CPT – HANKY – PEPIS; k. KATHY 1P: KATHY – ABSAV – RUDMO – PEPIS; l. GIBSO 1P: GIBSO – SOKDU – ABSAV – RUDMO – PEPIS; m. NOTGI 1P: NOTGI – EVEXU – RUDMO – PEPIS.

Objective: To establish RNAV1 SIDs and STARs to reduce complexity, establish efficiency and predictability of operation for Farnborough traffic whilst minimising disturbance to local residents and continuing to afford access to airspace for all stakeholders. Proposal ID : 98.002 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Implemented GBR Description: To remove the en-route dependency on the Turnberry/ TRN 27 FEB 2020 Originator(s): DVOR the STARs (both BRNAV & Conventional) will be GBR

87. made RNAV5 and designated by their start point as Project Category: described below and the Holds at TARTN & SUMIN will ATS Routes made RNAV: a. The TWEED 2B will become TUNSO 1E; b. The TWEED 2C will become GIRVA 1E; c. The TWEED 2D will become AGPED 1E;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 30

EUROCONTROL Network Management Directorate

d. The TWEED 3A will become INPIP 1E; e. The BLACA 1C will become BLACA 1P; f. The APPLE 1P will become APPLE 2P; g. The RIBEL 1P will become RIBEL 2P; h. The TRN 1A will become BLACA 1G.

Objective: To remove the en-route dependency on the TRN DVOR and facilitate the eventual removal of the facility Proposal ID : 84.011 Status: Contributor: Comments: Project Name: Central sector Zagreb Phase 2b Implementation: State(s) and Org:  Further evaluation required.

Implemented HRV  Phase 2a: FL355 and above 2 April Description: 27 FEB 2020 Originator(s): 2015. Additional Sector Group Phase 2b: 88. Full lateral and vertical implementation of Central sector HRV Related proposals:

below FL355.  69.001 Project Group: Objective: RFG SE  69.068b

To further improve the airspace structure within Zagreb FIR Project Category:  74.051b and increase capacity. ATC Sectors Proposal ID : 94.010 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to

Implemented ITA take action. Description: To replace 5LNC CEDRO. 27 FEB 2020 Originator(s):  This 5LNC is used worldwide for 3 significant points. Objective: ICAO  Not registered in ICARD and Italy was To resolve worldwide 5LNCs duplication. Project Category: notified by ICAO DM on 4 APR 2018 to 5LNC take action. Civil/Military Airspace 89.  In use at LIMS airport "Piacenza/S.Diamana" (Military) - Approach and Terminal Usage.  ITA (MIL) confirmed that CEDRO cannot be found on a Civilian FMS, therefore the issue is considered as closed. CEDRO will note be substituted. Proposal ID : 71.047 Status: Contributor: Comments: 90. Project Name: Free Route Airspace Morocco (MORFRA), Implementation: State(s) and Org:  Night period 22:00 - 06:00 UTC.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 31

EUROCONTROL Network Management Directorate

Phase 1 Implemented MAR  'Double AIRAC procedure’ for AIRAC

Description: 27 FEB 2020 ESP AIP AMDT publication required for To implement Night Free Route Airspace FL195 - Serial Number: PRT implementation (ICAO Annex 15 EUR/NAT 20/01-HS-MRC refers). FL460 within the AoR of Agadir ACC. Originator(s):  High Seas Coordination (Serial no: Objective: Circulation Letter: MAR EUR/NAT 19/02-HS-MRC) circulation To further improve the flight planning options within EUR/NAT 20-0075.TEC of 30 Project Group: January 2020 letter ref: EUR/NAT 19-0220.TEC of 24 Casablanca FIR. RFG SW May 2019 circulated with deadline on Project Category: 24 June 2019. Free Route Airspace  High Seas Coordination (Serial no: EUR/NAT 20/01-HS-MRC) circulation letter ref: EUR/NAT 20-0075.TEC of 30 January 2020 circulated with deadline 14 February 2020. Revised Proposal.  High Seas Proposal (Serial no: EUR/NAT 20/01-HS-MRC) Approval letter ref: EURNAT 20-0104.TEC of 17 February 2020.  ATS Route Network will be removed.

Related proposals:  71.054a  71.054b Proposal ID : 98.015 Status: Contributor: Comments: Project Name: SEEN FRA Phase 3 Implementation: State(s) and Org: 'Double AIRAC procedure’ for AIRAC AIP

Description: Implemented SVK AMDT publication required for 27 FEB 2020 BGR implementation (ICAO Annex 15 refers). To expand SEEN FRA time availability within Bratislava FIR by 4 hours to 20:00 - 06:00 (19:00 - 05:00). HUN Related proposals: ROU  69.052 91. Objective: To further improve the Free Route Airspace operations Originator(s):  81.001 SVK  90.034 within Bratislava FIR. Project Group:  98.016 RFG SE

Project Category: Free Route Airspace Proposal ID : 80.036 Status: Contributor: Comments: 92. Project Name: FRA Improvement Sofia FIR / Bucuresti Implementation: State(s) and Org: Proper flight planning options allowed via

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 32

EUROCONTROL Network Management Directorate

FIR Implemented BGR RAD Appendix 5. 26 MAR 2020 ROU Description: To implement shorter FRA option for DEP LROP/LRBS via Originator(s): Sofia FIR to RIXEN / ARTAT. EUROCONTROL

Objective: Project Group: To further improve FRA options between Sofia FIR and RFG SE

Bucuresti FIR. Project Category: ATS Routes Proposal ID : 93.026 Status: Contributor: Comments: Project Name: Nicosia ACC -Tel Aviv ACC - Cairo ACC Implementation: State(s) and Org: NM support provided to find a better Re-organisation Implemented CYP sectorisation and re-organisation of the

Description: 26 MAR 2020 ISR interface of the South Nicosia area with Tel- 1. To re-sectorise Nicosia CTA and adapt the ATC Serial Number: EGY Aviv FIR and Cairo FIR. EUR/NAT 19/21-HS-CYP High Seas Coordination Procedure (Serial sectors to future traffic flows. Originator(s): 2. To permit "Direct" flight planning options according to Circulation Letter: ISR no: EUR/NAT 19/21-HS-CYP-GRC-ISR) 93. traffic flows within Nicosia UIR. EUR/NAT 19-0528.TEC of 4 EUROCONTROL - Circulation letter ref: EUR/NAT 19- 0528.TEC of 4 December 2019 with 3. To re-organise the Nicosia ACC, Tel Aviv ACC December 2019 Project Group: and Cairo ACC interface area. deadline on 25 December 2019. Approval Letter: RFG SE - Approval letter ref: EUR/NAT 20- Objective: EUR/NAT 20-0012.TEC of 6 Project Category: 0012.TEC of 6 January 2020. To further improve the airspace structure of Nicosia UIR at January 2020 Airspace Structure the interface with Tel Aviv FIR and Cairo FIR. ATC Sectors High Seas Proposal ID : 99.001 Status: Contributor: Comments: Project Name: ATS Route Improvement Egypt Implementation: State(s) and Org:  LAKTO is a border point with Cyprus.

Implemented EGY  GENIV is a new point but not Description: To implement a new ATS route segment L324 LAKTO – 26 MAR 2020 Originator(s): registered in ICARD. 94. GENIV. EGY

Objective: Project Category: To further improve the ATS route network in Egypt. ATS Routes Proposal ID : 75.082d Status: Contributor: Comments:

Project Name: Brest ACC re-organisation - Step 4 Implementation: State(s) and Org: Related proposals: 95. Implemented FRA Description:  75.082a 26 MAR 2020 To extend Rennes TMAs up to FL195.. Originator(s):  75.082b

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 33

EUROCONTROL Network Management Directorate

Objective: FRA  75.082e

To further improve the airspace structure within France FIR. Project Category: Airspace Structure Proposal ID : 83.016 Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org:  FRA was introduced on 17 DEC 2009 issues Implemented IRL and announced via AIC.

Description: 26 MAR 2020 Originator(s):  Around 5 years later the AIP To publish in AIP Ireland the Free Route Airspace EUROCONTROL Publication is missing or it is not in accordance with ERNIP Part 1. procedures. Project Category:  Coordination between the NM and Objective: AIP Ireland on AIP publication was already To adapt in AIP the FRA publication in accordance with the initiated. ERNIP.  At RNDSG/92 it was stated that Irish 96. CAA refused to approve such publication considering it as non- compliant with ICAO. An explanation on that conclusion is required as ERNIP FRA publication was coordinated at European level.

Related proposals:  87.028a  99.018 Proposal ID : 99.016 Status: Contributor: Comments: Project Name: New TSA near Kaunas Implementation: State(s) and Org: Implemented LTU Description: To implement new: 26 MAR 2020 Originator(s): a. TSA (TSA7) near Kaunas; LTU 97. b. SIDs/STARs from/to Kaunas (EYKA) airport. Project Category: Objective: Airspace Structure To fulfil MIL request for Training zone update and improve Traffic Flow to/from Kaunas Intl. Airport. Proposal ID : 97.023 Status: Contributor: Comments: Project Name: ATS Route deletion Norway Implementation: State(s) and Org: Linked to the removal of Z704 / Z705 in DK

98. Description: Implemented NOR and Maastricht and to the deletion of ATS 26 MAR 2020 DNK routes within NEFAB States.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 34

EUROCONTROL Network Management Directorate

To remove ATS routes Z704 and Z705 in Norway. Serial Number: ICAO High Seas Coordination Procedure (Serial EUR/NAT 19/06-HS-NOR FAB NEFAB No: EUR/NAT 19/06-HS-NOR) Objective: To further improve the airspace organisation within Norway Circulation Letter: Originator(s): Circulation Letter: EUR/NAT 19-0341.TEC and harmonize with Free Route operations. EUR/NAT 19-0341.TEC of 2 NOR of 2 August 2019, deadline for replies on 2 September 2019. August 2019 Project Category: Approval Letter: EUR/NAT 19-0388.TEC of Approval Letter: ATS Routes 4 September 2019. EUR/NAT 19-0388.TEC of 4 High Seas September 2019 Related proposals:  96.019 / 30.001  97.025  97.030 Proposal ID : 98.027 Status: Contributor: Comments: Project Name: 5LNC replacement by Norway Implementation: State(s) and Org:  Waypoint named as TIBLA is properly Implemented NOR registered and assigned to Czech Description: To replace 5LNC TIBLA within Norway. 26 MAR 2020 Originator(s): Republic information from ICARD and was never registered for Norway in Objective: EUROCONTROL ICARD. 99. To eliminate like sounding 5LNCs within ECAC airspace. Project Category:  Considering the agreed procedures for 5LNC replacement of any problematic 5LNC within ICAO EUR/NAT Region Norway was requested remove TIBLA from AIP Norway, ENR 4.4 and to replace it. Proposal ID : 97.030 Status: Contributor: Comments: Project Name: ATS Route deletion Norway Implementation: State(s) and Org:  Points will be kept for FRA operations.

Description: Implemented NOR  Route Rationalisation DK-SE FAB - To delete ATS route P603 in Norway 26 MAR 2020 FAB NEFAB Maastricht UAC and the deletion of Serial Number: DNK ATS routes within NEFAB States. Objective: EUR/NAT 19/11-HS-NOR ICAO  High Seas Coordination (Serial no: To rationalize the existing ATS route network, improve the EUR/NAT 19/11-HS-NOR) circulation airspace organisation within Norway and harmonize with Circulation Letter: Originator(s): letter ref: EUR/NAT 19-0408.TEC of 24 100. Free Route operations. EUR/NAT 19-0408.TEC of 24 NOR September 2019 circulated with September 2019 Project Category: deadline on 24 October 2019. Approval Approval Letter: ATS Routes letter ref: EUR/NAT 19-0508.TEC of 13 EUR/NAT 19-0508.TEC of 13 High Seas November 2019. November 2019 Related proposals:  96.019 / 30.001

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 35

EUROCONTROL Network Management Directorate

 97.023  97.025 Proposal ID : 69.238b / 12.001b Status: Contributor: Comments: Project Name: ATS Route Improvement Russian Implementation: State(s) and Org:  P727 DUBIN - LATLA was Federation Implemented RUS implemented by LVA on 13 DEC 2012.

26 MAR 2020 LVA  IATA supports to have LATLA in Description: westbound direction. To implement eastbound ATS route segment P727 LATLA - Originator(s): 101. UBANO - KOLET for ARR ULLI. LVA Related proposals:

Objective: Project Group: a. 69.238a / 12.001a To further improve the ATS route network within the Russian SG BALTIC

Federation. Project Category: ATS Routes Proposal ID : 96.021 / 29.030 Status: Contributor: Comments: Project Name: ATS routes deletion within NEFAB States Implementation: State(s) and Org:  AIC with additional details shall be

Description: Implemented EST published by DEC 2019. To delete partly ATS routes within NEFAB States. 23 APR 2020 EUROCONTROL  Latvia: no ATS route deletion. a) Norway: between FL135 - FL660. Connecting routes Serial Number: FAB Denmark/Sweden  Estonia: High Seas Coordination EUR/NAT 19/18-HS-EST FAB NEFAB Procedure (Serial no: EUR/NAT 19/18- to/from ENGM, ENTO, ENVA, ENBR shall not be deleted. Circulation Letter: FIN HS-EST) Circulation letter ref: b) Estonia: between FL095 - FL660. Connecting routes EUR/NAT 19-0507.TEC of 13 IACA EUR/NAT 19-0507.TEC of 13 to/from EFHK shall not be deleted. Some ATS routes on November 2019 IATA November 2019 with deadline for reply ICAO on 13 December 2019. Approval letter the FIR border between Estonia and Russian Approval Letter: LTU ref: EUR/NAT 19-0541.TEC of 16 Federation might also be not deleted. EUR/NAT 19-0541.TEC of 16 c) Finland: FL095 - FL660. Connecting routes to/from LVA December 2019. 102. December 2019 NOR EFHK and some other routes shall not be deleted.  Finland: High Seas Coordination RUS Procedure (Serial no: EUR/NAT 19/17- Objective: SWE To further improve the airspace organisation within NEFAB HS-FIN) Circulation letter ref: EUR/NAT ISL 19-0506.TEC of 13 November 2019 States. Originator(s): with deadline for reply on 13 December FAB NEFAB 2019. Approval letter ref: EUR/NAT 19-

Project Group: 0540.TEC of 16 December 2019. FAB NEFAB  Norway: “ATS routes in Norway will be SG BALTIC deleted stepwise from 2019 and deletion will be coordinated separately Project Category: for each route or set of routes”. Airspace Structure Related proposals:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 36

EUROCONTROL Network Management Directorate

ATS Routes 1. 96.019 / 30.001 CDRs Civil/Military Airspace Free Route Airspace High Seas RAD Route Redesignation Proposal ID : 99.011 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Estonia Implementation: State(s) and Org:  Will be done together with Full FRA in Implemented EST April 2020 Description: To change all existing CDR Categories into a single CDR 23 APR 2020 Originator(s): category. EST 103. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in SCC Bulgaria. Proposal ID : 99.014a Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - UK -Phase 1 Implementation: State(s) and Org: Implemented GBR Description: To change existing CDR Categories into a single CDR 23 APR 2020 Originator(s): category. GBR 104. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in United SCC Kingdom. Proposal ID : 74.064c Status: Contributor: Comments: Project Name: ATS Route Improvement Athinai FIR Implementation: State(s) and Org:  Connected to PBN implementation in Implemented GRC Athens TMA. Description: 1. To realign ATS route segment G8 / N/UN604 KRO - 23 APR 2020 Originator(s):  SOSIR 382423Ν 0250732Ε new OLIDA - LSV as KRO - SUSOR (crossing point with Serial Number: GRC waypoint on G/UG802 and G8- 105. G/UG802) - LSV. EUR/NAT 18/14-HS-GRC N/UN604 airways intersection. Project Group:  Cancellation of waypoint OLIDA 2. To withdraw ATS route G8 ATV - KRO - OLIDA - LSV Circulation Letter: RFG SE following the re-alignment of N604. EUR/NAT 18-0630.TEC of 21 382506Ν 0245328Ε. Project Category: Objective: December 2018  High Seas Coordination (Serial no: ATS Routes EUR/NAT 18/14-HS-GRC) Circulation

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 37

EUROCONTROL Network Management Directorate

To further improve ATS route network within Athinai FIR. High Seas letter ref: EUR/NAT 18-0630.TEC of 21 December 2018 - deadline on 21 January 2019. Proposal ID : 99.019 Status: Contributor: Comments: Project Name: Replace 5LNC replacement by Morocco Implementation: State(s) and Org: Implemented MAR Description: To replace 5LNC BEDUX by TOBZA. 23 APR 2020 Originator(s): ICAO Objective: 106. To avoid 5LNCs duplication within the EUR/NAT Region. Project Category: To improve the aeronautical information provided; 5LNC To be compliant with ICAO Annex 11.

Proposal ID : 97.042a Status: Contributor: Comments: Project Name: TMA re-organisation Warsaw FIR - Step 1 Implementation: State(s) and Org: Implemented POL Description: To re-organise TMA of Gdansk in order to allow CDA 23 APR 2020 Originator(s): 107. operations from more directions than it is available today. POL

Objective: Project Category: To further improve the airspace structure within Warsaw FIR CCO/CDO while enhancing CDA operations. TMA Proposal ID : 98.020a Status: Contributor: Comments: Project Name: Bratislava ACC re-sectorisation - Step 1 Implementation: State(s) and Org: Split of LZBBU3 and LZBBU4 sectors

Description: Implemented SVK according to traffic demand and based 23 APR 2020 upon the staff availability. To implement an additional geographical split for Bratislava Originator(s): 108. ACC sectorisation, allowing a 5 or 6 sector configuration. SVK Related proposals:

Objective: Project Category: 1. 98.020b To further improve the airspace structure within Bratislava Airspace Structure FIR while providing additional sector configuration to better ATC Sectors distribute traffic demand between ACC sectors. Proposal ID : 98.014 / 31.005 Status: Contributor: Comments: Project Name: ATS Route Network Improvement Kyiv Implementation: State(s) and Org:  ICAO Secretariat will initiate High Sea 109. UIR/ Odesa FIR Implemented UKR Regional Coordination as an outcome

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 38

EUROCONTROL Network Management Directorate

Description: 23 APR 2020 Originator(s): of RDGE/31. a. To implement eastbound ATS route segment M856 Serial Number: UKR  High Seas Coordination (Serial no: GOBLI - TARKA - DIGAM (FL275 - FL660) (re- EUR/NAT 19/12-HS-UKR EUR/NAT 19/12-HS-UKR) Project Group: alignment of existing ATS route). Circulation Letter: SG BLACK  Circulation letter ref: EUR/NAT 19- b. To re-designate existing ATS route M856 ODESE - 0412.TEC of 2 October 2019 circulated EUR/NAT 19-0412.TEC of 2 Project Category: PERED - ULGEK - DIGAM as P156. with deadline on 2 November 2019. October 2019 ATS Routes c. To remove existing ATS route segment M856 GOBLI -  Negative comments received from High Seas ODS. Russian Federation ref. EUR/NAT 19- d. To implement new 5LNC point - ODESE instead of 05376.TEC (NAE/CUP) Odesa ODS VOR/DME.  State letter reference EUR/NAT 19- Objective: 0536.TEC of 11 December 2019. To further improve the ATS route network within Kyiv UIR/ Odesa FIR. Proposal ID : 99.029 Status: Contributor: Comments: Project Name: New LEBL SIDs Implementation: State(s) and Org: Currently NATPI departures are using Implemented ESP existing MOPAS SIDs and dog-leg MOPAS Description: To impelement NATPI SIDs. 21 MAY 2020 Originator(s): DCT NATPI. This DCT will remain available 110. only for DEP LERS. Objective: ESP

To further improve airspace organisation for flights from Project Category: Barcelona (LEBL) airport. Airspace Structure TMA Proposal ID : 99.006 Status: Contributor: Comments: Project Name: France FRA FLOS Implementation: State(s) and Org:  Below FL195 the FLOS will be defined Implemented FRA by ATS routes and will be unchanged. Description: To change the FLOS in AIP France, ENR 1.7 from "East- 21 MAY 2020 Originator(s):  Subject to civil military coordination. West" to "North-South" above FL195. FRA 111. Objective: Project Category: To adapt the Flight Level Orientation Scheme in France with Airspace Structure existing procedures along ATS route network and prepare for FRA required procedures. Proposal ID : 99.024 Status: Contributor: Comments: Project Name: New GMTT SIDs Implementation: State(s) and Org: This will allow shorter option for DEP GMTT

112. Description: Implemented MAR via PIMOS by around 5NM. 21 MAY 2020 ESP To impelement BARPA SIDs.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 39

EUROCONTROL Network Management Directorate

Objective: Originator(s): To further improve airspace organisation for flights from MAR

Tanger (GMTT) airport. Project Category: Airspace Structure TMA Proposal ID : 98.029 Status: Contributor: Comments: Project Name: ATS Route Improvement Norway Implementation: State(s) and Org: New 5LNC - PENNO. Implemented NOR Description: Related proposals: To realign existing ATS-route Z201 as ROSVI - PENNO - 21 MAY 2020 Originator(s): 1. 98.025 113. EVABO. NOR

Objective: Project Category: To further improve the ATS-route network in Northern ATS Routes Norway. Proposal ID : 98.057 Status: Contributor: Comments: Project Name: ATS Route Improvement Norway Implementation: State(s) and Org: MOKAX: 69°04'29.00" N 019°55'29.00" E - Implemented NOR new 5LNC Description: To realign the following bidirectional ATS routes: 21 MAY 2020 Originator(s): Related proposals: 114. a) P853 as RIXEM - MOKAX - TRO; NOR a. 98.025 b) T399 as ABASU - MOKAX - KUNUB. Project Category: Objective: ATS Routes To further improve the ATS route network in Norway. Proposal ID : 98.053 Status: Contributor: Comments: Project Name: DKR VOR replacement Implementation: State(s) and Org: Pending implementation of ESSB RNAV 1 Implemented SWE SID/STAR system. Description: To replace DKR by PETEV in ATS routes L87, N88 and 21 MAY 2020 Originator(s): 115. N872. SWE

Objective: Project Category: To replace DKR VOR in Sweden which is u/s. 5LNC Proposal ID : 98.052 Status: Contributor: Comments: Project Name: FBZ ES D184/185 Implementation: State(s) and Org: Implemented SWE 116. Description: To create FBZ ES D184/185. 21 MAY 2020 Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 40

EUROCONTROL Network Management Directorate

Objective: SWE

To create a flight planning buffer in the ESAA part of ES Project Category: D184/185. Civil/Military Airspace Proposal ID : 96.029 / 30.003 Status: Contributor: Comments: Project Name: KABAN re-opening Implementation: State(s) and Org:  The ATS route over KABAN will be

Description: Implemented TUR available for flights above FL260 in 21 MAY 2020 IRQ respect to the currently existing FAA To re-open for traffic existing westbound boundary point KABAN. Originator(s): SFAR 77.  For the EASA SIB, Iraq is in Objective: TUR negotiations with EASA to include the To further improve ATS route network between Ankara FIR IRQ possible new ATS route within and Baghdad FIR. Project Group: Baghdad FIR in an updated version of 117. SG BLACK the SIB. Project Category:  Careful assessment of traffic flows ATS Routes distribution and network effect of all RAD possible options with Operational Stakeholders in the European and Middle East Regions was required following an agreement on KABAN re- opening.  Publication via NOTAM. Proposal ID : 99.017 Status: Contributor: Comments: Project Name: Establishment of LCD_BARBARA 3 Implementation: State(s) and Org: - AMC manageable area, naval artillery Planned CYP activities, notified by NOTAM. Description: To establish new Danger Area LCD_BARBARA 3. 18 JUN 2020 Originator(s): High Seas Coordination Procedure Serial Number: - Circulation Letter Ref: EUR/NAT 20- Objective: CYP EUR/NAT 20/03-HS-CYP 0122.TEC of 26 February 2020, deadline To facilitate training needs of United Nations Interim Force in Project Category: for reply 26 March 2020. 118. Lebanon (UNIFIL). Circulation Letter: High Seas EUR/NAT 20-0122.TEC of 26 - Approval Letter Ref: EUR/NAT 20- February 2020 0195.TEC of 30 March 2020.

Approval Letter: EUR/NAT 20-0195.TEC of 30 March 2020

Proposal ID : 98.050 Status: Contributor: Comments: 119. Project Name: ATS route Improvement Bremen ACC - Implementation: State(s) and Org: FARCU is a new FIR border point between

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 41

EUROCONTROL Network Management Directorate

Warsaw ACC Confirmed DEU Germany and Poland. 18 JUN 2020 POL Description: To implement the following new ATS route segments: Originator(s): a) P45 FARCU - USEDU; DEU b) P46 TORLO - FARCU. Project Category: Objective: ATS Routes To further improve the ATS route network between Bremen ACC and Warsaw ACC while separating arrivals to EPSC from departures from EDDT/ EDDB via point BINKA. Proposal ID : 98.047 Status: Contributor: Comments: Project Name: PBN Implementation at EDDH, EDHI, Implementation: State(s) and Org: The conventional procedures will be EDHL, EDHK Confirmed DEU reduced to a backbone network, only

Description: 18 JUN 2020 Originator(s): available for those flights that are not 1. To implement new routes T909, T812, T813, T814, DEU capable of RNAV-1. The formerly transition and FMS overlays T815 for PBN implementation at EDDH/EDHI, EDHL Project Category: For EDDH/EDHI : will be transformed into proper RNAV-1 5LNC STARs, APCHs and SIDs. a) new IAF for conventional flights - LYE Locator ATS Routes b) Connection RARUP - LYE via HAM ; PBN c) Connection LUGEG - LYE: New route T812 ; 120. d) Connection RAMAR - LYE: New route T813 ; e) Connection BOGMU - LYE: New touye T814 ; f) Connection HAM - LYE: New route T815. 2. To reduce the NAV Aids in this region as follows: a. Elbe VOR/DME (LBV) replaced by 5LNC ELSOB; b. Michaelsdorf DVOR (MIC) replaced by 5LNC MICOS; c. Lübeck DVOR (LUB) replaced by 5LNC LUGEG.

Objective: To improve the arrivals at EDDH, EDHI, EDHL Proposal ID : 99.009 Status: Contributor: Comments: Project Name: Correct CDR publication of L18 and Q60 Implementation: State(s) and Org: Notes:

Description: Confirmed GBR a. Currently as both ATS route segments 18 JUN 2020 have different availability on different 121. To publish, in accordance with ERNIP Part 1, the whole daily Originator(s): period of use of the following CDRs: EUROCONTROL directions in AIP terms “westbound” and “eastbound” are used, which a. L18 MEDOG - LIPGO; Project Category: b. Q60 MORAG - UNGUS. seems is unclear and misleading.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 42

EUROCONTROL Network Management Directorate

Objective: CDRs b. In case of different applicability times To clarify the availability of ATS routes and conditions on same bi-directional ATS route segment but on opposite directions, these terms shall not be used due to lack of definition. The reference shall be based to definition of ATS route segment direction by significant points order. c. Coordination is in progress in UK and possible changes can be expected on 23 APR 2020.

Proposal ID : 97.008 Status: Contributor: Comments: Project Name: New FRA (I) point in POLFRA Implementation: State(s) and Org:  Position proposed is east of existing Confirmed POL point MIRVO, just outside the D24 Description: To establish new FRA (I) point LAJQU within POLFRA area 18 JUN 2020 Originator(s): Buffer zone. 122. also allowing shorter avoidance of D24Z. IATA  Proposal for avoiding D24Z more efficient going north via ADVAB Objective: Project Category: towards BABEN. To allow shorter avoidance of D24Z in FRA environment. Free Route Airspace  Point Name is LAJQU Proposal ID : 99.002 Status: Contributor: Comments:

Project Name: ATS Route Improvements Sweden on Implementation: State(s) and Org: Related proposals: L727, Y41, Z132 Confirmed SWE  98.054 Description: 18 JUN 2020 Originator(s): 1. To re-align L727 from PENOR - IPKAL - GETPA - SWE

MOGLU to PENOR - NEGIL - LATKU - KORET - Project Category: GETPA - MOGLU, uni-directional eastbound, FL095 - ATS Routes FL660. 2. To re-align Y41 from LARMA - XENTA to LARMA - 123. SABAK, present Y41 segment KELIN - XENTA - REPKU gets new designator Y43 and segment KELIN - XENTA becomes uni-directional eastbound. 3. To implement new ATS route segment Y44 PENOR - SABAK, uni-directional westbound, FL095 - FL660. 4. To delete Z132 segment IPKAL - LATKU and change segment to LATKU - XENTA uni-directional eastbound.

Objective:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 43

EUROCONTROL Network Management Directorate

To further improve the ATS route network in Sweden. Proposal ID : 98.054 Status: Contributor: Comments: Project Name: PCA redesign and ATS route relocation Implementation: State(s) and Org: High Seas Coordination Procedure (Serial Confirmed SWE no: EUR/NAT 20/02-HS-SWE) Circulation Description: To redesign PCA L71, S8 and S9 which affects ATS routes 18 JUN 2020 Originator(s): Letter: EUR/NAT 20-0108.TEC of 18 L727, (Y41), Z132 and FRA connecting from/to ADs within Serial Number: SWE February 2020 and deadline for replies: 18 Oslo/Farris TMA (only in ESAA FIR). EUR/NAT 20/02-HS-SWE March 2020 Project Category: Approval letter: EUR/NAT 20-0193.TEC of 124. Objective: Circulation Letter: Civil/Military Airspace EUR/NAT 20-0108.TEC of 18 30 March 2020. to offload PCAs from penetrating GAT. High Seas February 2020 Related proposals:

Approval Letter:  99.002 EUR/NAT 20-0193.TEC of 30 March 2020

Proposal ID : 76.068b Status: Contributor: Comments: Project Name: Istanbul New Airport/ LTFM - Phase 1b Implementation: State(s) and Org: That might also result in a TMA re-design.

Description: Confirmed TUR Related proposals: 1. To implement 3rd RWY at Istanbul New Airport (LTFM). 18 JUN 2020 BGR  76.068a GRC 2. To re-organise the airspace of Istanbul FIR, Ankara  95.008 / 28.024 ROU 125. FIR and adjacent FIRs accordingly, if required.

Objective: Originator(s): TUR To further improve the airspace structure and to accommodate the traffic growth for the coming years. Project Category: Airspace Structure TMA Proposal ID : 99.012 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Italy Implementation: State(s) and Org: Planned ITA Description: To change all existing CDR Categories into a single CDR 16 JUL 2020 Originator(s): 126. category. ITA

Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in Italy. SCC Proposal ID : 98.042 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 44

EUROCONTROL Network Management Directorate

Project Name: UK CTA Improvements Implementation: State(s) and Org: Planned GBR Description: 1. To establish Borders & Yorkshire CTAs DB/FL195 and 13 AUG 2020 Originator(s): Northern CTA FL195/FL245 to replace the airspace GBR

currently described by airways L612, N57, N601, N864 Project Category: 127. (partial), P16, P17, P18 (partial) and T256. AIP 2. To transfer airways L612, N57, N601, P16, P17 and Airspace Structure T256 from AIP ENR3.1 into ENR3.3. ATS Routes Objective: To re-define UK airspace below FL245 and re-design a series of CTAs to enable the ATS Route network to be correctly promulgated in ENR3.3 of the UK AIP. Proposal ID : 98.030 Status: Contributor: Comments: Project Name: ATS (helicopter) Route improvement - Implementation: State(s) and Org: High Seas Coordination Procedure (Serial Norway Planned NOR no: EUR/NAT 19-16-HS-NOR) 13 AUG 2020 ICAO Circulation letter ref: EUR/NAT 19- Description: 1. To Implement the following new ATS (helicopter) routes: Circulation Letter: Originator(s): 0499.TEC of 7 November 2019 deadline on a. KY957 XUNEV - BEPVU - ENFOB - ABGAB - EUR/NAT 19-0499.TEC of 7 NOR 5 December 2019. EVGOP - OSKAK; November 2019 Approval letter ref: EUR/NAT 19-0531.TEC Project Category: b. KY959 XUNEV - IFTID - LOLAW; Approval Letter: of 6 December 2019. 128. ATS Routes c. KY960 NOSVA - USIRA - OSKAK. EUR/NAT 19-0531.TEC of 6 High Seas 2. To extend the following ATS (helicopter) route: KY953 December 2019 ALAVU - POFMA - DIPEW - ADNUM - ABGOR - (GALTU - VAVAK - OMIDU).

Objective: To further improve the ATS (helicopter) route network in Norway. Proposal ID : 97.021 Status: Contributor: Comments: Project Name: Implement New ATS Route for approach Implementation: State(s) and Org: TISAD is IAF for the approach at LRSM to LRSM Planned ROU 13 AUG 2020 HUN Description: 129. To implement ATS Route Z243 KARIL - TISAD, eastbound, Originator(s): FL055 - FL285 with the purpose of shortening the distance ROU flown for arrivals using the VOR RWY01 approach at LRSM. Project Category: Objective: ATS Routes

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 45

EUROCONTROL Network Management Directorate

To improve the approach at LRSM. Proposal ID : 98.062 Status: Contributor: Comments: Project Name: Preparation for PBN implementation Implementation: State(s) and Org:  Formerly transition and FMS overlays EDDE airport Planned DEU will be transformed into proper RNAV-1

Description: 10 SEP 2020 Originator(s): STARs and SIDs. 1. To implement the following new ATS route segments: DEU  To reduce complexity the SIDs will be shortened and reduced as follows: a. Q243 NEVKO – BAMKI - NIBIL. Project Category: ◦ TABAT and BAMKI SIDs will be b. Q244 NEVKO – TABAT – KULOK – BAROB – ATS Routes NIBIL. replaced by NEVKO SID; 130. PBN 2. To release route designators T189 and T192 as of 10 ◦ SOMIX SID will be deleted, traffic SEP 2020. has to use LASTO SID;

Objective: ◦ PILAM and ERSIL SIDs are kept; To further improve the ATS route network while offering ◦ new ERF SID for non RNAV-1 DEP. a connection from NEVKO to the ATS route network (TABAT and BAMKI). Related proposals:  84.074 Proposal ID : 97.031 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Planned GBR Description: To remove the en-route dependency from WCO and WOD 10 SEP 2020 Originator(s): NDBs and BNN and MID DVOR will result in the BNN GBR

Hold becoming RNAV'd and the following STARs being Project Category: made RNAV5 and designated by their start fix as follows as ATS Routes well as re-designating some other STARs in accordance with ICAO: a. GROVE 1B will become SILVA 1B; 131. b. GROVE 1C will be extended back to HEMEL and become HEMEL 1B;; c. JACKO 1A will become SILVA 1C; d. WILLO 3B will become KIDLI 1G; e. New STAR will be established from DISIT and become DISIT 1G; f. BNN 4A will become HON 1H; g. BNN 1B will become NUGRA 1H; h. BNN 1D will become BEDEK 1X; i. BNN 1E will become LAM 1Z;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 46

EUROCONTROL Network Management Directorate

j. LOREL 5A will become SILVA 1L; k. LOREL 1B will be truncated at SILVA and will use SILVA 1L; l. LOREL 2L will be removed and will use SILVA 1L; m. SPEAR 1A will be truncated and become SILVA 1S; n. TIMBA 1D will become MID 1X; o. ASKEY 5A, ASKEY 1B, BNN 1C, BOVVA 4A, BOVVA 1B, BOVVA 1C, BOVVA 1D, BOVVA 1E are all removed; p. L89 will be re-designated as N16 extension and also link to existing N16 at GWC; q. KATHY - HAZEL - WOD will be replaced by ATS route designated as L89.

Objective: To remove the en-route dependency on the WCO NDB & BNN DVOR. Proposal ID : 98.004 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Planned GBR Description: To remove the en-route dependency on Daventry/ DTY 10 SEP 2020 Originator(s): DVOR will result in the RNAVing of the CHASE & PIGOT GBR

Hold which will become an UPDUK Hold and some STARs Project Category: into these Holds will be made RNAV5 and some new STARs ATS Routes will be established to ensure appropriate Descent Planning levels are captured in the RNAV Coding Tables and re- designated as per ICAO as follows: a. The CHASE 3A STAR will be removed; 132. b. The CHASE 2D will be extended to MALUD and become MALUD 1B; c. The CHASE 1C will become WAL 1B; d. A STAR via MAKUX will be established and be designated MAKUX 1B; e. A STAR via NOSLO will be established and be designated NOSLO 1B; f. The PIGOT 1J will be extended to HEMEL and become a HEMEL 1E; g. The PIGOT 1H will become a DTY 1E.

Objective:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 47

EUROCONTROL Network Management Directorate

Remove the en-route dependency on DTY DVOR and facilitate the eventual removal of the DVOR. Proposal ID : 89.043 Status: Contributor: Comments: Project Name: RAD Promulgation Ankara FIR Sofia FIR Implementation: State(s) and Org: Not acceptable for BULATSA

Description: Proposed BGR summer 2020 TUR To modify RAD restrictions LBLT1005 (NEGEM) and LBLT1006 (ODERO) in order to allow traffic from Arabian Originator(s): Peninsula to use the relevant connections (DASIS and any POL

133. new point at interface Ankara FIR / Tehran FIR) for flights to Project Group: north Europe and North America via point NEGEN and RFG SE ODERO respectively. Project Category: Objective: RAD To further improve ATS route options via Ankara FIR and Sofia FIR. Proposal ID : 94.012 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  This 5LNC is used worldwide for 5 Proposed ESP significant points and the Priority State Description: To replace 5LNC INDIA. summer 2020 Originator(s): identified by ICAO to keep the code is USA. Objective: ICAO  Not registered in ICARD and Spain To resolve worldwide 5LNCs duplication. Project Category: 134. was notified by ICAO DM on 4 APR 5LNC 2018 to take action.  As per JeppView located in Zaragoza TMA.  Point is used by the Spanish military authority. Proposal ID : 94.013 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  This 5LNC is used worldwide for 4 Proposed ESP significant points and the Priority State Description: To replace 5LNC MITOS. summer 2020 Originator(s): identified by ICAO to keep the code is Malaysia. 135. Objective: ICAO  Not registered in ICARD and Spain To resolve worldwide 5LNCs duplication. Project Category: was notified by ICAO DM on 4 APR 5LNC 2018 to take action.  Crossing point between B46/UN851

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 48

EUROCONTROL Network Management Directorate

and N/UN608.  The point is part of an SID in Spain. Proposal ID : 94.015 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  This 5LNC is used worldwide for 4 Proposed ESP significant points and the Priority State Description: To replace 5LNC PINTO. summer 2020 Originator(s): identified by ICAO to keep the code is USA. 136. Objective: ICAO  Not registered in ICARD and Spain To resolve worldwide 5LNCs duplication. Project Category: was notified by ICAO DM on 4 APR 5LNC 2018 to take action.  In use at LEPA airport. Proposal ID : 94.017 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  This 5LNC is used worldwide for 4 Proposed ESP significant points and the Priority State Description: To replace 5LNC VERDE. summer 2020 Originator(s): identified by ICAO to keep the code is USA. Objective: ICAO  Not registered in ICARD and Spain To resolve worldwide 5LNCs duplication. Project Category: 137. was notified by ICAO DM on 4 APR 5LNC 2018 to take action.  Real purpose of existence needs to be re-verified.  Point is used by the Spanish military authority. Proposal ID : 88.031c Status: Contributor: Comments: Project Name: ATS route improvement Madrid FIR Implementation: State(s) and Org: Proposed by Spain holding/descent Proposed ESP procedures via AMR are unacceptable by Description: To allow proper descend when LER-63 is active up to summer 2020 Originator(s): AOs and CFSPs. Update will be provided at RNDSG/100 FL260 by: EUROCONTROL

a) Introducing new significant points outside of lateral Project Category: Related proposals: 138. borders of LER-63 on ATS routes B112/UL112, ATS Routes  88.031a W810/UY810, G850/UN860, G53/UM143 and  88.031b H372/UM192; b) Publishing new flight plan arrival procedures allowing proper descent - new STARs via significant points in a. above.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 49

EUROCONTROL Network Management Directorate

Objective: To further improve flight planning options and ATS route network for flights to/from Almeria (LEAM) airport. Proposal ID : 94.016 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  This 5LNC is used worldwide for 4 Proposed ESP significant points and the Priority State Description: To replace 5LNC PRADA. summer 2020 Originator(s): identified by ICAO to keep the code is Canada. Objective: ICAO  Not registered in ICARD and Spain To resolve worldwide 5LNCs duplication. Project Category: 139. was notified by ICAO DM on 4 APR 5LNC 2018 to take action.  Real purpose of existence needs to be re-verified.  Point is used by the Spanish military authority. Proposal ID : 94.014 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  This 5LNC is used worldwide for 4 Proposed ESP significant points and the Priority State Description: To replace 5LNC OSCAR. summer 2020 Originator(s): identified by ICAO to keep the code is USA. Objective: ICAO  Not registered in ICARD and Spain 140. To resolve worldwide 5LNCs duplication. Project Category: was notified by ICAO DM on 4 APR 5LNC 2018 to take action.  Located at area of LETO airport.  Point is used by the Spanish military authority. Proposal ID : 97.010 Status: Contributor: Comments: Project Name: Unnamed Significant Points - Phase 3 Implementation: State(s) and Org: Remaining points are on routes :A1 (3 pts),

Description: Proposed FRA B37 (3 pts), G32 (2 pts), J41 (1 pt), R226 (1 summer 2020 pt), W110 (1 pt) Phase 3: To remove from ENR 3 in AIP 3 unnamed Originator(s): 141. significant points. EUROCONTROL Related proposals:

Objective: Project Category: 1. 89.020b To further improve the AIP airspace data publication. AIP a. 89.020c ATS Routes Proposal ID : 99.010 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 50

EUROCONTROL Network Management Directorate

Project Name: Correct CDR publication of UN29 & UZ57 Implementation: State(s) and Org: Notes: Proposed FRA 1. Currently both ATS routes are Description: To publish, in accordance with ERNIP Part 1, the whole daily summer 2020 Originator(s): published as “CDR1. 0100-0800 (SUM: period of use of the following CDRs: EUROCONTROL - 1HR).” without reference on a) UN29 REGHI - BULOX; availability for the rest or the period. Project Category: 2. Despite being discussed by AIOPS b) UZ57 NERLA - GONEK. CDRs meetings for almost 3 years there is no Objective: harmonized way of expression of time 142. Tu clarify the availability of ATS routes in AIP publication. 3. Normally, if interpretation of NM is correct, based on approved NMOC time expression and Doc 8126, publication shall be “CDR 1: MON - SUN 01:00 - 08:00 (00:00 - 07:00), Rest of time: Not available or By ATC or PERM”.

Proposal ID : 95.020 Status: Contributor: Comments: Project Name: 5LNC replacement by France Implementation: State(s) and Org: BASTO is reserved in ICARD for United Proposed FRA States of America. Description: To replace existing 5LNC BASTO. summer 2020 Originator(s): Used by Spanish military. 143. EUROCONTROL Objective: To avoid 5LNCs duplication within the ECAC area of the Project Category: ICAO EUR/NAT region, to improve the aeronautical 5LNC information provided and be compliant with ICAO Annex 11. Proposal ID : 98.010 Status: Contributor: Comments: Project Name: EGPX FIR Direct Implementation: State(s) and Org:  Previously AOs filed option SAB DCT Proposed GBR TARTN, but it was closed by RAD Description: To allow Direct flight planning option BEVAM DCT HAVEN, summer 2020 Originator(s): restriction EG50346 due to to the above FL195 and when no military activity. IATA complexity of the ATC sector from the east. Objective: Project Category: 144.  AOs also stressed on problems with To further improve flight planning options within Scottish FIR DCTs some pilots not wanting to descend RAD into uncontrolled airspace. Therefore lower limit of FL195 is proposed as it is Class G airspace below.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 51

EUROCONTROL Network Management Directorate

 Currently ARR EGPH fly via BEVAM UP16 NATEB Y96 HAVEN STAR.  Proposed option would shorten the distance by 20 NM and 3 minutes flight time, compared to option via NATEB.  Proposal already presented to NATS.  Alternative, more realistic options: CUTEL - NATEB or ROBEM - AGPED. Proposal ID : 98.044 Status: Contributor: Comments: Project Name: FBZ AIP Publication Implementation: State(s) and Org: In RAD1913 (5 DEC 2019) there are 9 Proposed GBR (nine) FUA restrictions by UK for relevant Description: To publish in AIP UK the 9 FBZs for EGD701 area. summer 2020 Originator(s): sub-parts FBZs for EGD701 area. The 145. issue reported was that these FBZs are not Objective: EUROCONTROL published in AIP UK and there is no To perform with ERNIP requirements and align the airspace Project Category: justification to Operational Stakeholders for objects to existing RAD Appendix 7 restrictions. AIP the source of publication. Proposal ID : 94.021 Status: Contributor: Comments: Project Name: 5LNC replacement by Israel Implementation: State(s) and Org:  This 5LNC is used worldwide for 4 Proposed ISR significant points and the Priority State Description: To replace 5LNC ESTER. summer 2020 Originator(s): identified by ICAO to keep the code is USA. Objective: ICAO  Not registered in ICARD and Israel was 146. To resolve worldwide 5LNCs duplication. Project Category: notified by ICAO DM on 4 APR 2018 to 5LNC take action.  Located within Ben Gurion TMA as entry/exit on ATS routes T80, T84 and T85. Proposal ID : 88.013 Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org: issues Proposed MKD

Description: summer 2020 Originator(s): 147. To adapt existing ATS routes definition and template in AIP, EUROCONTROL ENR 3 in accordance with Doc.10066. Project Category: Objective: AIP To resolve airspace data publication inconsistencies in State

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 52

EUROCONTROL Network Management Directorate

AIP. Proposal ID : 98.018 Status: Contributor: Comments: Project Name: ATS Route Improvement Amsterdam FIR Implementation: State(s) and Org:  Currently there is no way to flight plan Proposed NLD a C130H across Dutch airspace below Description: To allow “low level” GAT flight planning options below summer 2020 Originator(s): FL245 using GAT. When there was FL245 within Amsterdam FIR. U.S.A.F.E TACAN airways TB6 etc. USAF could flight plan a mission over EHAA Objective: Project Category: airspace with no problems by filing 148. To further improve flight planning options for USAF flights ATS Routes OAT. within Amsterdam FIR.  This has a significant impact when attempting to flight plan any C130s across Dutch/MUAC airspace. USAF has had to over Denmark to/from Poland to get to the UK. Proposal ID : 86.029 Status: Contributor: Comments: Project Name: ECAC States AIP publication issues Implementation: State(s) and Org:  Currently in accordance with AIP Norway Proposed NOR Norway only three SIDs VEMIN4A,

Description: summer 2020 Originator(s): VEMIN9D and VIBUK5C exist for To adapt coding of ENGM RNAV SIDs via VEMIN and EUROCONTROL RWY01L/19R connecting 6 other waypoints. These connections after VIBUK. Project Category: VEMIN and VIBUK are named - Objective: AIP “transitions” where the same named To align AIP publication in accordance with ICAO Annex 11 “transitions” have different and Doc 8168. environmental performances.  These 6 waypoints are specified 149. significant points on designated ATS routes, at which the en-route phase of a flight commences. The en-route phase cannot start at VEMIN or VIBUK as there is no connection with ATS routes.  Normally these NUVSA, EVTOG, ATLAP, TOR, MASEV and OKSAT “transitions” shall be codded as separate SIDs using these en-route name-codes. Proposal ID : 81.084 / 15.001 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 53

EUROCONTROL Network Management Directorate

Project Name: ATS Route Improvement Russian Implementation: State(s) and Org:  Operators request minimum opening Federation Proposed RUS times between 2240z to 2400z/0000z summer 2020 FIN (local time: 2:40am-4:00am). Description: To implement westbound ATS route PEMIL - TOGRU - Originator(s):  Russian Federation: further studies 150. AGAMO. IATA required.

Objective: Project Group: To further improve ATS route network within the Russian SG BALTIC

Federation. Project Category: ATS Routes Proposal ID : 99.007 Status: Contributor: Comments: Project Name: New APP Sectors Implementation: State(s) and Org: Currently 2 Upper Sectors FL155 - FL245 Proposed TUR exists at Menderes APP and one Upper Description: To implement new UPPER Sectors within Izmir TMA and summer 2020 Originator(s): Sector 9500 FT AMSL - FL245. 151. Dalaman TMA. TUR

Objective: Project Group: To further improve airspace organisation within Istanbul FIR RFG SE

for flights to Izmir, Bodrum and Dalaman Airports. Project Category: ATC Sectors Proposal ID : 64.031 Status: Contributor: Comments: Project Name: Berlin Brandenburg International (BER) Implementation: State(s) and Org:  EDDB:The planned openings of the airport Planned DEU new Berlin Brandenburg International

Description: 08 OCT 2020 Originator(s): (BER) airport on 03.06.2012 and New Berlin Brandenburg International (BER) airport: DEU 27.10.2013 were postponed.  EDDB : The new Berling Brandenburg a) to establish a second runway at BER airport (current Project Category: International airport will start operations Berlin Schoenefeld airport); Airspace Structure during the night og 30-31 October b) to establish independent parallel runway operations; TMA 152. c) new/modified SIDs/STARs; 2020, publication will be made for d) operational procedures; AIRAC 8 Oct 2020 and de-activated by e) to adjust Terminal sectors; NOTAM until opening. f) one additional departure sector;  EDDT: Berlin-Tegel planned to be g) to raise the DFL from FL165 to FL205. closed 2-4 weeks after EDDB is in operation. Objective: To further improve the airspace structure within Bremen FIR  Possible ATFM Regulations due to by expansion of Berlin Schoenefeld airport to become Berlin acclimatization of ACC and TWR staff Brandenburg International (BER) airport. (new airspace C structure and

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 54

EUROCONTROL Network Management Directorate

DEP/ARR procedures). Proposal ID : 84.036 Status: Contributor: Comments: Project Name: 5LNC replacement by Spain Implementation: State(s) and Org:  MAROT is with double reservation in Planned ESP ICARD for Russian Federation and Description: To replace existing 5LNC MAROT. 08 OCT 2020 Originator(s): Haiti.  Proposal for replacement is based on 153. Objective: EUROCONTROL “Common criteria for replacement of To avoid 5LNCs duplication within the ECAC area of the ICAO duplicated 5LNCs” as point is not ICAO EUR/NAT region, to improve the aeronautical Project Category: reserved for Spain. information provided and be compliant with ICAO Annex 11. 5LNC Proposal ID : 89.005 Status: Contributor: Comments: Project Name: EUR/NAT States AIP en-route publication Implementation: State(s) and Org:  Contrary to Annex 15 AIP Spain issue Spain Planned ESP includes ATS route segment UM744

Description: 08 OCT 2020 Originator(s): LASIB - ROSAL which is within Lisbon To properly adapt the AIP publication of ATS route UM744 as EUROCONTROL FIR. Air traffic services is delegated from Lisbon ACC to Seville ACC ROSAL - CARBO instead of LASIB - ROSAL - CARBO. Project Category: between LASIB and ROSAL. 154. Objective: AIP  In AIP Spain UM744 LASIB - ROSAL To resolve airspace data publication inconsistencies in State ATS Routes … - SVL (FL245 - FL460) is published AIP. as CDR2 / PERM.  In AIP Portugal UM744 LASIB - ROSAL (FL195 - FL460) is published BTN FL 245 / FL 460 H24. Proposal ID : 50.053c Status: Contributor: Comments: Project Name: Lisboa / Casablanca / Canarias Axis Implementation: State(s) and Org: 22:00 - 06:00 UTC is MORFRA. Phase 1c Planned ESP Related proposals: Description: 08 OCT 2020 MAR  50.053a FAB SW To review the airspace organisation on the Lisboa /  50.053b Casablanca / Canarias axis by allowing the following Daily Originator(s): a. 50.053d 155. 06:00 - 22:00 UTC DCT options: ESP a. 50.053e a. DESUM DCT XELER; MAR 1. 73.052

b. XELER DCT MARJA; Project Group: a. 75.022 c. MARJA DCT OSDAM. FAB SW Objective: RFG SW

To further improve the ATS route network and airspace Project Category: organisation within Canarias FIR/UIR, Casablanca FIR/UIR

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 55

EUROCONTROL Network Management Directorate

and Lisboa FIR. DCTs Proposal ID : 50.053d Status: Contributor: Comments: Project Name: Lisboa / Casablanca / Canarias Axis Implementation: State(s) and Org:  Phase 1 of the project started 30 JAN Phase 1d Planned ESP 2020;

Description: 08 OCT 2020 MAR  Phase 2 of the project - complete re- FAB SW organisation of the Interfaces - in line To dualise VASTO point by properly utilising new 5LNC point DESUM at Canarias/Agadir ACC Interface by establishment Originator(s): with new Canarias TMA re-organisation - is planned for summer 2022. of new SIDs DESUM for GCRR (Lanzarote) and GCFV ESP 156. (Fuerteventura) in Canarias ACC. MAR Related proposals:

Objective: Project Group: a. 50.053a To further improve the ATS route network and airspace FAB SW  50.053b organisation within Canarias FIR/UIR and Casablanca RFG SW  50.053c

FIR/UIR. Project Category:  50.053e Airspace Structure  60.034b DCTs a. 73.052 1. 75.022 Proposal ID : 96.017 Status: Contributor: Comments: Project Name: Decommission FSK and STT Navaids Implementation: State(s) and Org: Planned NOR Description: To realign RNAV route Z202 ...STO - LURUX - LEBDO... 08 OCT 2020 Originator(s): (LURUX replaces STT). NOR 157. Objective: Project Group: To decommision NAVAIDS FSK and STT. FAB NEFAB

Project Category: ATS Routes Proposal ID : 97.007 Status: Contributor: Comments: Project Name: Single CDR category (SCC) - Bulgaria Implementation: State(s) and Org: Planned BGR Description: To change all existing CDR Categories into a single CDR 05 NOV 2020 Originator(s): category. BGR 158. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in SCC Bulgaria.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 56

EUROCONTROL Network Management Directorate

Proposal ID : 99.035 Status: Contributor: Comments: Project Name: new FAWUR STAR Frankfurt/ EDDF Implementation: State(s) and Org: New waypoint FAWUR. Planned DEU Description: a. To delete ASPAT STAR (EDDF). 05 NOV 2020 Originator(s): b. To introduce new HTO-STAR (RNAV 1) from FAWUR DEU

with vertical constraints (EDDF). Project Category: 159. c. To adopt T161 to connect to new FAWUR STAR. ATS Routes Objective: To optimize the arrival/ STAR structure at Frankfurt/ EDDF airport. To avoid hand-over conflicts at the München ACC/ Langen ACC interface. Proposal ID : 95.021 Status: Contributor: Comments: Project Name: 5LNC replacement by France Implementation: State(s) and Org: NISMO is reserved in ICARD for Japan. Planned FRA France selected WIQMO as a replacement. Description: To replace existing 5LNC NISMO with WIQMO 05 NOV 2020 Originator(s): Implementation TBA 160. EUROCONTROL Objective: To avoid 5LNCs duplication within the ECAC area of the Project Category: ICAO EUR/NAT region, to improve the aeronautical 5LNC information provided and be compliant with ICAO Annex 11. Proposal ID : 97.006c Status: Contributor: Comments:

Project Name: Single CDR category (SCC) - France - Implementation: State(s) and Org: Related proposals: Phase 3 Planned FRA  97.006a Description: 05 NOV 2020 Originator(s): a. 97.006b To change all existing CDR Categories into a single CDR FRA 161. category. Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in France. Proposal ID : 64.066b / 09.012b Status: Contributor: Comments: Project Name: Tbilisi TMA Implementation: State(s) and Org:  For ARR via TISOT at first phase

162. Planned GEO shorter flight planning options will be Description: 1. To reconfigure existing Tbilisi TMA. 05 NOV 2020 Originator(s): allowed by RAD Appendix 5. 2. To introduce new RNAV1 (GNSS) SIDs/STARs for EUROCONTROL  Currently arrivals follow ATS routes

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 57

EUROCONTROL Network Management Directorate

Tbilisi (UGTB) airport including STARs via TISOT. GEO G482 / N82 and then STAR via DF with extension of 60NM. Objective: Project Group: To further improve the airspace organisation within Tbilisi SG BLACK Related proposals:

FIR. Project Category: 1. 64.066a / 09.012a TMA Proposal ID : 88.008 / 23.022 Status: Contributor: Comments: Project Name: ECAC States AIP publication issues Implementation: State(s) and Org:  In accordance with ICAO the basic Georgia Planned GEO indicator shall be the name or name-

Description: 05 NOV 2020 Originator(s): code of the significant point where a To properly designate all UGTB STARs in accordance with EUROCONTROL standard arrival route begins.  Currently for few STARs the 163. Annex 11. Project Group: description defines that names used for Objective: RFG SE coding are not these points where a To adapt the STAR coding. SG BLACK STAR begins. Project Category: AIP Proposal ID : 99.032 / 31.018 Status: Contributor: Comments: Project Name: RAD Promulgation Tbilisi FIR Implementation: State(s) and Org: FRA relevance in AIP Georgia, ENR 4.4: Planned GEO LURIS (EX) available FL225 - FL660; Description: To publish for FRA (EX) point LORUS difference from 05 NOV 2020 Originator(s): EVEN FLs for all entering aircraft; FRASC FL availability: FL225 - FL660 and delete RAD GEO ODD FLs for all exiting aircraft. restriction UG2003. EUROCONTROL 164. Objective: Project Group: To further improve flight planning options within Tbilisi FIR SG BLACK

while adapting the FRA AIP publication to ERNIP Part 1 Project Category: requirements. AIP RAD Proposal ID : 96.023 Status: Contributor: Comments: Project Name: Norway FIR renaming Implementation: State(s) and Org: Some documentation update may delayed

Description: Planned NOR due to external to Norway reasons. 05 NOV 2020 ICAO 165. To rename Norway FIR as Polaris FIR.

Objective: Originator(s): NOR To adapt the FIR naming in order to comply with Annex 11 provisions. Project Category:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 58

EUROCONTROL Network Management Directorate

Airspace Structure Proposal ID : 98.058 / 31.012 Status: Contributor: Comments: Project Name: ATS Route Network Improvement in Implementation: State(s) and Org: L61 PEXON - ESALO - BAGRI; Odesa FIR, Simferopol’ FIR and Dnipro FIR Planned UKR L62 ESALO - BOGMA - RONIT;

Description: 05 NOV 2020 Originator(s): L63 OSDOR - RITED - DITIX; To replace existing DCTs within Odesa FIR, Simferopol’ FIR UKR L64 RASIL - RITED - TADID. 166. For detailed description see attached and Dnipro FIR by ATS routes. Project Group: documents. Objective: SG BLACK

To further improve ATS route network. Project Category: ATS Routes Proposal ID : 98.046 / 31.013 Status: Contributor: Comments: Project Name: Airspace Structure Improvement Kyiv Implementation: State(s) and Org: Postponed due to COVID 19. UIR/Dnipro FIR Planned UKR

Description: 05 NOV 2020 Originator(s): To significantly re-design the airspace in Kyiv UIR/Dnipro UKR

FIR as follows: Project Group: a) To change horizontal and vertical borders of TMA SG BLACK Kharkiv; horizontal borders of TMA Poltava. b) To remove the existing sector TMA Kharkiv HV3. Project Category: c) To change horizontal and vertical borders of UTA Airspace Structure Dnipro-North DVN; horizontal borders of UTA Dnipro- ATC Sectors North DVC, UTA Dnipro-North DVW, UTA Dnipro-North ATS Routes DVN, UTA Dnipro-North DVE and CTA Dnipro-North 167. DVC. d) To establish new CTA Dnipro-North DVN e) To re-align the existing ATS routes A83, A137, L4, L32, L980, M853, M995, M996, N604, N623, N983, P29, P30, P851, W536, W538, W624, W644 and W693 in Kyiv UIR/Dnipro FIR. f) To set as bidirectional the segments MOGRI - MODEZ - KHR of the existing ATS route M996. g) To remove ATS route A97. h) To remove 5LNC points ADAKO, BADIG, ETUKI, GASNU, KUBUL, KUTOV, NESLO, OKSAR, SODRA, SUTOR, SUVIV, TAGAN, TOMKA and, accordingly, add 10 new 5LNC points in Kyiv UIR/Dnipro FIR.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 59

EUROCONTROL Network Management Directorate

Objective: To further improve the ATS route network and associated Airspace Structure of Kyiv UIR/ Dnipro FIR. Proposal ID : 99.030a Status: Contributor: Comments: Project Name: SECSI FRA - FRALB Night cross-border Implementation: State(s) and Org:  Night period to be defined. FRA Planned ALB  ATS route network removed.

Description: 03 DEC 2020 AUT  The South East Common Sky Initiative/ To implement Night Cross Border Free Route Airspace HRV SECSI FRA includes the airspace the between SECSI FRA and FRALB. SVN AoRs of Wien ACC, Ljubljana ACC, SRB Zagreb ACC, Sarajevo ACC and Objective: MNE Beograd ACC. To further harmonise the implementation of Free Route BIH  'Double AIRAC procedure’ for AIRAC 168. Airspace flight options as a single cross-border FRA area in South East Europe between the AoRs of Tirana ACC, Wien Originator(s): AIP AMDT publication required for ACC, Ljubljana ACC, Zagreb ACC, Sarajevo ACC and EUROCONTROL implementation (ICAO Annex 15 refers). Beograd ACC. Project Category: Free Route Airspace Related proposals: High Seas  71.086a  71.086b  90.010  99.030b Proposal ID : 100.002 Status: Contributor: Comments: Project Name: PBN Transition Plan - Austria Implementation: State(s) and Org: See attached plan Planned AUT Description: To implement Performance Based Navigation (PBN). 03 DEC 2020 Originator(s): 169. AUT Objective: To be compliant with EC Regulation 2018/1048. Project Category: PBN Transition Plan Proposal ID : 97.034 Status: Contributor: Comments: Project Name: ATS Route Improvement Brussels FIR / Implementation: State(s) and Org: Amsterdam FIR Planned BEL

Description: 03 DEC 2020 NLD 170. To implement new ATS route segment L191 NIK - PEVAD - Originator(s): VICOT. NLD

Objective: Project Category:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 60

EUROCONTROL Network Management Directorate

To further improve the ATS route network between Brussels ATS Routes FIR and Amsterdam FIR. Proposal ID : 99.034 Status: Contributor: Comments: Project Name: Deletion of operational FL Implementation: State(s) and Org:  Part 1: routes within the AoRs of ACCs

Description: Planned DEU Langen and Zürich - 08 OCT 2020. 03 DEC 2020 CHE  Part 2: routes within the AoRs of ACCs 1. To delete all operational altutides/ FLs from ATS-Routes in AIP Germany ENR 3.3 Column 4. Originator(s): Bremen and München and UAC Karlsruhe - 05 NOV 2020. 171. 2. To partly adopt the lower limits of the affected ATS- DEU  Part 3: last routes with operational FL Routes. Project Category: within the AoR of UAC Karlsruhe will Objective: ATS Routes be deleted within the frame of To be conform to PANS-OPS AMDT 9. preparatory changes for DFS FRA - 03 DEC 2020. Proposal ID : 100.001 Status: Contributor: Comments: Project Name: PBN Transition Plan - France Implementation: State(s) and Org: See attached plan Planned FRA Description: To implement Performance Based Navigation (PBN). 03 DEC 2020 Originator(s): 172. FRA Objective: To be compliant with EC Regulation 2018/1048. Project Category: PBN Transition Plan Proposal ID : 98.003 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Planned GBR Description: To remove the en-route dependency on the Barkway/ BKY 03 DEC 2020 Originator(s): DVOR. The STARs via BKY will be made RNAV5 and re- GBR

designated by their start fix in accordance with ICAO and the Project Category: ABBOT STAR will become a RNAV Hold. The changes to ATS Routes 173. the STARs are as follows: a. The LOREL 5F will become LISTO 1L; b. The LOREL 3G will either become MCT 1L or removed; c. The LOREL 2H will be amended via FINMA and become FINMA 1L; d. The LOREL 1K will be removed; e. The SPEAR 2H will be amend via FINMA and become FINMA 1S;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 61

EUROCONTROL Network Management Directorate

f. The SPEAR 2L will become LISTO 1S; g. The SPEAR 1M will either become MCT 1S or removed.

Objective: Remove en-route dependency on BKY DVOR and facilitate its eventual removal. Proposal ID : 98.043 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Planned GBR Description: a. To remove the en-route dependency on LAM DVOR by 03 DEC 2020 Originator(s): RNAV-ing the LOGAN 1H STAR such that it becomes a GBR

LOGAN 2H and establishing two new STARs from Project Category: BARMI - BARMI 1H for Heathrow and BARMI 1G for ATS Routes 174. Gatwick to capture the important Descent Planning PBN levels at BARMI of FL300 and FL260 respectively. b. RNAV-ing the holds at LAM, SABER, BRASO & LOGAN.

Objective: To remove the en-route dependency from LAM DVOR and the eventual removal of the DVOR. Proposal ID : 97.032 Status: Contributor: Comments: Project Name: DVOR Removal Project Implementation: State(s) and Org: Planned GBR Description: To remove the en-route dependency from MAY DVOR some 03 DEC 2020 Originator(s): STARs that route via this facilities into those holds being GBR made RNAV 5 and designated by their start fix as follows: 175. Project Category: a. LOREL 4Q will become BANVA 1L; AIP b. LOREL 1R will become ABBOT 1L; ATS Routes c. ASKEY 4Q and ASKEY 1R will be removed.

Objective: To remove the en-route dependency from MAY DVOR. Proposal ID : 100.003 Status: Contributor: Comments: Project Name: PBN Transition Plan - Croatia Implementation: State(s) and Org: See attached plan Planned HRV 176. Description: To implement Performance Based Navigation (PBN). 03 DEC 2020 Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 62

EUROCONTROL Network Management Directorate

Objective: HRV

To be compliant with EC Regulation 2018/1048. Project Category: PBN Transition Plan Proposal ID : 95.035b Status: Contributor: Comments:

Project Name: New STARs to LIMF Implementation: State(s) and Org: Related proposals: Planned ITA Description: a. 95.035a To implement the following new ATS route segments to be 03 DEC 2020 Originator(s): linked with new STAR to Torino/ LIMF: ITA 177. a. W456 AKASU – NELAB (link to LIMF); Project Category: b. W323 EVRIP - SRN – NELAB (link to LIMF). ATS Routes Objective: To further improve the ATS route network in Milano FIR. Proposal ID : 95.011 Status: Contributor: Comments: Project Name: Sector 3 re-design Amsterdam ACC Implementation: State(s) and Org:

Description: Planned NLD To re-design Sector 3. 03 DEC 2020 BEL 178. MUAC Objective: To further improve the airspace structure within Amsterdam Originator(s): NLD FIR and Brussels FIR. Project Category: ATC Sectors Proposal ID : 53.006 Status: Contributor: Comments: Project Name: RAXAD and MAKED dualisation Implementation: State(s) and Org:  Point TUTUN 421743N 0220104E will

Description: Planned SRB be new TCP between Skopje ACC and 03 DEC 2020 MKD Beograd ACC, 10NM west of RAXAD. To dualise the existing points RAXAD and MAKED as follows: Originator(s):  Further dualisation north of VAGEN a) VAGEN - TUTUN - SKJ bidirectional; could also be considered. EUROCONTROL b) TUTUN - PEP southbound; MKD Related proposals: 179. c) TUTUN - TALAS southbound; Project Group:  64.005 d) TUTUN - ERANA southbound (TUTUN - ERANA is RFG SE parallel with the existing UL617 and will be used for ARR LGTS/LGKV). Project Category: ATS Routes Objective: To further improve the ATS route network between Beograd

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 63

EUROCONTROL Network Management Directorate

FIR/UIR and Skopje FIR while reducing workload and increasing safety and efficiency. Proposal ID : 99.033 Status: Contributor: Comments: Project Name: ATS route AIP publication adaptaion Implementation: State(s) and Org:  Currently Z209 is eastbound but via

Description: Proposed AUT RAD is available bi-directional. To change to bi-directional existing eastbound ATS route autumn 2020 DEU  Discussions are in progress between CHE Austria, germany and Switzerland. Z209 GAMSA - BIRGI and remove RAD restrcition 180. LOLS1000. Originator(s): EUROCONTROL Objective: To adapt publication in AIP Austria in line with real utilisation Project Category: of the ATS route. AIP RAD Proposal ID : 66.095 / 01.010 Status: Contributor: Comments: Project Name: ATS Route Improvement Teheran FIR Implementation: State(s) and Org:

Description: Proposed AZE To implement lower ATS route P146 AGINA - GODNA within autumn 2020 IRN TUR Tehran FIR with lower limit of FL175.

Objective: Originator(s): 181. TUR To further improve the ATS route options within Tehran FIR for Nakhchivan (UBBN) airport. Project Group: SG BLACK

Project Category: ATS Routes Proposal ID : 95.009 Status: Contributor: Comments: Project Name: DCT Praha FIR Implementation: State(s) and Org:  As stated by IATA this expansion would Proposed CZE secure a southbound connection to Description: To expand the availability from Night to H24 of allowed autumn 2020 Originator(s): Italy, avoiding Germany as presently “Direct” flight planning option RASAN DCT BUDEX. IATA there is no southbound avoidance option. 182. Objective: Project Category:  The H24 option would be a To further improve the flight planning options within Praha DCTs contingency routing only, as flying time FIR. is around +15 minutes extra.  Any trade off connection within Czech airspace between RASAN - BUDEX or

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 64

EUROCONTROL Network Management Directorate

RASAN - TIVAP would be interesting. Proposal ID : 99.004 Status: Contributor: Comments: Project Name: Single CDR Category (SCC) Spain - Implementation: State(s) and Org:  UM445 – PEPAS-BEGOX – FL345- Phase 1 Proposed ESP FL660

Description: autumn 2020 Originator(s):  UY810 – ALT-AMR – FL265-FL285 To change existing CDR Categories into a single CDR ESP 183. category. Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in Spain. Proposal ID : 99.026 Status: Contributor: Comments: Project Name: Single CDR Category(SCC) Greece Implementation: State(s) and Org: Proposed GRC Description: To change existing CDR Categories into a single CDR autumn 2020 Originator(s): category. EUROCONTROL

184. Objective: Project Group: To further improve flight planning options reducing CDR RFG SE

complexity by simplifying the CDR category in Greece. Project Category: CDRs SCC Proposal ID : 99.018 Status: Contributor: Comments:

Project Name: Correct FRA Publication in Ireland Implementation: State(s) and Org: Related proposals: Proposed IRL Description: a. 83.016 To review the publication of FRA Ireland according to ERNIP autumn 2020 Originator(s): 185. Part 1 EUROCONTROL

Objective: Project Category: To publish Free Route Airspace in line with ERNIP Part 1 AIP Free Route Airspace Proposal ID : 65.018c Status: Contributor: Comments: Project Name: ATS Route Improvement Casablanca FIR Implementation: State(s) and Org:

186. Proposed MAR Description: To implement ATS route segment SONSO - RAVOL - autumn 2020 Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 65

EUROCONTROL Network Management Directorate

OSDAM northbound. MAR

Objective: Project Category: To further improve the ATS route network within Casablanca ATS Routes FIR. Proposal ID : 66.081b Status: Contributor: Comments:

Project Name: ATS Route Improvement Casablanca FIR Implementation: State(s) and Org: Related proposals: Proposed MAR Description: 1. 66.081c To implement the following ATS route segments: autumn 2020 Originator(s): a) SUBAL - SUNID - IBALU - RBT bi-directional; MAR 187. b) BEXAL - SUNID - NISBA bi-directional. Project Category: Objective: ATS Routes To further improve ATS route network within Casablanca FIR/UIR. Proposal ID : 71.052 Status: Contributor: Comments: Project Name: New TMA Tetouan (GMTN) airport Implementation: State(s) and Org: Proposed MAR Description: 1. To implement a new TMA for Tetouan (GMTN) Saniat autumn 2020 Originator(s): R’mel airport. MAR 188. 2. To implement new SIDs and STARs for Tetouan Project Category: (GMTN) Saniat R’mel airport. Airspace Structure Objective: TMA To further improve airspace structure around Tetouan (GMTN) Saniat R’mel airport. Proposal ID : 92.012 Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org: Current coding of these SIDs/STARs might issues Proposed MAR be considered none compliant with ICAO as

Description: autumn 2020 Originator(s): it is based on NOLRO not on first point 189. To code existing GMTT NOLRO SIDs/STARs as ADKIM. MAR ADKIM.

Objective: Project Category: To comply with provisions of Annex 11. Airspace Structure Proposal ID : 89.004b Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org: For example for STAR MOKIR1A 190. issues Morocco Proposed MAR referenced to point MOKIR additional

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 66

EUROCONTROL Network Management Directorate

Description: autumn 2020 Originator(s): abbreviated codes MKR1A is published. To properly adapt the AIP publication of all STARs for EUROCONTROL These abbreviated STAR codes supposed to be incorrect as NAVAID MKR does not GMMX in accordance with Annex 11. Project Category: exist. Objective: AIP To assure that all SIDs for the airport are properly coded in Related proposals: accordance with Annex 11 but when SID is referenced to 1. 89.004a 5LNC additional short SID code is published in AIP Morocco in parallel. Proposal ID : 99.008 Status: Contributor: Comments: Project Name: Connection between ATS routes and Implementation: State(s) and Org: Notes: Arrival GMME Proposed MAR 1. Currently there are designed and

Description: autumn 2020 Originator(s): published STARs ESALA but with no To allow proper transition between ATS route network and EUROCONTROL connection to ATS route network. STAR ESALA for Arrivals at GMME (Rabat/Sale) by either: 2. With removal of DCT limit within Project Category: Casablanca FIR/UIR there are no available 191. 1. Implementation of new ATS route segments LAKAM - ATS Routes ESALA and AGDAL - ESALA, or flight planning options. 2. Re-alignment via ESALA of existing ATS routes UA411 3. As temporary solution SAK DCT and Z/UZ801, and implentation of A411. ESALA was allowed for ARR GMME via RAD Appendix 4. Objective: To improve arrivals at GMME Proposal ID : 97.040 Status: Contributor: Comments: Project Name: AFUA concept Warszawa FIR Implementation: State(s) and Org: Proposed POL Description: 1. To reduce the size of FBZs/ Flight buffer zones from autumn 2020 Originator(s): currently 5NM to ~2,5NM. POL 2. To reduce the required tactical distance between 192. Project Category: segregated areas and GAT in en-route controlled Airspace Structure airspace from 3,5NM to 2,5NM. Civil/Military Airspace Objective: To further improve the airspace structure and its utilisation within Warszawa FIR. Proposal ID : 90.008 Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org:  Helicopter Routes are published within 193. issues Proposed PRT Lisbon CTR. The CTR is defined in

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 67

EUROCONTROL Network Management Directorate

Description: autumn 2020 Originator(s): AD2.12 CTR SFC / 2000FT ALT, Class To properly publish in ENR 3.4 all Helicopter Routes in EUROCONTROL C. All routes are subject to ATC.

accordance with Annex 11 and Annex 15.  Publication is not in accordance with Project Category: Objective: AIP Annex 11 and Annex 15. RDs, name- To further adapt existing AIP publication. codes, upper and lower limits, airspace classification, minimum flight altitudes are not published. Proposal ID : 99.022 Status: Contributor: Comments: Project Name: 5ANNCs publication Implementation: State(s) and Org:  Currently significant points HR401, Proposed PRT HR456, HR458, HR560, SM700, Description: To remove all RNAV SID/STAR and Instrument Approach autumn 2020 Originator(s): SM800, SM900 related to Santa Maria Procedure significant points from AIP Portugal, ENR 4.4. EUROCONTROL TMA are still published in ENR 4.4 194. contary to ICAO provisions. Objective: Project Group:  Portugal stated that these points were To publish the significant points in accordance with ICAO RFG SW already identified and will be processed provisions. Project Category: out of the document in a forthcoming AIP AIP amendment. Proposal ID : 78.052 / 18.010 Status: Contributor: Comments: Project Name: ATS route improvement between Helsinki Implementation: State(s) and Org: Russian Federation: further studies FIR and Russian Federation. Proposed RUS required. autumn 2020 FIN Description: To implement new ATS route OLATA - 640015N 0302830E - Originator(s): MAGON. FIN 195. RUS Objective: To further improve the ATS route network at the interface Project Group: between Helsinki FIR and Russian Federation. SG BALTIC

Project Category: ATS Routes Proposal ID : 79.028 / 18.011 Status: Contributor: Comments: Project Name: ATS route improvement between Helsinki Implementation: State(s) and Org: Russian Federation: further studies FIR and Russian Federation. Proposed RUS required.

Description: autumn 2020 FIN Related proposals: 196. To implement new ATS route OLATA - 640015N 0302830E - Originator(s):  81.085 / 15.003 UGMOR. FIN RUS

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 68

EUROCONTROL Network Management Directorate

Objective: Project Group: To further improve the ATS route network at the interface SG BALTIC between Helsinki FIR and Russian Federation. Project Category: ATS Routes Proposal ID : 80.021c Status: Contributor: Comments: Project Name: RNAV/RNP Procedures Implementation: State(s) and Org: Proposed TUR Description: To introduce P-RNAV SIDs/STARs for Izmir/Adnan autumn 2020 Originator(s): Menderes (LTBJ) airport. TUR

197. Objective: Project Group: To further improve the airspace organisation within Istanbul RFG SE

FIR and Ankara FIR. Project Category: PBN TMA Proposal ID : 95.013 Status: Contributor: Comments: Project Name: Istanbul Sabiha Gökcen/ LTFJ airport Implementation: State(s) and Org:  July 2020, opening of 2nd runway, Proposed TUR closure of existing runway for Description: To implement a new independent parallel RWY and new autumn 2020 Originator(s): renovation 198. ground infrastructure for Istanbul Sabiha Gökcen/ TUR  November 2020, operation of 2

LTFJ airport. runways Project Category: Objective: Airspace Structure To further improve the airspace structure and to TMA accommodate the traffic growth for the coming years. Proposal ID : 81.041 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to Planned ITA take action. Description: To replace existing 5LNC BRAVO. 28 JAN 2021 Originator(s):  Annex 11 stated that the 5LNCs shall be unique. Objective: EUROCONTROL  BRAVO is used 7 times worldwide and 199. To avoid 5LNCs duplication within the ECAC area of the ICAO is allocated in ICARD to Brazil. ICAO EUR/NAT region, to improve the aeronautical Project Group:  Found in Italian Mil AIP for LIPI SID information provided and be compliant with ICAO Annex 11. RFG SE CHI 1E/1F. Project Category:  ICAO DM sent relevant message to ITA 5LNC (DM23/01 MSG 14-027).

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 69

EUROCONTROL Network Management Directorate

Civil/Military Airspace  ITA (mil) confirmed that BRAVO cannot be found on civilian FMS, therefore the issue is considered as closed. ITA (mil) will not susbtitute BRAVO Proposal ID : 98.056 Status: Contributor: Comments: Project Name: Airspace Re-Structuring Project AoR Implementation: State(s) and Org:  The Local Approach Units (LAUs) LOVV 2021 Planned AUT LOWG/I/K/L are reaching up to FL165

Description: 25 FEB 2021 Originator(s): (LOWS up to FL125). To split the “1”-sectors (lowest sector layer/FL-band) of Wien AUT  LOVV ACC sectors W/B/N/S get a “0”- 200. layer from FL165 – FL245 (LOVV B ACC sectors and create a new lower ACC sector “0” Project Category: above LOWS APP and LOVV S-sector (“zero”) below each LOVV ACC “1”-sectors. Airspace Structure overhead MURA the “0”-sector will Objective: ATC Sectors reach from FL125 up to FL245). To further improve the airspace structure and allow a flexible  Above FL245 the “normal” known ACC usage of the "0" -sectors according to traffic demand. sectorization is provided. Proposal ID : 89.063 Status: Contributor: Comments: Project Name: Free Route Airspace Praha/ FRACZECH, Implementation: State(s) and Org:  'Double AIRAC procedure’ for AIRAC Step 4 Planned CZE AIP AMDT publication required for

Description: 25 FEB 2021 Originator(s): implementation (ICAO Annex 15 201. To implement H24 Free Route Airspace from FL095 - FL660 CZE refers).  ATS Route Network not available. within Prague FIR. Project Category: Objective: Airspace Structure Related proposals: To further improve flight efficiency within in Prague FIR. Free Route Airspace  100.004 1. 89.070 Proposal ID : 100.004 Status: Contributor: Comments: Project Name: ATS routes deletion Praha TMA Implementation: State(s) and Org:  Linked to H24 Free Route Planned CZE Airspace implementation within Prague Description: To delete/ amend the following ATS route segments: 25 FEB 2021 Originator(s): FIR 25 FEB 2021. a) L984 between BALTU - BEKVI; CZE  Possible RD release in ICARD after b) P31 between MAREM - PEMEL; deletion of routes. 202. Project Category: c) P733 between LOMKI - EROKA; ATS Routes Related proposals: d) P861 between DOBEN - GOLOP; 1. 89.063 e) T106 between MAREM - VESUB; f) T108 between EROKA - NIRGO; g) T871 between ODPAL - ARTUP;

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 70

EUROCONTROL Network Management Directorate

h) Z21 between OMELO - VOZ; i) Z30 between VOZ - VLM; j) Z39 between GOSEK - GOLOP; k) Z164 between VOZ - TIPRU; l) Z401 between EROKA - VLM.

Objective: To release existing ATS route designators for further use within Praha TMA and facilitate flight planning. Proposal ID : 97.015 Status: Contributor: Comments:

Project Name: Langen ACC Sector Group 1 re-design Implementation: State(s) and Org: Related proposals: Planned DEU Description: 1. 97.011 1. To redesign Langen ACC Sector Group 1 25 FEB 2021 Originator(s):  97.012 2. To re-design EDDL SIDs and STARs accordingly and DEU 3. Creation of new and/or change of existing ATS routes in 203. Project Category: the vicinity of EDDL to connect those SIDs & STARs to Airspace Structure the existing network. ATC Sectors Objective: ATS Routes To prepare Dusseldorf/ EDDL approach and surrounding sectors for the implementation of PSS (pre-requisite for future iCAS implementation). Proposal ID : 75.082e Status: Contributor: Comments:

Project Name: Brest ACC re-organisation - Step 5 Implementation: State(s) and Org: Related proposals: Planned FRA Description:  75.082a 25 FEB 2021 204. To extend Nantes TMA up to FL 195 Originator(s):  75.082b

FRA 1. 75.082d Objective: To further improve the airspace structure within France FIR. Project Category: Airspace Structure Proposal ID : 90.021 Status: Contributor: Comments: Project Name: EBCI procedures Implementation: State(s) and Org: Proposed BEL Description: To design adapted STARs to EBCI and an appropriate winter 2020/21 Originator(s): 205. Holding procedure, in function of military airspace release. BEL

Objective: Project Category: To further improve the airspace structure while de-conflicting Airspace Structure

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 71

EUROCONTROL Network Management Directorate

and segregating as far as practicable EBCI STARs and STARs to EBBR airport, improving flight and operational efficiency. To better accommodate traffic situations induced by bad weather. Proposal ID : 92.024b Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org: Z64 needs a new IFP calculation, airspace issues Proposed CHE study and CNS assessment.

Description: winter 2020/21 Originator(s): 206. To adapt the lower vertical limit, expressed in FL, of ATS EUROCONTROL route Z64 within Switzerland - change of IFR FL to VFR FL. Project Category: Objective: AIP To adapt in State AIP ATS routes vertical limits. ATS Routes Proposal ID : 99.020 Status: Contributor: Comments: Project Name: SID/STAR ID adaptation Implementation: State(s) and Org:  For example LCLK SID PAFOS 2B Proposed CYP shall be coded as PHA 2B in Description: To properly identify and code existing LCLK and LCPH winter 2020/21 Originator(s): accordnace with Annex 11. SIDs/STARs terminating / starting at VOR/DME PHA. EUROCONTROL  Request for re-consideration of this 207. publication is already send to Cyprus. Objective: Project Group: To adapt the airspace objects identification and publication RFG SE

in accordance with ICAO provisions. Project Category: AIP Proposal ID : 99.027 Status: Contributor: Comments: Project Name: Airspace classification in HELLAS UIR. Implementation: State(s) and Org:

Description: Proposed FAB BLUE MED winter 2020/21 GRC To classify the airspace of HELLAS UIR: a. FL460 - FL660: Class C; Originator(s): b. FL660 - UNL:Class G. GRC 208. Objective: Project Group: To further improve airspace structure in HELLAS UIR. RFG SE

Project Category: Airspace Structure High Seas Proposal ID : 99.014b Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 72

EUROCONTROL Network Management Directorate

Project Name: Single CDR Category (SCC)-UK-Phase 2 Implementation: State(s) and Org: Proposed GBR Description: To change all existing CDR Categories into a single CDR winter 2020/21 Originator(s): category. GBR 209. Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in United SCC Kingdom. Proposal ID : 90.022 Status: Contributor: Comments: Project Name: ATS route improvement ATHINAI Implementation: State(s) and Org: FIR/HELLAS UIR. Proposed GRC winter 2020/21 FAB BLUE MED Description: To implement, as CDR, the RNAV route ARLOS - GUDIS Originator(s): (bi-directional), in order to offer shorter route option for traffic GRC 210. from/to LMML. Project Group: Objective: RFG SE

To further improve the ATS route network within HELLAS Project Category: UIR/ATHINAI FIR. ATS Routes High Seas Proposal ID : 92.046 Status: Contributor: Comments: Project Name: ATS Route Improvement ATHINAI Implementation: State(s) and Org: FIR/HELLAS UIR Proposed GRC

Description: winter 2020/21 Originator(s): To re-designate existing RNAV route V/UV57 RDS - IRA as GRC

211. N/UN136 (FL065 - FL 460) (release of UV57). Project Group: Objective: RFG SE

To further improve ATS route network within ATHINAI Project Category: FIR/HELLAS UIR. ATS Routes High Seas Proposal ID : 87.012 Status: Contributor: Comments: Project Name: ATS Route Improvement Athinai FIR Implementation: State(s) and Org:

212. Proposed GRC Description: To change the availability of existing ATS route UP14 PINDO winter 2020/21 Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 73

EUROCONTROL Network Management Directorate

- RIKSO from Night (22.00 - 04.00) to H24. EUROCONTROL

Objective: Project Group: To further improve ATS routes network in PINDO area of RFG SE

Hellas UIR. Project Category: ATS Routes Proposal ID : 99.028 Status: Contributor: Comments: Project Name: Extention of HELLAS UIR upper limit. Implementation: State(s) and Org: To achieve harmonisation of the upper limit Proposed GRC in Blue Med FAB. Description: To extend the upper limit of controlled airspace within winter 2020/21 Originator(s): HELLAS UIR from FL460 to FL660. GRC

213. Objective: Project Group: To further improve the airspace organisation within HELLAS RFG SE

UIR. Project Category: Airspace Structure High Seas Proposal ID : 91.010 Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org:  As per AIP Tunisia airspace FL215 - issues Proposed ITA UNL is covered by ATS routes R723 / winter 2020/21 TUN UR723 and UM739 with Classes A and Description: To properly publish in AIP Italy and AIP Tunisia existing ATS Originator(s): G while as per AIP Italy airspace route segment R723 / UR723 / UM739 between TABOT and EUROCONTROL FL215 - FL660 is covered by ATS route M739 with Class C. The time DOPEL. Project Category: availability or CDR 3 is also not Objective: AIP understandable. To remove double ATS route publication of an ATS route ATS Routes 214.  Another issue open to interpretation is within ATS delegated area. that in AIP Tunisia TABOT is quoted as FIR/UIR BDRY without stating which one and in AIP Italy TABOT is quoted Marseille ACC / Tunis ACC which might be considered as an area of ATS delegation.  Relevant information for resolution was sent to Tunisia after RNDSG/95. Proposal ID : 95.040 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 74

EUROCONTROL Network Management Directorate

Project Name: Lamezia CTR re-organisation and new Implementation: State(s) and Org:  Approach Control Service in Lamezia Calabria CTA implementation Proposed ITA CTR, Crotone CTR and Calabria CTA

Description: winter 2020/21 Originator(s): will be provided by Roma ACC. To implement the following improvement measures: ITA  New dedicated sector (ES0) will be implemented. 1. Withdrawal of Lamezia CTR zone 2, 3, 4, 5 and 6; Project Group: 2. New Crotone CTR; FAB BLUE MED 3. Modification of Lamezia and Crotone ATZ; 4. New Calabria CTA (3 zones with different vertical limits), Project Category: 215. this new CTA partially substitutes the withdrawn Airspace Structure Lamezia CTR zones; TMA 5. Modification and/or deletion of SIDs/STARs from/to Lamezia (LICA) and Crotone (LIBP) airports; 6. Adaptation of Brindisi CTA with new Calabria CTA.

Objective: To further improve the airspace organisation and to rationalize Control Service. Proposal ID : 95.042 Status: Contributor: Comments: Project Name: Ronchi CTR re-organisation and new Implementation: State(s) and Org:  Approach Control Service in Ronchi Venezia Giulia CTA Proposed ITA CTR and Venezia Giulia CTA will be

Description: winter 2020/21 Originator(s): provided by Padova ACC. 1. Modification of Ronchi CTR zone 1 , withdrawal of zone ITA  New dedicated sector (CE0) will be implemented. 2, 3, 4, 5 and 6; Project Group: 2. Modification of Ronchi ATZ; FAB BLUE MED 3. Implementation of new Venezia Giulia CTA (4 zones 216. with different verical limits), this CTA partially substitutes Project Category: the withdrawn Ronchi CTR zones; Airspace Structure 4. Adaptation of Padova CTA zone 7 and 9 with the new Venezia Giulia CTA.

Objective: To further organise the airspace and to rationalize Control Service. Proposal ID : 99.023 Status: Contributor: Comments: Project Name: 5ANNCs publication Implementation: State(s) and Org:  Currently for all airports in Norway

Description: Proposed NOR where there are published RNAV 217. To remove all RNAV SID/STAR and Instrument Approach winter 2020/21 Originator(s): SIDs/STARs and IAPs significnat Procedure significant points from AIP Norway, ENR 4.4. EUROCONTROL points are published in ENR 4.4

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 75

EUROCONTROL Network Management Directorate

Objective: Project Category: contary to ICAO provisions. To publish the significant points in accordance with ICAO AIP  Request for re-consideration of this provisions. publication is already send to AIM Norway.  "Having RNAV way points (5ANNC) as part of ENR 4.4 part 2 is something Avinor has practiced since year 2006, there is no change now and there are no planned actions to change this in the near future. This “deviation” from the recommendations are known and have been practiced for 14 years." Proposal ID : 95.032 Status: Contributor: Comments: Project Name: ATS Route Improvement Bratislava FIR Implementation: State(s) and Org:  BABKO 493642N 0192810E

Proposed SVK  LIPTY 491408N 0191954E Description: To implement ATS route Z169 BABKO - LIPTY - UMARY. winter 2020/21 Originator(s):  UMARY 490604N 0193715E 218. SVK Objective: To further improve the ATS route structure while providing a Project Category: lower route option for traffic arriving/ departing LZTT from ATS Routes Northwest, when CDR P27 is closed. Proposal ID : 99.021 Status: Contributor: Comments: Project Name: SID/STAR ID adaptation Implementation: State(s) and Org:  For example, in AIP Sweden, AD 2 Proposed SWE ESSA 4-37- 40 ESSA SID DUNKER Description: To properly identify and code existing SIDs/STARs winter 2020/21 Originator(s): 5G shall be coded as DKR 5G, AROS 219. terminating / starting at NAVAIDs for Swedish airports. EUROCONTROL 5G as ARS 5G and TROSA 5G as TRS 5G. Objective: Project Category:  Request for re-consideration of this To adapt the airspace objects identification and publication AIP publication is already send to Sweden. in accordance with ICAO provisions. Proposal ID : 99.036 Status: Contributor: Comments: Project Name: new TANJO STAR Frankfurt/ EDDF Implementation: State(s) and Org: New waypoint TANJO. Planned DEU Description: 220. To introduce new STAR (RNAV 1) from TANJO as extension 25 MAR 2021 Originator(s): of existing ROLIS STAR (EDDF). DEU To adopt T911 to connect to new TANJO STAR. Project Category:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 76

EUROCONTROL Network Management Directorate

Objective: ATS Routes To further optimize the arrival structure at Frankfurt/ EDDF airport. Proposal ID : 95.014 Status: Contributor: Comments: Project Name: BAS sector split - Barcelona ACC Implementation: State(s) and Org: Planned ESP Description: 221. To split the existing Barcelona LECBBAS sector. 25 MAR 2021 Originator(s):

ESP Objective: To further improve capacity within Barcelona ACC. Project Category: ATC Sectors Proposal ID : 65.051b Status: Contributor: Comments: Project Name: New runway Dublin Airport (EIDW) Implementation: State(s) and Org:  Depending on traffic evolution, subject Planned IRL to growth to 23.5 M pax/y. Description: a. To build a new north parallel runway for Dublin Airport 25 MAR 2021 Originator(s):  New TWR planned for Q3 2020.

(EIDW). IRL Related proposals:

222. b. To develop SIDs and STARs for the new north parallel Project Category: a. 65.051a runway at Dublin airport. Airspace Structure Objective: To further improve the airspace structure within Shannon UIR, to increase capacity and further enhance the efficiency of ATM operations at Dublin airport. Proposal ID : 92.031 / 27.004 Status: Contributor: Comments: Project Name: PBN - Point Merge Implementation Riga Implementation: State(s) and Org: Airport Planned LVA

Description: 25 MAR 2021 LTU EST a. To implement PBN based procedures (RNP AR) for Riga (EVRA) airport. Originator(s): 223. b. To introduce Point Merge arrival systems for Riga LVA (EVRA) airport. Project Group: Objective: SG BALTIC

To further improve airspace organisation within Riga TMA, Project Category: reduce controller workload and increase operational CCO/CDO efficiency for Riga approach. PBN TMA

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 77

EUROCONTROL Network Management Directorate

Proposal ID : 94.040a Status: Contributor: Comments: Project Name: Free Route Airspace Spain - ESFRA Implementation: State(s) and Org:  No suspension of ATS route network. Phase 1 Planned ESP  FRA Concept not applied in TMAs

Description: 22 APR 2021 Originator(s): airspace. To implement Night Free Route Airspace 00:00 - 05:00 ESP  No cross-border operations between FIRs/UIRs. (00:00 - 04:00), FL195 - FL660 within Madrid FIR/UIR and Project Category: Barcelona FIR/UIR as single FRA area and Canarias Free Route Airspace  No cross-border operations between FIR/UIR. Madrid FIR/UIR and Barcelona High Seas Objective: FIR/UIR, border points will be 224. mandatory. To implement the FRA Concept and improve flight planning options within Spain.  'Double AIRAC procedure’ for AIRAC AIP AMDT publication required for implementation (ICAO Annex 15 refers).

Related proposals:  73.051 a. 76.051 a. 94.040b Proposal ID : 76.022 / 16.017 Status: Contributor: Comments: Project Name: ATS Route Improvement Lviv FIR/ Minsk Implementation: State(s) and Org:  AAAAA will be new boundary point FIR Proposed BLR between Ukraine and Belarus.

spring 2021 UKR  BLR further studies required taking into Description: To implement westbound ATS route ASKIL - AAAAA - VI. Originator(s): account further changes of route

225. UKR network in Moscow area. Objective: To further improve ATS route network between Lviv FIR and Project Group: Minsk FIR. SG BALTIC

Project Category: ATS Routes Proposal ID : 80.032 / 19.003 Status: Contributor: Comments: Project Name: ATS Route Improvement Lviv FIR/ Minsk Implementation: State(s) and Org:  BLR further studies required taking into FIR Proposed BLR account further changes of route

Description: spring 2021 UKR network in Moscow area 226. To implement southbound ATS route RATIN - DIBON - Originator(s):  The city pairs interested in this new KOVUS. EUROCONTROL option are CP41 UUEE - LIRF and CP45 UUDD - LYTV. Objective: Project Group:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 78

EUROCONTROL Network Management Directorate

To further improve ATS route network between Minsk FIR SG BALTIC  Current option for flights via AMIRI is

and Lviv FIR. Project Category: longer by 7.4NM. ATS Routes Proposal ID : 87.018 / 23.012 Status: Contributor: Comments: Project Name: ATS Route Improvement Minsk FIR/ Kyiv Implementation: State(s) and Org:  AAAAA - will be new boundary point FIR/ Chisinau FIR Proposed BLR BLR/UKR;

Description: spring 2021 MDA  BBBBB - will be new boundary point UKR UKR/MDA; To implement one of the following bi-directional ATS routes: 1. DUBIN - AAAAA - BBBBB - BINOM; or Originator(s):  BLR further studies required; 227. 2. DUBIN - AAAAA - BBBBB - LIPTA - GIDRO; or MDA  UKR further studies required. 3. DUBIN - AAAAA - LAVDA. Project Group: Objective: SG BALTIC To further improve ATS route network between Belarus, SG BLACK

Ukraine and Moldova. Project Category: ATS Routes Proposal ID : 96.027 / 29.015 Status: Contributor: Comments: Project Name: FIR boundary points Riga FIR - Minsk FIR Implementation: State(s) and Org:

Description: Proposed BLR spring 2021 LVA To consider the possibility to implement more FIR boundary points between Riga FIR and Minsk FIR to further increase Originator(s): 228. Free Route Airspace efficiency. BLR LVA Objective: To further improve the airspace structure between Riga FIR Project Group: and Minsk FIR. SG BALTIC

Project Category: Airspace Structure Proposal ID : 84.063 Status: Contributor: Comments: Project Name: 5LNC replacement by Finland Implementation: State(s) and Org:  Currently in AIP Finland, Part AD for Proposed FIN each aerodrome after the table with Description: To withdraw or replace, in accordance with Annex 11, VFR spring 2021 Originator(s): RNAV terminal points there is a table 229. reporting points published as pronounceable 5LNCs in AIP EUROCONTROL with VFR reporting points most of which are declared as compulsory. Finland, part AD 2. Project Category:  These VFR reporting points are Objective: 5LNC designated as five-letter

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 79

EUROCONTROL Network Management Directorate

To comply with requirements of Annex 11 in designation of pronounceable name-codes (5LNCs) significant points with 5LNCs. and internal finalization of their purpose, reason of AIP publication and compatibility with ICAO shall be discussed.  In accordance with Annex 11 only when a significant point is used for ATC purposes, it shall be designated by a unique five-letter pronounceable “name-code”.  None of these 5LNCs are reserved for Finland.  The use of already reserved 5LNCs is contrary to provisions of Annex 11 and might be considered as safety issue. Proposal ID : 99.025 / 31.017 Status: Contributor: Comments: Project Name: ATS route and airspace structure Implementation: State(s) and Org: improvement between Finland FIR and Russian Proposed FIN Federation spring 2021 RUS

Description: Originator(s): To implement two new FIR boundary points between Finland FIN 230. and Russian Federation in the vicinity of RATLA. RUS

Objective: Project Group: To further improve the ATS route and airspace structures SG BALTIC

between Finland FIR and Russian Federation Project Category: ATS Routes Proposal ID : 92.015 Status: Contributor: Comments: Project Name: RAD Promulgation Scottish FIR Implementation: State(s) and Org:  When both UK North Sea and Proposed GBR Maastricht flow regulations are in force Description: To further improve RAD restrictions EG2163, EG2160, spring 2021 Originator(s): by allowing to file via NATEB area to EG2166 and EG5094. IATA Scandinavian destinations, AOs could 231. shorten the "flow avoidance route" to Objective: Project Category: 111 NM / 14 min while from To further improve flight planning options from EGLL to RAD Scandinavian destinations to 120 NM / Scandinavia via NATEB area within Scottish FIR. 20 min.  Currently not feasible to

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 80

EUROCONTROL Network Management Directorate

further improve flight planning options from Scandinavia to EGLL via NATEB area. Proposal ID : 97.033 Status: Contributor: Comments: Project Name: Route Rationalisation & U Removal Implementation: State(s) and Org:

Description: Proposed GBR 1. To remove the U prefix from route designator of ATS spring 2021 IRL FRA 232. routes UM30, UN22 and UN32. 2. To re-designate UN34 as N27 and UP620 as N36. Originator(s): GBR Objective: To improve route rationalisation and remove U designator Project Category: prefix. ATS Routes Proposal ID : 91.022 Status: Contributor: Comments: Project Name: Greek Airspace reorganization - Phase 2 Implementation: State(s) and Org:  Linked to the implementation of the Proposed GRC new ATM system. Description: To redesign the ACC sectorisation within Athinai FIR/ Hellas spring 2021 Originator(s):  Depends on FRA implementation. 233. UIR, Step 2. GRC Related proposals:

Objective: Project Category: a. 91.021 To further improve the airspace organisation within Athinai Airspace Structure 1. 91.023 FIR/ Hellas UIR and enhance capacity within Greek ACCs. ATC Sectors Proposal ID : 96.001 Status: Contributor: Comments: Project Name: LGGG FIR Direct Routes Implementation: State(s) and Org:  New option proposed will save 2 Proposed GRC minutes of flight time. Description: To allow H24 "Direct" options GUDIS DCT ARLOS and spring 2021 Originator(s):  USAF estimates these DCTs will save ARLOS DCT GUDIS. U.S.A.F.E 1560lbs of fuel and 33640lbs of CO2 per year. 234. Objective: Project Group: To further improve route options and reduce the flight time FAB BLUE MED and CO2 emissions. RFG SE

Project Category: DCTs RAD Proposal ID : 92.011 Status: Contributor: Comments: 235. Project Name: ATS route improvement Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 81

EUROCONTROL Network Management Directorate

Proposed ITA take action. Description: 1. To establish new REP MOPIP (provisional name). spring 2021 Originator(s):  Project run in cooperation with Italian 2. To implement eastbound ATS routes T114 MOPIP - ITA Air Force (ITAF) responsible for Treviso CTR. OSLOP - BARPI and Y92 BADOP - MONFA. Project Category:  New REP is in charge of ITAF. 3. To implement new bidirectional connections as part of ATS Routes existing ATS routes N606 and Q19. Civil/Military Airspace Objective: To further improve procedures / ATS routes for ARR/DEP LIPH (Treviso). Proposal ID : 93.005 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to Proposed ITA take action. Description: To replace 5LNC ALPHA. spring 2021 Originator(s):  This 5LNC is used worldwide for 11 significant points and the Priority State Objective: ICAO identified by ICAO to keep the code is 236. To avoid worldwide 5LNC duplication, to improve the Project Category: Lao People's Democratic Republic. aeronautical information provided and be compliant with 5LNC  For Italy 5LNC exists for 2 significant ICAO Annex 11. Civil/Military Airspace points at/around LIPL and LIRL airport. Codes replaced by 5LNC ADBOR and ADNOB. Implementation date tba. Proposal ID : 94.011 Status: Contributor: Comments: Project Name: 5LNC replacement by Italy Implementation: State(s) and Org:  NM requested ICAO to remind ITAF to Proposed ITA take action. Description: To replace 5LNC PETER. spring 2021 Originator(s):  This 5LNC is used worldwide for 4 significant points and the Priority State Objective: ICAO identified by ICAO to keep the code is To resolve worldwide 5LNCs duplication. Project Category: 237. USA. 5LNC  Not registered in ICARD and Italy was Civil/Military Airspace notified by ICAO DM on 4 APR 2018 to take action.  In use at LIPL airport - Approach and Terminal Usage. Proposal ID : 98.024 Status: Contributor: Comments: 238. Project Name: JAMP 2020+: Step 1 Implementation: State(s) and Org:

Description: Proposed LVA

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 82

EUROCONTROL Network Management Directorate

To implement a vertical split of the East sector in Riga FIR. spring 2021 EST

Objective: LTU To further improve the airspace structure and increase BLR RUS capacity within the NEFAB area. Implement a first step towards dynamic sectorisation, increase capacity for Originator(s): anticipated traffic growth and gain experience with vertically LVA split sectors. FAB NEFAB

Project Group: FAB NEFAB SG BALTIC

Project Category: ATC Sectors Proposal ID : 61.017 Status: Contributor: Comments: Project Name: ATS Route Improvement Madrid UIR/ Implementation: State(s) and Org: Casablanca FIR. Proposed MAR spring 2021 ESP Description: 239. To implement, as permanent southbound ATS route Originator(s): segment GALTO - FES. IATA

Objective: Project Category: To further improve the ATS route network between Madrid ATS Routes UIR and Casablanca FIR. Proposal ID : 71.049 Status: Contributor: Comments: Project Name: Radar approach Fes (GMFF) airport Implementation: State(s) and Org: Re-organisation of existing Fes (GMFF) Proposed MAR Saiis airport TMA implemented. Description: 1. To introduce radar approach (MSSR mode S and spring 2021 Originator(s): Primary radar approach) for Fes (GMFF) Saiis airport. MAR 240. 2. To implement new SIDs and STARs for Fes (GMFF) Project Category: Saiis airport. Airspace Structure Objective: TMA To further improve airspace organisation around Fes (GMFF) Saiis airport. Proposal ID : 71.053 Status: Contributor: Comments: 241. Project Name: New TMA Al Hoceima (GMTA) airport Implementation: State(s) and Org: Proposed MAR Description:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 83

EUROCONTROL Network Management Directorate

1. To implement new TMA for Al Hoceima (GMTA) Cherif spring 2021 Originator(s): El Idrissi airport. MAR

2. To implement new SIDs and STARs for Al Project Category: Hoceima (GMTA) Cherif El Idrissi airport. Airspace Structure Objective: TMA To further improve airspace organisation around Al Hoceima (GMTA) Cherif El Idrissi airport. Proposal ID : 71.054b Status: Contributor: Comments: Project Name: Free Route Airspace Morocco (MORFRA), Implementation: State(s) and Org:  Coordination with NM required to Phase 2 Proposed MAR ensure harmonised network FRA

Description: spring 2021 ESP implementation. PRT  'Double AIRAC procedure’ for AIRAC To implement H24 Free Route Airspace FL195 - FL460 within the AoR of Agadir ACC. Originator(s): AIP AMDT publication required for 242. implementation (ICAO Annex 15 Objective: MAR refers). To further improve airspace organisation within Casablanca Project Group:  ATS Route Network will be removed. FIR. RFG SW Related proposals: Project Category: 1. 71.047 Free Route Airspace 1. 71.054a Proposal ID : 71.051 Status: Contributor: Comments: Project Name: New TMA Nador (GMMW) airport Implementation: State(s) and Org: Proposed MAR Description: a. To implement new TMA. spring 2021 Originator(s): 243. b. To implement new SIDs and STARs. MAR

Objective: Project Category: To further improve airspace organisation around Nador Airspace Structure (GMMW) El Aroui airport. TMA Proposal ID : 66.081d Status: Contributor: Comments: Project Name: ATS Route Improvement Casablanca Implementation: State(s) and Org: FIR/UIR Proposed MAR

Description: spring 2021 Originator(s): 244. To implement the following ATS routes: MAR

a) BAGBO - PIXOV bi-directional (CDR); Project Category: b) OZT - OJD bi-directional (CDR). ATS Routes

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 84

EUROCONTROL Network Management Directorate

Objective: To further improve ATS route network within Casablanca FIR/UIR. Proposal ID : 97.009 Status: Contributor: Comments: Project Name: 5LNC replacement by Norway Implementation: State(s) and Org:  VFR reporting points are designated as Proposed NOR “mandatory” five-letter pronounceable Description: To withdraw or replace, in accordance with ICAO Annex 11, spring 2021 Originator(s): name-codes (5LNCs) (not ICARD) or of VFR reporting points published inside/at controlled EUROCONTROL “mandatory” VFR with names of more than 10 letters or also use the special airspace boundaries in AIP Norway, part AD 2, VFR Routes. Project Category: Norwegian letters like “Ø”. Objective: 5LNC  Further assessment of reservation in To comply with requirements of Annex 11 in designation of ICARD of those 5LNCs and their significant points with 5LNCs. possible used worldwide by other 245. States need to be assessed.  Based on provided way forward and that in accordance with Annex 11 only when a significant point is used for ATC purposes, it shall be designated by a unique five-letter pronounceable “name-code”, internal finalization of VFR reporting point purpose, reason of AIP publication and compatibility with ICAO shall be considered. Proposal ID : 62.091e Status: Contributor: Comments: Project Name: Reorganisation ACC Warszawa sector Implementation: State(s) and Org:  Depending on technical issues configuration – three layer division - Step 1 Proposed POL (frequencies) and increasing the

Description: spring 2021 Originator(s): amount of ATC staff. To implement a new airspace structure and sectorisation POL  New elementary sectors with vertical within Warszawa ACC considering vertical splits (division splits. 246. Project Category: into three layers),  Division into three layers. Airspace Structure Step 1 : 3rd Layer (EPWWJ, EPWWR, EPWWK, EPWWZ) Related proposals: ATC Sectors Objective: 1. 62.091c To further improve the airspace structure within Warszawa 1. 99.015a ACC and increase capacity while applying vertical splits.  99.015b a. 99.015c Proposal ID : 97.042b Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 85

EUROCONTROL Network Management Directorate

Project Name: TMA Reorganisation Warsaw FIR - Step 2 Implementation: State(s) and Org: Proposed POL Description: To re-organise TMA of Poznan in order to allow CDA spring 2021 Originator(s): 247. operations from more directions than it is available today. POL

Objective: Project Category: To further improve the airspace structure within Warsaw FIR CCO/CDO while enhancing CDA operations. TMA Proposal ID : 63.051 / 08.006 Status: Contributor: Comments: Project Name: ATS Route Improvement Kyiv/Dnipro FIR Implementation: State(s) and Org:  Further studies required taking into - Moscow FIR Proposed RUS account future changes of route spring 2021 UKR network in Moscow area; Description: To implement the following ATS routes: Originator(s):  AAAAA and BBBBB will be new TCPs between Dnipro FIR and Moscow FIR. 248. a) KUROS - AAAAA - PT (Petrovskoye) eastbound; IATA  a) CDR in Ukraine. b) KOROT - BBBBB - TUVOG westbound. Project Group:  In case of implementation ATS routes Objective: SG BALTIC will be available after prior coordination To further improve the ATS route network at the Eastern Project Category: with ATC units. ECAC interface between Kyiv/Dnipro FIR and Moscow FIR. ATS Routes Proposal ID : 63.052 / 08.007 Status: Contributor: Comments: Project Name: ATS Route Improvement Kyiv/Dnipro FIR Implementation: State(s) and Org:  KUROS - KO westbound; - Moscow FIR Proposed RUS  AAAAA will be new TCP between

spring 2021 UKR Dnipro FIR and Moscow FIR. Description: To implement bidirectional ATS route TUVOG - KUROS - Originator(s):  KUROS - AAAAA CDR. AAAAA - BUTRI - ABARO. IATA  For potential distance and 249. Objective: Project Group: environmental savings see the relevant assessment. To further improve the ATS route network between SG BALTIC Kyiv/Dnipro FIR and Moscow FIR.  Further studies required taking into Project Category: account future changes of route ATS Routes network in Moscow area. Proposal ID : 86.028 Status: Contributor: Comments: Project Name: 5LNC replacement by Serbia and Implementation: State(s) and Org:  More than 60 (sixty) VFR reporting Montenegro Proposed SRB points are designated as five-letter

250. spring 2021 MNE pronounceable name-codes Description: To withdraw or replace VFR reporting points published as Originator(s): (5LNCs). Most of them are reserved in pronounceable 5LNCs in AIP Serbia / Montenegro, part AD EUROCONTROL ICARD and already used worldwide by

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 86

EUROCONTROL Network Management Directorate

2, Chart for VFR flights. other States. Project Group: Objective: RFG SE  In accordance with Annex 11 only To align AIP publication in accordance with Annex 11. when a significant point is used for ATC Project Category: purposes, it shall be designated by a 5LNC unique five-letter pronounceable AIP “name-code”.  Internal finalization of VFR reporting point purpose, reason of AIP publication and compatibility with ICAO shall be considered. Proposal ID : 87.022 Status: Contributor: Comments: Project Name: ECAC States AIP en-route publication Implementation: State(s) and Org:  6 (six) VFR reporting points are similar issues Proposed SVK to five-letter pronounceable name-

Description: spring 2021 Originator(s): codes (5LNCs). Most of these names To withdraw or replace, in accordance with ICAO Annex 11, EUROCONTROL are reserved as 5LNCs in ICARD and VFR entry and exit points to/from CTRs published as village already used worldwide by other Project Category: States. names composed of five-letters similar to pronounceable AIP  These names maintained in any 251. 5LNCs in AIP Slovakia, part AD 2. aeronautical database create and Objective: might create artificial name duplication To further improve the AIP publication avoiding duplication of contrary to Annex 11. pronounceable 5LNCs.  Internal finalization of VFR reporting point purpose, reason of AIP publication and compatibility with ICAO shall be considered. Proposal ID : 86.027 Status: Contributor: Comments: Project Name: 5LNC replacement by Sweden Implementation: State(s) and Org:  Around 30 (thirty) VFR reporting points Proposed SWE are designated as five-letter Description: To withdraw or replace VFR reporting points published as spring 2021 Originator(s): pronounceable name-codes pronounceable 5LNCs in AIP Sweden, part AD 2, Visual EUROCONTROL (5LNCs). Most of them are reserved in ICARD and already used worldwide by Approach Charts. Project Category: 252. other States. Objective: 5LNC  In accordance with Annex 11 only To align AIP publication in accordance with Annex 11. AIP when a significant point is used for ATC purposes, it shall be designated by a unique five-letter pronounceable “name-code”.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 87

EUROCONTROL Network Management Directorate

 Internal finalization of VFR reporting point purpose, reason of AIP publication and compatibility with ICAO shall be considered.  Pending CAA decision. Proposal ID : 71.040d / 16.026d Status: Contributor: Comments: Project Name: FRAU Free Route Airspace Ukraine, Step Implementation: State(s) and Org:  'Double AIRAC procedure’ for AIRAC 1 (Sc 1b) - Phase 3 Proposed UKR AIP AMDT publication required for

Description: spring 2021 Originator(s): implementation (ICAO Annex 15 To implement H24 - Free Route Airspace operations within UKR refers).  Impl. postponed due to ATM system Odesa ACC (excl. Sectors OVS, OVL, OVU) from FL275 to Project Group: issues. FL660. RFG SE 253.  ATS Route Network available. Objective: SG BLACK

Related proposals: To implement FRA Concept and further improve flight Project Category: efficiency within Kyiv UIR. Free Route Airspace  71.040a / 16.026a 1. 71.040b / 16.026b  71.040c / 16.026c a. 81.018a / 19.021a  81.018b / 19.021b Proposal ID : 89.016 Status: Contributor: Comments: Project Name: DCT Brussels FIR Implementation: State(s) and Org:  Stepped approach.

Proposed BEL  Postponed due to a lack of resources. Description: To allow additional "Direct" flight planning options within summer 2021 Originator(s): 254. Brussels FIR below FL245. BEL

Objective: Project Category: To further improve flight planning options within Brussels DCTs FIR. RAD Proposal ID : 91.023 Status: Contributor: Comments: Project Name: Greek Airspace reorganization - Phase 3 Implementation: State(s) and Org: Depends on FRA implementation. Proposed GRC Description: Related proposals: 255. To finetune the redesign of the ACC sectorisation within summer 2021 Originator(s): 1. 91.021 Athinai FIR/ Hellas UIR, Step 3. GRC  91.022

Objective: Project Category: To further improve the airspace organisation within Athinai Airspace Structure

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 88

EUROCONTROL Network Management Directorate

FIR/ Hellas UIR and balance workload/ capacity within the ATC Sectors Greek ACCs. Proposal ID : 98.021 Status: Contributor: Comments: Project Name: Budapest TMA and ACC re-organisation Implementation: State(s) and Org: Due to COVID-19 the planned hardware Proposed HUN upgrade of the ATM system and the move Description: To implement new sectorisation for Budapest ACC. summer 2021 Originator(s): from the OPS to the Contingency room 256. from 12/10/2020-30/04/21 might be Objective: HUN postponed for the next year To further improve the airspace structure within Budapest Project Category: FIR to better distribute workload according to traffic demand/ Airspace Structure flows. ATC Sectors Proposal ID : 66.021 Status: Contributor: Comments: Project Name: CDR harmonisation Implementation: State(s) and Org: To add the following comment: “Planned to Proposed ITA be reassessed during works about Description: To extend the availability of CDR3 UY170 LEGLO - ABREG summer 2021 Originator(s): reorganisation of military areas for strike within Milano UIR as CDR1/2 following the utilisation of EUROCONTROL fighter F35 needs (in the NE and NW of 257. Italy). UY170 ABREG - ARGAX - ROMIR within Swiss UIR. Project Category: Objective: CDRs Related proposals: To further harmonise the utilisation of the existing CDRs  61.025b within ECAC airspace. a. 79.026 Proposal ID : 98.028 / 31.011 Status: Contributor: Comments:

Project Name: Lithuania Airspace reconfiguration Implementation: State(s) and Org: Related proposals: project Proposed LTU  94.043 Description: summer 2021 Originator(s): Lithuania Airspace restructure Study 2030 including: LTU

a) New proposed structure of Palanga TMA; Project Group: b) Revision of SID / STAR system for Vilnius TMA; SG BALTIC 258. c) New proposed structure of Vilnius and Kaunas TMAs; Project Category: d) New entry-exit points for Palanga TMA, and existing for Kaunas TMA; Airspace Structure e) Reconfiguration of military areas within Vilnius FIR; Civil/Military Airspace f) Cross border sectorisation for Baltic FAB (see also TMA proposal 94.043).

Objective: To review and establish new airspace structure for Republic

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 89

EUROCONTROL Network Management Directorate

of Lithuania. Proposal ID : 91.035 / 26.032 Status: Contributor: Comments: Project Name: FIR border harmonisation Norway FIR - Implementation: State(s) and Org:  ICAO is unable to process the PFA due Bodo Oceanic FIR Proposed NOR to the naming of NORWAY FIR.

summer 2021 ISL  The implementation might be delayed Description: To realign the FIR border between NORWAY FIR and BODØ Originator(s): until the naming issue is solved. 259. OCEANIC FIR. NOR

Objective: Project Group: To harmonize the FIR border between NORWAY FIR and SG BALTIC

BODØ OCEANIC FIR with underlying ACC sectorisation. Project Category: Airspace Structure High Seas Proposal ID : 96.024 Status: Contributor: Comments: Project Name: FIR border realignment Murmansk FIR / Implementation: State(s) and Org: Ref RNDSG action item RNDSG/93-01 and Bodø FIR / Norway FIR Proposed NOR RDGE action plan item 26/03

Description: summer 2021 RUS Agreement between the Russian To realign the FIR border between Murmansk FIR and Bodø ICAO Federation and the States will approach FIR / Norway FIR. EUROCONTROL ICAO with a recuest to update the Air 260. FAB NEFAB Navigation Plan and relevant documents Objective: related to alignment of the FIR border To resolve the long-standing issue of the unallocated Originator(s): NOR airspace (NO-FIR area) between Murmansk FIR and Bodø FIR / Norway FIR. Project Category: Airspace Structure ATC Sectors High Seas Proposal ID : 98.065 Status: Contributor: Comments: Project Name: New SID and STAR structure in Cascais Implementation: State(s) and Org: TMA Sectors to be implemented for new Proposed PRT Lisboa TMA as follows: Description: To improve the airspace structure at Cascais, summer 2021 Originator(s):  LPTMAE - Lisbon Terminal East; a. New RNAV1 procedures will be implemented at LPCS: PRT  LPTMAW - Lisbon Terminal West; 261.  LPAPP Lisbon Arrival Sector; b. New RNAV1 STAR´s structure for LPCS.New RNAV1 Project Category: SID’s structure for LPCS.  TV LPPTARR and LPCSARR. Airspace Structure Objective: TMA Related proposals: To further improve the airspace organization in Lisboa TMA  98.051

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 90

EUROCONTROL Network Management Directorate

while reducing complexity, enhancing arrival sequencing 1. 98.064 and increasing sector capacity. Proposal ID : 98.066 Status: Contributor: Comments: Project Name: Madeira TMA optimization Implementation: State(s) and Org: Madeira TMA redesign pending on Proposed PRT availability of resources and slot for final Description: To improve airspace structure in Madeira TMA: summer 2021 Originator(s): training. Project (due on June 18) is suspended UFN. a) New RNAV1 STAR´s structure for LPMA. PRT b) New RNAV1 SID’s structure for LPMA. Related proposals: 262. Project Category: c) New RNAV1 STAR´s structure for LPPS. Airspace Structure  98.048 d) New RNAV1 SID’s structure for LPPS. TMA Objective: To further improve the airspace organization in Madeira TMA. Proposal ID : 98.048 Status: Contributor: Comments: Project Name: Extension of Madeira TMA boundaries Implementation: State(s) and Org:  Madeira TMA redesign pending on Proposed PRT availability of resources and slotfor final Description: 1. To slightly extend Madeira TMA boundaries. summer 2021 Originator(s): training. Project (due on June 18) is 2. To implement new 5LNCs on the new TMA boundaries: Serial Number: PRT suspended UFN. EKNOT, FAGUT, GALOZ, IBBAN, ILCAT, KICAS, EUR/NAT 19/19-HS-POR  As Free Route Procedures are Project Category: available in Lisboa FIR, there will be no AMZIC, DEMZO. Circulation Letter: Airspace Structure need to publish new Lower/Upper ATS 3. To implement the following changes to ATS routes: EUR/NAT 19-0520.TEC of 28 High Seas Routes. As today, Entries and Exists a) G851 - TABOM will be replaced by FAGUT; November 2019 TMA to/from Lisboa FIR will be planned by b) R1 - MADAT will be removed; Approval Letter: means of "DCT" as specified in Lisboa c) W3 - IRSAN and NIKAV will be removed and EUR/NAT 20-0001.TEC of 2 Free Route Airspace general 263. replaced by ILCAT; January 2020 d) UL600 - IRSAN and NIKAV will be removed and procedures published in AIP Portugal replaced by ILCAT; ENR 1.3. e) UN975 - FAGUT will be inserted in this ATS route.  High Seas Coordination (Serial no: EUR/NAT 19/19-HS-POR) Objective: ◦ Circulation letter ref: EUR/NAT 19- To improve airspace organisation and increase capacity in 0520.TEC of 28 November 2019 - Madeira TMA. deadline on 29 December 2019 ◦ Approval letter ref: EUR/NAT 20- 0001.TEC of 2 January 2020

Related proposals:  98.066

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 91

EUROCONTROL Network Management Directorate

Proposal ID : 98.064 Status: Contributor: Comments: Project Name: Lisboa TMA Point Merge System Implementation: State(s) and Org: TMA Sectors to be implemented for new Proposed PRT Lisboa TMA as follows: Description: To improve the airspace structure in Lisbon TMA, Point summer 2021 Originator(s):  LPTMAE - Lisbon Terminal East; Merge System will be implemented for arrivals/departures to PRT  LPTMAW - Lisbon Terminal West; LPPT.  LPAPP Lisbon Arrival Sector; 264. Project Category: a) New RNAV1 STAR´s structure for LPPT. Airspace Structure  TV LPPTARR and LPCSARR. b) New RNAV1 SID’s structure for LPPT. Post-poned due to COVID-19 TMA Objective: Related proposals: To further improve the airspace organization in Lisboa TMA  98.051 while reducing complexity, enhancing arrival sequencing  98.065 and increasing sector capacity. Proposal ID : 98.051 Status: Contributor: Comments: Project Name: Vertical Limits of Class G Airspace in Implementation: State(s) and Org:  High Seas Coordination (Serial no: Lisboa TMA Proposed PRT EUR/NAT 19/22-HS-POR)

Description: summer 2021 Originator(s): ◦ Circulation letter ref: EUR/NAT 19- To change the vertical limits of Class “G” airspace in a small Serial Number: PRT 0534.TEC of 10 December 2019 - portion of the south-western limits of Lisboa TMA to 1000 EUR/NAT 19/22-HS-POR deadline on 10 January 2020 Project Category: ◦ Approval letter ref: EUR/NAT 20- 265. ft/AMSL Circulation Letter: Airspace Structure EUR/NAT 19-0534.TEC of 10 0048.TEC of 16 January 2020 Objective: High Seas December 2019 Related proposals: To improve airspace organisation and increase capacity in TMA Lisboa TMA. Approval Letter:  98.064 EUR/NAT 20-0048.TEC of 16  98.065 January 2020

Proposal ID : 98.022 Status: Contributor: Comments: Project Name: Bucuresti ACC re-organisation Implementation: State(s) and Org:  New ATM system implementation in Proposed ROU Romania is a prerequisit. Description: To re-organise Bucuresti ACC sectors in line with the SEE summer 2021 Originator(s):  Possible “cross-border” sectors shall 266. be considered. FRA H24 operation experience. ROU

Objective: Project Category: Related proposals: To further improve the airspace structure of Bucuresti Airspace Structure  82.033 ACC at the interface with Budapest ACC and Sofia ACC. ATC Sectors Proposal ID : 74.056 Status: Contributor: Comments: 267. Project Name: RAD promulgation Istanbul FIR Implementation: State(s) and Org: None allowance of alternative ATS route

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 92

EUROCONTROL Network Management Directorate

Proposed TUR option Description: To adapt RAD restriction LT2017 by adding exception during summer 2021 Originator(s):  This restriction is directly connected Night (Note 3) same as RAD restriction LT2070. EUROCONTROL with any changes to RAD restriction LT2070. As from 5 MAY 2011 LT2070 Objective: Project Group: (Note 3) had been changed and during To further improve airspace utilisation between Istanbul FIR, RFG SE the NIGHT period 17.30h - 02.30h Hellas UIR and Sofia FIR. Project Category: (AIRAC APR - AIRAC OCT inclusive) RAD DEP LTAI are allowed to fly via IMR (and not only via VADEN/MAKOL). The most logic option is IMR UN128 LMO PEREN where there are two possibilities UN128 PEREN - FSK - RUGAS or UN133 PEREN - EVIVI. Currently LT2017 is not adapted to LT2070.  This restriction artificially blocks second alternative and AOs are not able to fly via EVIVI. Proposal ID : 93.027 Status: Contributor: Comments: Project Name: Canarias ACC sector split Implementation: State(s) and Org: Related proposals: Description: Planned ESP  93.028 07 OCT 2021 MAR To split the existing Canarias ACC NE sector (FL125 - UNL). Originator(s): 268. Objective: To further improve capacity of Canarias ACC. ESP

Project Group: RFG SW

Project Category: ATC Sectors Proposal ID : 94.040b Status: Contributor: Comments: Project Name: Free Route Airspace Spain - ESFRA Implementation: State(s) and Org:  Subject to availability of the ATS sytem Phase 2 Planned ESP cross-border operations between the

Description: 04 NOV 2021 Originator(s): FIRs/UIRs might be expected. 269. To implement H24 Free Route Airspace, FL195 - FL660 ESP  No sector reorganization possible in the short term. In 2023 able to re- within Madrid FIR/UIR and Barcelona FIR/UIR as single FRA Project Group: organize sectors to accommodate new area and Canarias FIR/UIR. FAB SW flows. Objective: RFG SW

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 93

EUROCONTROL Network Management Directorate

To implement the FRA concept and improve flight planning Project Category:  ATS route network might be withdrawn. options within Spain Free Route Airspace  'Double AIRAC procedure’ for AIRAC High Seas AIP AMDT publication required for implementation (ICAO Annex 15 refers).

Related proposals:  94.040a Proposal ID : 92.065 Status: Contributor: Comments: Project Name: Free Route Airspace Switzerland Implementation: State(s) and Org:  ATS Route Network will be removed

Description: Planned CHE above FL195, except where route To implement H24 Free Route Airspace in skyguide's AoR 02 DEC 2021 FRA segments are needed to provide above FL195. DEU connections with STARs, SIDs and the AUT ATS route network below. Objective: ITA  Implementation of FRA is dependent 1. Compliance, by the end of 2021, with the Commission FAB EC on deployment of new ATM Implementing Regulation (EU) No 716/2014 of 27 June functionalities in skyguide scheduled 270. 2014. Originator(s): for 2020. 2. No loss in sector capacity that affects skyguide's CHE  'Double AIRAC procedure’ for AIRAC performance. Project Group: AIP AMDT publication required for 3. To improve skyguide's service to airspace users by FAB EC implementation (ICAO Annex 15 offering shorter trajectories and simplifying the RAD Project Category: refers). where possible. Free Route Airspace  Due to technical issues 'Double AIRAC procedure’ currently not possible/applicable in Switzerland.

Proposal ID : 87.005f Status: Contributor: Comments: Project Name: FRA Germany - Step 2c Implementation: State(s) and Org:  Gradual Move towards FRA H24 via Planned DEU a flow-wise opening of FRA DCT Description: To implement Free Route Airspace Germany (Solution 02 DEC 2021 Originator(s): options (RAD Apendix 4 DCTs + ATS 2) H24 within South West - core area - above FL245. DEU Route Changes) between JUN 2020 271. and DEC 2021. Objective: FAB EC  ATS route network is kept until H24 To implement H24 Full FRA - according to PCP Project Group: FRA operations are effective. requirements - and improve flight efficiency within Karlsruhe FAB EC  FRA H24 EDUU West: FL 245+. UAC/ FAB EC. Project Category:  FRA H24 EDUU South: FL 310+. Free Route Airspace  'Double AIRAC procedure’ for AIRAC

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 94

EUROCONTROL Network Management Directorate

AIP AMDT publication required for implementation (ICAO Annex 15 refers).

Related proposals:  87.005a  87.005b  87.005c  87.005d  87.005e  87.036c  95.018b Proposal ID : 91.017a Status: Contributor: Comments: Project Name: Free Route Airspace Brest Atlantic - Step Implementation: State(s) and Org:  One FRA Area with two cells LFRR 1.0 Planned FRA FRA North FL245+ and LFRRFRA 02 DEC 2021 FAB EC West FL195+. Description: North West FRA Cell Step 1 - To implement H24 Free Originator(s):  BOTA area will not be part of FRA Route Airspace in Brest ACC Atlantic Area above FL195. FRA Area.  FRA I points should not be used to Objective: Project Group: enter or exit the FRA area from below. To implement FRA Concept and further improve flight FAB EC FRA connectivity from below will be efficiency within Brest ACC. Project Category: only by using A or D points. Free Route Airspace  ATS Route Network will be removed, High Seas except UM25 ANNET - INGOR and 272. UN862 SKESO - UPALO.  'Double AIRAC procedure’ for AIRAC AIP AMDT publication required for implementation (ICAO Annex 15 refers).

Related proposals:  91.017b  91.017c  93.032  93.033  93.034  95.010 Proposal ID : 93.034 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 95

EUROCONTROL Network Management Directorate

Project Name: Free Route Airspace Paris - Step 1.1 Implementation: State(s) and Org: 'Double AIRAC procedure’ for AIRAC AIP

Description: Planned FRA AMDT publication required for 02 DEC 2021 FAB EC implementation (ICAO Annex 15 refers). Center FRA Cell - To implement H24 Free Route Airspace in Paris ACC above FL195 in LMH sector. Originator(s): Related proposals: 273. FRA  91.017a Objective: To implement FRA Concept and further improve flight Project Group:  91.017b efficiency within Paris ACC. FAB EC  91.017c

Project Category:  93.032 Free Route Airspace a. 93.033  95.010 Proposal ID : 93.032 Status: Contributor: Comments: Project Name: Free Route Airspace Bordeaux - Step 1.0 Implementation: State(s) and Org:  ATS Route Network will be removed.

Description: Planned FRA  'Double AIRAC procedure’ for AIRAC 02 DEC 2021 FAB EC AIP AMDT publication required for South West FRA Cell - To implement H24 Free Route Airspace in Bordeaux ACC above FL195. Originator(s): implementation (ICAO Annex 15 refers). FRA Objective: 274. To implement FRA Concept and further improve flight Project Group: Related proposals: efficiency within Bordeaux ACC. FAB EC  91.017a

Project Category:  91.017b Free Route Airspace  91.017c High Seas  93.033  93.034  95.010 Proposal ID : 84.058b Status: Contributor: Comments:

Project Name: Free Route Airspace Santa Maria FIR - Implementation: State(s) and Org: Related proposals: Phase 2 Planned PRT  64.030 02 DEC 2021 Description: Originator(s):  68.002 To reconsider existing boundary points between Santa Maria PRT 1. 84.058a 275. FIR and Lisboa FIR and implement new in support of FRA Project Category: operations. Free Route Airspace Objective: To further improve the airspace utilisation between Santa Maria FIR and Lisboa FIR. Proposal ID : 95.045 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 96

EUROCONTROL Network Management Directorate

Project Name: Split ZGZ / TER upper sector Implementation: State(s) and Org:  ZGZ sector is currently main bottleneck Proposed ESP in Madrid ACC. Description: To increase capacity in Madrid ACC by introduction of Upper autumn 2021 Originator(s):  ZGZ sector is with the highest delays in sector in ZGZ/TER sectors. ESP LECM in the last two years (2017 and 276. 2018). Objective: Project Group:

To further improve Airspace Structure and increase FAB SW

capacity within Madrid ACC. Project Category: Airspace Structure ATC Sectors Proposal ID : 88.019 Status: Contributor: Comments: Project Name: Jersey new ATS delegation Implementation: State(s) and Org: Implementation planned in connection with Proposed FRA New TSA 6 (ID 57.024). Description: To create a new TMA East of existing Jersey CTA with autumn 2021 Originator(s): Related proposals: delegation of ATS. FRA  57.024 277. Objective: Project Category: To further improve the airspace structure at the interface TMA between Jersey APP and London ACC while allowing new Vertical FE Jersey and Guernsey SID/STAR implementation for optimum climb/descent profiles. Proposal ID : 68.022 / 11.019 Status: Contributor: Comments: Project Name: Batumi and Kutaisi TMAs Optimization Implementation: State(s) and Org: Proposed GEO Description: 1. To reconfigure Batumi TMA and establish new autumn 2021 Originator(s): SIDs/STARs ROLIN (FL190/FL180). GEO 278. 2. To expand the existing TMAs, both in their horizontal Project Group: and vertical boundaries. SG BLACK 3. To implement separated SIDs and STARs. Project Category: Objective: TMA To further improve airspace organisation within Tbilisi FIR. Proposal ID : 71.054a Status: Contributor: Comments: Project Name: Free Route Airspace Morocco (MORFRA), Implementation: State(s) and Org:  Coordination with NM required to 279. Phase 3 Proposed MAR ensure harmonised network FRA

Description: autumn 2021 ESP implementation. PRT  Night period 22:00 - 06:00 UTC. To implement Night / Week-end Free Route Airspace

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 97

EUROCONTROL Network Management Directorate

FL195 - FL460 within the AoR of Casablanca ACC. Originator(s):  'Double AIRAC procedure’ for AIRAC MAR AIP AMDT publication required for Objective: To further improve the flight planning options within Project Group: implementation (ICAO Annex 15 Casablanca FIR. RFG SW refers).  ATS Route Network will be removed. Project Category: Free Route Airspace Related proposals: 1. 71.047  71.054b Proposal ID : 71.089e Status: Contributor: Comments: Project Name: Free Route Airspace Malta - Phase 3c Implementation: State(s) and Org:  Limited benefits of lowering FRA DFL Proposed MLT due to missing traffic flows as a result Description: To implement H24 Free Route Airspace FL195 - autumn 2021 Originator(s): of the Libyan crises. FL660 within Malta UIR. MLT  'Double AIRAC procedure’ for AIRAC AIP AMDT publication required for Objective: Project Group: implementation (ICAO Annex 15 280. To further improve the flight planning options within Malta FAB BLUE MED refers). UIR. Project Category:  ATS Route Network available. Free Route Airspace Related proposals:  71.089a  71.089b  71.089c  90.018 Proposal ID : 90.018 Status: Contributor: Comments: Project Name: INTRAC Phase 2 Implementation: State(s) and Org: INTRAC/ New Terminal Routing Airspace Proposed MLT Concept Description: To design a new TMA and SIDs / STARs. autumn 2021 Originator(s): Related proposals: 281. Objective: MLT  71.089e

To further improve the airspace organisation within Malta Project Category: FIR. PBN TMA Proposal ID : 99.013a Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Romania Implementation: State(s) and Org:

282. Proposed ROU Description: To change existing CDR Categories into a single CDR autumn 2021 Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 98

EUROCONTROL Network Management Directorate

category. ROU

Objective: Project Category: To further improve flight planning options while reducing CDRs CDR complexity by simplifying the CDR category in SCC Romania. Proposal ID : 99.013b Status: Contributor: Comments: Project Name: Single CDR Category (SCC) - Romania Implementation: State(s) and Org: Step 2 Proposed ROU

Description: autumn 2021 Originator(s): To change all existing CDR Categories into a single CDR ROU 283. category. Project Category: Objective: CDRs To further improve flight planning options while reducing SCC CDR complexity by simplifying the CDR category in Romania. Proposal ID : 81.022a / 19.061a Status: Contributor: Comments: Project Name: FRATURK - Phase 1 Implementation: State(s) and Org:  Encompasses the boundaries of Proposed TUR Istanbul and Ankara FIRs as published Description: To implement Night FRA Operations above FL335 in autumn 2021 Originator(s): in AIP of Republic of Turkey, ENR 2.1. Turkey. TUR FRA concept is not applied in the airspace of TMAs and CTRs. Objective: EUROCONTROL  Night period 23.00 - 05.00 UTC. To implement FRA operations in Ankara and Istanbul FIRs Project Group:  Extension of FRA lower limit to FL 305 RFG SE will be considered after gaining some 284. SG BLACK experience with FRA operations and Project Category: conducting a post-implementation Free Route Airspace assessment.  'Double AIRAC procedure’ for AIRAC AIP AMDT publication required for implementation (ICAO Annex 15 refers).

Related proposals:  81.022b / 19.061b Proposal ID : 99.030b Status: Contributor: Comments: 285. Project Name: SECSI FRA - FRALB H24 cross-border Implementation: State(s) and Org:  ATS route network removed.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 99

EUROCONTROL Network Management Directorate

FRA Planned ALB  The South East Common Sky Initiative/

Description: 30 DEC 2021 AUT SECSI FRA includes the airspace the To expand to H24 existing Night Cross Border Free Route HRV AoRs of Wien ACC, Ljubljana ACC, Airspace between SECSI FRA and FRALB. SVN Zagreb ACC, Sarajevo ACC and SRB Beograd ACC. Objective: MNE  'Double AIRAC procedure’ for AIRAC To further harmonise the implementation of Free Route BIH AIP AMDT publication required for Airspace flight options as a single cross-border FRA area in implementation (ICAO Annex 15 South East Europe between the AoRs of Tirana ACC, Wien Originator(s): refers). EUROCONTROL ACC, Ljubljana ACC, Zagreb ACC, Sarajevo ACC and Beograd ACC. Project Category: Related proposals: Free Route Airspace  71.086a High Seas  71.086b  90.010  99.030a Proposal ID : 84.074 Status: Contributor: Comments: Project Name: 5LNC replacement by Germany Implementation: State(s) and Org:  ANIBI is reserved in ICARD for Planned DEU Morocco and used as VFR point. Description: To replace existing 5LNC ANIBI. 30 DEC 2021 Originator(s):  Proposal for replacement is based on “Common criteria for replacement of Objective: EUROCONTROL 286. duplicated 5LNCs” as point is not To avoid 5LNCs duplication within the ECAC area of the ICAO reserved for Germany. ICAO EUR/NAT region, to improve the aeronautical Project Category: information provided and be compliant with ICAO Annex 11. 5LNC Related proposals: 1. 98.062 Proposal ID : 95.025 Status: Contributor: Comments: Project Name: New ATM system Praha ACC Implementation: State(s) and Org: Planned CZE Description: 287. To implement the new ATM system TopSky in Praha ACC. 24 FEB 2022 Originator(s):

CZE Objective: To further improve the ACC capacity within Paha ACC. Project Category: ATM System Proposal ID : 94.043 Status: Contributor: Comments: Project Name: Baltic FAB cross border FRA Implementation: State(s) and Org: 'Double AIRAC procedure’ for AIRAC AIP 288. Description: Planned LTU AMDT publication required for 24 FEB 2022 POL implementation (ICAO Annex 15 refers). To implement H24 cross border FRA within the Baltic FAB

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 100

EUROCONTROL Network Management Directorate

area. Originator(s): Related proposals:

Objective: LTU a. 75.040b / 15.042b POL  76.053 / 18.039 To further improve the Free Route Airspace operations and flight efficiency between Warszawa FIR and Vilnius FIR. Project Group: 1. 98.028 / 31.011 SG BALTIC

Project Category: Free Route Airspace Proposal ID : 95.037 Status: Contributor: Comments: Project Name: Copenhagen SIDs/STARs re-design Implementation: State(s) and Org:

Description: Proposed DNK To implement PBN in Copenhagen Area and re-design of winter 2021/22 SWE 289. SIDs/STARs. Originator(s): DNK Objective: To further improve airspace structures in Copenhagen Area. Project Category: TMA Proposal ID : 95.046 Status: Contributor: Comments: Project Name: Third layer TLU and DGU-PAU Implementation: State(s) and Org:  Increase of capacity is expected Proposed ESP to reduce the need of scenarios to Description: To increase capacity in Madrid ACC: winter 2021/22 Originator(s): manage demand. a) by introduction of third layer in TLU and DGU-PAU ESP  Third layer split is necessary to reduce 290. overloads, delays and increase sectors. Project Group: capacity at higher FLs. Objective: RFG SW

To further improve Airspace Structure and increase capacity Project Category: within Madrid ACC. Airspace Structure ATC Sectors Proposal ID : 85.018 Status: Contributor: Comments: Project Name: PBN SIDs/STARs Athens TMA Implementation: State(s) and Org: Connected to PBN implementation in Proposed GRC Athens TMA. Description: To implement new SIDs/STARs for Athens (LGAV) airport. winter 2021/22 Originator(s): 291. GRC Objective: To further improve the airspace organisation within Athinai Project Category: FIR. Airspace Structure PBN

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 101

EUROCONTROL Network Management Directorate

Proposal ID : 98.025 Status: Contributor: Comments:

Project Name: Northern Norway TMAs airspace re- Implementation: State(s) and Org: Related proposals: organization Proposed NOR 1. 98.029 Description: winter 2021/22 Originator(s):  98.057 1. To implement and realign SIDs and STARs for ENTC, NOR

292. ENDU, ENEV and ENBO airports. Project Category: 2. To adapt procedures to ATM requirements and military TMA operations.

Objective: To further improve the airspace organization to/from ENTC, ENDU, ENEV and ENBO airports. Proposal ID : 97.039 Status: Contributor: Comments: Project Name: AMC Poland - FMP Warszawa Implementation: State(s) and Org: coordination procedures Proposed POL

Description: winter 2021/22 Originator(s): 1. To implement close cooperation between AMC Poland POL

and FMP Warszawa. Project Category: 2. To implement new coordination procedures taking Civil/Military Airspace 293. into account forecasted demand of civil traffic on segregated airspace allocation in time on the day of the operations.

Objective: To further improve airspace procedures while reducing as much as possible the restrictive influence of segregated areas on civil traffic. Proposal ID : 80.003 Status: Contributor: Comments: Project Name: Removal U prefix Lisboa FIR Implementation: State(s) and Org:  "U" prefix removal for all routes below Proposed PRT FRAL is under consideration. Description: 294. To remove the distinction between Upper and Lower ATS winter 2021/22 Originator(s):  Further adaptation of lower and upper routes - "U" prefix within Lisboa FIR. PRT ATS routes might be required.  Postponed for after the new system Objective: Project Category: implementation in Lisboa. To simplify Air Traffic Management in Lisboa FIR. ATS Routes Proposal ID : 82.005 Status: Contributor: Comments: 295. Project Name: ATS route re-designation Lisboa FIR Implementation: State(s) and Org: Requirement is due to duplicate use in

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 102

EUROCONTROL Network Management Directorate

Description: Proposed PRT different parts of the ICAO EUR/NAT region

To re-designate the following ATS routes: winter 2021/22 Originator(s): of route designators. a) Y101 ODEMI - USALU as new Y; EUROCONTROL Removal of U Prefix is delayed. b) Y102 XAPAS - USALU as new Y; c) Y103 VFA - GIMAL as new Y; Project Category: d) Y105 ERTIS - GENRO as new Y; Route Redesignation e) Y207 FTM - LIS - EKMAR as new Y; f) UZ4 BAROK - ESP as new Z; g) UZ5 PIREN - ESP as new Z; h) Z11 DEGUN - VERAM as new Z; i) Z14 NARTA - LIDRO as new Z; j) Z15 BABEX - OTPAK as new Z; k) UZ21 BUSEN - GUNTI as new Z; l) UZ28 DIRMA - BANAL as new Z; m) UZ29 DIRMA - ARMED as new Z; n) UZ220 ABALO - NIDUL as new Z; o) Z226 INBOM - PRT as new Z; p) UH80 ASPOR - PRT as T7 or T326 or T328; q) W/UW106 RALUS - MOSEN as Z/UZ406.

Objective: To further simplify the existing RDs within Portugal and avoid duplication in ICAO EUR Region. Proposal ID : 81.018a / 19.021a Status: Contributor: Comments: Project Name: FRAU Free Route Airspace Ukraine, Step Implementation: State(s) and Org:  'Double AIRAC procedure’ for AIRAC 2 (Sc 2a) Proposed UKR AIP AMDT publication required for

Description: winter 2021/22 Originator(s): implementation (ICAO Annex 15 To implement cross-border H24 - Free Route Airspace within UKR refers). Lviv ACC, Kyiv ACC, Odesa ACC and Dnipro ACC from  ATS Route Network available. 296. Project Group: FL275 to FL660. RFG SE Related proposals:

Objective: SG BLACK  71.040a / 16.026a 1. 71.040b / 16.026b To implement FRA Concept and further improve flight Project Category: efficiency within Kyiv UIR. Free Route Airspace  71.040c / 16.026c  71.040d / 16.026d  81.018b / 19.021b Proposal ID : 89.003 Status: Contributor: Comments: 297. Project Name: ATS Route Improvement Brussels FIR/ Implementation: State(s) and Org:  RAD restrictions and military area/

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 103

EUROCONTROL Network Management Directorate

Langen FIR Proposed BEL EDR-117 require a longer routing to spring 2022 DEU provide a sensible decent profile. Description: To re-consider existing option for ARR EDDK from South via Originator(s):  Linked to Langen 2.0, delayed UFN. ATS route T860 IBESA. IACA IATA Objective: To further improve the ATS route network at the interface Project Category: between Brussels ACC, Langen ACC and Maastricht UAC. ATS Routes Proposal ID : 77.029 Status: Contributor: Comments: Project Name: Palma TMA Reorganisation - Phase 3 Implementation: State(s) and Org:  The new SID would be 7 NM shorter West Proposed ESP than the current one and it could be

Description: spring 2022 Originator(s): used by a significant amount of flights 1. To re-organise Palma TMA Sectors. EUROCONTROL and City Pairs (138 flights, 58 City 2. To introduce new RNAV1 procedures in Palma TMA. IACA Pairs, on 29 June 2012).  To be considered in the context of 3. To implement new SID MEROS and/or CHELY from Project Category: Palma and Ibiza TMA re-organisation 298. Palma (LEPA) airport. TMA 4. To implement new SID PTC from Ibiza (LEIB) airport. as well as LUMAS project.

Objective: Related proposals: To provide AOs with additional and more efficient options for a. 66.053e traffic departing from LEPA and proceeding north-eastbound. a. 75.007 To further improve the ATS route network within Barcelona a. 89.011 FIR while allowing a shorter route connection to existing route segment PTC - CPD - CHELY/ MEROS. Proposal ID : 82.019 Status: Contributor: Comments: Project Name: Malaga TMA Implementation: State(s) and Org: Currently crews can only request the Proposed ESP BLN2H SID on departure (on ATC Description: 1. To re-design existing Malaga TMA. spring 2022 Originator(s): Approval). This is very rarely given and 2. To introduce Point Merge system for ARR LEMG. IACA aircraft route to the south on BLN2C which 299. 3. To re-design relevant SIDs/STARs especially those uses an additional 145 kg of fuel. The large Project Category: number of departures routing to the north SIDs via GDA (Granada), to be able to permanently file Airspace Structure flight plans independent of Military activity. via BLN would bring significant environmental benefits. Objective: To further improve departure and arrival procedures and improve flight efficiency and the environment. Proposal ID : 73.053c Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 104

EUROCONTROL Network Management Directorate

Project Name: Barcelona TMA - Phase 2 Implementation: State(s) and Org: Complete redesign of the TMA Proposed ESP Description: Related proposals: To introduce new PBN structure for Barcelona TMA. spring 2022 Originator(s):  73.053a 300. Objective: ESP  73.053b

To further improve airspace organisation within Barcelona Project Category: TMA. PBN TMA Proposal ID : 89.012b Status: Contributor: Comments:

Project Name: Madrid TMA - Phase 2 Implementation: State(s) and Org: Related proposals: Proposed ESP Description: 1. 89.012a To implement independent parallel approaches for LEMD spring 2022 Originator(s): 301. Madrid Barajas Airport (Northbound configuration). ESP

Objective: Project Category: To increase capacity and efficiency in Madrid TMA. PBN TMA Proposal ID : 89.011 Status: Contributor: Comments:

Project Name: Palma TMA Reorganisation - Phase 1 Implementation: State(s) and Org: Related proposals: East Proposed ESP 1. 77.029 Description: spring 2022 Originator(s): 302. To re-organise Menorca TMA sectors. ESP

Objective: Project Category: To further improve airspace organisation within Barcelona Airspace Structure FIR. ATC Sectors TMA Proposal ID : 89.007 Status: Contributor: Comments: Project Name: FINEST - Cross-border sectorisation Implementation: State(s) and Org:

Description: Proposed EST spring 2022 FIN To introduce: 1. Operational cross FIR boundaries sector design and Originator(s): 303. ATC sectors tactical utilization according to traffic FAB NEFAB

trajectories; Project Category: 2. Dynamical Cross-border ANS provision between ANS Airspace Structure Finland and EANS. FRA Connecting route adjustments ATC Sectors to support available capacity.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 105

EUROCONTROL Network Management Directorate

Objective: To efficiently accommodate future traffic flows. Proposal ID : 69.095a Status: Contributor: Comments: Project Name: Future Airspace Strategy Implementation Implementation: State(s) and Org:  To establish PRNAV procedures, - North (FASI-N) Proposed GBR revised SIDs that accommodate CCDs,

Description: spring 2022 Originator(s): revised STARs allowing CDAs from To re-design the Northern Terminal Control Area/ NTCA of GBR higher altitudes, improved arrival and Prestwick ACC (formerly Manchester TMA project) and departure management and holding Project Category: concepts to include Point Merge, if and 304. then PLAS 2b. PBN where considerate appropriate. Objective: TMA  To consider specific requests for route To further improve the airspace structure within London FIR improvements from the operators such through redesign in order to enhance safety, capacity and as TNT - LAMIX and LIBSO - PEDIG. provide environmental improvements with expected traffic  In NOP: PC Lower Airspace Phase 1 growth from airfields in Northern England. (2017), Phase 2 (2018), Phase 3 (2019). Proposal ID : 94.058 Status: Contributor: Comments: Project Name: Future Airspace Strategy Implementation Implementation: State(s) and Org:  Edinburgh, Glasgow and NATS - North Proposed GBR Prestwick Centre are working together

Description: spring 2022 Originator(s): in accordance with the UK's new To improve airspace of Prestwick ACC AoR: GBR CAP1616 airspace change process.  The proposed implementation status a. Replacement of the LANAK hold with the RULUR hold, Project Category: will be updated more accurately when which moves approx. 4NM further South East; ATS Routes b. Replacement of existing STAR’s to LANAK with RNAV5 more information on the particular 305. STAR’s to RULUR (5 STAR’s); proposals has been received form the c. New RNAV1 route to link to the end of Edinburgh’s sponsors. MAVIX SID. Moving the Talla/Galloway Sector boundary; d. Amendment of one STAR inbound to Edinburgh Airport (amendment to the Edinburgh ACP).

Objective: To further improve airspace efficiency and remove dependency on ground based Nav Aids. Proposal ID : 94.059 Status: Contributor: Comments: 306. Project Name: ATS Route Improvement Edinburgh Implementation: State(s) and Org:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 106

EUROCONTROL Network Management Directorate

airport Proposed GBR

Description: spring 2022 Originator(s): To improve airspace structure at Edinburgh airport: GBR

a) Replacement of the TWEED Hold with the EDIBO Hold Project Category: which moves slightly South East; ATS Routes b) Replacement of Existing STAR’s to TWEED with RNAV5 STAR’s to EDIBO (4 STAR’s) and replication of the existing STAR to STIRA to RNAV5; c) Two new RNAV1 inbound transitions from the EDIBO Hold and GNSS approaches for either end of the runway. Introduction of 10 new RNAV1 SID’s, which include usage based on type, time and day of the week. Several SID’s climb to FL’s (FL100/ FL150). New SID’s can provide reduced departure separations dependant on aircraft type and routing.

Objective: To further improve airspace efficiency and remove dependency on ground based Nav Aids. Proposal ID : 97.037 Status: Contributor: Comments: Project Name: Expansion Radom/ EPRA airport Implementation: State(s) and Org: Proposed POL Description: To expand Radom/ EPRA airport with radar approach spring 2022 Originator(s): service provided by Warsaw APP. POL 307. Objective: Project Category: To further improve the airspace structure and enhance Airspace Structure efficiency for Radom regional airport, mainly dedicated to accommodate charter and low-cost traffic. Proposal ID : 99.015a Status: Contributor: Comments: Project Name: Reorganisation ACC Warszawa sector Implementation: State(s) and Org:  Depending on technical issues configuration – three layer division - Step 2 Proposed POL (frequencies) and increasing the

Description: spring 2022 Originator(s): amount of ATC staff. 308. To implement a new airspace structure and sectorisation POL  New elementary sectors with vertical splits. within Warszawa ACC considering vertical splits (division Project Category: into three layers),  Division into three layers. Airspace Structure Step 2 : EPWWT, EPWWC Related proposals: ATC Sectors  62.091e

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 107

EUROCONTROL Network Management Directorate

Objective:  99.015b To further improve the airspace structure within Warszawa  99.015c ACC and increase capacity while applying vertical splits. Proposal ID : 71.088a Status: Contributor: Comments: Project Name: Free Route Airspace Cyprus - FRANIC Implementation: State(s) and Org:  Studies ongoing in the context of Blue Phase 1 Proposed CYP Med.

Description: summer 2022 Originator(s):  Needs alignment with IDP & TEN-T. To implement H24 Free Route Airspace FL285 - FL660 in CYP  'Double AIRAC procedure’ for AIRAC Nicosia FIR. FAB BLUE MED AIP AMDT publication required for 309. implementation (ICAO Annex 15 Objective: Project Group: refers). To align the airspace structure with real operations. FAB BLUE MED RFG SE Related proposals:

Project Category:  71.088b Free Route Airspace 1. 86.056a  86.056b Proposal ID : 50.053e Status: Contributor: Comments:

Project Name: Lisboa / Casablanca / Canarias Axis Implementation: State(s) and Org: Related proposals: Phase 2 Proposed ESP  50.053a Description: summer 2022 PRT a. 50.053b MAR To review the airspace organisation on the Lisboa /  50.053c Casablanca / Canarias axis: Originator(s):  50.053d a) to optimise the ATS route network in line with the new ESP  60.034b Canarias TMA organisation; PRT  73.052 b) PRNAV structure for Canarias TMA, Phase 2 (includes MAR  75.022 Casablanca / Canarias interface); 310. Project Group: c) Interface Canarias/Agadir ACC and FAB SW Canarias/Casablanca ACC development; RFG SW d) Interface between Lisboa/Agadir ACCs to be considered if required; Project Category: e) Interface between Agadir/ACC and Sevilla ACC to be Airspace Structure revisited. PBN TMA Objective: To further improve the ATS route network and airspace organisation within Canarias FIR/UIR, Casablanca FIR/UIR, Lisboa FIR and Madrid FIR/UIR. Proposal ID : 98.020b Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 108

EUROCONTROL Network Management Directorate

Project Name: Bratislava ACC re-sectorisation - Step 2 Implementation: State(s) and Org: Split of LZBBU3 and LZBBU4 sectors

Description: Proposed SVK according to traffic demand and based summer 2022 upon the staff availability. To implement an additional geographical split for Bratislava Originator(s): ACC sectorisation, allowing a 7 sector configuration. SVK Related proposals: 311. 1. 98.020a Objective: Project Category: To further improve the airspace structure within Bratislava Airspace Structure FIR while providing additional sector configuration to better ATC Sectors distribute traffic demand between ACC sectors and reduce workload. Proposal ID : 93.028 Status: Contributor: Comments: Project Name: Canarias APP sector split Implementation: State(s) and Org: APP sector located below ACC NE sector. Planned ESP With current NE capacity, the approach Description: To split of existing Canarias APP AAC sector (GND - 06 OCT 2022 Originator(s): sector is overloaded often and needs to be regulated. 312. FL125). ESP

Objective: Project Group: Related proposals: To further improve capacity of Canarias APP. RFG SW  93.027

Project Category: ATC Sectors Proposal ID : 93.011 Status: Contributor: Comments: Project Name: DCT Marseille ACC Implementation: State(s) and Org:  Required for air refuelling flights of Proposed FRA USAF via Marseille ACC AoR. Description: To allow “Direct” flight planning option SOTAX DCT ODAKA autumn 2022 Originator(s):  The option will be alternative below DCT ELSAG for traffic Type M below FL275. U.S.A.F.E FL275 and Marseille ACC will be properly informed by USAF when this 313. Objective: Project Category: option will be used. To further improve flight planning options within Marseille DCTs  Current option via existing ATS routes ACC. RAD SOTAX UM871 EYEKO UM986 ORKUM UM603 ELSAG is 17.6NM longer. Proposal ID : 87.028f Status: Contributor: Comments: Project Name: Borealis FRA - Step 6 Implementation: State(s) and Org:  A delay may occur due to COVID-19

314. Proposed GBR crisis, additional information will follow. Description: NATS Free Route Airspace Deployment 2 - To implement autumn 2022 Originator(s): Planned implementation as soon as H24 Free Route Airspace across certain sectors of the FAB Denmark/Sweden possible after Step 4. Impact on

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 109

EUROCONTROL Network Management Directorate

Swanwick ACC AoR. Specifically, in the following sectors: FAB NEFAB Swanwick still to be evaluated. a) Sector 9 (FL245+); FAB UK/Ireland Potential coincident with Step 4. b) Sectors 5, 8, 35 & 36 (FL305+). ISL  Borealis Steps 4, 6 and 7 dependent

Objective: Project Group: on the timely update of the ATM To further improve the airspace structure and the flight FAB Denmark/Sweden system in Swanwick ACC. planning options within parts of the London FIR (part of FAB NEFAB  Transition to Free Route operations. Borealis FRA) while providing Cross Border FRA operations FAB UK/Ireland  Cross Border FRA operations with with Ireland FRA. RFG NW Ireland.  'Double AIRAC procedure’ for AIRAC Project Category: AIP AMDT publication required for Free Route Airspace implementation (ICAO Annex 15 refers).

Related proposals:  81.073a  87.028a  87.028b  87.028c  87.028d  87.028e  87.028g  87.028h Proposal ID : 87.028d Status: Contributor: Comments: Project Name: Borealis FRA - Step 4 - Scottish Free Implementation: State(s) and Org:  A delay will occur due to COVID-19 Route Airspace Proposed GBR crisis, new implementation date(s) will

Description: autumn 2022 Originator(s): follow. Original implementation was NATS Free Route Airspace Deployment 1 - To implement FAB Denmark/Sweden planned for summer 2017, postponed H24 Free Route Airspace FL255 - FL660 at Prestwick ACC FAB NEFAB at RNDSG/89 due to technical reason, AoR within the following ATC Sectors: FAB UK/Ireland as FRA depends on new platform a) Rathlin East Sector; ISL delivery (March 2021) and will be 315. implemented after deployment of the b) Rathlin West Sector; Project Group: c) Central Sector; new ITEC system at Prestwick ACC. FAB Denmark/Sweden  Full Cross Border operations with d) Hebrides High Sector; FAB NEFAB Ireland FRA and NEFRA. e) Moray High Sector; FAB UK/Ireland  Interface with Shanwick OAC and f) Part of Tyne Sector; RFG NW g) Montrose North Sector; Reykjavik OAC remains as today. h) Part of Dean Cross North Sector. Project Category:  'Double AIRAC procedure’ for AIRAC Free Route Airspace Objective: AIP AMDT publication required for

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 110

EUROCONTROL Network Management Directorate

To further improve the airspace structure and the flight implementation (ICAO Annex 15 planning options within Scottish FIR (part of Borealis FRA) refers). while providing Full Cross Border operations with Ireland  ATS route network (all Upper Air FRA and NEFRA. Routes and Conditional Routes) within FRA volume will be removed above FL255.

Related proposals:  81.073a  87.028a  87.028b  87.028c  87.028e  87.028f  87.028g  87.028h Proposal ID : 81.022b / 19.061b Status: Contributor: Comments: Project Name: FRATURK - Phase 2 Implementation: State(s) and Org:  Encompasses the boundaries of Proposed TUR Istanbul and Ankara FIRs as published Description: To implement H24 FRA Operations above FL335 in Turkey. autumn 2022 Originator(s): in AIP of Republic of Turkey, ENR 2.1. TUR FRA concept is not applied in the Objective: airspace of TMAs and CTRs. To implement FRA operations in Ankara and Istanbul FIRs. EUROCONTROL  Extension of FRA lower limit to FL 305 Project Group: or FL285 will be considered after RFG SE gaining some experience with FRA 316. SG BLACK operations and conducting a post- Project Category: implementation assessment. Free Route Airspace  'Double AIRAC procedure’ for AIRAC AIP AMDT publication required for implementation (ICAO Annex 15 refers).

Related proposals:  81.022a / 19.061a Proposal ID : 98.045 Status: Contributor: Comments: Project Name: LOVV 2020 Airspace Re-Structuring Implementation: State(s) and Org: 317. Description: Proposed AUT

1. To provide a new “0”- layer from FL165 – FL245 for winter 2022/23 CZE

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 111

EUROCONTROL Network Management Directorate

LOVV ACC sectors W/B/N/S. DEU 2. LOVV B - sector above LOWS APP and LOVV S - HRV sector overhead MURA the “0”-sector will reach from HUN FL125 up to FL245. ITA 3. The new "0"-sectors can be combined flexibly, either SVK with the Local Approach Units (LAUs) below or with the SVN

“1”-sectors above as they are today. Originator(s): 4. Above FL245 the current ACC sectorization will remain. AUT

Objective: Project Category: To improve capacity by splitting the “1”-sectors (lowest ATC Sectors sector layer) of Wien ACC and creating a new lower ACC TMA sector “0” (“zero”) below each LOVV ACC “1”-sectors. Proposal ID : 93.033 Status: Contributor: Comments: Project Name: Free Route Airspace Reims - Step 2.0 Implementation: State(s) and Org: 'Double AIRAC procedure’ for AIRAC AIP

Description: Proposed FRA AMDT publication required for winter 2022/23 FAB EC implementation (ICAO Annex 15 refers). North East FRA Cell - To implement H24 Free Route Airspace in Reims ACC. Originator(s): Related proposals: 318. FRA  91.017a Objective: To implement FRA Concept and further improve flight Project Group:  91.017b efficiency within Reims ACC. FAB EC  91.017c

Project Category:  93.032 Free Route Airspace  93.034  95.010 Proposal ID : 93.030 Status: Contributor: Comments: Project Name: Airspace Structure Improvement Implementation: State(s) and Org: Marseille ACC Proposed FRA

319. Description: winter 2022/23 Originator(s): To improve LFKJ interface within Marseille ACC. FRA

Objective: Project Category: To further improve the airspace structure within France FIR. Airspace Structure Proposal ID : 95.010 Status: Contributor: Comments: Project Name: Free Route Airspace Marseille ACC - Step Implementation: State(s) and Org: 'Double AIRAC procedure’ for AIRAC AIP 320. 2.0 Proposed FRA AMDT publication required for winter 2022/23 implementation (ICAO Annex 15 refers). Description: Originator(s):

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 112

EUROCONTROL Network Management Directorate

South East FRA Cell - To implement H24 Free Route FRA Related proposals: Airspace in Marseille ACC.  91.017a Project Category: Objective: Free Route Airspace  91.017b To implement FRA Concept and further improve flight  91.017c efficiency within Marseille ACC.  93.032  93.033  93.034 Proposal ID : 91.017b Status: Contributor: Comments: Project Name: Free Route Airspace Brest Continental Implementation: State(s) and Org:  ATS Route Network will be removed. West- Step 1.2 Proposed FRA  'Double AIRAC procedure’ for AIRAC

winter 2022/23 FAB EC AIP AMDT publication required for Description: North West FRA Cell Step 2 - To implement H24 Free Originator(s): implementation (ICAO Annex 15 Route Airspace in Brest ACC Central Area above FL195. refers). FRA

321. Objective: Project Group: Related proposals: To implement FRA Concept and further improve flight FAB EC  91.017a

efficiency within Brest ACC. Project Category:  91.017c Free Route Airspace  93.032 High Seas  93.033  93.034 a. 95.010 Proposal ID : 91.020b Status: Contributor: Comments: Project Name: Hellas FRA - Free Route Airspace Greece Implementation: State(s) and Org:  'Double AIRAC procedure’ for AIRAC - Phase 4b Proposed GRC AIP AMDT publication required for

Description: winter 2022/23 Originator(s): implementation (ICAO Annex 15 To implement H24 Free Route Airspace within Hellas UIR GRC refers). FL335 - FL460. FAB BLUE MED  ATS Route Network available.  Gradual implementation of lower 322. Objective: Project Category: vertical limits till end 2022. To further improve flight planning options within Hellas UIR. Free Route Airspace Related proposals:  91.018a  91.018b  91.019  91.020a Proposal ID : 89.060a Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 113

EUROCONTROL Network Management Directorate

Project Name: NORWAY FAS (Future ATM System) - Implementation: State(s) and Org: Spring 2024 for North sectors. South Proposed NOR Related proposals: Description: spring 2023 Originator(s):  89.060b To introduce a new operating system iTEC (interoperability NOR 323. Through European Collaboration) for the South sectors Project Category: within Norway FIR. ATM System Objective: The project will introduce a Trajectory Based FDP system and associated Controller Tools to Norway FIR. Proposal ID : 98.031 Status: Contributor: Comments: Project Name: FAB DK-SE - Baltic FAB Cross Border Implementation: State(s) and Org: FRA Proposed POL

Description: spring 2023 SWE To implement H24 Cross Border Free Route Airspace DNK between FAB DK-SE and Baltic FAB. EST FAB Baltic Objective: FAB Denmark/Sweden To allow more efficient flight planning GBR IRL ISL NOR 324. FIN LVA LTU

Originator(s): POL SWE

Project Group: FAB Baltic FAB Denmark/Sweden

Project Category: Free Route Airspace Proposal ID : 99.015b Status: Contributor: Comments: Project Name: Reorganisation ACC Warszawa sector Implementation: State(s) and Org:  Depending on technical issues 325. configuration – three layer division - Step 3 Proposed POL (frequencies) and increasing the spring 2023 amount of ATC staff.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 114

EUROCONTROL Network Management Directorate

Description: Originator(s):  New elementary sectors with vertical To implement a new airspace structure and sectorisation POL splits.

within Warszawa ACC considering vertical splits (division Project Category:  Division into three layers.

into three layers), Airspace Structure Related proposals: Step 2 : EPWWB, EPWWD ATC Sectors  62.091e Objective:  99.015a To further improve the airspace structure within Warszawa ACC and increase capacity while applying vertical splits. Proposal ID : 98.016 Status: Contributor: Comments: Project Name: SEE FRA Phase 2 Implementation: State(s) and Org: 'Double AIRAC procedure’ for AIRAC AIP

Description: Proposed SVK AMDT publication required for summer 2023 BGR implementation (ICAO Annex 15 refers). To expand SEE FRA time availability from Night to H24 within Bratislava FIR. HUN Related proposals: ROU  69.052 326. Objective: To further improve the Free Route Airspace operations Originator(s): a. 81.001 SVK  82.033 within Bratislava FIR. Project Group:  90.034 RFG SE  98.015

Project Category: Free Route Airspace Proposal ID : 81.018b / 19.021b Status: Contributor: Comments: Project Name: FRAU Free Route Airspace Ukraine, Step Implementation: State(s) and Org:  Class C Airspace, in Ukraine, at 2 (Sc 2b) Proposed UKR present - (year 2014) is at FL105 and

Description: summer 2023 Originator(s): above. To extend implementation of cross-border H24 - Free Route UKR  'Double AIRAC procedure’ for AIRAC AIP AMDT publication required for Airspace operations in entire Class C Airspace. Project Group: implementation (ICAO Annex 15 Objective: RFG SE 327. refers). To implement FRA Concept and further improve flight SG BLACK Related proposals: efficiency within Lviv CTA/UTA, Kyiv CTA/UTA, Odesa Project Category:  71.040a / 16.026a CTA/UTA and Dnipro CTA/UTA. Free Route Airspace  71.040b / 16.026b a. 71.040c / 16.026c  71.040d / 16.026d  81.018a / 19.021a Proposal ID : 89.010 Status: Contributor: Comments:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 115

EUROCONTROL Network Management Directorate

Project Name: Canarias TMA Phase 2a Implementation: State(s) and Org: Planned ESP Description: To implement RNAV 1 structure in Canarias TMA - Phase 05 OCT 2023 Originator(s): 328. 2a. ESP

Objective: Project Category: To further improve the flight efficiency within Canarias FIR. Airspace Structure PBN TMA Proposal ID : 87.028g Status: Contributor: Comments: Project Name: Borealis FRA - Step 7 Implementation: State(s) and Org:  The implementation of FRA at Planned GBR Prestwick ACC and Swanwick ACC are Description: NATS Free Route Airspace Deployment 3 - To implement 28 DEC 2023 Originator(s): currently planned to be conducted at H24 Free Route Airspace across certain sectors of the FAB Denmark/Sweden the same time. Prestwick ACC & Swanwick ACC AoRs. Specifically, in the FAB NEFAB  Borealis Steps 4, 6 and 7 dependent following sectors: FAB UK/Ireland on the timely update of the ATM a) Part of Tyne sector (FL255+); ISL system in Swanwick ACC.  Transition to Free Route operations. b) Part of Dean Cross North sector (FL255+); Project Group:  Cross Border FRA operations with c) Dean Cross South sector (FL255+); FAB Denmark/Sweden d) Humber sector (FL255+); FAB NEFAB Ireland and NEFRA. e) Montrose South sector (FL255+); FAB UK/Ireland  This step represents full 329. f) Sectors 3, 4, 7, 10 & 11 (FL305+). implementation of FRA in Scottish FIR. RFG NW Objective:  'Double AIRAC procedure’ for AIRAC Project Category: AIP AMDT publication required for To further improve the airspace structure and the flight Free Route Airspace planning options within parts of the Scottish & London FIRs implementation (ICAO Annex 15 refers). (part of Borealis FRA)while providing full Cross Border FRA operations with Ireland FRA and NEFRA. Related proposals:  87.028a  87.028b  87.028c  87.028d  87.028e a. 87.028f  87.028h Proposal ID : 95.012 Status: Contributor: Comments: 330. Project Name: Krakow airport Implementation: State(s) and Org:

Proposed POL

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 116

EUROCONTROL Network Management Directorate

Description: 2023 Originator(s): To implement a new runway at Krakow airport. POL

Objective: Project Category: To further improve the airspace structure and increase the Airspace Structure capacity for Krakow airport. TMA Proposal ID : 99.037 Status: Contributor: Comments: Project Name: FRA based re-sectorisation Sofia ACC Implementation: State(s) and Org: Proposed BGR Description: To reorganise and adapt Sofia ACC sectors based on FRA winter 2023/24 Originator(s): 331. implementation and further flow orientation change analysis. BGR

Objective: Project Category: To further improve the airspace organisation within Sofia Airspace Structure FIR, to better suit demand redistribution and enhance ATC Sectors capacity. Proposal ID : 89.070 Status: Contributor: Comments: Project Name: New Sectorisation Praha FIR Implementation: State(s) and Org: A decision for Lower airspace re- Proposed CZE organisation is pending due to coordination Description: To introduce a new sectorisation within Prague FIR providing winter 2023/24 Originator(s): of MIL requirements and the new Warsaw airport project. additional sectors, changing sector shapes and possibly add CZE 332. a 4th geographical split/ layer. Project Category: Related proposals:

Objective: ATC Sectors  89.063 To further improve the airspace organisation, adjust sectors to new traffic flows after FRA implementation and increase capacity. Proposal ID : 66.053e Status: Contributor: Comments: Project Name: LUMAS, Phase 2b Marseille FIR - Implementation: State(s) and Org:  Linked to re-orginasation of Palma Barcelona FIR Proposed ESP TMA.

winter 2023/24 FRA  Introduction of the new structure shall Description: Originator(s): be without impact of the LF-D54 South 333. To re-organise the ATS route network at the interface between Spain and France, around LF-D54 military zone ESP that remains AMC non-manageable. and to reconsider the traffic distribution of overflying FRA  Proposal is under study following the LECB-LFMM Interface Meeting No.2 currently points DIBER or LUMAS. Project Group: a) To implement a 3 point interface network structure for held 15-16 OCT 2014. RFG SW flights from Barcelona to Marseille ACC instead of Related proposals:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 117

EUROCONTROL Network Management Directorate

current 2 points interface (DIBER / LUMAS). Project Category: a. 77.029

Objective: Airspace Structure To further improve the ATS route network and airspace ATC Sectors structure and to enhance sector capacity at the interface ATS Routes between Marseille ACC and Barcelona ACC. Proposal ID : 92.002 Status: Contributor: Comments: Project Name: ELIXIR Phase 1 Implementation: State(s) and Org: Subject to TSA10 activity and RFL. Proposed FRA Description: To implement a new route (or DCT) from DVL parallel to winter 2023/24 Originator(s): UN859 between SITET and LMG/BEBIX. FRA 334. Objective: GBR

To improve London ACC / Brest ACC interface, increase the Project Category: capability of Brest Q and X sectors to climb UK departures ATS Routes to their RFL, thus increasing capacity on the UK / Southwest DCTs of France and Spain flows. Proposal ID : 92.003 Status: Contributor: Comments: Project Name: ELIXIR Phase 2 Implementation: State(s) and Org: Subject to TSA10 activity and RFL. Proposed FRA Description: To implement a new route (or DCT) parallel to UN859 winter 2023/24 Originator(s): between SITET and LMG/BEBIX - extension of the new FRA 335. route from SITET. GBR

Objective: Project Category: To improve London ACC / Brest ACC interface, increase the ATS Routes capability of Brest Q and X sectors to climb UK departures DCTs to their RFL, thus increasing capacity on the UK / Southwest of France and Spain flows. Proposal ID : 91.017c Status: Contributor: Comments: Project Name: Free Route Airspace Brest Continental Implementation: State(s) and Org:  ATS Route Network will be removed. East- Step 1.3 Proposed FRA  'Double AIRAC procedure’ for AIRAC

winter 2023/24 FAB EC AIP AMDT publication required for Description: 336. North West FRA Cell Step 3 - To implement H24 Free Originator(s): implementation (ICAO Annex 15 refers). Route Airspace in Brest ACC East Area above FL305. FRA

Objective: Project Group: Related proposals: To implement FRA Concept and further improve flight FAB EC 1. 91.017a

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 118

EUROCONTROL Network Management Directorate

efficiency within Brest ACC. Project Category:  91.017b Free Route Airspace  93.032 High Seas  93.033  93.034  95.010 Proposal ID : 97.014 Status: Contributor: Comments: Project Name: Future Airspace Strategy Implementation Implementation: State(s) and Org:  Large Scale redevelopment to include - South (FASI-S) Proposed GBR various deployments;

Description: winter 2023/24 FRA  More information to be provided as the Large Scale re-design of the airspace structure of the south- BEL Project progresses - phased east of the UK to include new SIDs, new STARs, Transitions, NLD deployment from 2023 to 2025. amended ATS Route structure incorporating RNAV1 and MUAC RNAV5, new COPs, potential sector re-designs and revised FAB EC EUROCONTROL London TMA.

Objective: Originator(s): GBR To increase capacity, reduce delay, more specific information to be provided as the Project progresses. Project Group: FAB EC 337. Project Category: 5LNC AIP Airspace Structure ATC Sectors CDRs DCTs High Seas PBN RAD Route Redesignation TMA Vertical FE Proposal ID : 95.034 Status: Contributor: Comments: Project Name: New common ATM system in Belgian Implementation: State(s) and Org:  2019 Step 1: replacement of Belgian 338. airspace Proposed BEL Defence ATM system spring 2024 MUAC by a Shared Air Traffic Management Description: To implement the new Shared Air Traffic Management Originator(s): System (SAS2);

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 119

EUROCONTROL Network Management Directorate

System/ SAS3 providing Air Navigation Services in Belgian BEL  Step 2: replacement of skeyes Air airspace. MUAC Traffic Management System

Objective: Project Category: by a Shared Air Traffic Management To further improve the current cost-efficiency and capacity ATM System System (SAS3); within Brussels ACC and Maastricht UAC.  2024 Step 3: single ATM system used by all three parties. Proposal ID : 93.031 Status: Contributor: Comments: Project Name: Airspace Structure Improvement Implementation: State(s) and Org: Study already started. Bordeaux ACC Proposed FRA FIrst step is completed. 2 options are now

Description: spring 2024 Originator(s): studied in detail. To re-organise the lower airspace by changing the DFL FRA 339. between upper and lower airspace and delegate ATS to APP Project Category: units at FL145 - FL195 for relevant airspace in Bordeaux Airspace Structure ACC.

Objective: To further improve the airspace structure within France FIR. Proposal ID : 89.060b Status: Contributor: Comments: Project Name: NORWAY FAS (Future ATM System) - Implementation: State(s) and Org: Spring 2023 for South sectors. North Proposed NOR Related proposals: Description: spring 2024 Originator(s):  89.060a To introduce a new operating system iTEC (interoperability NOR 340. Through European Collaboration) for the North sectors Project Category: within Norway FIR. ATM System Objective: The project will introduce a Trajectory Based FDP system and associated Controller Tools to Norway FIR. Proposal ID : 99.015c Status: Contributor: Comments: Project Name: Reorganisation ACC Warszawa sector Implementation: State(s) and Org:  Depending on technical issues configuration – three layer division - Step 4 Proposed POL (frequencies) and increasing the

Description: spring 2024 Originator(s): amount of ATC staff. 341. To implement a new airspace structure and sectorisation POL  New elementary sectors with vertical splits. within Warszawa ACC considering vertical splits (division Project Category: into three layers),  Division into three layers. Airspace Structure Step 2 : EPWWF, EPWWG, EPWWN, EPWWE Related proposals: ATC Sectors

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 120

EUROCONTROL Network Management Directorate

Objective:  62.091e To further improve the airspace structure within Warszawa  99.015a ACC and increase capacity while applying vertical splits. Proposal ID : 93.035 Status: Contributor: Comments: Project Name: Paris ACC re-organisation - Phase 3 Implementation: State(s) and Org: Proposed FRA Description: To re-organise the lower airspace and delegate ATS to APP autumn 2024 Originator(s): 342. units below FL115 for relevant airspace in Paris ACC (North FRA West of FIR). Project Category: Objective: Airspace Structure To further improve the airspace structure within France FIR. Proposal ID : 87.028h Status: Contributor: Comments: Project Name: Borealis FRA - Step 8 Implementation: State(s) and Org:  Transition to Free Route operations.

Proposed GBR  This step represents full Description: NATS Free Route Airspace Deployment 4 - To implement autumn 2024 Originator(s): implementation of FRA in London FIR. H24 Free Route Airspace above FL305 across sectors 1, FAB Denmark/Sweden  Full cross border FRA operations with 2, 12, 13, 15, 17, 19, 20, 22, 24, 27, 32 & 34 of the FAB NEFAB Ireland and NEFRA. Swanwick ACC AoR. FAB UK/Ireland  FRA airspace design dependent on ISL London TMA re-design. Objective: To further improve the airspace structure and flight planning Project Group:  'Double AIRAC procedure’ for AIRAC options within parts of London FIR (as part of Borealis Free FAB Denmark/Sweden AIP AMDT publication required for 343. Route Airspace/ FRA), allowing full free route operations in FAB NEFAB implementation (ICAO Annex 15 refers). London FIR as well as full cross border FRA operations with FAB UK/Ireland Ireland FRA and NEFRA. RFG NW Related proposals:

. Project Category:  81.073a Free Route Airspace  87.028a  87.028b  87.028c  87.028d a. 87.028e 1. 87.028f  87.028g Proposal ID : 97.043 Status: Contributor: Comments: 344. Project Name: Lower airspace re-organisation Implementation: State(s) and Org:

Proposed POL

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 121

EUROCONTROL Network Management Directorate

Description: 2024 Originator(s): To re-organise the lower airspace in Poland, including POL TMAs. Project Category: Objective: Airspace Structure To further improve the airspace structure within Warsaw FIR TMA while optimising the airspace configuration. Proposal ID : 96.022 Status: Contributor: Comments: Project Name: Airspace structure improvement at Reims Implementation: State(s) and Org: ACC Proposed FRA

Description: winter 2024/25 Originator(s): To create 2 new sectors at Reims ACC by vertical split of FRA

the following sectors: Project Category: 345. a. KD into KD / HD; ATC Sectors b. KF into KF / HF.

Objective: To create new airspace configurations possibilities with 3 sectors in order to better adapt to traffic and to further improve capacity of Reims ACC.

Proposal ID : 95.005 Status: Contributor: Comments: Project Name: Reims ACC/ Brest ACC/Paris ACC re- Implementation: State(s) and Org: sectorisation Proposed FRA

Description: winter 2024/25 Originator(s): 346. 1. To optimise Reims ACC North and West sectors. FRA

2. To optimise Brest ACC East sectors. Project Category: Objective: Airspace Structure To further improve the airspace structure at the interface ATC Sectors between Reims ACC and Brest ACC. Proposal ID : 96.006 Status: Contributor: Comments: Project Name: Airspace Structure Improvement Reims Implementation: State(s) and Org: ACC Proposed FRA 347. Description: winter 2024/25 Originator(s): To re-organise the lower airspace by changing the DFL FRA

between upper and lower airspace and delegate ATS to APP Project Category:

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 122

EUROCONTROL Network Management Directorate

units at FL145 - FL195 for relevant airspace in Reims ACC. Airspace Structure

Objective: To further improve the airspace structure within France FIR.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 123

EUROCONTROL Network Management Directorate

General clarifications: 1. Due to the fully automated short-term airspace improvement process in States and Organisations box the following ISO-3 coding of States is used: ALB Albania FRA France MKD North Macedonia ARM Armenia GBR United Kingdom MLT Malta AUT Austria GEO Georgia MNE Montenegro AZE Azerbaijan, Republic of GRC Greece NLD Netherlands BEL Belgium HRV Croatia NOR Norway BGR Bulgaria HUN Hungary POL Poland BIH Bosnia and Herzegovina IRL Ireland PRT Portugal BLR Belarus IRN Iran, Islamic Republic of ROU Romania CHE Switzerland MUAC Maastricht UAC RUS Russian Federation CYP Cyprus IRQ Iraq SRB Serbia CZE Czech Republic ISL Iceland SVK Slovakia DEU Germany ITA Italy SVN Slovenia DNK Denmark LBY Libya SWE Sweden DZA Algeria LTU Lithuania SYR Syrian Arab Republic EGY Egypt LUX Luxembourg TUN Tunisia ESP Spain LVA Latvia TUR Turkey EST Estonia MAR Morocco UKR Ukraine FIN Finland MDA Moldova, Republic of 2. Content of each proposal is an indication of State’s intention to implement the relevant airspace improvement but don't represent a copy of any official publication. For the correctness and verification of the relevant aeronautical information consult official State AIP publication. The data from this document should not be used for operational purposes.

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 124

EUROCONTROL Network Management Directorate

Edition Number: 1.0 Edition Validity Date: 08-07-2020 Classification: White Page: 125

SUPPORTINGSUPPORTING EUROPEAN EUROPEAN AVIATION AVIATION EUROCONTROL

© EUROCONTROL - April 2020 This document is published by EUROCONTROL for information purposes. It may be copied in whole or in part, provided that EUROCONTROL is mentioned as the source and it is not used for commercial purposes (i.e. for financial gain). The information in this document may not be modified without prior written permission from EUROCONTROL. www.eurocontrol.int