stroopwafel said:
I don't know if that is necessarily true. From what I understand the sensor in MCAS never worked as intended even in tests and they needed to put the jet engines closer to the fuselage to compensate for this and calculate a larger margin of error. That the pilots wrestled with controls when MCAS pushed the plane down so they kept flying at a dangerous altitude also isn't a good sign. I'd say the entire MCAS the way it was tested, overcompensated for and implemented leaves a lot to be desired. The argument that the pilots didn't receive specific intsructions on how to disengage MCAS because they 'should know about it' and that it only ever really works on autopilot is the crux of the problem: the plane crashed b/c the pilots were wrestling to take back it's controls. That is never good design even if the pilots lacked some crucial info on the specifics of the plane.
MCAS doesn't work on auto pilot only when hand flying. The engines are mounted slightly forward of where they are on the non max's (for ground clearance) so to keep the feel the same they added MCAS (On underwing mounted planes theres a nose up moment whenever thrust is added)
I hate to defend boeing when I fly their competition but these pilots had all the info. The bulletin was released last year so it was in their FOM(flight ops manuel). The bulletin even says where to put it in the FOM. Even if they never heard of MCAS it manifest itself as stabilizer trim runaway which is a memory item. ( aircraft usually have 10-15 things that are memory/immediate action items pilots have to have memorized)
It shouldn't matter if the trim issue is caused by a motor continuously running due to mechanical issue or due to software commanding it. The procedure is the exact same.
So assuming Ethiopian was MCAS induced they took off positive rate gear up, then got to flap retraction altitude when the issue arose because MCAS doesn't work till flaps are up. They would have noticed an increase in required backpressure to maintain pitch. (should be automatic to then trim up cause we use trim constantly when hand flying this would also have the effect of shutting off MCAS temporarily) If they didn't do that there is trim indication on their EICAS (center screen with trim/gear/engine data), there is also mechanical trim wheels they would see moving. Apparently none of those things registered with either pilot and they didn't execute the memory item which would have had them hit the cutout switches.
Like I said Boeing has some blame coming imho because MCAS doesn't time out after the initial 10 seconds. But these pilots outside of willfull negligence knew about MCAS, knew the procedure to stop it but when the time came didn't do the memory item.
Perhaps experience played a role, the FO only had 200 hours total, a 73 FO in the US would have closer to 4000-7000 hours.(just the nature of airline industry here vs abroad) Combine a new FO and suddenly you have a young captain trying to handle an issue basically single pilot, gets overwhelmed and doesn't execute. IDK.
TLDR, no love for boeing but the pilots knew of MCAS and had 5 different things the could have done to deactivate it, had a memory item for it that would have solved it for good, had 3 maybe 4(depending on eicas messages) things they would have seen/felt that would indicate trim issue. For whatever reason never did the memory/iai for it.