Flight Plan Filing & Subscriber Data Base

Transcription

1 Flight Plan Filing & Subscriber Data Base Takes advantage of standard fields in ICAO 2012 Flight Plan Flight Plan: Field 10a Equipment Code: Standardized J codes indicate FANS equipage Field 18 (Other Information): Data Comm specific DAT/ codes used to identify flights receiving DCL or PDC Clearances Field 18 DAT/ codes will include a primary and secondary hierarchy. This ICAO FPL preference takes priority over any other sources Operator may override the SDB by filling preferences in Field 18 DAT/ Subscriber Data Base (SDB) maintains IATA addressing for air carriers to receive PDC messages and DCL dispatch messages SDB also maintains a set of master preferences aircraft operators can setup for each fleet type FAA will provide SDB update template prior to DCL going live 1

2 Flight Plan Filing Rules For full details, please refer to End-to-End document Flight Plan Filing with DAT/ entries for PDC or FANS will override preferences in Subscriber Database Within DAT/ entry, can file: 1VOICE = Voice Only 1PDC = PDC Only FANS or FANSP = CPDLC DCL using FANS 1/A or FANS 1/A+ Do not recommend this filing because it does not give fallback options in case FANS is out of service. 1FANS2PDC or 1FANSP2PDC = Preference is for CPDLC service, if not available, use PDC instead. Notes: To receive Dispatch Message, an entry must exist in the SDB for that flight with the associated IATA Address To receive a PDC, there MUST be an entry in the SDB for the flight receiving the PDC. 2

3 Field 10a Data Link J Codes 10a J Code Description Data Comm J1 CPDLC ATN VDL Mode N/A Link2000+ J2 CPDLC FANS 1/A HFDL N/A Oceanic J3 CPDLC FANS 1/A VDL Mode A Applicable J4 CPDLC FANS 1/A VDL Mode 2 Applicable J5 CPDLC FANS 1/A SATCOM (INMARSAT) N/A -- Oceanic J6 CPDLC FANS 1/A SATCOM (MTRSAT) N/A Oceanic J7 CPDLC FANS 1/A SATCOM (Iridium) N/A -- Oceanic Note1: If using Field 18 /DAT, Z must be included in Field 10a. (e.g., J4Z) Note2: Field 18 /DAT codes designate FANS 1/A+ as a work around. 3

4 ROUTE LOADING LIMITATIONS 4

5 Routes Analysis Findings Data Comm DCL Trials have found many FAA mandated routes in NAS are not loadable A review of ERAM adaptation and flight plan data revealed a significant number of other non-loadable routes Adapted routes containing Non-Loadable elements Airway to Airway no named intersection (KIAH).AEX6..MCB..MEI..MGM..AJFEB..GRD..J209..J207..FKN..J79..JFK..HTO..KPVD Radials flown as a route element. (KSLC)..TCH.TCH094..MTU303.MTU..HBU 3 Letter Identifiers being utilized as origin and destination airports Airports, CDR s ZNY Automation / Controller Entry Fake or Ghost Intersections Computer assigned AOC s insert to make loadable today, some FMC s have capability, not all. Coding that allows Airport to Airway intercepts KMEM J42 BKW J147 CSN OTT6 KBWI NAT Tracks, XXX 5

6 Route Problems Quantified Identified 2573 non loadable routes. Estimating 3500 total (Key Site KSLC ~16% of high altitude departure routes are non-loadable) Radials flown as a route element 1,253+ in adapted departure routes 247 in published preferred departure routes Airway to Airway no named intersection 512+ in adapted departure routes 174 in published preferred departure routes 3 Letter Identifiers accepted as airports Allowed in any NAS flight plan, or when manually entered by ATC Unpublished, Fake or Ghost Intersections Unknown number adapted in ERAM Numerous from AOC s Adapted routes containing Airport to Airway intercepts 181+ in adapted departure routes 206 in published preferred departure routes NAT Tracks, XXX All NATx s XXX Used to indicate bad route element 6

7 Route Solution Space Education in the field Automation Departments / POFM s Airspace Managers AOC/GOC Airline Partners Command Center Air Space Design Groups OAPM PBN TDLS/ARTCC Facility Route Analysis (Data Mining) ~80% of ERAM Assigned Route Issues Correctable w/adaptation ~90% of Non Automated Route Issues Correctable (Command Center & Pref. Routes) Remaining issues will be corrected as solutions are identified. 7

8 Automation Route Rules for Loadable Clearance Data Comm Loadable Route Rules Definitions Fix : As used below, the term fix means published intersections, waypoints, or navaids. A fix may also be a fix-radial-distance (FRD), or a latitude/longitude (L/L). For the purposes of this document an airport is not considered a fix. Route Element: Airways and fixes defining a route of flight. Departure/Arrival airports are NOT considered route elements. General Rules Use of an airway as a route element requires a published entry and exit point for the airway. (e.g...sjn.j108.gingr..) An implied airway/airway junction (i.e. no fix between airways) is NOT loadable. (e.g..j4..j65.) If a named fix is published at the implied junction, it may be added to make the route loadable. (e.g..j4.abi.j65.) Note- This is the preferred option. A navaid radial is NOT a loadable route element in a Data Comm clearance. (e.g..air111. or.abq092r.) An FRD may be used in place of a navaid radial, or unnamed airway junction. (e...tch..tch mtu..) Note- Use a named fix, if available. Unpublished, named (Ghost) fixes are not loadable. (e.g. KMSY..TIKDP..) ClearanceSupportAlphas (formerly Host G-Keys) are forwarded to PDC, but not to tower DCL, or flight crews. Possible impacts are being investigated. Use of ClearanceSupportAlphas should be avoided, if possible. (e.g. MAXIE-STAR or RV LAIRD or RV HDG030) Departure Phase - (ADR/PDR, ADAR/PDAR, CDR, IFR Preferential Route, Playbook Routes, etc.) The first route element after departure must NOT be an airway. (e.g. KPHX.J65..) The first route element may be a fix, or a SID/DP followed by the last fix on the common route, or a published transition fix. Other exit fixes are NOT loadable. (e.g. KPHX..PXR.J65.) Arrival Phase - (AAR/PAR, ADAR/PDAR, APR, CDR, IFR Preferential Route, Playbook Routes, etc.) The last route element prior to destination must NOT be an airway. (e.g...j78.kama) The last route element must be a fix, or a STAR proceeded by a published transition fix, or the first fix on the common route. Other entry fixes are NOT loadable. (e.g....j78.ama..kama) 8

9 SUBSCRIBER DATABASE 9

10 Subscriber Database - Scenario 1 Create different priority for all tail numbers FLID ARPT AIRL PRIORITY SERVICE IATA CSP START end_date/time DCC Type GREQ N8888C ALL ABC 1 FANS XXXXXXX ARINC 2099/12/31 ALLF Y N8888C ALL ABC 2 PDC YYYYYYY ARINC 2099/12/31 N711HK ALL ABC 1 PDC YYYYYYY ARINC 2099/12/31 N711Hk ALL ABC 2 FANS XXXXXXX ARINC 2099/12/31 ALLF Y Note: Can be overridden using filed flight plan This option is simplest if all PDC/DCL capable tails are not changing over time 10

11 Subscriber Database - Scenario 2 PDC for all flights unless otherwise filed. Dispatch messages should go to different address than PDC FLID ARPT AIRL PRIORITY SERVICE IATA CSP START end_date/time DCC Type GREQ ABC ALL ABC 1 PDC YYYYYYY ARINC 2099/12/31 ABC ALL ABC 2 FANS XXXXXXX ARINC 2099/12/31 ALLF Y For flights that would like to receive FANS CPDLC DCL Field 10A = Must have Z in addition to associated equipment codes Field 18 DAT/ = 1FANSP2PDC It is the most flexible option but not the simplest option All flight plans that wants to be DCL capable, must be amended with Field 10A and 18. Least impact to current PDC operations 11

12 DCL CLEARANCES 12

13 DTAP FANS CPDLC Messages FANS AFN logged in Flight Deck Requests Initial DCL via Clearance Request message (DM25) Initial (Revised Initial) Clearances: - Cleared as Filed (CAF) - UM79 Cleared to XYZ via [SID/RTE INFO] Cleared to Destination Then as Filed (Non CAF Domestic/International Flights) - UM80 - Full Route Clearance (Non CAF Domestic Flights) - Non RTE info sent (DP, EDCT, EXPALT, ALT, DEPFREQ) Revised Clearances: - UM79 - Revised RTE after XYZ Rest of Route Unchanged (SID and/or Trans, First part of route changes) - UM80 - Full Route Clearance (Entire Route Sent) - UM83 - Revised RTE AT XYZ (Route AT Point to Destination mods ) - Revised DCLs pushed to Flight Deck - Non RTE Revisions (DP, EDCT, EXPALT, ALT, DEPFREQ) 13 13

14 Route Examples 14

15 AFN FANS CPDLC LOGON 15 15

16 DM25 Example Crew Makes Req 16

17 AOC Dispatch Messages All initial and Revised DCLs messages sent to AOCs via CSP: - Not an ATC Clearance - Beacon removed - ACK expected but not mandatory (Gate optional like done today) - New ARINC 620 message (PDC format) AOC Systems Impacts: - Dispatch Messages sent when DCL is uplinked - Messages sent to airline at provided IATA address 17

18 Cleared as Filed Example Flight Deck 1. Clearance to Destination Airport and Departure Procedure The FAA will not uplink runway information, therefore, the SID must always be entered into the FMC manually. 2. Initial cleared altitude Flight crew should check filed altitude against CAF clearance to ensure it is the same. Changes to filed altitude will not be provided as revision 18

19 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 19

20 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ Address of Carrier Host CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 20

21 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ Address of Sending system and day/time CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 21

22 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ Message type: CCI = Clearance Copy Initial CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 22

23 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ Message Sequence Number and Message Header CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 23

24 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 Flight Number and Departure Airport CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 24

25 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ A/C Type, Equipment Code, and P-Time CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 25

26 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ ATC Computer ID Code, and Exp FL CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 26

27 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ Cleared as Filed Clearance Indicated by THEN AS FILED SID and Transition is also provided. CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 27

28 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 Local ATC information and contact instructions CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 28

29 Cleared As Field Dispatch Copy Example QU ANPOCWN OKCTWXA CCI 003 CPDLC DCL DISPATCH MSG - NOT TO BE USED AS ACLEARANCE SWA9901 KMEM D/B737/J4 P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ Full route clearance copied on the last line for information to dispatch. Note: This line is not provided to the flight deck. CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y..D42U..ILC..OAL.MADN5.KOAK 29

30 Initial Modified Clearances These are clearances that are modified prior to flight deck receiving its first clearance. Will be sent in place of the CAF clearance. Two main types of Initial Modified Clearances Route is modified to connect to field flight plan downstream Usually used to amend the initial portion of the route (e.g., changing departure gates) Full route amendment or downstream amendment In both cases, the route change will be menu-loadable by the flight crew Depiction of a revision to the initial portion of the DCL 30

31 Initial Modified Clearance Flight Deck and Load Review In this example, the amendment is to MOL. After MOL, the rest of filed flight plan is as filed. 31

32 Initial Modified Connect to Downstream Dispatch Copy Example QU ANPOCWN.OKCTWXA CCI 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE SWA9901 KMEM MODIFIED RTE D/B737/J4 P FL300 REVISED RTE CLEARED TO GCK VIA EOS ICT ZUMIT.FOXOM, AFTER GCK CLEARED TO KOAK AS FILED CLIMB VIA SID EXCEPT MAINT 5000FT DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..KD48W..HVE..ILC..OAL.MADN 5.KOAK 32

33 Initial Modified Connect to Downstream Dispatch Copy Example QU ANPOCWN.OKCTWXA CCI Header for clearance that has been modified from flight plan filing 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE SWA9901 KMEM MODIFIED RTE D/B737/J4 P FL300 REVISED RTE CLEARED TO GCK VIA EOS ICT ZUMIT.FOXOM, AFTER GCK CLEARED TO KOAK AS FILED CLIMB VIA SID EXCEPT MAINT 5000FT DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..KD48W..HVE..ILC..OAL.MADN 5.KOAK 33

34 Initial Modified Connect to Downstream Dispatch Copy Example QU ANPOCWN.OKCTWXA CCI 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A Modified clearance with the revised route to GCK which was in original filing. After GCK, the rest of filing to KOAK is as filed. CLEARANCE SWA9901 KMEM MODIFIED RTE D/B737/J4 P FL300 CLEARED TO GCK VIA EOS ICT ZUMIT.FOXOM, AFTER GCK CLEARED TO KOAK ARPT AS FILED CLIMB VIA SID EXCEPT MAINT 5000FT DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..KD48W..HVE..ILC..OAL.MADN 5.KOAK 34

35 Initial Modified Connect to Downstream Dispatch Copy Example QU ANPOCWN.OKCTWXA CCI 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE Full route clearance is provided in dispatch SWA9901 KMEM MODIFIED RTE message. D/B737/J4 P FL300 CLEARED TO GCK VIA EOS ICT ZUMIT.FOXOM, AFTER GCK CLEARED TO KOAK ARPT AS FILED CLIMB VIA SID EXCEPT MAINT 5000FT DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..KD48W..HVE..ILC..OAL.MADN 5.KOAK 35

36 Initial Full Modified Clearance 36

37 Initial Modified Full Route Clearance Dispatch Copy Example QU ANPOCWN.OKCTWXA CCI 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE SWA9901 KMEM MODIFIED RTE D/B737/J4 P FL300 In the case of a full route clearance the entire clearance is provided in the dispatch message on this line KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..AVE.MARVN1.KOAK ZUMIT.FOXOM CLIMB VIA SID EXCEPT MAINT 5000FT DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS 37

38 Revised Clearances Clearances that are revised after the flight deck responds to the initial uplink. Similar to initial modified clearances, route can be revised in two ways: Initial portion to connect downstream Full route revision What are the SOPs for revised clearances? Do all revisions have to be approved by dispatch before acceptance by the flight deck? Weight/balance/fuel recalculations 38

39 Revised Clearance Connect downstream Dispatch Example QU ANPOCWN.OKCTWXA CCR CCR = Clearance Copy Revised 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE SWA9901 KMEM REVISED RTE DPP D/B737/J4 P FL300 REVISED RTE CLEARED TO GCK VIA EOS ICT REVISED DPP ZUMIT.FOXOM, AFTER GCK REST OF ROUTE UNCHANGED CLIMB VIA SID EXCEPT MAINT 5000FT KMEM.ZUMIT.FOXOM..EOS..ICT..GCK.. KD48W..HVE..ILC..OAL.MADN5.KOAK 39

40 Revised Clearance Connect downstream Dispatch Example Similar to Initial clearance except REVISED QU ANPOCWN.OKCTWXA CCR instead of MODIFIED. Also note other headers (RTE, DPP) 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE SWA9901 KMEM REVISED RTE DPP D/B737/J4 P FL300 REVISED RTE CLEARED TO GCK VIA EOS ICT REVISED DPP ZUMIT.FOXOM, AFTER GCK REST OF ROUTE UNCHANGED CLIMB VIA SID EXCEPT MAINT 5000FT KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..KD48W..HVE..ILC..OAL.MADN 5.KOAK 40

41 Revised Clearance Connect downstream Dispatch Example QU ANPOCWN.OKCTWXA CCR Instead of CLEARED TO in initial clearance, 005 CPDLC DCL DISPATCH REVISED MSG NOT RTE TO is used BE USED to indicate AS A this is a CLEARANCE revision to the initial clearance. SWA9901 KMEM REVISED RTE DPP D/B737/J4 P FL300 REVISED RTE CLEARED TO GCK VIA EOS ICT REVISED DPP ZUMIT.FOXOM, AFTER GCK REST OF ROUTE UNCHANGED CLIMB VIA SID EXCEPT MAINT 5000FT KMEM.ZUMIT.FOXOM..EOS..ICT..GCK..KD48W..HVE..ILC..OAL.MADN 5.KOAK 41

42 Revised Clearance Full Revised Route Dispatch Copy Example QU ANPOCWN.OKCTWXA CCR 005 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE SWA99901 KMEM REVISED RTE DPP DEP FREQ D/B737/J4 P FL300 REVISED RTE KMEM.ZUMIT.FOXOM..EOS.. AVE.MARVN1.KOAK REVISED DPP CHDLR2.ANSWA CLIMB VIA SID REVISED DEP FREQ

43 Revised UM80 and Load Review 43

44 Revised UM80 Load and Print 44

45 Non-Rte Revision Example Revised DEP FREQ 45

46 Pilot Response Message QU ANPOCWN.BNATWXA CCP 001 FDX9901 KMEM PILOT RESPONSE - WILCO 001 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE FDX9901 KMEM D/A320/Q P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y.. KD42U..ILC..OAL.MADN5.KOAK 46

47 Pilot Response Message QU ANPOCWN.BNATWXA CCP CCP message type = Pilot response 001 FDX9901 KMEM PILOT RESPONSE - WILCO 001 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE FDX9901 KMEM D/A320/Q P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y.. KD42U..ILC..OAL.MADN5.KOAK 47

48 Pilot Response Message QU ANPOCWN.BNATWXA CCP 001 FDX9901 KMEM PILOT RESPONSE - WILCO Pilot response provided as soon as pilot response is received by FAA 001 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE FDX9901 KMEM D/A320/Q P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y.. KD42U..ILC..OAL.MADN5.KOAK 48

49 Pilot Response Message QU ANPOCWN.BNATWXA CCP 001 FDX9901 KMEM PILOT RESPONSE - WILCO Corresponding clearance is also copied into this message. 001 CPDLC DCL DISPATCH MSG NOT TO BE USED AS A CLEARANCE FDX9901 KMEM D/A320/Q P FL300 CLEARED TO KOAK AIRPORT CHLDR2.ANSWA THEN AS FILED CLIMB VIA SID DEP FREQ CTC GROUND CONTROL 121.9, ADV ON INIT CTC YOU HAVE ATIS KMEM.CHLDR2.ANSWA..TUL..KA39Y.. KD42U..ILC..OAL.MADN5.KOAK 49

50 Dispatch Message Acknowledgement Required by FAA ground system as acknowledgement Retains similar format to current PDC acknowledgment However, departure time and gate assignment are ignored in response the Dispatch Message <SOH>QU BNATWXA. ANPOCWN <STX>CCA SWA N34522 P2145 A05 <ETX> {Flight ID } {Sequence Number} {Tail Number}{ Departure Time*} {Gate Assignment*} *Ignored by FAA system but not rejected if in message in response to DCL Dispatch Copy 50

51 Operational Problem Reporting Harris is setting up an Operational Problem Reporting (OPR) Process/System Helpdesk/call center Online reporting tool Track Data Comm trouble tickets for operational issues Unsuccessful clearance Failed Logon CPDLC Errors System Outages Harris can work with each carrier to align this process with your ops process for data link problem reporting Expect OPR Process documentation published in Spring

52 SUPPORT OF FAA TEST PROGRAM 52

53 Initial Testing Opportunities Initial AOC Testing Using the FAA DCL Trial System to send Dispatch Messages to IATA address of carrier s choosing Will need to work with CSP to route message correctly Follow up AOC Testing Using FAA s final interface for dispatch and PDC Initial Flight Deck Testing A/C can be located at any airport Log into the DCL Trial System at ACY to receive test clearances Important to begin develop procedures for flight deck 53

54 BACKUP 54

55 Field 18/DAT Proposed Codes for Data Comm # User Preference Data Comm Capability Description ICAO 2012 Fld 10a Data Comm Fld 18 DAT/ Comments Fld 10a order is any order and world-wide Z is required to get to DAT/ No spaces in actual DAT/ field 1a Voice only* Not equipped for ACARS or FANS; gets voice only E3J4J7 Default if user is not getting PDC or DCL. Field 10a may be optional. 1b Voice only* Equipped for ACARS and FANS but wants voice only E3J4J7 1VOIC E (opt) Optional. Only needed if users want to negate stored default and use voice only. 2a PDC only* Not ACARS equipped but gets PDC via manual means Z 1PDC Some aircraft are non-acars equipped, and 10a is physical equipage. Still get PDC via other means. Optional if currently getting PDC. 2b PDC only* Equipped only for ACARS PDC E3 Z 1PDC Optional if currently getting PDC. 2c PDC only* Equipped for ACARS PDC and FANS but wants PDC only E3J4Jx Z 1PDC Equipped for ACARS PDC and FANS 1/A or 1/A+, and possibly other capabilities (Jx). Identifies US domestic preference for PDC. Optional if currently getting PDC. * No ICAO FP change required if user currently gets PDC and does not want DCL. Current PDC designation will be the default. 55

56 Field 18/DAT Proposed Codes for Data Comm - cont d # User Preference Data Comm Capability Description ICAO 2012 Fld 10a Data Comm Fld 18 DAT/ Comments Fld 10a order is any order and world-wide Z is required to get to DAT/ No spaces in actual DAT/ field 3a FANS1/A DCL only Equipped for ACARS/PDC and FANS but wants FANS 1/A only E3J4Jx Z 1FANS Identifies US domestic preference for FANS 1/A DCL. 3b FANS 1/A+ DCL only Equipped for ACARS/PDC and FANS but wants FANS 1/A+ only E3J4Jx Z 1FANSP Identifies US domestic preference for FANS 1/A+ DCL. 4a FANS 1/A DCL/PDC Equipped for ACARS PDC and FANS 1/A, with primary/secondary preferences E3J4Jx Z 1FANS 2PDC Code number shows priority preference, e.g., FANS 1/A DCL is primary preference; PDC is secondary that will be used if primary is unavailable and feasible. 4b FANS 1/A+ DCL/PDC Equipped for ACARS PDC and FANS 1/A+, with primary/secondary preferences E3J4Jx Z 1FANSP 2PDC Code number shows priority preference, e.g., FANS 1/A+ DCL is primary preference; PDC is secondary that will be used if primary is unavailable and feasible. 5 ATN/FANS 1/A+ DCL/ PDC Equipped for ATN DCL, FANS 1/A+ DCL, and PDC; preference is ATN. E3J1J4Jx Z 1ATNB 2FANSP 3PDC Code shows preference, e.g, ATN B2 (ATNB) DCL, then FANS 1/A+ DCL, then PDC. This is one example only. ATN codes are TBD and will need to be worked. 56

57 Key Site IOC Dates KS 1: Salt Lake City (KSLC) 6/10/15 KS 2: Houston Intercontinental (KIAH) 07/16/15 KS 3: Houston Hobby (KHOU) 08/13/15 IOA Complete 11/16/15 In-Service Decision 12/09/15 57