Aviation operations
When a tail goes MX or FAR 117 bites, OCC needs a defensible recovery in minutes—not a cascade of cancels. See routing repair, multi-leg crew assignment, hybrid alternates, and compliance-ready audit trails.
Loading OCC command center…
Overview
Disruption → routing repair → crew rebid → audit pack.
Workflow
Designed for operations controllers—under two minutes to a defensible recovery plan.
Load disruption
MX hold, FDP bust, or weather cascade.
Recover
Tail routing + CP-SAT crew assignment.
Compare plans
Manual, classical, and hybrid alternates.
Export audit
FAR 117 proof, QUBO, and QPU trace.
Scenarios
Each scenario exercises tail routing, FAR 117 crew legality, and recovery cost trade-offs.
Inbound delay pushes a connecting crew over FDP at KDCA; two afternoon departures need reassignment.
Tail
N903DL
Station
KDCA
Quals
A320 · ETOPS
Crew affected
8
Network
2 legs in view · amber rows are in the disruption cascade
| Flight | Route | Dep | Tail |
|---|---|---|---|
| B61441 | KDCA → KORD | 07:00 | N445BZ |
| B61442 | KORD → KDFW | 10:00 | N445BZ |
Engine log
Tail routing, crew assignment, repair window, then hybrid micro-solve.
Awaiting disruption
Select a scenario and click "Recover" to populate this log.
Recovery plans
Each plan assigns crew across all open cascade legs with FAR 117 proof in the audit drawer.
Plans appear after recover
You will see one classical recovery plan and up to three hybrid alternates.
Scoreboard
Run "Recover" to compare manual, classical, and hybrid paths.
No results yet
Click "Recover" to generate the OCC scoreboard.
Business case
Model DOT-tracked disruption cost for your network. Figures are directional for OCC discussion.
Monthly savings
$119,000
Annual savings
$1,428,000
Avoiding ~1 controllable cancellations/month at $850 per pax.
Your data
PII-free CSV only. Session data expires in 24 hours.
Required: crew_id, qualifications, base, block_hours_week, last_duty_end, seniority_date.
