Commission Implementing Regulation (EU) 2021/116 of 1 February 2021 on the establishment of the Common Project One supporting the implementation of the European Air Traffic Management Master Plan provided for in Regulation (EC) No 550/2004 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 409/2013 and repealing Commission Implementing Regulation (EU) No 716/2014 (Text with EEA relevance)

The Common Project One (‘CP1’) is established to support the implementation of the European Air Traffic Management (‘ATM’) Master Plan.

For the purposes of this Regulation, the definitions set out in Article 2 of Implementing Regulation (EU) No 409/2013 shall apply. The following definitions shall also apply: (1) ‘airport – collaborative decision making’ or ‘A-CDM’ means a process by which decisions related to air traffic flow and capacity management (‘ATFCM’) at airports are made on the basis of interaction between operational stakeholders and other actors involved in ATFCM and which aims at reducing delays, improving the predictability of events, optimising the utilisation of resources and reducing environmental impacts. (2) ‘airport operations plan’ or ‘AOP’ means a single, common and collaboratively agreed rolling plan available to all relevant operational stakeholders which provides a common situational awareness for optimised processes; (3) ‘network operations plan’ or ‘NOP’ means a plan, including its supporting tools, developed by the Network Manager in coordination with the operational stakeholders to organise its operational activities in the short and medium term in accordance with the guiding principles of the network strategic plan and which includes, for the European route network design-specific part of the network operations plan, the European route network improvement plan; (4) ‘to operate an ATM functionality’ means putting in service the ATM functionality in question which is fully used in daily operations; (5) ‘AF 1’ or ‘extended arrival management and integrated arrival management (‘AMAN’)/departure management (‘DMAN’) in the high-density terminal manoeuvring areas’ means an ATM functionality that improves the precision of the approach trajectory and facilitates air traffic sequencing at an earlier stage and the optimum utilisation of runways, integrating the AMAN and DMAN sequences, by deploying specific ATM solutions.; (6) ‘AF 2’or ‘airport integration and throughput’ means an ATM functionality that facilitates the provision of approach and aerodrome control services by improving runway safety and throughput, enhancing taxi integration and safety and reducing hazardous situations on the runway; (7) ‘AF 3’ or ‘flexible airspace management and free route airspace’ means an ATM functionality that combines the operation of flexible airspace management and free route and enables airspace users to fly as closely as possible to their preferred trajectory without being constrained by fixed airspace structures or fixed route networks. It allows operations that require segregation to take place safely and flexibly and with minimum impact on other airspace users; (8) ‘AF 4’ or ‘network collaborative management’ means an ATM functionality that improves the European ATM network performance, notably capacity and flight efficiency, through exchange, modification and management of trajectory information. AF 4 contributes to the implementation of a collaborative network for planning and decision-making, which enables the implementation of flight- and flow-centric operations; (9) ‘AF 5’ or ‘system wide information management (SWIM)’ means an ATM functionality that consists of standards and infrastructure enabling the development, implementation and evolution of services for information exchange between operational stakeholders via interoperable services which are built on SWIM standards and are delivered through an internet protocol; (10) ‘AF 6’ or ‘initial trajectory information sharing’ or ‘i4D’ means an ATM functionality that improves the use of target times and trajectory information, including where available the use of on-board 4D trajectory data by the ground ATC system and Network Manager systems, implying fewer tactical interventions and improved de-confliction situation.

1 The CP1 shall comprise the following ATM functionalities: (a) extended arrival management and integrated AMAN/DMAN in the high-density terminal manoeuvring areas; (b) airport integration and throughput; (c) flexible airspace management and free route airspace; (d) network collaborative management; (e) system wide information management; (f) initial trajectory information sharing.

2 The operational stakeholders identified in the Annex to this Regulation shall implement the ATM functionalities referred to in paragraph 1 and implement the associated operational procedures in accordance with the Annex to this Regulation. The military operational stakeholders shall deploy those ATM functionalities only to the extent necessary to comply with the fourth and fifth subparagraphs of point 3.2 of Annex VIII to Regulation (EU) 2018/1139 of the European Parliament and of the Council .

1 Common projects shall identify the ATM functionalities and their sub-functionalities. Those functionalities and sub-functionalities shall be based on SESAR solutions addressing the essential operational changes defined in the European ATM Master Plan, shall be ready for implementation and shall require synchronised implementation. Readiness for implementation shall be assessed, inter alia, based on the results of validation carried out during the development phase, the status of industrialisation and an assessment of interoperability, as well as in relation to the International Civil Aviation Organization (‘ICAO’) Global Air Navigation Plan and relevant ICAO material.

2 Common projects shall set out for each ATM functionality and sub-functionality the following characteristics: (a) essential operational changes they contribute to; (b) the operational and technical scope; (c) the geographical scope; (d) the operation stakeholders that are required to implement them; (e) the synchronisation requirements; (f) the implementation target dates; (g) the interdependencies with other functionalities or sub-functionalities.

3 By way of derogation from paragraph 1, common projects may also include ATM functionalities or sub-functionalities that are not ready for implementation but that constitute an essential component of the common project concerned and provided that their industrialisation is deemed to be finalised within three years from the adoption of the concerned common project. For that purpose, an industrialisation target date for those ATM functionalities or sub-functionalities shall also be defined in the common project.

4 At the expiry of the industrialisation target date, the Commission, with the support of the European Union Aviation Safety Agency, shall verify that the ATM functionalities or sub-functionalities referred to in paragraph 3 have been standardised and that they are ready for implementation. Where they are found not to be ready for implementation, they shall be withdrawn from the common project regulation.

5 The deployment manager, the SESAR Joint Undertaking, the European standardisation organisations, Eurocae and the relevant manufacturing industry shall cooperate under the coordination of the European Union Aviation Safety Agency to ensure that the industrialisation target date is met.

6 Common projects shall also: (a) be consistent with and contribute to the European Union-wide performance targets; (b) demonstrate a positive business case for the EATMN, based on cost-benefit analysis, and identify any potential local or regional negative impact for any specific category of operational stakeholders; (c) take account of the relevant deployment elements specified in the Network Strategy Plan and the Network Operations Plan of the Network Manager; (d) demonstrate an improved environmental performance.’;

1 The deployment programme shall provide a comprehensive and structured work plan of all activities necessary to implement technologies, procedures and best practices required to implement common projects. The deployment programme shall specify the technological enablers for implementing the common projects.

2 The deployment programme shall define how the implementation of common projects shall be synchronised within the EATMN, taking into account local operational requirements and constraints.

3 The deployment programme shall constitute the references for all operational stakeholders required to implement common projects and for the management and implementation levels. The operational stakeholders shall provide the deployment manager with relevant information concerning the implementation of deployment programme. The deployment programme shall be part of the framework partnership agreement and, as such, all the beneficiaries shall commit to implement it.’.

Regulation (EU) No 716/2014 is repealed.

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.