1 / 14

Delivering Digital Services

Delivering Digital Services. 4D Trajectory Scope For FF-ICE Step 1. Presented By: Dr. Stéphane Mondoloni Date: August 28, 2014. Background. ICAO developing flight planning provisions for FF-ICE/1 using FIXM. Long-term goal: FF-ICE Concept (Doc. 9965).

maisie-humphrey
Download Presentation

Delivering Digital Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Delivering Digital Services 4D Trajectory Scope For FF-ICE Step 1 Presented By: Dr. Stéphane Mondoloni Date: August 28, 2014

  2. Background • ICAO developing flight planning provisions for FF-ICE/1 using FIXM • Long-term goal: FF-ICE Concept (Doc. 9965) • GANP (Doc 9750) provides ASBU Modules with FICE Thread • FF-ICE/1 provisions apply to ASBU Block 1(Ready for implementation by 2018) • Some language on scope provided by module descriptions  Greater clarity & agreement required

  3. From ASBU Description • FF-ICE will facilitate the exchange of information associated with the flight plan, allowing more flexibility for flight data submission, amendment and publishing. • Provides a basis for transition towards a full FF-ICE deployment: • a) globally unique flight identifier (GUFI); • b) a common data format, i.e. flight information eXchange model (FIXM) in the context of the overall transition to extensible markup language/geography markup language (XML/GML) for aeronautical and meteorological information; and • c) basic roles, rules and procedures for submission and maintenance of FF-ICE information including provisions for the early sharing of trajectory information.

  4. More ASBU Language The changes included in FF-ICE, Step 1 are the following: a) support for early provision of flight intention information; b) support for exchange of 4D trajectory information between the AOC and the ASP; c) a new format for flight and flow information using internet protocol and XML; d) a globally unique flight identifier (GUFI); and e) FF-ICE, Step 1 information elements. The foreseen services related to flight information submission and management in the framework of FF-ICE, Step 1 are: a) initial submission; b) validation; c) GUFI allocation (after the initial flight submission); d) nominal trajectory generation (in absence of airspace users defined trajectory); e) flight information negotiation (to solve conflict between airspace users’ intended flight and existing constraints); f) flight information update (to change or add to current flight information); g) acknowledgement/rejection; h) flight information publication; i) flight information subscription; j) flight information cancellation; k) flight suspension; and l) flight information. Focus on the 4D Trajectory Implications

  5. Scoping Assumption • Section 11.1.3 Identifies Movement & Control messages: • Movement • Coordination • Supplementary • AIDC • Control • Focus on pre-departure exchange implies: • New FF-ICE/1 provisions applicable to Movement & Supplementary • Coordination, AIDC and Control: present-day provisions are left in place for Block 1

  6. Implications • Movement messages: FPL, CHG, CNL, DLA, DEP, ARR • Supplementary messages: RQP, RQS, SPL • Inclusion of DEP – end of pre-departure phase • Inclusion of ARR – post-departure • Mixed-mode compatibility • Require ability to translate to/from these messages • Require compatibility with present-day provisions (timing and complete messages) • Coordination maintains present-day provisions: • No GUFI used for these • Information updated in flight may be shared, including 4DT • Provisions do not describe • Present-day messages are used to update internal flight information • Bilateral agreements may develop for coordination

  7. Pre-departure Overview Early Information (e.g. scheduling) Pre-departure Constraint Information Flight Information & Desired 4DT Feedback on 4DT (Negotiating) Agreement on 4DT Others Ranked 4DTs Verification of 4DT Distribution consistent with 4DT AU ASP Optional – Provisions do not describe Provisions will describe

  8. Pre-departure Interactions • In Block 1: • Piecewise 4DT • Coordination fix conditions • AU may respond withend-to-end 4DT • If no feedback, sameas present day Publish Publish Distribution ASP 1 ASP 2 AU

  9. Post-departure Illustration ASP may update 4DT & publish (provides advanced information for TFM) 10:58 10:54 10:55 10:57 10:52 CPL Coordination as per present provisions Publish • As Block 1 advances towards Block 2 • Processes developed for coordination using 4DT • Bilateral agreements may enable earlier implementations

  10. FIXM 4DT Implications • Representation of 4DT • Consistent and linked to other elements • Example: • 4DT uniquely associated with a route for clearance • 4DT Points associated with route fixes • E.g., For verification of constraint application

  11. Pictorial Representation ROUTE ARR procedure RWY Named points Associated Step climb w speed change Reference IAS/ predicted wind Altitude/airspeed constraint DEP procedure RWY Requested altitudes/airspeeds TOD MF (significant point) RWY 4DT points Lat/long/alt/time 4DT Type of TCP Estimated runway arr time Estimated runway dep time RWY

  12. Additional 4DT Implications • Operator-provided 4DT • Feedback of constraints • Incorporation of trajectory constraints • Support for negotiation • Agreement on 4DT • Publication of 4DT Update

  13. Acknowledgement • Scoping was a joint effort between NextGen and the SESAR Joint Undertaking (SJU) under Coordination Plan 3.1. Participants included: • Kim Breivik • Anna Cagidemetrio • Philippe Leplae • Gérard Mavoian • Stéphane Mondoloni • Scope was presented at an ICAO ATMRPP Working Group meeting

  14. Questions 2

More Related