SystemFlight Operations & Dispatch

Airline Disruption Management

Airline disruption management that brings the OCC three rehearsed, costed recovery plans before the ground stop

See one case, screen by screen ↓
Watch with transcript →

Built forDuty managersFlight dispatchersCrew controllersMaintenance controllersCustomer recovery managers

The Problem Today

When a storm hits a hub, recovery is pieced together on a bridge call, and crew and aircraft limits surface too late.

$80M
lost to disruption in a year by a 100-aircraft airline, at most our estimate
$75,000
maximum civil penalty per violation past the tarmac limit published

Checked team by team, by hand

  • Crew duty
  • Aircraft
  • Curfews
  • Connections
  • Millions on one bad eveningRefunds, hotels, crew overtime and rebooking
  • Reasons lost by morningThe review is rebuilt from logs and chats days later

The Solution

  1. A ground stop seen earlyFlagged with its confidence and the weather and FAA advisories behind it
  2. Each candidate plan rehearsedTested against crew limits, open MEL items, curfews and connections
  3. Only passing plans shownEach comes with a cost receipt whose lines cite their source
  4. The duty manager signsEdits a flight in plain words, sees it re-solved, then signs

Built-in controls

  • Nothing reaches stations or crews unsigned
  • Each cost line cites its contract, fare or rule
  • Each edit and acknowledgment on a sealed trail

What You Get

The OCC recovers a storm evening for less, with a plan that keeps most connections.

  • Tarmac and refund clocks in viewEach flight's tarmac, refund and curfew clock, warned early
  • Each team told once signedStations, dispatch, crews and passengers, each reply tracked
  • After-action review draftedBuilt from the signed plan and the live outcome
In short

What is Airline Disruption Management?

Airline disruption management is how an airline's operations control center recovers the schedule when weather, a ground stop or a failed system breaks it: which flights to delay, cancel, swap or consolidate, and how to look after crews and passengers. Airline Disruption Management gives the OCC eight agents that build recovery plans, rehearse each one against crew limits, MEL items, curfews, connections and the DOT rules, and price it line by line, while the duty manager edits, asks why and signs.

How to choose AI for airlines: a buyer's guide to agentic AI solutions →

Updated

The problem

Airline disruption management still runs on a bridge call, check by check

When a thunderstorm line, a ground stop or a failed system hits a hub, airline disruption management comes down to minutes. The airline operations control center must decide which flights to delay, cancel, swap or consolidate. The duty manager pulls that answer together over a disruption bridge with dispatch, crew control, maintenance control, customer recovery and the hub station, each looking at a different system. A check that fails sends the plan back for another round: the solver does not know the crew or the passengers, and crew control does not see the cost.

In irregular operations recovery, the expensive mistakes are the ones found late. A plan is chosen and then a crew times out under Part 117. A swap lands on a tail whose MEL item limits it to ETOPS 120 on a route that needs ETOPS 180. Connections are noticed when passengers reach the counter, a tarmac clock is noticed near three hours, a refund owed under the DOT automatic refund rule is missed, and by the next morning nobody can say why the decision was made.

estimated$80Ma year, at most, that an airline of about 100 aircraft can lose to disruption
typical$75,000maximum civil penalty per violation; past the tarmac limit, each passenger can count
Where a storm evening's staff days goestimated
By hand6.5 days
With the solution1.6 days
  • Building options and running bridge rounds1 → 0.2 d
  • Checking crews, tails, curfews and connections1.5 → 0.3 d
  • Telling stations, crews, dispatch and passengers1 → 0.3 d
  • Tarmac, refund and compensation follow-up1 → 0.5 d
  • Rebuilding the day for the after-action review2 → 0.3 d

Estimated staff days across the OCC and customer teams for one hub storm evening and its follow-up, by hand and with the solution.

How it works

IROPS recovery, from the first ground stop warning to the release

What comes in
Signals in9 feeds · weather, FAA flow programs, crew, maintenance, bookings
Agents at work
Watch agentpredicts the ground stop
Then
Recovery agentbuilds many plans
Then
Crew legality agentPart 117
Aircraft and MEL agentMEL, ETOPS, curfews
Connections agentconnections at risk
Obligations agenttarmac, refunds, receipt
Then
Release agentafter signature only
Review agentplan vs outcome
A person decides
Duty Manageredits, asks why, signs with a reason code
What comes out
Signed plan with its receipt
Stations, crews, dispatch, ATC told
After-action review
One case, step by step

Disruption management on one storm evening at the Denver hub

A weekday evening at the airline's Denver hub, 16:22 local time. A line of thunderstorms is coming, and 188 flights, 28,289 passengers and 2,540 connections are at risk in the 16:00, 17:30 and 19:00 banks. Here is what happens next, screen by screen, in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 0116:21

    The agents speak first: “I have three plans.”

    Duty manager

    The duty manager's Today screen opens on a message from the Recovery agent: “Ground stop likely at 16:40. I have three plans.” Since 15:41 the agents have read 9 feeds, built 11 recovery plans and rehearsed each one. Plan B cancels 14 short flights, swaps a healthy 787 onto the London flight and keeps 2,262 of 2,540 connections for $1.81M. Under “Needs you”: nothing has gone to stations, crews or customers yet, two aircraft are in the departure queue, and one swap waits for maintenance control.

    “One decision needs you before 16:40.”

  2. 02How sure is it?

    An early warning with its confidence and its sources

    Watch agent

    The Watch agent read a convective SIGMET (a line 40 nm wide moving east at 25 kt, tops FL450), the DEN TAF amendment, lightning within 5 nm and an FAA advisory that calls a ground stop probable from 16:40, with a ground delay program likely after. Confidence rose from 0.74 to 0.82. A what-if tries the ground stop at 16:30 or 17:00 to show how sensitive the plans are; it does not change them.

    The Watch agent warns and cites its sources. Declaring an event is left to the OCC.

  3. 03The recovery

    The hub's banks, the storm and three plans, side by side

    Recovery agent

    The Recovery screen draws the DEN day as arrival and departure bank waves from 12:00 to 23:00, with the thunderstorm line from 16:30 to 19:00, the likely ground stop from 16:40 to 18:30 and the ramp closed for lightning from 16:35 to 17:45. Plan A holds and delays for $2.61M with 9 crew time-outs; Plan B thins the 17:30 bank for $1.81M; Plan C cancels early for $2.05M. Each plan is drawn over the real schedule, with its cost receipt below.

    “I built 11 plans and rehearsed each against crew duty limits, MEL items, curfews, connections and the DOT tarmac rule; three passed. I recommend Plan B.”

  4. 04Rehearsal

    Eight plans failed, and the duty manager can see why

    Four checking agents

    The crew legality, aircraft and MEL, connections and obligations agents rehearse each plan without seeing the planner's reasoning. Plan D kept a 787 with an inoperative APU on the London flight, but MEL 49-11-01 limits that tail to ETOPS 120 minutes and the route needs ETOPS 180. Plan G would land a flight at Santa Ana at 23:24, after the 23:00 curfew. Plan H would take a flight to its 3-hour tarmac limit at 19:05. None of the eight is offered as an option.

    “8 plans failed rehearsal. They are not options; they are here so you can see what was tried.”

  5. 05One sentence

    “Keep the Chicago flight, cancel the other one instead”

    Duty manager

    Plan B as proposed cancels a flight to Chicago. The duty manager knows Chicago matters more tonight and types the change: keep it, and cancel a second flight instead. The Recovery agent re-solves Plan B in 8.2 seconds and the four checks run again: still 14 cancellations, connections kept 2,262 → 2,310 (+48), cost $1.81M → $1.84M (+$30,000). The Chicago flight carries 96 connecting passengers, the second flight 48. The duty manager accepts the edit with the reason Customer priority.

    Nothing changes until the duty manager presses “Accept the edit”; “Undo” puts Plan B back as proposed.

  6. 0616:27

    Why the second flight cannot wait, answered with the rule

    Crew legality agent

    Its captain and first officer reported at 07:05 and this is their fourth segment, so Part 117 Table B allows 13 hours and their duty ends at 20:05. The earliest slot is 19:10, block-in 21:15, a 1 h 10 min extension. The captain took a 52-minute extension earlier in the week with no 30-hour rest since, so a second one over 30 minutes is not allowed, and no reserve A321neo captain is at DEN before 21:40.

    “Canceling and rebooking its 142 passengers costs $41,000 less than a reserve-crew delay after 22:00.”

  7. 07The London swap

    A healthy 787 for London, confirmed by maintenance control

    Aircraft and MEL agent

    One 787's APU has been inoperative since 21:12 the night before, a category C item under MEL 49-11-01, which limits it to ETOPS 120 minutes. A second 787 came in from SFO at 16:05 with no open items and takes the London flight at 20:05; the first flies a domestic flight to Houston, where ground power and air are confirmed. The maintenance controller confirmed both swaps at 16:20.

    The Aircraft and MEL agent does not clear an MEL item or confirm a swap; maintenance control does.

  8. 08The clocks

    Tarmac, refund and curfew clocks in view

    Obligations agent

    Two flights closed their doors at 16:05 and 16:12, so their 3-hour domestic tarmac limits fall at 19:05 and 19:12. Plan B returns both to the gate by 17:12. The obligations agent warns at 2 h 15 min, starts returns by 2 h 30 min, and keeps the refund queue under the DOT automatic refund rule. In Plan A, four flights would have come within 30 minutes of the limit.

    The obligations agent cannot waive an obligation or send a refund.

  9. 0916:31 · signed

    Signed with a reason code; only then does anything move

    Duty manager

    The signing screen restates the plan (14 cancellations, 22 delays, 4 swaps, 2,310 of 2,540 connections kept, $1.84M, all five checks passed) and what will be sent. The plan is under the co-sign limits of 25 cancellations and $3M, so the duty manager's signature is enough. The duty manager picks the reason Protects connections and customers and signs at 16:31.

    “When you sign, the release agent sends the plan to 8 stations, dispatch, ATC, 31 crew members and 5,072 passengers, and tracks each acknowledgment.”

  10. 10The release

    Stations, dispatch, crews and passengers told, each reply tracked

    Release agent

    Cancellation and gate notices go to 8 stations, 22 amended releases to dispatch for the dispatcher to sign, 9 slot substitutions from the canceled DEN arrivals, new reports and hotels for 31 crew members, messages to 1,964 passengers on canceled flights and 3,108 on delayed ones, and 410 rooms at six contracted DEN hotels. Each has a time limit and an owner; OMA station is flagged as overdue at 7 of 8.

    The release agent sends nothing before signature, and the dispatcher signs each amended release.

Who it’s for

The disruption bridge, seen from five operations control seats

The same storm evening for the duty manager, dispatch, maintenance control, customer recovery and the VP: by hand, then with the solution.

Duty manager
Signs each recovery plan
Before
Runs the disruption bridge and assembles a plan from dispatch, crew control, maintenance control and customer teams, round after round.
Now
Opens three rehearsed plans with cost receipts, edits a flight in plain words, asks why, and signs with a reason code.
Flight dispatcher
Signs the amended releases
Before
Hears about moved flights late, then amends releases, fuel and alternates one by one.
Now
Gets the 22 amended releases drafted with new times, fuel and alternates the moment the plan is signed, and signs them.
Maintenance controller
Confirms each aircraft swap
Before
Finds out a swap broke an MEL restriction after the plan is already chosen.
Now
Sees each tail's open MEL items, ETOPS capability and station support checked before a plan is shown, and confirms the swap.
Customer recovery manager
Rebooking, hotels and refunds
Before
Learns about missed connections when passengers reach the counter, and chases refund clocks afterwards.
Now
Sees each passenger group re-accommodated by priority, unaccompanied minors and wheelchair passengers first, with hotel rooms and messages ready to go at signature.
VP, operations control
Co-signs above 25 cancellations or $3M
Before
Waits days for someone to rebuild the evening from logs and chats for the after-action review.
Now
Reads a review built from the signed plan and the live outcome, and decides which proposed lessons become rules.
The agents

Watch, recovery and checking agents for airline disruption management

Recovery plans are watched for, built, rehearsed and priced by eight agents that check each other; the Duty Manager edits, asks why and signs.

Watch agent

Reads aviation weather, FAA flow programs and advisories, lightning and systems status each minute, and warns of ground stops, ground delay programs and ramp closures with a confidence and its sources.

  • Never declares an event; it warns and cites
  • Read-only on each feed
Recovery agent

Builds up to 12 candidate plans for schedule and crew recovery (delays, cancellations, swaps, consolidations, ferries), sends each to the four checking agents, shows the best three that pass by the airline's weights, and re-solves around a person's edits.

  • Never shows a plan that has not been rehearsed
  • Never changes the schedule
Crew legality agent

Checks each crew member a plan touches against Part 117 Table B, the 117.19 extension rules, rest and the crew agreement, flags any duty within 30 minutes of its limit and finds qualified reserves.

  • Never assigns a crew; the crew controller does
  • Never assumes a captain's agreement to an extension
Aircraft and MEL agent

Checks each tail in a plan: open MEL items and their operational restrictions, ETOPS capability for the route, checks due, curfews and what each station can support.

  • Never clears an MEL item
  • Never confirms a swap; maintenance control does
Connections agent

Scores each connection under each plan, re-accommodates passengers by priority (children traveling alone, passengers needing assistance, last flights of the day, then everyone else) and drafts the customer messages.

  • Never rebooks a passenger before the plan is signed
  • Never moves a passenger who chose to stay
Obligations agent

Watches the tarmac, refund and curfew clocks a disruption starts, and prices each plan's cost receipt line by line from hotel, crew and partner contracts, fares and the rules.

  • Never waives an obligation
  • Never sends a refund
Release agent

After signature, sends the plan to stations, dispatch, ATC, crews, customers and hotels, tracks each acknowledgment against its time limit and escalates silence.

  • Never sends before signature
  • The dispatcher signs each amended release
Review agent

Writes the after-action review from the signed plan, the outcome and the conversation: plan against outcome and the decisions on the record. It proposes lessons.

  • Never edits the record
  • Lessons are proposed; a person approves
Duty Manager

Signs every plan; maintenance control confirms swaps; the dispatcher signs amended releases.

Ask in plain words

Plain-word questions about the storm, a flight, a crew or a passenger

Ask in plain words, or say what to change. Each answer cites the roster, MEL record, contract or rule it came from, and opens the screen it is about. These answers use the sample data.

Could the flight we cancel instead wait out the storm with a delay?

Not with its crew. The captain reported at 07:05 and this is the fourth segment; Table B ends the duty at 20:05. Any slot after the bank (19:10 is the earliest) needs a second extension over 30 minutes this week, which 117.19(a)(2) forbids, and no reserve captain is at DEN before 21:40. So the flight either goes at 17:50 or is canceled.

What does Plan B cost, line by line?

Plan B as proposed: $1.81M. Refunds and lost revenue $0.90M, hotels and meals $0.30M, crew $0.18M, partner rebooking $0.21M, goodwill $0.14M and aircraft $0.08M. Plan A is $2.61M.

Which flights are close to the 3-hour tarmac limit?

None yet. Two flights closed their doors at 16:05 and 16:12, so their limits are 19:05 and 19:12; the plan returns both to the gate by 17:12. Each passenger kept too long can cost up to $75,000.

Who has not acknowledged yet?

OMA station has not acknowledged after 10 minutes. The release agent paged the station manager again and escalates to the duty manager at 15 minutes.

The screens

The OCC's disruption management screens, from Today to the review

From the working solution, on its sample data. Pick one to see it large.

TodayThe duty manager's start screen: the Recovery agent's three plans, the ground stop at 16:40, flights and passengers at risk, and what needs a decision.
Early warningThe ground stop warning with its confidence, the SIGMET, FAA advisory and lightning it came from, and a what-if on the ground-stop time.
IROPS recovery on the hubOperations control recovery on the hub: the arrival and departure banks with the storm, ground stop and ramp closure, three recovery plans in the conversation and Plan B's cost receipt.
Plans that failed rehearsalEight plans the checks rejected for MEL and ETOPS, crew duty limits, curfews, the tarmac limit or connections, each with why.
An edit, re-solvedKeeping the Chicago flight and canceling another, re-solved and rehearsed again, with the change to connections and cost before the edit is accepted.
Asking whyWhy one flight cannot be delayed: the crew's Part 117 duty clock, the extension rule and the reserves, each cited.
Aircraft and MELThe tails a plan touches, with one 787's open APU item, the ETOPS check for its new route and the swaps maintenance control confirmed.
Passenger re-accommodationPassenger re-accommodation after the edit: 2,310 of 2,540 connections kept and each passenger group ready to rebook by priority, with 5,072 messages drafted and 410 hotel rooms, sent when the plan is signed.
Tarmac, refund and curfew clocksEach tarmac clock against its 3-hour limit, with the return to gate each flight gets in the plan.
Sign the planThe plan restated, the reason code, the e-signature, and whether the plan is under the VP's co-sign limits.
The releaseThe signed plan going to stations, dispatch, ATC slot substitutions, crews, passengers and hotels, each with its time limit, owner and acknowledgments.
After-action reviewThe after-action review of the signed plan: plan against outcome as the evening goes, the decisions on the record and the lessons the review agent proposes.
Recovery rulesPlan weights, ground-stop and tarmac warnings, return-to-gate and refund thresholds, minimum connections, crew duty warning, co-sign limits and curfews.
Governance

Rehearsal, signatures and a sealed trail in airline disruption management

Only rehearsed plans are shownFour checking agents rehearse each plan against crew duty limits, MEL and ETOPS, curfews, connections and the tarmac and refund rules, without seeing the planner's reasoning. The plans that failed stay visible with the check that failed them.
A named person signs each planThe duty manager signs with a reason code and an e-signature; above 25 cancellations or $3M the VP Operations Control co-signs, and whoever edits a plan cannot co-sign it.
Nothing moves before the signatureSeats can be held, but tickets reissue and messages go to stations, crews, dispatch, ATC and passengers only once the plan is signed. Maintenance control confirms each swap and the dispatcher signs each amended release.
Each number cites its sourceEach cost receipt line, crew duty clock, MEL restriction and agent statement links to the contract, fare, roster, maintenance record, advisory or rule it came from.
Agents stay inside their limitsNo agent changes the schedule, assigns crews, clears MEL items, rebooks before signature, waives an obligation or sends a refund. Turning an agent off needs the VP Operations Control's approval.
A trail nobody can editEach agent step and decision is recorded in order, each entry chained to the one before it. One export gives the evidence pack for a DOT or FAA question: the trail, the signed plan, the cited sources, tarmac clocks minute by minute and passenger messages.
Configuration

Plan weights, tarmac warnings and curfews the OCC sets for IROPS recovery

The airline's recovery rules, approved by the VP Operations Control, set how airline recovery optimization weighs cost, connections kept and tomorrow's schedule. A change needs a reason code and is rehearsed on the last six disruption days before it applies.

SettingDefaultChoose from
Plan weightsCost 40 · connections kept 40 · tomorrow's schedule 20Your own weights, changed by the VP Operations Control
Plans built / shownUp to 12 built · 3 shownHow many candidates to build and how many rehearsed plans to show
Ground-stop warningConfidence 0.60 or moreThe confidence at which the Watch agent warns
Tarmac warning2 h 15 min domestic · 3 h 15 min internationalWhen the clock alerts the Duty Manager, station and captain
Return to gate starts by2 h 30 min domestic · 3 h 30 min internationalSet inside the 3- and 4-hour limits of 14 CFR 259.4
Significant change (refund)Delay over 3 h domestic, 6 h internationalFollows the DOT automatic refund rule
Minimum connection at DEN40 min domestic · 75 min internationalPer hub
Crew duty warningWithin 30 minutes of the limitYour company buffer on top of Part 117
Co-signature by the VPOver 25 cancellations or $3MYour thresholds
CurfewsSNA 23:00 · SAN 23:30 · FRA 23:00–05:00 · LHR night quotaEvery station's curfew or quota
Connections

FAA flow programs, weather, crew rosters and MEL records behind each plan

FAA flow programs and advisoriesground stops, GDPs, AFPs, EDCTs and slot substitutions
Aviation weather and lightningSIGMETs, TAFs, METARs, radar and strikes near each hub ramp
Crew managementrosters, pairings, duty history and reserves
Maintenance and engineeringMEL items, checks due and aircraft status
Reservations and departure controlbookings, connections, seats and check-in
Station, crew, customer and hotel messagingstation messages, the crew app, passenger app, text and email, contracted hotels
What it changes

What a rehearsed recovery plan saved against hold and delay

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

demo
$0.77M
less than the delay-first plan on the sample storm evening
Hold and delay$2.61M
Rehearsed Plan B$1.84M
target
0
tarmac-limit breaches, the design goal; each passenger past 3 hours can cost up to $75,000
demo
91%
of connections kept on the sample storm evening
2,310 of 2,540
the rest rebooked with a hotel

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the sample DEN storm evening, priced from contract rates and fares; AltexSoft, June 2026, citing an airline IT provider, a vendor figure: an airline of about 100 aircraft can lose up to $80 million a year to disruption) · “typical” = published figures (49 U.S.C. 46301 as amended by the FAA Reauthorization Act of 2024: up to $75,000 per violation; 14 CFR 259.4 tarmac delays, 14 CFR Part 260 refunds, 14 CFR Part 117 crew duty). Names on the screens are sample data.

Questions

IROPS recovery and airline disruption management questions from OCC leaders

What is airline disruption management?

Airline disruption management is how an airline's operations control center recovers the schedule when weather, a ground stop or a failed system breaks it: which flights to delay, cancel, swap or consolidate, and how to look after crews and passengers. Airline Disruption Management gives the OCC eight agents that build recovery plans, rehearse each one against crew limits, MEL items, curfews, connections and the DOT rules, and price it line by line, while the duty manager edits, asks why and signs.

How does it handle IROPS recovery when a ground stop is coming?

The Watch agent reads weather, lightning and FAA advisories and warns with a confidence. On the sample evening it saw a ground stop and a ground delay program coming at DEN: the stop likely from 16:40 at 0.82, the program likely after it. The Recovery agent builds up to 12 plans for the affected banks, the checking agents rehearse them, and the duty manager sees the three best that passed, each with its cost receipt.

How does it keep crews legal under Part 117 during a delay?

The crew legality agent checks each crew member a plan touches against Table B duty limits, the 117.19 extension rules, rest and the crew agreement, and flags any duty within 30 minutes of its limit. A plan that times out a crew fails rehearsal and is not offered. The agent does not assign a crew; the crew controller does.

Does it check MEL items and ETOPS before a tail swap?

Yes. The aircraft and MEL agent reads each tail's open MEL items and their restrictions, ETOPS capability, checks due, curfews and station support. On the sample evening it caught that MEL 49-11-01 limited one 787 to ETOPS 120 on a London route that needs ETOPS 180. Maintenance control confirms each swap.

How does it help with the DOT tarmac delay rule and automatic refunds?

The obligations agent runs each tarmac clock from door close or touchdown, warns at 2 h 15 min and starts returns to the gate by 2 h 30 min, inside the 3-hour domestic limit of 14 CFR 259.4. It keeps the queue of DOT automatic refunds under 14 CFR Part 260, where a delay over 3 hours domestic or 6 hours international is a significant change, and prices refunds into each plan's receipt. It does not waive an obligation or send a refund itself.

Can the duty manager change a plan or ask why a flight was chosen?

Yes, in plain words. On the sample evening, keeping the Chicago flight and canceling a second flight instead was re-solved in 8.2 seconds and rehearsed again, showing +48 connections and +$30,000 before the edit was accepted. “Why not delay it?” was answered with the crew's duty clock, the extension rule and the reserve list, each cited.

Who has to sign before stations, crews and passengers are told?

The duty manager, with a reason code. Airline Disruption Management is OCC decision support: nothing reaches stations, crews, dispatch, ATC or passengers before that signature. The VP Operations Control co-signs above 25 cancellations or $3M, maintenance control confirms swaps and the dispatcher signs amended releases. Each step and decision is on a trail nobody can edit.

Can we test it on our own past disruption days before go-live?

Yes. The Agentic Solution Engine builds and deploys it from your requirements and documents (your recovery rules, crew agreements, contracts and customer service plan), and it goes live once each quality gate has passed. Before go-live it is replayed on your past disruption days; on the sample setup, its plans matched or beat the decisions made on 5 of 6.

Run airline disruption management
on one of your own past storm days.

We'll run Airline Disruption Management on one of your own past disruption days.