This section describes the use cases related the eFPL usage by ANSPs.
Status
Use of eFPL for Visualisation
General Description
Several items of the eFPL can be displayed to various actors in an ACC for enhancing their situational awareness and satisfying additional information needs.
- Use of the eFPL data as an analysis tool – for learning purposes and training
- Visualisation of eFPL data as a Fall back mechanism, should the system encounter failure
- Visualisation of eFPL data enabling to perform ATC even when radar contact has been lost (Lack of contact with AU, procedural separation mechanisms)
Relevant eFPL content
These items include:
- Agreed 4D Trajectory
- Unconstrained Trajectory
To be clarified: is this the desired trajectory captured in the filed eFPL, or the performance profile, which a zero-wind, standard atmosphere profile reflective of the flight capabilities and desired parameters.
- Trajectory Change Points (TCP)
- FPL2012 Field 15
Actors
- Flight Data Assistant
- Flow Manager
- Supervisor
- Coordination Controller
- Executive Controller
Use of eFPL for Flow Management (Traffic Complexity Tools)
General Description
The information of the eFPL can be used in Flow- and Complexity Tools in order to improve the quality of the respective forecasts and the related planning for sector configurations and staff allocation.
By taking the first step of accepting FF-ICE flight plans through the filing service, ASPs would gain access to more detailed trajectory information. This would be useful for strategic traffic flow management purposes, at the same time allowing ASPs to explore/develop other capabilities made possible by the additional trajectory information. ASPs will be able to gain experience in using the trajectory information and hence better build up their system capabilities for information processing, ……
Relevant eFPL content
Take-off Mass ( Would be used in EFD)
Performance data: performance profile, speed schedule ( Would be used in EFD)
Agreed 4D Trajectory
Trajectory Change Points (TCP)
FPL2012 Field 15
Actors
Flow Manager
Supervisor
Use of eFPL data in Core ATC system (FDPS)
General Description
The information of the eFPL can be used in various components of the core ATS-System, where flight plan information is used and needed. The mainly affected component would be the Flight Data Processing System (FDPS), but also other components could benefit directly or indirectly from eFPL information, e.g. Arrival Management Systems and Conflict Detection Tools
Relevant eFPL content
- Take-off Mass:
- Displaying the take-off mass to the ATCO with an indication whether this is considered heavy for such A/C type could give an indication on whether some ROCD can be made or not, without the ATCO having to ask, thus saving frequency time.
- As an example, A320 is categorised as ”medium” but could be an actual ”heavy”
- as input to the local trajectory computation
- Displaying the take-off mass to the ATCO with an indication whether this is considered heavy for such A/C type could give an indication on whether some ROCD can be made or not, without the ATCO having to ask, thus saving frequency time.
- Performance data:
- Performance profile
- Speed schedule
- Agreed 4D Trajectory
- Trajectory Change Points (TCP)
- In today's operations, ANSP systems commonly ignore, or make assumptions on, level constraints and “clip them out”. This operationally leads to (1) clearances instructed by the ATCO (e.g. instructs FL350, while the clipped out level was FL300) and (2) sometimes intruders to our next partner. Especially if we know levels because of regulations, situation (2) would no longer occur. The information about the reason why a level constraint is present in the trajectory (for instance, PTR or regulation) will help avoid (2)
- FPL2012 Field 15
Actors
- Supervisor
- Coordination Controller
- Executive Controller