Presented to: DCIT Flight Deck Working Group By: Andy Fry, Thane Inc. Date: October 12, 2011 Federal Aviation Administration Data Communications DCIT #10 October 12-13, 2011 MD-11 Lab Visit

Data Communications Program 2 Federal Aviation Administration October 12, 2011 Agenda Review of September minutes MD-11 Engineering Lab Visit Action Item Discussions –Airline Flight Deck/AOC Discussion –End2End Monthly meeting input

Data Communications Program 3 Federal Aviation Administration October 12, 2011 MD-11 ATC LOGON / Status

Data Communications Program 4 Federal Aviation Administration October 12, 2011 MD-11 ATC Comm Established No Aural Alert or Visual annunciation on Nav Display –Only a Scratch Pad message on the MCDU

Data Communications Program 5 Federal Aviation Administration October 12, 2011 MD-11 Initial DCL UM80

Data Communications Program 6 Federal Aviation Administration October 12, 2011 MD-11 Review Page

Data Communications Program 7 Federal Aviation Administration October 12, 2011 MD-11 Secondary Flt Plan

Data Communications Program 8 Federal Aviation Administration October 12, 2011 MD-11 Secondary Flt Plan – Con’t

Data Communications Program 9 Federal Aviation Administration October 12, 2011 MD-11 Nav Display – Initial DCL

Data Communications Program 10 Federal Aviation Administration October 12, 2011 MD-11 Revised DCL – UM83

Data Communications Program 11 Federal Aviation Administration October 12, 2011 MD-11 Revised DCL – MCDU Review

Data Communications Program 12 Federal Aviation Administration October 12, 2011 MD-11 UM83 Nav Display w/Mod

Data Communications Program 13 Federal Aviation Administration October 12, 2011 MD-11 Revised DCL – UM79

Data Communications Program 14 Federal Aviation Administration October 12, 2011 MD-11 Revised DCL UM79 Review

Data Communications Program 15 Federal Aviation Administration October 12, 2011 MD-11 Free Text – Lat/Long Free Text –Word Wraps –Handles 256 characters 84 Displayed in picture Lat/Long –Can handle up to 40 Lat/Longs on a RTE of Flight

Data Communications Program 16 Federal Aviation Administration October 12, 2011 MD-11 Findings Pegasus Platform circa 2000’ –Can accept all DCL clearances MD-11 Exception: UM80/83 –Any RTE clearance ending in an “Airway” to an Arrival Transition Fix creates a RTE Discontinuity after the Arrival Transition Fix »Flight Crew Procedures Corrects the RTE page J50 MCB CEW SZW SSCOT1.SZW J2 KMIA Discontinuity

Data Communications Program 17 Federal Aviation Administration October 12, 2011 MD-11 Findings Con’t Revised DCL –MD-11 Exception: UM79 Fails to load any UM79 when a Runway or Departure procedure is included in the Route Clearance Element Fails to Load any UM79 when the Arrival Transition point is the “AT” point in the uplinked message –Last Point on the UM79 must be a FIX/Waypoint on RTE of flight before a Arrival Transition Fix »E.G., TO CEW via SWB..HRV..PNS J50 EIC AEX MCB CEW SZW SWB HRV PNS

Data Communications Program 18 Federal Aviation Administration October 12, 2011 Action Items Flight Crew Request for DCL –Demand or Push Update on “Time” when DCL is available –Impact of 30min vs. 45min DCL availability AOC discussion –Flt Planning –FMS Uplinks (Wind, T/O, Perf) –Lat/Long Airbus/Boeing DP and RWY discussion End2End discussion

Data Communications Program 19 Federal Aviation Administration October 12, 2011 Backup