Here's the story about a travel disruption that happened in the UK through a series of unexpected events.
It started with a flight between Paris and LA that passed over the UK. Its flight plan had two way points with the same name, and the software couldn't handle that and caused an error to appear, which then disrupted air traffic control. Controllers had to manually manage flights, and as a result they had to reduce the number of flights passing over that area.
There was a solution for this: an engineer could log in remotely and clear the error. Except that due to "the design and architecture" of the system, the credentials were rejected.
And it took them more than an hour to manage to log in.
By now, the complete system was facing a backlog and delays. Flights were being rerouted, departures were held up for hours. Chaos ruled for many hours, affecting airlines, passengers, and scheduling for a while to come.
And all because of a coding error and not having someone on site who could fix the problem. Oops.
https://www.businessinsider.com/air-traffic-control-chaos-engineer-login-problem-passengers-disruption-airlines-2024-11
https://www.businessinsider.com/air-traffic-control-chaos-engineer-login-problem-passengers-disruption-airlines-2024-11
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.