Re:Deep dive into the UK air traffic control meltdown
by d1sxeyes on Monday September 11, 2023 @03:00PM
(#37472047)
> It makes me wonder if there wasn't someone who was fixing these as they came up in the 4 hour window, and he just happened to be off that day.
This is very possible. I know of a guy who does (or at least a few years ago did) 24x7 365 on-call for a piece of mission (although not safety) critical aviation software.
Most of his calls were fixing AWBs quickly because otherwise planes would need to take off empty or lose their take-off slot.
Although there had been some “bus factor” planning and mitigation around this guy’s role, it involved engaging vendors etc. and would have likely resulted in a lot of disruption in the short term.
Re:Deep dive into the UK air traffic control meltdown
by fbdab103 on Monday September 11, 2023 @04:34PM
(#37473300)
Please tell me this guy is now wealthy beyond imagination and living a life of leisure?
Re:Deep dive into the UK air traffic control meltdown
by d1sxeyes on Tuesday September 12, 2023 @03:30AM
(#37477853)
I would love to. But it wouldn’t be true.
Re:Deep dive into the UK air traffic control meltdown
by zaphar on Monday September 11, 2023 @03:12PM
(#37472239)
Bad records aren't supposed to be ignored. They are supposed to be looked at by a human who can determine what to do.
Failing the way NATS did means that all future flight plan data including for planes already in the sky are not longer being processed. The safer failure mode was definitely to flag this plan and surface to a human while continuing to process other plans.
The thing that blows my mind is that this was apparently the first time this situation had happened after 15 million records processed. I would have expected it to trigger much more often. It makes me wonder if there wasn't someone who was fixing these as they came up in the 4 hour window, and he just happened to be off that day.