1 / 1

En Route: Flight Data Publication

En Route: Flight Data Publication.

courtney
Télécharger la présentation

En Route: Flight Data Publication

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. En Route: Flight Data Publication Today in the NAS there are multiple versions of flight data, depending upon the state of flight. Prior to filing, TFM flight data is based off of various schedule data, airline provided data, historical information and/or foreign flight plans not yet processed by En Route. Once filed, flight data is processed by ERAM and is sent to many ATM systems. Subsequent flight data updates for active aircraft are managed by the En Route Domain and distributed to other ATM systems. One goal of better flight data management in the Segment 1 timeframe is to improve the flight data processing to ensure consistency of flight data across the NAS and to consolidate the flight data maintained by multiple systems into a distributed flight object accessible by all. The distributed flight object will include data such as the filed flight plan, the currently-cleared route, the “ATC-intended” route to be cleared, the predicted aircraft trajectory, and the current state of the flight. The distributed flight object will be comprised of elements supplied by multiple domains, and through this data sharing and coordination, the Flight Data Publication Service will support trajectory-based ops between En Route, Terminal, and TFM domains. ICE Gateway (FTI) The operational threads to be integrated across these domains will require the ability of other systems to update flight data in the distributed flight object. Examples include aircraft taxi status FTI NORAD information and clearance delivery status from Terminal systems such as the TDLS and the EFSTS. Other ATM systems such as TFMS will be synchronized via flight data received from the En Route Domain. Conversely, the En Route Domain flight object will be updated by flight data received from TFMS. Flight Data Flight Data ERAM Flight Data TDDS SWIM Service TDLS EFSTS WJHTC TFMS SWIM Service ARTCC ASDE-X RVR This SWIM service will replace and enhance legacy flight data interfaces provided today by FDIO and HADDS/CMS. Terminal Cluster (TRACON & TOWER) Product Fact Sheet – Flight Data Publication

More Related