So all these airlines choosing to ground the planes must be acting because they've got the first data from the black box, right?
So all these airlines choosing to ground the planes must be acting because they've got the first data from the black box, right?
So all these airlines choosing to ground the planes must be acting because they've got the first data from the black box, right?
feels like an easy thing to blame but i don't think its far fetched either.
Terrifying.
Where's the Boeing Defense Force from the other thread with the poster that was trying to blame the pilots and amounted it to user error? Because he sure looks stupid now.
I think I read somewhere that only a single reading is required to trigger mcas though. Shouldn't it ideally require both (and not activate if there's a disagreement?)
My main concern is that it's now rushed and will be more of an issue.The thing I don't quite get...
Boeing claims that they will roll out an important MCAS update in ~10 days and they blame the government shut-down... yet the government shut-down was over more than 2 months ago.... and they couldn't get their critical update approved... ? and now they can get it done in less than 2 weeks?
and nobody is calling them out on their bullshit?
This is an interesting theory, it also explains why they would (possibly) disable the autopilot allowing the MCAS system to take over.It'd be interesting if it was actually an auto throttle or engine power management issue.... if the throttle went crazy, it would push the nose up, which would then cause the AP or MCAS to trim the nose down... and if the readings were messed up the throttle could kick even higher.
That could actually explain both incidents then.
These deaths were likely not some freak accident. Pilots complained at least five times to federal authorities last year about the model's autopilot system, many warning that the planes suddenly tilted nose-down after take-off, which, based on the evidence recovered, appears to be what happened in the Ethiopian flight too. One pilot called the flight manual "inadequate and criminally insufficient." Another called the shoddy level of training pilots received to fly the planes "unconscionable." Yet until almost the last possible moment, the Federal Aviation Administration continued to argue that there were "no systemic performance issues" and "no basis to order grounding the aircraft." There's a reason Ralph Nader, the famed consumer advocate and Samya's great uncle, calls the agency a "patsy."
Boeing is not just a lobbying juggernaut that donates prodigiously to politicians all over the country; it's also a company in which numerous members of Congress are personally invested, and it cultivates mutually beneficial financial relationships with top officials. Meanwhile, as William McGee of Consumer Reports told Amy Goodman, these issues are rooted in the FAA's lax, business-friendly oversight of the very industry it's meant to regulate, a case of regulatory capture that stretches back long before this administration.
But more than that, they are victims of an ideology that tells us the greatest insult to human life is not the death and misery that comes from unchecked greed, but efforts to democratically control it through public institutions. The real problems aren't unsafe products, pollution, dangerous chemicals, and the like, we're told, but "red tape" and the taxes used to fund the bodies regulating them. Meanwhile, activists like Nader have long been painted as "wacky" extremists in the pursuit of some quixotic ideological crusade simply for trying to do things like prevent people from dying in cars without seat belts.
The fact so many planes are already grounded indicate that this will hurt Boeing very badly and for a very long time.https://www.jacobinmag.com/2019/03/boeing-crash-faa-trump-safety-regulation
The Lives the Free Market Took
The fact that it was designed to support that checking/redundancy but not mandated is crazy. Planes fly over populated areas, you shouldn't allow cost cutting to that level. And on a multi million dollar purchase the 1% (wild guess, would be interesting to know the cost difference) add on for extra safety takes some awful accounting to justifyIMO the thing Boeing / the FAA have to answer for is how an indicator to pilots that two sensors are in disagreement is optional.
IMO the thing Boeing / the FAA have to answer for is how an indicator to pilots that two sensors are in disagreement is optional.
link to this?Answering my own question sort of, the planes in question have three different indicators telling pilotsif there is a disagreement between the two AoA sensors, all of which are optional at an extra cost, and Lion Air had none of them. Apparently this is not mandated by the FAA as something that is required to be included.
The fact so many planes are already grounded indicate that this will hurt Boeing very badly and for a very long time.
I originally heard it discussed here (21:30) - https://www.flightradar24.com/blog/avtalk-episode-53-ethiopian-302-and-the-grounding-of-the-737-max/link to this?
did not know planes had optional packages like cars.
SINGAPORE/SEATTLE (Reuters) - An optional warning light could have alerted engineers about mechanical faults on Lion Air's Boeing 737 MAX jet that crashed last month, experts said, sparking an industry debate over whether installing the system should become mandatory.
Lion Air did not install the AOA DISAGREE alert, which warns pilots when the "angle of attack" (AOA) readings do not match, because it is optional and not required by regulators, Managing Director Daniel Putut told Reuters.
"In retrospect, clearly it would have been wise to include the warning as standard equipment and fully inform and train operators on MCAS," said Clint Balog, a professor at Embry-Riddle Aeronautical University.
"I expect you will see this warning included in future MAX production and retrofitted into already delivered MAX aircraft."
Boeing and the U.S. Federal Aviation Administration (FAA) made the AOA alert an optional feature for the 737 MAX, meaning it was not deemed critical for safe operation.
https://en.wikipedia.org/wiki/Competition_between_Airbus_and_BoeingI've never even flown in a plane that isn't a Boeing. How can it hurt them when they monopolize the market?
Why are you so confident of this?Boeing will be just fine. Beyond taking some sort of lawsuit hit. And even then, based on the preliminary report, one should still expect the Lion Air report will place some culpability on Lion due to the maintenance / logging issues that should've taken that plane out of service.
737 MAX will be back in service in a matter of weeks and will continue to be delivered in the thousands.
That's not true at all. Airbus is as common as Boeing. Maybe you only fly domestically?I've never even flown in a plane that isn't a Boeing. How can it hurt them when they monopolize the market?
That's not true at all. Airbus is as common as Boeing. Maybe you only fly domestically?
The DC-10's production was ceased due to lack of orders merely four years after it was grounded for a while.
The DC-10's production was ceased due to lack of orders merely four years after it was grounded for a while.
Where's the guy who kept insisting in this thread this was the pilot's fault for not following the manual. That was infuriating.
From the article posted above:It's still the case that if the runaway stabilizer trim checklist was followed the Lion Air crash would not have happened. We know this because the previous flight crew did exactly that on the flight earlier in the day. If it turns out the problem on this flight was the same it would also be true that working down the three items on the checklist would address the problem and allow the flight to continue with manual stabilizer trim.
Boeing insists that the pilots on the Lion Air flight should have recognized that the horizontal stabilizer was moving uncommanded, and should have responded with a standard pilot checklist procedure to handle what's called "stabilizer runaway."
If they'd done so, the pilots would have hit cutoff switches and deactivated the automatic stabilizer movement.
Boeing has pointed out that the pilots flying the same plane on the day before the crash experienced similar behavior to Flight 610 and did exactly that: They threw the stabilizer cutoff switches, regained control and continued with the rest of the flight.
However, pilots and aviation experts say that what happened on the Lion Air flight doesn't look like a standard stabilizer runaway, because that is defined as continuous uncommanded movement of the tail.
On the accident flight, the tail movement wasn't continuous; the pilots were able to counter the nose-down movement multiple times.
In addition, the MCAS altered the control column response to the stabilizer movement. Pulling back on the column normally interrupts any stabilizer nose-down movement, but with MCAS operating that control column function was disabled.
These differences certainly could have confused the Lion Air pilots as to what was going on.
I can't see 737-Max not taking a hit when it's a risky plane rolling its chances on a new software update plus I'm sure people will be weary of taking that plane which in turn will affect the airlines. So why order more of a tainted aircraft.
I mean, in the end I'm sure Boeing will be fine. But this will cost.
It's still the case that if the runaway stabilizer trim checklist was followed the Lion Air crash would not have happened. We know this because the previous flight crew did exactly that on the flight earlier in the day. If it turns out the problem on this flight was the same it would also be true that working down the three items on the checklist would address the problem and allow the flight to continue with manual stabilizer trim.
That can make you mad if you want it to but it's still true.
It absolutely behaves as uncommanded runaway trim. It's trimming without being told to specifically when hand flying. Of course you can counteract it with the trim switch on the yoke - you always can. That description makes little sense.
The same goes for car developers. Ignorance is bliss.Wasn't there an old Dev / QA joke about designing software for airplanes...
"10 developers were asked if they would ever fly in a plane that they developed software for. 9 out of 10 of the developers quickly replied No. The other developer said it wouldn't matter because there's no way my plane would even make it off the ground."