Download
1 / 8
80 likes | 190 Views
AOC/FOC Interface for Data Comm Production System. To: AOC WG From: Data Comm Production Sub-Team Date: 07/11/12. Recap Last Telecon Decisions- 7/02/12. Requirements for Production System (2015)
E N D
AOC/FOC Interface for Data Comm Production System To: AOC WG From: Data Comm Production Sub-Team Date: 07/11/12
Recap Last Telecon Decisions- 7/02/12 • Requirements for Production System (2015) • Add route string to DCL Courtesy Copy even if flight is Cleared as Filed, as FYI for AOC [Applies to both Trials and Production systems?] • FAA will send a new message (Gate ID Request message) to AOC when DCL is approved by controller. AOC will respond with Gate ID. Applies to both Trials and Production systems. • FAA will send the DCL Courtesy Copy to AOC when actual uplink is sent to pilot. Applies to both Trials and Production systems. • ICAO 2012 Flight Plan is a viable mechanism for AOCs to provide clearance delivery information to FAA, e.g., whether a specific flight will get a legacy PDC or DCL. New equipage/preference codes apply to Production system only. Trials will use Remarks field in current flight plan; no change for ICAO 2012 flight plan.
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. No change to PDC exchange. • Gate ID Request/Response messages will be exchanged for all DCL flights • If users do not currently provide gate, only requirement for DCL is an AOC Host computer system response in the agreed to DCIT format. • Gate Changes • No requirement for users to provide unsolicited Gate ID messages for gate changes after the initial message exchange • Error Handling. • Same as today (for PDC) • If there is a mismatch or missing referent message number for an acknowledgement from AOC, no error will be returned by FAA
Gate ID Request : Summary cont’d • Gate ID Request Message from FAA to AOC • Similar header to DCL Courtesy Copy with unique identifier as Gate ID Request message • Flight Identification includes: Flight ID (e.g., XYZ123), Tail Number if available, and Departure Airport. • Format being worked today • Response Message from AOC to FAA • 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. • Format being worked today
Next Steps • Determine if any other DCIT document changes needed • DCIT Plenary July 12 • Coordination with larger community for ICAO 2012 flight plan codes in Field 18/DAT Questions?
Initial Departure Clearance : Gate ID and CC messages Tower Controller Pilot Avionics Data Comm Flight Data AOC/FOC Automation 1. Flight Plan Circa P-Time- 60 min 2. Flight Data 3. Flight Strip Circa P-Time- 30 min 4. Clearance for approval 5. Approved Departure Clearance 6. Session Start Circa P-Time- 20 min 7. Gate ID Request 8. Gate ID Response This case shows a revision occurs before pilot downlink request. Is the same as nominal without any change. 9. Revised Flight Data Pilot will request DCL x minutes before departure 10. Rev Approve Clearance 11. Departure Clearance Request 12. Departure Clearance 13. DCL CC 14. DCL CC Ack 15. Departure Clearance Response
