Why do some results of my reports using FLIGHTS_OTP table in Sky Warehouse seem different?

Based on customer feedback, we’ve recently improved our calculation logic for flights_otp view. Users may notice a change as a small number of flights have been affected by this update.

For example, taking column d0, our previous logic for flights_otp view in the Cirium Sky Data Warehouse showed 0 (zero) in some cases because it was assuming a null (missing) value for (flight) is_cancelled or is_diverted equal true, and then not all d0 conditions in the logic were fulfilled therefore to display 1. A value of 0 (zero) in column d0 could be interpreted as a flight being delayed, yet when comparing against the flight data that wasn’t necessarily the case.

This change was implemented at the beginning of August 2024.