1 / 10

AOC/FOC Interface for Data Comm Production System

AOC/FOC Interface for Data Comm Production System. To: AOC WG From: Data Comm Production Sub-Team Date: 08/22/12. Data Comm and ICAO FP: Summary. Current Approach Trials system will use Field Remarks field of current 4444 ICAO FPL 1 Users to file “FRC DCL” in Field 18/RMK

shanon
Download Presentation

AOC/FOC Interface for Data Comm Production System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AOC/FOC Interface for Data Comm Production System To: AOC WG From: Data Comm Production Sub-Team Date: 08/22/12

  2. 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 Flight Plan - ICAO FPL, NAS FP

  3. Fld 18/DAT – Proposed Codes for Data Comm

  4. 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.

  5. 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.

  6. Gate ID Request: Proposed Format

  7. Gate ID Response: Proposed Format

  8. 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

  9. 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

  10. Questions?

More Related