Live data from Hacker News

Alaska Airlines' statement on IT outage

news.alaskaair.com

21–30 of 150 posts

Re: Alaska Airlines' statement on IT outage

#21
post #20
post #18

Was there any impact on the flights in air?

Several reported having to be diverted, and I think in one case a flight that left JFK had to return to JFK while over the midwest: https://www.flightaware.com/live/flight/ASA31

> Several reported having to be diverted

How does that work? What is it about a computer outage in your parent company that affects whether you're able to make an already-scheduled landing?

Re: Alaska Airlines' statement on IT outage

#22

I was affected. Taking off now for a 5:30pm PT flight to Seattle. Aside from clearly not having an appropriate disaster readiness plan, communication was bad even though some information was readily available. For example, there was an inbound ground stop for KSEA for hours, but it was never announced to passengers. We were very lucky the crew was fresh, and there was no discussion of when they would time out. I happ…

[flagged]

> someone should invent an anti-lead; something to put in the water supply to add 30 IQ points, but that would probably be punishable by death

Why do you think we add iodine to salt?

Re: Alaska Airlines' statement on IT outage

#23
post #20

Earlier quoted context omitted.

Several reported having to be diverted, and I think in one case a flight that left JFK had to return to JFK while over the midwest: https://www.flightaware.com/live/flight/ASA31

> Several reported having to be diverted How does that work? What is it about a computer outage in your parent company that affects whether you're able to make an already-scheduled landing?

I'm guessing any/some/all of:

- Whether parent company has the capacity to service your plane at the landing location

- Whether parent company has the capacity to handle boarding new passengers for the next flight at landing location

- Whether parent company can get next flight off the ground from landing location

- "Risk" management by sending planes and passengers where parent company thinks it has better ability to recover to normal operations

- And probably a bunch more only people who work in that industry would think of

Re: Alaska Airlines' statement on IT outage

#24
post #20

Earlier quoted context omitted.

Several reported having to be diverted, and I think in one case a flight that left JFK had to return to JFK while over the midwest: https://www.flightaware.com/live/flight/ASA31

> Several reported having to be diverted How does that work? What is it about a computer outage in your parent company that affects whether you're able to make an already-scheduled landing?

No flights were departing their gates in SEA so presumably it was turned around to avoid gridlock at SEA due to no gates available.

Re: Alaska Airlines' statement on IT outage

#27
I was affected as well. My IAH->SEA 7:10 PM Central flight took off 4 hours late. It’s 4 AM central and we’re just descending to land in Seattle. Communication from the airline was basically nonexistent and the poor ground crews didn’t get any information either. I thought we wouldn’t even take off because of crew time limits, but we were lucky to have a fresh one. The system apparently came back and died several times before we could take off. We pushed away from the gate because the system was working and then had to wait on the tarmac for an hour because the system was down again. Not a fun day for air travelers.

Re: Alaska Airlines' statement on IT outage

#29

I was affected. Taking off now for a 5:30pm PT flight to Seattle. Aside from clearly not having an appropriate disaster readiness plan, communication was bad even though some information was readily available. For example, there was an inbound ground stop for KSEA for hours, but it was never announced to passengers. We were very lucky the crew was fresh, and there was no discussion of when they would time out. I happ…

[flagged]

> they would probably want to pay $100 (rationally, closer to $1000) amortized over 50 years to pay for that

Which would just flow into the pockets of ClownStrike or some big consultancy and nothing would actually change.

Re: Alaska Airlines' statement on IT outage

#30

I was affected. Taking off now for a 5:30pm PT flight to Seattle. Aside from clearly not having an appropriate disaster readiness plan, communication was bad even though some information was readily available. For example, there was an inbound ground stop for KSEA for hours, but it was never announced to passengers. We were very lucky the crew was fresh, and there was no discussion of when they would time out. I happ…

[flagged]

> I think politically, everyone would want airlines to have working IT-systems and they would probably want to pay $100 (rationally, closer to $1000) amortized over 50 years to pay for that, but apparently humanity is just too stupid to make it work.

Not stupid, just corrupt :)

If we did this, the money would get misappropriated or stolen - most likely completely legally through overpaid consulting fees.

So clearly we should pay someone to prevent that from happening.

Wait a minute...

Post reply on HN