An MBA designed the door plug installation process?
Maybe it’s the Boeing engineers that need some scrutiny?
An MBA designed the door plug installation process?
Maybe it’s the Boeing engineers that need some scrutiny?
"We need to replicate the pitch performance of the 737-800. These engines pitch the plane up when accelerating and it messes up go-arounds."
"What if we have the computer just pitch down to compensate? We know the angle of attack and the engine thrust output."
<implements>
Meanwhile in another conference room:
"United is telling us that Airbus is giving them an A321 for 10% less than us. What can we cut?"
"No regulation requires us to have 3 angle of attack sensors. We could get by with 1 and stick it on the Minimum Equipment List if it fails."
"That sounds great."
Then the 1 angle of attack sensor fails the system that was designed for 3. Was it the engineer who agreed to hack 737-800 handling emulation onto the 737 MAX that failed here? Was it the engineer that agreed that the AoA sensors didn't need to be redundant, perhaps before MCAS was even invented?
These complex failures are rarely the result of one individual failing. Everyone did their job; the business saved United 10% (I actually have no idea who their launch customer was), the engineer saved thousands of pilots from being pulled off the line for re-training. But combined, it was a tragedy. Ultimately, it's the organization and its processes that failed, not an individual. As a manager, you own the organization and the processes.
Turns out the Max8 does have two angle of attack (AoA) sensors.
But the MCAS system only read from AoA1, and never validated it against AoA2. It was recieving info from AoA2, but never used it!
You can do something with 3 or more, but 2 are completely useless.
If there is a mismatch, the system outputs an error and MCAS will disable itself.
In fact, that is literally one of the requirements set by the FAA to begin flying the Max8 again
> FAA Airworthiness Directive approved design changes for each MAX aircraft, requiring input from two AoA sensors for MCAS activation, elimination of the system's ability to repeatedly activate, and allowing pilots to override the system if necessary.
It absolutely was the fault of the engineers who failed to realize what would happen with an AOA fault. I'd love to be corrected, I don't believe a single email from the engineers to management telling them would would happen was ever dug up. And, there's never been an engineer whistleblower saying "I warned them."
Has a single PE lost their license over the Max?
This is false. At the time of the incident (>1month) The FFA and NTSB found 23 reports of uncommanded pitch down attitudes during takeoff.
Quick Google gave me this.
https://www.sbs.com.au/news/article/it-pitched-nose-down-us-...
Hiding MCAS to avoid recertification was well above the paygrade of an engineer at a bench poking a circuit.
Also, if you want a short version of how this stuff goes very wrong even when engineers do say something, the challenger disaster[1] movie is great. Chase it with the NASA documents[2] for the long version.
[1]: https://www.youtube.com/watch?v=bvv2-7iOD_8
[2]: https://www.nasa.gov/history/rogersrep/genindex.htm
Edit: typo
or, what can engineers possibly know about engineering: https://www.airliners.net/forum/viewtopic.php?t=213075
Can they all be fired and the wealth they leach redistributed then please? :)
Cost
Quality
Time
MBA push for cost, then time (to market), above quality.
If you believe it should be engineers, we're fully in agreement, but then why do we have managers...
Heck, they fired the last CEO over the 737 crashes but he was literally only on the job for 3 years and had no involvement with the 737 design. The problem? He was an engineer and he was already stirring up shit inside. So they threw him under the bus and replaced with him another useless goon that spouts PR bullshit and has no technical experience other than milking companies dry.