Slashdot Mirror
Computer Glitch Friday Grounded US Airways Flights
mschaffer writes "A computer glitch Friday night snarled the travel plans of US Airways customers, as reports flooded in of flights grounded around the country." As someone stranded for several hours yesterday by this outage, "glitch" seems like quite a euphemism. With outgoing flights blocked, and new ones arriving full of passengers expecting to meet connections, the atmosphere got a little heated. Customers could see nice weather, and planes lined up outside, but "The System Is Down" trumps all. The E concourse at Charlotte (a US Airways hub) was packed full of customers ranging from livid (a handful) to merely angry (most) to calmly resigned — which means those of us with seats, snacks, and books or computers. It was disheartening to see how brittle is the infrastructure the airline employs; with the part of the system visible to airline employees down, customers thought they might get more information, or even rebooking, through the US Airways website. But that was down, too, and all the desk staff could do is shrug.
OK, let's count to three and blame COBOL! :p
"Sum Ergo Cogito"
I work in airport IT, so I'll describe what I see airline crews doing during trouble. If the system at one gate or terminal is down, yes, then they'll send the plane on it's way. This is called "boarding manually". They simply hand collect tickets, hand count bags, etc, and send the flight off. After they've gathered all of the info thats been collected manually, they'll send it to their local office or front desk and process it at working terminals that have a connection to airline systems. It's a pain, but do-able. But if EVERYBODY is down, then the whole thing grinds to a halt. If no one has any access to all the schedule info, weight and baggage, manifests, etc.... then it's simply impossible to board manually on a massive scale.
Life is hard, and the world is cruel
As I am now located in proximity to an airport with a US Airways "service focus" and have had the "pleasure" of flying with them several times, I have to ask - how would you be able to tell the difference? Every time I've been in a US Airways terminal, there's always a significant number of non-weather-related delays and cancellations (compared to the other airlines' monitors). My wife and I have independently had three separate incidents this year where we were 4th and inches from having to stay overnight at an airport due to cancellations/late planes/overbooked crew/etc. In two of those cases, I had flights where we took off at the 2'55" mark, just shy of the three hour requirement to return to gate and let everyone off. The cynic in me suspects that US Airways is actually using that three hour window to plan its flights.
It's an abhorrent mess, and when I see the US Airways CEO defending against his last place customer service ranking, I have to wonder just how much denial one management team can stand.
"Mod, mod, mod...and another troll bites the dust."
This simply isn't about the problem. It's about whether the solution has been implemented. Nothing more.
And that is down to whether it is cost-effective to implement the solution. You will never be able to get the probability of failure down to zero. and the cost skyrockets the closer you get to zero. How often do outages like this happen, and how much would it cost to prevent them at every airport worldwide? And to prevent every other conceivable scenario? Yes, it could have been prevented, and lots of other possible outages that didn't happen could have been prevented, but the cost of air tickets would be prohibitive.
Quidnam Latine loqui modo coepi?