1. Presented to: DCIT By: Andy Fry, Thane Inc. Date: September 20, 2011 Federal Aviation Administration Data Communications DCIT #9 Flight Deck Working Group

2. Data Communications Program 2 Federal Aviation Administration September 20, 2011 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. Data Communications Program 3 Federal Aviation Administration September 20, 2011 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. 2 nd 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. Data Communications Program 4 Federal Aviation Administration September 20, 2011 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. Data Communications Program 5 Federal Aviation Administration September 20, 2011 J50 Initial DCL – Base Line Clearance w/RNAV SID UM80 {RouteClearance} Urg(N)/ Alr(A)/ Resp(W/U)/ Rec(RC) Airport Departure[0] Airport Destination [1] Procedure Arrival [6] Route information [7] KDFW KMIA SSCOT1.SZW EIC..AEX.J50.CEW.J2.SZW (6) Optional if a ARR is not part of the route Information EIC AEX MCB CEW SZW UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) CLARE2.EIC RNAV SIDManual Entry by the Flight Crew SSCOT1.SZW CLARE2.EIC J2 Loaded Data KDFW KMIA

6. Data Communications Program 6 Federal Aviation Administration September 20, 2011 Initial DCL – Base Line Clearance w/RNAV SID UM Number Response Attributes ASN1 Definition Sample ClearanceLab Validation UM80 {RouteClearance} Urg(N)/Alr(A)/ Resp(W/U)/Rec(RC) Airport Departure[0] Airport Destination [1] Procedure Arrival [6] Route information [7] KDFW KMIA SSCOT1.SZW EIC..AEX.J50.CEW.J2.SZW (6) Optional if a ARR is not part of the route Information UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) CLARE2.EIC RNAV SID UM19 MAINTAIN [level] Urg(N)/Alr(A)/ Resp(W/U)/Rec(VC) LevelType ::= CHOICE levelFeet [0] levelFlightLevel[2] MAINTAIN 10000FT UM169 [freetext] Urg(N)/Alr(L)/ Resp(R) FreeText ::= IA5String (SIZE (1..256)) EXP FLXXX WI 10 MIN AFT DEP. DEP FREQ 118.55 EDCT 2145Z FL/FT, MIN/MILES, Freq is Ctrl selected from DP, EDCT – display if HADS provides UM123 SQUAWK [code] Urg(N)/Alr(M)/ Resp(W/U) Code ::= SEQUENCE SIZE (4) OF CodeOctalDigit CodeOctalDigit ::= INTEGER (0..7) SQUAWK 0562

7. Data Communications Program 7 Federal Aviation Administration September 20, 2011 Revised DCL – UM83 – AT POSITION CLEARED J50 EIC AEX MCB CEW SZW SSCOT1.SZW CLARE2.EIC UM83 AT [position] CLEARED [routeClearance] Urg(N)/Alr(M)/ Resp(W/U) PositionPosition ::= SEQUENCE SIZE (2) OF Position – atposition RouteClearance ::= SEQUENCE Airport Destination [1] Procedure Arrival [6] Route information [7] CEW KMIA SSCOT1.SZW KRSTO..SZW All previously entered data (Man or via FMC Load) is retained except for wind data at point KRSTO and beyond to destination NOTE DP, RWY, T/O Data, Performance Data and Wind Data to CEW is retained. KRSTO UM83 can 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 KDFW KMIA

8. Data Communications Program 8 Federal Aviation Administration September 20, 2011 UM83 Route 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. UM Number Response Attributes ASN1 Definition Sample ClearanceLab Validation UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) REVISED ROUTE UM83 AT [position] CLEARED [routeClearance] Urg(N)/Alr(M)/ Resp(W/U) PositionPosition ::= SEQUENCE SIZE (2) OF Position – atposition RouteClearance ::= SEQUENCE Airport Destination [1] Procedure Arrival [6] Route information [7] CEW KMIA SSCOT1.SZW KRSTO..SZW UM19 MAINTAIN [level] Urg(N)/Alr(A)/ Resp(W/U)/Rec(VC) LevelType ::= CHOICE levelFeet [0] levelFlightLevel[2] MAINTAIN 10000FT

9. Data Communications Program 9 Federal Aviation Administration September 20, 2011 J50 Revised DCL - UM79 - Cleared TO VIA EIC AEX MCB CEW SZW SSCOT1.SZW CLARE2.SWB J2 UM79 CLEARED TO [position] VIA [routeClearance] Urg(N)/Alr(M)/ Resp(W/U) PositionPosition ::= SEQUENCE SIZE (2) OF Position – toposition RouteClearance ::= SEQUENCE Airport Departure[0] Airport Destination [1] Route information [7] MCB KDFW KMIA SWB All previously entered data (Man or via FMC Load) is retained FROM MCB and beyond to destination NOTE DP is manually entered by the flight crew. RWY, T/O Data, Performance Data and Wind Data From MCB to destination is retained. UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256))CLARE2.SWB Requires manual entry by the flight crew SWB UM79 can 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 KDFW KMIA

10. Data Communications Program 10 Federal Aviation Administration September 20, 2011 UM79: Procedure Departure and different transition fix. Route information: different transition fix, links with an existing downstream route of flight waypoint UM Number Response Attributes ASN1 Definition Sample ClearanceLab Validation UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) REVISED DP TRSN AND RTE UM79 CLEARED TO [position] VIA [routeClearance] Urg(N)/Alr(M)/ Resp(W/U) PositionPosition ::= SEQUENCE SIZE (2) OF Position – toposition RouteClearance ::= SEQUENCE Airport Departure[0] Airport Destination [1] Route information [7] CLEARED TO MCB KDFW KMIA SWB UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) CLARE2.SWB UM19 MAINTAIN [level] Urg(N)/Alr(A)/ Resp(W/U)/Rec(V C) LevelType ::= CHOICE levelFeet [0] levelFlightLevel[2] MAINTAIN 10000FT

11. Data Communications Program 11 Federal Aviation Administration September 20, 2011 J50 J2 Q102 J86 J50 UM80 Reroute - Complete Change of Flight EIC AEX MCB CEW SZW UM80 {RouteClearance} Urg(N)/Alr(A) / Resp(W/U)/R ec(RC) Airport Departure[0] Airport Destination [1] Procedure Arrival [6] Route information [7] KDFW KMIA CYY.CYY6 CLL.IAH.J86.LEV.Q102.CYY Removes all previously loaded data – RWY, DP, T/O Data, Wind Data UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) ARDIA3.CLL RNAV SIDManual Entry by the flight crew BAGGS CLL IAH LEV BLVNS CYY KDFW KMIA Yellow is the loadable uplink Red = new RTE on Nav Display ARDIA3.CLL CYY.CYY6

12. Data Communications Program 12 Federal Aviation Administration September 20, 2011 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 UM Number Response Attributes ASN1 Definition Sample ClearanceLab Validation UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) REVISED DP AND RTE UM80 {RouteClearance} Urg(N)/Alr(A)/ Resp(W/U)/Rec(RC) Airport Departure[0] Airport Destination [1] Procedure Arrival [6] Route information [7] KDFW KMIA CYY.CYY6 CLL.IAH.J86.LEV.Q102.CYY UM169 [freetext] Urg(N)/Alr(L) /Resp(R) FreeText ::= IA5String (SIZE (1..256)) ARDIA3.CLL RNAV SID UM19 MAINTAIN [level] Urg(N)/Alr(A)/ Resp(W/U)/Rec(VC) LevelType ::= CHOICE levelFeet [0] levelFlightLevel[2] MAINTAIN 10000FT UM169 [freetext] Urg(N)/Alr(L)/ Resp(R) FreeText ::= IA5String (SIZE (1..256)) REVISED DEP FREQ 125.12

13. Data Communications Program 13 Federal Aviation Administration September 20, 2011 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. Data Communications Program 14 Federal Aviation Administration September 20, 2011 ATC MSG / Response Attributes Audible Chime with EICAS  ATC Responding to an Uplinked Clearance ATC Function Key…………………………Select View the message and act appropriately on the message. Ensure you verify the Initial Altitude and Squawk as part of the uplinked Clearance.  ATC MCDU Key……………………….Select Return to the ATC Communication message and after the flight crew agrees with the ATC Departure Clearance and have verified route upload to the FMC  ACCEPT …………………………………..Select Standby, Reject are also available response as needed by the flight crew

15. Data Communications Program 15 Federal Aviation Administration September 20, 2011 DCL Request / DP and RWY Entry Request a Departure Clearance (DCL)Manual Entry of DP and Runway  ATC MCDU Key……………………………..Select  Clearance 4R…………………….…………..Select  REQUEST CLEARANCE……………………Select (Some airplanes)  SEND…..………………………………………..Select  Dept/ARR…………………….……………….Select  RWY………………………..……………………Select  Procedure………………..…………………..Select  Transition…………………………….……….Select  RTE………………………………………..……..Select Verify the appropriate Departure procedure, Runway and Transition are correct against the DCL with no Route Discontinuities  Execute…………………………………….…..Select

16. Data Communications Program 16 Federal Aviation Administration September 20, 2011 FMS RTE and Legs Check Loading and Verifying an FMS uplinked DCLLEGS Page / Distance check for Uplinked DCL  Load……………………………………….……..……Select LOAD prompt automatically updates FMC RTE page with route clearance information.  FMC RTE …………………………………………….Select  Verify ………………………………………DEPT Airport  Verify ………………………………………DEST Airport  Verify ………………..………………………..….FLT NO: For Example:CAL123  Verify……………………….…………….Cleared Route The Departure Procedure and Runway will require manual entry (see manual entry of DP and RWY)  Activate………………………………..……………..Select  EXEC ……………………………….………………….Select to complete the RTE page upload  LEGS ……………….………………………………….Select  Map Mode……………….…………………………Select Step through the legs page using “Step” at 6R and observe on the Navigation Display: o Waypoints and Altitude constraints agree with those on your filed flight plan and navigation charts, and o No discontinuities exist between waypoints  Verify that an active waypoint is depicted in 1L on LEGS page 1  Verify the total route distance is proper for route of flight versus your filed flight plan

17. Data Communications Program 17 Federal Aviation Administration September 20, 2011 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. Data Communications Program 18 Federal Aviation Administration September 20, 2011 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. Data Communications Program 19 Federal Aviation Administration September 20, 2011 Backup

20. Data Communications Program 20 Federal Aviation Administration September 20, 2011 Action Items: