Data Communications

1. Data Communications DCIT Update Flight Deck Working Group

2. Agenda • Update on “Then As filed” • Flight Deck Flow - Initial DCL • Sample Clearances • Review of DCIT #12 Discussion Items

3. Then As Filed • Definition has been completed • At P-30, DCL will be made available for request to the aircraft by an indication of a of ATC Comm Established message to the flight crew. • If any revisions come through after the initial DCL, a UM79 or UM83 as appropriate will be sent to the aircraft.

4. Then As Filed • Maintain Current Flight Deck Procedures for FMS pre-flight. • When the Filed ATC Flight Plan “A” equals the DCL Clearance “C”, then the DCL Then As Filed clearance will be sent to the aircraft • It is incumbent that the ARINC 702 Load matches the Filed Flt Plan

5. Flight Deck Flow - DCL Flight Crew Arrives at the Aircraft Initiates Normal Pre-Flight Requested AOC RTE Data, PERF Data, T/O Data and Wind Data is Sent to the aircraft and Loaded into the FMS – After Loading – FMS “RTE COPY” is selected if available Align the IRU’s /ADIRU and Initialize the FMS LOGON Received - KMEM – Aircraft on participation list LOGON TO KMEM Complete Normal Aircraft Pre-Flight 30 Minutes prior to P Time Flt Plan correlation, DCL Approved and pending • ATC ATC Comm Established Select “CLEARANCE” Request and “SEND” DCL Request Received - Approved DCL sent to the aircraft ATC Message AOC Function Flight Deck Flight Crew Selects ATC Function Key or Menu select KEY - CPDLC ATC Function

6. “Then As Filed” – MCDU Preflight FMS Normally, Verify AOC Uplink against Filed Flight Plan using normal flight crew procedures Request DCL – if Cleared “Then As Filed” is received this means there was exact match between the Original Flt Plan and the embedded HOST/ERAM automated FLT plan output/ Flight Crew Displays the ATC DCL Message Selects “ACCEPT” SEND ATC receives a “Wilco” Response from Aircraft accepting DCL Clearance

7. “THEN AS FILED” (777/787) Flight Crew Displays the ATC DCL Message Preflight FMS Normally, Verify AOC Uplink against Filed Flight Plan using normal flight crew procedures Request DCL – if Cleared “Then As Filed” is received this means there was exact match between the Original Flt Plan and the embedded HOST/ERAM automated FLT plan output/ ATC receives a “Wilco” Response from Aircraft accepting DCL Clearance Selects “ACCEPT” SEND

8. Message Definition – Then As Filed

9. New Discussion Items • DCL Departure Procedure naming • Departure Procedures using “RNAV SID” on the UM169 Free Text • Is this necessary? CLARE2.EIC RNAV SID OR CLARE2.EIC • Recommendation… • Commas between each name e.g., clare2,swb,rnav,sid • Recommendation… Remove the Free Text “RNAV DP/SID” • DCL ALT information – Downstream Reroutes • Inclusion of Initial ALT on revised downstream clearances – UM83 e.g., Re-Stating previously cleared information • Repeat initial cleared altitude with any trajectory change/reroute? • Where is the initial DCL, How to ID the right clearance, is setting it in the ALT window enough? • Recommendation… No need to repeat Maintain ALT for UM83/Downstream clearances. • Enroute ATC Comm • Auto Session Establishment • Typically for those areas where DCL ground service is not in use • DCL aircraft will maintain their ATC Comm connection and will be handed off to enroute automatically • Adaptable parameter similar to the DCL termination action using Time • Open discussion on ATN/FANS session initiations – ATOP/B1 • Recommendations…(Start Point for Discussion) DM Time + X minutes to ensure session establishment occurs at an altitude greater than 3000 AGL - local adaptation.

10. Questions?