If MCAS is the culprit here, Boeing clearly released this functionality without proper vetting and testing. It’s a sad day for safety and for automation. These accidents will likely slow the advance of BVR for drones[2] and more autonomous flight for cargo.[3] The fact these accidents are occurring overseas where the pilots have less training will also buttress the decision for the 1500 hour rule.[4] Like I said, if MCAS is suspected here, probably time to ground the new 737 despite what it will do to Boeing, because right now it looks like they cut some corners, the FAA let them, and families are mourning. Pilot error isn’t really the issue, it’s engineering, process, and training.
[1] https://news.ycombinator.com/item?id=19077371
[2] https://www.altiuas.com/bvlos-mean-commercial-drone-users/
[3] https://www.bloomberg.com/news/articles/2018-10-10/will-you-...
[4] https://www.forbes.com/sites/marisagarcia/2018/07/27/a-perfe...
That doesn’t seem like engineering, process, nor training.
That looks like something connected to large scale corporate profit.
How did Boeing manage to gain self reporting to the FAA?
From what I read MCAS is not even a true safety system, much more like a piloting assist, and should not have had the authority to override pilot input.
It appears that the true stall avoidance system is a "hard" safety system and works independently with much safeguards, and a lot of "overrideability" just for such moments of sensor failure.
So, they added that dangerous system to just let pilots to have the same feel and experience as in old model - an absolutely noncritical issue.
Truly, "UX" people...
I'm sure this is an edge case given all of the successful 737 MAX 8 fights, but it's a catastrophic one.
To go from smooth flying conditions to having the nose unexpectedly dive and having seconds to save your life and everyone on board is almost more dangerous than difficult flying conditions because it's so unexpected.
I'd be surprised if Boeing continues to treat this as a training issue. The plane needs to be better.
There are 350 737Max in service. It's a brand new airplane - it went into service in mid-2017.
For 2 brand new (months old) 737Max to fall out of the sky is not an "edge case".
And Boeing’s procedures on how it disseminates information should be held under a microscope and punished severely.
2 accidents is 2 too many, but it's not like every MAX 8 or anywhere close to the majority or even a large minority are experiencing catastrophic failure.
Sure, it's far higher than what's acceptable and the industry norm, but I'd imagine it's enough of an edge case that it snuck past testing and 99%+ of real world flights.
I'm just saying its simpler, cheaper, and safer to deploy people who can troubleshoot simple flying systems rather than to deploy people who will have to debug untested and complicated automation systems on the fly. It would be the most extreme field service posting, ever.
What we have here is an over optimization problem; we "have to" build unflyable aircraft to keep up with everyone elses level of recklessness to squeeze a couple more hyper-financialized pennies out of the system or be replaced by someone reckless enough to do it. Traditionally regulation helps in these situations. The aircraft of the future is far more likely to have networking and interconnected processors prohibited by law for safety reasons than to be an internet of things self-flying appliance. That would result in a nice simple, admittedly lower performance, far more reliable overall system. Non-networked non-interconnected control microprocessors seem safe enough so far, but making an infinitely complicated hyper optimized system seems in practice to result in planes falling out of the sky too often.
Until we teach spherical cows to fly planes, that is...