Summary - FF-ICE Data item presence in the distributed eFPL
WORK IN PROGRESS
The table below provides a recap of the rules on the presence of fields for the distributed eFPL (i.e. the eFPL sent by NM to ANSPs). The table follows the same conventions as the previous table and can be read in a similar manner.
The distributed eFPL is sent by NM to ANSPs using the FF-ICE Publication Service. ICAO Doc 9965 Ed2 Volume 2 does NOT specify the FF-ICE Messages exchanged by this Publication Service. As a result:
no tabular description of the distributed eFPL can be found in Appendix C of ICAO Doc 9965 Ed2 Volume 2. The table shown below is however inspired by ICAO Doc 9965 Ed2 Volume 2, chapters C-4 Filed Flight Plan and C-5 Filing Status, with altogether provides a good baseline for outlining the content of the distributed eFPL.
no XML message template exists in the FIXM "FF-ICE Message" Application 1.1.0 that can support the exchange of the distributed eFPL. The NM B2B Publication Services actually exchanges the distributed eFPL using a message named “FficePublicationMessage”, which is a bespoke NM B2B message. This message, however, still uses FIXM Core 4.3.0 for the representation of the flight data. It should be noted that all flight data items in FIXM Core 4.3.0 are declared optional. Therefore, for readability purpose, the column "From FIXM" outlining the requirements on the presence of fields is not shown in the table below.
Content of |
| Requirements on Data Item presence in | |||||
Data Category | Data Item | Mandatory in filed eFPL? | From | From | Aggregated Requirements | NM R27 | Notes / Justifications |
|---|---|---|---|---|---|---|---|
Flight Identification | GUFI | Yes | M |
| M |
| |
Aircraft Identification | Yes | - |
| M |
| ||
Flight Status | Operator Flight Plan Version | Yes | M |
| M |
| |
Flight Characteristics | Flight Rules | Yes | M |
| M |
| |
Type of Flight | Yes | M |
| M |
| ||
Special Handling | No | - |
| O |
| ||
Flight Plan Originator | No | - |
| O |
| ||
Remarks | No | - |
| O |
| ||
Operator | No | - |
| O |
| ||
Equipment and Capabilities | Yes | M |
| M |
| ||
Supplementary Information Source | No | - |
| O |
| ||
Required Runway Visual Range | No | - |
| O |
| ||
Aircraft Characteristics | Total number of aircraft | No | - |
| O |
| |
Registration | No | - |
| O |
| ||
Aircraft Address | No | - |
| O |
| ||
SELCAL Code | No | - |
| O |
| ||
Mode A Code | No | - |
| O |
| ||
Number and type of aircraft | Yes | M |
| M |
| ||
Wake Turbulence Category | Yes | M |
| M |
| ||
Aircraft Approach Category | No | - |
| O |
| ||
Departure/Destination Data | Departure Aerodrome | Yes | M |
| M |
| |
Destination Aerodrome | Yes | M |
| M |
| ||
Estimated Off-Block Time | Yes | M |
| M |
| ||
Departure Airport Slot Identification | No | - |
| O |
| ||
Destination Airport Slot Identification | No | - |
| O |
| ||
Departure Runway | No | - |
| O |
| ||
Destination Runway | No | - |
| O |
| ||
Alternates | Alternate Destination Aerodrome(s) | No | - |
| O |
| |
Alternate Take-Off Aerodrome(s) | No | - |
| O |
| ||
Alternate En-Route Aerodrome(s) | No | - |
| O |
| ||
Agreed Route/Trajectory | N/A | M |
| M |
| ||
Route/Traj. Group | Aircraft Take-off Mass | Yes | M (Cond) |
| M (Cond) |
| |
Requested Cruising Speed | Yes | - |
| M |
| ||
Requested Cruising Level | Yes | - |
| M |
| ||
Total Estimated Elapsed Time | Yes | - |
| M |
| ||
General Flight Constraint | No | - |
| TBD |
| ||
Route/Traj. Element | Yes | M (2+) |
| M (2+) |
| ||
| Along Route Distance | Yes | - |
| M |
| |
Route Element Start Point | Yes | - |
| M |
| ||
Route to Next Element | No | - |
| O |
| ||
Modified Route Indicator | No | - |
| O |
| ||
Route Truncation Indicator | No | - |
| O |
| ||
Requested Change | No | - |
| O |
| ||
Route/Trajectory Constraints | No | - | |||||