Timeline for Why are on-board computers allowed to change controls without notifying the pilots?
Current License: CC BY-SA 4.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 26, 2019 at 1:51 | vote | accept | Machavity | ||
Mar 26, 2019 at 0:03 | history | edited | RealAnswersNotAI | CC BY-SA 4.0 |
Clarified a few points
|
Mar 25, 2019 at 22:34 | comment | added | MikeY | There’s an argument to be made for a flight engineer to wade through all of that stuff, but that stuff is there to replace the flight engineer in the first place. Go figure. | |
Mar 25, 2019 at 21:33 | history | edited | RealAnswersNotAI | CC BY-SA 4.0 |
added disclaimer at bottom
|
Mar 25, 2019 at 20:21 | comment | added | reirab | I seem to recall a deluge of contradictory and confusing system messages being an issue in Qantas 32. Thankfully, the pilots were able to work through that one and get the plane in the ground mostly in tact (aside from the bits that had blown off the engine and wing when the turbine disc exploded,) but I seem to recall hearing the pilots talk about how many superfluous system messages they had to wade through in order to get to the important information of "an engine blew up, another is uncontrollable, and there's a hole in the wing." | |
Mar 25, 2019 at 18:20 | comment | added | Machavity | That's a good point. Information overload is a very real problem. | |
Mar 25, 2019 at 17:25 | history | edited | RealAnswersNotAI | CC BY-SA 4.0 |
Shortened first sentence of last paragraph
|
Mar 25, 2019 at 17:16 | history | edited | RealAnswersNotAI | CC BY-SA 4.0 |
Added disclaimer about how this isn't very satisfying of an answer
|
Mar 25, 2019 at 17:04 | history | answered | RealAnswersNotAI | CC BY-SA 4.0 |