1 / 18

4D TRAD Progress

4D TRAD Progress. It’s all downhill from here” John Gonda/Dijana Pasic. Overview. What is 4DTRAD and where we are (i.e. 4DTRAD vs. ITBO)? Are there issues that require plenary guidance (particularly if any required to be able to progress the rest of the week)

macon
Download Presentation

4D TRAD Progress

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. 4D TRAD Progress It’s all downhill from here” John Gonda/Dijana Pasic

  2. Overview What is 4DTRAD and where we are (i.e. 4DTRAD vs. ITBO)? Are there issues that require plenary guidance (particularly if any required to be able to progress the rest of the week) What do you want from the Nav crowd? Progress report

  3. 1. 4DTRAD in Context

  4. 4DTRAD – An Integrated Service Trajectory Data Downlink CPDLC DLIC ACL Trajectory Data ACM Event Reporting 4DTRAD MET Data MET Ground Pilot/ATCO ATSU 1 ATSU 2 Human ATSU X

  5. High Level Operational Context Aircraft makes descent from cruise level meeting assigned constraints . Aircraft follow the planned trajectory taking into account the uplinked constraint. Monitoring of trajectory intent conducted by air and ground Airborne System provides full remaining 4D trajectory as requested by ATSU. Lift-Off At gate Descent En-route ‘Air/Ground Sync Message’ based on preferred trajectory, airspace constraints, metering needs, etc. loaded to FMS Trajectory-based clearance for ANSP AOR issued to the a/c by ATCo Uplink of speed descent schedule before TOD. Ground system acquires a/c intent through trajectory downlink both prior to and after departure. Notified to all interested parties 1 4 2 En-route ANSP(s) DestinationANSP(s) DepartureANSP(s) Trajectory intent data downlinked based on synchronised Trajectory. Ground system now assigns a constraint to the aircraft 7 6 5 3 Ground System Speed Constraint issued for short durations To add footer, go to View; select Header and Footer. To delete footer, go to Master Slide and delete. 5 Time Constraints issued one at a time 10/4/2014

  6. 4D TRAD ~ IP 2/Seg 2 Capabilities • Env B/C 4D TRAD OSA/OPA • Draft 9694 EPP functionality • Multiple waypoints available in FMS with earliest/latest ETA @ all waypoints, waypoints downstream of time constraint(s) assume meeting time constraints • Multiple RTAs are being discussed, resolution to the second; accuracy tolerance of 30 seconds • RTA in Descent • DO 214 Avionics and Interops • Will require new Certification and approval • Higher Benefits ...

  7. Initial TBO ~ IP-1/Seg 1 Capabilities • Env A CPDLC OSA/OPA (Existing DO 290/ED 120) • Integration (FANS 2 style or stand alone CMU based integration with the FMC) • Existing Avionics (FANS 1/A+), ATN 110B messages and DO 280/ED 110 Interops • Single CPDLC RTA in some aircraft, B737 allows RTA in descent • Will require new Ops Approval • RTA accuracy to the minute • Benefits ...

  8. 2. Plenary Guidance Requested

  9. 4D TRAD Decision Needed Plenary 5 Plenary 6 Work Plenary 7 Approval Draft 4D TRAD OSD in ISPR format Mature Draft 4D TRAD OSD in ISPR format as separate doc ? Draft 4D TRAD OSD Per TOR and previous Plenary Guidance ITBO OSD In ISPR style ITBO OSD for incorporation in ISPR ? New CPDLC messages desired ITBO OSD Stand alone document ENV A/B OSA, OPA Note: The 4D TRAD OSD would not be incorporated into the ISPR until a 4D TRAD OSA/OPA was complete

  10. 3. Navigation Related Issues

  11. Current Draft OR’s that Require Nav Expertise Communication Domain • OR4 - The airborne domain and ground domain time sources shall be synchronized to within one second. • OR8 - Pilots and controller awareness on the 4DTRAD service termination shall be supported by their respective ground and airborne systems tools • OP.Rec1 - It is recommended that the airborne domain provide adequate guidance in the trajectory data, for example achievable min/max speeds and ETA min/max at each point in the trajectory, to support the ground systems processing • OR41 - The airborne system shall provide real time monitoring of the flight’s potential divergence from the accepted time or speed constraints including alerting functions in case of non-conformance • OR43 - The pilot shall be aware of any uplinked constraints and shall be required to approve and execute the aircrafts conformance to that constraint. • OR45 - The avionics supporting the trajectory negotiation process shall provide the flight crew with tools that support the review of the impact of the trajectory changes and constraints proposed by the ground systems

  12. Current Draft OR’s That Require Nav Expertise Minimum Airborne Capabilities • OR4 - The airborne domain and ground domain time sources shall be synchronized to within one second. • OR8 - Pilots and controller awareness on the 4DTRAD service termination shall be supported by their respective ground and airborne systems tools • OP.Rec1 - It is recommended that the airborne domain provide adequate guidance in the trajectory data, for example achievable min/max speeds and ETA min/max at each point in the trajectory, to support the ground systems processing • OR41 - The airborne system shall provide real time monitoring of the flight’s potential divergence from the accepted time or speed constraints including alerting functions in case of non-conformance • OR43 - The pilot shall be aware of any uplinked constraints and shall be required to approve and execute the aircrafts conformance to that constraint. • OR45 - The avionics supporting the trajectory negotiation process shall provide the flight crew with tools that support the review of the impact of the trajectory changes and constraints proposed by the ground systems

  13. 4. Progress Report

  14. Results of November BRU 4D TRAD Meeting • Agreed to reshape the OSD to conform to ISPR format • Agreed to 4D TRAD Messages for delivery to OSA • Agreed to divide the OSD into two compatible services based upon predicted capabilities and Environment • Initial Trajectory Based Operations (ITBO) • 4D Trajectory Data Link (4D TRAD) • Coordinated ITBO informally with Eurocontrol, FAA and SESAR

  15. 4D TRAD OSD Progress Structure as per SC 214 214/78 ISPR format Remove tech dependency statements on ADS-C and refer to trajectory data requirements only Remove flight plan update references and make the air/ground sync section more generic pending agreement on the topic Integrate the latest update on required CPDLC messages provided to SG ½ in November Path the way for a new Initial Trajectory Based Operations (ITBO) OSD

  16. ITBO OSD Progress • Down scoped 4D TRAD OSD referred to on previous slide • Resulting ITBO reflects 4D TRAD progress to date • Less those capabilities not available in ENV A • Supported by on-going CPDLC OSA and OPA • New CPDLC messages desired

  17. 4D TRAD • Met @ Eurocontrol 3-5 Nov • Results: • Reviewed ADAS 4D TRAD concept and minimum requirements • Reviewed new Env A/B/C for impact • Agreed to reshape the OSD to conform to ISPR format • Agreed to 4D TRAD Messages for delivery to OSA • Agreed to divide the OSD into two compatible services based upon capabilities and Environment • Initial Trajectory Based Operations (ITBO) • 4D Trajectory Data Link (4D TRAD) • 19/66 Action Items remain open • 139/354 Comments remain open

  18. 4D TRAD Planned Activities • Hold weekly telcons to resolve comments • Meet in Toulouse, 8-12 Dec to complete and deliver the draft OSD • Deliver Mature OSD to Plenary on March 9, 2009 free of relevant comments • Will plan as if the OSD will be integrated into the ISPR

More Related