FF-ICE in the EU CP1 regulation
- LEPORI Hubert
- WILSON Scott
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.
Status
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
For FF-ICE/R1 Services, the geographical scope is the EATMN (European Air Traffic Management Route Network) which in the context of CP1 means
the 27 EU Member States + Norway and Switzerland + SOTA and NOTA of Shanwick FIR.
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
For FF-ICE/R1, all General Air Traffic [GAT] operating IFR or mixed VFR/IFR within the geographical scope is concerned, including overflights.
The following ANSPs are affected by the CP1 requirements related to FF-ICE/R1
- The ANSPs operating the ACCs within the geographical scope.
- The ANSPs operating the TWR and TMAs in the airport referred to in point 1.2 of the CP1 regulation, namely Adolfo Suarez Madrid-Barajas; Amsterdam Schiphol; Barcelona El Prat; Berlin Brandenburg Airport; Brussels National; Copenhagen Kastrup; Dublin; Düsseldorf International; Frankfurt International; Milan-Malpensa; Munich Franz Josef Strauss; Nice Cote d’Azur; Palma De Mallorca Son Sant Joan; Paris-CDG; Paris-Orly; Rome-Fiumicino; Stockholm-Arlanda; Vienna Schwechat.
Clarification of the CP1 mandate
The CP1 regulation states that:
(a) related to FF-ICE Release 1 Services:
- flight plan and routes generation and validation;
- flight plans, 4D trajectory, flight performance data, flight status;
- flights lists and detailed flight data;
These statements in CP1 context means:
- routes generation and validation: “routes generation” relates to the Expanded Route as described in the FF-ICE/R1 Manual, Appendix E-3. (An expanded route contains every significant point that is in the route. While a Route has only the entry and exit point from each ATS route traversed, the expanded route contains each significant point traversed along each ATS route.). “validation” relates to the outcome of the flight plan validation and is an aspect covered in bullet point 4) Flight Status below.
- 4D trajectory: this relates to the Trajectory information provided as part of the Route/Trajectory Group, as explained in the FF-ICE/R1 Manual, Appendix E-3.
- flight performance data: this relates to the Route/Trajectory Specific Performance Data as described in the FF-ICE/R1 Manual, Chapter 10.3, table 2. It comprises the Aircraft Take-Off Mass, the Performance climb and descent profile and the Climb and descent speed schedule.
- Flight status: this relates to the Operator Flight Plan Version and the Filing Status value that are specified in the FF-ICE/R1 Manual, Appendix B-2.14 and B-2.23.2. Note: The term "Flight Status” used in CP1 does NOT refer to Field 18 STS, sometimes called status field, which captures the Reason for special handling by ATS. In FF-ICE, this piece of information is explicitly represented by the Data Item “Special Handling” in Data Category “Flight Characteristics”.
- flights lists: the notion of "Flights Lists" is not described in the FF-ICE/R1 Manual. It is therefore considered that this particular wording relates to the use of the GUFI to assist in associating a message to the correct flight and to help in distinguishing between similar flights, as explained in the FF-ICE/R1 Manual, chapter 3.7.1;
- detailed flight data: This relates to the eFPL content that is not new compared to what is currently exchanged, i.e. this relates to the flight plan data items already exchanged in FPL 2012 format.
Expected operational benefits in Europe
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:
Working Draft