Data Communications

1. Data Communications DCIT #9 Flight Deck Working Group

2. Agenda • System Engineering Action Item • Review and Discuss CPDLC Disconnect after Takeoff • DCL Clearance Delivery Time – ATC Discussion • Review the DCL Services description • UM80 Initial DCL • UM79 & UM83 Revised Clearances • Make recommendations to End-To-End Use Case • Review and Discuss Flight Deck Procedures • CPDLC LOGON for Trial • FMS Loading • FMS RTE and LEGS Checking requirements • Catalog Airline Specific Aircraft Capability: • ATS Print Functionality Discussion • Nav Data Base Configuration – Customized for airline operations? • Integrated FMS Capability – Open Discussion • Discuss MITRE DCL Demo of Initial and Revised Clearance

3. Disconnecting CPDLC Link • System Engineering Action Item • Review and Discuss CPDLC Disconnect after Takeoff • Boeing and Airbus differences • Boeing always notifies the flight crew with a Aural and Visual cockpit indication of CPDLC status - Termination • Airbus does not alert the flight crew of CPDLC termination when your session has been discontinued – display status • Ground System will send a CPDLC system level message that the CPDLC session has been Discontinued after Takeoff • Aircrew will be notified • Options for this message are Altitude or Time or Pilot Initiated Log Off • Altitude Advantage: Predictable and can be set to not interfere with other flight crew activities (Checklist, Sterile Cockpit) • Time/Handoff: Handoff can vary due to other controller / ground system activities, Time is a variable set in the ground system D+3min • Pilot Initiated Log Off: Time Consuming, changes flight deck procedures • Recommendation: Altitude disconnect @ 12000 FT MSL. 2nd Option – Time Adaptable handoff D+10 Mins • DCL Clearance Delivery Time – ATC Discussion • Flight Deck request an earlier delivery of DCL clearance changed from 30 mins to a DCL Clearance Delivery of 45 mins prior to Proposed Departure Time • Recommendation: Flight Deck requires DCL Clearance Delivery 45 mins prior to Proposed Departure Time - Tower will investigate, Spurious messages will be investigated for occasional revised messages

4. Review the DCL Services description • UM80 Initial DCL • Analysis is Complete • ATC working group working with FAA Tower to determine if modification will be necessary for the following: • EXP ALT WI 10 MINS • DEP FREQ • Recommendation: No changes, continue with current solution • UM79, UM83 and UM80 Revised Clearances • Action is to recommend to the DCIT any further Flight Deck concerns or needs • Coordinate with ATC working Group concerning any issues • Recommendation: No changes, continue with current solution • Make input to End-To-End Use Case • Format Descriptions were submitted for DCIT review • Recommendation: Input to the End2End was completed from flight deck working group

5. Initial DCL – Base Line Clearance w/RNAV SID KDFW Loaded Data EIC AEX MCB CEW J50 SZW CLARE2.EIC J50 J2 KMIA SSCOT1.SZW

6. Initial DCL – Base Line Clearance w/RNAV SID

7. Revised DCL – UM83 – AT POSITION CLEARED UM83can modify anything from a DP Transition Fix on an existing route of flight to destination - No change to the DP or Transition Yellow is the loadable uplink Red = new RTE on Nav Display EIC AEX KDFW MCB CEW J50 SZW J50 CLARE2.EIC KMIA KRSTO SSCOT1.SZW

8. UM83Route Modification: from a point on an existing route of flight to destination. No change to the DP or Transition. Route information: Route change from point on original route to destination to include arrival procedure as applicable.

9. Revised DCL - UM79 - Cleared TO VIA UM79can modify anything to a point on an existing route of flight – Last modification point is limited to the Transition Fix on the Arrival - No change to the Arrival Procedure or Transition is allowed Yellow is the loadable uplink Red = new RTE on Nav Display EIC AEX KDFW MCB CEW SZW CLARE2.SWB J50 J2 SWB KMIA SSCOT1.SZW

10. UM79:Procedure Departure and different transition fix. Route information: different transition fix, links with an existing downstream route of flight waypoint

11. UM80 Reroute - Complete Change of Flight KDFW Yellow is the loadable uplink Red = new RTE on Nav Display EIC AEX MCB CEW J50 SZW J50 ARDIA3.CLL J2 J86 CLL Q102 KMIA IAH Q102 LEV Q102 BLVNS BAGGS CYY CYY.CYY6

12. UM80 – Revised Clearance:Complete change of route using UM80 - Procedure Departure and different transition fix, Route information: different transition fix, change of route to connect to a new arrival procedure to original destination

13. Flight Deck Procedures • CPDLC LOGON • Flt ID: FDX765 “ICAO ID” • Tail Number: N787BA • Facility: Trial will be Facility ID (e.g., KLAS) • FMS Loading: See next slides • FMS RTE and LEGS Checking requirements: See next slides • Recommendation: No changes, • Next step is to review current airline procedures and review at the next DCIT Flight Deck Working group

14. ATC MSG / Response Attributes

15. DCL Request / DP and RWY Entry

16. FMS RTE and Legs Check

17. Catalog Airline Specific Aircraft Capability • Aircraft Configuration • ATS Print Functionality Discussion • Airlines? Will send a request to all DCIT Airlines for input • Nav Data Base Configuration – Customized for airline operations? • Airlines? Will send a request to all DCIT Airlines for input • Integrated FMS Capability – Open Discussion • Access to Messages • Complex Clearances • Duplicate Waypoints • Shared Displays • Postponed until next DCIT

18. MITRE DCL Demo • Discuss MITRE DCL Demo of Initial and Revised Clearance • Lab Environment • B777 Like cockpit • Hosted FMS / CPDLC Application • Aircraft already Logged on • Initial DCL: UM80 Full RTE Clearance DFW-MIA • Revised DCL: UM83 due to WX near “CEW” • Retention of DATA • Reduced Flight Crew Workload vs. “Old” UM80 Revised Clearance procedures

19. Backup

20. Action Items: