The disruption environment changed underneath the people we trained to absorb it. The job description has quietly moved from fire station to portfolio management — and most operations are still running on the old manual.
By Joshua Goring, Chief Commercial Officer, StratosX
It’s 4 a.m. on a Tuesday in an airline OCC somewhere in North America. A controller who’s worked every irregular ops season since the 2010 ash cloud is fielding three phone calls, two chat channels, and four screens. She is extraordinary at what she does. She is also, by any honest modern definition, doing the wrong job. The work in front of her is not firefighting. It’s portfolio management: decaying options, competing constraints, and decisions that compound across the network. The tools haven’t been told yet.
The job description changed while nobody was looking
OCC culture was built for crisis. Heroic, adrenaline-driven, individual. A good controller in 1998 was the one who kept the aircraft moving through a thunderstorm with a phone in each hand. That instinct — react, decide, absorb — is still the backbone of how most ops floors run.
But the environment underneath has changed. EU261 in Europe. APPR in Canada. DOT rulemaking tightening in the United States through 2026. Every minute a disruption continues now carries a compensation number. Passengers expect proactive rebooking before they’ve even been told the flight is delayed.
Close to half of all delay minutes are now reactionary, disruption multiplying through the network. The cost of getting a recovery wrong is no longer a quiet operational footnote. It’s a line item the CFO watches. The job description has changed. The architecture around it has not.
What traders have that controllers don’t
Walk onto any trading floor and you’ll find a culture airline operations would recognise, but have not yet adopted.
Traders have real-time visibility across every position, consolidated into one view. Pre-computed scenarios for every plausible market move. A number on every option, and critically, they can see those options decaying in real time. A position available now won’t be in thirty minutes. The discipline is: decide while the option still has value, because deliberation has a cost.
Airline controllers face the same physics. The spare aircraft available right now will be assigned to another recovery in twenty minutes. A crew pairing that’s legal at 14:00 hits its flight duty limit at 14:45. The protection seat on the next connecting bank closes when the gate agent releases it. Every minute of deliberation narrows what’s possible, but nothing on the controller’s screen tells them the option is depreciating.
Worse, the information they need lives in separate systems. Aircraft state in one feed. Crew legality in another. Passenger connections in a third. Cost exposure derived manually. Controllers assemble the picture themselves, from memory and phone calls, under pressure. That isn’t a training gap. It’s a data architecture problem.
Why individual brilliance hits a ceiling the architecture built
The airlines with the strongest OCC operators look brilliant in normal operations. They get punished during compound events, not because the operators are less capable, but because individual brilliance doesn’t aggregate when the architecture forces sequential decisions.
A morning AOG triggers a cascade that will hit passenger connections in six hours. Three desks — aircraft, crew, passenger — each take ownership of their piece. Each solves the problem with excellent individual judgement, working from the information they can see.
The combined outcome is worse than it needed to be. The aircraft desk’s best swap breaks the crew desk’s pairing logic. The crew desk’s best reassignment strands passengers the passenger desk was about to protect. Three right answers, sequentially. One wrong outcome, together. By the time they reconciled it, the decision window had already depreciated.
This isn’t a coordination failure, and it certainly isn’t a people failure. It’s a structural one. When each desk can only see its own constraints, sequential conflict is built into the system. The answer isn’t faster controllers or better heroes. It’s a shared operational picture: aircraft, crew, and passengers evaluated as one joint problem, with trade-offs visible to everyone at the same time.
The three shifts the next decade requires
Getting the OCC from fire station to trading floor is not a single technology decision. It’s three shifts in how decisions get supported.
From fragmented to unified awareness. Aircraft, crew, and passenger constraints evaluated against each other at the same moment, not handed off through three desks or reconciled in the controller’s head under a countdown. One ranked set of options that accounts for crew legality, aircraft availability, passenger exposure, and downstream cost. The controller stops assembling and starts choosing.
From reactive to continuous. The analytical work doesn’t start when the disruption starts. It runs in the background, monitoring constraints and pre-computing scenarios, so when the moment arrives options are already ranked and the controller is choosing, not assembling.
From individual memory to institutional memory. Fifteen years of “which routes cascade, which bases have flex” lives in the heads of controllers who will retire in the next decade. The shift is to encode that knowledge into the decision support layer, while the experts are still around to validate it and trust that the system has learnt what they know.
What changes when you make the shift
The controller’s job doesn’t disappear. It evolves. Less time assembling information, more time making judgement calls with full awareness. Less adrenaline, more intent. The operation handles bigger problems with fewer fire drills, because the architecture surfaces what matters before the window closes.
Senior controllers stay not because the next recovery will be adventurous, but because the job lets them do work worthy of their experience, with the full picture in front of them rather than reassembled from memory under a countdown.
The airlines that complete the shift first will be the ones still competing in 2030. The alternative — heroic controllers burning out under a compounding disruption load and a tightening regulatory environment — is not a ten-year plan. You can’t fund what you can’t see, and recovery remains aviation’s largest unmeasured function.
The OCC of 2030 won’t be defined by headcount. It’ll be defined by whether the architecture gives controllers the full picture — aircraft, crew, passengers, cost — before the decision window closes.
Joshua Goring is Chief Commercial Officer at StratosX, the company behind X360, an integrated recovery platform for airline operations centres. StratosX will be presenting on this topic at Aviation Festival Americas, Miami, June 2026. Join us today.
For more like this, see:
