Business Jet Departures and Flight Hours Can Move in Opposite Directions, BizJet Journal Analysis Explains
Why It MattersActivity reports built on different units, populations or periods can point in opposite directions, so business aviation growth figures only compare once the unit, scope and denominator are fixed.
An analysis by BizJet Journal explains why one report can show more business jet departures while another shows fewer flight hours, without either being wrong. More aircraft may be flying shorter sectors, or the reports may measure different aircraft, places or periods. The analysis stresses defining the unit before reading any growth rate: a departure is a takeoff event and an arrival is a landing event, while flight hours need a further definition of when the clock starts and stops. The WINGX data glossary, for example, defines hours as wheels-up to wheels-down duration and movements as arrivals plus departures, making its hours an airborne measure rather than block time or billed charter hours.

For the same population of completed flights, total airborne hours equal departures multiplied by average airborne duration. In the article's worked example, Period A has 1,000 departures and 2,000 airborne hours, an average of 2.0 hours, while Period B has 1,100 departures and 1,980 hours, an average of 1.8 hours. Departures rise 10%, hours fall 1% and average duration falls 10%, because 1.10 times 0.90 equals 0.99, so simply adding the percentage changes would wrongly suggest no change. Departures describe how often aircraft operate but cannot be converted directly into passengers, occupancy or charter revenue, and airborne hours do not replace cycles, calendar intervals or serial-specific maintenance status.
The analysis also advises keeping the data population and denominator fixed, recording geography, aircraft inclusion, operator filters, date range, time zone and retrieval date. It notes that the FAA's TFMSC documentation says the system captures IFR flights recorded by its enroute computers, with most VFR and some non-enroute IFR traffic excluded, and that WINGX's methodology describes multiple sources, UTC timestamps and a typical 24–48-hour reporting lag.

















































