AOC/FOC Interface for Data Comm Production System To: AOC WG From: Data Comm Production Sub-Team Date: 08/22/12 Federal Aviation Administration Data Comm and ICAO FP: Summary • Current Approach – Trials system will use Field Remarks field of current 4444 ICAO FPL1 • Users to file “FRC DCL” in Field 18/RMK – Production system (IOC 2015) will use Field 10a and Field 18 DAT/ of ICAO 2012 FPL • Field 18 DAT/Codes used to identify flights getting DCL or PDC • Field 18 DAT/ Codes will include a primary/secondary hierarchy – Designate preferred clearance delivery mechanism – Designate secondary “back up” delivery mechanism – Flight plan preferences take priority over any other sources 1 DCP SE AOC Sub-team 22 August 2012 Flight Plan - ICAO FPL, NAS FP Federal Aviation Administration 2 Fld 18/DAT – Proposed Codes for Data Comm # User Preferenc e Data Comm Capability Description ICAO 2012 Fld 10a 1 Voice only Equipped for ACARS and FANS but gets voice only E3J4J7 2a PDC only Not ACARS equipped but gets PDC via manual means Z 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 No change from current filing. If no Data Comm code in DAT/, then will get voice 1PDC Some aircraft are non-ACARS equipped, and 10a is physical equipage. Still get PDC. Optional; legacy PDC not being changed. 2b PDC only Equipped only for ACARS PDC E3 Z 1PDC Optional; legacy PDC not being changed. 3 PDC only Equipped for ACARS and FANS but gets PDC only E3J4J7 Z 1PDC Equipped for ACARS PDC and FANS 1/A+, and possibly other capabilities. Identifies US domestic preference for PDC. 4 FANS DCL only Equipped for ACARS and FANS but gets FANS only E3J4J7 Z 1FANSP Identifies US domestic preference for FANS 1/A+ DCL. Would be1FANS if 1/A (Trials only) 5 FANS DCL/PDC FANS DCL if available; PDC if not E3J4J7 Z 1FANSP 2PDC Code shows priority preference, e.g, FANS 1/A+ DCL is primary preference, then PDC. 6 ATN/FANS DCL, PDC Equipped for ATN DCL, FANS DCL, and PDC; 1st preference is ATN. E3J1J4 Z 1ATNB 2FANSP 3PDC Code shows preference, e.g, ATN B2 (ATNB) DCL, then FANS 1/A+ DCL, then PDC. ATN is placeholder only and specific codes are TBD. DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 3 Gate ID Request : Summary – Scope • • Gate ID Request message is designed to provide same functionality as in current response by AOC to PDC from FAA Will be sent only to those users who currently supply Gate ID in PDC response – Gate ID Request Message from FAA to AOC • • Similar header to DCL Courtesy Copy with unique identifier as Gate ID Request message Flight Identification (e.g., XYZ123), Tail Number if available, and Departure Airport. DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 4 Gate ID Request : Summary – cont’d – Response Message from AOC to FAA • • • • Unique response message for this request message Similar header to Gate ID Request message with unique identifier as Gate ID Response message and sequence number from request message Flight Identification is same, e.g., Flight ID (e.g., XYZ123), Tail Number if available, and Departure Airport. Gate ID field content – If gate known, gate number is inserted into this field – If gate is unknown, “G” is inserted into this field. DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 5 Gate ID Request: Proposed Format ^AQU {IATA address TO } . {IATA address FROM} {DDHHMM} ^BGID { Sequence Number} DCL Gate ID Request {Flight ID } {Airport Departure} ^C Line Text Notes 1 ^AQU ANPOCWN Destination address (e.g., AOC automation) 2 .OKCTWXA 081251 Automation System address (e.g. TDLS at OKC) and day/time of message 3 ^BCGI SMI (message type identifier) 4 001 Sequence number and message type notification 5 UAL123 KBWI Flight ID and departure airport 18 ^C ETX DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 6 Gate ID Response: Proposed Format Field name Field Explanation {IATA address TO } Address of TDLS at destination tower . {IATA address FROM} {DDHHMM} Address of airline host sending the Response Flight ID Departure Airport 3-char customer ID (e.g. SWA, not WN) plus numerals This should match the sequence number of the BGID that this acknowledges Departure Airport identification, e.g., Gate Assignment Default if missing is “G” Sequence Number Time message was sent to TDLS {field values in brackets. Field identifiers marked with “#” from table below} ^AQU {IATA address TO } . {IATA address FROM} {DDHHMM} ^BC?R (Verify with A. Onken) {Flight ID *A} { Sequence Number} {Departure Airport} {Gate Assignment} ^C DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 7 DCL Service Fallback Concept: Recap • If CPDLC service for DCL is not available, FAA automation will “fall back” to PDC – AOC/User must tell FAA they want this to occur; system-wide, not per airport • Can be done in ICAO FP preferences in Field 18/DAT • An additional option is for AOC to provide this fallback preference via Web Access portal – Fallback preferences can be stored in the SDB in TDLS automation and used when applicable – Fallback only occurs if AOC/User has designated PDC as the secondary clearance type preference DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 8 DCL Service Fallback Concept: Recap cont’d • At July DCIT, ATC and Flight Deck WGs agreed to review concept. May have new “rules” or constraints – Trials will start with procedures at MEM; may need automation support for future sites – For Production system requirements, need to clarify what will automation support vs what will be done via procedures? Still working – Assumptions: • If flight has been “processed” as DCL, no PDC will be sent, e.g., if past normal “drop” time, flights will go to voice • New flights or those earlier than “drop” time, will get PDCs if user has indicated this via flight plan codes or other mechanism DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 9 Questions? DCP SE AOC Sub-team 22 August 2012 Federal Aviation Administration 10