Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
borderColorblack
borderStyledashed
Excerpt

This section summarises the CP1 regulatory framework, its geographical scope and affected stakeholders, and outlines the expected operational benefits of the FF-ICE implementation in Europe.

Table of Contents
maxLevel1
absoluteUrltrue
typeflat
separatorpipe

Warning
titleStatus
WORK IN PROGRESS - content should not be used
Panel
titleFull table of contents

Table of Contents

Regulatory framework

The deployment of FF-ICE and its related requirements falls under the umbrella of Commission Implementing Regulation (EU) No 116/2021 (CP1) that replaced (EU) No 716/2014 of 27 June 2014, known as the “Pilot Common Project (PCP)”. FF-ICE R1 Services are to be deployed in a timely, coordinated and synchronised way, such as all ATM functionalities that are mature for implementation and that contribute to the achievement of the essential operational changes identified in the European ATM Master Plan.

Geographical scope & affected stakeholders

All operational stakeholders in the European Air Traffic Management Route Network (EATMN), with the exception of airports, must deploy FF-ICE service. This includes the Network Manager, AUs and ANSPs.

Clarification of the term EATMN

The EATMN is defined in (EU) 549/2004 as follows:

‘European air traffic management network’ (EATMN) means the collection of systems listed in Annex I to Regulation (EC) No 552/2004 of the European Parliament and of the Council of 10 March 2004 on the interoperability of the European air traffic management network (the interoperability Regulation) enabling air navigation services in the Community to be provided, including the interfaces at boundaries with third countries;

Annex I to Regulation (EC) No 552/2004 further clarifies that

For the purpose of this Regulation the EATMN is subdivided into eight systems.
1.    Systems and procedures for airspace management.
2.    Systems and procedures for air traffic flow management.
3.    Systems and procedures for air traffic services, in particular flight data processing systems, surveillance data processing systems and human-machine interface systems.
4.    Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air communications.
5.    Navigation systems and procedures.
6.    Surveillance systems and procedures.
7.    Systems and procedures for aeronautical information services.
8.    Systems and procedures for the use of meteorological information

Affected Airspace Users

CP1 mandates all Airspace Users operating in the EATMN Airspace – including overflights – to adopt FF-ICE. In other terms, all Airspace Users operating in the EATMN Airspace must start filling eFPL by 31/12/2025 at the latest.

  • This understanding of the implementation requirement has been clarified and agreed with the European Commission in a bilateral meeting EC-SDM on October 6th 2022.

CP1 also applies to military when they fly GAT, but does NOT apply to OAT:

CP1 does not apply to OAT
  • Clarified by the European Commission on February 28th 2023.
Note
  • .


Affected Air Navigation Service Providers

The European Commission confirmed that this CP1 applied for the EATMN, so for the entire European airspace plus two states (Switzerland and Norway).


Expected operational benefits in Europe

TODO

Supporting materials

Browse the presentation "Introduction to the FF-ICE requirements in CP1 and in the SESAR Deployment Programme" to the NDOP/NDTECH Joint Session on FF-ICE on 01-Mar-2023:

Expand

PDF
nameFF-ICE requirements in CP1 and in the SESAR Deployment Programme.pdf


Browse the presentation "Expected FF-ICE Short/Medium/Long term operational benefits" to the NDOP/NDTECH Joint Session on FF-ICE on 01-Mar-2023:

Expand

PDF
nameExpected FF-ICE Short-Medium-Long term operational benefits.pdf


Browse the "Note on Airspace Users CP1 mandate to implement FF-ICE Release 1", published by SDM on October 18th, 2022:

Expand

PDF
nameAU FF-ICE Mandate.pdf