Tell me more about this TFMData service.
The Terminal Flight Data service provides data that TFMS receives from their partner airline systems as an aggregate feed to the FAA’s Terminal Flight Data Manager (TFDM) system and to Collaborative Decision Making (CDM) participants. TFDM uses this airline data, along with data from other FAA systems, to provide their Surface Collaborative Decision Making (CDM) capability. The Terminal Flight Data service adheres to the FIXM (Flight Information Exchange Model) standard.
This Terminal Flight Data service includes the following terminal and surface data:
- AOBT (Actual Off-Block Time)
- ATOT (Actual Takeoff Time)
- ALDT (Actual Landing Time)*
- AIBT (Actual In-Block Time)
- EOBT (Earliest Off-Block Time)
- ERTD (Earliest Runway Time of Departure)
- IOBT (Initial Off-Block Time)
- Flight Cancellation
- Flight Intent (to hold in Airport Movement Area during departure)
- Gate Assignment / Departure Stand Assignment
- and more….
* Note: The terminal element ALDT (Actual Landing Time) was mistyped in the TFMData v2.0.5 schema as ALTD. The correct spelling should be ALDT. This has been corrected in the v3.0 update to the TFMData schema.
There is also useful information in the presentation slides from the “TFMS Developer Workshop”. The focus of this workshop was on developing TFMData v2.0.5 (TFMS R13) interfaces with the Request/Reply service and the Terminal Flight Data service.
Refer to the following for the high-level layout of the Terminal Data schema:
(Note that the “tfdinput” feed was reserved for future use but never actually used, and hence will be removed from a future release of the TFMData schema.)
Whoops! Is that a typo in the TFMData v.2.0.5 schema for Terminal?
Yes, you’re right! The terminal element ALDT (Actual Landing Time) was mistyped in the v2.0.5 schema as ALTD. The correct spelling should be ALDT. This has been corrected in the v3.2 and later versions of the TFMData schema.