NILABLE TouchAndGoData DiversionAirportICAO is the airport the flight diverted from. A value here means that the aircraft has been diverted. ArrivalAirportICAO further up is the new destination for this flight leg. Identification Required if UniqueFlightLegId isn't included. Required if UniqueFlightLegId isn't included. Required if UniqueFlightLegId isn't included. Strongly preferred if UniqueFlightLegId isn't included. Contains the data elements to set check-in data. Identification NILABLE Contains the data elements to set gate data. Identification Required. Resource Management Data in this setting is data a RMS / Apron Management / Aircraft Parking system updates for one flight leg. A RMS system is by nature airport oriented and will often operate on turnarounds. In this setting it's usual to update two flight legs, the inbound flight leg and the outbound flight leg. Please remember that arrival and departure data on a flight leg is on two airports, but when viewed as a turnaround arrival and departure data is on the same airport, but on two flight legs. A RMS system will typically only update: Contains the data elements to set check-in data. IdentificationAtmData
UniqueFlightLegId If UniqueFlightLegId is included it is used as the only identification element. It must have been received previously by data from the airport system responsible for allocating it, typically an AODB. Callsign AircraftRegistration SSRCode DepartureAirportICAO ArrivalAirportICAO AtmCdmStatus AtmFlightLegStatus FlightLegStatus AircraftInZone TSAT TOBT IOBT
Required if available.EOBT
Required if available.AOBT EXOT AXOT CTOT ETOT ATOT ELDT NILABLE
Required if available.ELDTAccuracy EXIT AXIT EIBT
Required if available.AIBT AircraftICAOType WakeTurbulenceCategory OperatingAirlineICAO FlightServiceTypeICAO FlightServiceTypeExtended MilitaryFlightOwner NumberOfAircraft To remove touch&go data set the TouchAndGoCount to '0' (zero) for the given airport. NILABLE FlightRule SIDRoute STARoute RunwayDeparture RunwayArrival DiversionAirportICAO
AtmDataIn
BaggageData
Departure baggage data NILABLE NILABLE NILABLE NILABLE
Arrival baggage dataNILABLE NILABLE NILABLE NILABLE NILABLE NILABLE BaggageBinData
BaggageDataIn
CheckInData
Required if UniqueFlightLegId isn't included. Required if UniqueFlightLegId isn't included. Required if UniqueFlightLegId isn't included. Strongly preferred if UniqueFlightLegId isn't included. Check-in data NILABLE NILABLE NILABLE NILABLE
CheckInDataIn
ArrivalData
PaxCanDisembark NILABLE PaxBusIsNeededArrival NILABLE PaxBusRemarkArrival NILABLE FlightIsDomesticTransfer NILABLE ELDT TLDT NILABLE ALDT NILABLE SIBT NILABLE EIBT NILABLE AIBT NILABLE
DepartureData
AircraftParkingPositionDeparture PaxCanEmbark PaxBusIsNeededDeparture PaxBusRemarkDeparture NILABLE ASBT ASRT NILABLE ASAT NILABLE SOBT EOBT NILABLE AOBT NILABLE ETOT TTOT NILABLE ATOT FuelRampRequested NILABLE
FlightLegData
FlightLegDataIn
GateData
Required if UniqueFlightLegId isn't included. Required if UniqueFlightLegId isn't included. Required if UniqueFlightLegId isn't included. Strongly preferred if UniqueFlightLegId isn't included. Gate data NILABLE NILABLE NILABLE NILABLE NILABLE NILABLE
GateDataIn
RmsData
NB! This will be either the inbound flight leg or the outbound flight leg of a turnaround.Departure data Departure data for the outgoing flight leg. If used, arrival data is not expected to be present. GateDeparture NILABLE AircraftParkingPositionDeparture NILABLE UniqueFlightLegIdLinkedArrival NILABLE Arrival data Arrival data for the incoming flight leg. If used, departure data is not expected to be present. GateArrival NILABLE AircraftParkingPositionArrival NILABLE UniqueFlightLegIdLinkedDeparture NILABLE
RmsDataIn
TransData
CorrelationId SourceOrganization SourceData
If UniqueFlightLegId isn't available.
Strongly preferred if available, but must be used with other identifiers like Callsign, DepartureAirportICAO, ArrivalAirportICAO and some of the time elements.
If UniqueFlightLegId isn't available.
Strongly preferred if available, but must be used with other identifiers like IFPLID, DepartureAirportICAO, ArrivalAirportICAO and some of the time elements.
Strongly preferred if available, but must be used with other identifiers like IFPLID, DepartureAirportICAO, ArrivalAirportICAO and some of the time elements.
NILABLE
NILABLE
Required if available.
Required if available.
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
NILABLE
If UniqueFlightLegId is included it is used as the only identification element. It must have been received previously by data from the airport system responsible for allocating it, typically an AODB.
If UniqueFlightLegId is included it is used as the only identification element. It must have been received previously by data from the airport system responsible for allocating it, typically an AODB.
NILABLE
NILABLE
NILABLE
If UniqueFlightLegId is included it is used as the only identification element. It must have been received previously by data from the airport system responsible for allocating it, typically an AODB.
UniqueFlightLegId is required to identify the relevant flight leg.
Identifier that can be used to correlate messages, transactions, log entries etc. The identifier should be unique across all relevant systems. It is the responsibility of the creator of the message/transaction/log entry/... to guarantee uniqueness. The CorrelationId can for instance be a GUID, or something shorter based on site specific rules.
Name of the organization/company that created the original data. This will typically be an airline company or an handler. The value set are site specific.
UTC timestamp for when the source was updated. If unknown, use current (UTC) time.
SourceData will only exist when the source data is something else than XML or JSON. SourceData will typically be the IATA message or an EFD message from Eurocontrol.
Overview
Content Tools