/
Summary - FF-ICE Data item presence in the submitted eFPL

Summary - FF-ICE Data item presence in the submitted eFPL

2024 Apr 26

    WORK IN PROGRESS

     

     

    The table below provides a recap of the rules on the presence of fields for the submitted eFPL. The table should be read as follows:

    • Columns 1 and 2 contains the name of the Data Category and Data Item as listed in ICAO Doc 9965 Ed2 Volume 2 (the FF-ICE/R1 Implementation Guidance Manual), chapter C-4 Filed Flight Plan. A data item displayed in italic is an FF-ICE data item that is specific to Europe.

      • Use of symbol indicates that the FF-ICE Data Item is new in the eFPL compared to the legacy FPL content.

    • Columns 3 to 7 describe the rules on the presence of the FF-ICE Data Item in the submitted eFPL.

      • Column 3 indicates whether the data item is declared Mandatory (M) or Optional (O) in the message template for the filed flight plan provided by FIXM's FF-ICE Message Application 1.1.0, which generally reflect the rules on the presence of fields from ICAO Doc 9965 Ed2 Volume 2, Appendix C.

      • Column 4 indicates whether the data item is considered mandatory (M) as per CP1. Use of the character "-" indicates that CP1 does not specify any rule for that item.

      • Column 5 indicates whether the data item is considered Mandatory (M), Optional (O), forbidden (F), or not needed by NM. Use of the character "-" indicates that no rules are specified on top of what FIXM specifies.

      • Column 6 indicates whether the data item is considered Mandatory (M) from the perspective given OUTDATED - Use cases (ANSPs).

      • Column 7 provides the aggregated rule on the presence of the data item, which corresponds to the most stringent of the FIXM, CP1, NM and Use Cases rules.

    • Column 8 provides an indication whether the data item is supported by the current NM systems, based on the NM B2B R27 documentation. Use of symbol means that the data item is supported by the NM B2B R27 Filing Service. Use of symbol indicates that data item is either partly supported (e.g. can be received but cannot be processed yet) or not supported.

    • Column 9 may capture additional notes in relation to the requirements on the data item presence, such as the justification for a particular CP1 requirement that is more stringent than what ICAO specifies.

     

     

    Content of
    the filed eFPL

    Requirements on Data Item presence in
    the filed eFPL



    Data Category

    Data Item

    From
    FIXM

    From
    EU CP1

    From
    NM B2B

    Aggregated Requirement

    NM R27
    Capabilities

    Notes / Justifications

    Message Information




    List of Recipients

    O

    -

    Not needed

    Not needed

    The FIXM template leaves these fields optional, even though they are described as mandatory in ICAO Doc 9965 Ed2 Volume 2 Appendix C-4, to allow these fields to be absent from the XML body of the FF-ICE message if they can be exchanged/retrieved through other means, as is the case in the NM B2B implementation.

    Message Originator

    O

    -

    Not needed

    Not needed

    Request for Translation and Delivery

    O

    -

    Not needed

    Not needed

    This item identifies the eASP that has been requested to translate and deliver the Flight Plan to identified Requested Recipients. In the context of the European implementation of FF-ICE, this eASP is always NM. The information is therefore implicit and the field is irrelevant.

    Requested Recipients

    O

    -

    -

    O

    This implements the (IFPS Users Manual) Re-addressing Function.

    Request for Forwarding

    O

    -

    Not needed

    Not needed

    This item identifies the eASP that is requested to forward the Flight Plan to all Relevant ASPs. In the context of the European implementation of FF-ICE, this eASP is always NM. The information is therefore implicit and the field does not need to be provided.

    Relevant ASPs

    M

    -

    M

     

    Message Date-Time

    O

    -

    Not needed

    Not needed

    See Notes above for "Message Originator"

    Message Identifier

    O

    -

    M

    M

     

    Type of Request/Response

    O

    -

    M

    M

     

    AFTN Address

    O

    -

    -

    -

    ?

     

    Contact Information

    O
    O

    -

    Not needed

    Not needed

    The NM B2B services implements an authentication mechanism (using digital certificates – PKI) which makes the exchange of contact information about the sender not needed as part of the FF-ICE Message.

    Flight Identification

    GUFI

    M

    M

    -

    M

     

    Aircraft Identification

    M

    M

    M

    M

     

    Flight Status

    Operator Flight Plan Version

    M

    M

    -

    M

     

    Flight Characteristics







    Flight Rules

    M

    M

    -

    M

     

    Type of Flight

    O

    M

    M

    M

     

    Special Handling

    O

    -

    -

    O

     

    Flight Plan Originator

    O

    -

    -

    O

     

    Remarks

    O

    -

    -

    O

     

    Operator

    O

    -

    -

    O

     

    Equipment and Capabilities

    M

    M

    -

    M

     

    Supplementary Information Source

    O

    -

    -

    O

     

    Required Runway Visual Range

    O

    -

    -

    O

     

    EUR Special Handling

    N/A

    -

    O

    O

     

    Aircraft Characteristics






    Total number of aircraft

    O

    -

    -

    O

     

    Registration

    O

    -

    -

    O

     

    Aircraft Address

    O

    -

    -

    O

     

    SELCAL Code

    O

    -

    -

    O

     

    Mode A Code

    O

    -

    -

    O

     

    Number and type of aircraft

    M

    M

    -

    M

     

    Wake Turbulence Category

    M

    M

    -

    M

     

    Aircraft Approach Category

    O

    -

    -

    O

     

    Departure/Destination Data





    Departure Aerodrome

    M

    M

     

    M

     

    Destination Aerodrome

    M

    M

     

    M

     

    Estimated Off-Block Time

    M

    M

     

    M

     

    Departure Airport Slot Identification

    O

    -

    -

    O

     

    Destination Airport Slot Identification

    O

    -

    -

    O

     

    Departure Runway

    O

    -

    -

    O

     

    Destination Runway

    O

    -

    -

    O

     

    Alternates

    Alternate Destination Aerodrome(s)

    O

    -

    -

    O

     

      Working Draft