HeliFlightData

Airport Data Dictionary ElementDescription
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).
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.

OperatingAirlineICAO
Use the ICAO code for the helicopter operator if that is available.

The ICAO code of the airline operating the flight.  See AirlineICAO for definition of term.
OperatingAirlineCodeSome code, typically neither IATA nor ICAO, for the operating airline. System specific content.
OperatingAirlineNameThe name of the operating airline.
FlightRouteOperator
The party operating the flight route. This will often be a company that has hired the airline to operate a given route.
HelicopterTypeA code indicating which type of helicopter this is. Not standardized.
HelicopterTypeDescriptionDescriptive text for HelicopterType
AircraftICAOType
3-4 character code as designated by International Civil Aviation Organisation (ICAO) to uniquely designate Aircraft Type. Local (non-ICAO) codes can be added as required as long as they are unique for aircraft types within the defined context.
Reference Document: ICAO document 8643.
AircraftConfigVersion
Detailed information about the aircraft configuration, received in the aircraft_conf_version field in the ASM and SSM IATA messages.
AircraftTailNumber
Tail number painted on the tail used by some carriers as an aircraft identifier. Often the last 3 characters of AircraftRegistration.
HelicopterFlightStatusA code indicating the status of the whole helicopter flight, from departure to final arrival if this was a multi hop flight. Not strictly standardized.
FlightLegStatusThe status of a "FlightLeg". The following values are defined: "SCH", "FPL", "FLS", "ACT", "CAN", "LAN", "RER", "DIV", "DEL", "UNK"
FlightIsCancelledSet to true if the flight operation is cancelled. For flight as with code share it's possible to only cancel the code shared flight.
FlightServiceTypeIATA
IATA SSIM Appendix C Service Types.
FlightServiceTypeExtended
Installation/customer specific set of flight service types. Typically used when the defined set in FlightServiceType isn't specific enough. Encoded as integer to clearly separate it from FlightServiceType.


First departureThe following elements are for the first departure (if multi hop)
DepartureAirportIATA

Either the departure airport or the arrival airport must be a "proper" IATA airport.


Departure airport IATA code (see AirportIATA for description of term).

DepartureHeliportNameName of the departure heliport.
DepartureHeliportTypeType of the departure heliport. Not strictly defined.
SOBTScheduled Off-Block Time. The time that an aircraft is scheduled to depart from its parking position. Always UTC time.
EOBTEstimated Off-Block Time. The estimated time at which the aircraft will start movement associated with departure. Always UTC time.
TOBTTarget Off-Block Time. The time that an Aircraft Operator or Ground Handler estimates that an aircraft will be ready, all doors closed, boarding bridge removed, push back vehicle available and ready to start up / push back immediately upon reception of clearance from the TWR. Always UTC time.
AOBTActual Off-Block Time. Time the aircraft pushes back / vacates the parking position. (Equivalent to Airline / Handlers ATD – Actual Time of Departure & ACARS=OUT). Always UTC time.
ETOTEstimated Take Off Time. The estimated take off time taking into account the EOBT plus EXOT. Always UTC time.
ATOTActual Take Off Time. The time that an aircraft takes off from the runway. (Equivalent to ATC ATD–Actual Time of Departure, ACARS = OFF). Always UTC time.
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.

GateUniquely defines one gate at the airport.
MailWeightLoadedWeight in Kilos of mail loaded onto the aircraft.
CargoWeightLoadedWeight in Kilos of cargo (freight) loaded onto the aircraft at the current airport.
PaxBoardingThe number of "seated passengers" boarding the aircraft, infants excluded.
PaxBoarding = PaxAdultBoarding + PaxChildBoarding 


Last arrivalThe following elements are for the last arrival (if multi hop)
ArrivalAirportIATA

Either the departure airport or the arrival airport must be a "proper" IATA airport.


Arrival airport IATA code (see AirportIATA for description of term).
ArrivalHeliportNameName of the arrival heliport.
ArrivalHeliportTypeType of the arrival heliport. Not strictly defined.
SIBTScheduled In-Block Time. The time that an aircraft is scheduled to arrive at its first parking position. Always UTC time.
EIBTEstimated In-Block Time. The estimated time that an aircraft will arrive in-blocks. (Equivalent to Airline/Handler ETA –Estimated Time of Arrival). Always UTC time.
AIBTActual In-Block Time. The time that an aircraft arrives in-blocks. (Equivalent to Airline/Handler ATA –Actual Time of Arrival, ACARS = IN). Always UTC time.
ELDTEstimated Landing Time. The estimated time that an aircraft will touchdown on the runway. (Equivalent to ATC ETA–Estimated Time of Arrival = landing). Always UTC time.
ALDTActual Landing Time. The time that an aircraft lands on a runway. (Equivalent to ATC ATA –Actual Time of Arrival = landing, ACARS=ON). Always UTC time.
MailWeightUnloadedWeight in Kilos of mail unloaded off the aircraft.
CargoWeightUnloadedWeight in Kilos of cargo (freight) unloaded off the aircraft at the current airport.
PaxDisembarkingThe number of passengers and passive crew disembarking the plane, infants excluded.
PaxDisembarking = PaxAdultDisembarking + PaxChildDisembarking


ViasIf multi hop the structure below describe the via helipads
FlightRouteIATA

FlightRouteIATA should contain at least 2 entries, the first departure and the last arrival, for a helicopter flight without any additional hops.


List of airports a multi leg flight will land on before arriving at the destination. The list consists of AirportIATA codes. The list should contain all airports including first departure airport and last destination airport. The list should be ordered by the actual sequence the aircraft uses the airports.

ResponseStatus


 

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.

For the operations defined her the following values can be used:

  • "OK": Operation succeded.
  • "ERR01":
  • "ERR02":
  • "":
  • "":
  • "ERR99": Other error. "statusText" should describe the error

 

 

The possible values must be decided and documented as coding progresses.

ResponseStatusText
A textual description of ResponseStatusCode.

TransData


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.

  • No labels