FFICE-010

Provision of trajectory information in the submitted eFPL

The desired route/trajectory of the submitted eFPL SHALL contain trajectory information, with at least:
  - One Initial Prediction Point;
  - One End Prediction Point;
  - Top of Climb (TOC) points for the initial cruising level and every subsequent requested cruising level change after a climb;
  - One Top of Descent (TOD) point where the trajectory begins a descent from the final (last) cruising level.
  - Trajectory Change Point – Vertical (TCP-V) points where a level segment (intermediate or cruise) is initiated or terminated;
in line with the rules of the IFPS Users Manual. (*)

(*) NOT APPLICABLE to State Flights (incl. military flights) and to Mixed IFR/VFR operations.

AF5 Information and System Requirements  UNDER REVIEW

Information Exchange Requirements for FF-ICE/R1 UNDER REVIEW

A Route/Trajectory is distinguished by the type of route provided, and the type of trajectory information provided. The FF-ICE/R1 Manual, Appendix E-3. Route/Trajectory, outlines five options for the level of details of the route/trajectory information in an eFPL, described as packages:
  - Package 1A = Route and no trajectory points
  - Package 1B = Route with selected trajectory points
  - Package 2A = Expanded Route and no trajectory points
  - Package 2B = Expanded Route with selected trajectory points
  - Package 2C = Expanded Route with complete trajectory

The CP1 wording routes generation is interpreted as relating to the Expanded Route.

Altogether, REQ-FFICE-009 and REQ-FFICE-010 (this requirement) require that at least Package 2B (Expanded Route with selected trajectory points) is supported in the submitted eFPL. The selection of trajectory points to be supported compulsorily is based on the minimum trajectory requirements specified in the NM IFPS User Manual R27.0.

State Flights and Mixed IFR/VFR operations are exempted from fulfilling this requirement in order to acknowledge that the information can be either sensitive or harder to originate and process.

The wording “in line with the rules of the IFPS Users Manual” is used in the requirements in order to acknowledge that the IPFS Users Manual might specify further rules on the expected route/trajectory content in some particular cases, for instance when the submitted eFPL contains en-route delay information (see e.g. chapter C-7 En-Route Delay).