Aircraft Utilisation – Daily (ADS-B based)

ColumnData TypeData descriptionKeyData SetJoin On
Natural IDvarchar(30)Natural aircraft ID (combination of the ch-aviation production line code and either the line/construction or manufacturer serial number, changes for aircraft not yet delivered where l/n, c/n or msn are not yet known (assigned by ch-aviation)ForeignAircraftNatural ID
Aircraft IDint(11)Unique ch-aviation created aircraft ID, remains stable throughout an aircraft’s life (assigned by ch-aviation)ForeignAircraftAircraft ID
Operatorvarchar(255)Operator name
Opr. ch-a Codevarchar(5)Operator ch-aviation code (assigned by ch-aviation). Operator ch-aviation codes can be 2, 3, or 5 characters.ForeignOperatorsOperator ch-a Code
Variantvarchar(255)Aircraft Variant designation (i.e. A321-200N)
CNvarchar(16)Construction/Line Number
MSNvarchar(16)Manufacturer Serial Number
Registrationvarchar(16)Aircraft Registration, blank if unknown or no longer registered
Datedatedate (YYYY-MM-DD)
cyclesint(8)number of daily cycles
hoursdecimal(23,2)number of daily hours (hhh.hh)
avg stage lengthchar(5)average daily stage length in hours and minutes (hh:mm)
utilisation_data_typevarchar(255)type of utilisation data
As ofdateAs of date (date when utilisation data was last provided) (YYYY-MM-DD)
Sourcevarchar(255)Source of utilisation data
data quality indicatorvarchar(16)An aircraft is whitelisted for an operator/MSN combination if it meets one of the following: Utilization Match: Spire ADS-B based cycles closely align with OEM data (within ±1–2 cycles or ±10%, depending on sample size) in the past two years. Flight Path Continuity: At least 95% of previous destinations match the next origin, with 10+ flights tracked in the past two years. Otherwise, it is blacklisted
data quality indexdecimal(3,2)A score from 0 to 1 indicating completeness of flight tracking for the day: 0 = takeoff and/or landing missing; 1 = both takeoff and landing are present; values in between reflect partial data completeness.