What problem does it solve?
An airline's plan for the day links every aircraft, crew and passenger connection. When a storm closes a hub, an aircraft goes technical or a crew runs out of legal duty time, one change ripples through the network: the next flight has no aircraft, the crew is in the wrong city, passengers miss connections and hotels fill up. Operations controllers have minutes to decide what to delay, swap or cancel.
Traditionally they do it by experience, looking across separate systems for aircraft rotation, crew, passengers and maintenance that were never built to optimize together. Decisions that are good for one dimension, such as protecting the schedule, can be expensive in another, such as passenger compensation, crew overtime or noise charges. Passenger facing rebooking can soften the damage, but the cost is set earlier, by the recovery plan the control center chooses.
How does it work?
- Build one picture of the operation. Aircraft rotations, crew pairings and legality, passenger bookings and connections, maintenance status, airport and air traffic control constraints and weather are replicated into one near real time data layer.
- Predict trouble early. Models forecast delays, missed connections and the effect of forecast weather at hubs, hours ahead.
- Generate recovery options. Optimization searches for plans that retime, swap or cancel flights and reassign crew, scoring each on cost, passenger impact, crew legality and knock on effects.
- Explain and propose. The controller sees the recommended plan and its alternatives with the trade offs in plain terms, including costs such as fuel, charges and passenger care.
- Decide and execute. Controllers accept, change or reject the plan; accepted changes flow to the rotation, crew and passenger systems, which trigger rebooking and notifications.
- Learn. Outcomes of each event feed back into the models and cost functions.
- Audience
- Employee facing
- Autonomy
- Copilot
- Adoption
- Early adopters
- Channels
- Internal tools
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
| KPI | Median | Reported range | Data points | Claimed by |
|---|---|---|---|---|
| Cost savings | Not pooled | at least CHF 1 million | 1 | 1 organization |
Value drivers: Lower cost to serve, Customer experience, Speed and cycle time, Employee productivity.
Indicative value
An airline operating 200,000 flights a year
USD 800,000 to USD 6 million
Disruption cost avoided per year
How this is calculated
Formula: flights * disruptedShare * costPerDisruption * costReduction. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| Flights per year flights, flights per year | 200,000 | 200,000 | The reference airline. |
| Share of flights that need a recovery decision disruptedShare, fraction of flights | 0.05 | 0.1 | Editorial assumption for a network airline, replace with your own irregular operations data. |
| Direct cost per disrupted flight costPerDisruption, USD per disrupted flight | 4,000 | 10,000 | Editorial assumption covering crew, passenger care and compensation, repositioning and charges. Replace with your own cost model. |
| Reduction in disruption cost from better recovery plans costReduction, fraction of disruption cost | 0.02 | 0.03 | Editorial assumption, replace with your own. Neither deployment on this page reports savings from disruption recovery alone. SWISS reports more than CHF 1 million saved in the first 14 weeks of its rotation optimization feature, from lower fuel use and avoided charges such as airport noise charges, so that figure does not set this range. |
What it leaves out: Counts only direct disruption cost. It leaves out savings from optimizing rotations on normal days, the revenue effect of fewer cancellations and missed connections, the cost of the data platform and optimization software, and the change in the control center's way of working.
Who already uses it?
3 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
British Airways
United Kingdom · Travel and hospitality · 2025
British Airways says a 100 million pound investment in operational resilience has funded a range of AI tools that helped it reach a punctuality record at Heathrow: 86% of its flights left on time in the first quarter of 2025, its previous best being 46% in 2008. One system allocates arriving aircraft to stands based on a live analysis of passengers' onward travel plans, reducing missed connections, which the airline estimates has saved 160,000 minutes of delay.
Another system proactively reroutes aircraft around poor weather, which it estimates has prevented 243,000 minutes of delay. Chief executive Sean Doyle told an innovation summit that the tools give staff the information to make rapid decisions and get flights away on time, and said the airline will start using additional AI tools over the coming months. The same investment also funded new apps for pilots, cabin crew and aircraft dispatch teams.
No outcome disclosed.
American Airlines
United States · Travel and hospitality · 2022
American Airlines built the Hub Efficiency Analytics Tool (HEAT) in house and has used it at its hubs since spring 2022. When severe weather is forecast, it weighs weather, load factors, customer connections, gate availability, air traffic control and crew constraints and shifts the departure and arrival times of flights at the hub, which operations center coordinators decide whether to apply. In a newsroom article from 2023, American says that since its initial deployment the year before, HEAT has prevented nearly 1,000 flight cancellations across its network. The same program includes intelligent gating at Dallas Fort Worth, which assigns the nearest available gate to arriving aircraft automatically.
No outcome disclosed.
Swiss International Air Lines
Switzerland · Travel and hospitality · 2022
SWISS, part of Lufthansa Group, developed the Operations Decision Support Suite (OPSD) with Google Cloud as a layer above its operational systems. It replicates the state of the operation minute by minute with crew, passenger, rotation and technical data in one place, and uses optimization and machine learning to propose scenarios, such as swapping aircraft between flights or managing missed connections, that operations controllers approve before they take effect. The first use cases were rotation planning and passenger management. Lufthansa Group says OPSD lays the foundation for optimizing across the different operational dimensions, and eventually across airline borders, with the goal of rolling it out to other Lufthansa Group airlines.
- Cost savings: at least CHF 1 million, first three and a half months of the rotation optimization feature
"In three and a half months, this has generated more than a million Swiss Francs in savings."
Claimed by: organization
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Near real time aircraft rotation, crew pairing and passenger connection data
- Crew legality rules (duty and rest limits) and qualifications in machine readable form
- Agreed cost functions for delay, cancellation, passenger care, compensation and charges
- Historical disruption events with the decisions taken and their outcomes
Systems to integrate
- Operations control and aircraft rotation system
- Crew management and tracking system
- Passenger service and reservation system
- Maintenance and technical fleet systems
- Weather, air traffic flow and airport data feeds
Complexity: High
The optimization is hard but available from specialist vendors and cloud providers. The larger effort is the data layer that joins rotation, crew, passenger and maintenance systems in near real time, cost functions the airline agrees on, and trust from controllers who are accountable for safe and legal operation.
- 1
Start with one decision and one metric
Pick a frequent, contained decision such as aircraft swaps within a fleet or retiming at a hub before forecast weather, and agree how success is measured before building.
- 2
Build the shared data layer
Replicate rotation, crew, passenger and maintenance data into one near real time view. This alone helps controllers, and every later optimization depends on it.
- 3
Agree the cost functions
Put a price on delay minutes, missed connections, cancellations, crew overtime and charges, signed off by operations, finance and customer teams, so the optimizer and the controllers weigh options the same way.
- 4
Recommend, do not execute
Show proposals with their trade offs and let controllers accept or reject them. Track the acceptance rate and the reasons for rejection as the main signal of fit.
- 5
Connect to passenger recovery
Feed accepted plans straight into rebooking and customer notifications, so the passenger side starts as soon as the operational decision is taken.
- 6
Extend to crew and network recovery
Add crew reassignment and multi hub recovery once the first use case is trusted, with crew legality checked by rules the optimizer cannot relax.
Guardrails
- Crew duty and rest limits, qualifications and maintenance status are hard constraints the model cannot override
- Controllers approve every plan before it changes the operation
- Every proposal shows its cost assumptions and the alternatives considered
- A manual fallback process is rehearsed for when the tool or its data feeds fail
- Cost functions and model changes go through change control with operations sign off
KPIs to instrument
- Acceptance rate of proposals and reasons for rejection
- Cancellations, delay minutes and missed connections per disruption event, against comparable events
- Direct disruption cost per event (crew, passenger care, compensation, charges)
- Time from disruption detection to an approved recovery plan
- Controller workload and satisfaction with the tool
Human in the loop
Operations controllers and duty managers remain responsible for every decision. They approve, change or reject each proposal, and coordinators decide whether a tool such as a weather retiming plan is used at all for a given event. Crew schedulers confirm reassignments, and a review after each major disruption checks the tool's proposals against what happened.
Common failure modes
- Optimizing on stale data
- A plan built on an out of date crew or aircraft position is worse than none. Monitor data freshness and block proposals when feeds lag.
- Plans the controllers do not trust
- If proposals ignore constraints controllers know about, acceptance collapses. Capture rejection reasons and turn them into constraints.
- Cheapest plan, worst experience
- Cost functions that underprice passenger impact produce plans that save money and lose customers. Review the weights with customer teams.
- No fallback when the system fails
- A recovery tool that fails during the peak of a meltdown leaves controllers without their usual process. Keep and rehearse the manual process.
What are the risks and rules?
EU AI Act
Depends on design
Recommending schedule, aircraft and passenger recovery plans to controllers is not listed in Annex III. Annex III point 4(b) covers AI used to make decisions affecting terms of work relationships, to allocate tasks based on individual behavior or personal traits or characteristics, or to monitor and evaluate the performance and behavior of workers.
A design that reassigns individual crew members on such grounds, or that scores controllers or crew on their performance, falls in that category; one that works on flights, aircraft and crew legality and qualifications alone is less likely to, although assigning duties by qualification can still touch terms of work.
The tool is not itself a safety component of an aircraft or other product regulated under Regulation (EU) 2018/1139, which Annex I Section B lists, so that route to high risk does not normally apply. Decisions that affect flight safety stay under aviation safety regulation and the airline's approved procedures; keep crew legality and maintenance limits as hard rules outside the model.
Guidance
- EASA Artificial Intelligence Roadmap 2.0: A human-centric approach to AI in aviation (European Union Aviation Safety Agency, Europe). Outlines EASA's vision for the safety and ethical considerations of AI in aviation.
Controls to put in place
- Documented cost functions and hard constraints with an accountable owner in operations
- Audit log of every proposal, the data behind it and the controller's decision
- Post event reviews of major disruptions comparing proposals with outcomes
- Tested manual fallback and data feed monitoring
Frequently asked questions
- How is this different from an AI rebooking agent?
A rebooking agent helps passengers after the airline has decided what to do. Operations control decision support shapes that decision: which flights to delay, swap or cancel and how to recover aircraft and crew. The two work best connected, so an approved plan triggers rebooking and notifications straight away.
- What results have airlines reported?
SWISS says the rotation optimization in its Operations Decision Support Suite saved more than CHF 1 million in its first three and a half months, and that controllers accept about nine in ten optimization runs. In 2023, American Airlines said its HEAT tool had prevented nearly 1,000 flight cancellations since its first use in April 2022; that is American's own figure, published without a baseline.
- Does the AI make the decisions?
No. At SWISS, operations controllers approve every change before it takes effect. At American, coordinators work with air traffic control and meteorologists to decide whether HEAT is used for a given storm, and Cranky Flier reports that HEAT starts from crew rest and availability. Beyond what these deployments disclose, a sound design keeps crew legality and maintenance limits as hard rules outside the model, because controllers remain accountable for safe and legal operation.
How to cite this page
Blits.ai AI Use Case Library, "AI decision support for airline operations control and disruption recovery", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/airline-operations-control-decision-support. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 29 September 2026: Added deployments: British Airways.
- 27 September 2026: First published