Overview
The figure below shows the all of the entities in AvinorFlightLegState. Details about each entity is on the relevant page.
Information about the aircraft that flew this flight leg.
Main entity that contains all the elements that make up the state of a flight leg.
The figure below shows the entities that are directly associated with AvinorFlightLegStateData.
Baggage information related to the flight leg.
NB! Information about transfer baggage are placed in PassengerData.
| | ADD Term | Description / Comments |
|---|
| BaggageDepartureData |
| | BagCanBeLoadedCount | The number of bags that can be loaded onto this aircraft on this airport. This includes local bags, and expected transfer bags. | | BaggageCountLoaded | Number of bags loaded onto an aircraft. | | BaggageWeightLoaded | Weight in kilos of baggage loaded onto an aircraft. | |
| | A baggage bin. Typically where a baggage handling system places the bags that are sorted. | | Code/string defining which baggage segregation that are associated with the relevant Bin. Codes are system/handler specific. |
|
| | BaggageArrivalData |
| BaggageClaimUnit | Baggage belt (carousel) onto which passenger bags are loaded for collection by passengers on arrival flights.
There are a set of BaggageClaimUnits for each airport. | | BeltFirstBagEstimate | Estimated time for BeltFirstBag. | | BeltFirstBag | UTC time the first passenger bag was loaded onto a baggage belt (carousel). | | BeltLastBag | UTC time the last passenger bag was loaded onto baggage a belt (carousel) | | BaggageCountUnloaded | Number of bags unloaded off an aircraft. | | BaggageWeightUnloaded | Weight in kilos of baggage unloaded off an aircraft. |
|
Information about the cargo of this flight leg.
Entity containing any data related to crossing of charging areas. This would typically be when the aircraft entered a new FIR.
Entity containing any check-in data connected to this flight leg.
| | ADD Term | Description / Comments |
|---|
CheckInStatus | The check in status of a single flight that is allocated to one or more check in desks. | | CheckInOpen | The time (UTC) when the first check-in desk opened against this flight. | | CheckInClose | The time (UTC) when the last check-in desk against this flight closed. | | CheckInDisplayText | A text "message" related to check in that are meant to be displayed to passengers, typically to indicate where check in for this departure is. |
|
Entity containing any codeshare data connected to this flight leg.
Entity containing any de-ice data connected to this flight leg.
| | ADD Term | Description / Comments |
|---|
| DeIceIsRequested | A boolean value indicating that de-icing, or anti-icing, is requested for the relevant aircraft. | | DeIceProcessStatus | Indicates the status of the de-icing process. | | DeIcePlatform | The platform where the de-icing occurred. The names are airport specific. De-icing is typically done either on stand or on a dedicated de-icing platform. | | DeIceParkingPosition | Indicates the AircraftParkingPosition where de-icing was done. See also DeIcePlatform. | | DeIceConditionCode | The code for the (weather) condition that led to de-icing being requested, and possibly performed. The codes listed under "Legal values" should always be supported. Additional codes can be defined if necessary. Codes defined here are always two digits. | | DeIceAirTemperature | The air (ambient) temperature where the de-icing process occurs. | ERZT | Estimated Ready for De-icing Time. The estimated time when the aircraft is expected to be ready for de-icing operations. Always UTC time. | | ARZT | Actual Ready for De-icing Time. The time when the aircraft is ready to be de-iced. Always UTC time. | | ECZT | Estimated Commencement of De-icing Time. The estimated time when de-icing operations on an aircraft are expected to start. Always UTC time. | | ACZT | Actual Commencement of De-icing Time. The time when de-icing operations on an aircraft starts. Always UTC time. | | EEZT | Estimated End of De-icing Time. The estimated time when de-icing operations on an aircraft are expected to end. Always UTC time. | | AEZT | Actual End of De-icing Time. The time when de-icing operations on an aircraft end. Always UTC time. | | EDIT | Estimated De-icing Time. Metric: EEZT – ECZT. | | ADIT | Actual De-icing Time. Metric: AEZT – ACZT | | MechanicalDeIceIsUsed | A boolean value indicating that mechanical de-icing in some form is used on the relevant aircraft. | | AntiIceStartHoldoverTime | The start of the anti-ice holdover time. This will typically be when the first truck started to apply anti-ice fluid. Always UTC. | | HandlerCode | Identifies a Handler. | | HandlerName | Name of a Handler. |
|
| | AodbDeIceFluidUsage |
| | DeIceFluidType | Indicates which de-ice fluid type, including water, that has been used on the relevant aircraft. Each fluid type is specified separately, typically with the volume used. | | DeIceFluidVolume | Indicates the volume used of the relevant DeIceFluidType. |
|
Entity containing any delay data connected to this flight leg, departure or arrival.
DisplayData indicates if the information in the corresponding AvinorFlightLegStateData should be displayed or not. This is primarily for monitors, but should also be respected for other clients. It might mean that the data also should be removed from services, but that decision should be on a per service basis.
NB! FlightLegStateMetadata.ClassificationLevel MUST be respected. Only flight legs marked as "PUBLIC" should ever be displayed, or made available through services, to the general public.
The following matrix shows the possible combinations of ClassificationLevel and PublicDisplayStatus.
| ClassificationLevel | PublicDisplayStatus | Result |
|---|
| 1 - «PUBLIC» | '0' | Should not be shown/made available without authorization. |
1 - «PUBLIC» | '1' | Can be shown/made available everywhere |
| 1 - «PUBLIC» | '2' | Should only be visible at the departure airport |
| 1 - «PUBLIC» | '3' | Should only be visible at the arrival airport |
| 2 - «NON-PUBLIC» | All values | Should not be shown/made available without authorization. |
3 - «RESTRICTED» | All values | Should not be shown/made available without authorization. |
Information related to how the flight leg data should be displayed.
| | ADD Term | Comments |
|---|
| Indicates if the data set is for public display.
Default value is '1'. | | UTC time when next information about the flight is expected. |
|
Entity containing information about the airport this flight leg diverted from.
The first DiversionFromData entity is always the original arrival airport with corresponding timestamps. If an aircraft is diverted multiple times there will be multiple instances of DiversionFromData.
See Specification: Rerouting of flights and flight legs for more information on how diversions should be handled.
FlightLegStateMetadata give extra information about AvinorFlightLegStateData, and not about the flight leg.
| | Event | Values used: - "CREATE"
The flight leg has been created. Creation is alway from only one source, given in CreatedSource. - "UPDATE"
The flight leg has been updated. Most common event. One update can include data from multiple sources.
If no "CREATE" event has been received an "UPDATE" should be handled as a "CREATE". - "DELETE"
The flight leg has been removed/deleted. It will never be reinstated and should just be remover/deleted in all systems. - "MERGE"
This flight leg has been merged into another flight leg, identified by MergedIntoUniqueFlightLegId. - "REQUEST"
The data set has been produced as a result of a request operation. This includes Avinor internal operations to force synchronization of systems.
| | CreatedSource | CreatedSource will be the first element in DataSources. | | CreatedSourceOrganization | The organization that is the source of CreatedSource. | CreatedTimestamp |
| | LastUpdatedTimestamp |
| | DataSources | NB! As data comes from a new source, and is matched to one flight leg, the source is just added to the DataSources list regardless of the new data actually updating the flight leg or not. NB! In some cases DataSources can be longer than allowed by the type. In this case sources should be removed from the DataSources string until it is within the allowed length. Remove the sources starting with the oldest. The first source to be removed would then be the CreatedSource. | | ReferenceDataStatus |
| | ClassificationLevel | NB! ClassificationLevel = "PUBLIC" does not mean that all information, like passenger numbers, are public information, only that the flight leg itself is. Default value is "NON-PUBLIC". | | MergedIntoUniqueFlightLegId |
| | MessageTimestamp | Tminestamp indication when this AvinorFlightLegStateData dataset was created. | | CorrelationId | Generated by the Avinor AODB. Used for distributed debugging. |
|
Entity containing any gate data connected to this flight leg.
Entity containing any handler data connected to this flight leg, departure or arrival.
Entity containing flight segment related load data for single or multi leg flights. See Specification: IATA - Calculating PAX numbers from Load data.
Load data is segment oriented data. A flight segment is what you can buy a ticket for.
- For a single leg flight, A to B, the flight segment is AB.
- For a multi leg flight, A to B to C to D the following flight segments exist: AB, AC, AD, BC, BD, CD
Load data are submitted at each departure airport for the remaining segments.
Passenger data, including data about transfers from other (previous) flights and transfers to other (later) flights.
Entity containing any remarks connected to this flight leg.
| | ADD Term | Description / Comments |
|---|
RemarkTimestamp |
| RemarkType | The following remark types are used by Avinor AODB: - PublicGate
- PublicCheckin
- PublicDeparture
- PublicArrival
- StaffDeparture
- StaffArrvial
| RemarkText | Free text |
|
| MAOS Code | MAOS Description | Direction | Data Definition (max 16 characters) | Explanation |
|---|
| PG | PublicGateRemark | D | PublicGate | The remark shall be shown on all gate screens. Typical use is telling passengers on row 16-32 that is time to board the plane. |
| PC | PublicCheckinRemark | D | PublicCheckin | The remark shall be shown on all check-in screens. Typical use is letting pax know that check-in area has been changed. |
| PD | PublicDepartureRemark | D | PublicDeparture | The remark shall be shown on all screens where the departure flight is shown, both for pax and employees. |
| SD | StaffDepartureRemark | D | StaffDeparture | The remark shall only be shown to employees in the client. There is also a separate field for this in the xml-feeds. This remark is not to be displayed on any pax screens. |
| PA | PublicArrivalRemark | A | PublicArrival | The remark shall be shown on all screens where the arrival flight is shown, both for pax and employees. |
| SA | StaffArrivalRemark | A | StaffArrvial | The remark shall only be shown to employees in the client. There is also a separate field for this in the xml-feeds. This remark is not to be displayed on any pax screens. |
Entity containing any data related to crossing of touch and gos.
Entity containing number of passengers and baggage that
- are expected to be transferred from an arriving flight to this flight leg.
- are expected to be transferred from this flight leg to departing flights.
| | ADD Term | Description / Comments |
|---|
| UniqueFlightLegId | A system specific unique identifier for a flight leg. Can be anything, and doesn't have to be meaningful in any way. Proposed terms will never change and will never be reused. | | FlightId | 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. | | FlightDepartureDate | The scheduled date (based on UTC) of departure of flight. For flights with multiple legs this is the departure of the first leg. This date must not change once set as it is used to make the FlightIds unique. | | DepartureAirportIATA | Departure airport IATA code (see AirportIATA for description of term). | | ArrivalAirportIATA | Arrival airport IATA code (see AirportIATA for description of term). | | SOBT | Scheduled Off-Block Time. The time that an aircraft is scheduled to depart from its parking position. Always UTC time. | | SIBT | Scheduled In-Block Time. The time that an aircraft is scheduled to arrive at its first parking position. Always UTC time. | | PaxAdult | The number of adult passengers in some context. | | PaxChild | The number of children in some context. | | PaxInfant | The number of infants in some context. | | BaggageCount | The number of bags in some context. |
|
