General Discussion
Related: Editorials & Other Articles, Issue Forums, Alliance Forums, Region ForumsHoly crap: the 737 fiasco is worse than we thought (Lion Air crash)
The investigation into this is absolutely astounding.
I'm in an aviation tech company and we just got emailed this advisory from the Air Line Pilots' Assocation:
The MCAS function becomes active when the airplane Angle of Attack exceeds a threshold based on airspeed and altitude. Stabilizer incremental commands are limited to 2.5 degrees and are provided at a rate of 0.27 degrees per second. The magnitude of the stabilizer input is lower at high Mach number and greater at low Mach numbers. The function is reset once angle of attack falls below the Angle of Attack threshold or if manual stabilizer commands are provided by the flight crew. If the original elevated AOA condition persists, the MCAS function commands another incremental stabilizer nose down command according to current aircraft Mach number at actuation.
This is the first description you, as 737 pilots, have seen. It is not in the AA 737 Flight Manual Part 2, nor is there a description in the Boeing FCOM. It will be soon.
(Emphasis mine)
Holy shit.
Cousin Dupree
(1,866 posts)lagomorph777
(30,613 posts)Baitball Blogger
(46,698 posts)causing a massive dose of WTF?
And, shit. It's raining outside so now I have to wait to start my errands.
Recursion
(56,582 posts)This control subsystem points the nose of the airplane down if the plane starts pointing "too far" up, by its own definition.
This control subsystem was introduced without any documentation or warning to pilots, and it seems to be responsible for the Lion Air crash.
Baitball Blogger
(46,698 posts)Thank you.
Cattledog
(5,914 posts)joshcryer
(62,269 posts)Adrahil
(13,340 posts)it's tricky. There should generally be a manual override in any circumstance that control inputs are automatically generated. If pilots KNEW that the MCAS could generate a nose down command, despite manual inputs, then they could have attempted a manual override. As it was, it seems the MCAS thought the pilots were commanding the aircraft into a stall condition. A lay person might say, "yeah, but the aircraft was descending! Rapidly!" Yes. But the instinct of many (though not usually trained pilots) would be to pull back the yoke and try to get the nose up. But if the aircraft is in, or close to a stall, that just makes things worse. The automatic down command is intended to prevent that from happening. If the AOA sensor had failed and there was no way to manually override the MCAS, then the aircraft was not savable. If there WAS a way to override the MCAS (likely, but I don't know), then pilots probably should have attempted such an override, but if they were not trained in this specific scenario, they may not have had enough time to think through the problem.
joshcryer
(62,269 posts)And I agree that the pilots should've known about this feature. When I read about the part being installed incorrectly or something to that effect, I figured there had to also be a pilot issue (in this case lack of information about an undocumented technology). There was an airspeed sensor that froze up in one flight and newer pilots were in control of the plane because the captain was asleep. He comes back from sleep after the new pilots struggled with the plane for a few minutes (causing it to stall), and immediately tells them to stop climbing. Was too late though as it'd been falling like a rock for a few minutes at that point, cockpit transcript reading is haunting.
Adrahil
(13,340 posts)If one realizes the paradox too late, then nothing can be done.
lagomorph777
(30,613 posts)FreepFryer
(7,077 posts)uponit7771
(90,335 posts)... HAD to have said something to someone
Cousin Dupree
(1,866 posts)Delphinus
(11,830 posts)This does not sound safe.
Engrish, please!
Response to Recursion (Original post)
Name removed Message auto-removed
Recursion
(56,582 posts)I can't link to a mailing list email. When they get it up on their website I'll be happy to link to that.
FreepFryer
(7,077 posts)its presence was undcumented... and so when it failed, there were no procedures to adjust to the condition.
A grievous error, indeed.
Is that correct, OP?
Recursion
(56,582 posts)Boeing adds new subsystems all the time, but if they affect control characteristics they have always documented that and told simulator manufacturers about them.
WhiskeyGrinder
(22,316 posts)0rganism
(23,937 posts)with help from corporate idiots who don't furnish this information to the pilots who need it
Xolodno
(6,390 posts)...its like Microsoft updating my PC quietly in the background and suddenly the programs I use most of the time are inoperable.
Recursion
(56,582 posts)In unusual circumstances, the same control inputs that can produce a climb in the old 737s produce a nosedive in the new ones, and they didn't mention that in the documentation.