Case study

Kronos Flight-Times Feed (FlightView API Decommission)

Apr 2025 – Dec 2025·Product owner

Replaced a paid third-party flight-times API with an in-house Kronos feed for estimated and actual times when ACARS is unavailable; delivered under budget and ahead of schedule.

Challenge

Estimated and actual flight times fell back to a third-party API whenever ACARS was unavailable, at a recurring annual cost. The replacement had to match the data quality and then carry forward into the new flight-ops platform.

Approach

  • Shipped the FlightView decommission and Kronos implementation in April 2025.
  • Carried the feed into the CAE Movement Manager program: flight-message integration with five-minute ETA collection, a five-minute delta threshold, and immediate OFF/ON events; QA'd and demoed in December 2025.
  • Produced the system diagrams for the CAE, charter platform, and Kronos data flows; later added logic to preserve ACARS times when Kronos or FAA data arrives.

Outcome

  • Recurring third-party API cost removed; delivered under budget and ahead of schedule.
  • Feed re-targeted to the new system of record without a gap.

Systems involved

  • Kronos / UKG
  • CAE Movement Manager
  • ACARS
  • MuleSoft

Milestones

  1. Apr 2025Third-party flight-times API decommissioned