Re-crewing the flights a storm strands takes an airline 4 to 12 hours by hand. We got it to about a tenth of a second. When a storm grounds a hub, the downstream flights start losing their crews within the hour. The operations center works the phones for half a day while passengers sleep on terminal floors. The slow part was never the math. It was doing the math by hand, under rules that don't bend. So we built StormCrew, a shadow-mode advisor that sits on top of the solver an airline already runs. Inject the storm and it shows the blast radius first: the 53 flights now at risk, the grounded ones plus the downstream flights about to lose their crews too. Then it returns a recovery plan where every move is legal by construction. Crew assignments past FAA Part 117 duty limits or the union contract's segment cap are masked out before the optimizer ever sees them, so they can't be picked. In the seeded storm we recorded, 52 of those 53 flights came back with zero illegal assignments. Honest about what this is: a synthetic, seeded network with a real optimizer (CBC) doing the solving. We use the solver, we don't claim to beat it. We make the recovery fast, provably legal, and auditable. For anyone who runs an OCC: how much of your recovery time today goes to the re-crewing itself versus proving the plan is legal before you commit it? #IROPS #AirlineOps #CrewScheduling #FAAPart117