European Route Network Improvement Plan doc/ERNIP/ERNIP_Part 2_ARN_V_2016_2020...European Route Network Improvement Plan - Part 2 - ARN Version 2016 - 2019/20 - Catalogue of Projects

EUROCONTROL

Network Managernominated by the European Commission

Edition June 2016European Network Operations Plan 2016-2019/20

European Route Network Improvement Plan

PART 2 European ATS Route Network - Version 2016-2019/20

European Route Network Improvement Plan

- Part 2 -

ATS Route Network

ARN Version 2016 - 2019/20

Catalogue of Airspace Projects

Edition Number : 1.0

Edition Date : 28.06.2016

Status : Released Issue

Intended for : General Public

AARRNN VV--22001166 -- 22001199//2200

European Route Network Improvement Plan - Part 2 - ARN Version 2016 - 2019/20 - Catalogue of Projects

ii 28 June 2016 Edition: 1.0

Left blank intentionally

AARRNN VV--22001166 -- 22001199//2200


iii 28 June 2016 Edition: 1.0

DOCUMENT CHARACTERISTICS

TITLE

European Route Network Improvement Plan ARN Version 2016 - 2019/20

Catalogue of Airspace Projects

Publications Reference:

Document Identifier Edition Number: 1.0

Edition Date: 28.06.2016

Abstract This document contains the ATS Route Network ARN Version 2016 - 2019/20 Catalogue of Airspace Projects as Part 2 of the European Route Network Improvement Plan (ERNIP). It is in response to the COMMISSION REGULATION (EU) No 970/2014 of 12 September 2014 amending Regulation (EU) No 677/2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions. The ERNIP Part 2 - ARN Version 2016 - 2019/20 provides a consolidated picture of the European airspace structure aimed to deliver a safe and operationally efficient operation of air traffic. It responds to the operational performance targets set for the European ATM network for both RP1 and RP2. It 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.

Keywords

Network Manager Route Network Route Network Plan Efficiency Plan

Airspace Design Airspace Utilisation Airspace Functional Blocks

Sectors Traffic flow

Authors

EUROCONTROL NMD/NOM/OPL

Contact Person(s) Tel Division

Razvan Bucuroiu + 32 2 729 36 48 NMD / NOM / OPL

STATUS, AUDIENCE AND ACCESSIBILITY

Status Intended for Accessible via

Working Draft General Public Intranet

Draft Operational Stakeholders Extranet

Proposed Issue Restricted Audience Internet (www.eurocontrol.int)

Released Issue Printed and electronic copies of the document can be obtained from the Publications Infocentre (see page iv)

AARRNN VV--22001166 -- 22001199//2200


iv 28 June 2016 Edition: 1.0

DOCUMENT CHANGE RECORD

The following table records the complete history of the successive editions of the present document.

EDITION

NUMBER EDITION DATE REASON FOR CHANGE PAGES AFFECTED

0.1 13.05.2016 Proposed Issue

RNDSG/88 for agreement All

0.2 30.05.2016 Proposed Issue

NETOPS/15 and NDOP/14 for approval

All

1.0 28.06.2016 Released issue - NMB/16

Approved All

Publications

EUROCONTROL Headquarters

96 Rue de la Fusée

B-1130 BRUSSELS

Tel: +32 (0)2 729 1152

Fax: +32 (0)2 729 5149

E-mail: [email protected]

mailto:[email protected]

AARRNN VV--22001166 -- 22001199//2200


v 28 June 2016 Edition: 1.0

TABLE OF CONTENT DOCUMENT CHARACTERISTICS ............................................................................................... iii

DOCUMENT CHANGE RECORD ................................................................................................. iv

TABLE OF CONTENT .................................................................................................................... v

EXECUTIVE SUMMARY .............................................................................................................. vii

ORGANISATION AND CONTENTS .............................................................................................. ix

1. A CONSOLIDATED EUROPEAN AIRSPACE DEVELOPMENT ...................................... 1

1.1. OBJECTIVE, SCOPE AND TIMEFRAME...................................................................... 1

1.2. DEMANDING PERFORMANCE TARGETS .................................................................. 2

1.2.1. PERFORMANCE SCHEME - SECOND REFERENCE PERIOD (RP2) - 2015 - 2019 . 2

There are no performance indicators/targets set yet for 2020. ................................................. 4

1.3. EUROPEAN ROUTE NETWORK IMPROVEMENT PLAN - PRINCIPLES .................... 4

1.4. THE AIRSPACE ACTION PLAN ................................................................................... 5

1.5. THE FLIGHT EFFICIENCY PLAN ................................................................................. 5

1.6. PREPARATION OF THE ERNIP Part 2 - ARN VERSION 2016 - 2019/20 .................... 6

1.7. FUNCTIONAL AIRSPACE BLOCKS INTEGRATION INTO THE ERNIP Part 2 - ARN VERSION 2016 - 2019/20 ............................................................................................. 7

1.7.1. FAB Performance Plans and their Relation to the European Route Network Improvement Plan .................................................................................................................... 7

1.7.2. Functional Airspace Blocks/ FABs Main Projects and Performance Evaluations.......... 9

2. ARN VERSION 2016 - 2019/20 BENEFITS .................................................................... 18

2.1. TOTAL EXPECTED BENEFITS - ERNIP Part 2 - ARN VERSION 2016 - 2019/20 ...... 18

2.2. CAPACITY ENHANCEMENT BENEFITS OF ERNIP Part 2 - ARN VERSION 2016 - 2019/20 ....................................................................................................................... 19

3. EUROPEAN ROUTE NETWORK DESIGN FUNCTION AND FLIGHT EFFICIENCY ACTION PLANS ........................................................................................................................... 21

3.1. EUROPEAN ROUTE NETWORK DESIGN FUNCTION .............................................. 21

3.2. FREE ROUTE AIRSPACE .......................................................................................... 21

3.3. ASM Solutions ............................................................................................................ 22

3.4. SIMPLIFYING THE RAD ............................................................................................. 23

3.5. IMPROVING TMA STRUCTURES .............................................................................. 23

3.6. THE FLIGHT EFFICIENCY PLAN ............................................................................... 24

3.7. THE NETWORK MANAGER FLIGHT EFFICIENCY INITIATIVE ................................ 24

4. CONCEPT OF OPERATIONS FOR EUROPEAN AIRSPACE DESIGN ......................... 27

4.1. MAIN PRINCIPLES ..................................................................................................... 27

4.2. ERNIP Part 2 - ARN VERSION 2016 - 2019/20 IMPROVEMENTS HIGHLIGHTS ...... 28

4.2.1. Introduction ................................................................................................................ 28

4.2.2. Basic Concept ........................................................................................................... 28

4.2.3. European Network Consistency ................................................................................. 28

4.2.4. Airspace Continuum .................................................................................................. 29

4.2.5. ARN Version 2016 - 2019/20 Components ................................................................ 29

4.2.6. Airspace Classification ............................................................................................... 29

4.2.7. Airspace Organisation ............................................................................................... 30

4.2.8. Airspace Development Approach .............................................................................. 30

4.2.9. Operating the ERNIP Part 2 - ARN Version 2016 - 2019/20 ...................................... 32

4.2.10. Military Operations ..................................................................................................... 33

AARRNN VV--22001166 -- 22001199//2200


vi 28 June 2016 Edition: 1.0

4.2.11. Airspace Management (ASM) Solutions .................................................................... 33

4.2.12. Network Enablers ...................................................................................................... 35

4.2.13. Impact on Adjacent Areas .......................................................................................... 35

5. A NETWORK COOPERATIVE DECISION MAKING PROCESS .................................... 37

5.1. A NETWORK ORIENTATED APPROACH .................................................................. 39

5.2. AIRSPACE UTILISATION AND MANAGEMENT ........................................................ 40

5.3. MILITARY REQUIREMENTS ...................................................................................... 40

6. TRAFFIC DEMAND EVOLUTION AND ASSESSMENT ................................................. 41

6.1. GENERAL ................................................................................................................... 41

6.2. TRAFFIC DEMAND VARIATION - COMPARISON 2008/2015 .................................... 41

6.3. WEEK AND WEEK-END DISTRIBUTION ................................................................... 42

6.4. DISTRIBUTION AND EVOLUTION - SHORT HAUL AND MEDIUM/LONG HAUL ...... 44

6.5. VERTICAL DISTRIBUTION (EVOLVING AND CRUISING TRAFFIC) ......................... 45

6.6. FLIGHT LEVEL DISTRIBUTION ................................................................................. 46

6.7. AIRPORT TRAFFIC INCREASE ................................................................................. 46

6.8. TOP 50 AIRPORTS ..................................................................................................... 47

6.9. BUSIEST CITY PAIRS ................................................................................................ 48

6.10. AIRSPACE USERS ..................................................................................................... 50

6.11. AIRCRAFT TYPES ...................................................................................................... 51

7. MAIN PROJECTS INCLUDED IN ERNIP PART 2 - ARN VERSION 2016 - 2019/20 ..... 53

7.1. FREE ROUTE AIRSPACE .......................................................................................... 53

ANNEXES .................................................................................................................................... 57

Annex A. Reference Documents ............................................................................................. 59

Annex B. Acronyms and Abbreviations ................................................................................. 61

Annex C. Summary of ERNIP PART 2 - ARN VERSION 2016 - 2019/20 Proposals .............. 63

Annex D. List of ERNIP PART 2 - ARN VERSION 2016 - 2019/20 Proposals ........................ 70

AARRNN VV--22001166 -- 22001199//2200


vii 28 June 2016 Edition: 1.0

EXECUTIVE SUMMARY

In accordance with the COMMISSION REGULATION (EU) No 970/2014 of 12th September 2014 amending Regulation (EU) No 677/2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions 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.

In response to the same COMMISSION REGULATION (EU) and the EUROCONTROL Provisional Council Airspace Action Plan, the objective of the ERNIP Part 2 - ARN Version 2016 - 2019/20 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 2016 - 2019/20 also responds to the COMMISSION REGULATION (EU) No 390/2013 of 3rd May 2013 (laying down a performance scheme for air navigation services and network functions). It 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 2nd Reference Period of the Single European Sky Performance Scheme (RP2) will not be met unless the proposed NM measures will be implemented.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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 FL310 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 2016 - 2019/20:

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.

As from the full implementation of ERNIP Part 2 - ARN Version 2016 - 2019/20 in 2019/2020, flying distances would be reduced year to year by approximately 4 million NMs. When compared to the start of RP2, the total benefits that ENRIP Part 2 - ARN Version 2016 - 2019/20 would bring represent 84 million NMs, i.e. the equivalent of 500 000 tons of fuel saved, or reduced emissions of 1 680 000 tons, or 420 million Euros.

AARRNN VV--22001166 -- 22001199//2200


viii 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


ix 28 June 2016 Edition: 1.0

ORGANISATION AND CONTENTS

This document is identified as European Route Network Improvement Plan - ARN Version 2016 - 2019/20 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 2016 - 2019/20 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 2013/2015.

Chapter 7 Provides a description of the ARN Version 2016 - 2019/20 layers.

Annexes

Annex A Reference Documents

Annex B Acronyms and Abbreviations

Annex C Summary of ARN Version 2016 - 2019/20 Proposals

Annex D List of ARN Version 2016 - 2019/20 Proposals

AARRNN VV--22001166 -- 22001199//2200


x 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


1 28 June 2016 Edition: 1.0

1. A CONSOLIDATED EUROPEAN AIRSPACE DEVELOPMENT

1.1. OBJECTIVE, SCOPE AND TIMEFRAME

In response to the COMMISSION REGULATION (EU) No 970/2014 of 12th September 2014 amending Regulation (EU) No 677/2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions and the EUROCONTROL Provisional Council Airspace Action Plan, the objective of the ERNIP Part 2 - ARN Version 2016 - 2019/20 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 of both in the European airspace. In response to the COMMISSION REGULATION (EU) No 390/2013 of 3rd May 2013 (laying down a performance scheme for air navigation services and network functions) the Network Manager shall support 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. This regulation requires that, the Network Manager

shall support functional airspace blocks and their air navigation service providers in reaching their performance targets during reference periods by ensuring consistency between performance plans, the Network Strategy Plan and the Network Operations Plan. In that respect, a close cooperation and synchronisation was ensured between the Network Manager and all the FABs in the preparation of their Performance Plans, of the Network Strategy Plan, of the Network Operations Plan and the ERNIP - Part 2 - ARN Version 2016 - 2019/20.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 will contribute to the achievement of the performance targets of the 2nd Reference Period of the Single European Sky Performance Scheme (RP2).

The ERNIP Part 2 - ARN Version 2016 - 2019/20 will ensure the implementation, in cooperation with the ANSPs and the FABs, of the Airspace Vision agreed by the Network Management Board that includes:

a comprehensive cross-border implementation of Free Route Airspace, at least at and above FL310, in the European airspace;

an optimised route structure below FL310 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 2016 - 2019/20:

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;

AARRNN VV--22001166 -- 22001199//2200



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 (EU) 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 (set target dates for the implementation of DCT and FRA in the ICAO EUR region).

The ERNIP Part 2 - ARN Version 2016 - 2019/20 combines airspace design projects developed in a cooperative manner between the Network Manager and its operational stakeholders aimed for implementation over the period Autumn 2015 - end of 2020. The full development phase including the validation covers the period from Summer 2015 until Summer 2016. The implementation started in Autumn 2015 and continues in stages until the end of 2020. Further updates will be brought through subsequent versions of the ERNIP Part 2. The ERNIP Part 2 - ARN Version 2016 - 2019/20 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. The ERNIP Part 2 - ARN Version 2016 - 2019/20 is derived from the following sources:

Proposals covering a cohesive development of the European Airspace Structure;

Solutions developed inside various FAB initiatives;

Proposals originating at national or sub-regional level;

Aircraft operators proposals.

The European Route Network Improvement Plan - Part 2 - ARN Version 2016 - 2019/20 covers a similar geographical area like the Network Operations Plan:

EU member States (Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, United Kingdom).

EUROCONTROL member States that are not EU members (Albania, Armenia, Bosnia and Herzegovina, Georgia, Moldova, Montenegro, Norway, Serbia, Switzerland, The Former Yugoslav Republic of Macedonia, Turkey, Ukraine).

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, Egypt, Iceland, Israel, Jordan, Kazakhstan, Lebanon, Libya, Morocco, Russian Federation and Tunisia.

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: http://www.eurocontrol.int/articles/eurocontrol-regional-charts

1.2. DEMANDING PERFORMANCE TARGETS

1.2.1. PERFORMANCE SCHEME - SECOND REFERENCE PERIOD (RP2) - 2015 - 2019

In response to the COMMISSION REGULATION (EU) No 390/2013 of 3rd May 2013 (laying down a performance scheme for air navigation services and network functions), a new set of Key Performance Indicators and associated targets have been set for the 2nd Reference Period (RP2).

http://www.eurocontrol.int/articles/eurocontrol-regional-charts

AARRNN VV--22001166 -- 22001199//2200



It includes two important key performance areas and associated indicators, related to the operational performance of the European ATM network for the period 2015 - 2019.

Environment o average horizontal en-route flight efficiency of the actual trajectory, defined as

follows: - the indicator is the comparison between the length of the en-route part of

the actual trajectory derived from surveillance data and the corresponding portion of the great circle distance, summed over all IFR flights within or traversing the European airspace;

- “en-route” refers to the distance flown outside a circle of 40 NM around the airports;

- where a flight departs from or arrives at a place outside the European airspace, only the part inside the European airspace is considered;

This KPI is applicable at both network and Functional Airspace Block level.

o average horizontal en-route flight efficiency of the last filed flight plan trajectory, defined as follows:

- the difference between the length of the en-route part of the last filed flight plan trajectory and the corresponding portion of the great circle distance, summed over all IFR flights within or traversing the European airspace;

- “en-route” refers to the distance flown outside a circle of 40 NM around the airports;

- where a flight departs from or arrives at a place outside the European airspace, only the part inside the European airspace is considered;

This KPI is only applicable at network level.

Capacity o minutes of en-route ATFM delay per flight, calculated for the full year and

including all IFR flights within European airspace and all ATFM delay causes, excluding exceptional events.

For the second performance Reference Period starting on 1st January 2015 and ending on 31st December 2019, the European Union-wide performance targets will be as follows:

Environment target:

Actual trajectory (KEA) - an average of 2.6% route extension by 2019, decreasing from 3.17% in 2012 (based on PRB measurements)

Last filed flight plan trajectory (KEP) - an average of 4.1% route extension by 2019, decreasing from 5.15% in 2012 (based on PRB measurements)

Capacity target: average en route Air Traffic Flow Management (ATFM) delay of 0.5 minutes per flight for each year of the second Reference Period.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 also responds to the targets included in the Network Performance Plan (NPP) 2015 - 2019 as described below:

o Route extension - airspace design

Targets:

o achieve an improvement of the DES indicator by 0.57 percentage points between the baseline year of 2012 and 2019.

AARRNN VV--22001166 -- 22001199//2200



o Route extension - last filed flight plan

Targets:

o This is a European-wide indicator in RP2 and the NM target for RP2 is to achieve 4.1% value for KEP indicator by 2019 for the entire SES area and 3.82% for the NM area, fully consistent with the EU-wide target, i.e. a reduction by 1.05 pp (percentage points) between the baseline year of 2012 and 2019

o Route extension - actual trajectory

Targets:

o The NM target for RP2 is to achieve 2.6% value for KEA indicator by 2019 for both the SES and NM areas, fully consistent with the EU-wide target

o NM direct contributions to flight efficiency savings

o The NM objectives is that these FE direct savings will amount to 10% (2015 - 2016) and 5% (2017 - 2019) of the savings required to achieve the annual 0.15 pp reduction (or alternatively 5% of the actual KEP reduction) each year

o Increase the CDR1/2 usage

o NM objective is to increase the CDR availability (CD-RAI) and CDR usage (CDR-RAU) by 5% between 2015 and 2019

There are no performance indicators/targets set yet for 2020.

1.3. EUROPEAN ROUTE NETWORK IMPROVEMENT PLAN - PRINCIPLES

With the development of the ERNIP Part 2 - ARN Version 2016 - 2019/20 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 2016 - 2019/20 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, received from stakeholders having an operational requirement in the European airspace;

AARRNN VV--22001166 -- 22001199//2200



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.

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).

All principles above were fully considered in the development of the ERNIP Part 2 - ARN Version 2016 - 2019/20 of the European Route Network Improvement Plan.

1.4. THE AIRSPACE ACTION PLAN

The Airspace Action Plan was adopted by the EUROCONTROL PC at its 28th Session, in November 2007. The Airspace Action Plan covers the need for a continued pan-European approach and concrete actions to improve network efficiency and capacity through airspace planning, design and management at network level. This Airspace Action Plan helps in eliminating fragmentation and identifying best options that respond to the recommendations and strategic objectives agreed by the EUROCONTROL Provisional Council (PC) and the high level objectives of the Single European Sky.

The development of ERNIP Part 2 - ARN Version 2016 - 2019/20 fully responds to the actions set by the EUROCONTROL Provisional Council in the context of the Airspace Action Plan.

1.5. 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 Flight Efficiency Plan builds on the accelerated implementation of the measures already approved by the EUROCONTROL Provisional Council, currently put in place by all ATM actors, and included in the Airspace Action Plan, the Airspace Management Improvement Initiative, the Terminal Airspace Improvement Initiative and the Airport Programme.

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.45% in December 2015.

These achievements came as a result of the implementation of ARN Version-6, ARN Version-7 and ARN Version-8, ERNIP Part 2 - ARN Version 2013 - 2015 as well as from the initial steps of ERNIP Part 2 - ARN Version 2014 - 2018/19 and ERNIP Part 2 - ARN Version 2015 - 2019.

AARRNN VV--22001166 -- 22001199//2200



1.6. PREPARATION OF THE ERNIP PART 2 - ARN VERSION 2016 - 2019/20

The following steps were followed for the preparation of the ERNIP Part 2 - ARN Version 2016 -2019/20:

The development of the next European Route Network Improvement Plan - Part 2 edition will cover, as per the requirements of the NMF IR, a 5-years period (2016 - 2019/20).

All ANSPs and FABs will be required to provide their airspace plans until 2020.

The Network Manager will provide the list of all known plans until 2019/20 to all ANSPs and FABs.

The Network Manager will provide the environment/flight efficiency reference values per FAB for the period 2016 - 2019/20, as per the requirement of the Performance Scheme IR.

The following preparation calendar was followed:

Action Date Who

Distribution of all known airspace design plans until 2019/20 to all ANSPs and FABs

October 2015 NM

Comments and updates received from all ANSPs/FABs on the initial list of airspace projects

December 2015 NM/ANSPs/FABs

Preparation of the first version of the European Route Network Improvement Plan - Part 2 - ARN

Version 2016 - 2019/20 January 2016

NM/Ops Stakeholders

Initial performance indications per FAB based on the first version of the European Route Network Improvement Plan - Part 2 - ARN Version 2016 -

2019/20

February - March 2016

NM to all ANSPs

Further updates and synchronisation actions between NM, ANSPs and FABs to ensure the

achievement of RP2 targets

March - April 2016

NM/ANSPs/FABs

European Route Network Improvement Plan - Part 2 - ARN Version 2016 - 2019/20 consolidation and

approval through the CDM process May - June 2016

NM/Ops Stakeholders

Publication of European Route Network Improvement Plan - Part 2 - ARN Version 2016 -

2019/20 June 2016 NM

AARRNN VV--22001166 -- 22001199//2200



1.7. FUNCTIONAL AIRSPACE BLOCKS INTEGRATION INTO THE ERNIP PART 2 - ARN VERSION 2016 - 2019/20

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.

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 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.

Throughout 2012, and before 04/12/2012, nine FABs have submitted the documentation required for their establishment.

The Regulation (EC) No 677/2011, in particular Articles 6, 8 and 10, 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.

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.

The NM has included FAB perspective in the operational improvements planning processes even before the due date set for the Member States to implement FABs (December 2012).

The 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.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

1.7.1. FAB Performance Plans and their Relation to the European Route Network Improvement Plan

It is important to note that the COMMISSION REGULATION (EU) No 390/2013 of 3rd May 2013 (laying down a performance scheme for air navigation services and network functions) defines also the principles for assessing the FAB Performance Plans and targets. In this new framework, FABs will be asked to provide the evidence that they will meet the performance targets. In that respect, the following assessment criteria have been defined in the IR:

AARRNN VV--22001166 -- 22001199//2200



ENVIRONMENT

Average horizontal en route flight efficiency of the actual trajectory:

(a) comparison with historical performance achieved in previous years;

(b) comparison with a reference value based on information provided by the Network Manager;

(c) consistency with the European Route Network Improvement Plan developed by the Network Manager.

CAPACITY

En route delay level. Comparison of the expected level of en route ATFM delay used in the performance plans with:

(a) a reference value based on information from the Network Operations Plan of the Network Manager;

(b) the capacity plan established by the en route air navigation service provider(s) as reflected in the Network Operations Plan of the Network Manager.

The KEA reference values based on the European-wide target, for each of the Functional Airspace Blocks, are as follows:

2012 Achievement Improvement 2012-2019 2015 2016 2017 2018 2019

SW FAB 4.27% 0.99% 3.85% 3.71% 3.57% 3.43% 3.28%

UK-Ireland FAB 3.64% 0.65% 3.36% 3.27% 3.18% 3.09% 2.99%

FABEC 3.56% 0.60% 3.30% 3.22% 3.14% 3.05% 2.96%

BLUE MED FAB 3.02% 0.57% 2.78% 2.70% 2.62% 2.54% 2.45%

FAB CE 2.13% 0.32% 1.99% 1.94% 1.90% 1.85% 1.81%

DANUBE FAB 1.69% 0.32% 1.55% 1.50% 1.46% 1.41% 1.37%

Baltic FAB 1.61% 0.25% 1.50% 1.47% 1.44% 1.40% 1.36%

NEFAB 1.44% 0.22% 1.35% 1.32% 1.29% 1.26% 1.22%

DK-SE FAB 1.20% 0.01% 1.20% 1.20% 1.20% 1.20% 1.19%

The evaluations of the expected performance improvements in this document have used the year 2014 as the baseline year. They are based on assigned flight plan situation. By considering 2014 as a baseline year and a macroscopic evaluation not including all flights, they are considered to be conservative. They provide a good estimation of the potential of a FAB to deliver the expected performance to meet European targets. It also shows that the interfaces between FABs will require a very particular attention.

AARRNN VV--22001166 -- 22001199//2200



1.7.2. Functional Airspace Blocks/ FABs Main Projects and Performance Evaluations

Note: The evaluations below do not take into consideration the changes to the CPR transmission frequency. They are intended to evaluate the outlook of the KEA indicator and the additional measures necessary to achieve the Environment RP2 target.

FAB Europe Central (FAB EC) The main projects taken into consideration in the context of the FABEC are:

FABEC FRA Project with local implementation: o FRA DFS - Germany: o FRA Maastricht FL245+.

Additional more detailed projects are also in course of deployment and they are included in the ERNIP Part 2 - ARN Version 2016 - 2019/20. The Scenarios are considered in the chronological order of their implementation. The impacts are calculated to the baseline end 2015 scenario. The evaluation made for the scenarios above shows the following achievements:

Route Length Extension Analysis (V2.1) SAAM/NEST Airport-circle radix

(NM): 40.00 Filter used : Europe plus mediterranean

countries and part of the Russian Federation

REF Reduction of route

extension percentage points to reference

All network projects including FABEC FRA

Local Implementations FRA - DFS and MUAC

-0.19 pp

pp = percentage point

FABEC

2015

Reference Value

2015

Actual

3.30% 3.37%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.60 pp 0.19 pp

NM evaluation The 2015 reference value was not achieved and the reduction by 0.19 pp is not sufficient to achieve the network RP2 target.

NM proposed measures

To implement FRA Project at DSNA - France and skyguide - Switzerland. To expand x-border FRA operations with adjacent FABs - ACCs (e.g. Denmark / Sweden FAB, UK Ireland FAB). To further Improve interfaces with SW FAB, UK Ireland FAB and Blue Med FAB.

AARRNN VV--22001166 -- 22001199//2200


10 28 June 2016 Edition: 1.0

Blue Med FAB

The main projects taken into consideration in the context of the Blue Med FAB are:

FRAIT - IT Phase 3 (FRA FL335+).

Malta FRA FL335+.

Additional more detailed projects are also in course of deployment and they are included in the ERNIP Part 2 - ARN Version 2016 - 2019/20.

The Scenarios are considered in the chronological order of their implementation. The impacts are calculated to the baseline end 2015 scenario. The evaluation made for the scenarios above shows the following achievements:






All network projects including Malta FRA FL335+

FRA IT - Phase 3 - FL335+ -0.45 pp


Blue Med FAB

2015

Reference Value

2015

Actual

2.78% 2.84%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.57 pp 0.45 pp

NM evaluation The 2015 reference value was not achieved. Reference values might be met with deployment of FRA in Italy initially FL335+, Malta FL335+


Cross-border FRA projects implementation must be considered for the entire Blue Med FAB starting with FRA project for Greece together with lowering down of the FL to FL305 by the end of 2021. The interface between Blue Med FAB and FABEC needs to be addressed with priority. Timely implementation of projects in line with the ERNIP Part 2.

AARRNN VV--22001166 -- 22001199//2200


11 28 June 2016 Edition: 1.0

FAB Central Europe (FAB CE)

The main project taken into consideration in the context of the FABCE is the implementation of the FABCE Concept of Seamless operations. This includes the following projects:

Implementation of Free Route Airspace in gradual steps between 2016 and 2020;

Implementation of seamless operations by ensuring: o horizontal connectivity with adjacent FABs; o vertical connectivity through enhanced route network, CDO and CCDs with

lower airspace and TMAs.

Appropriate interoperability through gradual ATM systems evolutions to respond to the operational requirements resulting from the implementation of the Concept of Seamless Operations.

FABCE ASM/ATFCM project.


The FRA Implementation steps are described in the detailed projects included in the ERNIP Part 2 - ARN Version 2016 - 2019/20.






All network projects including FABCE FRA Projects

-0.36pp


FABCE

2015

Reference Value

2015

Actual

1.99% 1.90%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.32 pp 0.36 pp

NM evaluation Plans in line with the expected European targets


Maintain current implementation plans in FABCE, including cross-border FABCE implementation of FRA with adjacent FABs.

AARRNN VV--22001166 -- 22001199//2200


12 28 June 2016 Edition: 1.0

UK-Ireland FAB

The projects taken into consideration in the context of the UK/IE FAB are the ones included in the ERNIP Part 2 - ARN Version 2016 - 2019/20, including:

Phase 3 FRA Prestwick ACC FL255+







ERNIP Part 2 - ARN Version 2016 - 2019/20 Projects

Phase 3 - FRA Prestwick ACC FL255+

-0.08 pp


UK/IE FAB

2015

Reference Value

2015

Actual

3.36% 3.51%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.65 pp 0.08 pp

NM evaluation

The 2015 reference value was not achieved and the reduction by 0.08 pp is not sufficient to achieve the network RP2 target. Full FRA already implemented in Ireland FRA in Scottish UIR FL255+ has been included in the evaluation.


In order to meet the European target, cross-border FRA projects implementation must be considered for the entire UK/IE FAB. In addition to consider cross-border operations with neighbouring FABs (FABEC, DK/SWE FAB and NEFAB). The BOREALIS project is included in the NM work programme and will be included in future editions of the ERNIP Part 2. BOREALIS is expected to deliver the fully required performance after the end RP2.

AARRNN VV--22001166 -- 22001199//2200


13 28 June 2016 Edition: 1.0

Danube FAB

The main projects taken into consideration in the context of the Danube FAB are:

All proposals included in the ERNIP Part 2 - ARN Version 2016 - 2019/20, including cross border night FRA with Hungary;

Danube FAB cross-border FRA FL105+.







Proposals included in the ERNIP Part 2 - ARN Version

2016 - 2019/20, including cross border night FRA with Hungary and DANUBE FAB

cross-border FRA FL105 H24

-1.02 pp


Danube FAB

2015

Reference Value

2015

Actual

1.55% 1.31%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.32 pp 1.02 pp

NM evaluation

A significant proportion of the reduction is based on impacts from other changes in the network. It is essential that DANUBE FAB ensures implementation above FL105 to ensure the contribution to the achievement of the overall European target.


Implementation of cross-border FRA H24, with possibility to expand with adjacent FABs/ACCs is recommended. Cross-border FRA projects needs to be included in the ERNIP Part 2.

AARRNN VV--22001166 -- 22001199//2200


14 28 June 2016 Edition: 1.0

North European (NE) FAB

The main projects taken into consideration in the context of the NE FAB are:

NEFRA Project.








Finish airspace re-organisation

NEFRA -0.42 pp


NE FAB

2015

Reference Value

2015

Actual

1.35% 1.46%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.22 pp 0.35 pp

NM evaluation 2019 European target will be achieved


To implement all projects as planned including Borealis Project with Denmark Sweden FAB and UK Ireland FAB.

AARRNN VV--22001166 -- 22001199//2200


15 28 June 2016 Edition: 1.0

Denmark/Sweden FAB

The main projects taken into consideration in the context of the DK/SE FAB are:

The cross border FRA implementation in the DK/SE FAB that was already achieved;

The cross-border between DK/SE FAB, NEFAB and NEFRA Project.

NM considers that the further adaptations planned by DK/SE FAB will fully respond to the European targets.

DK/SE FAB

2015

Reference Value

2015

Actual

1.20% 1.23% (due to flow

changes)

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.01 pp 0.25 pp

NM evaluation 2019 European target will be achieved


Ensure cross-border FRA implementation with NEFAB and with other neighbouring FABs - Expand cross-border operations within Borealis project and in the future with FABEC.

AARRNN VV--22001166 -- 22001199//2200


16 28 June 2016 Edition: 1.0

Baltic FAB

The main projects taken into consideration in the context of the Baltic FAB are:

Poland and Lithuanian FRA projects








Poland and Lithuanian FRA projects

-0.19 pp


Baltic FAB

2015

Reference Value

2015

Actual

1.50% 1.64%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.25 pp 0.19 pp

NM evaluation

Target might be achieved with implementation of FRA FL245+ in Baltic FAB. Cross border FRA with neighbouring FABs will be required for full achievement of the target.


Initiate cross-border projects with neighbouring FABs.

AARRNN VV--22001166 -- 22001199//2200


17 28 June 2016 Edition: 1.0

South West Portugal Spain FAB

The main projects taken into consideration in the context of the SW FAB are:

Partial implementation of DCTs.








All network projects including Partial implementation of

DCTs -0.13 pp


SW FAB

2015

Reference Value

2015

Actual

3.85% 3.42%

2019

Reference Value

(pp reduction

vs 2012)

2019

NM evaluation

(pp reduction

vs 2015)

0.99 pp 0.13 pp

NM evaluation Full FRA already implemented in Portugal. Additional FRA projects definition required in Spain.


In order to meet the European target, cross-border FRA projects implementation must be considered for the entire SW FAB, in line with the NSP and the PCP.

The interface between SW FAB, FABEC needs to be addressed with priority.

AARRNN VV--22001166 -- 22001199//2200


18 28 June 2016 Edition: 1.0

2. ARN VERSION 2016 - 2019/20 BENEFITS

2.1. TOTAL EXPECTED BENEFITS - ERNIP PART 2 - ARN VERSION 2016 - 2019/20

The ERNIP Part 2 - ARN Version 2016 - 2019/20 contains, at this stage, more than 480 (four hundred eighty) packages of airspace proposals scheduled for implementation for the Summer seasons 2016 - 2019/20, out of which 147 are implemented by 28th April 2016.

These proposals include more than 300 route changes, around 20 re-sectorisation plans, more than 30 TMA projects, more than 60 Free Route Airspace projects, 5 civil/military airspace developments as well as more than 70 improvement measures eliminating unnecessary RAD restrictions or improving flight efficiency. They were or will be implemented as follows:

approximately 210 proposals for the Summer season 2016;



approximately 10 proposals for the Summer season 2019

approximately 20 proposals from autumn 2019 until the end of 2020.

As from the full implementation of ERNIP Part 2 - ARN Version 2016 - 2019/20 in 2019/2020, flying distances would be reduced year to year by approximately 4 million NMs. When compared to the start of RP2, the total benefits that ENRIP Part 2 - ARN Version 2016 - 2019/20 would bring represent 84 million NMs, i.e. the equivalent of 500 000 tons of fuel saved, or reduced emissions of 1 680 000 tons, or 420 million Euros.

The implementation of ERNIP Part 2 - ARN Version 2016 - 2019/20 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.45% in December 2015 to approximately 2.13% by 2020. The graph below shows the expected evolution of flight efficiency between 2008 and 2020 in terms of extension compared to the great circle.

2008

2010

20

12

20

14

2009

20

11

20

13

20

15

0

0,1

0,2

0,3

0,4

0,5

0,6

0,7

0,8

0,9

1

2,0%

2,5%

3,0%

3,5%

4,0%

4,5%

5,0%

5,5%

Ro

ute

Ex

ten

sio

n

AIRAC

Route Efficiency KPI per AIRAC cycle RTE-DES

RTE-FPL

3.65% Jan 2008

3.40% Sept 2009

2.45% End 2015

between 2.10-2.15% end 2020

3.13% Sept 2010

3.05% Sept 2011 2.95%

Sept 2012 2.69% Nov 2013

2.54% End 2014

AARRNN VV--22001166 -- 22001199//2200


19 28 June 2016 Edition: 1.0

2.2. CAPACITY ENHANCEMENT BENEFITS OF ERNIP PART 2 - ARN VERSION 2016 - 2019/20

The ERNIP Part 2 - ARN Version 2016 - 2019/20 Catalogue contains around 25 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 2016 - 2019/20 would bring an additional 5 - 7% capacity to the European ATM network when fully implemented.

AARRNN VV--22001166 -- 22001199//2200


20 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


21 28 June 2016 Edition: 1.0

3. EUROPEAN ROUTE NETWORK DESIGN FUNCTION AND FLIGHT EFFICIENCY ACTION PLANS

3.1. EUROPEAN ROUTE NETWORK DESIGN FUNCTION

The ERNIP Part 2 - ARN Version 2016 - 2019/20 responds to the obligations put in accordance with the COMMISSION REGULATION (EU) No 970/2014 of 12 September 2014 amending Regulation (EU) No 677/2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions and amending Regulation (EU) No 691/2010) on the European Route Network Design Function:

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

Until 3 March 2016 Free Route Airspace has been fully implemented in the following ACCs: Beograd ACC, Bucuresti ACC, Budapest ACC, Chisinau ACC, Kobenhavn ACC, Lisbon ACC, Malmo ACC, Shannon ACC, Sofia ACC, Stockholm ACC, Tampere ACC, Ukraine (individual UACs) and Zagreb ACC.

Free Route Airspace has been partially initiated but level restricted, on seasonal basis or through DCTs in the following ACCs: Brest ACC, Brindisi ACC, Bordeaux ACC, Karlsruhe UAC, London ACC, Ljubljana ACC, Maastricht UAC, Madrid ACC (SAN and ASI sectors), Malta ACC, Marseille ACC, Milano ACC, Padova ACC, Praha ACC, Prestwick ACC, Reims ACC, Roma ACC, Skopje ACC, Warszawa ACC, Wien ACC (see map below).

AARRNN VV--22001166 -- 22001199//2200


22 28 June 2016 Edition: 1.0

The following map shows the Free Route Airspace implementation plans proposed until end of RP2 in 2020.

The Free Route Airspace development year by year is presented in chapter 7.1 of this document.

3.3. ASM SOLUTIONS

The implementation of ASM solutions are particularly important in the context of the ERNIP Part 2 - ARN Version 2016 - 2019/20 that will include further solutions to improve network performance for the most penalised city pairs, through further deployment of the European night direct route network, solutions offering to the airspace users several and/or shorter routing options, etc.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 will require also to accommodate both civil and military requirements, the ASM solutions will need therefore to be fully exploited.

In this context a number of ASM solutions have been tested in 2014. Additional activities have been executed in 2015 in the frame of FREE Solutions Large Scale Demonstration Project to evaluate the application of ASM solutions in a FRA environment. A number of DCTs have been identified in order to promote a better utilisation of airspace based on co-ordination among civil and military.

FREES DCTs FIR/UIR

GTQ - BEGAR LFFF

BEGAR - ODINA LSAS

VANAS - GODRA LFFF, LSAS

GODRA - DITON LSAS

ARKIP - LMG LFFF

ERIXU - VALKU LFFF

RESIA - BABAG LIMM

BZO - ETPUB - TALEP LIMM

AARRNN VV--22001166 -- 22001199//2200


23 28 June 2016 Edition: 1.0

Based also on the outcome of the FREE Solutions Project, a revision of the ASM handbook has been initiated with the purpose to define a process to be applied in future for similar scenarios. In this respect NETOPS/14 agreed the proposed amendment on ASM solutions for ERNIP Part 3 ASM Handbook.

3.4. SIMPLIFYING THE RAD

A number of RAD restrictions have successfully been tackled and clear flight efficiency improvements achieved with no impact on safety or on capacity. An elimination of further restrictions impacting Croatia, Czech Republic, France, Germany, Italy, Poland, Spain, Turkey and UK is planned until end 2020.

There is a clear need to further review the RAD restrictions with the participation of all the interested parties. It is expected the Network Manager to run a Network impact assessment of the RAD restrictions implemented in the States. States will be requested to study if some of the RAD restrictions where put in place to balance capacity during a specific period of the year and therefore can be deactivated during the rest.

Furthermore the Network Manager provided input to the States/ANSPs/FABs on the inconsistencies identified in regard to the current allowed DCTs in RAD Appendix 4 and 5.

All the required improvements for many areas will be implemented within the context of ERNIP Part 2 - ARN Version 2016 - 2019/20.

3.5. IMPROVING TMA STRUCTURES

Improved Terminal Airspace design projects are or will be implemented in the context of the ARN Version 2016 - 2019/20 at:

- Al Hoceima TMA;

- Ankara TMA;

- Barcelona TMA;

- Batumi TMA;

- Beograd TMA;

- Canarias TMA;

- Istanbul TMA;

- Izmir TMA;

- Ljubljana TMA;

- London TMA;

- Milano TMA;

- Nador El Atoui TMA;

- NAPOC TMA;

- Oslo TMA (HOPE - Harmonisation of Oslo Procedures and Environment);

- Paris TMA (Point Merge TE);

- Poznan TMA;

- Santorini TMA;

- Tbilisi TMA;

- Tetouan TMA,

- Tivat TMA;

- Wien TMA.

In the time frame of ERNIP Part 2 - ARN Version 2016 - 2019/20 a third runway at Munich airport is considered, a new runway at Dublin airport and a new International airport planned for Istanbul.

AARRNN VV--22001166 -- 22001199//2200


24 28 June 2016 Edition: 1.0

3.6. 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 will lead to fuel and emissions savings in the short term to develop a Flight Efficiency Plan that was commonly agreed in September 2008.

The Flight Efficiency Plan builds on the accelerated implementation of the measures already approved by the EUROCONTROL Provisional Council, currently put in place by all ATM actors, and included in DMEAN, the Airspace Action Plan, the Airspace Management Improvement Initiative, the Terminal Airspace Improvement Initiative and the Airport Programme.

The action points of the Flight Efficiency Plan, relevant for the ERNIP Part 2 - ARN Version 2016 - 2019/20, are:

1. Enhancing European en-route airspace design through annual improvements of European ATS route network, high priority being given to:

o Implementation of a coherent package of annual improvements and of shorter routes;

o Improving efficiency for the most penalised city pairs;

o Implementation of additional Conditional Routes for main traffic flows;

o Supporting initial implementation of free route airspace.

2. Improving airspace utilisation and route network availability through:

o Actively support and involve aircraft operators and the computer flight plan service providers in flight plan quality improvements;

o Gradually applying route availability restrictions only where and when required;

o Improving the utilisation of civil/military airspace structures.

3. Efficient TMA design and utilisation, through:

o Implementing advanced navigation capabilities

o Implementing Continuous Descent Approaches (CDAs), improved arrival/departure routes, optimised departure profiles, etc.

The vast majority of the improvements considered in the context of the ERNIP Part 2 - ARN Version 2016 - 2019/20 contribute to the deployment of the Flight Efficiency Plan.

3.7. THE NETWORK MANAGER FLIGHT EFFICIENCY INITIATIVE

A closer cooperation with the airspace users to ensure a better flight planning is essential to ensure the achievement of the RP2 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

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 during the last AIRAC cycle;

The airspace users and the CFSPs will have the possibility to detect new implemented routes, CDRs available during similar periods of time, etc.;

It is expected that the airspace users and the CFSPs will use this interface to improve their flight planning for the “next” AIRAC cycle;

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

AARRNN VV--22001166 -- 22001199//2200


25 28 June 2016 Edition: 1.0

Enhanced utilisation of CDRs through the deployment of ASM solutions

Assessment of traffic demand, ATFM measures, sector configurations and CDRs availability;

Existence of CDRs segments in the FPL; Route extension compared with the “best option”; flight extension mostly for en-

route section (avoid extensive arrival/departure situations); Search for the flights with the shortest planned route for each city pair having at

least one CDR in their planned route; For each city pair assess the CDR availability requirements if all the flights on that

city pair would plan the shortest route; Proposals to AOs for better routes including CDRs; Possible coordination with military partners, when required, for coordinated

availability of CDRs.

Flight Planning improvements in the Pre-Tactical/Tactical Phases

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

recomputation 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;

Repetitive Flight Plans (RPLs) Proposals for RPL changes that need to be maintained by the airlines for each

AIRAC cycle. 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. 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.

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.

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 RP2 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, ANSPs and FABs will not provide their full potential.

AARRNN VV--22001166 -- 22001199//2200


26 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


27 28 June 2016 Edition: 1.0

4. CONCEPT OF OPERATIONS FOR EUROPEAN AIRSPACE DESIGN

4.1. MAIN PRINCIPLES

Successful European airspace design is achieved through:

o The implementation of an advanced and consolidated concept of operations;

o 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;

o Gradual elimination of bottlenecks and reasons for flight inefficiency;

o Optimised procedures for an enhanced use of airspace;

o A balanced approach between European network, regional and local requirements;

o 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.

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

AARRNN VV--22001166 -- 22001199//2200


28 28 June 2016 Edition: 1.0

4.2. ERNIP PART 2 - ARN VERSION 2016 - 2019/20 IMPROVEMENTS HIGHLIGHTS

4.2.1. Introduction

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. 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

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.

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.

4.2.2. Basic Concept

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.

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.

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.

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

The ARN Version 2016 - 2019/20 is built on a close co-operation between airspace design, ATFCM and ASM. It supports a close link between airspace design and airspace utilisation.

4.2.3. European Network Consistency

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

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

AARRNN VV--22001166 -- 22001199//2200


29 28 June 2016 Edition: 1.0

4.2.4. Airspace Continuum

An airspace continuum was envisaged in the development of the ERNIP Part 2 - ARN Version 2016 - 2019/20. 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.

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.

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

4.2.5. ARN Version 2016 - 2019/20 Components

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

The main characteristic of the ATS routes of the ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

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 2016 - 2019/20.

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.

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

ATC sectors of ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

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 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.

4.2.6. Airspace Classification

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 7 ICAO airspace classes.

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

AARRNN VV--22001166 -- 22001199//2200


30 28 June 2016 Edition: 1.0

4.2.7. Airspace Organisation

The practical airspace organisation features of ERNIP Part 2 - ARN Version 2016 - 2019/20 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. the European Night Direct Route Network or 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 2016 - 2019/20. Where incompatibilities arise, priorities were discussed and given depending on operational requirements to the en-route part or to the terminal structure.

4.2.8. Airspace Development Approach

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;

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

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

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

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 2016 - 2019/20 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.

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

AARRNN VV--22001166 -- 22001199//2200


31 28 June 2016 Edition: 1.0

available with no capacity constraints, but involving ASM solutions, or a longer route available with no airspace constraint.

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.

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 or 2.

4.2.8.2. Free Route Airspace

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

4.2.8.3. Sectorisation

The development of ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

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

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.

AARRNN VV--22001166 -- 22001199//2200


32 28 June 2016 Edition: 1.0

4.2.8.4. Modus Operandi

The Modus Operandi of the ERNIP Part 2 - ARN Version 2016 - 2019/20 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 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.

4.2.9. Operating the ERNIP Part 2 - ARN Version 2016 - 2019/20

The rationale for the ERNIP Part 2 - ARN Version 2016 - 2019/20 was to ensure that the ATS route network, the Free Route Airspace and the ATC sector planning allow for an improved balance between:

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.

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.

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.

Flight planning procedures were further improved to take into account the flexibility of route selection offered by the ERNIP Part 2 - ARN Version 2016 - 2019/20. Further initiatives are under way to facilitate improved flight planning and route selection. 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 2016 - 2019/20 supports the usage of DCT in the FPL within a consolidated concept and approach.

It is expected that operations within the ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

AARRNN VV--22001166 -- 22001199//2200


33 28 June 2016 Edition: 1.0

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

4.2.10. Military Operations

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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 2016 - 2019/20, 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 2016 - 2019/20 took into consideration.

Through the solutions proposed in ERNIP Part 2 - ARN Version 2016 - 2019/20, the military should be able to have:

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.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

4.2.11. Airspace Management (ASM) Solutions

General Principles

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 2016 - 2019/20. They include:

Reviewing the different application of CDR categories at the different stages;

Addressing the potential incompatibility of different CDR categories 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.

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.

AARRNN VV--22001166 -- 22001199//2200


34 28 June 2016 Edition: 1.0

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.

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.

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 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.

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.

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. 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.

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.

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

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 subregional (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 2016 - 2019/20.

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.

AARRNN VV--22001166 -- 22001199//2200


35 28 June 2016 Edition: 1.0

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.12. Network Enablers

The main enablers for the efficient implementation of the ERNIP Part 2 - ARN Version 2016 - 2019/20 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;

Adaptations to airspace management procedures.

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

4.2.13. Impact on Adjacent Areas

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

AARRNN VV--22001166 -- 22001199//2200


36 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


37 28 June 2016 Edition: 1.0

5. A NETWORK COOPERATIVE DECISION MAKING PROCESS

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

1. Preparation

Input from NSP, previous NOP, NM Annual Report;

Input from all operational stakeholders and ICAO;

NM(D) to prepare ERNIP proposals;

All operational stakeholders to agree on ERNIP proposals;

NETOPS substructure to review proposals;

NM(D) to prepare draft ERNIP. 2. Consultation

Network DOP, for any unresolved issues (if required);

NETOPS to agree on draft ERNIP. 3. 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 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. The Part 2 of the ERNIP is updated on an annual basis. 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.

AARRNN VV--22001166 -- 22001199//2200


38 28 June 2016 Edition: 1.0

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 either under the auspices of the RNDSG or independent, but bringing their results into the overall network picture through RNDSG processes. Examples are:

o Sub-Regional RNDSG Meetings;

o Regional co-ordination meetings between States;

o Working groups proposing various solutions for specific problem areas;

o Special projects (FABs, national re-organisation projects, sub-regional agreements, etc.).

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

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

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.

AARRNN VV--22001166 -- 22001199//2200


39 28 June 2016 Edition: 1.0

5.1. A NETWORK ORIENTATED APPROACH

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.

NETWORK ORIENTED

APPROACH

TRAFFIC FLOW

DEFINITION

MILITARY

REQUIREMENTS

CONNECTIVITY

TO TMA

ATS ROUTE

NETWORK

DESIGN

ATC SECTOR DESIGN

ATC SECTOR

CONFIGURATION

ROUTE NETWORK

AVAILABILITY

AIRSPACE

RESERVATION

REQUIREMENTS

DESIGN

MANAGEMENT

Adaptations of the route

network

‘MODUS OPERANDI’

(Airspace Structure Utilisation)

OPTIMAL USE OF

ROUTES AND

SECTORS

AARRNN VV--22001166 -- 22001199//2200


40 28 June 2016 Edition: 1.0

5.2. AIRSPACE UTILISATION AND MANAGEMENT

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.

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

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.

5.3. MILITARY REQUIREMENTS

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.

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.

AARRNN VV--22001166 -- 22001199//2200


41 28 June 2016 Edition: 1.0

6. TRAFFIC DEMAND EVOLUTION AND ASSESSMENT

6.1. GENERAL

This section will assess the traffic demand changes between the start of implementation of ARN Version-6 and the start of implementation of ERNIP Part 2 - ARN Version 2016 - 2019/20. Significant changes of the traffic patterns could be noted between 2008 and 2014 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/2015

The assessment was made for a busy week 25 in 2015 (15 - 21 June 2015) during which lower level of delays were recorded. Comparing the variation in traffic demand between 2008 and 2015 (see Figure 1 below), it can be seen that the Central and Western part of Europe recorded a significant traffic decrease, predominantly in Germany, UK and Spain. A continued traffic growth is recorded in the Southern and South Eastern part of Europe, predominantly on the South-West Axis, South-East Axis, North-South Axis, East-West Axis and in Turkey.

Figure 1: Traffic demand variation 2015 vs 2008

Traffic Demand Variation 2015 vs 2008 4 Weekdays of Traffic

> 80 Ac/day

60 to 80 Ac/day

40 to 60 Ac/day

20 to 40 Ac/day

10 to 20 Ac/day

Incr

De

cr

20 to 40 Ac/day

40 to 60 Ac/day

> 60 Ac/day

10 to 20 Ac/day

Cell size is 20NM x 20NM

Week 25 2015<>2008

AARRNN VV--22001166 -- 22001199//2200


42 28 June 2016 Edition: 1.0

6.3. WEEK AND WEEK-END DISTRIBUTION

The assessment was made for a busy week in 2015 (15 - 21 June 2015). 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 2 below) and gradually expanding to most of the European airspace and Turkey during weekend traffic (see Figure 3 below).

Figure 2: Week-days traffic density (4 days in June 2015)

Traffic Density for all Flights


One Week of Traffic

15-21/06/2015

> 400 Ac/day

300 to 400 Ac/day

200 to 300 Ac/day

100 to 200 Ac/day

50 to 100 Ac/day

25 to 50 Ac/day

Figure 3: Week-end traffic density (4 week-end days in June 2015)

Traffic Density for all Flights


WeekEnd traffic (Sat-Sun)

4 days in June 2015

> 400 Ac/day

300 to 400 Ac/day

200 to 300 Ac/day

100 to 200 Ac/day

50 to 100 Ac/day

25 to 50 Ac/day

AARRNN VV--22001166 -- 22001199//2200


43 28 June 2016 Edition: 1.0

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

Figure 4: Comparison Week/Week-end traffic Density in June 2015

Traffic Density Comparison Week <> Weekend


8 Days of Traffic

WE Week

WE <> Week in June 2015

The map above indicates the following:

o 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 - Milan axis;

- Europe - Africa axis via Algeria.

o 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”;

- Mediterranean area.

AARRNN VV--22001166 -- 22001199//2200


44 28 June 2016 Edition: 1.0

6.4. DISTRIBUTION AND EVOLUTION - SHORT HAUL AND MEDIUM/LONG HAUL

The assessment was made for the period 1st July 2007 - 30th June 2008 and 1st July 2014 - 30th June 2015. The short-haul traffic pattern (distances up to 400 NM - see Figure 5 below) shows a decrease of domestic and business traffic for short-haul flights in most of the European airspace, in UK, in Spain - especially for the city pair Barcelona-Madrid and in Northern Italy - especially the city pair Milano-Rome. Compared to 2007/08, a higher density of traffic is noted predominantly in Turkey.

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

Traffic Density Comparison for Short-Haul Flights


365 Days of Traffic

Jul to Jun 14/15 <> 07/08

> 50 Ac/day

25 to 50 Ac/day

10 to 25 Ac/day

5 to 10 Ac/day

0 to 5 Ac/day

Incr

De

cr

0 to 5 Ac/day

5 to 10 Ac/day

> 10 Ac/day

The medium to long-haul traffic pattern (flight distances over 400 NM - see Figure 6 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, Turkey and parts of the Mediterranean area.

Figure 6: Medium-Haul Flights (>400 NM)

Traffic Density Comparison for Other Flights (> 400NM)


365 Days of Traffic

Jul to Jun 14/15 <> 07/08

> 50 Ac/day

25 to 50 Ac/day

10 to 25 Ac/day

5 to 10 Ac/day

0 to 5 Ac/day

Incr

De

cr

0 to 5 Ac/day

5 to 10 Ac/day

> 10 Ac/day

AARRNN VV--22001166 -- 22001199//2200


45 28 June 2016 Edition: 1.0

6.5. VERTICAL DISTRIBUTION (EVOLVING AND CRUISING TRAFFIC)

The assessment of the traffic was made for a busy Friday (19th June 2015). The concentration of climbing/descending traffic (see Figure 7 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.

Figure 7: Areas of High Density Evolving Traffic


Number of Evolving

Flights

Traffic of 19 June 2015

> 300 Ac/day

200 to 300 Ac/day

100 to 200 Ac/day

50 to 100 Ac/day

25 to 50 Ac/day

10 to 25 Ac/day

The distribution of Cruising Traffic (see Figure 8 below) is more evenly distributed and increases are noted on the South East - North West axis.

Figure 8: Areas of High Density Cruising Traffic


Number of Cruising

Flights

Traffic of 19 June 2015

> 300 Ac/day

200 to 300 Ac/day

100 to 200 Ac/day

50 to 100 Ac/day

25 to 50 Ac/day

10 to 25 Ac/day

AARRNN VV--22001166 -- 22001199//2200


46 28 June 2016 Edition: 1.0

6.6. FLIGHT LEVEL DISTRIBUTION

With the implementation of RVSM combined with the performance of new generation aircraft, the vertical distribution of traffic has moved up significantly (FL360/FL420 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 9: Flight Level Distribution in EUROPE 2008 / 2015

6.7. AIRPORT TRAFFIC INCREASE

The assessment was made for the period 1st July 2007 - 30th June 2008 and 1st July 2014 - 30th June 2015. Figure 10 below indicates that with the exception of airports in Belgium, Latvia, the Mediterranean area, Middle East, Moldova, North Africa, Norway, Portugal, Romania, Russian Federation, Turkey, Ukraine and some low cost operators airports, all the other airports in Europe and the Canaries recorded a significant traffic decrease, the largest was accounted to the UK.

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

200 Busiest Airports – Change in Number of Movements from 2015 to 2008

Increase

Decrease

AARRNN VV--22001166 -- 22001199//2200


47 28 June 2016 Edition: 1.0

6.8. TOP 50 AIRPORTS

The table below indicates the Top 50 European airports in terms of movements for the period 1st July 2014 - 30th June 2015.

AARRNN VV--22001166 -- 22001199//2200


48 28 June 2016 Edition: 1.0

6.9. BUSIEST CITY PAIRS

The following two tables show the Top 50 busiest city pairs/ CPs flown in Europe for the periods July 2007 - June 2008 and July 2014 - June 2015.

The table below shows the Top 50 busiest city pairs/CPs in Europe for the period July 2007 - June 2008.

AP1 AP2 AD 07-08 % Tot

MADRID BARAJAS BARCELONA 44,913 0.4%

ROME FIUMICINO MILANO LINATE 27,542 0.3%

IZMIR-ADNAN-MENDERES ISTANBUL-ATATURK 19,723 0.2%

PALMA DE MALLORCA BARCELONA 19,105 0.2%

TOULOUSE BLAGNAC PARIS ORLY 18,905 0.2%

OSLO/GARDERMOEN BERGEN/FLESLAND 18,754 0.2%

JERSEY GUERNSEY 18,606 0.2%

TRONDHEIM/VAERNES OSLO/GARDERMOEN 17,705 0.2%

SCHIPHOL AMSTERDAM LONDON/HEATHROW 17,199 0.2%

PARIS ORLY NICE 17,123 0.2%

MUENCHEN 2 HAMBURG 16,805 0.2%

PALMA DE MALLORCA MADRID BARAJAS 16,248 0.2%

MAKEDONIA ATHINAI E. VENIZELOS 15,752 0.2%

MUENCHEN 2 DUESSELDORF 15,716 0.2%

STAVANGER/SOLA OSLO/GARDERMOEN 15,548 0.2%

MUENCHEN 2 KOELN-BONN 15,226 0.1%

ROME FIUMICINO CATANIA FONTANAROSSA 15,188 0.1%

VALENCIA MADRID BARAJAS 15,008 0.1%

TEGEL-BERLIN MUENCHEN 2 14,780 0.1%

PARIS CH DE GAULLE LONDON/HEATHROW 14,649 0.1%

ISTANBUL-ATATURK ANTALYA 14,628 0.1%

ISTANBUL-ATATURK ANKARA-ESENBOGA 14,515 0.1%

PARIS CH DE GAULLE FRANKFURT MAIN 14,438 0.1%

LONDON/HEATHROW DUBLIN 14,395 0.1%

LAS PALMAS FUERTEVENTURA 14,124 0.1%

OSLO/GARDERMOEN COPENHAGEN KASTRUP 14,033 0.1%

TENERIFE NORTE LAS PALMAS 14,011 0.1%

NEW YORK LONDON/HEATHROW 13,705 0.1%

LAS PALMAS ARRECIFE LANZAROTE 13,591 0.1%

TENERIFE NORTE LA PALMA 13,496 0.1%

ROME FIUMICINO PALERMO PUNTA RAISI 13,138 0.1%

MADRID BARAJAS LAS PALMAS 13,080 0.1%

ROME FIUMICINO PARIS CH DE GAULLE 12,663 0.1%

LONDON/HEATHROW EDINBURGH 12,656 0.1%

PARIS CH DE GAULLE MADRID BARAJAS 12,562 0.1%

TEGEL-BERLIN KOELN-BONN 12,542 0.1%

STOCKHOLM-ARLANDA COPENHAGEN KASTRUP 12,492 0.1%

TEGEL-BERLIN FRANKFURT MAIN 12,482 0.1%

MALAGA MADRID BARAJAS 12,373 0.1%

LONDON/HEATHROW FRANKFURT MAIN 12,341 0.1%

STOCKHOLM-ARLANDA HELSINKI-VANTAA 11,879 0.1%

MADRID BARAJAS LISBOA 11,831 0.1%

COPENHAGEN KASTRUP AALBORG 11,690 0.1%

LONDON/HEATHROW GLASGOW 11,592 0.1%

TEGEL-BERLIN STUTTGART 11,401 0.1%

PARIS ORLY MARSEILLE PROVENCE 11,392 0.1%

NIKOS/KAZANTZAKIS ATHINAI E. VENIZELOS 11,272 0.1%

SCHIPHOL AMSTERDAM PARIS CH DE GAULLE 11,101 0.1%

PARIS CH DE GAULLE MUENCHEN 2 10,941 0.1%

OSLO/GARDERMOEN STOCKHOLM-ARLANDA 10,887 0.1%

AARRNN VV--22001166 -- 22001199//2200


49 28 June 2016 Edition: 1.0

The table below shows the Top 50 busiest city pairs/CPs flown in Europe for the period July 2014 - June 2015.

AARRNN VV--22001166 -- 22001199//2200


50 28 June 2016 Edition: 1.0

6.10. AIRSPACE USERS

The table below indicates the Top 50 aircraft operators (AO) using the European airspace between July 2014 - June 2015.

AARRNN VV--22001166 -- 22001199//2200


51 28 June 2016 Edition: 1.0

6.11. AIRCRAFT TYPES

The table below indicates the Top 50 aircraft types using the European airspace between July 2014 - June 2015.

AARRNN VV--22001166 -- 22001199//2200


52 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


53 28 June 2016 Edition: 1.0

7. MAIN PROJECTS INCLUDED IN ERNIP PART 2 - ARN VERSION 2016 - 2019/20

The ERNIP Part 2 - ARN Version 2016 - 2019/20 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.

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.

The main direction taken by the ERNIP Part 2 - ARN Version 2016 - 2019/20 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: http://www.eurocontrol.int/articles/eurocontrol-regional-charts

7.1. FREE ROUTE AIRSPACE

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 2016 - 2019/20. This layer is supported by a network operational concept for Free Route Airspace Operations.

The map below shows the Free Route Airspace implementation plans for summer 2016.


AARRNN VV--22001166 -- 22001199//2200


54 28 June 2016 Edition: 1.0

The map below shows the Free Route Airspace implementation plans proposed for Summer 2017.

The map below shows the Free Route Airspace implementation plans proposed for Summer 2018.

AARRNN VV--22001166 -- 22001199//2200


55 28 June 2016 Edition: 1.0

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

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

AARRNN VV--22001166 -- 22001199//2200


56 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


57 28 June 2016 Edition: 1.0

ANNEXES

Annex A Reference Documents

Annex B Acronyms and Abbreviations

Annex C Summary of ERNIP Part 2 - ARN Version 2016 - 2019/20 Proposals

Annex D List of ERNIP Part 2 - ARN Version 2016 - 2019/20 Proposals

AARRNN VV--22001166 -- 22001199//2200


58 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200


59 28 June 2016 Edition: 1.0

ANNEX A. REFERENCE DOCUMENTS

In the Development and Implementation of ARN Version 2016 - 2019/20 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

ICAO Standards, Recommended Practices and Procedures

AARRNN VV--22001166 -- 22001199//2200


60 28 June 2016 Edition: 1.0


AARRNN VV--22001166 -- 22001199//2200

European Route Network Improvement Plan - Part 2 - ARN Version 2015 - 2019 - Catalogue of Projects

61 28 June 2016 Edition: 1.0

ANNEX 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, 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 CRAM Conditional Route Availability Message D Danger Area DCT Direct DEP Departure DMEAN Dynamic Management of European Airspace Network e-AMI Electronic ASM Information EANP European Air Navigation Plan ECAC European Civil Aviation Conference ERNIP European Route Network Improvement Plan ERND European Route Network Design 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 Filled 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 ICAO International Civil Aviation Organisation IFPS Initial Flight planning Processing System IFR Instrument Flight Rules

AARRNN VV--22001166 -- 22001199//2200


62 28 June 2016 Edition: 1.0

IR Implementing Rule kg kilogram KEA Key Performance Environment Indicator based on actual trajectory KEP Key Performance Environment Indicator based on last filed flight plan KPI Key Performance Indicators LoA Letter of Agreement min Minute/s NETOPS Network Operations Team NM Network Manager / Nautical Mile NMD Network Manager Directorate NOP Network Operations Plan NSP Network Strategy Plan OAT Operational Air Traffic P Prohibited Area PC Provisional Council P-RNAV Precision Area Navigation

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 Area TRA Temporary Reserved Area TSA Temporary Segregated Area VFR Visual Flight Rules WE Weekend UAC Upper Area Control Centre UIR Upper Flight Information region

AARRNN VV--22001166 -- 22001199//2200


63 28 June 2016 Edition: 1.0

ANNEX C. SUMMARY OF ERNIP PART 2 - ARN VERSION 2016 - 2019/20 PROPOSALS

This Annex provides an overview of the major improvement projects implemented or planned for implementation Autumn 2015 until 2020:

Autumn 2015 - Winter 2015 / 2016: Projects implemented (until 28 APR 2016)

Albania / Serbia / Montenegro

- New ARR/DEP LATI Phase 4. Austria

- Free Route Airspace Wien, FRAW, Stage 4b; - Vienna TMA improvements.

Bulgaria / Turkey / Romania

- UDROS / ODERO area re-organization. Cyprus

- Nicosia Direct Route Airspace - Phase 1A. Czech Republic

- Optimization of Praha FIR lower airspace structure; - Improved flight planning options between Adriatic coast and Scandinavia.

FABEC

- FABEC FRA Step 1. France

- Marseille ACC re-organisation, Phase 2. Germany:

- FRA Germany, Phase 1. Germany / Austria

- Long Range Direct Routing SE Axis. Germany / Switzerland

- DFS Karlsruhe - Skyguide Night DCT Package. Greece

- Night DCTs in Hellas UIR above FL355.

Italy - Milano TMA, Phase 2.

Lithuania

- Free Route Airspace H24, FL245+. Maastricht UAC

- Change of DFL in the West sectors of the Brussels Sector Group; - Straighten the boundary between the DECO and the Brussels Sector Group.

Poland

- Polish Airspace Project 2010+, Phase 3a; - FRA Like (DCT) - Phase 2.

AARRNN VV--22001166 -- 22001199//2200


64 28 June 2016 Edition: 1.0

Serbia/Montenegro - Reshape the geographical boundary between Beograd ACC West and North sectors.

Slovakia

- Free Route Airspace Bratislava - FRABRA Phase 1. Spain

- Vertically split existing SAN Sector into Lower (SAL) and Upper (SAU) Sectors Turkey

- SMART Project Phases 2 / 3. United Kingdom

- Airspace Efficiency improvements towards Paris TMA during the winter months. - LAMP Phase 1a.

AARRNN VV--22001166 -- 22001199//2200


65 28 June 2016 Edition: 1.0

Summer 2016: Projects planned or proposed for implementation

Albania

- Improved ATS route network within Tirana FIR. Bulgaria/ Bosnia and Herzegovina / Croatia / Serbia / Slovenia

- Long Range Direct Routing SE Axis. Cyprus

- Nicosia Direct Route Airspace - Phase 1B. DK/SE FAB - NEFAB

- NEFAB and DK/SE FAB Free Route Airspace - NEFRA. FAB NEFAB

- NEFAB Free Route Airspace H24. The Former Yugoslav Republic of Macedonia

- Free Route Airspace Skopje.

AARRNN VV--22001166 -- 22001199//2200


66 28 June 2016 Edition: 1.0


Albania

- FRALB - Free Route Airspace Albania - Phase 1. Armenia

- Night Free Route Airspace in Yerevan ACC. Austria / Slovenia

- SAXFRA - Slovenian Austrian X-border Free Route Airspace. Bulgaria

- Night Free Route Sofia FIR - FRAS, Phase 2. Bulgaria / Greece

- EVIVI dualisation. Bulgaria / Romania

- DANUBE FAB FRA - Phase 2. Bulgaria / Hungary / Romania

- Cross-border Night Free Route operations/ SEEN FRA. Croatia

- Central sector Zagreb Phase 2b. Croatia / Bosnia and Herzegovina / Serbia

- Free Route Airspace, Phase 5b - SEAFRA. Czech Republic

- Free Route Airspace Praha/ FRAPRA, Step 3. France

- Paris ACC re-organisation - Phase 2. - Marseille ACC re-organisation Phase 3.

France

- New TSA 6. Germany

- CDO approaches (STARs) at Munich/ EDDM airport; - FRA Germany - Phases 2 / 3.

Hungary / Bulgaria / Romania

- Cross-border Night Free Route operations/ SEEN FRA. Italy / Malta

- FAIR-IT Free Route Airspace Italy, Phase 3.

Irland / Island / Norway / UK - Borealis Free Route Airspace, Step 1 - Step 5.

Norway - HOPE - Harmonisation of Oslo Procedures and Environment - Phase 2.

Poland

AARRNN VV--22001166 -- 22001199//2200


67 28 June 2016 Edition: 1.0

- FRA Like (DCT) Warsaw FIR, Phase 3. Portugal

- Free Route Airspace Santa Maria FIR. Serbia / Montenegro

- Lower airspace re-organisation Beograd FIR - Step 2/3. Serbia / the Former Yugoslavi Republic of Macedonia

- RAXAD and MAKED dualisation. Spain / France

- LUMAS, Phase 2 and 2b. Spain / Portugal / Morocco

- Lisbon / Casablanca / Canarias Axis. Turkey

- SMART, Phases 4; Ukraine

- Free Route Airspace Ukraine, Step 1 (Sc 1b).

AARRNN VV--22001166 -- 22001199//2200


68 28 June 2016 Edition: 1.0


Albania

- FRALB - Free Route Airspace Albania - Phase 2. Armenia

- H24 Free Route Airspace in Yerevan ACC. Bulgaria

- Common Terminal Airspace System. Bulgaria / Romania

- DANUBE FAB FRA - Phases 3. Cyprus

- Free Route Airspace Cyprus – FRANIC, Phase 1. France

- Brest ACC re-organisation; - S-WAFLE - South West Adaptation Flight Level Evolution Phase 2.

France / Spain

- ESSO - Espace Superieur du Sud Ouest; - Barcelona, Madrid, Bordeaux Interface, BAMBI.

France / Belgium / Maastricht UAC

- Paris Point Merge TE. Germany

- FRA Germany - Phase 4. Maastricht UAC

- FRAM2 - Free Route Airspace Maastricht UAC, Phase 1. Morocco

- Free Route Airspace Casablanca, Phase 1, Phase 2 and Phase 3. Poland

- Free Route Airspace Warsaw FIR, Phase 4. Portugal / Spain / France

- Free Route Airspace Madrid / Brest. Spain

- Barcelona TMA, Phase 1 and Phase 2. Turkey

- FRA Like (DCT) SMART, Phase 5; - Free Route Airspace Turkey - Phase 1; - Istanbul International Airport - Phase 1.

United Kingdom

- Prestwick Lower Airspace – PLAS.

AARRNN VV--22001166 -- 22001199//2200


69 28 June 2016 Edition: 1.0


Bosnia and Herzegovina / Croatia / Montenegro /Serbia

- BH ATM, Phase 2. Bulgaria / Romania

- DANUBE FAB FRA – Phase 4 and Phase 5. Germany

- FRA Germany - Phase 5. Maastricht UAC

- FRAM2 - Free Route Airspace Maastricht UAC, Phase 2. Moldova

- Free Route Airspace Moldova - Phase 3; Poland

- Polish Airspace Project 2010+, Phase 3b; Ukraine

- Free Route Airspace Ukraine, Step 2 (Sc 2a).

Turkey

- Free Route Airspace Turkey, Phase 2.

End of 2020: Projects planned or proposed for implementation

Germany

- 3rd runway Munich airport; - Berlin Brandenburg International (BER) airport; - Sachsen / SAS Upper sector.

Italy - Free Route Airspace Italy, Phase 4.

Maastricht UAC

- Free Route Airspace Maastricht UAC, Phase 3.

Switzerland / Germany / France / Italy - New Cross-Border Coordination Concept; - FRA Switzerland Night, Phase 1.

UK

- Borealis Free Route Airspace, Step 6.

Ukraine - Free Route Airspace Ukraine, Step 2 (Sc 2b).

AARRNN VV--22001166 -- 22001199//2200


70 28 June 2016 Edition: 1.0

ANNEX D. LIST OF ERNIP PART 2 - ARN VERSION 2016 - 2019/20 PROPOSALS

The following pages present detailed information about each of the more than 480 improvement proposals developed within the RNDSG which are or will be implemented as part of ERNIP Part 2 - ARN Version 2016 - 2019/20. The description of the proposals is based on the information available from different sources (e.g. AOs, ANSPs and EUROCONTROL).

The table includes:

Proposal number:

A reference number to identify each proposal allowing to trace 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 2016 - 2019/20 proposals as they stood after RNDSG/88

(13th May 2016).

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: http://www.eurocontrol.int/articles/eurocontrol-regional-charts


AARRNN VV--22001166 -- 22001199//2200


71 28 June 2016 Edition: 1.0

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 IRQ Iraq

ARM Armenia ISL Iceland

AUT Austria ITA Italy

AZE Azerbaijan, Republic of LBY Libya

BEL Belgium LTU Lithuania

BGR Bulgaria LUX Luxembourg

BIH Bosnia and Herzegovina LVA Latvia

BLR Belarus MAR Morocco

CHE Switzerland MDA Moldova, Republic of

CYP Cyprus MKD The former Yugoslav Republic of Macedonia

CZE Czech Republic MLT Malta

DEU Germany MNE Montenegro

DNK Denmark NLD Netherlands

DZA Algeria NOR Norway

EGY Egypt POL Poland

ESP Spain PRT Portugal

EST Estonia ROU Romania

FIN Finland RUS Russian Federation

FRA France SRB Serbia

GBR United Kingdom SVK Slovakia

GEO Georgia SVN Slovenia

GRC Greece SWE Sweden

HRV Croatia SYR Syrian Arab Republic

HUN Hungary TUN Tunisia

IRL Ireland TUR Turkey

IRN Iran, Islamic Republic of UKR Ukraine

MUAC Maastricht UAC

2. BLUMED FAB, DANUBE FAB and FAB CE proposals referenced in proposal number box are coded with a unique identification number abbreviated as

BM or DN or CE, respectively, following by four digits (XXXX) (example BM0001 or DN0001 or CE0001). 3. 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.

AARRNN VV--22001166 -- 22001199//2200


72 28 June 2016 Edition: 1.0

Proposal ID : 85.037 Impl. Status: State(s) & Org. Comments:

1.

Project Name: Transfer of Night ATS CDR routes into Night DCT system.

Description: To withdraw the existing Night CDR routes UQ119, UQ224, UQ227, UQ233, UQ250, UQ374, UQ375 and replace them by Night DCTs in

RAD Appendix 4 with same trajectory and availability.

Objective:

To simplify AIP publication.

Implemented 15 OCT 2015

Project Category:

AIP ATS Routes CDRs DCTs Night Routes

AUT CZE DEU POL SVK

Originator(s):

CZE

Relevant RDs to be considered for release in ICARD.


2.

Project Name: Optimization of LKAA lower airspace structure

Description:

1. To optimize the Praha FIR lower airspace structure by changing division flight level between low sector and APP Brno, Karlovy Vary, Ostrava.

2. To re-design TMAs Brno, Karlovy Vary, Ostrava and Praha.

Objective:

To improve lower airspace structure and to distribute traffic load.


Project Category:

Airspace Structure ATC Sectors TMA

CZE DEU AUT POL SVK

Originator(s):

CZE


3.

Description: To allow DCT option between REGLI - VALPI.

Objective:

To further improve ATS route options within Praha FIR.


Project Category:

ATS Routes RAD

CZE

Originator(s):

IATA

Related proposals:

81.064a

81.064b

81.066

81.068c


4.

Project Name: Removal U prefix Praha FIR

Description: To remove the distinction between Upper and Lower ATS routes - "U"

prefix within Praha FIR.

Objective:

To simplify Air Traffic Management in Praha FIR.


Project Category:

Airspace Structure

CZE

Originator(s):

CZE


5. Description: Implemented CZE

AARRNN VV--22001166 -- 22001199//2200


73 28 June 2016 Edition: 1.0

To re-designate the following ATS routes: a. UT40 DOPOV - DOKEL as T46; b. T/UT47 BNO - HLV as L/UL726.

Objective:

To simplify the existing RDs and avoid unforeseen RD break within ICAO EUR/NAT Region.

15 OCT 2015

Project Category:

Route Redesignation

Originator(s):

EUROCONTROL


6.

Project Name: ECAC States AIP en-route publication issues

Description: To publish in ENR 3.3 CDRs Z30 and Z37 based on ERNIP publication

requirement to cover the whole period of availability.

Objective:

To resolve airspace data publication inconsistencies in State AIP.


Project Category:

AIP CDRs

CZE

Originator(s):

EUROCONTROL

Currently both CDRs are published with only weekend time availability.


7.

Description: To realign existing ATS route UP41 as LEMBI - DOKEL - RODUX.

Objective:

To further improve flight planning options for flights between Adriatic coast and Scandinavia.


Project Category:

ATS Routes

CZE

Originator(s):

IATA

Related proposals:

85.017


8.

Description: To replace existing 5LNC PALME.

Objective:

1. To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT region;

2. To improve the aeronautical information provided; 3. To be compliant with ICAO Annex 11.


Project Category:

5LNC

ESP

Originator(s):

EUROCONTROL ICAO

PALME is with double reservation in ICARD for France and USA. It is not used by USA and ICAO might consider reservation withdrawal from ICARD.

Point is used in Spain for military purpose. Proposal for replacement is based on

“Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Spain.


9.

Description: To replace existing 5LNC PODAS.

Objective:


2. To improve the aeronautical information provided;


Project Category:

5LNC

ESP

Originator(s):

EUROCONTROL ICAO

PODAS is reserved in ICARD for Russian Federation.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Spain.

AARRNN VV--22001166 -- 22001199//2200


74 28 June 2016 Edition: 1.0

3. To be compliant with ICAO Annex 11.


10.

Project Name: Unnamed Significant Points

Description:

1. To remove from ENR 3.1 unnamed significant points from ATS route L602.

2. To add new 5LNC IPSAD to ATS route L602

Objective:

To further improve AIP publication of aeronautical data.


Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


11.


Description: To add ASRUS, UNURO, NOVBA and IBOLU to ATS route N864.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


12.


Description: To add new 5LNCs RIPNO and OSMEG to ATS route T256.

Objective:

To further improve AIP publication of aeronautical.


Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


13.

Project Name: Airspace Efficiency

Description:

To relax level capping restriction for traffic between Manchester TMA to Paris TMA during the winter months.

Objective:

To allow traffic ex MTMA to Paris TMA to flight plan more optimum levels H24 during the winter months.


Project Category:

Airspace Structure RAD

GBR

Originator(s):

GBR


14.

Description: To remove the "U" prefix in the distinction between lower and upper ATS

routes within London FIR/UIR and Scottish FIR/UIR - Phase 1.


Project Category:

GBR

Originator(s):

GBR

Removal will start with ATS route Q/UQ295. If no problems encountered a phased

removal over the next couple of years will be initiated.

AARRNN VV--22001166 -- 22001199//2200


75 28 June 2016 Edition: 1.0

Objective:

To simplify ATS routes designation within London FIR/UIR and Scottish FIR/UIR.

ATS Routes


15.

Project Name: RAD Promulgation

Description:

To publish in AIP Macedonia, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Skopje FIR.

Objective:

To harmonize the RAD promulgation via the AIP by the ECAC States.


Project Group:

RFG SE

Project Category:

AIP RAD

MKD

Originator(s):

EUROCONTROL


16.


Description:

To publish in AIP Malta, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Malta FIR.

Objective:



Project Category:

AIP RAD

MLT

Originator(s):

EUROCONTROL

Proposal ID : 77.078b Impl. Status: State(s) & Org. Comments:

17.

Description: To implement ATS airspace class D in Balder CTA.

Objective:

To improve the safety of operations on the continental shelf.


Project Category:

Airspace Structure

NOR GBR

Originator(s):

NOR

Ekofisk CTA and Balder CTA are located within

Norway FIR and Scottish FIR and involves "High Seas" airspace.


18.

Description: To implement ATS route segment T335 ZLA - BILNA.

Objective:

To further improve the ATS route network structure within Bratislava FIR.


Project Category:

ATS Routes

SVK

Originator(s):

SVK


19. Description: To replace existing 5LNC LUMEN.

Implemented 12 NOV 2015

CZE

Originator(s):

LUMEN is reserved in ICARD for Belgium. Proposal for replacement is based on

AARRNN VV--22001166 -- 22001199//2200


76 28 June 2016 Edition: 1.0

Objective:



Project Category:

5LNC EUROCONTROL ICAO

“Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Czech Republic.


20.

Description: To re-designate the existing ATS route T296 ROSOK - NIKDA - CDA as Q296.

Objective:

To rationalise the existing ATS route designators in order to further facilitate flight planning.


Project Category:

Route Redesignation

DEU DNK

Originator(s):

DEU

Germany will change the status of that route and will allow all traffic to use it. Normally segregated arrival routes are designated as “T”.

Denmark was already informed and coordination is in progress.

Proposal ID : 69.064a / 16.035a Impl. Status: State(s) & Org. Comments:

21.

Project Name: NEFAB Free Route Airspace

Description: To implement H24 Free Route Airspace across NEFAB above FL95/FL135.

Objective:

To further improve the airspace structure between Norway FIR, Finland FIR, Tallinn FIR and Riga FIR.


Project Group:

SG BALTIC

Project Category:

Free Route Airspace

EST FIN LVA NOR

Originator(s):

FAB NEFAB

ATS routes will be kept.

Related proposals:

69.064b / 16.035b

Proposal ID : 83.021 / 20.040 Impl. Status: State(s) & Org. Comments:

22.

Description: To re-designate Y76 ULTIR - BEDSO as new Y75.

Objective:

To rationalize the non-regional ATS route designators.


Project Group:

SG BALTIC

Project Category:

Route Redesignation

FIN

Originator(s):

EUROCONTROL


23.

Description: To re-designate the existing ATS route T94 OGTUD - SUTEV - SLU as P998 (release of T94).

Objective:



Project Category:

Route Redesignation

FIN SWE

Originator(s):

EUROCONTROL

Extension of RD P998 currently used in Finland FIR.

AARRNN VV--22001166 -- 22001199//2200


77 28 June 2016 Edition: 1.0


24.

Description: To implement new bi-directional ATS route T255 ATPEL - VAXUN -

IXONO.

Objective:

To further improve the ATS route structure within Finland FIR.


Project Category:

ATS Routes

FIN

Originator(s):

FIN

Alternate ATS route when TSA and R-areas on both sides of existing ATS route T89 are active.

TSA's will also be realigned east of T89 but restricted areas west of T89 cannot be realigned.


25.

Description: 1. To implement bi-directional ATS route T225 ATPEL - VAXUN -

IXONO (PERM, FL095 - FL660). 2. To realign the following existing ATS-routes:

a. L85 as ... BAVMO - ABKEM - BEXUL; b. T99 as ... ERKOM - EROKU - GOSVA - ADEDO; c. P606 as ALAMI - OKEVU - EVADI - RUMEP - NIPIB ... VEPIN -

ROKVI - OTKAP ...; d. Y369 as NUNTO - PISOX - REKDO; e. N851 as ... RIRIP - ODESO - LAKUT; f. L24 as ... LAKUT - PEKUX - IBVUT ...; g. Y368 as LAKUT - IPMOT - BEVOM - OTKIL ... ; h. M857 as ... LUSEP - ERNUT - IBOSU ... XEVLO - ABOXU -

DODEP - OTBAR ...; i. T83 as LUSEP - OTPAL - NAPRU ...; j. M6 as ... ADOPO - TUSBI - IDEPI ...; k. N850 as ... PENIV - EPAXU - INSOB ...; l. N15 as ... BAVMO - DODEP - DIVEG ...; m. N5 as BAVMO - ABOXU - BAKLA; n. M611 as ... OTKAP - ROKVI - IRLOT ...; o. M854 as KETOL - ROKVI - NITAS ...; p. T351 as KOMEK - ROKVI; q. Y75 as ... OSKEK - ADEDO - MIMRU ... .

Objective:

To further improve ATS route network within Finland UIR.


Project Category:

ATS Routes

FIN SWE RUS

Originator(s):

FIN


26.

Description: To allow DCT LELNA - GOBUR (FL195 - FL500), usable whenever zone EGD023 is active.

Objective:

To provide an additional option when waypoint LORKU is not available


Project Category:

DCTs RAD

FRA

Originator(s):

FRA FAB EC

AARRNN VV--22001166 -- 22001199//2200


78 28 June 2016 Edition: 1.0

(only when ATS routes UN866/UM195/UN63 are not available).


27.

Description:

1. To allow the following Direct" flight planning options within France: a. TURDO DCT SOSOV; b. SOSOV DCT TURDO; c. LEBRI DCT KORUL.

2. To allow proper DCT within FRASAI area within Madrid FIR.

Objective:

To further improve ATS route network and flight planning options between France and Spain.


Project Category:

DCTs RAD

FRA ESP

Originator(s):

FRA FAB EC


28.

Description:

To implement the following ATS routes: 3. UN531 UMOXA - MADEK 4. UN542 UMOXA - PEVIS - RUSIB; 5. UN533 UMOXA - ROSMU - QPR; 6. UN734 UMLER - UMOXA - KEREB - KURIS; 7. UN535 UMOXA - XIDAN; 8. UN536 TIVLU - COQUE; 9. UN977 BUNAV - TIVLU - NOVAN; 10. UN868 TIVLU - AKEMO; 11. UN749 TIVLU - QPR.

Objective:

To further improve ATS route network within France.


Project Category:

ATS Routes

FRA

Originator(s):

FRA


29.

Description: To reconsider the RAD restriction LF3049 by replacing as start point

SITET with ETRAT allowing the use of Night ATS route UQ203 ETRAT - PUMAL.

Objective:

To further improve flight planning options within France.


Project Category:

RAD

FRA

Originator(s):

EUROCONTROL IACA

Currently LF3049 restricts ATS route UN859 SITET - LGL where the major overflying traffic flow is only allowed to follow via AMB.

The main issue is that the restricted segment of UN859 is SITET - ETRAT - DVL - LGL which means that UQ203 became unavailable as traffic on SITET - ETRAT shall fly only via AMB.

Proposal to revise restriction to UN859 ETRAT - LGL was send to France end of August 2015.

AARRNN VV--22001166 -- 22001199//2200


79 28 June 2016 Edition: 1.0


30.


Description: To add 5LNCs UDEGO, DIXOV, RUBOV and UMOPO to ATS route P6

by replacing existing "unnamed" significant points and deleting all others.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


31.

Project Name: AIP Improvement

Description: Add existing 5LNCs ATWEL and MULIT used for training flights to ATS route N864.

Objective:



Project Category:

ATS Routes

GBR

Originator(s):

EUROCONTROL

Proposal ID : 69.104a / BM0013 Impl. Status: State(s) & Org. Comments:

32.

Description: To allow NIGHT "Direct" flight planning option SIT - RUTOM.

Objective:

To further imporve flight planning options within Hellas UIR.


Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

GRC

Originator(s):

FAB BLUE MED

Related proposals:

71.087

Proposal ID : 69.105 / BM0014 Impl. Status: State(s) & Org. Comments:

33.

Description: To allow NIGHT "Direct" flight planning options ABILO - VAXOS - RDS.

Objective:



Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

GRC

Originator(s):

FAB BLUE MED

Related proposals:

71.087


34. Project Name: Night Free Route Airspace Greece


GRC

Studies ongoing in the context of Blue Med. Earlier FRA implementation possible on a

AARRNN VV--22001166 -- 22001199//2200


80 28 June 2016 Edition: 1.0

Description: To implement Night DCTs for Hellas UIR, FL355 and above (2100 -

0400 UTC).

Objective:

To allign the airspace structure with real operations. Operational DCT's to be made flight plannable

Project Group:

FAB BLUE MED RFG SE

Project Category:

50 MPCPEs Free Route Airspace

Originator(s):

GRC FAB BLUE MED

national basis.

Related proposals:

69.104a

69.105

71.085a

71.086a

71.086b

71.089b

74.021


35.

Description: To allow NIGHT "Direct" flight planning option PINDO - LINRO.

Objective:



Project Group:

RFG SE

Project Category:

DCTs RAD

GRC

Originator(s):

FAB BLUE MED

Related proposals:

69.163

71.087


36.


Description:

To publish in AIP Greece, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Athinai FIR / Hellas UIR.

Objective:



Project Category:

AIP RAD

GRC

Originator(s):

EUROCONTROL


37.

Description: To change from Exit to Exit/Entry FRA waypoint PESAT.

Objective:

To further improve HUFRA utilisation.


Project Group:

RFG SE

Project Category:

Free Route Airspace

HUN

Originator(s):

EUROCONTROL

Related proposals:

87.003


AARRNN VV--22001166 -- 22001199//2200


81 28 June 2016 Edition: 1.0

38.

Project Name: Milano TMA, Phase 2

Description:

To re-organise Milano TMA.

Objective:

To further improve airspace organisation within Italy.


Project Category:

TMA

ITA

Originator(s):

ITA

It consists in change of lateral and vertical limits, subdivision in zones (with different lower limits), reclassification of some portions (from A to D principally) and withdrawal of VFR sectors, this changes are essentially focused on VFR flights activities and do not have impact on commercial flights.

Related proposals:

75.037a


39.

Description:

1. To extend the following existing ATS routes: a. Z275 OKRUB - APTEK; b. Z264 / Z272 / Z276 ROGLO - BURIX; c. P621 TUPUV - POKAX; d. Z269 EDURA - DEXES.

2. To realign existing ATS route Z155 OGLOV - EDAPA (new 5LNC) -

ISVIG.

Objective:

To adapt ATS routes to adjusted ATC sectors.


Project Category:

ATS Routes

NOR

Originator(s):

NOR

Related proposals:

69.064b / 16.035b


40.


Description:

To publish in AIP Portugal, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Lisbon FIR.

Objective:



Project Category:

AIP RAD

PRT

Originator(s):

EUROCONTROL


41.

Description: 1. To establish new 5LNC LUKIG at crossing between ATS routes

T400 and T401.

2. To change the following ATS route segments from CDR1 to permanent: a. T400 EGAGO - DIBVA - LUKIG; b. T401 SOLKA - LUKIG.


Project Category:

CDRs

SWE

Originator(s):

SWE

AARRNN VV--22001166 -- 22001199//2200


82 28 June 2016 Edition: 1.0

Objective:

To further improve the airspace structure within ESAA FIR.

Proposal ID : 80.021a Impl. Status: State(s) & Org. Comments:

42.

Description: To introduce P-RNAV SIDs/STARs for Milas/Bodrum (LTFE) airport.

Objective:

To further improve the airspace organisation within Istanbul FIR and Ankara FIR.


Project Group:

RFG SE

Project Category:

PBN TMA

TUR

Originator(s):

TUR

PBN SID /STAR (P-RNAV ,Based on GNSS) procedures for LTFE Airport completed.

Implementation after completion of SMART project.

Related proposals:

60.010c


43.

Description:

To implement the following bi-directional ATS routes: a. T/UT283 OKESA - KAVAK - BALSU; b. UT284 SIV - ORI - ARSUG.

Objective:

To further improve ATS route network in Turkey.


Project Group:

RFG SE

Project Category:

ATS Routes

TUR

Originator(s):

TUR


44.

Project Name: NAKID

Description: To replace existing 5LNC NAKID.

Objective:

1. To avoid 5LNC duplication within the EUR/NAT Region. 2. To improve the aeronautical information provided. 3. To be compliant with Annex 11.


Project Category:

5LNC

TUR

Originator(s):

ICAO EUROCONTROL

NAKID is assigned to France in ICARD. NAKID is used in Turkey at 402657N

035625E, Terminal Airspace, but is not reserved in ICARD.

Per the common criteria for substitution, Turkey shall substitute this code (email from ICARD Data Manager to Turkey dated 18 June 2015 refers).


45.

Project Name: SUDEM

Description: To replace existing 5LNC SUDEM.

Objective:

1. To avoid 5LNC duplication within the EUR/NAT Region. 2. To improve the aeronautical information provided. 3. To be compliant with ICAO Annex 11.


Project Category:

5LNC

TUR

Originator(s):

ICAO EUROCONTROL

SUDEM is assigned to The Russian Federation in ICARD.

SUDEM is used in Turkey, at 374742N 0321842E, for terminal airspace, but is not reserved in ICARD for Turkey.

Per the common criteria for replacement, Turkey has to substitute SUDEM (email from ICARD DM dated 18 June 2015 to Turkey refers).

AARRNN VV--22001166 -- 22001199//2200


83 28 June 2016 Edition: 1.0


46.

Description: 1. To implement bidirectional ATS route Y179 KOSAK - RAPUL;

2. To realign the following existing ATS routes: a. B492 as ODS - VAKOM - VAPEL; b. N191 as NIROV - VAPEL - RIMDA ; c. T219 as ODS - VAPEL – MIMKO; d. N617 as ODS - XONKO - BIKVA - BAREN; e. L919 as GOBLI - ODSAN - RATNO; f. L986 as ASMIN - ODSAN - RAPUL; g. P156 as NOLDU - ODSAN - ODS; h. M854 as LAMEX - ODSAN - ODS; i. M856 as GOBLI - ODS;

3. To delete existing ATS route W639 GOBLI - SH.

Objective:

To further improve the ATS route network within Ukraine.


Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

UKR

Originator(s):

UKR

Optimization of ATS route network within CTA/UTA Odesa-North.

To further improve options from/to Kherson AD.

Proposal ID : 57.018c / CE0082 Impl. Status: State(s) & Org. Comments:

47.

Project Name: Vienna TMA

Description:

To re-organise Vienna APP sectors after implementation of a new ATC system for Vienna approach.

Objective:

To further improve the airspace structure and increase the capacity within Vienna TMA, depending on traffic demand.

Implemented 10 DEC 2015

Project Group:

FAB CE RFG SE

Project Category:

ATC Sectors TMA

AUT

Originator(s):

AUT

New ATC system plus sectorisation changes for the TMA planned 27/28 November 2015 (no AIRAC date).

Proposal ID : 77.072d Impl. Status: State(s) & Org. Comments:

48.

Project Name: Free Route Airspace Wien, FRAW, Stage 4b

Description: To extend the DCTs H24/7, FL165+ (parallel operations with ATS routes) while initialising cross border operations with single States, when

possible between ATC units within FABCE or with adjacent FABs or ANSPs.

Objective:

To further improve the flight planning options between Wien FIR and adjacent FIRs/UIRs as a forth step towards FRAW (Free Route Airspace Wien) implementation.


Project Group:

FAB CE RFG SE

Project Category:

DCTs Free Route Airspace RAD

AUT

Originator(s):

AUT

Phased implementation: Stage 1 implemented 18 October 2012 (37

DCTs). Stage 2 implemented 7 MAR 2013. Stage 3a/b implemented 6 MAR 2014 - 11

DEC 2014. Stage 4a implemented 2 April 2015, Stage

4b planned autumn 2015. Stage 5 planned end 2016.

Related proposals:

AARRNN VV--22001166 -- 22001199//2200


84 28 June 2016 Edition: 1.0

76.047

77.072a

77.072b

77.072c

87.001


49.


Description:

To publish in AIP Bosnia and Herzegovina, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Sarajevo FIR.

Objective:



Project Group:

RFG SE

Project Category:

AIP RAD

BIH

Originator(s):

EUROCONTROL


50.

Description: To allow “Direct” H24 flight planning option VIBOP DCT SOLGU DCT KENEM (FL115 - FL325) for ARR LDSP.

Objective:

To further improve flight planning options within Sarajevo FIR.


Project Group:

RFG SE

Project Category:

DCTs RAD

BIH

Originator(s):

EUROCONTROL

Existing option via Sarajevo FIR is on dog-leg alignment via KEB.

Possible saving could be more than 20NM.


51.

Project Name: Point Merge

Description:

To create Point Merge arrival route system for Leipzig (EDDP) airport and to assure appropriate connections to en-route network by implementing the following unidirectional ATS routes: a. T431 RENDO - NERID; b. T432 BEBKU - NERID; c. T433 LASGA - GERDO; d. T434 TABAT - GERDO; e. T435 PIBAD - GERDO; f. T436 BERDI - TAVSO; g. T437 ADMOS - TAVSO; h. Y225 MAGDA - NENAN - TAMEB.


Project Category:

ATS Routes

DEU

Originator(s):

DEU

AARRNN VV--22001166 -- 22001199//2200


85 28 June 2016 Edition: 1.0

Objective:

To further improve airspace organization for arrivals to Leipzig (EDDP) airport.


52.


Description:

To publish in AIP Germany, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside German FIRs / UIRs.

Objective:



Project Category:

AIP RAD

DEU

Originator(s):

EUROCONTROL


53.

Project Name: DFS Karlsruhe - Skyguide Night DCT Package

Description:

To allow cross border direct (DCT) routings at the interface Germany - Switzerland in a first step mainly at night.

Objective:

To improve flight efficiency within FABEC.


Project Group:

FAB EC

Project Category:

DCTs RAD

DEU CHE FAB EC

Originator(s):

CHE DEU FAB EC

Related proposals:

79.041


54.

Project Name: Long Range Direct Routing SE Axis

Description:

To allow new route options - missing DCT segments and cross border direct (DCT) routings along the SE axis and new DCT segments feeding the new Hungarian FRA entry/exit point PESAT.

Objective:

To improve flight efficiency for major European flows crossing more than one FAB (at the SE axis from/to UK to/from South East Europe/Middle East).


Project Group:

FAB CE FAB EC

Project Category:

DCTs RAD

DEU AUT

Originator(s):

DEU AUT FAB EC

Related proposals:

77.072a

86.040


55.

Description: To replace existing 5LNC BRAVO.

Objective:

To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT


Project Category:

5LNC

ESP

Originator(s):

EUROCONTROL ICAO

Annex 11 stated that the 5LNCs shall be unique.

BRAVO is used 7 times worldwide and is allocated in ICARD to Brazil.

ICAO DM sent relevant message to ESP

AARRNN VV--22001166 -- 22001199//2200


86 28 June 2016 Edition: 1.0

region, to improve the aeronautical information provided and be compliant with ICAO Annex 11.

(DM23/01 msg 14-022). ESP will co-ordinate through planning unit.


56.


Description: Phase 1: To publish the following SIDs for Madrid (LEMD) airport in AIP

Spain, ENR 2 in accordance with Annex 11: a. NANDO1UV as NANDO1E; b. NANDO1VX as NANDO1V; c. PINAR1UV as PINAR1E; d. PINAR1VX as PINAR1V; e. RBO1UV as RBO1E; f. RBO1VX as RBO1V; g. SIE1NQ as SIE1N; h. VTB2NF as VTB1N; i. VTB1XE as VTB1K; j. VTB1YD as VTB1T; k. ZMR1BJ as ZMR1B; l. ZMR1NZ as ZMR1N; m. ZMR1SK as ZMR1Q; n. ZMR1XN as ZMR1K.

Objective:



Project Category:

AIP

ESP

Originator(s):

EUROCONTROL

Coded designator shall contain maximum 7 (seven) characters.

After the validity indicator only 1 (one) letter indicating the route indicator is allowed.

Related proposals:

84.056


57.

Project Name: FABEC FRA Step 1 (Ref FABEC FRA RTS 1.1)

Description: To allow around 50 optimized cross border DCTs through Skyguide AoR outside of military activity, H24 and/or Night and Weekend.

Objective:

To implement FRA Concept and further improve flight efficiency within FABEC.


Project Group:

FAB EC

Project Category:

50 MPCPEs Free Route Airspace

FAB EC CHE FRA DEU

Originator(s):

FAB EC EUROCONTROL

FABEC FRA RTS 1.1 in DEC 2013 and P-RTS in APR 2014.

Related proposals:

75.081

87.002


58.


Description:

To replace by 5LNCs in ENR 3.1 the unnamed significant points on the


Project Category:

GBR

Originator(s):

EUROCONTROL

AARRNN VV--22001166 -- 22001199//2200


87 28 June 2016 Edition: 1.0

following ATS routes: a. NANEV on ATS route Y904; b. RISDO, ERDOG and RAVDI on ATS route Y905; c. ENUKU, EDONU, GANKI, NAXIL and OSLEL on ATS route P600.

Objective:

To further improve the AIP airspace data promulgation.

AIP ATS Routes


59.


Description:

To publish in AIP Ireland, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Shannon FIR.

Objective:



Project Category:

AIP RAD

IRL

Originator(s):

EUROCONTROL


60.

Project Name: Free Route Airspace Vilnius - Phase 1

Description: To implement H24 Free Route Airspace FL245+ in Vilnius ACC.

Objective:

To further improve airspace organisation within Vilnius FIR.


Project Group:

SG BALTIC

Project Category:

Free Route Airspace

LTU

Originator(s):

LTU

Related proposals:

75.040b / 15.042b

76.052 / 23.029


61.

Description: To change existing ATS route UZ29 from a CDR1 into a CDR3.

Objective:

To further improve the airspace structure within Maastricht UAC while providing an additional configuration enabling a better workload distribution between sectors in function of the traffic flows in the Brussels Sector Group.


Project Category:

ATS Routes CDRs

NLD MUAC

Originator(s):

MUAC

To improve workload by avoiding re-routing in case of the activation of the TRA N.

To have more accurate traffic counts in the DECO sectors.

To avoid sector clipping through the DECO sector.


62. Project Name: FRA Like (DCT) Warsaw FIR - Phase 2

Description:


POL

Originator(s):

Related proposals:

76.052 / 23.029

AARRNN VV--22001166 -- 22001199//2200


88 28 June 2016 Edition: 1.0

To allow new 31 "Direct" flight planning options and extend the availability of 4 existing DCTs within Warszawa FIR.

Objective:

To further improve the airspace organisation and flight efficiency within Warszawa FIR.

Project Group:

SG BALTIC

Project Category:


POL 78.028a

88.015 / 23.023


63.


Description:

To publish in AIP Poland, ENR 1.10 FLIGHT PLANNING under paragraph 1. Procedures for the submission of a flight plan common text for Adherence to Airspace Utilization Rules and Availability - RAD inside Warszawa FIR.

Objective:



Project Category:

AIP RAD

POL

Originator(s):

EUROCONTROL


64.

Description: To reconsider RAD restriction EP2164 allowing other traffic than ARR LOWW on ATS route T720 MOLIL - REGLI.

Objective:

To further improve flight planning options via Warszawa FIR.


Project Category:

RAD

POL

Originator(s):

IATA

Currently T720 is only available for traffic ARR LOWW in order to reduce complexity in the EPWWT sector.


65.

Project Name: BARPI area

Description:

To withdraw from AIP Slovenia ENR 3.3 the vertical limits of ATS route segment M/UM859 BARPI - TUTIV.

Objective:

To adapt the AIP publication of ATS routes within cross-border delegated airspace between Slovenia and Italy.


Project Group:

RFG SE

Project Category:

AIP

SVN

Originator(s):

EUROCONTROL

BARPI area is special due to State border shape, none existence of boundary points between Ljubljana and Milano FIRs on ATS routes M859, Z495, P28 and different lower/upper DFL195/245.

Currently in AIP Italy M/UM859 BARPI - TUTIV is published with limits FL95 - FL195 - FL460 while in AIP Slovenia these limits are 8000FT AMSL - FL245 - FL660. This double contradicting publication for both lower and upper limits creates difficulties in airspace data systems and flight plan processing.

Similar in that area is ATS route segment

AARRNN VV--22001166 -- 22001199//2200


89 28 June 2016 Edition: 1.0

Z/UZ495 BARPI - ETAKO for which vertical limits are published only in AIP Italy as FL95 - FL195 - FL460 and covering portion in Ljubljana FIR despite that lower/upper limit is FL245 and top limit FL660.

For the third ATS route segment in that area P28 BARPI - RCH vertical limits are again published only in AIP Italy.

The data maintenance for ATS route segment BARPI - TUTIV for the EAD SDO shall be similarly organized between Italy and Slovenia as for Z495 and P28.


66.

Description: To withdraw Route Designator Q863 from ATS route segment BEDOX - DIPSA also double designated as L863.

Objective:

To simplify route designation within Ljubljana FIR.


Project Group:

RFG SE

Project Category:

Route Redesignation

SVN

Originator(s):

EUROCONTROL

Resolution of “Unforeseen” RD break reported by Jeppesen.

As part of Stage 3b of FRAW project Austria deleted UQ863 DIPSA - ERKIR replacing it by DCT.

Currently RD Q863 exists after ERKIR in Germany and with dead end as PEROT - BEDOX - DIPSA.

Withdrawal of Q863 in Slovenia will not change the designation of existing ATS route segment while existence has no any purpose


67.


Description: To adapt the upper vertical limit of ATS routes P28 ABLAT - PZ - BARPI.

Objective:

To adapt in State AIP ATS routes vertical limits.


Project Category:

AIP

SVN

Originator(s):

EUROCONTROL

Related proposals:

83.040a


68.

Description: To replace existing 5LNC DOGAN

Objective:

To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT region, to improve the aeronautical information provided and be compliant with ICAO Annex 11.


Project Group:

RFG SE

Project Category:

TUR

Originator(s):

EUROCONTROL ICAO

DOGAN is used by and is allocated in ICARD to Morocco.

ICAO DM sent relevant message to TUR (DM 20/01 MSG 14-015).

TUR will enquire with military.

AARRNN VV--22001166 -- 22001199//2200


90 28 June 2016 Edition: 1.0

5LNC

Proposal ID : 60.010f Impl. Status: State(s) & Org. Comments:

69.

Project Name: SMART Phase 2/3

Description: 1. To transfer Istanbul ACC to new Ankara ACC FL245 and above. 2. To transfer Izmir ACC to new Ankara ACC FL245 and above.

Objective:

To further improve airspace organisation within Istanbul FIR and Ankara FIR and enhance capacity within the Turkish ACCs in order to cope with the increasing traffic demand.


Project Group:

RFG SE

Project Category:

Airspace Structure

TUR

Originator(s):

TUR

Related proposals:

60.010b

60.010c

60.010g / 15.046g

60.010h / 15.046h

Proposal ID : 86.048 / 23.004a Impl. Status: State(s) & Org. Comments:

70.

Description: To implement bi-directional ATS route P130 BODKA - ELSIV - REBLO.

Objective:

To further improve ATS route network between Baku FIR and Yerevan FIR.

Implemented 07 JAN 2016

Project Group:

SG BLACK

Project Category:

ATS Routes

ARM AZE

Originator(s):

ARM AZE TKM

ELSIV 403752N 0452214E will be a new boundary point.

Related proposals:

23.004b

Proposal ID : 79.029b / 18.012b Impl. Status: State(s) & Org. Comments:

71.

Description: To implement bi-directional ATS route T916 MATAL - SUBUT - LEYLA.

Objective:

To further improve the ATS route network in Baku FIR.


Project Group:

SG BLACK

Project Category:

ATS Routes

AZE

Originator(s):

EUROCONTROL


72.

Project Name: Nicosia Direct Route Airspace - Phase 1A

Description: To allow 5 (five) NIGHT "Direct" flight planning options above FL285.

Objective:

To further improve flight planning options within Nicosia FIR.


Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

CYP

Originator(s):

CYP FAB BLUE MED

DCT options are approved and included in the Blue Med document “OPS-D2.1 - BLUE MED BM DCT _AVBL Night Wkend_ Catalogue version Nov 2015_rev 1.2” produced by the BM RNC & FR TF.

Night period 21:00 - 04:00.

Related proposals:

71.088a

71.088b

86.056b

AARRNN VV--22001166 -- 22001199//2200


91 28 June 2016 Edition: 1.0

86.056c

86.056d

86.056e


73.

Project Name: New Apulia CTR

Description:

To modify the organisation of airspace inside Brindisi TMA by: a. withdrawal of Bari CTR; b. withdrawal of Brindisi CTR; c. implementation of new APULIA CTR (includes the airspace of above

mentioned CTRs plus a new connection area).

Objective:

To modify the traffic management in particular for inbound/outbound traffic to/from Bari (LIBD) and Brindisi (LIBR) airports.


Project Category:

Airspace Structure TMA

ITA

Originator(s):

ITA

The change is part of the activities related to the transit of the provision of Air Navigation Services (ANS) from Italian Air Force to ENAV SpA on the airport of Brindisi Casale.

In order to minimise the impact of this change on users (both AOs and ATCOs) has been decided not to modify SIDs and STARs of the related airports


74.

Project Name: SEE LRDCTs

Description: To allow 11 (eleven) “Direct” “Daily” and “Night” flight planning options.

Objective:

To further improve flight planning options between Sofia FIR, Beograd FIR, Sarajevo FIR, Zagreb FIR and Ljubljana FIR.

Implemented 04 FEB 2016

Project Group:

RFG SE

Project Category:

DCTs RAD

BGR BIH HRV SRB SVN

Originator(s):

SRB

Some of the DCTs are available in parallel with relevant FRAs.


75.

Description: To implement new P-RNAV SIDs/STARs for Burgas (LBBG) airport.

Objective:

To further improve airspace organisation within Sofia FIR.


Project Group:

RFG SE SG BLACK

Project Category:

Airspace Structure

BGR

Originator(s):

BGR


76. Description: To implement new P-RNAV SIDs/STARs for Varna (LBWN) airport.


BGR

Originator(s):

AARRNN VV--22001166 -- 22001199//2200


92 28 June 2016 Edition: 1.0

Objective:


Project Group:

RFG SE SG BLACK

Project Category:

Airspace Structure

BGR


77.

Description: To allow the availability during limited day hours for limited destinations above FL355 of "Direct" flight planning option MAREM DCT ABUDO.

Objective:

To further improve the ATS route network while providing a shorter route option for traffic from Scandinavia to the Adriatic coast.


Project Category:

DCTs RAD

CZE

Originator(s):

IATA

This is the only missing link on H24 southbound options to Croatia via Czech Republic, Austria and Slovenia from Scandinavia.

Currently under trial till 26 MAY 2016 used H24.

Related proposals:

69.220b

75.033a


78.

Project Name: AMOSA DCT WUR

Description: To allow H24 Direct flight planning option AMOSA DCT WUR for city pair

EDDM - ELLX above FL245.

Objective:

To offer new short routing within upper airspace and improve flight efficiency within FABEC (higher FL, shortcut).


Project Category:

DCTs RAD

DEU

Originator(s):

DEU FAB EC

Proposal ID : 59.017e Impl. Status: State(s) & Org. Comments:

79.

Project Name: London Airspace Management Program, LAMP Phase 1a

Description:

1. 5 new RNAV5 STARs into TIMBA (and LUMBA should MAY be out of service). WILLO and TIMBA remain as conventional holds.

2. A Point Merge arrival structure for Thames Radar incorporating two new holding stacks for London City named JACKO and GODLU with new STARs, new SIDs for departures to the South and additional Controlled Airspace.

3. Re-sectorisation of TCSE, TCSW and AC DVR/WOR sectors to include a solution to address the S17 OPA Hotspot.

4. Re-routeing of Stansted, Cambridge, Luton and Northolt DET


Project Category:

Airspace Structure ATS Routes PBN TMA

GBR

Originator(s):

GBR

Designs based on P-RNAV routes requiring considerable regulatory input.

AARRNN VV--22001166 -- 22001199//2200


93 28 June 2016 Edition: 1.0

departures into TC EAST (out of TCSE). 5. Re-routeing of Thames arrivals from the North into TC EAST (out of

TC MIDS and TCNE). 6. Lowering of CAS over the POMPI Triangle and Isle of Wight within

which a new contingency hold for Solent traffic will be located.

Objective:

To increase systemisation of the airspace structure in order to provide safety and efficiency enhancements and additional capacity in London TMA through a fundamental review of ATS route and sector structure (London Airspace Management Programme/ LAMP).


80.


Description:

1. To replace by 5LNCs in ENR 3.1 the "unnamed" significant points on the following ATS routes: a. OBUNI, VEMAB on ATS route L612; b. IDEXA, UNIGO, ARPUB, EMLIP, OSLOR on ATS route L975; c. OSTUG, UNDUX on ATS route L70; d. EDUXO, ELNOD on ATS route L603; e. ULSAX, ERGAB, UTOGU, IPDOR on ATS route N601; f. ROBVA, NENVO on ATS route N862; g. LOMVO on ATS route Y124.

2. To remove from ENR 3.1 "unnamed" significant points from ATS route L975.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


81.

Description: To allow “Direct” flight planning option DOLEV DCT NAKIT outside of

SEA FRA.

Objective:

To further improve flight planning options within South East Europe.


Project Group:

RFG SE

Project Category:

DCTs RAD

HRV BIH SRB

Originator(s):

MKD


82. Project Name: MABOX - ADEXI

Description:


ITA MLT

AARRNN VV--22001166 -- 22001199//2200


94 28 June 2016 Edition: 1.0

To extend existing ATS route M622 segment MABOX - ADEXI.

Objective:

To further improve the ATS route network while offering the shortest route for destination LICT according flow arrangement between Italy and Malta.

Project Group:

FAB BLUE MED

Project Category:

ATS Routes

Originator(s):

FAB BLUE MED

Proposal ID : 62.086c / BM0004 Impl. Status: State(s) & Org. Comments:

83.

Description: To implement southbound ATS route M727 GIANO - TRP - SENTI.

Objective:

To further improve the ATS route network within Roma FIR.


Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA

Originator(s):

FAB BLUE MED

ATS route exist in Italy as upper one.

Related proposals:

62.086e

Proposal ID : 62.086e / BM0075 Impl. Status: State(s) & Org. Comments:

84.

Description: To implement bidirectional ATS route M742 PAL - ADEXI.

Objective:

To further improve the ATS route network within Roma FIR.


Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA

Originator(s):

FAB BLUE MED

ATS routes exist in Italy as upper one.

Related proposals:

62.086c


85.

Description: To straighten the boundary between the DECO and the Brussels Sector Group.

Objective:



Project Category:

ATC Sectors

MUAC

Originator(s):

MUAC

To improve the working procedures of the Brussels West Sectors by reducing the radar working scale.

To optimise sector sequence by avoiding unnecessary sector clipping

To allow for better direct routeing.


86.

Description: To change the DFL, from FL335 to FL355, in the West sectors of the MUAC Brussels Sector Group.


Project Category:

MUAC

Originator(s):

MUAC

Low sectors between FL245 and FL355. Upper sector in the Brussels West Sector

Group above FL355. The DFL in the East remains FL335.

AARRNN VV--22001166 -- 22001199//2200


95 28 June 2016 Edition: 1.0

Objective:


ATC Sectors Follow-on projects envisage a 3 layer approach in the Eastern part of the Belgian airspace.


87.


Description: To re-designate existing Helicopter route KY04 as KY994.

Objective:

To adapt existing RDs in accordance with ICAO requirements.


Project Group:

RFG NW

Project Category:

AIP Route Redesignation

NOR

Originator(s):

EUROCONTROL

RD is not in accordance with Annex 11 and not coordinated via ICARD.

Related proposals:

80.010i


88.


Description: To re-designate the following existing Helicopter routes: KY01, KY06 - KY09, KY10 - KY21, KY30 - KY42, KY50 - KY51, KY53 - KY56, KY70 and KY80 as described in the attached document.

Objective:



Project Category:


NOR

Originator(s):

EUROCONTROL

RDs KY01, KY06 - 09 are not in accordance with Annex 11.

All RDs are not coordinated via ICARD.


89.



Objective:



Project Group:

RFG NW

Project Category:


NOR

Originator(s):

EUROCONTROL


Related proposals:

80.010j


90.

Project Name: Lower airspace re-organisation Beograd FIR - Step 1

Description:

To ajustment of Podgorica TMA horizontal boundaries.


Project Group:

SRB MNE

Originator(s):

Related proposals:

68.012b

68.012c

AARRNN VV--22001166 -- 22001199//2200


96 28 June 2016 Edition: 1.0

Objective:

To further improve the airspace structure and ATS route network within Beograd FIR.

RFG SE

Project Category:

Airspace Structure

SRB MNE

68.012d


91.

Description:

1. To reshape the geographical boundary between Beograd ACC West and North sectors.

2. To introduce 5 vertical layers which with 4 geographical shapes creates 20 airspace volumes as follows: a. Lower FL145 (later FL125) - FL325; b. Middle FL325 - FL345; c. Upper FL345 - FL365; d. Top FL365 - FL385; e. Super top FL385 - FL660.

Objective:

To further improve airspace organization within Beograd FIR/UIR.


Project Group:

RFG SE

Project Category:

ATC Sectors

SRB MNE

Originator(s):

SRB MNE

Considering the technical and HR capabilities Beograd ACC will be able to open up to 14 sectors during peak hours.


92.

Description: To allow “Direct” “Daily” flight planning option DONIV DCT ETIDA for

DEP LYBE.

Objective:

To further improve flight planning options within Beograd FIR.


Project Group:

RFG SE

Project Category:

DCTs RAD

SRB

Originator(s):

EUROCONTROL

Availability required outside of SEAFRA operational hours 05:00 - 23:00 (04:00 - 22:00).


93.

Description:

1. To implementation the following ATS routes: a. L131 GUSLI - DF southbound; b. L133 DISKA - LAPTO northbound; c. T921 ADEKI - KOTAN - ANAGU - LAPTO northbound.

2. To re-align existing bi-directional ATS route N644 LAGAS - ADEKI as LAGAS - BADIR 4129N 04522E - ADEKI.

Objective:

To further improve ATS route network between Baku FIR and Tbilisi FIR.

Implemented 03 MAR 2016

Project Group:

SG BLACK

Project Category:

ATS Routes

AZE GEO

Originator(s):

EUROCONTROL

a. DF - TBS - DISKA is an existing bi-directional ATS route segment M737.

b. straitening of existing dog-leg option M737/N82 DISKA - TBS - DF - LAPTO.

c. KOTAN - new waypoint on L850.

Related proposals:

86.051b / 23.007b


94. Project Name: ECAC States AIP en-route publication issues Implemented CZE

AARRNN VV--22001166 -- 22001199//2200


97 28 June 2016 Edition: 1.0

Description:

To publish in ENR 3.3 CDRs based on ERNIP publication requirement to cover the whole period of availability.

Objective:


03 MAR 2016

Project Category:

AIP CDRs

Originator(s):

EUROCONTROL


95.


Description: To re-designate the following existing Helicopter routes: KY60 - KY66, KY70 - KY74, KY82, KY85.

Objective:



Project Group:

RFG NW

Project Category:


DNK

Originator(s):

EUROCONTROL


Proposal ID : 80.010g Impl. Status: State(s) & Org. Comments:

96.



Objective:



Project Group:

RFG NW

Project Category:


DNK GBR

Originator(s):

EUROCONTROL


In AIP UK Helicopter routes are not published in ENR 3.4 as required by Annex 15. It is stated that these routes appear in AD 2, ENR 1.15 and ENR 6 but the information there is not sufficient and complete.

Proposal ID : 80.010j Impl. Status: State(s) & Org. Comments:

97.



Objective:



Project Group:

RFG NW

Project Category:


DNK

Originator(s):

EUROCONTROL


Norway re-designated its route as from 4 FEB 2016.

Related proposals:

80.010e

Proposal ID : 80.010i Impl. Status: State(s) & Org. Comments:

AARRNN VV--22001166 -- 22001199//2200


98 28 June 2016 Edition: 1.0

98.



Objective:



Project Group:

RFG NW

Project Category:


DNK

Originator(s):

EUROCONTROL


Norway re-designated its route as from 4 FEB 2016.

Related proposals:

80.010d


99.


Description: To further rationalisation of base of ATS route L9 by removing 2 (two) unnamed Lat/Long points in UK AIP.

Objective:

To further improve the AIP airspace data publication.


Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


100.


Description: Further rationalisation of base of ATS route M140 by removing 2 (two) unnamed Lat/Long points in UK AIP.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


101.


Description: Further rationalisation of base of ATS route N514 by removing 1 (one) unnamed Lat/Long points in UK AIP.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


102.


Description: Further rationalisation of base of ATS route Y76 by removing 1 (one) unnamed Lat/Long points in UK AIP.


Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL

AARRNN VV--22001166 -- 22001199//2200


99 28 June 2016 Edition: 1.0

Objective:



103.


Description: Further rationalisation of base of ATS route L980 by removing 1 (one) unnamed Lat/Long points in UK AIP.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL

Proposal ID : 62.091c Impl. Status: State(s) & Org. Comments:

104.

Project Name: Polish Airspace Project 2010+, Phase 3a

Description: To implement a vertical split at FL365 of all current geographical Warszawa ACC sectors creating LOW and HIGH Sectors respectively.

Objective:

To further improve the airspace structure within Warszawa ACC and increase capacity while applying vertical splits.


Project Category:

Airspace Structure ATC Sectors

POL

Originator(s):

POL

Depending on training of ATC staff. Max. 10/11 active sectors with vertical

splits.

Related proposals:

62.091a

62.091b

62.091e / 23.035

76.052 / 23.029

76.053 / 18.039


105.

Description: To re-designate existing ATS route Z136 LAGAR - GODLO as T871 (release of Z136).

Objective:

To rationalise the existing ATS route designators within Warszawa FIR in order to further facilitate flight planning and release RDs.


Project Category:

Route Redesignation

POL

Originator(s):

EUROCONTROL


106.

Description: To increase the upper limit of ATS route Z64 SPR - MOLUS from FL195

to FL660.

Objective:

To improve connectivity for flights DEP LSGS via UN871 and bring flight planning closer to real trajectories.


Project Category:

ATS Routes

CHE

Originator(s):

CHE


AARRNN VV--22001166 -- 22001199//2200


100 28 June 2016 Edition: 1.0

107.

Description:

To implement the following westbound ATS routes: a. Y263 BRANE - LODRO for DEP EDDT; b. Y264 BELID - MAG for DEP EDDB.

Objective:

To further improve ATS route options for departures from Berlin airports.


Project Category:

ATS Routes

DEU

Originator(s):

DEU


108.

Description: To replace existing 5LNC BANIX.

Objective:




Project Category:

5LNC

DEU

Originator(s):

EUROCONTROL ICAO

BANIX is reserved in ICARD for Portugal. Proposal for replacement is based on

“Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Germany.

OA/D to react accordingly.


109.

Description:

To re-designate the following ATS routes: a. Z11 LBU - ABUMO as Z3; b. Z16 POVEL - GALMA as Z94.

Objective:

To rationalise the existing ATS route designators within Germany in order to further facilitate flight planning and release RDs.


Project Category:

ATS Routes Route Redesignation

DEU DNK

Originator(s):

EUROCONTROL

Related proposals:

86.052c


110.

Description: To vertically split existing SAN Sector into SAN Lower (SAL) and SAN

Upper (SAU) Sectors with DFL345.

Objective:

To further improve airspace organization within Madrid FIR and improve capacity of Madrid ACC (LECM) ATC Sectors.


Project Group:

RFG SW

Project Category:

ATC Sectors

ESP

Originator(s):

ESP

LECMSAL will be never be used alone, and it will be used either with LECMSAU (as current LECMSAN sector) or with Asturias Lower, LECMASL (LECMNWL sector).


111.

Description:

To update both AIP Denmark and AIP Sweden with regard to DK-SE FAB FRA publication. a. FRA Flight planning moved from ENR 1.3 to ENR 1.10. b. Sub-section in ENR 4.1 and ENR 4.4 regarding FRA relevant point

in "other state" deleted and replaced with text description of FRA


Project Category:

AIP

FAB Denmark/Sweden

Originator(s):

DNK SWE

AARRNN VV--22001166 -- 22001199//2200


101 28 June 2016 Edition: 1.0

entry/exit to DK-SE FAB FRA in ENR 1.10. c. Update of ENR 6.2-1 map, DK-SE FAB FREE ROUTE AIRSPACE

(A/D/I deleted from map).

Objective:

To further improve the DK-SE FAB FRA publication.


112.

Description: To re-designate the existing ATS routes Q169 ROMAK - NARAK as N869 (same segment with different RDs Q169/UN869).

Objective:

To adapt the ATS route designation in lower and upper airspace.


Project Category:

Route Redesignation

FRA

Originator(s):

EUROCONTROL


113.

Project Name: Marseille ACC re-organisation Phase 2

Description: To implement a 4th layer FL375+ for sectors G - Y - A - B in Marseille

ACC (Zone East).

Objective:

To further improve the airspace structure and capacity within Marseille ACC.


Project Category:

ATC Sectors

FRA

Originator(s):

FRA

Frequencies allowing to split all new sectors progressively during summer 2016.

Related proposals:

83.025b


114.

Project Name: MEN - ETIDO project

Description: To implement a CDR3 UZ871 NINUN - ETIDO n order to segregate the

traffic MEN - ETIDO from the traffic MEN - LTP.

Objective:

To further improve ATS route options within France.


Project Category:

ATS Routes CDRs

FRA

Originator(s):

FRA


115.

Description: To create a new CDR 2 UL 10 segment RINTI-LESDO allowing

connection of Gatwick departures to CDR2 UL 15 at LESDO.

Objective:

To further improve the utilisation of existing CDRs while proposing a more direct route for south-east bound Gatwick departures.


Project Category:

CDRs

FRA

Originator(s):

FRA

Availability of UL 10 during high traffic season subject to evaluations during summer 2016 before final assessment in winter 2016/2017.


AARRNN VV--22001166 -- 22001199//2200


102 28 June 2016 Edition: 1.0

116.

Description: To implement bi-directional ATS route UN511 ERPOM - BERAD (FL285 -

FL500).

Objective:

To further improve ATS route avoiding options within France.


Project Category:

ATS Routes

FRA

Originator(s):

FRA

Required for avoidance of D12 area when active.


117.

Description: To replace existing 5LNC ASMAT.

Objective:




Project Category:

5LNC

FRA

Originator(s):

EUROCONTROL ICAO

ASMAT is reserved in ICARD for Russian Federation.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for France.


118.

Project Name: AVANT - TNT

Description: To establish H24 DCT AVANT - TNT above FL 375 initially and later extend CDR/Airway UN863 from AVANT to POL.

Objective:

To further improve efficiency for traffic overflying the London FIR


Project Category:

ATS Routes DCTs RAD

GBR

Originator(s):

GBR

Continuing as a Trial - likely to be amended to KATHY - TNT FL355+.


119.


Description: To further rationalisation of base of ATS route L10 by removing 3 (three) unnamed Lat/Long points in UK AIP.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


120.

Description:

To implement the following ATS routes for flights to/from Mazury (EPSY) airport: a. T720 GRUDA - VEKAV - ETEDI - IBINO; b. Y564 NIVON - IXIXI; c. Y565 OLILA - UDROV; d. Y566 UDROV - OTMAX - XESNA.


Project Category:

ATS Routes

POL

Originator(s):

POL

Unnamed points are in process of coordiantion with ICAO.

AARRNN VV--22001166 -- 22001199//2200


103 28 June 2016 Edition: 1.0

Objective:

To further improve airspace organization within Warszawa FIR.


121.

Description: To change to CDR 1 H24 existing weekend/night CDR 1 N5 VENES -

GITOV.

Objective:

To further improve ATS route network within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes CDRs

POL RUS

Originator(s):

POL

Currently N5 is CDR 1 every weekend FRI 2000 (2000) - MON 0600 (0600) and HOL, every night 2000 (2100) - 0500 (0600).

As GITOV is boundary point with RUS the change might have an impact on traffic flows in that region.


122.


Description: To replace by 5LNC in ENR 3.5 unnamed significant point "4016N" on ATS route T16 as NAVIX - 4016 - ETESO - GONAN.

Objective:

To further improve the AIP airspace data promulgation.


Project Category:

AIP ATS Routes

PRT

Originator(s):

EUROCONTROL

Co-ordination inside Portugal is in progress.


123.

Description: To re-place BAK VOR with 5LNC ELBUX at same position and re-align

the relevant 3 (three) existing ATS routes.

Objective:

To enhance the airspace structure in line with NAV strategy.


Project Category:

Airspace Structure

SWE

Originator(s):

SWE


124.

Description: To implement bi-directional ATS route L987 MALIV - SIMEG - ETRUS -

PENOR.

Objective:

To further improve airspace options within Sweden FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes DCTs RAD

SWE POL

Originator(s):

SWE

Related proposals:

85.033b / 22.042c


125. Project Name: Malmo ACC

Implemented SWE

AARRNN VV--22001166 -- 22001199//2200


104 28 June 2016 Edition: 1.0

Description: To split Malmo ACC/ ESMM sector 2.

Objective:

To further improve the sectorisation within Sweden while balancing traffic and workload, increasing capacity and improving flight efficiency.

31 MAR 2016

Project Category:

ATC Sectors

Originator(s):

SWE


126.

Description: To implement northbound ATS route T6 PINDO - ELBAK for ARR LATI.

Objective:

To further improve the ATS route network within Tirana FIR.

Implemented 28 APR 2016

Project Group:

RFG SE

Project Category:

ATS Routes

ALB

Originator(s):

EUROCONTROL


127.

Project Name: New ARR/DEP LATI Phase 4

Description: To implement southbound ATS route T8 AKIKA - INLOT for ARR LATI.

Objective:

To further improve the airspace structure between Beograd FIR and Tirana FIR.


Project Group:

RFG SE

Project Category:

Airspace Structure

ALB SRB MNE

Originator(s):

SRB MNE

Independent development but connected to proposal 71.014 improvements.

Final goal is to achieve round about DEP / ARR system for Tirana airport via Beograd FIR as follows: ALELU - DEP LATI; AKIKA - ARR LATI; RETRA - DEP LATI; PETAK - ARR LATI; EBELA - DEP LATI.

Related proposals:

71.014a

71.014c


128.

Description:

To implement the following northbound ATS routes: a. UM127 NIKRO - OVVER; b. UM173 OVVER - ALELU.

Objective:



Project Group:

RFG SE

Project Category:

ATS Routes

ALB

Originator(s):

IATA

M127 NIKRO - OVVER lower ATS route up to FL285 existing with no penalization, except that it is compulsory for DEP LGKR / LGPZ.

RD M173 is already used in Beograd FIR. Proposed option is beneficial for DEP

LGSA, for example and will allow avoidance of MIL, SKP and TSL sectors.

Proposed option is shorter by around 8NM then existing one - KFN UN731 YNN UL604 TRN UM127 ALELU.


AARRNN VV--22001166 -- 22001199//2200


105 28 June 2016 Edition: 1.0

129.

Description: To implement westbound ATS route UP14 PINDO - PAPIZ.

Objective:

To further improve ATS route network within Tirana FIR.


Project Group:

RFG SE

Project Category:

ATS Routes

ALB

Originator(s):

EUROCONTROL

FRA evaluation showed that this connection is attractive for the AOs.

RD P14 is already used in Hellas UIR.


130.

Description: 1. To implement southbound ATS route UP744 PETAK - DIMIS. 2. To re-align existing ATS route UL607 as PETAK - PINDO.

Objective:



Project Group:

RFG SE

Project Category:

ATS Routes

ALB

Originator(s):

ALB EUROCONTROL


131.

Project Name: UDROS / ODERO area re-organization

Description:

1. To establish new FIR boundary points and re-organize existing ones as follow: a. UDROS - swap from westbound to eastbound use to serve

traffic flows to Rostov FIR, Tbilisi FIR, Yerevan FIR and AGINA/DASIS to Tehran FIR;

b. ODERO - swap from eastbound to westbound use to serve

traffic flows from Rostov FIR, Tbilisi FIR, Yerevan FIR and DASIS from Tehran FIR;

c. NEGEM - new point South West of ODERO for westbound

traffic flows from Baghdad FIR and BONAM from Tehran FIR; d. ARTAT- new point South West of NEGEM for eastbound traffic

flows to Baghdad FIR and ALRAM to Tehran FIR. 2. To implement new ATS routes and re-organize accordingly the

existing ATS routes inside/between Bucuresti FIR, Sofia FIR and Istanbul / Ankara FIRs.

3. To allow proper DCT options and improse relevant RAD restrictions to balance the traffic flows.

Objective:

To further improve ATS route network between Romania, Bulgaria and Turkey.


Project Group:

RFG SE

Project Category:

ATS Routes

BGR TUR ROU

Originator(s):

EUROCONTROL TUR

Proposed airspace re-organization is required due to increased traffic flows in that area of the Black Sea following partial airspace unavailability of Simferopol FIR and Dnipropetrovsk FIR and limited airspace use of Damascus FIR and Baghdad FIR.

The study by all States for the best vertical split of sectors to cope with the new traffic distribution caused by the crisis situation imposing UDROS / ODERO area reorganization is required. EUROCONTROL to support in reaching the best solutions.

For detailed description see RNDSG Airspace Improvement Synopsis/ RAIS #5.0.


AARRNN VV--22001166 -- 22001199//2200


106 28 June 2016 Edition: 1.0

132.

Description: To raise the DFL between controlled Class C and uncontrolled airspace Class G from FL095 to FL105.

Objective:

To further simplify and harmonize airspace organization within DANUBE FAB.


Project Group:

RFG SE

Project Category:

Airspace Structure

BGR

Originator(s):

BGR

Outcome of DANUBE FAB ADODEG work for harmonization between Bulgaria and Romania.


133.

Description: To withdraw the following existing waypoints: EDADA, EMLOK, TAKAK and BADKI.

Objective:

To further simplify airspace organisation within Sofia FIR and release unnecessary waypoints.


Project Group:

RFG SE

Project Category:

5LNC

BGR

Originator(s):

EUROCONTROL

EMLOK, TAKAK were established few years ago to allow shorter connections mainly for flights to/from LBBG / LBWN depending on ATS routes availability.

BADKI was established during the initial ATS routes reorganization over the Black Sea.

Existing airspace organization within South East Europe allows a lot more new possibilities and existence of these waypoints is not operationally required.

In case being withdrawn these 5LNCs will be release in ICARD as part of simplification project initiated by ICAO and EUROCONTROL.


134.

Description: To implement new P-RNAV SIDs/STARs for Sofia (LBSF) airport.

Objective:



Project Group:

RFG SE SG BLACK

Project Category:

Airspace Structure

BGR

Originator(s):

BGR


135.

Description: To re-align existing ATS route Y505 as NISVA - OMENO - NIKTI.

Objective:

To further improve the ATS route network within Sofia FIR.


Project Group:

RFG SE

Project Category:

ATS Routes

BGR

Originator(s):

EUROCONTROL

New alignment of Y505 will be straight line and avoid zig-zag via DOTAM.

AARRNN VV--22001166 -- 22001199//2200


107 28 June 2016 Edition: 1.0


136.

Description:

To re-designate the following ATS routes: a. T299 GERGA - PEROM as T239; b. T299 PEROM - KOSEB - CDA as T298; c. T504 KOPEX - MIC as T155 (used south of MIC); d. T51 KELOM - KOPEX as T155 (release of T51).

Objective:

To rationalise the existing ATS route designators within Germany and Denmark in order to further facilitate flight planning and release RDs.


Project Category:

Route Redesignation

DEU DNK

Originator(s):

EUROCONTROL


137.

Project Name: FRA Germany - Phase 1

Description:

To initiate preparation Full Free Route Airspace within Germany by: a. replacement of most of German UQ routes with DCTs (release of

RDs); b. lowering of the MIN FL of several existing DCTs; c. fine-tuning of some KUAC DCTs (mainly supporting ERL sector

flows).

Objective:

To improve flight efficiency within FABEC and obtain more experiences within Munich ACC working with DCTs instead ATS routes without a very advanced ATM system.


Project Group:

FAB EC

Project Category:

ATS Routes DCTs Free Route Airspace

DEU

Originator(s):

DEU FAB EC

For detailed description see RNDSG Airspace Improvement Synopsis/ RAIS #5.0.

Related proposals:

87.005b

87.005c

87.005d

87.005e


138.

Project Name: NTM4 Sector split

Description: To implement 4th layer of NTM sector.

Objective:

To improve sector capacity within Karlsruhe UAC.


Project Category:

ATC Sectors

DEU

Originator(s):

DEU


139.

Description: To delete route-segment on T53 TUDLO - LUGAS - OSKEV - KORSA.

Objective:

To enhance AIP publication and avoid double designated route segments.


Project Category:

ATS Routes

DNK

Originator(s):

DNK


AARRNN VV--22001166 -- 22001199//2200


108 28 June 2016 Edition: 1.0

140.

Description:

To re-designate the following existing ATS routes: a. T13 DIPER - VESAN - RATUK - SOVAT as L613 (release of T13)

(same segment with different RDs T13/UL613); b. T120 KOKOS - BADUR as N585 (same segment with different RDs

T120/UN858).

Objective:



Project Category:

Route Redesignation

FRA

Originator(s):

EUROCONTROL


141.

Description: To allow ARR ETAR during the week via point MAKOT by revising existing RAD restrictions LFED1000, LF2926 and LF7000.

Objective:

To allow additional shorter flight plannable option between France and Germany.


Project Category:

DCTs RAD

FRA DEU

Originator(s):

U.S.A.F.E

Current arrival option from South is DJL UM129 RESPO UM187 POGOL R11 OBORN V17 LUPEN T126 SUL Y710 ESULI N851 LBU Z11 TAGIK Z818 RINEX A Z12 XIDOD DCT which is inefficient and adds 25 minutes of flight time to the more efficient weekend route.

USAF proposes that the weekend route allowed by above RAD restrictions DJL UM129 EPL UL47 GTQ G21 MAKOT Z818 SBN DCT be allowed also during the week.

USAF estimates that safety of flight will increase and it will also save €134,400 per year due to the decrease in flight time.


142.

Description: To replace existing 5LNC LAGOR

Objective:




Project Category:

5LNC

FRA

Originator(s):

EUROCONTROL ICAO

LAGOR is with double reservation in ICARD for Russian Federation and France.

Proposal for replacement by France is based on “Common criteria for replacement of duplicated 5LNCs” as point is used on single ATS route.


143.

Description: 1. To re-align existing ATS route J62 MKN - NITSA as RIPLI - NITSA. 2. To implement UJ62, FL245 - FL320.

Objective:

To further improve the ATS route network within Athinai FIR.


Project Group:

RFG SE

Project Category:

GRC

Originator(s):

GRC

To facilitate traffic entering Athinai FIR via REDRA with destination LGIR.

AARRNN VV--22001166 -- 22001199//2200


109 28 June 2016 Edition: 1.0

ATS Routes


144.

Description:

To implement the following bi-directional ATS routes: a. UN45 BIRSA - SUDIK - BINKO - RENRA - ROTAS - MONUV; b. UN47 RALAK - DIBAK - BINKO.

Objective:

To further improve ATS route network between Malta FIR and Hellas UIR.


Project Category:

ATS Routes

GRC MLT

Originator(s):

GRC MLT

ROTAS new FIR/UIR bundary point. Vertical Limits FL245 - FL460.


145.

Description: 1. To allow "Direct" flight planning options LARMA DCT IVGOR and

IVGOR DCT LARMA. 2. To implement bi-directional ATS route R235 IVGOR - BALIT.

Objective:

To further improve ATS route network between Warszawa FIR and Kaliningrad FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes

POL RUS SWE

Originator(s):

POL

IVGOR new point POL/RUS boundary.

Proposal ID : 85.033b / 22.042c Impl. Status: State(s) & Org. Comments:

146.

Description: 1. To allow "Direct" flight planning options PENOR DCT VADRU and

VADRU DCT PENOR. 2. To implement bi-directional ATS route R356 VADRU - BALIT.

Objective:

To further improve airspace options between Warszawa FIR and Kaliningrad FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes DCTs RAD

POL RUS SWE

Originator(s):

SWE

VADRU new point RUS/POL boundary.

Related proposals:

85.033a / 22.042a

Proposal ID : 70.018k / CE0014 Impl. Status: State(s) & Org. Comments:

147.

Description: To allow H24 "Direct" flight planning option BABKO DCT ALAMU.

Objective:

To further improve the ATS route network within the FAB CE area while providing additional shorter route options.


Project Group:

FAB CE

Project Category:

Night Routes

SVK

Originator(s):

FAB CE

Proposal ID : 70.019o / CE0055 Impl. Status: State(s) & Org. Comments:

AARRNN VV--22001166 -- 22001199//2200


110 28 June 2016 Edition: 1.0

148.

Description: To implement eastbound H24 DCT MAKAL - PITOK.

Objective:



Project Group:

FAB CE

Project Category:

DCTs RAD

SVK

Originator(s):

FAB CE

Night ATS route: 23.00h - 05.00h (22.00h - 04.00h).

Will be re-evaluated within FRA H24 in Bratislava FIR.


149.

Project Name: Free Route Airspace Bratislava - FRABRA Phase 1

Description: To allow "Direct" H24 DCT options in Bratislava ACC AoR above FL245.

Objective:

To further improve airspace organisation within Bratislava FIR.


Project Group:

FAB CE

Project Category:

Free Route Airspace

SVK

Originator(s):

SVK

ATS route network above FL245 will be withdrawn.

Related proposals:

88.020


150.

Project Name: Removal U prefix Bratislava FIR

Description: To remove "U" prefix for Upper ATS routes within Bratislava FIR,

FL245+.

Objective:

To simplify Air Traffic Management in Bratislava FIR.


Project Category:

Airspace Structure

SVK

Originator(s):

SVK

Related proposals:

75.041


151.

Description: The implementation of RNAV GNSS approaches for Gyumri/Shirak (UDSG) airport.

Objective:

To further improve airspace organisation within Yerevan FIR.

Implemented 26 MAY 2016

Project Group:

SG BLACK

Project Category:

Airspace Structure PBN

ARM

Originator(s):

ARM


152.

Description: 1. To change existing RAD restriction LBLT1001 by allowing point

TUDBU for overflights.


Project Group:

BGR TUR

Originator(s):

Currently TUDBU is used for DEP LTBA/LTFJ towards Bucuresti FIR while the overflights are allowed via VADEN.

AARRNN VV--22001166 -- 22001199//2200


111 28 June 2016 Edition: 1.0

2. To implement the following westbound ATS routes: a. N618 VADEN - BAKLO - GOL - ETIDA; b. T889 BAKLO - DEDIN.

3. To re-designate the following existing ATS routes: a. T268 GRN - NAVOD as T226; b. N618 NAVOD - MOPUG as T226.

4. To delete the following ATS route segments: a. N618 VADEN - NAVOD; b. T268 TUDBU - GRN; c. T889 VADEN - UPAMA.

5. To release RD T224.

6. To properly adapt "D" sector of Sofia ACC.

Objective:

To further improve the flight planning options and improve airsapce organization between Istanbul FIR and Sofia FIR.

RFG SE SG BLACK

Project Category:

RAD

EUROCONTROL


153.

Description:

To implement the following westbound ATS routes: a. T367 BAKLO - GOL; b. T368 BAKLO - DEDIN.

Objective:

To further improve ATS route network within Sofia FIR.


Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

BGR

Originator(s):

BGR

These ATS routes will be used for routeing scenarios for DEP LTBA/LTFJ during loaded periods allowing proper spacing with ARR LTBA/LTFJ.


154.

Description: To extend to H24 existing "Direct" flight planning option MAREM DCT ABUDO.

Objective:

To further improve the ATS route network while providing a shorter route option for traffic from Scandinavia to the Adriatic coast.


Project Category:

DCTs RAD

CZE

Originator(s):

IATA

This is the only missing link on H24 southbound options to Croatia via Czech Republic, Austria and Slovenia from Scandinavia.

Related proposals:

69.220a


155.

Description: To re-place VES VOR with 5LNC BAVTA at same position and re-align

existing 21 ATS routes.

Objective:

To enhance the airspace structure in line with NAV strategy.


Project Category:

Airspace Structure

DNK

Originator(s):

DNK


AARRNN VV--22001166 -- 22001199//2200


112 28 June 2016 Edition: 1.0

156.

Description: To re-designate existing ATS route UZ43 BIPET - ODEGI as UZ27.

Objective:

To rationalise the existing ATS route designators in Spain in order to further facilitate flight planning.


Project Category:

Route Redesignation

ESP

Originator(s):

EUROCONTROL

RDs will be published on 5 MAR 2015 but the RD is reserved in ICARD for Italy.


157.

Project Name: SID Truncation

Description: To truncate EGBB Southbound SIDs as follows:

a. CPT 5D and COWLY 3D Truncated at new waypoint ADMEX and become ADMEX 1D and use extended Y321 and L612 to get to CPT and COWLY respectively - new waypoint EMKUK at intersection of extended Y321 and L612;

b. DTY 4D Truncated at new point UNGAP and become UNGAP 1D and use P155 to get to BANTO and M189 to get to DTY.

Objective:

To reduce portion of flight plan route fuelled at SID Altitude.


Project Category:

Airspace Structure ATM System

GBR

Originator(s):

GBR


158.

Project Name: Unnamed Significant Point

Description: To remove the 2 (two) unnamed points on ATS route L10 published by

NOTAM.

Objective:

To further improve the ATS route promulgation in UK AIP.


Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


159.


Description: To add 5LNC IRKUN to L15/A30 to name unnamed significant point at

FIR boundary.

Objective:

To remove unnamed Lat/Long in the UK AIP and AIP France.


Project Category:

AIP ATS Routes

GBR FRA

Originator(s):

EUROCONTROL


160.

Project Name: Unnamed Significant Point

Description: To add new 5LNC BETPO to L/UL15 to remove unnamed sigficant point.


Project Category:

GBR

Originator(s):

EUROCONTROL

AARRNN VV--22001166 -- 22001199//2200


113 28 June 2016 Edition: 1.0

Objective:

To further improve the ATS route promulgation in UK AIP. AIP ATS Routes


161.

Project Name: Airspace Capacity

Description: a. To raise the DFL between S10/S11 over North Sea from FL315 to

FL335

b. To allows the following City Pair Level Caps to be raised from not above FL315 to not above FL335: Manchester Group,

EGCN/NH/NM/NO/NJ/NT/NV to/from EHAM/GG/HO/LW/TE,LFAV/QI/QO/QQ/QT via KOLAG / LAMSO / RAVLO EGCN/NH/NJ/NM/NO/NT/NV to EB**, EH**, EL**, EDDG/DK/DL/LE/LN/LP/LW/WE/WF /WI EBAW to EGNT/NV.

Objective:

To further improve City Pair level caps within UK.


Project Category:

ATC Sectors RAD Vertical FE

GBR

Originator(s):

MUAC GBR


162.

Description: To re-designate existing ATS route Y3 NUMPO - NIGIT as P2 (release of

Y3).

Objective:

To further simplify ATS route designation within London FIR/UIR and release RD.


Project Category:

Route Redesignation

GBR

Originator(s):

EUROCONTROL

Same ATS route segment with different RDs Y3 and UP2.


163.


Description:

To replace by 5LNCs in ENR 3.1 the "unnamed" significant points on ATS route Q41.

Objective:



Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL


164.


Description: To further ratioanlisation of base of ATS route N859 by removing 3 (three) unanmed Lat/Long points in UK AIP.

Objective:


Project Category:

AIP ATS Routes

GBR

Originator(s):

EUROCONTROL

AARRNN VV--22001166 -- 22001199//2200


114 28 June 2016 Edition: 1.0



165.

Description: To re-designate existing ATS route UQ863 PEROT - BEDOX as UQ856.

Objective:

To simplify route designation within Zagreb FIR.


Project Group:

RFG SE

Project Category:

Route Redesignation

HRV

Originator(s):

EUROCONTROL

Resolution of “Unforeseen” RD break reported by Jeppesen.

As part of Stage 3b of FRAW project Austria deleted UQ863 DIPSA - ERKIR replacing it by DCT.

Currently RD Q863 exists after ERKIR in Germany and with dead end as PEROT - BEDOX - DIPSA.

Currently RD Q856 exists as BEDOX - HOC via Slovenia, Austria, Germany and Switzerland.


166.

Project Name: D201 Bypass Route Phase 1

Description: To convert the existing ATS route M/UM17 STU - VATRY to CDR 1/3 and

establish flight plannable directs (DCTs) STU - LANPI (new point) - VATRY that will be avilable when M/UM17 is not available to go around Danger Area EG201A.

Objective:

To establish DCTs will be the first of three phases (Q63 will now be Phase 2) that will enable VATRY to be used when (U)M17 is not available.


Project Category:

ATS Routes

IRL GBR

Originator(s):

GBR IRL

Redevelopment of Danger Area D201 Complex to allow greater use of the existing airspace this summer requires existing route (U)M17 to become CDR between STU & VATRY.


167.

Description: 1. To implement southbound ATS route UN137 DOBAR - BITLA. 2. To withdraw ATS route L/UL616 KOGAT - VAROX. 3. To re-designate existing ATS route N/UN137 KOGAT - BITLA as

L/UL616.

Objective:

To further improve and simplify ATS route network within Skopje FIR.


Project Group:

RFG SE

Project Category:

ATS Routes Route Redesignation

MKD

Originator(s):

EUROCONTROL

FRA evaluation showed that H24 connection DOBAR - BITLA is attractive for the AOs. It exists as Night DCT between 22:00 - 04:00 which is not loaded.

VAROX is on common boundary Skopje FIR - Athinai FIR / Hellas UIR and not published in AIP Greece as well as continuation of ATS route L/UL616.


168. Description: To re-align existing helicopter route KY953 as GALTU - VAVAK - OMIDU.


NOR

Originator(s):

Realignment in order to harmonize with CTA.

AARRNN VV--22001166 -- 22001199//2200


115 28 June 2016 Edition: 1.0

Objective:

To further improve ATS route network within Norway FIR.

Project Category:

ATS Routes NOR


169.

Project Name: Removal U prefix Bucuresti FIR

Description: To remove the distinction between Upper and Lower ATS routes - "U" prefix within Bucuresti FIR.

Objective:

To simplify Air Traffic Management in Bucuresti FIR.


Project Group:

RFG SE SG BLACK

Project Category:

Airspace Structure

ROU

Originator(s):

EUROCONTROL

Current double designation of ATS route segments as T74/UP740 and T/UT4 / N/UN616 to be also considered for resolution.


170.

Description: To re-designate existing ATS route T1 AGMEL - ORA - SAT - RUMUK as M423 (release of T1).

Objective:

To rationalise the existing ATS route designators in Romania in order to further facilitate flight planning and release RDs.


Project Group:

RFG SE SG BLACK

Project Category:

Route Redesignation

ROU

Originator(s):

ROU


171.

Description: To implement eastbound ATS route Z317 MAVIT - EVRIK.

Objective:

To further improve ATS route network within Bucuresti FIR.


Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

ROU

Originator(s):

ROU


172.

Description: 1. To implement northbound ATS route T745 ARGES - EROMO -

VADIM. 2. To re-align existing ATS route P746 VADIM - LUGOL.

Objective:

To further improve ATS route network between Kyiv UIR, Bucuresti FIR and Warszawa FIR.


Project Group:

RFG SE SG BALTIC SG BLACK

Project Category:

ROU POL UKR

Originator(s):

UKR

Option will be used under conditions due to military areas with alternative routing along existing ATS routes to RUMUK.

EROMO will be new boundary point between Bucuresti FIR and Lviv FIR.

LUGOL - POLON in Warszawa FIR will be available as DCT as from begining of 2016.

AARRNN VV--22001166 -- 22001199//2200


116 28 June 2016 Edition: 1.0

ATS Routes


173.

Description: 1. To implement bi-directional ATS route L/UL851 ADINA - RIVOS. 2. To re-designate existing ATS route L/UL851 ADINA - CND - RIVOS

as L/UL5.

Objective:



Project Group:

SG BLACK

Project Category:

ATS Routes

ROU

Originator(s):

ROU


174.

Description: To re-designate existing ATS route UP184 SODGO - DEGET as UT139 (release of P184).

Objective:

To rationalise the existing ATS route designators in Romania in order to further facilitate flight planning and release RD.


Project Group:

RFG SE SG BLACK

Project Category:

Route Redesignation

ROU

Originator(s):

EUROCONTROL


175.

Description: To re-align existing ATS route L/UL852 KOMAN - POLUN - VAMON - SODGO as L852 KOMAN - POLUN - VAMON - DIRER.

Objective:



Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

ROU

Originator(s):

ROU


176.

Description: To implement westbound ATS route Z259 KSD - TEKVA - ESEBA.

Objective:

To further improve ATS route network within Sweden FIR for arrivals to ENGM (RWY 19).


Project Group:

SG BALTIC

Project Category:

ATS Routes CDRs

SWE NOR

Originator(s):

SWE EUROCONTROL

Both ATS routes CDR2 FL095 - FL285 / CDR1 FL285 - FL660.

Z259 / N623 double designator in segment TEKVA - ESEBA.


AARRNN VV--22001166 -- 22001199//2200


117 28 June 2016 Edition: 1.0

177.

Description: To withdraw the following existing waypoints: NENAD, SUDIM and DRVAR.

Objective:

To further simplify airspace organisation within Sarajevo FIR and release unnecessary waypoints.

Planned 23 JUN 2016

Project Group:

RFG SE

Project Category:

5LNC

BIH HRV

Originator(s):

EUROCONTROL

These points are crossings between lower and/or upper ATS routes allowing only illogic turns. There is no difference in lower or upper ATS route limits before and after these points and their existence is not operationally required.



178.

Project Name: Project Name: Nicosia Direct Route Airspace - Phase 1B

Description: To allow 6 (six) NIGHT "Direct" flight planning options above FL285.

Objective:


Planned 23 JUN 2016

Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

CYP

Originator(s):

CYP FAB BLUE MED



Related proposals:

71.088a

71.088b

86.056a

86.056c

86.056d

86.056e


179.

Description: To re-designate the existing ATS route Z/UZ713 OSN - SUVOX as Z/UZ718.

Objective:

To rationalise the existing ATS route designators within Germany in order to further facilitate flight planning and avoid duplicate RDs use.

Confirmed 23 JUN 2016

Project Category:

Route Redesignation

DEU

Originator(s):

EUROCONTROL


180.

Project Name: New Waypoint on T718 TRA - RIGVI

Description: To establish new waypoint ALINE on ATS route T718 between

Trasadingen VOR (TRA) and GATPI.


Project Category:

ATS Routes

DEU CHE FAB EC

Originator(s):

AARRNN VV--22001166 -- 22001199//2200


118 28 June 2016 Edition: 1.0

Objective:

To facilitate "direct to" instructions without the requirement for verbal coordination.

CHE FAB EC


181.

Description: 1. To allow new Direct flight planning option BOMBI DCT SIPVU and

change of flow restrictions for ARR ELLX, EBLG, EHBK (and others) via OKG (UL984) or UPALA (UL610).

2. To update the flow restrictions within EDUUERL sector.

Objective:

To improve flight efficiency within FABEC (higher FL, shortcut) by offering better profile (late descent) / new shorter routing and optimizing capacity for ERL sector.

Planned 23 JUN 2016

Project Category:

DCTs RAD

DEU

Originator(s):

DEU FAB EC


182.

Description: To replace existing 5LNC LEPES.

Objective:



Planned 23 JUN 2016

Project Category:

5LNC

ESP

Originator(s):

EUROCONTROL ICAO

LEPES does not belong in ICARD to ICAO EUR/NAT Region. It is NACC Region allocated point and requires further action by ICAO DM.

Proposal for replacement by Spain is based on “Common criteria for replacement of duplicated 5LNCs” as point is used as FIR boundary in Russian Federation.


183.

Project Name: NEFAB and DK/SE FAB Free Route Airspace - NEFRA Phase 1

Description: To implement H24 cross border Free Route Airspace between DK-SE FAB and NEFAB, except Norway, above FL285.

Objective:

To further improve the airspace structure between Finland FIR, Sweden FIR, Tallinn FIR, Riga FIR and Kobenhavn FIR.


Project Group:

FAB Denmark/Sweden FAB NEFAB SG BALTIC

Project Category:

Free Route Airspace

FIN EST LVA DNK SWE

Originator(s):

FAB NEFAB

NEFRA: North European Free Route Airspace (NEFAB plus DK/SE).

ATS routes will be kept. Norway plans to implement cross-border

Free Route Airspace spring 2017.

Related proposals:

67.046 / 16.024

69.064a / 16.035a

85.118


184.

Description: To allow proper flight planning options via RAD Appendix 5 for ARR UGTB via TISOT and DEP UGTB via DISKA.

Planned 23 JUN 2016

GEO

Originator(s):

These points will be allowed as Connecting Points until proper SIDs/STARs being designed.

AARRNN VV--22001166 -- 22001199//2200


119 28 June 2016 Edition: 1.0

Objective:

To further improve flight planning options for flights to/from UGTB.

Project Group:

RFG SE SG BLACK

Project Category:

RAD

EUROCONTROL By using current ATS route connections to existing SIDs and STARs penalization varies up to 70NM.

Currently design of SID/STAR is in progress.


185.

Project Name: Free Route Airspace Skopje

Description: To introduce H24 Free Route in Skopje ACC above FL245.

Objective:

To further improve airspace organisation within Skopje FIR.

Planned 23 JUN 2016

Project Group:

RFG SE

Project Category:

Free Route Airspace

MKD

Originator(s):

MKD

Free Route implementation depends on neighbouring States developments and requirements.

Full co-operation should be expected. ATS route network will remain.


186.

Project Name: FRA Like (DCT) Warsaw FIR - Phase 2

Description: To allow new 16 "Direct" (DCT) flight planning options within Warszawa

FIR: REGLI - DENKO, GRUDA - DEVEL, USTIL - OLILA, LENOV - GOVEN, LENOV - BADUP, BADUP - BINKA, RONEX - BINKA, ROLKA - DEVEL, ELPOL - ROLKA, PIXOR - AMTEK, SORIX - DIBED, KARTI - RILAB, RILAB - DIBED, ELPOL - LUGOL, LUGOL - BINKA, LUGOL - BABEN.

Objective:



Project Group:

SG BALTIC

Project Category:


POL

Originator(s):

POL

Related proposals:

76.052 / 23.029

78.028a

86.041 / 22.046


187.

Description: To implement westbound ATS route T926 TAVRO - REBLO for DEP UGTB.

Objective:

To further improve ATS route network within Yerevan FIR.

Confirmed 21 JUL 2016

Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

ARM GEO

Originator(s):

ARM GEO

Very beneficial for flights between Georgia and Iraq.

Saving in distance is around 105NM compare to current available option via NOLGA.


188. Project Name: S-WAFLE - South West Adaptation Flight Level Planned FRA

Phase 2: 5th layer in sectors L and R (FL385+).

AARRNN VV--22001166 -- 22001199//2200


120 28 June 2016 Edition: 1.0

Evolution Phase 1

Description:

To create an additional layer in Bordeaux ACC sectors L, R and P, Phase 1: 4th layer in sector P (FL365+).

Objective:

To further improve the airspace structure and increase capacity within Bordeaux ACC in order to meet traffic demand.

21 JUL 2016

Project Category:

ATC Sectors

Originator(s):

FRA

Related proposals:

84.018b


189.

Description: To replace existing 5LNC ROYAL as OKOMU.

Objective:


Planned 21 JUL 2016

Project Group:

RFG SE

Project Category:

5LNC

ITA

Originator(s):

EUROCONTROL ICAO


ROYAL is used 4 times worldwide and is created in ICARD for USA.

ICAO DM sent relevant message to ITA. Part of Torino procedures change.

Related proposals:

81.035


190.

Description: To re-design existing SID KRATO for DEP LWSK by extension to RAXAD and withdrawal of 5LNC KRATO.

Objective:

To further improve airspace organisation within Skopje FIR.

Planned 21 JUL 2016

Project Group:

RFG SE

Project Category:

5LNC Airspace Structure

MKD

Originator(s):

IACA EUROCONTROL

SID KRATO is designed (10 years ago) for DEP LWSK from RWY16.

Currently 5LNC KRATO is not part of the ATS route network in Skopje FIR and there is no further continuation of the SID.

Based also on current RAD RWY16 could be used for DEP LWSK to RAXAD only on dog-leg SID SINKO where the absolute straight flying distance is +17.4NM.

DCT KRATO - RAXAD (6NM) was introduced on 16 AUG 2011 by NOTAM and was inserted in RAD from 20 OCT 2011. Will be withdrawn following the introduction of new SID to RAXAD.

Related proposals:

74.008a


191. Project Name: FLOS

Description:

Planned 18 AUG 2016

DNK

Originator(s):

AARRNN VV--22001166 -- 22001199//2200


121 28 June 2016 Edition: 1.0

To swap the publication of “Table of cruising levels” in AIP Denmark, from ENR 1.3 to ENR 1.7 in accordance with Annex 15.

Objective:

To adapt the publication of the FLOS used within the airspace of Denmark.

Project Category:

AIP EUROCONTROL


192.

Description:

To change all CDR 1/2 within Danish FIR into CDR 1.

Objective:

To further harmonise the utilisation of the existing CDRs within ECAC airspace.

Planned 18 AUG 2016

Project Category:

CDRs

DNK

Originator(s):

DNK

Replecing former proposal 66.024

Related proposals:

88.017


193.

Description:

To implement the following eastbound CDRs: 1. Z191 LUMAS - NEVIX - NETUP - STP; 2. Z192 LUMAS - NEVIX - ROTIS - ADITA - STP; 3. Z193 DIVKO - SOSUR - OLNUL - NIVDA - PELOS; 4. Z194 DIVKO - SOSUR - OBLAD - NIVDA - PELOS.

Objective:

To further improve the alternative ATS routes when LFD54B or LFD54DA are active.

Planned 18 AUG 2016

Project Category:

CDRs

FRA

Originator(s):

FRA

Alternative routes for UM985 LUMAS - OBLAD - STP and UM731 FJR - TINOT - PELOS respectively.


194.

Project Name: City Pair Level cap

Description: To raise the City Pair Level Cap from FL270 to FL290 for traffic ex

Severn and Midlands Groups to EBBR.

Objective:

To further improve flight efficiency within UK.

Planned 18 AUG 2016

Project Category:

RAD Vertical FE

GBR

Originator(s):

GBR


195.

Description: 1. To implement eastbound ATS route T195 REGTO - INKIX. 2. To insert point INKIX 490556N 0210551E on ATS routes UN133 or

B/UB7. 3. To introduce new SID to REGTO for EPKT/KK.

Objective:

To further improve airspace organization and ATS route network

Planned 18 AUG 2016

Project Category:

Airspace Structure ATS Routes

POL SVK

Originator(s):

POL SVK

REGTO 492004N 204933E is new boundary point between Warszawa FIR and Bratislava FIR.

AARRNN VV--22001166 -- 22001199//2200


122 28 June 2016 Edition: 1.0

between Warszawa FIR and Bratislava FIR for DEP EPKT/KK.


196.


Description:

1. Phase 3: To adapt the remaining lower/upper vertical limits, expressed in FL, of ATS routes within Germany - change of IFR FL to VFR FL.

2. To withdraw flow restrictions from ENR 3.3 to avoid duplication with RAD related remarks.

Objective:


Planned 15 SEP 2016

Project Category:

AIP ATS Routes

DEU

Originator(s):

EUROCONTROL

Currently lower/upper limits are set either as FL80 or FL100 or FL200 or FL240 or FL250 etc.

Related proposals:

84.067a

84.067b


197.


Objective:


Planned 15 SEP 2016

Project Category:

5LNC

GBR

Originator(s):

EUROCONTROL ICAO



ICAO DM sent relevant message to GBR (DM24/01 MSG 14-034).


198.

Description: To replace existing 5LNC BISBO.

Objective:

a. To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT region;

b. To improve the aeronautical information provided; c. To be compliant with ICAO Annex 11.

Planned 15 SEP 2016

Project Category:

5LNC

GBR

Originator(s):

EUROCONTROL ICAO

BISBO is reserved in ICARD for France. Point is used in UK for military aerodrome

purpose at EGUN. Proposal for replacement is based on

“Common criteria for replacement of duplicated 5LNCs” as point is not reserved for UK.


199.

Project Name: SID truncation

Description: Truncation of EGSS BUZAD SID at new waypoint UTAVA and establish new ATS route Q75 BKY - UTAVA - BUZAD.

Objective:

To reduce the portion of the flight plannable route at 4000ft by circa 15 nm thereby reducing fuel uplift/burn.

Planned 15 SEP 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR

AARRNN VV--22001166 -- 22001199//2200


123 28 June 2016 Edition: 1.0


200.

Project Name: Airspace Rationalisation

Description:

To remove the Souther CTAs 2 & 3 by expanding Southern CTA 1 to include them and renaming of the airspace as Southern CTA.

Objective:

To remove anomalous airspace that can cause confusion as to teh classification of teh airspace beneath teh two anomalous areas.

Planned 15 SEP 2016

Project Category:

Airspace Structure

GBR

Originator(s):

GBR


201.


Description:

To allow the following "Direct" flight planning options: 1. GAPLI DCT TINAN; 2. TINAN DCT GIBSO DCT DVR.

Objective:

To further improve route efficiency within UK.

Planned 15 SEP 2016

Project Category:

DCTs RAD

GBR

Originator(s):

GBR


202.


Description:

1. To truncate the EGLL MID SIDs to new points UNBOB and UNVIK however the existing MID SIDs will remain published and available for aircraft that cannot meet the climb gradient required for the UNBOB & UNVIK SIDs (less than 5% of traffic).

2. To extend Y803 from MID to UNVIK to replace the portion of the MID SID and amend M185 to route MID - UNBOB - OCK to replace the portion of the MID SID.

3. To re-designate Y803 east of MID as L18 and remove the U from UL18 and transfer the amended route into ENR3.3 of the UK AIP

Objective:

To reduced fuel uplift as a result of a shortened SID for EGL deps via MID, rationalize route designation and be ICAO compliant.

Planned 15 SEP 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR


203.

Project Name: CDR Conversion

Description: To change the category of ATS route segment UL613 MOGLI - MAMAL from CDR1/3 to PERM.

Planned 15 SEP 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR

AARRNN VV--22001166 -- 22001199//2200


124 28 June 2016 Edition: 1.0

Objective:

To further improve ATS route network within London FIR.


204.


Description: Truncation of EGSS CPT SIDs to new way point NUGBO and extend

existing route M183 from BKY via NUGBO and SILVA to CPT.

Objective:

SID Truncation aimed at redcing flight plannable portion of flight at 4000ft by circa 30nm and therefore reduce fuel uplift/burn.

Planned 15 SEP 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR


205.

Project Name: Airspace Re-structuring

Description:

To establish the Strumble CTA between the western edge of N864 and the FIR Boundary to replace Class A airspace of L9, N546, M17 & P2 as well as the Class C airspace coincident with it up to FL245.

Objective:

To re-describe the structure of the airspace will facilitate the phased transfer of ATS Routes from ENR3.1/3.2 into ENR3.3 and the emoval of the U desigantor prefix where appropriate.

Planned 15 SEP 2016

Project Category:


GBR IRL

Originator(s):

GBR


206.

Project Name: D201 Bypass Route Phase 2

Description:

Conversion of existing ATS (U)M17 between STU and VATRY to CDR 1/3 and establish new bypass route CDR Q63 (with U removed) STU - LANPI (new point) - VATRY that will be avilable when (U)M17 is not available to go around new Danger Area EG D701F.

Objective:

Q63 will be the first of two bypass routes that will enable VATRY to be used when (U)M17 is not available.

Planned 15 SEP 2016

Project Category:

ATS Routes

GBR IRL

Originator(s):

GBR

Redevelopment of Danger Area EG D201 Comples to establish two new portions requires existing route (U)M17 to become CDR between STU & VATRY.


207. Project Name: Swanwick Contingency Route

Description:

Planned 15 SEP 2016

GBR

Originator(s):

Contingency Route

AARRNN VV--22001166 -- 22001199//2200


125 28 June 2016 Edition: 1.0

To establish a contingency route T999 BKY - SIVDA - OTBED FL155 -

FL195 only.

Objective:

Contingency Route to be only actiavted by NOTAM in the event og a significant outage/evacuation at Swanwick allowing limited operation of traffic from certain airports in the LTMA/Solent arae to specified airports in the north of the UK without entering Swanwick LAC airspace - transpfer of traffic from Swanwick TC to Prestwick Centre.

Project Category:

ATS Routes GBR


208.

Description: To replace existing 5LNC GANTO with EVDEG.

Objective:



Planned 15 SEP 2016

Project Category:

5LNC

GBR U.S.A.F.E

Originator(s):

EUROCONTROL ICAO

GANTO is reserved in ICARD for France / UK with existing coordinates. One record exists in ICARD which is not connected to UK as GANTO is not FIR boundary point.

Point is used in UK for military aerodrome purpose at EGUN.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for UK and cannot be used twice in same State.


209.

Description:

To re-designate the following existing ATS routes: 1. Y/UY76 REFSO - RIMBU - DET as Z/UZ291 (release of Y76); 2. L/UL26 OTBED - PENIL as L/UL60 (release of L26).

Objective:

To rationalise the existing ATS route designators within Netherland and UK in order to simplify the designation, release for further use and further facilitate the flight planning.

Planned 15 SEP 2016

Project Category:

Route Redesignation

NLD GBR MUAC

Originator(s):

EUROCONTROL GBR

Related proposals:

87.014b


210.

Description: To re-align existing TACAN ATS route TB1 as ... ORL - BASTU - FLE ...

and remove TB1E.

Objective:

To harmonize military traffic flows with available ground based navigational aids.

Planned 15 SEP 2016

Project Category:

ATS Routes

NOR

Originator(s):

NOR

TB1 / TB1E are TACAN routes only intended to be used by military aircraft during IFR operations above FL195.


AARRNN VV--22001166 -- 22001199//2200


126 28 June 2016 Edition: 1.0

211.

Description:

To allow northbound Night "Direct" flight planning option LUGOL DCT POLON.

Objective:

To further improve the flight planning options within Warszawa FIR.

Planned 15 SEP 2016

Project Group:

SG BALTIC

Project Category:

DCTs

POL

Originator(s):

UKR

Depending on update of PANSA internal flight plan validation and airspace management systems.


212.

Project Name: Prestwick ACC

Description: To introduce new operating system iTEC (interoperability Through European Collaboration) within Prestwick ACC.

Objective:

The iTEC project will introduce a Trajectory Based FDP and associated Controller Tools to the Prestwick Upper Airspace Sectors.

Proposed summer 2016

Project Category:

ATM System

GBR

Originator(s):

GBR


213.

Description: To allow the following Night “Direct” flight planning options for traffic type MIL: a. NAXAV DCT ROTAR; b. AIOSA DCT TIGRA.

Objective:

To further improve the flight planning options within Italy.


Project Category:

Civil/Military Airspace DCTs RAD

ITA

Originator(s):

U.S.A.F.E

The use of both DCTs is planned in combination with SEAFRA allowed option ROTAR DCT AIOSA.

The whole DCTs option NAXAV - ROTAR - AIOSA - TIGRA will reduce route distance by 31NM compared to current routing saving €1000 per flight.


214.

Description: To re-designate ATS route UZ16 POVEL - GALMA as UZ94.

Objective:

To rationalise the existing ATS route designators/ RDs within Germany in order to further facilitate flight planning and release RDs.

Planned 13 OCT 2016

Project Category:

Route Redesignation

DEU

Originator(s):

DEU

Related proposals:

86.052a


215.

Description: 1. To introduce new SID GISDI for Paderborn (EDLP) airport.

2. To implement the following westbound ATS routes for DEP EDLP: a. Y13 SONOR - GISDI - ALEXU - EDEGA; b. Y14 GISDI - NATSU.

Objective:

Planned 13 OCT 2016

Project Category:


DEU MUAC

Originator(s):

DEU

Airspace developments due to capacity problems in some of Langen ACC sectors.

The DEP traffic using these ATS routes will cross another sector and also get a significantly shortened routing.

AARRNN VV--22001166 -- 22001199//2200


127 28 June 2016 Edition: 1.0

To further imporve airspace organization within Germany.


216.

Description: To withdraw waypoint SEBER and re-align existing ATS routes UL126 and UL171 via waypoint BOGMU removing waypoint located with 1 sec

difference.

Objective:

To further simplify the ATS route network within Germany.

Planned 13 OCT 2016

Project Group:

FAB EC

Project Category:

ATS Routes

DEU MUAC FAB EC

Originator(s):

EUROCONTROL

As per JeppView coordinates of SEBER are 5358.75 01017.32 while of BOGMU 5358.75 01017.33.

The situation is at least like this since 2007, the only reason it popped up now is because of direction change on N850.

FABEC will be added as Project owners, as the changes in this area are influenced by former planning for CBA Land/CW.

Removal of SEBER will resolve worldwide 5LNC duplication with Canada.


217.

Description:

To Harmonise and adapt all CDRs at the interface between Hannover UIR / Kobenhavn FIR.

Objective:


Planned 13 OCT 2016

Project Category:

CDRs

DEU

Originator(s):

DEU

Replecing former proposal 66.024

Related proposals:

88.016


218.

Project Name: SAXFRA - Slovenian Austrian X-border Free Route Airspace

Description: To introduce H24/7 Cross Border Free Route Airspace as an airspace entity within AoRs of Austro Control (east of ROCKY Line) and Slovenia Control from GND to FL660.

Objective:

To further improve flight efficiency within AoRs of Austro Control (east of ROCKY Line) and Slovenia Control.

Planned 10 NOV 2016

Project Group:

FAB CE RFG SE

Project Category:

Free Route Airspace

AUT SVN

Originator(s):

AUT SVN

Phased implementation: FRAW Stage 1 - 18 OCT 2012. FRAW Stage 2 - 7 MAR 2013. FRAW Stage 3a/b - 6 MAR 2014 - 11 DEC

2014. FRAW Stage 4a/b - 2 APR 2015 - 10 DEC

2015. FRA Ljubljana Phase 1 - 6 MAR 2014 FRAW Stage 5 and FRA Ljubljana Phase 2

will be absorbed by SAXFRA. Cancellation of ATS routes in Wien FIR foreseen (except of Non RNAV ATS routes below FL095).

Related proposals:

76.047

77.066a

77.072a

AARRNN VV--22001166 -- 22001199//2200


128 28 June 2016 Edition: 1.0

77.072b

77.072c

77.072d

87.008


219.

Project Name: ATS routes / RAD update

Description:

To update German ATS routes at the German - Austrian interface and implement point based RAD restrictions (Austrian ATS routes will be deleted - SAXFRA).

Objective:

To support SAXFRA.

Planned 10 NOV 2016

Project Category:

ATS Routes RAD

DEU AUT

Originator(s):

DEU AUT

Related proposals:

87.001


220.

Project Name: EST - RUS airpsace changes

Description:

To implement new ATS routes and adapt the existing ATS route network within Tallinn FIR.

Objective:

To improve ATS route connections between Estonia and Russian Federation.

Planned 10 NOV 2016

Project Group:

SG BALTIC

Project Category:

ATS Routes

EST RUS LVA

Originator(s):

EST RUS


221.

Description:

To re-designate the following existing ATS routes: a. T12 MOROK - PENDU as L856 (same segment with different RDs

T12/UL856); b. T32 EPL - LASAT as N491 (same segment with different RDs

T32/UN491); c. UT40 TORPA - LUL as UM624 (extension); d. UT40 LUL - GIVOR as UT60.

Objective:

To rationalise the existing ATS route designators within French FIRs in order to further facilitate flight planning and resolve double RDs use in ICAO EUR Region.

Planned 10 NOV 2016

Project Category:

Route Redesignation

FRA

Originator(s):

EUROCONTROL


AARRNN VV--22001166 -- 22001199//2200


129 28 June 2016 Edition: 1.0

222.

Description:

To re-designate the following existing ATS routes: a. T16 MINPA - SAU as T616; b. UY105 TOKDO - LERGA as UY305; c. UZ39 BOLSA - SIJAN as UZ539; d. UZ131 OLRAK - FJR as UZ151.

Objective:

To rationalise the existing ATS route designators within French FIRs in order to further facilitate flight planning and resolve double RDs use in ICAO EUR Region.

Planned 10 NOV 2016

Project Category:

Route Redesignation

FRA

Originator(s):

EUROCONTROL


223.


Description: To adapt the upper vertical limit of ATS route Y560 ARMIX - ILB, by changing the IFR FL130 to VFR FL.

Objective:


Planned 10 NOV 2016

Project Group:

RFG SE

Project Category:

AIP

SVN

Originator(s):

EUROCONTROL


224.

Project Name: Free Route Airspace Ukraine, Step 1 (Sc 1b)

Description: To implement H24 Free Route Airspace operations above FL275

within individual UTAs in Ukraine.

Objective:

To implement FRA Concept and further improve flight efficiency within Kyiv UIR.

Planned 10 NOV 2016

Project Group:

RFG SE SG BLACK

Project Category:

Free Route Airspace

UKR

Originator(s):

UKR

Free Route Airspace Ukraine - FRAU project

Related proposals:

71.040a / 16.026a

81.018a / 19.021a

81.018b / 19.021b


225.

Project Name: Nicosia Direct Route Airspace - Phase 1C

Description: To allow 4 (four) NIGHT "Direct" flight planning options above FL285.

Objective:


Planned 08 DEC 2016

Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

CYP

Originator(s):

CYP FAB BLUE MED



Related proposals:

71.088a

71.088b

86.056a

AARRNN VV--22001166 -- 22001199//2200


130 28 June 2016 Edition: 1.0

86.056b

86.056d

86.056e


226.

Description: To allow “Direct” flight planning option WUR DCT TIPAM for DEP ETAR.

Objective:

To further improve the flight planning options within Germany.

Planned 08 DEC 2016

Project Category:

DCTs RAD

DEU

Originator(s):

U.S.A.F.E

The estimate by the USAF is save of €270K and 41K kilograms per year


227.

Project Name: FLOS

Description:

To publish in accordance with Annex 15 in AIP Germany, ENR 1.7 the relevant “Table of cruising levels” used within the airspace of Germany.

Objective:

To publish the FLOS used within the airspace of Germany.

Planned 08 DEC 2016

Project Category:

AIP

DEU

Originator(s):

EUROCONTROL

Currently the required “Table of cruising levels” is NOT published in AIP Germany as required by Annex 15. Germany is the only State in NM area without AIP reference to FLOS to be used.

ENR 3.3 - Note 1 contains explanation of arrows meaning and use of terms ODD/EVEN. ODD covers the altitude/flight levels starting with an odd number (e.g. FL70, FL90 …) while EVEN covers the altitude/flight levels starting with an even number (e.g. FL60, FL80 …).

As there is no ICAO explanation for terms ODD/EVEN the expression in AIP ENR 1.7 shall be based on Annex 2, Appendix 3 “Table of cruising levels”, a) including exact magnetic tracks applied as per table or Note represented as (***).


228.

Project Name: Night DCT Network

Description:

To implement a comprehensive Night DCT Network across both Geneva & Zurich ACC Areas of Responsibility, offering significant shortcuts during night.

Objective:

To offer significant shortcuts during night and gain experience with DCTs extending across AoR boundaries.

Planned 08 DEC 2016

Project Category:

DCTs Night Routes

DEU FRA CHE AUT FAB EC ITA

Originator(s):

CHE FAB EC

Redundant Night ATS Routes will be removed

Related proposals:

87.051

AARRNN VV--22001166 -- 22001199//2200


131 28 June 2016 Edition: 1.0


229.


Description:

To continue preparation of Full Free Route Airspace Germany by: 1. using of RAD Appendix 7 for ED-R308 (TRA); 2. lowering the MIN FL of some existing DCTs into AoR Munich ACC; 3. introducing first set of compulsory transition/connecting points for

ARR/DEP to/from some German airports; 4. publication of 4 lateral FRA cells as sub-airspaces within EDUU UIR

to support new RAD restriction/transition points/ transition routes; 5. if required introduction of first set of compulsory transition routes

linked to each transition point/connecting point.

Objective:

To support implementation of Full Free Route and simplify the RAD.

Planned 08 DEC 2016

Project Group:

FAB EC

Project Category:

ATS Routes Free Route Airspace RAD

DEU

Originator(s):

DEU FAB EC

Use of RAD Appendix 7 for TRA308 depending the experiences of usage RAD for ED-D47A/B (implemented AIRAC1513).

Related proposals:

87.005a

87.005c

87.005d

87.005e


230.

Project Name: M17 Off-load Route

Description: To establish alternative routing using Q65 and Q66 via new waypoints

when M17 STU - VATRY is closed by activity in D201A.

Objective:

Provide an alternative offload route to accommodate traffic when (U)M17 is closed by activity in D201A FL145+.

Planned 08 DEC 2016

Project Category:

ATS Routes

GBR IRL

Originator(s):

GBR

D201A is likely to be activated more often by NOTAM FL145+ and therefore this will close (U)M17 - to avoid a 40nm detour via WAL plan to establish new routes Q65/Q66 with only a 4nm detour. (U)M17 epected to be closed around 40 days per year for up to 4 hours per day.


231.


Description:

a. WCO 5D Delete SID and use UNGAP 1D/ADMEX 1D and DCTs to get to WCO.

b. WCO 1L Delete SID and use NEMKA 1E/GOXER 1Y and DCTs to get to WCO.

c. COWLY 1L Truncated at new waypoint GOXER and become GOXER 1Y and use L612 to get to COWLY.

d. CPT 1L Dellete SID and use GOXER 1Y via L612 and extended Y321 to get to CPT.

e. DTY 1L Truncated at new point XXXXX and use DCT to get to BANTO (P155) and L10 to get to DTY.

Objective:

To reduce the flight portion at SID altitude and associated redction in fuel

Planned 08 DEC 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR

Subject to prposed 2Y SIDs replacing current 1L SIDs from 26th May 2016.

AARRNN VV--22001166 -- 22001199//2200


132 28 June 2016 Edition: 1.0

uplift.


232.

Description: To re-designate existing ATS route N580 GOW - TIR as L602 (release of N580).

Objective:

To rationalise the existing ATS route designators within Scottish FIR in order to further facilitate flight planning and release RDs.

Planned 08 DEC 2016

Project Category:

Route Redesignation

GBR

Originator(s):

EUROCONTROL

Adaptation of RDs in lower and upper airspace.

Currently the ATS segment GOW - TIR is designated both as N580 and UL602.

RD N580 exists only along the GOW - TIR segment and by re-designation it can be released for use by other State/s.

This proposal reflects the ideal re-designation with use of only one RD - L/UL602 despite that presumably there will be a “RD break” of L602 between TLA - GOW.

Another possibility is to have two or three RDs on that segment by designating it as N572 and/or Y958 and UL602.


233.

Project Name: CDR Availability

Description: To extend the CDR 1 avilability of UY124 by one hour until 09:00 (08:00)

MON - FRI.

Objective:

To provide shorter route for Dublin departures via AMPIT, allow greater runway capacity at Dublin Airport and reduce complexity/enhance safety on the PC IoM Sector.

Planned 08 DEC 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR IRL

Needs agreement from UK MOD and USAFE.

Reciprocally the CDR2 avilablity is reduced by 1h.


234.

Project Name: ATS Route Accessibility Improvement

Description: To extend the availability of ATS route segment N864 WAL - DCS (FL195 - FL245) to H24.

Objective:

To reduce track mileage for traffic operating between FL200 and FL240 between WAL and DCS in both directions and reduce complexity on Sector 29.

Planned 08 DEC 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR

Below FL195 - FL155 remains only available weekends.


AARRNN VV--22001166 -- 22001199//2200


133 28 June 2016 Edition: 1.0

235.


Description: To implement westbound ATS route (CDR) TALGA - LANON.

Objective:

To further reduce track routeing.

Planned 08 DEC 2016

Project Category:

ATS Routes

GBR

Originator(s):

GBR

Related proposals:

85.114


236.

Project Name: Route Designator rationalisation

Description: To re-designate L15 LYD - IRKUN as M91.

Objective:

To facilitate removal of U from UL15.

Planned 08 DEC 2016

Project Category:

ATS Routes

GBR FRA

Originator(s):

GBR

This will not release L15 but will facilitate the eventual removal of the U designator prefix from UL15 and transfer into 3.3. re-designation is planned for December 2016 - removal of U will be summer 2017


237.

Project Name: Free Route Airspace Zagreb, Phase 5b - SEAFRA

Description: To introduce H24 Free Route Airspace in Zagreb ACC AoR above FL325.

Objective:

To further improve airspace organisation within Sarajevo FIR and Zagreb FIR.

Planned 08 DEC 2016

Project Group:

FAB CE RFG SE

Project Category:

Free Route Airspace

HRV BIH SRB

Originator(s):

HRV

In coordination with Free Route introduction in Beograd ACC.

FRA cross border application in Zagreb ACC and Beograd ACC AoRs.

Implementation depends on BH ATM, Phase 2 implementation.

RTS in Jan/Feb 2016.

Related proposals:

69.086a

74.016a

74.048a

74.048b

74.059b

75.013


238.

Project Name: FAIR-IT Free Route Airspace Italy, Phase 3

Description: To implement Full Free Route Airspace, initially above FL335.

Objective:

To further improve the airspace structure and the flight planning options within Milano, Roma and Brindisi UIR.

Planned 08 DEC 2016

Project Group:

FAB BLUE MED RFG SE

Project Category:

Free Route Airspace

ITA

Originator(s):

ITA

Co-operation inside BLUE MED with all the partners involved, to extend FAIR-IT at FAB level, starting from 2015.

Cross-border with Malta.

Related proposals:

71.085a

71.085b

71.085d

71.089c

AARRNN VV--22001166 -- 22001199//2200


134 28 June 2016 Edition: 1.0

88.021


239.

Project Name: Removal U prefix Milano, Roma and Brindisi UIR.

Description: To remove "U" prefix for Upper ATS routes within Milano, Roma and

Brindisi UIR, FL335+.

Objective:

To simplify Air Traffic Management within Milano, Roma and Brindisi UIR.

Planned 08 DEC 2016

Project Category:

Airspace Structure

ITA

Originator(s):

ITA

Related proposals:

71.085c


240.

Project Name: Free Route Airspace Vilnius - Phase 2

Description: To expand already implemented H24 Free Route Airspace FL245+ in Vilnius ACC down to FL095.

Objective:

To further improve airspace organisation within Vilnius FIR.

Planned 08 DEC 2016

Project Group:

SG BALTIC

Project Category:

Free Route Airspace

LTU

Originator(s):

LTU

Related proposals:

75.040a / 15.042a

76.052 / 23.029


241.

Project Name: Free Route Airspace Malta - Phase 3

Description: To implement H24 Free Route Airspace above FL335 within Malta UIR.

Objective:

To further improve the flight planning options within Malta UIR as a third step of Free Route Airspace Malta implementation.

Planned 08 DEC 2016

Project Group:

FAB BLUE MED

Project Category:

Free Route Airspace

MLT

Originator(s):

MLT

Co-operation/synchronisation with Free Route Airpsace Italy/ FAIR-IT, Phase 3.

Depending on new system implementation. Cross-border with Italy.

Related proposals:

71.085c

71.085d

71.089a

71.089b


242.

Project Name: Free Route Airspace Beograd, Phase 5b - SEAFRA

Description: To introduce H24 Free Route Airspace in Beograd ACC AoR above

FL325.

Objective:

To further improve airspace organisation within Sarajevo FIR and Beograd FIR.

Planned 08 DEC 2016

Project Group:

FAB CE RFG SE

Project Category:

Free Route

SRB MNE BIH HRV

Originator(s):

SRB

In coordination with Free Route introduction in Zagreb ACC.

FRA cross border application in Zagreb ACC and Beograd ACC AoRs.

Implementation depends on BH ATM, Phase 2 implementation.

RTS March 2016.

AARRNN VV--22001166 -- 22001199//2200


135 28 June 2016 Edition: 1.0

Airspace Related proposals:

69.086a

74.016a

74.016c

74.048a

74.048b

75.013

80.081


243.


Description: Phase 1 includes:

1. Change of en-route navigational requirements from RNP5 (B-RNAV) to PBN RNAV5 and RNAV routes adaptation;

2. Adjustment of coordinates in accordance with WGS84 Manual, Annex 15 and Doc 8168.

Objective:


Planned 08 DEC 2016

Project Group:

RFG SE

Project Category:

AIP

SRB MNE

Originator(s):

EUROCONTROL

Together with H24 Free Route Airspace implementation in Beograd ACC.

Related proposals:

74.059b


244.

Description:

To withdraw or replace VFR reporting points published as pronounceable 5LNCs in AIP Serbia / Montenegro, part AD 2, Chart for VFR flights.

Objective:

To align AIP publication in accordance with Annex 11.

Planned 08 DEC 2016

Project Group:

RFG SE

Project Category:

5LNC AIP

SRB MNE

Originator(s):

EUROCONTROL

More than 60 (sixty) VFR reporting points are designated as five-letter pronounceable name-codes (5LNCs). Most of them are reserved in ICARD and already used worldwide by other States.

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.


245.


Description:

To adapt the lower/upper vertical limits, expressed in FL, of ATS routes within Baku FIR - change of IFR FL to VFR FL.

Objective:

Proposed autumn 2016

Project Group:

SG BLACK

Project Category:

AZE

Originator(s):

EUROCONTROL

Currently lower/upper limits of upper ATS routes are set as FL200 - FL430 while for lower ATS routes upper limit is FL195 and lower varies as FL050, FL060,…FL150 etc.

Upper limits will be expanded till FL660.

AARRNN VV--22001166 -- 22001199//2200


136 28 June 2016 Edition: 1.0

To adapt in State AIP ATS routes vertical limits. AIP ATS Routes


246.

Description: To implement westbound ATS route RASAM - ADEKI for DEP UBBB.

Objective:

To further improve ATS route network within Baku FIR.


Project Group:

SG BLACK

Project Category:

ATS Routes

AZE

Originator(s):

EUROCONTROL


247.

Description: To implementation bi-directional ATS route L133 NETON - DISKA.

Objective:

To further improve ATS route network between Baku FIR and Tbilisi FIR.


Project Group:

SG BLACK

Project Category:

ATS Routes

AZE GEO

Originator(s):

EUROCONTROL

As agreed all changes inside Tbilisi FIR were implemented as from 3 MAR 2016.

Related proposals:

86.051a / 23.007a


248.

Description: To implement shorter ATS route option for DEP LROP/LRBS via Sofia

FIR towards Turkish airspace.

Objective:

To further improve ATS route options between Sofia FIR and Bucuresti FIR.


Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

BGR ROU

Originator(s):

EUROCONTROL

New point east of ARGES for DEP LROP/BS to ODERO.

Same point used for DEP LROP to RIXEN during Summer period (t.b.d.);

Use of RONBU for DEP LROP during Winter period (t.b.d.);

RAD: RONBU - RIXEN “Only available only for DEP LROP/BS”;

LOA: DEP LROP/BS initially climb FL150; Location of new point with regard to LRTSA

1C/1D, LRR34; Changes in LROP/LRCK TMA (new

departure routes, time); New SIDs from LROP/LRBS via OSTAL

planned by Romania; Implementation depends on UDROS /

ODERO reorganization.


249. Project Name: Night Free Route Sofia FIR - FRAS, Phase 2

Proposed BGR

Currently Night FRA is applicable FL245 -

AARRNN VV--22001166 -- 22001199//2200


137 28 June 2016 Edition: 1.0

Description:

Phase 2: To expand the FRAS by lowering the FL limit from FL245 to FL095, inclusion of ARR/DEP as part of FRA operations and introduction of new FRA points.

Objective:

To further improve the Free Route Airspace operations within Sofia FIR.

autumn 2016

Project Group:

FAB DANUBE RFG SE SG BLACK

Project Category:

Free Route Airspace

Originator(s):

BGR FL660 and flights ARR/DEP from airports located within LBSR FIR are not eligible for FRA operations and must be planned along the route network published in ENR 3.3 irrespective of the planned FL.

Related proposals:

76.014 / 16.009

83.010

Proposal ID : 81.002b / 20.043 Impl. Status: State(s) & Org. Comments:

250.

Project Name: ECAC States AIP en-route publication issues - Phase 2.

Description:

To resolve the spotted AIP ENR 3.3 publication issues - Phase 2.

Objective:



Project Group:

RFG SE SG BLACK

Project Category:

AIP

BGR

Originator(s):

EUROCONTROL

Further discussed at BULATSA / EUROCONTROL bi-lateral meeting in October 2013.

AIS Office prepares the relevant updates in accordance with ECAC States AIP en-route publication issues document.

Related proposals:

81.002a


251.

Description: To improve the use of existing point GODEK by:

a. revision of upper limit of ATS route N188 GODEK - OBLAK; b. allowance of DEP LBSF towards LI airspace; c. exclusion of OGOTA from L615 avoiding turn to DOLAP.

Objective:

To further improve ATS route network between Sofia FIR and Beograd FIR.


Project Group:

RFG SE

Project Category:


BGR SRB

Originator(s):

EUROCONTROL

Currently via DOLAP and normally continuing via UL615 (saving of 7.5NM per flight).

GODEK was initially established to allow one way DEP / ARR LBSF flow with NISVA but currently is used rarely by maximum one or two daily flights below FL145 as allowed after 30 APR 2015.


252.

Description: To implement new P-RNAV SIDs/STARs for Gorna Oryahovitsa (LBGO)

airport.

Objective:



Project Group:

RFG SE SG BLACK

Project Category:

Airspace Structure

BGR

Originator(s):

BGR


AARRNN VV--22001166 -- 22001199//2200


138 28 June 2016 Edition: 1.0

253.

Description:

To implement the following ATS routes: a. USTIL - AAAAA - BABUN bi-directional; b. SUPAK - USTIL eastbound; c. USTIL - BABKO westbound.

Objective:

To further improve ATS route network between Warszawa FIR, L'viv FIR and Minsk FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes

BLR POL UKR

Originator(s):

UKR

AAAAA will be new boundary point between Ukraine and Belarus.

Poland - further study required. Belarus further studies required taking into

account future changes of route network in Moscow area.


254.

Description: To implement westbound ATS route ASKIL - AAAAA - VI.

Objective:

To further improve ATS route network between L'viv FIR and Minsk FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes

BLR UKR

Originator(s):

UKR

AAAAA will be new boundary point between Ukraine and Belarus.

50MPCPE: Improving the flight efficiency of the city pair UUEE - LIRF.

BLR further studies required taking into account further changes of route network in Moscow area.


255.

Description: To implement southbound ATS route RATIN - DIBON - KOVUS.

Objective:

To further improve ATS route network between Minsk FIR and Lviv FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes

BLR UKR

Originator(s):

EUROCONTROL

BLR further studies required taking into account further changes of route network in Moscow area

The city pairs interested in this new option are CP41 UUEE - LIRF and CP45 UUDD - LYTV.

Current option for flights via AMIRI is longer by 7.4NM.


256.

Description:

To allow traffic from southern Italy and Malta to Stockholm and Northern Scandinavia via UL156 by deleting/amending RAD restrictions LK2190 / LK2070 / EP2041 / EP2081.

Objective:

To further improve the airspace utilisation at the interface between Czech Republic and Poland providing shorter route options.


Project Category:

RAD

CZE POL

Originator(s):

IATA

Despite that restrictions are coded as LK their existence is also connected to the neighbouring States requirements.

LK2190 restricts flights over LEDVA along UL156 only for arrivals to 4 (four) Polish and 3 (three) Czech airports.

LK2070 restricts flights on UL156 HLV - LUMOT only for arrivals to 3 (three) Polish airports and departures from 2 (two) Czech airports.

Saving is 16 NM compared to current available option via VEBAL - LITKU - JED.

AARRNN VV--22001166 -- 22001199//2200


139 28 June 2016 Edition: 1.0


257.

Project Name: RAD EPED5003

Description: To extend the availability of EPED5003 DCT LASIS - DIBED from

currently only Night to weekend (Friday 20.00 - Monday 06.00).

Objective:

To further improve the airspace utilisation at the interface between Germany and Poland.


Project Category:

RAD

DEU POL

Originator(s):

IATA

As of 28th June 2012 additional Night/ Weekend DCT’s are open by Free Route Airspace Maastricht/ FRAM, especially made for departure EHAM.

To make optimum use of these additional options by KLM the adjacent DCTs have to be open as well.

Germany ready to implement.


258.

Description: 1. To re-designate existing ATS route T53 ALS - TUDLO as T153. 2. To delete RD T53 from current double designaton of ATS route

segment P729 TUDLO - KOR.

Objective:

To rationalise the existing ATS route designators within Denmark in order to further facilitate flight planning and avoid duplicate RDs use.


Project Category:

Route Redesignation

DNK

Originator(s):

EUROCONTROL


259.

Description: To reconsider the RAD restriction LILF1019 according to the criterion of

flexibility in order to cancel the RAD restriction during some specific periods/days/hours.

Objective:

To improve the FE of the CP LIRF - LEMD.


Project Group:

50 MPCPEs

Project Category:

RAD

FRA ITA

Originator(s):

EUROCONTROL FRA

Proposal supported by Marseille FMP. With origin in LE2001 restriction to be

managed in an interface Barcelona ACC-Marseille ACC.

Not acceptable by Italy - confirmed again at RAD review NOV 2013.

Proposal ID : 80.010h Impl. Status: State(s) & Org. Comments:

260.


Description: To re-designate the following existing Helicopter routes: KZ35, KZ40, KZ45, KZ46, KZ50.

Objective:



Project Category:


GBR NLD

Originator(s):

EUROCONTROL

All RDs are not in accordance with Annex 11 and not coordinated via ICARD.

In AIP UK Helicopter routes are not published in ENR 3.4 as required by Annex 15. It is stated that these routes appear in AD 2, ENR 1.15 and ENR 6 but the information there is not sufficient and complete.


261. Description:

1. To implement unidirectional ATS route system between Ankara FIR Proposed autumn 2016

GEO TUR

Outcome of the Second Meeting of the Ad Hoc Afghanistan Contingency Group

AARRNN VV--22001166 -- 22001199//2200


140 28 June 2016 Edition: 1.0

and Tbilisi FIR; 2. To change existing bi-directional ATS route N644 to eastbound;

3. To implement new westbound ATS route parallel to N644.

Objective:

To further improve the ATS route network between Ankara FIR and Tbilisi FIR.

Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

Originator(s):

TUR (AHACG/2) held at Istanbul, Turkey from 17 to 19 November 2014.

The purpose of this reorganization is to enable an efficient traffic flow in the region.

Additionally a reduced ATS surveillance-based longitudinal spacing from 20NM to10NM after the implementation of OLDI is also considered.


262.

Description: To insert waypoint ALIKA also on ATS route N77 BANUT - IBERI.

Objective:

To further improve connectivity between lower and upper ATS routes.


Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

GEO

Originator(s):

EUROCONTROL

ALIKA is SID/STAR point for UGKO. Point exists only on ATS route A277 (below

FL195) but not on N77 (above FL195). Theoretically due to missing connection all

ARR/DEP UGKO shall fly below FL195 from/till BANUT.


263.

Project Name: Santorini - LGSR Instrument Procedures

Description:

To implement new Instrument Approach Procedures, SIDs, STARs from/to Santorini aerodrome (LGSR).

Objective:

To further improve airspace organisation within ATHINAI FIR.


Project Group:

RFG SE

Project Category:

Airspace Structure

GRC

Originator(s):

GRC

Related proposals:

81.086


264.

Project Name: Borealis FRA - Step 2

Description:

To implement FRA for flights departing/arriving within Reykjavik FIR via Bodø FIR and Norway FIR.

Objective:

To further improve the airspace structure and the flight planning options within Borealis FRA Area States.


Project Group:

FAB Denmark/Sweden FAB NEFAB FAB UK/Ireland RFG NW

Project Category:

Free Route Airspace

ISL NOR

Originator(s):

FAB Denmark/Sweden FAB NEFAB FAB UK/Ireland ISL

These flights will be able to fly direct tracks via defined TMA/airport entry/exit points in Reykjavik FIR and the NAT oceanic control area boundary.

The oceanic boundary waypoint will be in LAT/LONG degrees and minutes or 5LNC (in compliance with current IFPS requirements).

Related proposals:

87.028a

87.028c

87.028d

87.028e

AARRNN VV--22001166 -- 22001199//2200


141 28 June 2016 Edition: 1.0

87.028f

87.028g


265.

Description: To withdraw the following existing waypoints: KORIV, TUXOV, UPERO and VAROX.

Objective:

To further simplify airspace organisation within Skopje FIR and release unnecessary waypoints.


Project Group:

RFG SE

Project Category:

5LNC

MKD

Originator(s):

EUROCONTROL

All points are currently published in AIP, ENR 4.3.

KORIV is reserved in ICARD for MKD. TUXOV and UPERO are on common

boundary Skopje FIR / Beograd FIR and not published in AIP Serbia / Montenegro. In ICARD TUXOV is free for use by other States while UPERO is reserved only for MKD.

VAROX is on common boundary Skopje FIR - Athinai FIR / Hellas UIR and not published in AIP Greece as well as continuation of ATS route L/UL616. Contrary to that in ICARD VAROX is reserved only for GRC.

Existing airspace organization within South East Europe shows that existence of these waypoints is not operationally required.



266.


Description:

To adapt existing ATS routes definition and template in AIP, ENR 3 in accordance with Annex 15.

Objective:



Project Category:

AIP

MKD

Originator(s):

EUROCONTROL


267.

Description:

To publish in accordance with Annex 15 in AIP Norway, ENR 1.7 the relevant “Table of cruising levels”.

Objective:

To adapt the publication of the FLOS used within the airspace of Norway.


Project Category:

AIP

NOR

Originator(s):

EUROCONTROL

Currently it is stated that “Flight levels shall be selected so as to meet the requirements established regarding minimum terrain clearance and in addition correspond to the table of cruising levels in BSL F 1-1,

AARRNN VV--22001166 -- 22001199//2200


142 28 June 2016 Edition: 1.0

vedlegg III (Annex 2, Appendix 3 REF).” AIP ENR 1.7 shall include the “Table of

cruising levels” with exact reference of magnetic tracks applied. The reference Annex 2, Appendix 3 is not sufficient as there are 4 (four) tables possible and magnetic tracks might either be as per tables there 000° - 179° / 180° - 359° or as per Notes *** 090° - 269° / 270° - 089°.


268.

Description: To allow "Direct" flight planning option on segment ETRUS - GORPI - CHO - GOVEN during Night.

Objective:

To further improve flight planning options within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

DCTs

POL

Originator(s):

IATA

ATS route not accepted by Poland due to workload of ACC Sector Drezdenko and postponed until introduction of the vertical split in Warszawa FIR.

Related proposals:

62.028b / 20.044b


269.

Description:

To allow the following NIGHT "Direct" flight planning options: a. LENOV DCT BABEN or LENOV DCT VIBUL; b. REGLI DCT BURAN; c. XELOL DCT LENOV or ELPOL DCT LENOV.

Objective:

To further improve flight planning options within Warszawa FIR and Sweden UIR.


Project Group:

SG BALTIC

Project Category:

DCTs

POL SWE

Originator(s):

IATA

Saving for city pair LTAI - EKCH is 9NM compared to LENOV UN133 LDZ UM70 BABEN UL617 KOLOB.

Saving for city pair LYTV - ESSA is 15NM compared to SOPAV UL617 RONEX UL733 BURAN.

Depends on implementation of vertical split in Warszawa ACC sectors.

As an intermediate step, XELOL-LENOV, ELPOL-LENOV and LENOV-RONEX published as a night DCTs.

Related proposals:

75.048b


270.

Description: To allow "Direct" flight planning options PODAN DCT GITOV and GITOV DCT PODAN.

Objective:

To further imporve flight planning options within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

DCTs

POL RUS

Originator(s):

POL

As GITOV is boundary point with RUS the change might have an impact on traffic flows in that region.

AARRNN VV--22001166 -- 22001199//2200


143 28 June 2016 Edition: 1.0

RAD


271.

Description: To expand the NIGHT "Direct" flight planning option ENOBI DCT SUI to H24.

Objective:

To further improve flight planning option within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

DCTs RAD

POL

Originator(s):

BLR

All other options exist or will be allowed by 10 DEC 2015.


272.

Project Name: Removal U prefix Lisbon FIR

Description:

To remove the distinction between Upper and Lower ATS routes - "U" prefix within Lisbon FIR.

Objective:

To simplify Air Traffic Management in Lisbon FIR.


Project Category:

ATS Routes

PRT

Originator(s):

PRT

"U" prefix removal for all routes below FRAL is under consideration.

Further adaptation of lower and upper ATS routes might be required.


273.

Description:

To re-designate the following ATS routes: 1. Y101 ODEMI - USALU as new Y; 2. Y102 XAPAS - USALU as new Y; 3. Y103 VFA - GIMAL as new Y; 4. Y105 ERTIS - GENRO as new Y; 5. Y207 FTM - LIS - EKMAR as new Y; 6. UZ4 BAROK - ESP as new Z; 7. UZ5 PIREN - ESP as new Z; 8. Z11 DEGUN - VERAM as new Z; 9. Z14 NARTA - LIDRO as new Z; 10. Z15 BABEX - OTPAK as new Z; 11. UZ21 BUSEN - GUNTI as new Z; 12. UZ28 DIRMA - BANAL as new Z; 13. UZ29 DIRMA - ARMED as new Z; 14. UZ220 ABALO - NIDUL as new Z; 15. Z226 INBOM - PRT as new Z; 16. UH80 ASPOR - PRT as T7 or T326 or T328; 17. W/UW106 RALUS - MOSEN as Z/UZ406.

Objective:


Project Category:

Route Redesignation

PRT

Originator(s):

EUROCONTROL

Requirement is due to duplicate use in different parts of the ICAO EUR/NAT region of route designators.

AARRNN VV--22001166 -- 22001199//2200


144 28 June 2016 Edition: 1.0

To further simplify the existing RDs within Portugal and avoid duplication in ICAO EUR/NAT Region.


274.

Description: To enlarge AoR of the existing Cluj APP.

Objective:

To further improve the airspace organisation within Bucuresti FIR.


Project Group:

RFG SE SG BLACK

Project Category:


ROU

Originator(s):

ROU

The implementation of the new Terminal Area, NAPOC TMA for LRCL, LRTM and LRSB includes: vertical limits 3000 ft up to FL175; class C airspace; the three CTRs defined as rectangles, GND

up to 3000 ft ALT, class of airspace C; common transition altitude (including for

MCTR LRCT) 7000 ft; 121 standard and P-RNAV SIDs and

STARs for LRCL, LRTM and LRSB; realigned military areas; 44 DCTs to allow overflights.


275.

Project Name: RAXAD and MAKED dualisation

Description: To dualise the existing points RAXAD and MAKED as follows: a. VAGEN - TUTUN - SKJ bidirectional; b. TUTUN - PEP southbound; c. TUTUN - TALAS southbound; d. TUTUN - ERANA southbound (TUTUN - ERANA is parallel with the

existing UL617 and will be used for ARR LGTS/LGKV).

Objective:

To further improve the ATS route network between Beograd FIR/UIR and Skopje FIR while reducing workload and increasing safety and efficiency.


Project Group:

RFG SE

Project Category:

ATS Routes

SRB MKD

Originator(s):

EUROCONTROL MKD

Point TUTUN 421743N 0220104E will be new TCP between Skopje ACC and Beograd ACC, 10NM west of RAXAD.

Further dualisation north of VAGEN could also be considered.

Related proposals:

64.005


276.

Description: To implement bi-directional / westbound ATS route T/UT422 CAY -

ROKVA - ODMAX.

Objective:

To further improve ATS route options for ARR/DEP LTAS (Zonguldak) airport.


Project Group:

RFG SE SG BLACK

Project Category:

ATS Routes

TUR

Originator(s):

TUR

AARRNN VV--22001166 -- 22001199//2200


145 28 June 2016 Edition: 1.0


277.


Description:

To adapt the lower/upper vertical limits, expressed in FL, of ATS routes within Kyiv UIR - change of IFR FL to VFR FL.

Objective:



Project Group:

SG BLACK

Project Category:

AIP ATS Routes

UKR

Originator(s):

EUROCONTROL

Currently upper limit of lower ATS routes is set as FL270 while lower limit of upper ATS routes is set as FL280.


278.

Project Name: CDO Munich - EDDM airport

Description: To implement new CDO approaches (STARs) at Munich/ EDDM airport.

Objective:

To further improve the ATS route network and flight efficiency within Munich FIR.

Planned 02 FEB 2017

Project Category:

ATS Routes Vertical FE

DEU ITA

Originator(s):

DEU

Trial 13.10.2013 till 31.12.2014 was extended till 31.12.2015: o ATC München, Sectors NDG/WLD,

EGG/RDG und APP North, from 16.10.2014 STA und APPS, from 13.11.2014 LOVV.

o CDO STA coming from Padua (16. Oct. 2014).

o CDO NAPSA coming from Vienna (13. Nov. 2014).

March '16: preparations ongoing for CDO from South via Padua ACC (via point ANDEC).

End of April '16: Bilateral meeting Munich ACC – Padua.

CDOs from Austria via NAPSA currently on hold.


279.

Project Name: Free Route Airspace Georgia - FRAG Phase 1

Description: To implement H24 Free Route Airspace FL255 - FL660 in Tbilisi CTA.

Objective:

To further improve airspace organisation within Tbilisi FIR.

Planned 02 FEB 2017

Project Group:

SG BLACK

Project Category:

Free Route Airspace

GEO

Originator(s):

GEO

Related proposals:

85.009b / 21.023b


280. Project Name: ATS Route Improvement

Description:

Planned 02 MAR 2017

GBR

Originator(s):

AARRNN VV--22001166 -- 22001199//2200


146 28 June 2016 Edition: 1.0

To re-align existing ATS route P137 as SIVDA - REDFA and removal of U

from RD UP137.

Objective:

To reduce track mileage by 2.2NM and reflects what is tactically provided on a routeine basis by controllers.

Project Category:

ATS Routes GBR


281.

Description: To allow DEP UGTB via DISKA.

Objective:

To further improve ATS route or flight planning options for traffic UGTB - UBBB.

Proposed winter 2016/17

Project Group:

SG BLACK

Project Category:

ATS Routes DCTs RAD

AZE GEO

Originator(s):

EUROCONTROL

Aside of airspace design solution - SID DISKA allowance of DCT as per Doc 4444 is also possible via RAD Appendix 5.

Saving for city pair UGTB - UBBB is around 60NM.

Further discussions on allowance of ADEKI for city pair UGTB - UBBB shall be considered by both States.


282.

Project Name: EVIVI dualisation

Description: To re-organize the existing ATS routes in the EVIVI area.

Objective:

To further improve ATS route network between Sofia FIR and Athens FIR/Hellas UIR.


Project Group:

RFG SE

Project Category:

ATS Routes

BGR GRC

Originator(s):

GRC

Request by Greece for a new exit point towards Bulgaria.

Bi-lateral meeting required to consolidate a common proposal.

Related proposals:

75.010

Proposal ID : 75.010 / DU0089 Impl. Status: State(s) & Org. Comments:

283.

Description: a. To implement southbound ATS route M/UM748 GOL - LMO. b. To adapt Sofia ACC sectors C / D boundary.

Objective:

To further improve airspace organisation between Sofia FIR and Hellas UIR.


Project Group:

FAB DANUBE RFG SE

Project Category:

ATC Sectors ATS Routes

BGR GRC

Originator(s):

BGR GRC

Related proposals:

77.065


284.


Description:

To publish RNAV routes in ENR 3.3 in accordance with Annex 15.

Objective:


Project Category:

AIP

BIH

Originator(s):

EUROCONTROL

Part of proposed actions in AIP adaptation.

AARRNN VV--22001166 -- 22001199//2200


147 28 June 2016 Edition: 1.0



285.

Description: To allow “Daily” flight planning option VEBAL DCT OSLUD DCT AKIKA

for ARR BKPR / LYPR.

Objective:

To further improve flight planning options within Zagreb FIR, Sarajevo FIR and Beograd FIR.


Project Group:

RFG SE

Project Category:

DCTs RAD

BIH HRV MNE SRB

Originator(s):

IATA EUROCONTROL

Availability required outside of SEAFRA operational hours 05:00 - 23:00 (04:00 - 22:00).

Routing is 28NM shorter than currently used routing via KOMAR.


286.

Description: To replace existing 5LNC GOGOL with KOVIM.

Objective:




Project Category:

5LNC

CHE

Originator(s):

EUROCONTROL ICAO

GOGOL is reserved in ICARD for Armenia. Proposal for replacement is based on

“Common criteria for replacement of duplicated 5LNCs” as point GOGOL is not reserved for Switzerland.


287.


Description:

To adapt the lower vertical limits, expressed in FL, of ATS routes within Nicosia FIR - change of IFR FL to VFR FL.

Objective:



Project Group:

RFG SE

Project Category:

AIP ATS Routes

CYP

Originator(s):

EUROCONTROL

Currently lower limit is set as either FL100 or FL110 or FL250 or FL260.


288.


Description:

To adapt in AIP Czech Republic ENR 3.3, ATS route vertical limits (FL235 or FL245) for direction distinction.

Objective:

To align AIP publication in accordance with ERNIP Part 1.


Project Category:

AIP ATS Routes

CZE

Originator(s):

EUROCONTROL

Currently following a removal of “U” prefix some ATS routes (M725, M748, P27, etc.) are used as bi-directional below established FL.

AIP Czech Republic states that different direction is applicable “FL240 below”.

Normally this FL expression shall be with VFR FL - FL235 or FL245.

AARRNN VV--22001166 -- 22001199//2200


148 28 June 2016 Edition: 1.0


289.


Description: To re-designate the following existing Helicopter routes: KZ10, KZ15.

Objective:



Project Group:

RFG NW

Project Category:


DNK NLD

Originator(s):

EUROCONTROL



290.

Project Name: Lisbon / Casablanca / Canarias Axis

Description:

To review the airspace organisation on the Lisbon / Casablanca / Canarias axis: a. to optimise the ATS route network in line with the new Canarias

TMA organisation; b. PRNAV structure for Canarias TMA, Phase 2 (includes Casablanca

/ Canarias interface); c. to create an ATS route segment from Fuerteventura (GCFV) and

Lanzarote (GCRR) to NAVIX and vice versa; d. to create new STAR ORTIS and SID BIMBO for GCFV and GCRR

airports.

Objective:

To further improve the ATS route network and airspace organisation within Canarias FIR/UIR.


Project Group:

RFG SW

Project Category:


ESP PRT MAR

Originator(s):

ESP PRT MAR

ONDA Morocco and NAV Portugal ready. Tri-lateral meeting required.

Related proposals:

60.034b

73.052

75.022

79.021


291.

Description: To implement new SID MEROS and/or CHELY from LEPA

Objective:

To provide AOs with additional and more efficient options for traffic departing from LEPA and proceeding north-eastbound


Project Category:

TMA

ESP

Originator(s):

EUROCONTROL IACA

The new SID would be 7 NM shorter than the current one and it could be used by a significant amount of flights and City Pairs (138 flights, 58 City Pairs, on 29 June 2012)

Related proposals:

76.003


292.

Project Name: LUMAS, Phase 2

Description: To implement northbound ATS route P/UP9 MEROS - DIBER.


Project Category:

ESP

Originator(s):

ESP

This proposal will be considered for integration as a part of the development.

Related proposals:

AARRNN VV--22001166 -- 22001199//2200


149 28 June 2016 Edition: 1.0

Objective:

To further improve ATS route network in DIBER / LUMAS area of Barcelona FIR.

ATS Routes 66.053b

66.053d

66.053e


293.

Project Name: LUMAS, Phase 2b

Description:

To re-organise the ATS route network at the interface between Spain and France, around LF-D54 military zone and to reconsider the traffic distribution of overflying currently points DIBER or LUMAS.

1. To implement a 3 point interface network structure for flights from Barcelona to Marseille ACC instead of current 2 points interface (DIBER / LUMAS).

Objective:

To further improve the ATS route network and airspace structure and to enhance sector capacity at the interface between Marseille ACC and Barcelona ACC.


Project Group:

RFG SW

Project Category:

Airspace Structure ATC Sectors ATS Routes

ESP FRA

Originator(s):

ESP FRA

Introduction of the new structure shall be without impact of the LF-D54 South that remains AMC non-manageable. Proposal is under study following the LECB-LFMM Interface Meeting No.2 held 15-16 OCT 2014.

Related proposals:

66.053d

75.023


294.

Description:

To publish in AIP Estonia and AIP Latvia ENR 5.2 TSA2 and TSA8 as CBAs and harmonize their way of activation.

Objective:

To align AIP publication in accordance with ERNIP Part 3.


Project Group:

SG BALTIC

Project Category:

AIP Airspace Structure

EST LVA

Originator(s):

EUROCONTROL

Both areas are located across Tallinn FIR / Riga FIR boundary but are published as TSAs.

In AIP Estonia ENR 5.2 all TSAs are coded in accordance with ERNIP, Part 3 as EETSA except TSA2 and TSA8 where nationality letters for location indicator “EE” are missing. The same is published in ENR TRA (apparently this shall be ENR 6.1).

In AIP Latvia ENR 5.2 none of the TSAs are coded in accordance with ERNIP, Part 3 as nationality letters for location indicator “EV” are missing and there are undesired spaces. Both TSA 2 and TSA 8 are published but only for TSA 8 is stated in Column “Remark” “CBA in the Tallinn and Riga FIR”. In ENR 6.1 again “EV” is missing and only TSA 8 is indicated as TSA 8 (CBA).

Additional discrepancy spotted for TSA2 and TSA8 is the way of activation where in AIP Estonia is stated “NOTAM on the day

AARRNN VV--22001166 -- 22001199//2200


150 28 June 2016 Edition: 1.0

before OPS” while in AIP Latvia - “AMC manageable” and “Real-time activity information from Riga ATC Centre”.


295.

Description:

To extend the time availability during summer period of existing night ATS route UQ236 PIBAT - MEDIL.

Objective:

To further improve the availability of night options within France.


Project Category:

Night Routes

FRA

Originator(s):

IATA

Outcome of West Europe RAD Review 30th - 31st May 2013.

This ATS route currently is available only during nights 22.00 - 05.00 (23.00 - 04.00).

Time availability in winter period is 7 hours while in summer only 5 hours.


296.

Project Name: Realign P18

Description: To realign P18 from STAFA - TELBA to STAFA - VIDOK.

Objective:

To reduce flight plannable mileage for EGGP NANTI departures and Manchester LISTO 1Y/1R departures by 2.5NM per flight (will increase flight plannable mileage for some Manchester HON 1Y/1R by 2.5NM). Actual mileage in both cases will remain unchanged from today. Will facilitate correct positioning for transferring to next sector under aircraft's own navigation rather than being transferred on assigned headings.


Project Category:

ATS Routes

GBR

Originator(s):

GBR

Allows for correct positioning via RAD restrictions for all MTMA departures. Dependent on HON SID truncation.


297.

Description: To consider possible 5LNC removal from one of the ATS routes of the

crossing waypoints published on both ATS routes: a. OKAMA - L/UL602 / UM604; b. TOLSA - L/UL602 / UN866; c. KUBAX - UY70 / UN866; d. BEKMO - UY70 / UM604.

Objective:

To simplify the ATS route network within London FIR/UIR and Scottish FIR/UIR.


Project Category:

5LNC ATS Routes

GBR

Originator(s):

EUROCONTROL

Two of these 5LNCs are crossings of upper unidirectional ATS routes and do not have connections with lower airspace unless allowed via DCT filling. The other two are also part of lower ATS routes.

Most of the possible undesired, even illogic, turns are not acceptable by the ACCs and unavailable by RAD restrictions.

Waypoints might continue to stay as crossings but published on only one of the ATS routes which will not allow undesired turns and RAD restrictions will be withdrawn.

Possible 5LNC removal from one of the ATS routes should also be considered in

AARRNN VV--22001166 -- 22001199//2200


151 28 June 2016 Edition: 1.0

view of ATC procedures and usage in case of vectoring and resuming navigation to the relevant ATS route or waypoint.

Currently all crossing points part of UK ATS route network are under consideration by NATS.


298.


Description: To implement westbound ATS route SOVAT - CPT.

Objective:

To further reduce track mileage.


Project Category:

ATS Routes

GBR FRA

Originator(s):

GBR

Will be available only for traffic at FL360 and above overflying the UK FIR and not for Paris TMA departures or for traffic cruising FL350 and below nor landing in the UK FIR.

Related proposals:

85.115


299.

Project Name: Newcastle STAR & RNAV Approach Project

Description:

1. To establish STARs for arrivals into Newcastle (EGNT) airport via POL.

2. To establish northbound ATS route P19 POL - XXXXX to provide

connectivity to start of STAR from XXXXX to ZZZZZ via YYYYY.

Objective:

Establish STARs to EGNT to help reduce controller and pilot workload


Project Category:

ATS Routes

GBR

Originator(s):

GBR

Newcastle STAR & RNAV Approach Project


300.

Description: To implement, as CDR 1, bidirectional ATS route segment KARNO - POL (Phase 2).

Objective:

To further improve the ATS route network within London FIR/UIR.


Project Group:

RFG SW

Project Category:

ATS Routes

GBR

Originator(s):

GBR

FL300 and above only. Provide connectivity to/from UL180 and

UP16. Review greater use below FL300 post

implementation. BERUL - MERLY original proposal by IACA.

Related proposals:

67.005a


301.

Description: To replace 5LNC OTRON.

Objective:

To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT


Project Category:

5LNC

ISL

Originator(s):

EUROCONTROL ICAO

OTRON is used by and is allocated in ICARD to Russian Federation.

ICAO DM sent relevant message to ISL (DM28/01 MSG 14-050).

AARRNN VV--22001166 -- 22001199//2200


152 28 June 2016 Edition: 1.0

region, to improve the aeronautical information provided and be compliant with ICAO Annex 11.

ISL states that point is used for RWY20 procedures at BIKF airport but agrees to release first semester 2015.


302.


Description:

To implement FRA for flights departing/arriving within Reykjavik FIR via Scottish FIR (EGPX).

Objective:



Project Group:


Project Category:

Free Route Airspace

ISL GBR

Originator(s):


These flights will be able to fly direct tracks via defined TMA/airport entry/exit points in Reykjavik FIR and the NAT oceanic control area boundary.

The oceanic boundary waypoint will be in LAT/LONG degrees and minutes as coordinates OR 5LNC (in compliance with current IFPS requirements).

Related proposals:

87.028a

87.028b

87.028d

87.028e

87.028f

87.028g


303.

Description:

To implement the following bidirectional ATS route segments: a. CRAYE - TUPAL; OR b. PAL - CRAYE.

Objective:

To further improve the ATS route network between Brindisi UIR and Roma UIR.


Project Group:

FAB BLUE MED RFG SE

Project Category:

ATS Routes

ITA

Originator(s):

ITA

Option usable by traffic to/from the new Enfhida airport in Tunisia.

To add the following comment: “Planned to be reassessed during works about reorganisation of military areas for strike fighter F35 needs (Ionian sea and Sicily areas).


304.

Project Name: DIRED - PNZ

Description: To implement northbound RNAV route DIRED - PNZ.

Objective:

To further improve the ATS route network within Roma ACC while offering a shorter route option for traffic LICC - LIRF (50MPCPE).


Project Group:

50 MPCPEs FAB BLUE MED

Project Category:

ATS Routes PBN

ITA

Originator(s):

ITA



AARRNN VV--22001166 -- 22001199//2200


153 28 June 2016 Edition: 1.0

305.

Description: To implement, as CDR, RNAV route DELER - NEKPI northbound only.

Objective:

To further improve the ATS route network in Roma UIR while offering a shorter route option for traffic LICC - LIRF.


Project Group:

50 MPCPEs FAB BLUE MED

Project Category:

ATS Routes

ITA

Originator(s):

ITA



306.

Description: To extend the availability of CDR3 UY170 LEGLO - ABREG within Milano UIR as CDR1/2 following the utilisation of UY170 ABREG -

ARGAX - ROMIR within Swiss UIR.

Objective:



Project Category:

CDRs

ITA

Originator(s):

EUROCONTROL


Related proposals:

61.025b

79.026

Proposal ID : 52.025b / BM0078 Impl. Status: State(s) & Org. Comments:

307.

Description:

To implement the following bidirectional ATS route segments: a. BRD - CDC; OR b. CDC - CRAYE

Objective:

a. To further improve the ATS route network within Brindisi UIR. b. To allow new flight planning options for operators flying between

airports in the north Africa (DTMB, DTNH, DTTA), Malta (LMML) and south Italy (LICB, LICC, LICJ) on one side and Scandinavian States and Russian Federation on the other.


Project Group:

FAB BLUE MED RFG SE

Project Category:

ATS Routes

ITA

Originator(s):

IATA

Planned to be reassessed during works about reorganisation of military areas for strike fighter F35 needs (Ionian sea and Sicily areas combined) .


308.

Description: To implement bidirectional ATS route segment TRP - TUC.

Objective:

To offer a shorter route option at the interface ITALY_TUNISIA.


Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA TUN

Originator(s):

FAB BLUE MED

Planned to be reassessed during works about reorganisation of military areas for strike fighter F35 needs (Ionian sea and Sicily areas).


AARRNN VV--22001166 -- 22001199//2200


154 28 June 2016 Edition: 1.0

309.

Description: To implement bidirectional ATS route segment UT313 NEMBO - VALMA

- DORAS - FIR BDRY - INDOT, available during Night.

Objective:

To improve the route network between ELB and Sicily (Italy).


Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA MLT

Originator(s):

FAB BLUE MED


310.

Description: To implement bidirectional ATS route segment PININ - PNZ - PES.

Objective:

To offer a direct route to traffic between Tunisia/Italy and East Europe.


Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA

Originator(s):

FAB BLUE MED

Continuation PES - NIT requires further study for full benefits.

Related proposals:

69.128b


311.

Description: To implement new shorter option for ARR LIPR via RIFEN.

Objective:

To further improve ATS route network within Milano FIR.


Project Category:

ATS Routes

ITA

Originator(s):

EUROCONTROL

Currently in accordance with RAD restriction LI2253 UT128 ROSKA - BELOV is not available for traffic ARR LIPR. The aim is “To segregate arriving traffic. This traffic shall file ROSKA UM859”. This restriction is valid 05.00 - 21.00 (Summer) 06.00 - 21.00 (Winter). All ARR LIPR are forced to fly on very sharp dog-leg via ROSKA - CHI - BELOV additionally pushed 18NM.

If UT128 will be allowed for ARR LIPR there is a need for lower route as today limit is FL265 AGOMO - BELOV but contrary to that there is DCT ROSKA - RIM (FL095 - FL460) due to “There is no alternative route for flight planning for traffic type MIL”. There is a different treatment between civil and military flights in that case.


312.

Description:

To implement new ATS route or allow “Direct” flight planning option or improve the RAD for flights to Pisa (LIRP) airport from ADOSA.

Objective:


Project Category:

ATS Routes

ITA

Originator(s):

IATA

Solution possible after the re-organisation of Roma TMA, Milano ACC, Roma ACC, Padova ACC and Brindisi ACC.

Currently the shortest possible option for

AARRNN VV--22001166 -- 22001199//2200


155 28 June 2016 Edition: 1.0

To further improve ATS route options for ARR LIRP. DCTs RAD

ARR LIRP from North is via VIC - FER - BOA - LUPOS.

Proposed solutions for B737-700 in zero wind conditions might save per flight up to 25NM, 116 kg fuel and 3 min flying time.

Related proposals:

79.034c


313.

Description: To replace existing 5LNC URENA.

Objective:




Project Category:

5LNC

ITA

Originator(s):

EUROCONTROL ICAO

URENA is with double reservation in ICARD for Russian Federation and Italy.

Proposal for replacement by Italy is based on “Common criteria for replacement of duplicated 5LNCs” as point is used on single ATS route.

Change is planned to be done within the work for LIBD (Bari) SIDs/STARs revision.


314.

Description: To re-designate the existing ATS route Q101 BML - OZT as Q401.

Objective:



Project Category:

Route Redesignation

MAR

Originator(s):

GBR EUROCONTROL

Re-designation requested on behalf of the UK in view of their Helicopter Route Project

It is proposed as much as possible RD number to be coherent with flight tracks.

Morocco was already informed and coordination is in progress.


315.

Project Name: HOPE - Harmonisation of Oslo Procedures and Environment - Phase 2

Description:

1. Adjustments of HOPE 1 procedures. 2. RNP approaches based on Visual RNAV Approach tests

3. New adjusted noise abatement procedures at Oslo/ ENGM airport adapted to visual RNAV approach tests and revised SIDs.

Objective:

To further improve airspace organisation in Norway FIR for flights to/from Oslo (ENGM) airport. (Revised Point Merge System Oslo TMA - post ASAP development).


Project Category:

PBN TMA

NOR

Originator(s):

NOR

Related proposals:

73.004


AARRNN VV--22001166 -- 22001199//2200


156 28 June 2016 Edition: 1.0

316.

Description: To adapt coding of ENGM RNAV SIDs via VEMIN and VIBUK.

Objective:

To align AIP publication in accordance with ICAO Annex 11 and Doc 8168.


Project Category:

AIP

NOR

Originator(s):

EUROCONTROL

Currently in accordance with AIP Norway only three SIDs VEMIN4A, VEMIN9D and VIBUK5C exist for RWY01L/19R connecting 6 other waypoints. These connections after VEMIN and VIBUK are named - “transitions” where the same named “transitions” have different environmental performances.

These 6 waypoints are specified 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.


317.

Description: 1. To implement westbound ATS route SUW - OSKUD. 2. To change from eastbound to bidirectional the existing UY225 ATS

route segment BODLA - OSKUD.

Objective:

To further improve the ATS route network within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

ATS Routes

POL

Originator(s):

DEU EUROCONTROL

Pending on introduction of the vertical split.

Related proposals:

65.010a

68.078


318.

Project Name: FRA Like (DCT) Warsaw FIR, Phase 3

Description: H24 DCTs (FRA like) expanding the availability of existing DCT options and allowing additional "Direct" flight planning options in the Upper airspace of Warsaw FIR, FL355 and above.

Objective:



Project Group:

SG BALTIC

Project Category:

DCTs Free Route Airspace

POL

Originator(s):

POL

Stepped implementation: o Night DCTs o Weekend DCTs o H24 DCTs in upper airspace (FRA like)

RTS in April 2013. Part of Polish Airspace Project 2010+

(Phase 4).

Related proposals:

62.091b

62.091c

75.040b / 15.042b

76.053 / 18.039

AARRNN VV--22001166 -- 22001199//2200


157 28 June 2016 Edition: 1.0

78.028a

86.041 / 22.046

88.015 / 23.023


319.

Description: To allow flight planning during Night on LENOV N133 POLON N983 ELPOL AMROR ROE , by excluding it from restriction EP2068.

Objective:

To allow additional shorter flight plannable options within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

RAD

POL SWE

Originator(s):

IATA

In accordance with EP2068 ATS route N983 POLON - ELPOL is not available for traffic when L621 is open with operational goal to reduce traffic complexity in sector C.

Proposal is penetrating the same ACC sectors as allowed routing but is saving 15NM.

After the implementation of Warszawa ACC vertical sector split .

Proposal ID : 70.019z / 23.031 Impl. Status: State(s) & Org. Comments:

320.

Description: To allow H24 "Direct" flight planning option SUPAK DCT POLON.

Objective:

To further improve the flight planning options within Warszawa FIR while providing additional shorter route options.


Project Group:

SG BALTIC

Project Category:

DCTs RAD

POL

Originator(s):

FAB CE

Consider FRA H24 implementation Warsaw FIR.

Related proposals:

70.019x


321.

Description: To allow “Direct” flight planning option DIMEX DCT PENOR.

Objective:

To allow additional shorter flight plannable option within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

DCTs RAD

POL SWE

Originator(s):

IATA

Shorter option for flights from ESSA to/from Austria and beyond.

After implementation of Warszawa ACC vertical sector split.


322.

Project Name: Free Route Airspace Santa Maria FIR

Description: To extend the Lisbon Free Route Airspace concept/ FRAL to Santa

Maria FIR.

Objective:


Project Category:

Free Route Airspace

PRT

Originator(s):

PRT

FRAL - Free Route Airspace Lisboa FIR above FL245 implemented 7 May 2009.

Free Route Airspace SAN & ASI sectors/FRASAI, Phase 2 implemented 1 May 2014.

Related proposals:

AARRNN VV--22001166 -- 22001199//2200


158 28 June 2016 Edition: 1.0

To further improve the airspace utilisation between Santa Maria FIR and Lisbon FIR.

64.030

68.002


323.

Project Name: RNAV 1 procedures Ljubljana TMA

Description: To design and publish RNAV 1 STARs for Ljubljana airport.

Objective:

To further improve the airspace organisation within TMA Ljubljana.


Project Group:

RFG SE

Project Category:

PBN TMA

SVN

Originator(s):

SVN


324.

Description: To replace existing 5LNC SULAX.

Objective:



Project Category:

5LNC

SWE FRA

Originator(s):

EUROCONTROL ICAO

SULAX is reserved in ICARD for Sweden. Proposal for replacement is based on

“Common criteria for replacement of duplicated 5LNCs” as point is not reserved for France

ICARD DM EUR/NAT reconfirmed by e-mail to France on 27 May 2016 that they shall substitute SULAX unless they can find an arragement with Sweden (SULAX was released by France in February 2012)


325.

Description: To introduce P-RNAV SIDs/STARs for Ankara/Esenboga (LTAC) airport.

Objective:



Project Group:

RFG SE SG BLACK

Project Category:

PBN TMA

TUR

Originator(s):

TUR

Proposal ID : 80.023e / 23.034 Impl. Status: State(s) & Org. Comments:

326.

Description: To introduce RNP APCH, SIDs/STARs for Igdir (LTCT) airport.

Objective:



Project Group:

RFG SE SG BLACK

TUR

Originator(s):

TUR

Related proposals:

80.023a

80.023b

80.023c

80.023d

AARRNN VV--22001166 -- 22001199//2200


159 28 June 2016 Edition: 1.0

Project Category:

PBN TMA


327.

Description: To replace existing 5LNC ANIBI.

Objective:


Planned 27 APR 2017

Project Category:

5LNC

DEU

Originator(s):

EUROCONTROL ICAO

ANIBI is reserved in ICARD for Morocco and used as VFR point.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Germany.


328.


Description:

To continue preparation of Full Free Route Airspace Germany by: 1. use of RAD Appendix 7 for ED-R401 (VPA); 2. introducing next set of compulsory transition/connecting points for

ARR/DEP to/from most German airports (to cover North East H24 and South West at Night);

3. introducing if required set of compulsory transition routes linked to each transition point/connecting point (above);

4. updating RAD Appendix 4 DCT (if required) supporting MIL on.

Objective:

To support implementation of Full Free Route and simplify the RAD.

Planned 27 APR 2017

Project Group:

FAB EC

Project Category:


DEU

Originator(s):

DEU FAB EC

Related proposals:

87.005a

87.005b

87.005d

87.005e


329.


Description:

1. To introduce flight director position in Beograd TMA. 2. To reduce RDR separation minima to 3NM at least for flight director.

Objective:


Planned 25 MAY 2017

Project Group:

RFG SE

Project Category:

Airspace Structure

MNE SRB

Originator(s):

MNE SRB

Related proposals:

68.012a

68.012d


330.

Project Name: FRALB - Free Route Airspace Albania - Phase 1

Description: To implement NIGHT Free Route Airspace within Tirana CTA / UTA,

Proposed spring 2017

Project Group:

ALB

Originator(s):

ALB

Night period - 21:00 - 05:00 (20:00 - 04:00). ATS route network will be suspended during

FRA hours. Phase 1 is planned to continue till 7 DEC

AARRNN VV--22001166 -- 22001199//2200


160 28 June 2016 Edition: 1.0

FL195 and above.

Objective:

To align the airspace structure with real operations and to make operational DCT's flight planable.

RFG SE

Project Category:

Free Route Airspace

FAB BLUE MED 2017 and will be extended to H24.

Related proposals:

71.085a

71.086b

71.087

71.089b

Proposal ID : 69.052 / 16.008 / DU0073 Impl. Status: State(s) & Org. Comments:

331.

Project Name: SEEN FRA

Description: To implement cross-border NIGHT Free Route Airspace within the DANUBE FAB area. and HUFRA area.

Objective:

To further improve the Free Route Airspace operations within and between Budapest FIR, Bucuresti FIR and Sofia FIR.


Project Group:


Project Category:

Free Route Airspace

BGR ROU HUN

Originator(s):

FAB DANUBE

Related proposals:

82.030 / 20.032

82.031 / 20.033

82.032 / 20.034

82.033 / 20.035


332.

Project Name: Long Range Direct Routings

Description:

1. To implement a set of published DCT segments during night that are specifically designed to facilitate and shortcut significant traffic flows on a large scale (across ANSP boundaries).

2. To facilitate level changes, very long segments will be divided into several legs.

Objective:

To further improve flight efficiency during night and gain first experience with DCT segments across ANSP boundaries.


Project Category:

DCTs Night Routes

CHE AUT DEU FRA ITA FAB EC

Originator(s):

CHE FAB EC

Related proposals:

87.050


333.

Project Name: Direct Route Airspace Implementation - Geneva AoR

Description:

To implement a comprehensive network of DCT segments in AoR Geneva, FL315+, available H24 subject to airspace availability.

Objective:

To increase flight efficiency during daytime.


Project Category:

DCTs

CHE FRA FAB EC

Originator(s):

CHE FAB EC

Redundant ATS routes will be removed.

Related proposals:

87.053

87.054


AARRNN VV--22001166 -- 22001199//2200


161 28 June 2016 Edition: 1.0

334.

Project Name: Free Route Airspace Praha/ FRAPRA, Step 3

Description:

To allow additional individual "Direct" (DCT) options as support to the existing ATS route network in Praha FIR.

Objective:

To further improve the flight planning options within Praha FIR as a third step towards the full implementation of Free Route Airspace Praha/ FRAPRA.


Project Group:

FAB CE

Project Category:

Free Route Airspace

CZE

Originator(s):

CZE

All Airways above FL 165 remain available for flight planning.

Departing/Arriving within FRA shall file via airways.

Any further development will be based on FAB CE xBorder FRA Project.

Related proposals:

69.097a

69.097b


335.

Description: To implement, as CDR, bi-directional ATS route segment M/UM372 AMR

- ESAMI.

Objective:

To further improve the ATS route network between Madrid UIR and Casablanca FIR.


Project Category:

ATS Routes

ESP MAR

Originator(s):

IACA

Connection ESAMI - ARI within Casablanca FIR exists.

Implementation of this CDR depending on Spain decision.


336.

Description: To implement, as CDR1/3, southbound ATS route segment PIMOS - FES.

Objective:

To further improve the ATS route network between Madrid UIR and Casablanca FIR.


Project Category:

ATS Routes

ESP MAR

Originator(s):

IATA

Morocco: ready for implementation. Initially approved by the Spanish military,

pending official confirmation. PIMOS - FES bidirectional to be considered

at a later stage.


337.

Description:

To implement the following new bi-directional ATS routes: 1. MGA - BERUM; 2. MGA - ALM,

or, to allow “Direct” flight planning options for the two segments.

Objective:

1. To further improve the ATS route structure within Madrid FIR and Casablanca FIR. 2. To allow better flight planning options between Madrid FIR and Casablanca FIR.


Project Category:

ATS Routes DCTs RAD

ESP MAR

Originator(s):

MAR

In practice currently there are no logic options between MGA and ALM except huge detours via GONZA and TTN.

First option is only inside Madrid FIR. Second option requires coordination

between the two States as possible DCTs are cross-border.

Morocco is ready and an implementation request is already communicated to Spain during the meeting held in Casablanca this year. Waiting for their answer and decision.


AARRNN VV--22001166 -- 22001199//2200


162 28 June 2016 Edition: 1.0

338.


Description:

To revise ENR 3.3 template column naming and publish relevant aeronautical data in accordance with ICAO requirements.

Objective:

To adapt publication of significant points in accordance with ICAO requirements.


Project Group:

SG BALTIC

Project Category:

AIP

EST

Originator(s):

EST

Proposal ID : 69.064c / 16.035c Impl. Status: State(s) & Org. Comments:

339.

Project Name: NEFAB and DK/SE FAB Free Route Airspace - NEFRA Phase 2

Description: To implement H24 cross border Free Route Airspace between DK-SE FAB and NEFAB, above FL285.

Objective:

To further improve the airspace structure between Norway FIR, Finland FIR, Sweden FIR, Tallinn FIR, Riga FIR and Kobenhavn FIR.


Project Group:

FAB Denmark/Sweden FAB NEFAB SG BALTIC

Project Category:

Free Route Airspace

FAB NEFAB FAB Denmark/Sweden

Originator(s):

FAB NEFAB

NEFRA: North European Free Route Airspace (NEFAB plus DK/SE).

ATS routes will be kept. Phase 1 planned for 23 JUN 2016.


340.

Project Name: New TSA 6

Description: To redesign TSA6 LF_R146B and TSA8 LF_R7B.

Objective:

To adapt military areas for more dynamic ASM and specific training missions within Brest ACC.


Project Group:

RFG SW

Project Category:

Civil/Military Airspace

FRA

Originator(s):

FRA

France: Civil - military agreement reached.

Related proposals:

65.045

88.019


341.

Description:

To re-designate the following existing ATS routes: 1. Y491 SOMEN - BETUV as Y111 (same segment with different RDs

Y491/UY111); 2. Y491 BETUV - KOKOS as N491 (release of Y491) (same segment

with different RDs Y491/UN491).

Objective:



Project Category:

Route Redesignation

FRA

Originator(s):

EUROCONTROL


AARRNN VV--22001166 -- 22001199//2200


163 28 June 2016 Edition: 1.0

342.

Project Name: Jersey new ATS delegation

Description:

To create a new TMA East of existing Jersey CTA with delegation of ATS.

Objective:

To further improve the airspace structure at the interface between Jersey APP and London ACC while allowing new Jersey and Guernsey SID/STAR implementation for optimum climb/descent profiles.


Project Category:

TMA Vertical FE

FRA

Originator(s):

FRA

Implementation planned in connection with New TSA 6 (ID 57.024).

Related proposals:

57.024


343.

Description: To establish a DCT or ATS route between RIBEL and GUNTU FL245+.

Objective:

To reduce flight plannable mileage and reflect the route tactically provided on a regular basis.


Project Category:

DCTs RAD

GBR

Originator(s):

GBR

Not available for UK overflights via NATEB.


344.

Project Name: PLAS

Description:

To implement systemised closely spaced ATS route structure across the Irish Sea below FL285 by establishing up to 8 RNAV1 routes (5 between London FIR and Shannon FIR and 3 between London FIR and Scottish FIR).

Objective:

To increase safety and capacity as well as environmental & efficiency improvements in the PC IoM Sector.


Project Category:

Airspace Structure ATC Sectors ATS Routes CDRs

GBR IRL

Originator(s):

GBR

Requires CAA Regaulatory approval as well as 3NM radar separation approval.

Route Designators have been requested and provided and reserved for the UK.


345.

Project Name: Tbilisi TMA

Description: a. To reconfigure existing Tbilisi TMA. b. To introduce new SIDs/STARs for Tbilisi (UGTB) airport.

Objective:

To further improve the airspace organisation within Tbilisi FIR.


Project Group:

SG BLACK

Project Category:

TMA

GEO

Originator(s):

EUROCONTROL GEO

Related proposals:

64.066a / 09.012a


346.

Project Name: Batumi TMA

Description: To reconfigure Batumi TMA and establish new SIDs/STARs ROLIN

(FL190/FL180).


Project Group:

SG BLACK

GEO

Originator(s):

GEO

AARRNN VV--22001166 -- 22001199//2200


164 28 June 2016 Edition: 1.0

Objective:


Project Category:

TMA


347.

Project Name: Batumi and Kutaisi TMAs Optimization

Description:

a. To expand the existing TMAs, both in their horizontal and vertical boundaries.

b. To implement separated SIDs and STARs.

Objective:



Project Group:

SG BLACK

Project Category:

TMA

GEO

Originator(s):

GEO


348.

Description: 1. To allow bidirectional use of point BARAD by changing to

bidirectional existing eastbound ATS route M747 LAGAS - BARAD. 2. To allow bidirectional use of point ADEKI by changing to

bidirectional the following existing westbound ATS routes: a. N644 LEYLA - ADEKI; b. L850 BEKIR - ADEKI; c. N319 EDELU - ADEKI; d. T921 POLAD - ADEKI.

Objective:

To further improve ATS route network within South Caucasus Area between Baku FIR and Tbilisi FIR.


Project Group:

SG BLACK

Project Category:

ATS Routes

GEO AZE

Originator(s):

EUROCONTROL

Proposals for implementation of sub-proposal 1: Option 1: Establishment of NEVEB as new TCP between Baku ACC and Tbilisi ACC. ATC on M747 BARAD - NEVEB and M737 DISKA - NEVEB will be provided by Tbilisi ACC including responsibility of NEVEB westbound traffic separation. Option 2: No change in TCPs and introduction of FL allocation on BARAD for westbound traffic depending on loads. For example BARAD only FL340 / FL360 on Primary Permission Request procedure.

Related proposals:

76.019a / 16.014a


349.

Description: 1. To implement ATS route M749 SKP - ROPOX (crossing point with

northern lateral limits of Athinai TMA) - ATV with the relevant procedures (SIDs and STARs) for LGAV.

2. To withdraw ATS route B1 SKP - ABLON - ATV following the implementation of M749.

Objective:

To further improve ATS route network within Athinai FIR / Hellas UIR.


Project Group:

RFG SE

Project Category:

ATS Routes

GRC

Originator(s):

GRC

Connected to PBN implementation in Athens TMA.


350. Description: Proposed GRC

Connected to PBN implementation in Athens

AARRNN VV--22001166 -- 22001199//2200


165 28 June 2016 Edition: 1.0

1. To realign ATS route segment G8 / N/UN604 KRO - OLIDA - LSV

as KRO - SUSOR (crossing point with G/UG802) - LSV. 2. To withdraw ATS route G8 ATV - KRO - OLIDA - LSV following the

re-alignment of N604.

Objective:

To further improve ATS route network within Athinai FIR.

spring 2017

Project Group:

RFG SE

Project Category:

ATS Routes

Originator(s):

GRC TMA.


351.

Description:

To implement new SIDs/STARs for Athens (LGAV) airport.

Objective:

To further improve the airspace organisation within Athinai FIR.


Project Category:


GRC

Originator(s):

GRC

Connected to PBN implementation in Athens TMA.


352.

Project Name: Central sector Zagreb Phase 2b

Description: Additional Sector Group Phase 2b: Full lateral and vertical implementation of Central sector below FL355.

Objective:

To further improve the airspace structure within Zagreb FIR and increase capacity.


Project Group:

RFG SE

Project Category:

ATC Sectors

HRV

Originator(s):

HRV

Phase 2a: FL355 and above 2 April 2015

Related proposals:

69.001

69.068b

74.051b


353.

Description:

To introduce radar approach (MSSR mode S and Primary radar approach) for Marrakech (GMMX) Ménara airport.

Objective: To further improve airspace organisation around Marrakech (GMMX)

Ménara airport.


Project Category:

Airspace Structure

MAR

Originator(s):

MAR

Related proposals:

71.048a

71.048b

71.048d


354.

Description: To replace existing 5LNC TOLSO.

Objective:



Project Category:

5LNC

MAR

Originator(s):

EUROCONTROL ICAO


TOLSO is used by and is allocated in ICARD to Spain.


AARRNN VV--22001166 -- 22001199//2200


166 28 June 2016 Edition: 1.0

355.

Description:

To implement the following ATS routes: a. BAGBO - PIXOV bi-directional (CDR); b. OZT - OJD bi-directional (CDR).

Objective:

To further improve ATS route network within Casablanca FIR/UIR.


Project Category:

ATS Routes

MAR

Originator(s):

MAR


356.

Project Name: Implementation of PBN SID/STAR and APCH procedures in Beograd FIR

Description: 1. To Implement GNSS RNP1 SID/STAR and RNP APCH for

Podgorica airport (LYPG). 2. To implement GNSS RNP1 SID/STAR for Tivat airport (LYTV).

Objective:

To further improve the airspace structure within Beograd FIR.


Project Group:

RFG SE

Project Category:

PBN TMA

SRB MNE

Originator(s):

SRB MNE


357.


Description:

1. To revise vertically all other TMAs inside Beograd FIR, except Podgorica TMA and Tivat TMA.

2. To adjust the traffic flows to/from Beograd Nikola Tesla Airport (LYBE) and introduction of a new RNAV1 and conventional SID and

STARs consequently.

Objective:



Project Group:

RFG SE

Project Category:

Airspace Structure

SRB

Originator(s):

SRB

Related proposals:

68.012a

68.012c

68.012d


358.

Description:

To implement the following ATS routes: a. SOMAT - AAAAA - OSTOV southbound (even FLs above FL275); b. LOMOS - BBBBB - TADUN northbound (odd FLs above FL275).

Objective:

To further improve the ATS route network between Kyiv UIR and Bucuresti FIR.


Project Group:

SG BLACK

Project Category:

ATS Routes

UKR ROU

Originator(s):

UKR

AAAAA – will be new boundary point between Bucuresti FIR and L’viv FIR/Kyiv UIR.

Sections of ATS routes expected to be CDR in Bucuresti FIR, with alternative routing along existing ATS routes to RUMUK.


359. Project Name: Nicosia Direct Route Airspace - Phase 2A Planned CYP

AARRNN VV--22001166 -- 22001199//2200


167 28 June 2016 Edition: 1.0

Description: To allow new H24 and/or expand from NIGHT to H24 some of the

existing "Direct" flight planning options above FL285.

Objective:


22 JUN 2017

Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

Originator(s):

CYP FAB BLUE MED

Related proposals:

86.056a

86.056b

86.056c

86.056e


360.

Project Name: Free Route Airspace Yerevan ACC

Description: To implement Night Free Route Airspace in Yerevan ACC.

Objective:



Project Group:

SG BLACK

Project Category:

Free Route Airspace

ARM

Originator(s):

ARM

Related proposals:

83.030b / 21.003b

Proposal ID : 53.009 / 16.038 / DU0008 Impl. Status: State(s) & Org. Comments:

361.

Project Name: RAD LBLT1000

Description: To allow overflights via IBLAL by withdrawing RAD restriction

LBLT1000.

Objective:

To further improve the utilisation of existing ATS route network.


Project Group:


Project Category:

ATS Routes RAD

BGR TUR

Originator(s):

EUROCONTROL

IBLAL currently is only available for traffic departing LTBA/BU/FJ, to reduce complexity of Varna sectors.

Requires further study and simulations.


362.

Project Name: Common Terminal Airspace System

Description:

1. To establish a common Terminal Airspace System and implement P-RNAV procedures for Burgas (LBBG) and Varna (LBWN) airports.

2. To adjust the ACC sectors according to the future common TMA, if necessary.

Objective:

To further improve the airspace structure within Sofia FIR and to cope with the expected traffic increase at the Black Sea airports(Phase 2).


Project Group:

RFG SE SG BLACK

Project Category:


BGR

Originator(s):

BGR

Implementation date is not defined yet - FTS/RTS and Safety case are required.

Large scale airspace management project as a follow up of the merger of the two ACCs.

Related proposals:

62.048a

Proposal ID : 68.006b / 19.064 / DU0039 Impl. Status: State(s) & Org. Comments:

AARRNN VV--22001166 -- 22001199//2200


168 28 June 2016 Edition: 1.0

363.

Description:

1. To implement dualised unidirectional ATS routes system on axis CND - WRN for ARR/DEP LBBG/LBWN.

2. To adapt TMA boundaries and establish direct transfer of air traffic control between Constanta APP and Varna APP.

Objective:

To further improve the airspace structure between Sofia FIR and Bucuresti FIR while allowing smooth climbing/descending profiles for ARR/DEP LBBG/LBWN and off-loading ACC sectors (Phase 2).


Project Group:


Project Category:

Airspace Structure

BGR ROU

Originator(s):

EUROCONTROL

CND - WRN will be used under conditions as passes via area LRR32.

During passed years several proposals for this dualised system of ATS routes were made by MDA and UKR.

MDA: BALIK or WRN - AAAAA - GLT - BBBBB - LIPTA northbound; WRN - AAAAA - BBBBB - BOTNA northbound; ARGES - BBBBB - LIPTA northbound.

UKR: BADKA - RATNO - BAREN northbound; WRN - BBBBB - AAAAA - CND northbound. Reconsideration of RAD restriction LB2008 (TUGSO).

Related proposals:

68.006a


364.

Project Name: DANUBE FAB FRA - Phase 2

Description: To extend time availability of NIGHT Free Route Airspace within the DANUBE FAB area.

Objective:

To further improve the Free Route Airspace operations within and between Bucuresti FIR and Sofia FIR.


Project Group:


Project Category:

Free Route Airspace

BGR ROU

Originator(s):

FAB DANUBE

Related proposals:

69.052 / 16.008

82.031 / 20.033

82.032 / 20.034

82.033 / 20.035


365.

Description:

To implement one of the following bi-directional ATS routes: a. DUBIN - AAAAA - BBBBB - BINOM; or b. DUBIN - AAAAA - BBBBB - LIPTA - GIDRO; or c. DUBIN - AAAAA - LAVDA.

Objective:

To further improve ATS route network between Belarus, Ukraine and Moldova.


Project Group:

SG BALTIC SG BLACK

Project Category:

ATS Routes

BLR MDA UKR

Originator(s):

MDA

AAAAA - will be new boundary point BLR/UKR.

BBBBB - will be new boundary point UKR/MDA.


AARRNN VV--22001166 -- 22001199//2200


169 28 June 2016 Edition: 1.0

366.

Description: To re-designate existing ATS route Z55 BASUD - GERSA as Z50 (release of Z55).

Objective:

To further simplify the existing RDs within Switzerland.


Project Category:

Route Redesignation

CHE

Originator(s):

EUROCONTROL


367.

Description: To allow H24 “Direct” flight planning options VEBAK DCT NOLRU DCT NAVPI and vice-versa for ARR/DEP ETNG.

Objective:

To further improve the flight planning options within Maastricht UAC.


Project Category:

DCTs RAD

DEU MUAC

Originator(s):

U.S.A.F.E FAB EC

Requested DCT options could decrease the USAF flight time by 16 minutes saving €318 and 1.1M CO2 per and year


368.

Description: 1. To adapt the availability of UM176 PPN - CMA - CLS within Madrid

UIR / Barcelona UIR. 2. To use UM176 PPN - CMA - CLS as CDR 2, week-days during the

activation period of D104 (05:00 - 23:00 during winter and 06:00 - 24:00 during summer) and as CDR 1 or permanent the rest of the time.

Objective:



Project Category:

CDRs

ESP

Originator(s):

EUROCONTROL

Currently the availability is as follows: o PPN - CMA: CDR3: MON/FRI EXC

HOL:SUMMER:0500-1500;WINTER:0600-1600.

o CMA - CLS: CDR3: MON/FRI EXC HOL:SUMMER:0500-2300;WINTER:0600-2400.

Pending military agreement.

A full revision of CDRs ongoing.


369.

Description: To allow via RAD ATS route T16 - UN975 - ORTIS for ARR

GCRR/GCFV.

Objective:

To further improve the ATS route network while providing additional, shorter flight planning options within Canarias FIR/UIR.


Project Group:

RFG SW

Project Category:

ATS Routes RAD

ESP

Originator(s):

IACA

Outcome of South West Europe RAD Review 21st - 22nd February 2013.

Solution via the RAD was requested again due to missing STARs ORTIS.

Under Lisbon / Casablanca / Canarias Axis proposal by IACA for STAR ORTIS, request by Spain to be deleted as operationally not feasible.

The two possibilities might be either DCTs from ORTIS via RAD Appendix 4 or connecting point ORTIS via RAD Appendix 5.

Connections after NAVIX via Casablanca FIR are also possible but complex due to difficult co-ordination with Morocco.

AARRNN VV--22001166 -- 22001199//2200


170 28 June 2016 Edition: 1.0

The NM RAD Team proposed this issue to be further discussed at SW Axis meetings.

Permanent airspace design solution will be linked to Canarias TMA Phase II.

Related proposals:

50.053b

75.022


370.

Description: To implement new SID PTC from LEIB.

Objective:

To further improve the ATS route network within Barcelona FIR while allowing a shorter route connection to existing route segment PTC - CPD - CHELY/ MEROS.


Project Category:

ATS Routes

ESP

Originator(s):

ESP

Related proposals:

75.007


371.

Description: To consider possible 5LNC removal from one of the ATS routes of the

crossing waypoints published on both ATS routes.

Objective:

To simplify the ATS route network within Madrid FIR/UIR and Barcelona FIR/UIR.


Project Category:

5LNC ATS Routes

ESP

Originator(s):

EUROCONTROL

Outcome of South West Europe RAD Review 21st - 22nd February 2013.

All 5LNCs are crossings of only upper ATS routes and in most of the cases unidirectional one. These 5LNCs do not have connections with lower airspace unless allowed via DCT filling.

Most of the possible undesired, even illogic, turns are not acceptable by the ACCs and unavailable by RAD restriction.

Waypoints might continue to stay as crossings but published on only one of the ATS routes which will not allow undesired turns and RAD restriction will be withdrawn.

Possible 5LNC removal from one of the ATS routes should also be considered in view of ATC procedures and usage in case of vectoring and resuming navigation to the relevant ATS route or waypoint.


372.

Project Name: EUR/NAT States AIP en-route publication issues

Description:

To adapt the AIP CDR publication of:


Project Category:

ESP

Originator(s):

EUROCONTROL

Publication location (AIP placeholder) for Spain will be further discussed under WP/11. The ATS routes are published in 5

AARRNN VV--22001166 -- 22001199//2200


171 28 June 2016 Edition: 1.0

a. Lower/Upper limits expression in VFR FLs or intermediate levels between IFR FLs;

b. CDR categories of ATS routes UL58, UM445, UM744, UN747, UN860, UT245, UT249, UT252 and UT312.

Objective:

To adapt in State AIP ATS route vertical limits.

AIP CDRs

(five) ENR sub-parts instead of required by ICAO - ENR 3.1/3.2/3.3..

In most of the cases the CDRs are published with IFR FL limits and either FL340 or FL360 or FL380 is not covered by conditions and stays as available FL.

Pending military agreement.


373.

Description: To allow eastbound flights on UN741 from EDUMO to NELSO.

Objective:

To further improve the ATS route network while allowing eastbound flights between EDUMO and NELSO on UN741 for USAF flights when diplomatic clearances can't be obtained.


Project Group:

RFG SW

Project Category:

ATS Routes

ESP

Originator(s):

U.S.A.F.E

Saves 26 minutes of flight time and $5,965 USD per flight.

Under study by Canarias ACC due to conflicting routes in non-radar environment.


374.

Description:

To re-consider the use of RWY13 procedures for DEP LEMG, depending on traffic demand and if necessary to revise them.

Objective:

To further improve SID / STAR procedures to improve flight efficiency and the environment.


Project Category:

Airspace Structure

ESP

Originator(s):

IACA

Currently crews can only request the BLN2H SID on departure (on ATC Approval). This is very rarely given and aircraft route to the south on BLN2C which uses an additional 145 kg of fuel. The large number of departures routing to the north via BLN would bring significant environmental benefits.


375.

Description: To replace existing 5LNC MAROT.

Objective:

To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT region;

To improve the aeronautical information provided; To be compliant with ICAO Annex 11.


Project Category:

5LNC

ESP

Originator(s):

EUROCONTROL ICAO

MAROT is with double reservation in ICARD for Russian Federation and Haiti.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Spain.


376.


Description:


ESP

Originator(s):

In accordance with AIP Spain, part AD2, LEMD P-RNAV SIDs are identified by coded designator containing 8 (eight)

AARRNN VV--22001166 -- 22001199//2200


172 28 June 2016 Edition: 1.0

To publish all SIDs / STARs in AIP Spain, ENR 2 in accordance with Annex 11: 1. coded designator to contain maximum 7 (seven) characters; 2. after the validity indicator only 1 (one) letter indicating the route

indicator is allowed.

Objective:


Project Category:

AIP EUROCONTROL characters - BARDI1AX, BARDI1AY,

NANDO3AR, etc. coming from additional letter added. All other P-RNAV SIDs also contain similar additional letter - SIE1AL, VTB2AS, etc.

In accordance with AIP Spain, part AD2, all LEMD and LEBL instrument arrivals - continuous descent (CDA) STARs are identified by coded designator containing 9 (nine) characters - MORAL3DCC or ORBIS1DCC or ALBER1DCN or PUMAL2DCN, etc.

Furthermore with AIRAC AMDT 01/15 (WEF 05 MAR 2015) Spain continued to publish new CDA STARs for Gran Canaria AD containing 9 characters such as COSTI1DCC, ODEGI1DCC, REMGI1DCC and VIDRI1DCC.

This 8 (eight) or 9 (nine) characters publication of designators is not compliant with ICAO and has an impact on aeronautical database systems. As an example in EAD SDO (Static Data Operations) STAR PUMAL2DCN is converted and coded as MAL2DCN due to 7 characters limit.

Spain (ENAIRE ATM and AIS part) as well as ICAO were approached on clarifying the justification of this publication.

Related proposals:

84.056a


377.

Description:

1. To implement the following ATS routes: a. Z17 MABUX - GODOX eastbound; b. Z19 EPAMA - WALLY westbound; c. UZ26 EBROX - LATRO northbound; d. UL184 TLD - RBO northbound (extension of existing RD); e. Z53 ADKIM - VJF northbound; f. Z82 MEROS - VERSO northbound; g. L58 VIBAS - PEPAS - OBAKA - BERUM bi-directional.


Project Category:

ATS Routes

ESP

Originator(s):

ESP

AARRNN VV--22001166 -- 22001199//2200


173 28 June 2016 Edition: 1.0

2. To re-designate the following existing ATS routes: a. Z/UZ230 HIJ - TLD as L/UL184 (release of Z230); b. UT257 NANDO - MABUX as Z17.

3. To withdraw existing ATS route UT257 MABUX - LASPO (double

designation as UM871).

Objective:

To further improve ATS route network within Spain.


378.

Description:

To withdraw or replace, in accordance with ICAO Annex 11 and Annex 15, the following reporting points published AIP Spain, ENR 4.4.: a. NORAY - not coordinated via ICARD; b. All SID/STAR RNAV points - most of them already published in AD

2; c. Around 50 (fifty) five-letter pronounceable name codes (5LNCs)

used for Military purpose - not coordinated via ICARD; d. Other codes used for Military purpose - plain text or letters/numbers

combinations.

Objective:

To further improve the AIP publication avoiding 5LNCs inconsistency with Annex 11.


Project Category:

5LNC AIP

ESP

Originator(s):

EUROCONTROL

In accordance with Annex 15, ENR 4.4 shall contain ONLY “An alphabetically arranged list of name-code designators (five-letter pronounceable “name-code”) established for significant points at positions not marked by the site of radio navigation aids, including:”

In accordance with Annex 11 where a significant point is required at a position not marked by the site of a radio navigation aid, and is used for ATC purposes, it shall be designated by a unique five-letter pronounceable “name-code”. This name-code designator then serves as the name as well as the coded designator of the significant point. States’ requirements for unique five-letter pronounceable name-code designators shall be notified to the Regional Offices of ICAO for coordination.

Information on this AIP inconsistency was already reported to Spain and relevant actions expected.

As from 4 FEB 2016 the following SID/STAR RNAV points will be replaced by 5LNCs: FV624, FV625, FV733, FV734, FV735, FV736, RR403, RR404, RR405, RR521 to DEMEX, LIRBU, ROXES, NOBLI, RATAT, TUVIL, GARGO, LOBSO, GOLFY, TUXAM respectively.

Part of the military 5LNCs are created in ICARD following coordination with ICAO and based on ICARD 5LNC Task Force decisions.

AARRNN VV--22001166 -- 22001199//2200


174 28 June 2016 Edition: 1.0


379.

Description:

To implement the following bi-directional ATS routes: a. UT115 MGA - AMR; b. UM192 AMR - GATAS - TARIK.

Objective:

To further improve ATS route network within Barcelona FIR at interface with Algiers FIR.


Project Category:

ATS Routes

ESP DZA

Originator(s):

ESP

Lower ATS route A44 exists as MGA - AMR - TARIK - MOS inside Madrid FIR and Algiers FIR.

Extension of RD N865 or M192 and new RD are foreseen to be used.

No information for implementation of Upper part TARIK - MOS.


380.

Description: To allow H24 “Direct” flight planning options LUXUR DCT PIMAD or GENIO DCT PIMAD and vice-versa for ARR/DEP LERT / LEMO.

Objective:

To further improve flight planning options for flights arriving/departing to/from LERT / LEMO.


Project Category:

DCTs RAD

ESP

Originator(s):

U.S.A.F.E

Requested due to shifting of USAF routing to enter the Barcelona FIR at point LUXUR instead via point MORSS for aircraft coming from South West Asia which saves around 4 minutes of flight time and €100K per year.

Requested DCT options could decrease the USAF flight time by 7 minutes saving another €200K per year.

Options will allow proper connection to ATS route UT100 and will avoid existing very sharp turn LUXUR/GENIO UM134 XARON UT100 PIMAD


381.

Project Name: FLOS

Description:

To adapt existing ATS routes in AIP Spain, ENR 3 or swap to/publish new FLOS in AIP Spain, ENR 1.7.

Objective:

To adapt the FLOS used within the airspace of Spain.


Project Category:

AIP

ESP

Originator(s):

EUROCONTROL

In accordance with AIP ENR 1.7-2 “Table of cruising levels” the direction of cruising levels in Spain is East/West: ODD 000° - 179° (e.g. FL310, FL330 …FL410…etc.) and EVEN 180° - 359° (e.g. …, FL300, FL320 …FL430…etc.).

In accordance with AIP ENR 3 for majority of ATS routes the direction of cruising levels is contrary (anti-hemispheric) to what is specified in ENR 1.7. With help by Jeppesen it was found that around 75% of ATS route segments are NOT in accordance with AIP ENR1.7.

In RAD Appendix 4 the direction of cruising levels announced for majority of DCTs is also contrary to AIP Spain.

Portugal, Morocco, and France use the

AARRNN VV--22001166 -- 22001199//2200


175 28 June 2016 Edition: 1.0

other FLOS North/South (ODD 090° - 269° and EVEN 270° - 089°).


382.

Description: To adapt all EFHK RNAV SIDs with ATS route network.

Objective:

To further improve airspace organisation within Helsinki TMA.


Project Group:

SG BALTIC

Project Category:

5LNC ATS Routes

FIN

Originator(s):

EUROCONTROL

Currently none of the published in AIP Finland EFHK RNAV SIDs last 5LNCs have connection to the existing ATS route network. Either points are on the line of relevant ATS route or far from any ATS routes. In AIP all these points are published as only connected to EFHK AD.


383.

Description:

To re-designate the following existing ATS routes: a. Z637 AOSTA - BANKO as L615; b. UZ637 AOSTA - BANKO - MILPA as UL615 (release of Z637).

Objective:

To rationalise the existing ATS route designators within Italy and France in order to simplify the designation, release for further use and further facilitate the flight planning.


Project Category:

Route Redesignation

FRA ITA CHE

Originator(s):

EUROCONTROL


384.

Project Name: Marseille ACC re-organisation Phase 3

Description: To redefine the split between the layer 1 and the layer 2 for all the

sectors in Marseille ACC.

Objective:

To further improve the airspace structure and capacity within Marseille ACC.


Project Category:

ATC Sectors

FRA

Originator(s):

FRA

Related proposals:

83.025a


385.

Description: To re-designate the existing ATS route UQ211 BALSI - VATIR as UQ209

(release of Q211).

Objective:

To rationalise the existing ATS route designators within France in order to simplify the designation, release for further use and further facilitate the flight planning.


Project Category:

Route Redesignation

FRA CHE

Originator(s):

EUROCONTROL

AARRNN VV--22001166 -- 22001199//2200


176 28 June 2016 Edition: 1.0


386.

Project Name: Paris ACC re-organisation - Phase 2

Description:

To re-organise the lower airspace and delegate ATS to APP units below FL145 for relevant airspace in Paris ACC.

Objective:

To further improve the airspace structure within France FIR.


Project Category:

Airspace Structure

FRA

Originator(s):

FRA

Related proposals:

69.089a

69.089c

69.089e

69.089f

75.080

75.082


387.


Description: To implement H24 Free Route Airspace above FL255 at Prestwick ACC AoR within the following ATC Sectors:

a. Rathlin Sector; b. Central Sector; c. Hebrides High Sector; d. Moray High Sector; e. Part of Tyne Sector; f. Montrose North Sector; g. Part of Dean Cross North Sector.

Objective:



Project Group:


Project Category:

Free Route Airspace

GBR

Originator(s):


Dependant and possible to implement after instalation of the new ATM system at Prestwick ACC foreseen MAR 2016.

Also looking at cross-border DCT’s with adjacent States.

ATS route network will be withdrawn above FL255.

Related proposals:

81.073a

87.028a

87.028b

87.028c

87.028e

87.028f

87.028g


388.


Description:

To implement FRA for all flights transiting via Bodø, Norway or Scottish FIRs.

Objective:



Project Group:


Project Category:

Free Route Airspace

GBR NOR

Originator(s):


Enhanced Free Route operation with increased lateral flexibility (latitude expressed in degrees and minutes) for all flights when crossing 010W and 000L east of Iceland, en route via Bodø, Norway or Scottish FIRs.

Related proposals:

87.028a

87.028b

87.028c

87.028d

87.028f

87.028g

AARRNN VV--22001166 -- 22001199//2200


177 28 June 2016 Edition: 1.0


389.

Description: To implement bi-directional ATS route ASKAM - OTBED or allow "Direct" flight planning options ASKAM DCT OTBED and OTBED DCT ASKAM.

Objective:

To improve airspace options when area D323C is not active.


Project Category:

ATS Routes DCTs

GBR

Originator(s):

IATA

When area D323B is not active the option is ATS route UL975.


390.

Description: To design and introduce UGTB STARs via TISOT.

Objective:

To further imporve airspace structure within Tbilisi FIR.


Project Group:

RFG SE SG BLACK

Project Category:

Airspace Structure

GEO

Originator(s):

EUROCONTROL

At first phase shorter flight planning options will be allowed by RAD Appendix 5.

Currently arrivals follow ATS routes G482 / N82 and then STAR via DF with extension of 60NM.


391.

Description: To properly designate all UGTB STARs in accordance with Annex 11.

Objective:

To adapt the STAR coding.


Project Group:

RFG SE SG BLACK

Project Category:

AIP

GEO

Originator(s):

EUROCONTROL

In accordance with ICAO the basic indicator shall be the name or name-code of the significant point where a standard arrival route begins.

Currently for few STARs the description defines that names used for coding are not these points where a STAR begins.


392.

Description: To change the availability of existing ATS route UP14 PINDO - RIKSO

from Night (22.00 - 04.00) to H24.

Objective:

To further improve ATS routes network in PINDO area of Hellas UIR.


Project Group:

RFG SE

Project Category:

ATS Routes

GRC

Originator(s):

EUROCONTROL


393.

Description: To allow point BAREB for SEAFRA operation.

Objective:

To further improve FRA options within Zagreb FIR.


Project Group:

RFG SE

HRV

Originator(s):

EUROCONTROL

BAREB was allowed for HUFRA operation as from 25 JUN 2015

As continuation currently Croatia allows only BAREB DCT VIBOP (FL265 - FL335) and VIBOP DCT BAREB (FL295 - FL345)

AARRNN VV--22001166 -- 22001199//2200


178 28 June 2016 Edition: 1.0

Project Category:

Free Route Airspace

outside of SEAFRA operations


394.

Description:

To re-designate all remaining ''Lower'' non-RNAV ATS routes as RNAV and rationalise the use of existing RNAV designators as follows: a. W10 CRK - CML - GERVO - CLY - LIFFY as N12; b. W12 SHA - CLY as N160; c. W13 DUB - INKUR - KORAK - SHA as L975; d. W15 KORAK - CRN as Q150; e. V14 BAGSO - DUB - SHA as L70; f. Q202 SUROX - DEVOL as L18 (release of Q202).

Objective:

To rationalise the existing ATS route designators within Shannon FIR/UIR and SOTA in order to make them compatible with the existing RNAV airspace and further facilitate the flight planning.


Project Category:

Route Redesignation

IRL

Originator(s):

EUROCONTROL

ENSURE project removed All ''Upper'' ATS routes as of 17 DEC 2009.

Minor rationalisation of lower routes feasible.

Release of freed up ATS routes required. Exact AIRAC date still to be confirmed. It is likely that routes will be withdrawn –

(Borealis- Step1, extension of FRA down to FL075).

Related proposals:

87.028a


395.


Description:

To publish in AIP Ireland the Free Route Airspace procedures.

Objective:

To adapt in AIP the FRA publication in accordance with the ERNIP.


Project Category:

AIP

IRL

Originator(s):

EUROCONTROL

FRA was introduced on 17 DEC 2009 and announced via AIC.

Around 5 years later the AIP Publication is missing or it is not in accordance with ERNIP Part 1.

Coordination between the NM and Ireland on AIP publication was already initiated.


396.


Description: To extend the Free Route Airspace in Shannon CTA down to FL075.

Objective:



Project Group:


Project Category:

Free Route Airspace

IRL

Originator(s):


The implementation of this step will include removal of the lower ATS routes (FL075 - FL245) within most of the Shannon CTA.

The portion of the Shannon CTA between FL185 and FL245 above the Dublin CTA is not affected. This will bring flight planning for operators in line with the current daily operation.

Related proposals:

65.066

87.028b

87.028c

AARRNN VV--22001166 -- 22001199//2200


179 28 June 2016 Edition: 1.0

87.028d

87.028e

87.028f

87.028g


397.

Project Name: AIRLA - RNAV approaches

Description: a. To develop RNAV LPV approaches to 21 State & Regional airport

runways. b. To restructure the airspace at each airport to provide direct routing

to the new LPV procedures, protected by controlled airspace.

Objective:

To further improve the airspace structure and enhance efficiency within Shannon UIR.


Project Category:


IRL

Originator(s):

IRL

Phased implementation 2017/2018 To be conducted under a funding contract

awarded by GSA.


398.


Objective:



Project Group:

RFG SE

Project Category:

5LNC

ITA

Originator(s):

EUROCONTROL ICAO



ICAO DM sent relevant message to ITA (DM23/01 MSG 14-027).


399.

Description: To replace existing 5LNC RASIN.

Objective:




Project Category:

5LNC

ITA

Originator(s):

EUROCONTROL ICAO

RASIN is with double reservation in ICARD for Croatia and Senegal.

Point is used in Italy for military aerodrome purpose at LICZ.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Italy.


400.

Description: To replace existing 5LNC LORIS.

Objective:

1. To avoid 5LNCs duplication within the ECAC area of the ICAO


Project Category:

5LNC

ITA

Originator(s):

EUROCONTROL ICAO

LORIS is not in ICARD and it is not available for selection in any region.

Point is used in Italy for two separate military aerodrome purpose at LICZ and

AARRNN VV--22001166 -- 22001199//2200


180 28 June 2016 Edition: 1.0

EUR/NAT region; 2. To improve the aeronautical information provided; 3. To be compliant with ICAO Annex 11.

LIPL. Proposal for replacement is based on

“Common criteria for replacement of duplicated 5LNCs” as point is not reserved for Italy.


401.

Description: To implement ATS route segment SONSO - RAVOL - OSDAM northbound.

Objective:

To further improve the ATS route network within Casablanca FIR.


Project Category:

ATS Routes

MAR

Originator(s):

MAR


402.

Description:

To implement the following ATS routes: 1. RBT - TOLSI northbound; 2. BAGBO - RBT bidirectional (CDR).

Objective:



Project Category:

ATS Routes

MAR

Originator(s):

MAR


403.

Description:

To implement the following ATS route segments: a. SUBAL - SUNID - IBALU - RBT bi-directional; b. BEXAL - SUNID - NISBA bi-directional; c. SONSO - MAK northbound; d. CSD - RBT bi-directional;

Objective:

To further improve ATS route network within Casablanca FIR/UIR.


Project Category:

ATS Routes

MAR

Originator(s):

MAR

Currently SUBAL - SUNID - IBALU - RBT and BEXAL - SUNID - NISBA are available as DCTs.

Related proposals:

66.081c


404.

Description: To implement southbound ATS route TAKAV - VEDOD.

Objective:



Project Category:

ATS Routes

MAR

Originator(s):

IACA

Connection already exists as DCT in RAD Appendix 4.


AARRNN VV--22001166 -- 22001199//2200


181 28 June 2016 Edition: 1.0

405.

Description:

1. To introduce radar approach (MSSR mode S and Primary radar approach) for Fes (GMFF) Saiis airport.

2. To implement new SIDs and STARs for Fes (GMFF) Saiis airport.

Objective: To further improve airspace organisation around Fes (GMFF) Saiis

airport.


Project Category:


MAR

Originator(s):

MAR

Re-organisation of existing Fes (GMFF) Saiis airport TMA implemented.


406.

Description:

To introduce radar approach (MSSR mode S and Primary radar approach).

Objective:

To further improve airspace organisation around Casablanca (GMMN) Mohammed V airport.


Project Category:

Airspace Structure

MAR

Originator(s):

MAR


407.

Description:

a. To implement new TMA. b. To implement new SIDs and STARs.

Objective: To further improve airspace organisation around Nador (GMMW) El

Aroui airport.


Project Category:


MAR

Originator(s):

MAR


408.

Description:

To introduce radar approach (MSSR mode S and Primary radar approach) for Tanger (GMTT) Ibn Battouta airport.

Objective: To further improve airspace organisation around Tanger (GMTT) Ibn

Battouta airport.


Project Category:

Airspace Structure

MAR

Originator(s):

MAR


409.

Description: To replace existing 5LNC KESIR.

Objective:



Project Category:

5LNC

MAR

Originator(s):

EUROCONTROL ICAO


KESIR is used by and is allocated in ICARD to Turkey.


AARRNN VV--22001166 -- 22001199//2200


182 28 June 2016 Edition: 1.0

410.

Description: To allow “Direct” H24 flight planning option IBALU DCT SAMAR for ARR GCLP / GCXO.

Objective:

To further improve the flight planning options within Morocco for arrivals to Grand Canaria and Tenerife North airports.


Project Category:

DCTs RAD

MAR

Originator(s):

ESP

Outcome of SW Axis/37 (17 - 18 MAR 2015).

An optimum use was considered by AOs and it is for all European DEP except EG.. / EI…

Information on possible loading (25 daily flights) was provided to Morocco for further consideration.

Similar distance as existing option via TERTO but shifts traffic in other Canarias ACC Sector allowing proper re-distribution.

Option available after the new sectorisation.

This DCT is used Tactically between Canarias ,Casablanca and Seville during weekend on request by Canarias


411.

Description: To redesignate existing ATS route L/UL19 MOLIX - TULIP as M/UM624 (release of L19).

Objective:

To further improve the ATS route network within Amsterdam FIR in order to adapt the ATS route designators to the existing traffic flows and facilitate flight planning.


Project Group:

FAB EC

Project Category:

Route Redesignation

NLD

Originator(s):

EUROCONTROL


412.


Description: To re-designate the following existing Helicopter routes: KZ02 - KZ09, KZ20, KZ23, KZ25, KZ30, KZ53, KZ60, KZ66.

Objective:



Project Category:


NLD

Originator(s):

EUROCONTROL

RDs KZ02 - 09 are not in accordance with Annex 11.



413.

Description: To replace 5LNC REGNA.

Objective:



Project Category:

5LNC

NLD

Originator(s):

EUROCONTROL ICAO


REGNA is allocated to Russian Federation.Released by Netherlands on 19 AUG 2002 but still used for EHRD SID as per AIPNetherlands - ENR 4.4-4 / 27 JUN

AARRNN VV--22001166 -- 22001199//2200


183 28 June 2016 Edition: 1.0

2013. ICAO DM sent relevant message to NLD

(DM28/01 MSG 14-051). NLD confirmed 290114 that they will

investigate.


414.

Description: To replace existing 5LNC PEPEL.

Objective:

a. To avoid 5LNCs duplication within the ECAC area of the ICAO EUR/NAT region;

b. To improve the aeronautical information provided; c. To be compliant with ICAO Annex 11.


Project Category:

5LNC

NLD

Originator(s):

EUROCONTROL ICAO

PEPEL is reserved in ICARD for Uzbekistan.

Proposal for replacement is based on “Common criteria for replacement of duplicated 5LNCs” as point is not reserved for the Netherlands.


415.

Project Name: RNAV procedures for EPPO

Description: To implement RNAV procedures for TMA Poznan South (EPPO) airport.

Objective:

To further improve the airspace organisation within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

PBN TMA

POL

Originator(s):

POL

Related proposals:

79.076a

79.076b


416.

Description:

To expand the utilization of existing H24 “Direct” flight planning option DENKO DCT LATAG by allowing ARR LI...

Objective:

To further improve the utilization of allowed DCTs within Warszawa FIR.


Project Group:

SG BALTIC

Project Category:

RAD

POL

Originator(s):

IATA

Currently this DCT is allowed for traffic DEP EK/ES - ARR EDDM, LOWI, LOWS and LOWW.

This DCT is solely within Warszawa ACC Sector D and could shorten flying distance with 34NM.


417.

Description: To expand the "Direct" flight planning option on segment ETRUS - GORPI - CHO - GOVEN to H24.


Project Group:

SG BALTIC

POL

Originator(s):

IATA

Night DCT ETRUS - GORPI - CHO - GOVEN

existing.

Related proposals:

62.028a / 20.044a

AARRNN VV--22001166 -- 22001199//2200


184 28 June 2016 Edition: 1.0

Objective:

To further improve flight planning options within Warszawa FIR.

Project Category:

DCTs


418.

Description:

To expand the following Night "Direct" flight planning options to H24: a. LENOV DCT BABEN or LENOV DCT VIBUL; b. REGLI DCT BURAN; c. XELOL DCT LENOV or ELPOL DCT LENOV.

Objective:

To further improve flight planning options within Warszawa FIR and Sweden UIR.


Project Group:

SG BALTIC

Project Category:

DCTs

POL SWE

Originator(s):

IATA

Night DCT flight planning options existing.


419.

Description: To implement H24 "Direct" flight planning option PITOK DCT LALES.

Objective:



Project Group:

FAB CE

Project Category:

DCTs RAD

SVK

Originator(s):

FAB CE

Currently not part of FRABRA.

Related proposals:

74.017 / 16.025

Proposal ID : 70.019x / CE0064 Impl. Status: State(s) & Org. Comments:

420.

Description: To allow H24 "Direct" flight planning option PARAK DCT SUPAK.

Objective:



Project Group:

FAB CE

Project Category:

DCTs RAD

SVK

Originator(s):

FAB CE

Currently not part of FRABRA

Related proposals:

70.019z / 23.031


421.

Description: To allow "Direct" flight planning option ALAMU or ERGOM DCT BILNA.

Objective:

To further flight planning option on Northbound direction within Bratislava FIR.


Project Group:

RFG SE

Project Category:

DCTs RAD

SVK

Originator(s):

IATA

SVK: no northbound track feasible for safety reasons.

This is the only missing link on bi-directional options from Croatia via Hungary, Slovakia, Czech Republic and Poland towards Scandinavia and vice-versa.

Related proposals:

AARRNN VV--22001166 -- 22001199//2200


185 28 June 2016 Edition: 1.0

81.064a

81.064b

81.066

81.067


422.

Description:

To withdraw or replace, in accordance with ICAO Annex 11, VFR entry and exit points to/from CTRs published as village names composed of five-letters similar to pronounceable 5LNCs in AIP Slovakia, part AD 2.

Objective:

To further improve the AIP publication avoiding duplication of pronounceable 5LNCs.


Project Category:

AIP

SVK

Originator(s):

EUROCONTROL

6 (six) VFR reporting points are similar to five-letter pronounceable name-codes (5LNCs). Most of these names are reserved as 5LNCs in ICARD and already used worldwide by other States.

These names maintained in any aeronautical database create and might create artificial name duplication contrary to Annex 11.



423.

Description:

To withdraw or replace VFR reporting points published as pronounceable 5LNCs in AIP Sweden, part AD 2, Visual Approach Charts.

Objective:

To align AIP publication in accordance with Annex 11.


Project Group:

SG BALTIC

Project Category:

5LNC AIP

SWE

Originator(s):

EUROCONTROL

Around 30 (thirty) VFR reporting points are designated as five-letter pronounceable name-codes (5LNCs). Most of them are reserved in ICARD and already used worldwide by other States.



Pending CAA decision.

Proposal ID : 60.010g / 15.046g Impl. Status: State(s) & Org. Comments:

424.

Project Name: SMART, Phase 4

Description:

To completely redesign entire Turkish lower and upper airspace, ACC sectorisation (20 sectors FL235 and above) and reconfigure ACC/APP with DFL235 and FL325.


Project Group:

RFG SE SG BLACK

TUR

Originator(s):

TUR

SMART: Systematic Modernization of ATM Resources in Turkey.

Related proposals:

60.010c

60.010f

AARRNN VV--22001166 -- 22001199//2200


186 28 June 2016 Edition: 1.0

Objective:

To further improve airspace organisation within Istanbul FIR and Ankara FIR and enhance capacity within the Turkish ACCs in order to cope with the increasing traffic demand (SMART project, Phase 4).

Project Category:


60.010h / 15.046h


425.

Description: To adapt RAD restriction LT2017 by adding exception during Night (Note 3) same as RAD restriction LT2070.

Objective:

To further improve airspace utilisation between Istanbul FIR, Hellas UIR and Sofia FIR.


Project Group:

RFG SE SG BLACK

Project Category:

RAD

TUR

Originator(s):

EUROCONTROL

None allowance of alternative ATS route option This restriction is directly connected with

any changes to RAD restriction LT2070. As from 5 MAY 2011 LT2070 (Note 3) had been changed and during the NIGHT period 17.30h - 02.30h (AIRAC APR - AIRAC OCT inclusive) 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.


426.

Project Name: 5LNC KAMAN

Description: To replace existing 5LNC KAMAN.

Objective:

1. To avoid 5LNC duplication worldwide. 2. To improve the aeronautical information provided. 3. To be compliant with ICAO Annex 11.


Project Group:

SG BLACK

Project Category:

5LNC

TUR

Originator(s):

ICAO

KAMAN is one of that TMA entry/exit points, is on the AWY A/UA 285 and will be replaced by ADVOK point which has been allocated to Turkey at 13.04.2015.


427.

Description: To introduce P-RNAV SIDs/STARs for Izmir/Adnan Menderes (LTBJ)

airport.

Objective:



Project Group:

RFG SE SG BLACK

Project Category:

PBN

TUR

Originator(s):

TUR

AARRNN VV--22001166 -- 22001199//2200


187 28 June 2016 Edition: 1.0

TMA


428.

Project Name: FRALB - Free Route Airspace Albania - Phase 2

Description: To extend time availability to H24 of NIGHT Free Route Airspace within

Tirana CTA / UTA.

Objective:

To further improve the Free Route Airspace operations within Tirana FIR.

Planned 07 DEC 2017

Project Group:

RFG SE

Project Category:

Free Route Airspace

ALB

Originator(s):

ALB FAB BLUE MED

ATS route network will be withdrawn.

Related proposals:

71.085a

71.086a

71.087

71.089b


429.

Project Name: Nicosia Direct Route Airspace - Phase 2B

Description: To allow new H24 and/or expand to H24 the rest of the existing NIGHT

"Direct" flight planning options above FL285.

Objective:


Planned 07 DEC 2017

Project Group:

FAB BLUE MED RFG SE

Project Category:

DCTs RAD

CYP

Originator(s):

CYP FAB BLUE MED

Related proposals:

86.056a

86.056b

86.056c

86.056d


430.


Description:

To implement Full Free Route Airspace Germany, Solution 1a and 1b as follows: 1. H24 within North East (above FL285/315); 2. Night within South West (above FL245/315); 3. Night within AoR of Munich ACC (FL245 - FL315); 4. Night within AoR of Bremen ACC (FL245-FL285).

Objective:

To implement Full FRA according to PCP requirements and improve flight efficiency within FABEC.

Planned 07 DEC 2017

Project Group:

FAB EC

Project Category:

Free Route Airspace

DEU

Originator(s):

DEU FAB EC

Related proposals:

87.005a

87.005b

87.005c

87.005e


431.

Project Name: FRAM2 Project - Phase 1

Description: To introduce NIGHT Free Route Airspace above FL245 within the

Maastricht UAC AoR.

Planned 07 DEC 2017

Project Group:

FAB EC

MUAC BEL DEU NLD

Night period 23:00 - 05:00 (22:00 - 04:00). ATS route network and all allowed DCTs will

exist.

Related proposals:

AARRNN VV--22001166 -- 22001199//2200


188 28 June 2016 Edition: 1.0

Objective:

To allow Free Route Airspace operations within Maastricht UAC.

Project Category:

Free Route Airspace

Originator(s):

MUAC FAB EC

87.036b

87.036c


432.

Description:

To withdraw or replace, in accordance with Annex 11, VFR reporting points published as pronounceable 5LNCs in AIP Finland, part AD 2.

Objective:

To comply with requirements of Annex 11 in designation of significant points with 5LNCs.


Project Group:

SG BALTIC

Project Category:

5LNC

FIN

Originator(s):

EUROCONTROL

Currently in AIP Finland, Part AD for each aerodrome after the table with RNAV terminal points there is a table with VFR reporting points most of which are declared as compulsory.

These VFR reporting points are designated as five-letter pronounceable name-codes (5LNCs) and internal finalization of their purpose, reason of AIP publication and compatibility with ICAO shall be discussed.


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.


433.

Project Name: BALTIC FAB ATS routes

Description:

a. To implement the following new ATS routes: i. EVODO - AAAAA westbound; ii. SUW - VABER eastbound; iii. AAAAA - BADUS westbound; iv. AAAAA - LAVAR westbound.

b. To change the following existing ATS routes: i. N858 DENKO - BOKSU - LAVAR change of direction to

westbound; ii. L735 GOVEN - ZZZZZ - AAAAA westbound; iii. T727 SUI - XXXXX - VABER change of direction to eastbound; iv. Y225 new segment OSKUD - YYYYY (in T727) eastbound; v. L29 VABER - LAVAR change of direction to eastbound.

Objective:


Project Group:

FAB Baltic SG BALTIC

Project Category:

ATS Routes

POL LTU

Originator(s):

FAB Baltic

AAAAA (540216N 0233059) will be a new common boundary point between FIR EPWA and FIR EYVL (coordinates are not finally fixed).

Changes to Vilnius SIDs/STARs also required.

Depends on changes in Moscow area followed by changes in interface between Republic of Belarus and Lithuania.

AARRNN VV--22001166 -- 22001199//2200


189 28 June 2016 Edition: 1.0

To further improve the ATS route network within the Baltic FAB.


434.


Description: To extend time availability to H24 on Seasonal bases above a certain FL of NIGHT Free Route Airspace within the DANUBE FAB area.

Objective:



Project Group:


Project Category:

Free Route Airspace

BGR ROU

Originator(s):

FAB DANUBE

Related proposals:

69.052 / 16.008

82.030 / 20.032

82.032 / 20.034

82.033 / 20.035


435.

Project Name: Implementation of FUA restrictions

Description:

To change from a route-based airspace management to an airspace-based ASM philosophy.

Objective:

To get Swiss Airspace Management techniques ready for FRA implementation.


Project Category:

Civil/Military Airspace DCTs RAD

CHE AUT DEU ITA FRA FAB EC

Originator(s):

CHE FAB EC

This includes the operational use of Flight Planning Buffer Zones and the implementation of (potentially complex) FUA restrictions in RAD Appendix 7 and adaptation of several restrictions in the Pan-Europe Annex - see attached file.

Related proposals:

87.052

87.053


436.

Project Name: Direct Route Airspace Implementation AoR Zurich

Description:

To implement a comprehensive network of DCT segments in Zurich ACC AoR, FL305+, H24 subject to airspace availability.

Objective:

To increase flight efficiency during daytime and become compliant with PCP implementing rule.


Project Category:

DCTs

DEU FRA CHE FAB EC

Originator(s):

CHE FAB EC

Redundant ATS routes will be removed.

Related proposals:

87.052

87.054


437.

Project Name: Brest ACC re-organisation

Description: To re-organise the lower airspace and ATS delegation to APP units below FL195 for relevant airspace in Brest ACC (2nd and final Step) .

Objective:


Project Category:

Airspace Structure

FRA

Originator(s):

FRA

Under study. To be done progressively. Final Step summer 2015.

Related proposals:

69.089a

69.089c

AARRNN VV--22001166 -- 22001199//2200


190 28 June 2016 Edition: 1.0

To further improve the airspace structure within France FIR. 69.089e

69.089f

75.073a

75.080


438.

Project Name: Paris Point Merge TE

Description: To implement the Point Merge TE (Paris ACC) for Paris TMA arrivals

from the north-east.

Objective:

To further improve the airspace structure while increasing the capacity of the sectors concerned, the decent profiles and sequencing of traffic with destination Paris TMA.


Project Category:


FRA BEL MUAC

Originator(s):

FRA FAB EC


439.

Project Name: ESSO - Espace Superieur du Sud Ouest

Description: To re-organize Bordeaux ACC upper airspace (military zones, route

network and sectorisation) taking into account both French civilian and military requirements (adaptation to the new training needs resulting from new aircraft and new weapons).

Objective:

To further improve the ATS route network and associated airspace structure both within Bordeaux UIR and at the interface between France UIR, Madrid UIR and Barcelona UIR, by segregating major traffic flows and creating specialised ATC sectors, in order to increase capacity, considering civil as well as military airspace requirements.


Project Group:

RFG SW

Project Category:

Airspace Structure Civil/Military Airspace

FRA ESP

Originator(s):

FRA ESP

Common project at the Barcelona/Madrid/Bordeaux interface (BAMBI) is part of this project.

Related proposals:

64.014b

66.053a

66.053b

66.053d


440.

Project Name: Barcelona, Madrid, Bordeaux Interface, BAMBI

Description: To re-organise the Barcelona/ Bordeaux interface as part of the

Barcelona/Madrid/Bordeaux (BAMBI) interface: 1. to implement PPG - ALBER dualization via new point EREPI. 2. to implement northbound trident GIROM - TIPAP - OKABI.

Objective:


Project Group:

RFG SW

Project Category:

Airspace Structure Civil/Military

FRA ESP

Originator(s):

FRA ESP

BAMBI: Common project at the Barcelona/ Madrid/ Bordeaux interface along the South-west axis.

a. Agreement with French military required.

Related proposals:

64.014c

64.014d

AARRNN VV--22001166 -- 22001199//2200


191 28 June 2016 Edition: 1.0

To further improve the ATS route network and associated airspace structure at the Barcelona FIR/ Bordeaux FIR interface by segregating major traffic flows in order to increase capacity, considering civil as well as military airspace requirements.

Airspace


441.

Project Name: Barcelona, Madrid, Bordeaux Interface, BAMBI

Description: To re-organise the Madrid/ Bordeaux interface as part of the

Barcelona/Madrid/Bordeaux (BAMBI) interface: 1. To re-design TSA 34 (enlargement). 2. To adjust ATS routes accordingly (LATEK area). 3. To change Madrid ACC sectors ZGZ/PAU/PAL accordingly.

Objective:

To further improve the airspace structure at the interface between Madrid FIR/UIR and Bordeaux FIR by enlarging TSA34 in response to future military needs and adjust ATS routes/ ATC sectors accordingly, considering civil as well as military airspace requirements.


Project Group:

RFG SW

Project Category:

Airspace Structure Civil/Military Airspace

FRA ESP

Originator(s):

FRA ESP

BAMBI: Common project at the Barcelona/ Madrid/ Bordeaux interface along the South-west axis.

Related proposals:

64.014b


442.

Project Name: S-WAFLE - South West Adaptation Flight Level Evolution Phase 2

Description:

To create an additional layer in Bordeaux ACC sectors L, R and P, Phase 2: 5th layer in sectors L and R (FL385+)

Objective:

To further improve the airspace structure and increase capacity within Bordeaux ACC in order to meet traffic demand.


Project Category:

ATC Sectors

FRA

Originator(s):

FRA

Phase 1: 4th layer in sector P (FL365+).

Related proposals:

84.018a


443.

Project Name: Free Route Airspace Georgia - FRAG Phase 2

Description: To expand existing H24 Free Route Airspace in Tbilisi CTA down to

FL085.

Objective:



Project Group:

SG BLACK

Project Category:

Free Route Airspace

GEO

Originator(s):

GEO

Related proposals:

85.009a / 21.023a


AARRNN VV--22001166 -- 22001199//2200


192 28 June 2016 Edition: 1.0

444.

Description: 1. To implement a new TMA for Tetouan (GMTN) Saniat R’mel airport. 2. To implement new SIDs and STARs for Tetouan (GMTN) Saniat

R’mel airport.

Objective: To further improve airspace structure around Tetouan (GMTN) Saniat

R’mel airport.


Project Category:


MAR

Originator(s):

MAR


445.

Description: 1. To implement new TMA for Al Hoceima (GMTA) Cherif El Idrissi

airport. 2. To implement new SIDs and STARs for Al Hoceima (GMTA) Cherif

El Idrissi airport.

Objective: To further improve airspace organisation around Al Hoceima (GMTA)

Cherif El Idrissi airport.


Project Category:


MAR

Originator(s):

MAR


446.

Project Name: INTRAC

Description: To design and publish RNAV SIDs and STARs for LMML airport.

Objective:

To further improve the airspace organisation within Malta FIR.


Project Category:


MLT

Originator(s):

EUROCONTROL

INTRAC/ New Terminal Routing Airspace Concept.


447.

Project Name: Free Route Airspace Warsaw FIR, Phase 4

Description: To implement full Free Route Airspace in Warsaw FIR FL305+.

Objective:

To further improve the airspace organisation and flight efficiency within Warszawa FIR (Polish Airspace Project 2010+, Phase 5).


Project Group:

SG BALTIC

Project Category:

Free Route Airspace

POL

Originator(s):

POL

Part of Polish Airspace Project 2010+

(Phase 5). No extension planned to lower FRA

operations within Warsaw FIR below FL305.

Related proposals:

62.091b

62.091c

76.052 / 23.029

Proposal ID : 60.010h / 15.046h Impl. Status: State(s) & Org. Comments:

448. Project Name: FRA Like (DCT) SMART, Phase 5


TUR

Planned, phased implementation: SMART: Systematic Modernization of ATM

AARRNN VV--22001166 -- 22001199//2200


193 28 June 2016 Edition: 1.0

Description: To allow Free Route flight during Night (DCTs) and Weekend (DCTs) above FL285.

Objective:

To further improve airspace organisation within Istanbul FIR and Ankara FIR and enhance capacity within the Turkish ACCs in order to cope with the increasing traffic demand (SMART project, Phase 5).

Project Group:

RFG SE

Project Category:

Free Route Airspace

Originator(s):

TUR Resources in Turkey.

2012 -2015: gradual implementation of DCTs during night or H24;

Nov 2013: full current airspace structure validation in SAAM, including en-route and TMA;

Nov 2013 - Spring 2014: detailed development of Free Route Airspace airspace design and associated sectorisation;

Autumn/Winter 2014/15 - RTS of new airspace structure;

Spring 2015 - Autumn 2015: fine-tuning of airspace design, airspace publication validation with NM, airspace structure testing in DNM systems;

Summer 2018: FRA implementation.

Related proposals:

60.010c

60.010f

60.010g / 15.046g

76.068 / 19.063


449.


Description:

To further reorganize vertical and horizontal TMA boundaries in Beograd FIR.

Objective:


Planned 24 MAY 2018

Project Group:

RFG SE

Project Category:

Airspace Structure

SRB MNE

Originator(s):

SRB MNE

Related proposals:

68.012a

68.012b

68.012c


450.

Project Name: Barcelona TMA, Phase 1

Description: To introduce new SIDs and STARs for LEBL airport, prior to the

implementation of new P-RNAV structure of Barcelona TMA.

Objective:

To further improve airspace organisation within Barcelona FIR.


Project Group:

RFG SW

Project Category:


ESP

Originator(s):

ESP

Project currently on hold, further update pending.

Related proposals:

66.085

AARRNN VV--22001166 -- 22001199//2200


194 28 June 2016 Edition: 1.0


451.

Project Name: Prestwick Lower Airspace - PLAS

Description: To re-design the Northern Terminal Control Area/ NTCA of Prestwick ACC (formerly Manchester TMA project).

Objective:

To further improve the airspace structure within London FIR through redesign in order to enhance safety, capacity and provide environmental improvements with expected traffic growth from airfields in Northern England.


Project Category:

PBN TMA

GBR

Originator(s):

GBR

To establish PRNAV procedures, revised SIDs that accommodate CCDs, revised STARs allowing CDAs from higher altitudes, improved arrival and departure management and holding concepts to include Point Merge, if and where considerate appropriate.

To consider specific requests for route improvements from the operators such as TNT - LAMIX and LIBSO - PEDIG.

Related proposals:

82.054


452.


Description: To truncate EGBB Northbound SIDs as follows:

a. WHI 4D Truncate at new waypoint LUVUM and become LUVUM 1D and use L8 to get to NANTI and use L8 to ASNIP and Y53 to WAL - removes requirement for DCT between WHI and WAL;

b. TNT 4D Truncate at new waypoint LEDLA and become LEDLA 1D and use T29 to get to TNT;

c. WHI 1L/TNT 1L Truncate at new waypoint ODUNU and become ODUNU 1L and use extended Y124 to get to NANTI and MOGTA and extended T29 to get from ODUNU to TNT (via LEDLA).

Objective:

To reduce portion of flight plan route fuelled at SID Altitude.


Project Category:

Airspace Structure ATM System

GBR

Originator(s):

GBR

Part 2 of Prestwick Lower Airspace - PLAS project.

Related proposals:

69.095a


453.

Project Name: Free Route Airspace Madrid / Brest

Description: To implement Free Route Airspace based on DCTs in Madrid FIR and

Brest FIR as a continuation of Free Route Airspace in Lisbon FIR.

Objective:

To further improve the airspace organisation between Lisbon FIR, Madrid FIR and Brest FIR.


Project Group:

FAB EC FAB SW

Project Category:

Free Route Airspace

PRT ESP FRA

Originator(s):

PRT ESP FRA FAB EC

Postponed from winter 2014/15 to winter 2017/18 after FRES/2 meeting.

FRAL - Free Route Airspace Lisbon FIR above FL245 implemented 7 May 2009.

Free Route Airspace SAN & ASI sectors/FRASAI, Phase 2 implemented 1 May 2014.

Related proposals:

64.030

73.051

AARRNN VV--22001166 -- 22001199//2200


195 28 June 2016 Edition: 1.0


454.

Project Name: Istanbul International Airport - Phase 1

Description: 1. To implement a new Istanbul international airport - northwest of

the city - having initially 3 (three) runways with the plan to extend up to six runways.

2. To re-organise the airspace of Istanbul FIR and Sofia FIR accordingly, if required.

Objective:

To further improve the airspace structure and to accommodate the traffic growth planned by Turkish airlines for the coming years.


Project Group:

RFG SE SG BLACK

Project Category:


TUR BGR

Originator(s):

TUR

LTBA and LTFJ airports will continue to be operational. LTBA might be devoted to other types of traffic.

That will also result in a major TMA re-design with significant network impacts.

Related proposals:

60.010h / 15.046h


455.

Description: To implement H24 Free Route Airspace in Yerevan ACC.

Objective:



Project Group:

SG BLACK

Project Category:

Free Route Airspace

ARM

Originator(s):

ARM

Related proposals:

83.030a / 21.003a


456.

Project Name: Common Terminal Airspace System

Description:

1. To implement a common Terminal Airspace System and implement P-RNAV procedures for Sofia (LBSF), Plovdiv (LBPD) and Graf Ignatievo (LBGI) airports.

2. To adjust the ACC sectors according to the future common TMA, if necessary.

Objective:

To further improve the airspace structure within Sofia FIR and to cope with the expected traffic increase.


Project Group:

RFG SE SG BLACK

Project Category:


BGR

Originator(s):

BGR

Implementation will be at least one year after introduction of P-RNAV procedures for Burgas (LBBG) and Varna (LBWN) airports..


457.

Project Name: Free Route Airspace Cyprus - FRANIC Phase 1

Description: To implement H24 Free Route Airspace FL285 - FL660 inNicosia FIR.

Objective:

To align the airspace structure with real operations. Operational DCT's to


Project Group:

FAB BLUE MED RFG SE

CYP

Originator(s):

CYP FAB BLUE MED

Studies ongoing in the context of Blue Med. Needs alignment with IDP & TEN-T.

Related proposals:

71.088b

86.056a

AARRNN VV--22001166 -- 22001199//2200


196 28 June 2016 Edition: 1.0

be made flight plannable Project Category:

Free Route Airspace

86.056b

86.056c


458.

Project Name: Barcelona TMA, Phase 2

Description: To introduce new P-RNAV structure for Barcelona (LEBL) TMA, Phase

2.

Objective:

To further improve airspace organisation within Barcelona FIR.


Project Group:

RFG SW

Project Category:

PBN TMA

ESP

Originator(s):

ESP

Project currently on hold, further update pending .

Related proposals:

73.053


459.

Project Name: Free Route Airspace Casablanca, Phase 1

Description:

To implement Night FRA based on DCTs in Western part of Casablanca FIR (Oceanic and West Sectors).

Objective:

To further improve the flight planning options within Casablanca FIR.


Project Category:


MAR

Originator(s):

MAR

Night period to be further defined.

Related proposals:

71.054


460.

Project Name: Free Route Airspace Casablanca, Phase 2 & Phase 3

Description:

1. To introduce Casablanca ACC dynamic sector management. 2. To implement Free Route during Night/Week-end within South and

East Sectors (Phase 2). 3. To implement Free Route within South Sector FL250+ (Full concept

Phase 3). 4. To implement Free Route for East/West traffic (Oceanic and West

Sectors).

Objective:

To further improve airspace organisation within Casablanca FIR.


Project Category:

Free Route Airspace

MAR

Originator(s):

MAR

Related proposals:

71.047


461.

Project Name: Free Route Airspace Turkey - Phase 1

Description: To implement Night FRA Operations above FL285 in Turkey.


Project Group:

RFG SE

TUR

Originator(s):

TUR EUROCONTROL

Turkey: within the sovereign airspace only. Night period 23.00 - 05.00 (22.00 - 04.00).

Related proposals:

AARRNN VV--22001166 -- 22001199//2200


197 28 June 2016 Edition: 1.0

Objective:

To implement FRA operations in Ankara and Istanbul FIRs SG BLACK

Project Category:

Free Route Airspace

81.022b / 19.061b


462.

Project Name: Free Route Airspace Ukraine, Step 2 (Sc 2a)

Description: To implement H24 - Free Route Airspace operations above FL275 -

Ukraine wide.

Objective:

To implement FRA Concept and further improve flight efficiency within Kyiv UIR.

Planned 08 NOV 2018

Project Group:

RFG SE SG BLACK

Project Category:

Free Route Airspace

UKR

Originator(s):

UKR

Free Route Airspace Ukraine - FRAU project

Related proposals:

71.040a / 16.026a

71.040b / 16.026b

81.018b / 19.021b


463.

Project Name: BH ATM, Phase 2

Description: To re-organise the airspace structure within Sarajevo FIR above FL325.

Objective:

To further improve the ATS route network and associated airspace structure in order to support the establishment of the new ACC within Sarajevo FIR (BH ATM Project, Phase 2).

Planned 06 DEC 2018

Project Group:

RFG SE

Project Category:

Airspace Structure

BIH HRV MNE SRB

Originator(s):

BIH

Phase 1: FL325 and below successfully implemented 13 NOV 2014. o Re-sectorisation required within Croatia

and Serbia. Close coordination with the Network

Manager and neighbouring ACCs. Phased implementation of Night DCTs and

H24 DCTs FL245+ planned. Postponed due to lack of ATCOs.

Related proposals:

60.006a


464.


Description: To implementation of Full Free Route Airspace Germany, Solution 2 H24 within South West - core area - (above FL385).

Objective:

To implement H24 Full FRA - according to PCP requirements and improve flight efficiency within FABEC.

Planned 06 DEC 2018

Project Group:

FAB EC

Project Category:

Free Route Airspace

DEU

Originator(s):

DEU FAB EC

Related proposals:

87.005a

87.005b

87.005c

87.005d


AARRNN VV--22001166 -- 22001199//2200


198 28 June 2016 Edition: 1.0

465.

Project Name: Free Route Airspace Moldova - Phase 3

Description: To implement H24 Free Route Airspace above FL285 within Chisinau FIR (NFRAC).

Objective:

To further improve the airspace organisation within Chisinau FIR.


Project Group:

RFG SE SG BLACK

Project Category:

Free Route Airspace

MDA

Originator(s):

MDA

Related proposals:

72.052 / 14.015

83.061 / 21.016

Proposal ID : 62.091e / 23.035 Impl. Status: State(s) & Org. Comments:

466.

Project Name: Polish Airspace Project 2010+, Phase 3b

Description:

To implement a new airspace structure and sectorisation within Warszawa ACC considering vertical splits (division into three layers),

including TMA connectivity and interface areas with neighbouring States.

Objective:

To further improve the airspace structure within Warszawa ACC and increase capacity while applying vertical splits.


Project Group:

SG BALTIC

Project Category:


POL

Originator(s):

POL

Depending on technical issues (frequencies) and increasing the amount of ATC staff.

New elementary sectors with vertical splits. Finally the division into three layers.

Related proposals:

62.091c


467.


Description: To extend H24 availability on Seasonal bases to all FLs of NIGHT Free Route Airspace within the DANUBE FAB area.

Objective:



Project Group:


Project Category:

Free Route Airspace

BGR ROU

Originator(s):

FAB DANUBE

Related proposals:

69.052 / 16.008

82.030 / 20.032

82.031 / 20.033

82.033 / 20.035


468.


Description: To expand to NIGHT and Weekends existing Free Route Airspace above FL245 within the Maastricht UAC AoR.

Objective:

To further improve the Free Route Airspace operations within Maastricht UAC.


Project Group:

FAB EC

Project Category:

Free Route Airspace

MUAC BEL DEU NLD

Originator(s):

MUAC FAB EC

Night period 23:00 - 05:00 (22:00 - 04:00). ATS route network and all allowed DCTs will

exist.

Related proposals:

87.036a

87.036c


AARRNN VV--22001166 -- 22001199//2200


199 28 June 2016 Edition: 1.0

469.


Description: To extend to full H24 above certain FL of NIGHT Free Route Airspace within the DANUBE FAB area.

Objective:



Project Group:


Project Category:

Free Route Airspace

BGR ROU

Originator(s):

FAB DANUBE

Related proposals:

69.052 / 16.008

82.030 / 20.032

82.031 / 20.033

82.032 / 20.034


470.

Project Name: Free Route Airspace Turkey - Phase 2

Description: To implement H24 FRA Operations above FL285 in Turkey.

Objective:

To implement FRA operations in Ankara and Istanbul FIRs.


Project Group:

RFG SE SG BLACK

Project Category:

Free Route Airspace

TUR

Originator(s):

TUR EUROCONTROL

Turkey: within the sovereign airspace only.

Related proposals:

81.022a / 19.061a


471.

Project Name: Free Route Airspace Ukraine, Step 2 (Sc 2b)

Description: To extend implementation of H24 - Free Route Airspace operations in entire Class C Airspace - Ukraine wide.

Objective:

To implement FRA Concept and further improve flight efficiency within L'viv CTA/UTA, Kyiv CTA/UTA, Odesa CTA/UTA and Dnipropetrovs'k CTA/UTA.

Proposed 2019

Project Group:

RFG SE SG BLACK

Project Category:

Free Route Airspace

UKR

Originator(s):

UKR

Class C Airspace, in Ukraine, at present - (year 2014) is at FL105 and above.

Related proposals:

71.040a / 16.026a

71.040b / 16.026b

81.018a / 19.021a


472.

Project Name: New Cross-Border Coordination Concept

Description:

To implement a new cross-border coordination concept as opposed to the current way of working, exchange of flights between centres will not be based solely on points, but will be organized via "gates" or "windows".

Objective:

To flexibilize the exchange of flights between adjacent centres and prepare for FRA implementation.


Project Category:

Airspace Structure ATC Sectors ATM System Free Route Airspace

CHE DEU FRA ITA FAB EC

Originator(s):

CHE FAB EC

Related proposals:

87.056a

87.056b

AARRNN VV--22001166 -- 22001199//2200


200 28 June 2016 Edition: 1.0

RAD


473.

Project Name: FRA Switzerland Night - Phase 1

Description: To implement (full) Free Route Airspace during Night within Zurich and

Geneva AoRs.

Objective:

To improve flight efficiency during night and gain experience with (full) Free Route operations.


Project Category:

Free Route Airspace

CHE DEU FRA ITA FAB EC

Originator(s):

CHE FAB EC

Related proposals:

87.055

87.056b


474.

Project Name: Berlin Brandenburg International (BER) airport

Description:

New Berlin Brandenburg International (BER) airport: a. to establish a second runway at BER airport (current Berlin

Schoenefeld airport);

b. to establish independent parallel runway operations; c. new/modified SIDs/STARs; d. operational procedures; e. to adjust Terminal sectors; f. one additional departure sector; g. to raise the DFL from FL165 to FL205.

Objective:

To further improve the airspace structure within Bremen FIR by expansion of Berlin Schoenefeld airport to become Berlin Brandenburg International (BER) airport.


Project Category:


DEU

Originator(s):

DEU

EDDB:The planned openings of the new Berlin Brandenburg International (BER) airport on 03.06.2012 and 27.10.2013 were postponed.

EDDT : Berlin-Tegel planned to be closed same time as EDDB is in operation.

Possible ATFM Regulations due to acclimatization of ACC and TWR staff (new airspace C structure and DEP/ARR procedures).

RNDSG/81 DEU: to be on hold when more details will be availble in the future.

Related proposals:

65.011c

70.063


475.

Project Name: Sachsen/ SAS Upper sector

Description: To implement a Sachsen/ SAS Upper sector.

Objective:

To further improve the airspace structure while balancing traffic/workload and consequently increasing capacity within Bremen FIR to meet traffic demand.


Project Category:

ATC Sectors

DEU

Originator(s):

DEU

Depending on traffic evolution/demand and FRA implementation as well as the opening of the BER airport.

Related proposals:

64.031


476. Project Name: Borealis FRA - Step 6

Proposed GBR

AARRNN VV--22001166 -- 22001199//2200


201 28 June 2016 Edition: 1.0

Description: To implement H24 Free Route Airspace above FL 255 within the whole Prestwick ACC AoR and in parts of London ACC AoR above FL335.

Objective:


spring 2020

Project Group:


Project Category:

Free Route Airspace

Originator(s):


Transition on to Free Route operations with

potential Cross Border DCTs with adjacent States.

Above some specific ACC sectors, FRA operations will start only above FL285.

Related proposals:

81.073a

87.028a

87.028b

87.028c

87.028d

87.028e

87.028g


477.


Description: To expand to H24 existing Free Route Airspace above FL245 within the

Maastricht UAC AoR.

Objective:

To further improve the Free Route Airspace operations within Maastricht UAC.


Project Group:

FAB EC

Project Category:

Free Route Airspace

MUAC BEL DEU NLD

Originator(s):

MUAC FAB EC

ATS route network and all allowed DCTs will be deleted.

Related proposals:

87.036a

87.036b


478.

Project Name: New runway Dublin Airport (EIDW)

Description: a. To build a new north parallel runway for Dublin Airport (EIDW).

b. To develop SIDs and STARs for the new north parallel runway at Dublin airport.

Objective:

To further improve the airspace structure within Shannon UIR, to increase capacity and further enhance the efficiency of ATM operations at Dublin airport.


Project Category:

Airspace Structure

IRL

Originator(s):

IRL

Depending on traffic evolution, subject to growth to 23.5 M pax/y.

Related proposals:

65.051a


479. Project Name: Langen 2.0

Proposed 2020

DEU

Phased implementation with early implementation steps before 2020.

AARRNN VV--22001166 -- 22001199//2200


202 28 June 2016 Edition: 1.0

Description:

To re-design Langen ACC sectors completely, based on traffic flows.

Objective:

To further improve the airspace organization within Germany.

Project Category:

ATC Sectors

Originator(s):

DEU


480.

Description: To implement southbound ATS route segment BAKOR - CHI - TEA.

Objective:

To further improve the ATS route network while offering a shorter route in the north/eastern part of Italian airspace.

Proposed 2020

Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA

Originator(s):

FAB BLUE MED

To be further evaluated by Italy.


481.

Description: To implement bidirectional ATS route segment ARNOS - ROSKA.

Objective:

To further improve the ATS route network while offering a shorter route in the northern part of Italian airspace.

Proposed 2020

Project Group:

FAB BLUE MED

Project Category:

ATS Routes

ITA SVN

Originator(s):

FAB BLUE MED

LI R49 interference; Complex coordination.


482.

Project Name: FAIR-IT Free Route Airspace Italy, Phase 4

Description: To extend the Free Route Airspace from above FL335 down to FL315.

Objective:

To further improve the airspace structure and the flight planning options within Milano, Roma and Brindisi UIR.

Proposed 2020

Project Group:

RFG SE

Project Category:

Free Route Airspace

ITA

Originator(s):

ITA

Developments in line with PCP.

Related proposals:

71.085a

71.085b

71.085c

71.089c

- END -

Contact details

EUROCONTROL

© June 2016 – European Organisation for the Safety of Air Navigation (EUROCONTROL)

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

DNM/COO/NOM/[email protected]