DeIceData describes the current de-ice status of the flight leg (aircraft).
|
| ADD element | Description |
|---|
| FlightLegIdentifier | FlightLegIdentifier is a set of attributes that uniquely can identify a FlightLeg in different contexts. It consists of the following:None are required, but enough have to be present to actually uniquely identify a FlightLeg. | | 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. | | DeIceFluidUsage | Entity | | 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. | | Indicates the volume used of the relevant DeIceFluidType. |
|
This is the standard Airport Data Dictionary FlightLegIdentifier. None of the elements are required, but enough have to be present to actually uniquely identify a flight. |
IFPLID | Defined by Eurocontrol as "A unique flight plan identifier, assigned by the IFPS". Two letters followed by eight digits. | | callsign | A call sign is used to uniquely identify an aircraft using the airspace around a particular airport. Call signs in aviation are derived from several different policies, depending upon the type of flight operation. In most countries, unscheduled general aviation flights identify themselves using the call sign corresponding to the aircraft's registration number. Commercial operators, including scheduled airline, air cargo and air taxi operators, will usually use an ICAO or FAA-registered call sign for their company. These will typically consist of the ICAO code of the operating airline followed by a flight identification. The flight identification is very often the same as the flight number, but could be different due to call sign confusion, if two or more flights close to each other have similar flight numbers (i.e. KLM649 and KLM645 or BAW466 and BAW646). | | aircraftRegistration | An aircraft registration is a unique alphanumeric string that identifies an aircraft. In accordance with the Convention on International Civil Aviation all aircraft must be registered with a national aviation authority and they must carry proof of this registration in the form of a legal document called a Certificate of Registration at all times when in operation.
An aircraft can be re-registered in special cases, for instance if it's sold to an operator in another country. | | ssrCode | Secondary Surveilence Radar CodeA four-digit octal number received from the aircraft transponder when it is interrogated by a secondary surveillance radar (SSR). | | 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). | | departureAirportICAO | Departure airport ICAO code (see AirportICAO for description of term). | | arrivalAirportICAO | Arrival airport ICAO code (see AirportICAO for description of term). |
|
| | statusCode : ResponseStatusCode | 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. - "OK": Operation succeded.
- "ERR01":
- "ERR02":
- "":
- "":
- "ERR99": Other error. "statusText" should describe the error.
Status codes must be documented by the service implementation. | | statusText : ResponseStatusText | A textual description of ResponseStatusCode. |
|
| | CorrelationId | 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. | | SourceOrganization | 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. | SourceTimestamp | UTC timestamp for when the source was updated. If unknown, use current (UTC) time. |
|
