Should we therefore ground and review all the planes?
Also, the autopilot uses stabilizer trim. If you turn stabilizer trim to cutoff, you have no autopilot. Also, the emergency airworthiness directive says it's possible a runaway continues even after stabilizer trim is set to cutoff: If runaway continues, hold the stabilizer trim wheel against rotation and trim the airplane manually.
Once there was a second crash, with stabilizer jackscrew in the full nose down position, it was untenable to allow the planes to be considered airworthy, for the very central reason that we don't completely understand what happened and how to avoid it.
The proper response in aviation safety is not to assume pilots are doing the wrong thing upon receipt of an emergency airworthiness directive. It's to assume they are following the directive. You don't just pretend they're morons and keep on subjecting the general public to risk, while you guess at what the problem is.
And we don't want that?
> You can drive your car without cruise control
Sure, because cruise control is there to allow me to be lazy, not to keep my car on the road.
The aircraft has handling deficiencies at high angles of attack due to the engines being mounted differently. The MCAS is there to correct this. It's this or redesign the plane. Only 2 things that could have helped: an angle of attack disagree light to warn the pilots of the issue, and to to retrain the pilots. The first was sold just as an optional package, the second was considered unneeded since Boeing treated the new plane as a perfect equivalent of its predecessor. Disabling the MCAS is not a fix and without it the plane is not certified to fly.
You can fly a plane without an engine if needed but just try certifying a plane with one engine under one wing.
It is shocking to me that the second crash happened, if they both turn out to be MCAS and stab trim sourced. How could you step into the cockpit of a 737-Max that day and not know about the MCAS issue and be primed to respond according to the checklist?
I have to add that I'd be happy to put myself or my family onto a 737-Max flown by a US-flag carrier (Southwest, American, United [Delta doesn't fly the -Max]), as I believe there's a significant variance in crew training worldwide.
It shocks me that the redundant angle of attack sensor and the "disagree" light is not standard equipment. Who is buying multi-million dollar airplanes and cares about the cost of an angle of attack sensor and a lamp? Not people that care about safety, that's for sure. I know the airline industry loves nickel-and-diming their customers, but safety equipment is a little more important than priority boarding and a checked bag. It is shameful that Boeing adopted that business model.
More on angle of attack sensors: https://www.flightliteracy.com/angle-of-attack-indicators/. If you fly GA, you should get one. Having a readout of the flight energy you have available is one of the greatest safety upgrades you can make.
U.S. based pilots have said they didn't know anything about MCAS or MCAS upset until the FAA issued an emergency airworthiness directive, AD#: 2018-23-51, expressed surprise and were critical to discover this after the fact. Years after the fact. And it took a crash.
A second crash, despite the issuance of the AD suggests the AD is somehow sufficient. Maybe we don't know the full range of possible MCAS upset behavior. Maybe we don't know if there are additional factors that contribute to surprise and confusion.
the MCAS caused almost crash the day before the first crash of the same plane - it was only that off-duty pilot who knew about MCAS and thus saved the plane. Yet the next day that plane flew again with an MCAS unaware crew. Looks like some systemic issue. Grounding of the planes would allow to correct the specific tech issue of MCAS. Whether the systemic issue is going to be corrected is yet to be seen.
What is a waste is pretending that wasted resources is the worst thing that can happen here when we have two fatal crashes being investigated.
https://www.schneier.com/blog/archives/2016/10/security_desi...
Well, that put me my place. I'll hop right on another one tomorrow!