Aircraft disposition data is aircraft oriented - not flight (leg) oriented. It will result in the update of one or more flight legs for the given FlightDepartureDate AircraftDispositionFlightData 0..* The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types: For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data IataASMRoutingData 0..* The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types: For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data IataASMRoutingData 0..* The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types: For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data IataASMAircraftData 0..* IataASMRoutingData 0..* The figure below shows the Airport Data Dictionary based data structure representing the following IATA ASM message types: For more information on the mapping from IATA ASM data to ADD, see: ASM data to ADD data IataASMRoutingData 0..* The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Diversion Message (DIV) as defined in the Airport Handling Manual (AHM) 781. The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Load Message (LDM) as defined in the Airport Handling Manual (AHM). For more mapping information, see: LDM data to ADD data IataLoadCompartmentData The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Movement Message (MVT) as defined in the Airport Handling Manual (AHM). For details about mapping from AHM 780 AIRCRAFT MOVEMENT MESSAGE to ADD, see MVT data to ADD data The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Passenger Assistance List (PAL), Change Assistance List (CAL) and Passenger Service Message (PSM). PAL and CAL are defined in the Passenger Services Conference Resolutions Manual (PSCRM) Recommended Practice 1708a. For more mapping information, see: PRM data to ADD data The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA Passenger Transfer Message (PTM) as defined in the Passenger Services Conference Resolutions Manual (PSCRM) RP 1718. If part '1' comes again all transfer data previously received for this flight leg should be discarded, as it will be resent. For IATA messages with multiple "parts". IATA based identifier for this flight, usually issued long before the flight actually takes place. FlightId is normally the concatenation of OperatingAirlineIATA, FlightNumber and OperationalSuffix. FlightId typically identifies a flight to the majority of systems, but it is not unique across time. It's unique only in conjunction with FlightDepartureDate. Exception: Some airlines use their ICAO code (OperatingAirlineICAO) instead of OperatingAirlineIATA. This might be because they aren't an IATA member or because they just prefer the ICAO code. Regardless, this means that it is allowed to use OperatingAirlineICAO as part of FlightId. FlightId is then defined as the concatenation of AirlineIATAorICAO, FlightNumber and OperationalSuffix. Date part of SOBTlocal. Departure airport IATA code (see AirportIATA for description of term). Arrival airport IATA code (see AirportIATA for description of term). This is the flight leg passengers on the flight leg identified above transfer to. NB! If IataPtmTransferToData is "missing" then all previously received PTM data for this flight should be deleted. New PTM data will most likely be forthcoming. The name string as it appears on a ticket. Can contain multiple names. The number of adult passengers in some context. The number of children in some context. The number of infants in some context. The number of bags in some context. The figure shows the elements and structure of an Airport Data Dictionary (ADD) based entity representing an IATA SSIM file row. The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types: For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types: The table below lists, for ease of reference, the elements included in the entity. For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types: The table below lists, for ease of reference, the elements included in the IataSSMDeleteData. For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data The figure below shows the Airport Data Dictionary based data structure representing the following IATA SSM message types: The table below lists, for ease of reference, the elements included in the IataSSMInsertUpdateData. For more information on the mapping from IATA SSM data to ADD, see: SSM data to ADD data IataSSMPeriodData IataSSMAircraftData IataSSMRoutingData If departure and arrival airport is omitted FlightId and FlightDepartureDate must identify a single leg in the relevant context. ResponseStatusCode indicates if the operation succeeded or failed, and if it failed - why. ResponseStatusText is a textual description of ResponseStatusCode. For all operations the set of response codes must be defined. The actual set is dependent upon the context. Must be defined!AircraftDispositionData
Entity / ADD element
If departure and arrival airport is missing then the AircraftRegistration apply for the whole flight, potentially multiple legs.
FuelRequestData
Entity / ADD element FuelRequestData
IataASMCancelData
Entity / ADD element IataASMCancelData Only departure/arrival airport are used for SubmitASMCancelData.
IataASMChangeFlightIdData
Entity / ADD element Only departure/arrival airport are used for IataASMChangeFlightIdData.
IataASMInsertUpdateData
Entity / ADD element IataASMInsertUpdateData
IataASMReinstateData
Entity / ADD element IataASMReinstateData Only departure/arrival airport are used for SubmitASMReinstateData.
IataDivData
Entity / ADD element
IataLoadData
Entity / ADD element IataLoadData
IataLoadDestinationData
IataMvtData
Entity / ADD element IataMvtData IataDelay
IataPrmData
PSM is defined in the Passenger Services Conference Resolutions Manual (PSCRM) Recommended Practice 1715.
IataPtmData
Entity / ADD element Comments IataPtmData Identifies the flight leg passengers transfer from and to other light legs.
The transfers will be on the arrival airport.IataPtmTransferToData 0..*
There will often be multiple data sets for the same flight leg.
110626443
Entity / ADD element
IataSSMChangeFlightIdData
IataSSMChangePeriodData
Entity / ADD element Comments IataSSMChangePeriodData See definition → See definition → Entity / ADD element Comments IataSSMPeriodData
IataSSMDeleteData
Entity / ADD element IataSSMDeleteData
IataSSMInsertUpdateData
Entity / ADD element IataSSMInsertUpdateData
70550297
Entity / ADD element Comments
ResponseStatus
statusCode : ResponseStatusCode statusText : ResponseStatusText
TransData
CorrelationId SourceOrganization SourceData
A textual description of ResponseStatusCode.
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