Use

Case categories

1. Use of the eFPL data as an analysis tool – for learning purposes and training
2. Visualisation of eFPL data as a Fall back mechanism, should the system encounter failure
3. 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

• 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

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

General Description

Relevant eFPL content

Actors

Use of the distributed eFPL by an ANSP

The data contained in the eFPL can be used by an ANSP in different ways:

ATC related

• Several items of an eFPL can be displayed to various actors in an ACC (Flight Data Assistant, Flow Manager, Supervisor, Coordination Controller, Executive Controller) for enhancing their situational awareness and satisfying additional information needs. For instance:
  
  • 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)
• 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.

ATFM related

• 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, as acknowledged in the ICAO FF-ICE Implementation Guidance Manual, Section “Implementation Strategy”
  • 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, …

The following table provides 

Overview

Content of the distributed eFPL		Use Cases
Data Category	Data Item
Flight Identification	GUFI
	Aircraft Identification
Flight Status	Operator Flight Plan Version
	Revalidation Status
	Revalidation Status Explanation
Flight Characteristics	Flight Rules
	Type of Flight
	Special Handling
	Flight Plan Originator
	Remarks
	Operator
	Equipment and Capabilities
	Supplementary Information Source
	Required Runway Visual Range
Aircraft Characteristics	Total number of aircraft
	Registration
	Aircraft Address
	SELCAL Code
	Mode A Code
	Number and type of aircraft
	Wake Turbulence Category
	Aircraft Approach Category
Departure/Destination Data	Departure Aerodrome
	Destination Aerodrome
	Estimated Off-Block Time
	Departure Airport Slot Identification
	Destination Airport Slot Identification
	Departure Runway
	Destination Runway
Alternates	Alternate Destination Aerodrome(s)
	Alternate Take-Off Aerodrome(s)
	Alternate En-Route Aerodrome(s)
Desired Route/Trajectory
Agreed Route/Trajectory		Display of the Agreed Route/Trajectory to the ATCO when radar contact has been lost
Route/Traj. Group	Aircraft Take-off Mass	Processing of the Aircraft Take-off Mass by the FDPS Display of the Aircraft Take-off Mass to the ATCO
	Requested Cruising Speed
	Requested Cruising Level
	Total Estimated Elapsed Time
	General Flight Constraint
Route/Traj. Element
	Along Route Distance
	Route Element Start Point
	Route to Next Element
	Modified Route Indicator
	Route Truncation Indicator
	Requested Change
	Route/Trajectory Constraints
	Trajectory Point
	Geo Position
	Time
	Predicted Airspeed
	Predicted Ground Speed
	Wind Vector
	Assumed Altimeter Setting
	Temperature
	Trajectory Point Property
	Weight at 4D Point
	Planned Delay
Route/Traj. Aircraft Performance	Performance Profile	Processing of the Performance Profile by the FDPS
	Speed Schedule	Processing of the Speed Schedule by the FDPS
Route to Revised Destination	Revised Destination
	Route String to Revised Destination
Dangerous Goods	Dangerous Goods Information
AIRAC	AIRAC Reference
Supplementary Information	Fuel Endurance
	Persons on Board
	Emergency Radio
	Survival Capability
	Life Jacket Characteristics
	Aircraft Colour and Markings
	Pilot in Command
	Dinghies
	Remarks
Other European Items	Route Text
	Ifps Identifier
	Stay Information
	AO What-If ReRoute Indicator
	Replacement Flight Plan Indicator

Use cases descriptions

Processing of the Aircraft Take-off Mass for trajectory computation

Display of the Aircraft Take-off Mass to the ATCO

Processing of the Performance Profile by the FDPS

Processing of the Speed Schedule by the FDPS

Expand

Name Processing of the Speed Schedule by the FDPS Category Actors Main: ANSP FDPS Other: NM Publication Service Preconditions the NM Publication Service is consumed by the ANSP the Speed Schedule is provided by the AU in the filed eFPL the Speed Schedule provided in the filed eFPL is shared by NM in the distributed eFPL Trigger A distributed eFPL containing a Speed Schedule is received by the ANSP. Description TODO ...

Display of the Agreed Route/Trajectory to the ATCO when radar contact has been lost