Airline crew recovery that re-crews every broken pairing legally, with the crew told in 20 minutes
Every broken pairing re-crewed legally before it costs a flight, crew told in 20 minutes.
See one case, screen by screen ↓Airline crew recovery, also called IROPS crew recovery or crew disruption management, is the day-of-operation work of re-crewing flights when a delay, sick call or cancellation pushes a crew past its duty, flight time or rest limits. Airline Crew Recovery puts seven agents on the crew desk. They re-check every crew's legality on every event, build and independently check the repairs, show each one's knock-on and cost, and draft the crew notifications. A crew controller chooses, signs and sends.
How to choose AI for airlines: a buyer's guide to agentic AI solutions →
Updated
Airline crew recovery starts the moment a delay, a sick call or a cancellation hits the day of operation. The crew controller has to find which crews it pushes past their Part 117 flight duty period, flight time or rest limits, or the flight attendants' 10-hour rest under 14 CFR 121.467, and re-crew those flights before they leave. Today the crew system raises its alert when the break is already a fact. The controller works out the limit by hand, phones reserves down the call list and checks the pilot and flight attendant agreements from memory.
What the controller cannot see is what the repair does next: the pay protection and reassignment premium under the agreement, tomorrow's flight retimed for rest, a base left under its reserve floor for the evening bank. In December 2022 a US carrier's crew scheduling system was overwhelmed by a winter storm. The result was 16,900 cancellations, more than $600 million in refunds and a record $140 million DOT penalty.
Estimated split, in minutes, for one broken pairing at a busy crew base, worked by hand and with the solution.
Seven agents watch every crew's legality, build and check each repair, show its knock-on and draft the calls; a crew controller chooses and sends.
Tuesday, October 13, at the Denver crew base of Corvane Airways. CV 1442 is two hours late, and pairing 4127 is about to break. Here is what happens next, screen by screen, in the working solution.
Since 06:00 the agents have re-checked 3,912 crew members 18,420 times and repaired 9 pairings with Rosa. Her Today screen shows 3 pairings broken, 11 near a limit and 14 DEN reserves on the A320 family. The Legality Watch agent leads with the one that needs her before 15:05: CV 1442's two-hour delay breaks pairing 4127.
“Captain Okafor and FO Reyes would land in MSY at 20:35, 1 h 45 past their 18:50 limit.”
Pairings at DEN are drawn as chains of flights on one time axis, each crew's duty limit marked on its row. Pairing 4127's link at CV 1587 glows red: CV 1442 is two hours late with a bleed-air valve change. Two other crews are near a limit. The cabin crew stay legal at 14 h 00 of 15 h.
Captain Okafor reported at 06:50 for four segments, so the Table B flight duty period limits give him 12 hours and a duty end of 18:50. The projected flight duty period is 13 h 45. Rest before tomorrow would be 9 h 05, 55 minutes short of the 10 hours. Flight time is 6 h 16, inside the 9-hour limit. Every value links to its rule.
The Legality Watch agent never changes a roster. It flags, cites the rule and hands the pairing on.
The Crew Recovery agent reads the roster, the ops feed and maintenance control, then builds 9 repairs: reserves, swaps, a deadhead, an extension and a cancellation. The Rules Check agent re-checks each one on its own and fails 5: 117.19, 117.21, a lapsed qualification, timing and the call-out window. The Knock-on agent simulates 36 hours ahead, and the Reserve agent checks DEN coverage.
“Recommended option A to the Crew Controller · Waiting for your choice; nothing sent.”
Rosa asks in plain words. The Rules Check agent answers with its sources. The rule allows only one extension over 30 minutes before a 30-hour rest, and he used one on October 10: 45 minutes on CV 1720, reported to the FAA on October 12. His last 30-hour rest ended October 9, and company policy forbids planning past a limit.
“So I failed that option; you will find it with the other four on the compare page.”
A: DEN reserves Capt. Marisol Vega and FO Ethan Brooks fly both legs, with a 1 h 25 margin, for $3,030. B: swap with pairing 4133 for $3,550, but it breaks that pairing and still retimes tomorrow's CV 1588. C: two DEN reserve pairs for $4,860, leaving 10 reserves against a floor of 12. D: cancel CV 1587 and CV 1588 for $61,400, with the Duty Manager's co-approval. Each option passed 12 of 12 rules.
CV 1588 MSY–DEN leaves at 08:35 CDT instead of 07:40 so Vega and Brooks get their 10 hours of rest, at $1,850. 112 passengers are booked, and all six DEN connections still make their flights. DEN reserves go from 14 to 12, and the floor of 12 holds. Okafor and Reyes are released with pay protection, $1,180, and the MSY hotel changes names at no charge.
“Mark each item fine or flag it before you choose.”
Rosa picks option A and the reason code R2, “Reserve covers, knock-on accepted”. The dialog restates the repair: Vega and Brooks report at 15:05 at DEN gate B32, fly CV 1442 and CV 1587, lay over in MSY and fly CV 1588 tomorrow. Nothing has been sent yet.
“I choose this repair as Rosa Delgado, Crew Controller — e-signature, Oct 13, 2026, 14:10 MDT.”
The Notification agent drafts six messages: one each for Vega, Brooks, Okafor and Reyes, one for the four flight attendants and one for the crew hotel. Rosa sends all 6 at 14:12. All six acknowledge by 14:21. FO Reyes has not replied after eight minutes, so the agent calls her at 14:20 and she acknowledges by phone.
“Pairing 4127 is legal again … no flight canceled. 20 minutes from the break to the crew told.”
Every agent step and every human decision is listed, newest first, each row chained to the one before it so a change to any row breaks the chain. The evidence package exports for a grievance, an FAA question or an internal review. At night the Day Review agent writes up the day for Grant to sign.
The same broken pairing, seen by four of the people who carry it: what the day looked like, and what it looks like now.
Seven agents watch every crew's legality, build and check each repair, show its knock-on and draft the calls; a crew controller chooses and sends.
Re-checks every crew member on every delay, sick call and schedule change, and every 5 minutes. It works out flight duty, flight time, rest and cumulative limits, pilots and cabin crew separately, and flags near-limit and broken pairings with the margin in minutes.
Builds up to 12 repairs for a broken pairing: reserves, swaps, deadheads, retimes, extensions and cancellations. It ranks the ones that pass by cost, knock-on and reserve coverage, and re-plans around the controller's instruction, such as “use Hale's crew instead”.
Re-applies Table B and C, 117.11, 117.19, 117.21, 117.23, 117.25, 121.467, the pilot and flight attendant agreements, company policy and each crew member's qualifications to every repair, on its own.
Simulates each repair 36 hours ahead: tomorrow's flights and rest, other crews' pairings, reserves, hotels, passengers and pay. It prices every line from its agreement, contract or the delay-cost table.
Keeps each reserve's legal-until time under 117.21 by base, fleet and seat, offers reserves in the agreement's call order, and forecasts the evening need against the base floor.
Drafts one message per person, plus call scripts for reserves. It sends them after a Crew Controller approves, calls anyone who has not replied in 8 minutes and tells the Reserve Crew Coordinator at 15 minutes. After approval it updates crew tracking and the crew hotel.
Writes up the day from the audit trail at 22:00: every break and repair, how long the crew waited to hear, what it cost, any extensions, and lessons to approve.
Chooses every repair; the Duty Manager co-approves a cancellation. The agents propose; a named person decides.
Ask why, or tell the agents what to do in plain words. Every answer points to the rule, the roster record or the ops feed message behind it, and no crew member is called, assigned or released until a Crew Controller approves.
Why can't Captain Okafor fly CV 1587?
He reported at 06:50 and today has four segments, so Table B ends his duty at 18:50. CV 1442 is two hours late, so CV 1587 would land at 20:35, 1 h 45 past the limit. An extension is not available: he used one over 30 minutes on Oct 10 without a 30-hour rest since.
What happens to tomorrow's CV 1588?
With option A, Vega and Brooks are released in MSY at 20:50 MDT and need 10 hours of rest, so CV 1588 leaves at 08:35 CDT, 55 minutes late. 112 are booked; all six DEN connections keep at least 50 minutes. Cost about $1,850. Option C keeps 07:40 but leaves DEN with 10 reserves against a floor of 12.
Use Hale's crew instead
Re-planned and re-checked: Captain Hale and FO Kowalski land at DEN at 14:15 and are legal to 22:45 with four segments. Their CV 1621 to BZN then needs reserves Lowell and Park, and the lost layover pays a $520 premium. They land in MSY at 20:35 like any crew on CV 1587, so CV 1588 still leaves 55 minutes late. Total $3,550 against $3,030, and it changes two crews instead of one.
How many DEN reserves will be left tonight?
14 now. Option A uses two, leaving 12 against an evening need of 11 and a floor of 12. Keller and Lin (737 MAX 8) are held for pairing 4166.
13 screens from the working solution, on its sample data. Pick one to see it large.
Thresholds and approval levels are settings. A change is proposed, versioned, logged and applied only when the Crew Scheduling Manager approves it.
| Setting | Default | Choose from |
|---|---|---|
| Near-a-limit margin | 30 min | Any margin in minutes; pairings inside it are listed and options prepared |
| Planning buffer before a limit | 15 min | Any buffer in minutes; repairs must end at least this long before the limit |
| DEN evening reserve floor | 12 reserves, 17:00–21:00 | Set per base, fleet and time of day (company policy CR-7) |
| Call when no reply after | 8 min | Any number of minutes; crew app first, then a phone call |
| No planned extension over 30 minutes | Always on | Company policy CR-4 |
| Crew Controller chooses alone | Repairs up to $10,000 with no cancellation | Reason code and e-signature |
| A repair that cancels a flight | Crew Controller + Duty Manager | Co-approval (company policy CR-9) |
| An extension under 117.19 | Crew Scheduling Manager + the captain | FAA report drafted within 10 days |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on the sample day of the fictional Corvane Airways · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (US DOT consent order, December 2023: a record $140M penalty, 16,900 cancellations, over $600M in refunds and reimbursements). Rules cited: 14 CFR 117.11, 117.13 (Table B), 117.19, 117.21, 117.23, 117.25 and 121.467. People, flights, pairings and hotels named on this page are fictional: characters and sample data in the working solution.
Airline crew recovery, also called IROPS crew recovery or crew disruption management, is the day-of-operation work of re-crewing flights when a delay, sick call or cancellation pushes a crew past its duty, flight time or rest limits. Airline Crew Recovery puts seven agents on the crew desk. They re-check every crew's legality on every event, build and independently check the repairs, show each one's knock-on and cost, and draft the crew notifications. A crew controller chooses, signs and sends.
The Legality Watch agent works out each crew's flight duty period from Table B by report time and segments, plus flight time under 117.11, rest under 117.25 and the cumulative limits under 117.23. It does this on every event and every 5 minutes. Each limit and margin cites its rule. Every repair is then re-checked on its own by the Rules Check agent, including qualifications.
The Reserve agent offers short-call reserves in the agreement's call order, each with its legal-until time under 117.21: the reserve availability period plus duty may not exceed Table B plus 4 hours or 16 hours, whichever is less. It warns when a repair would leave the base under its evening floor. The Reserve Crew Coordinator decides any hold or release.
Yes. Cabin crew are checked separately from pilots: 10 hours of rest after a scheduled duty of 14 hours or less, with no reduction, and the flight attendant agreement's actual duty limit. In the demo, the four flight attendants on pairing 4127 stay legal at 14 h 00 of 15 h, with 10 h 15 of rest at MSY.
No. The agents never call, assign, release or retime anyone before a Crew Controller approves. The Notification agent sends only the approved text, and never calls crew in rest, except reserves on short call.
Yes. A repair that cancels a flight needs the Duty Manager's co-approval: nothing is canceled and no one is told until the Duty Manager co-approves. An extension under 117.19 needs the Crew Scheduling Manager and the captain, and its FAA report is drafted within 10 days. Company policy CR-4 rules out any planned extension over 30 minutes.
The Agentic Solution Engine builds and deploys it from your requirements and documents: your crew system, ops feed, Part 117 rules, pilot and flight attendant agreements and company policies. It goes live once every quality gate has passed. Before go-live it replays one of your past disrupted days and compares its repairs with what your desk did.
Not one illegal duty day published, and every limit shown with the rule that sets it.
1-min demoFatigue Risk Management SystemEvery fatigue report tied to its roster and the science the same day, fixed by the board.
1-min demoCrew Pairing OptimizationEvery trip legal and cited, at the cost and crew quality of life you chose.
1-min demoWe'll replay Airline Crew Recovery on one of your own past disrupted days, against your rules and agreements.