Hacker News new | past | comments | ask | show | jobs | submit login

cursory search:

> Preliminary information about the accident remains scarce, though two people familiar with the aircraft tell The Air Current that the aircraft in question, N704AL, had presented spurious indications of pressurization issues during two instances on January 4. The first intermittent warning light appeared during taxi-in following a previous flight, which prompted the airline to remove the aircraft from extended range operations (ETOPS) per maintenance rules. The light appeared again later the same day in flight, the people said.

https://theaircurrent.com/feed/dispatches/alaska-737-max-9-t...

No idea about the accuracy of the site. And it seems like they have some script that prevents text highlighting for whatever reason (turn off Javascript).




Well, that's an interesting thing. During taxi-in, the cabin altitude should be the ground altitude; outflow valves open at touchdown.

Hard to understand how an an incipient failure could manifest then (e.g. from increased leakage).

Of course, there's warning lights for excessive cabin pressure, etc, too... which would point to a different theory of the problem than a structural manufacturing problem.


Is "sensor just no longer responding" a failure mode which could trigger the alarm?


Jon Ostower is one of the best aviation reporters in the business and the Air Current is a site many professionals and executives in the industry trust.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: