Moderators: jsumali2, richierich, ua900, PanAm_DC10, hOMSaR
Interested wrote:osiris30 wrote:N14AZ wrote:Wow, I really hope no one of the ET crash victim’s families will read this statement.
Why? Because it is logical. Good grief. Everyone is falling all over themselves. This thread is discussing an accident. Accidents need to be dissected in a logical manner, not an emotional one. Emotional dissections lead to biases. Biases lead to erroneous decisions and data favoring. The families of the people on BOTH ET and JT flights have my most sincere condolences, as do the families of the folks on the Atlas '67, as do the families of the folks in NZ this morning. Condolences don't do jack squat to make anything safer or better. Calling out a false assumption is not some horrible heartless act as much as people here like to think it is when they climb aboard their trusty tall steed of moral righteousness.
The statement is 100% true because: There is NOT ONE single piece of man-made equipment on the planet that is PERFECT. Every aircraft has errors, so does every car, building, bridge, toaster, fridge, stove, lightbulb, etc. It does NOT (in and of itself) make them unsafe. If you can't grasp that, perhaps this thread isn't the one for you. The poster I was replying to was conflating imperfection with unsafe. That was and still is a false assumption and I called them on it.
Boeings wording for the software upgrade they've been working on since the Lion crash is:
the upgrade is designed “to make an already safe aircraft safer”.
I'm going to suggest they've had to be very careful when choosing those words
And I'm going to suggest they are biased
And I'm going to suggest that by the standards we expect plane makers to set the actual wording should be
"To make an unsafe aircraft safer"
This plane clearly wasn't and still isn't safe to the level Boeing or any other plane maker would expect?
Do you disagree?
Boeing won't admit it. But its out of their hands now anyway.
Interested wrote:The exact same plane that isn't safe to fly now wasn't safe to fly in October when it first crashed. Boeing became aware it wasn't safe in November at the latest. If not before.
osiris30 wrote:but I won't delude myself into thinking we are somehow less fallible than we were 20-30 years ago. The only difference is the level of arrogance has increased many-fold to the point where we THINK we are so much better than we used to be.
enilria wrote:UPDATE
Investigators at the crash site of the doomed Ethiopian Airlines flight have found new evidence that points to another connection to the earlier disaster involving the same Boeing jet.
The evidence, a piece of the Boeing 737 Max 8 jet that crashed in Ethiopia last weekend killing 157 people, suggests that the plane’s stabilizers were tilted upward, according to two people with knowledge of the recovery operations. At that angle, the stabilizers would have forced down the nose of the jet, a similarity with the Lion Air crash in October.
The causes of both crashes are still under investigation, but the new evidence potentially indicates that the two planes both had problems with a newly installed automated system on the 737 Max jet intended to prevent a stall.
https://www.nytimes.com/2019/03/15/busi ... crash.html
N212R wrote:osiris30 wrote:but I won't delude myself into thinking we are somehow less fallible than we were 20-30 years ago. The only difference is the level of arrogance has increased many-fold to the point where we THINK we are so much better than we used to be.
Math and science test scores, in the US, would argue we are MORE fallible than 20-30 years ago.
Varsity1 wrote:YoungDon wrote:Varsity1 wrote:So the first officer had 200 hours? This was probably his first flight flying a jet of any kind. I would suspect a loss of control.
That's definitely not the case, training programs in foreign countries start out with cadets with no time flown beginning on jets. He's definitely inexperienced, but it's entirely possible all of his flight time is in jets.
What will be interesting to know is the amount of time he had on the MAX.
You don't spend your first 200 hours learning in jets anywhere on earth except some militaries.
Even if he had 200 hours all in the 737 max, it's almost nothing for flight time. Most pilots fly 100 hours a month!
VS11 wrote:How soon apart were the two crashed MAXes built? Who is the manufacturer of the pitot tubes and the AOA indicators? MCAS may have its issues and like all software it is work in progress - wouldn’t be surprised if Boeing was working on newer versions even before Lion Jet. However, there is this serious issue of low quality components being installed on jets. Does Boeing or Airbus test these component before installed?
Sooner787 wrote:VS11 wrote:How soon apart were the two crashed MAXes built? Who is the manufacturer of the pitot tubes and the AOA indicators? MCAS may have its issues and like all software it is work in progress - wouldn’t be surprised if Boeing was working on newer versions even before Lion Jet. However, there is this serious issue of low quality components being installed on jets. Does Boeing or Airbus test these component before installed?
That's what I've been wondering. What if this turns out to be a manufacturing quality issue,
perhaps a batch of faulty AOA indicators or heck, maybe some bad wiring installations?
There was plenty of discussion how hard the workers were scrambling to adjust to
the higher build rate at the Renton factory. Something could have fallen thru the cracks
in their rush to catch up to the breakneck build rate
osiris30 wrote:As time has gone on I have continued to flesh out what *I* feel the chain of events is and to my mind now it starts before the take-off roll:
1) Either on prior flight or before commencing this flight; pilots of last flight or this flight disable MCAS as a precatuion (stab cut-off)
2) PIlots of this flight miss (or knew it was off), but fail to trim plane correctly.
JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
dragon6172 wrote:JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
Any plane left unsupervised will fly itself into the ground.
gensys wrote:JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
Such as AF 447 doing so from all the way up at cruise altitude?
IIRC the remedy for the A330 was replacing the defective part (pitot) and improved pilot training.
Are you as equally unhappy with the A330 situation?
gensys wrote:JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
Such as AF 447 doing so from all the way up at cruise altitude?
IIRC the remedy for the A330 was replacing the defective part (pitot) and improved pilot training.
Are you as equally unhappy with the A330 situation?
JohnKrist wrote:dragon6172 wrote:JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
Any plane left unsupervised will fly itself into the ground.
Well, this plane wasn’t really unsupervised, was it?
dragon6172 wrote:JohnKrist wrote:dragon6172 wrote:Any plane left unsupervised will fly itself into the ground.
Well, this plane wasn’t really unsupervised, was it?
Neither was AF447
DeltaMD90 wrote:Way too much speculation going on from people without the proper expertise and hard facts from scene. Why can't we say "we don't know at this point??osiris30 wrote:As time has gone on I have continued to flesh out what *I* feel the chain of events is and to my mind now it starts before the take-off roll:
1) Either on prior flight or before commencing this flight; pilots of last flight or this flight disable MCAS as a precatuion (stab cut-off)
2) PIlots of this flight miss (or knew it was off), but fail to trim plane correctly.
What is your background? Are you in the airlines and/or a Boeing pilot? Granted I have not worked for the airlines, and I am not currently a MAX pilot (but I did fly 737-800s for a few years) and I have a VERY hard time believing what you are so sure or here
1: the previous pilots that supposedly got this malfunction and threw off the stab switches didn't relay this info to maintenance and/or maintenance didn't relay this info to the pilots/it wasn't seen in the write ups?
2: what do you mean "disable MCAS as a precaution?" As in they had flight control problems or uncommanded nose drops and switched the stab cutoff switches? That would make it even more unbelievable they simply forgot to tell maintenance/maintenance didn't immediately ground the plane/didn't tell this crew/this crew missed the write up? Or do you mean they disabled it "just in case"?
It's been a couple years since I flew the 737 but I'm 99.5% sure that would disable MCAS........ but also the pilots' electric trim and autopilot leaving you with only the obnoxious wheel. I have a hard time believing they would go through all that or if the airline's SOP would even allow that
3: then you say the mishap crew perhaps "missed" that the stab cutoff switches were off? Did they miss the write up that undoubtedly would have existed? Did they also just overlook these switches being set incorrectly in their cockpit flows/checklists? Did they also not set takeoff trim in the green band, something you also hit in the checklist before every flight or was it already coincidentally in the green band?
Or "they knew it was off," I'd be surprised if ET lets their pilots takeoff with these switches tripped or the pilots did it on their own accord, could be wrong but that does not sound right at all.
On top of all that, all that stuff that would draw their attention to trim, they fail to set it correctly? It's not some complex equation or something rarely done, you get the trim calculated out every single flight and it should fall in the green band
I'm not saying all that is impossible but it doesn't pass the sniff test. I'd say you should go back to the drawing board... but why? Why over speculate and come up with an answer? There are way too many unknowns, I as a former 737 pilot wouldn't feel comfortable speculating off the very little info we have, why can't we just say "we don't know" and wait for more info?
The speculation doesn't help much and makes us all talk in circles. The level of certainty you exhibited makes it even worse
But maybe I misunderstood your points or you have a lot more expertise in the area, maybe ET does things a lot differently than I'd imagine (if what you outlined is the case I'd say they're extremely incompetent)
mcdu wrote:Interested wrote:The exact same plane that isn't safe to fly now wasn't safe to fly in October when it first crashed. Boeing became aware it wasn't safe in November at the latest. If not before.
Not safe to fly with 200 hour pilots. But any transport jet is unsafe with a 200 hour pilot.
Finn350 wrote:Based on the current information, the defective AoA vane is definitely a contributing factor.
smartplane wrote:estorilm wrote:For 50 years, normal stall recovery procedures were perfectly adequate on prior aircraft, even when it came time to certify the NG. For some reason, that's not the case with the MAX. It's not really a "feature" Boeing added as an upgrade with the new plane or something - it's a requirement for certification.
It's a feature Boeing added to perpetuate grandfathering. It is a requirement for certification, in order to mimic, within approved tolerances, the flight behaviour of the NG.
The MAX, within approved tolerances mimics the NG. The NG, within tolerances mimics the Classic. The Classic, within approved tolerances, mimics the 100/200. But the ultimate parent is the 100/200, which after applying multiple layers of tolerances, bears little or no resemblance to the flight behaviour of the MAX, even with electronic cloaking to make it seem so.
hivue wrote:trnswrld wrote:danj555 wrote:Couldn't the pilots in any case of malfunction just turn off all electronic bs? Like you're a pilot. You know how to fly a plane. You have flown thousands of take-offs. You know the right speed, right angle, right altitude. You know how to do it without electronic interference if need be.
So why not hit the kill switch if the computer is having a fit?
I asked this exact question many pages ago. It got pretty much no response. Big problems in IMC is one thing, but to not be able to fly an airplane in clear blue VMC daylight conditions just baffles me....computer issues or not. How does this happen? Look out the window.....fly the airplane FIRST, then figure what the heck is going on. I know easier said than done.
Killing all computers operating on an airplane would have the same effect as killing all computer chips that are operating in your car while you're driving (assuming you are not driving a Stone Age car).
gensys wrote:JohnKrist wrote:What worries me is all those who keep saying ”a pilot not knowing about this issue has been in a cave for 4 months”, ”it’s a training issue”, ”it’s because the F/o had 200 hours” etc. A plane should not fly itself into the ground, switch flicked off or not.
Such as AF 447 doing so from all the way up at cruise altitude?
anfromme wrote:From there on, the main input by the crew was to pitch up, even though the stall warning was sounding all the way through.
.
CO953 wrote:smartplane wrote:estorilm wrote:For 50 years, normal stall recovery procedures were perfectly adequate on prior aircraft, even when it came time to certify the NG. For some reason, that's not the case with the MAX. It's not really a "feature" Boeing added as an upgrade with the new plane or something - it's a requirement for certification.
It's a feature Boeing added to perpetuate grandfathering. It is a requirement for certification, in order to mimic, within approved tolerances, the flight behaviour of the NG.
The MAX, within approved tolerances mimics the NG. The NG, within tolerances mimics the Classic. The Classic, within approved tolerances, mimics the 100/200. But the ultimate parent is the 100/200, which after applying multiple layers of tolerances, bears little or no resemblance to the flight behaviour of the MAX, even with electronic cloaking to make it seem so.
What you're describing is the logical endpoint of a once-vibrant American (and global) aircraft-manufacturing industry which narrowed itself, at least in the Western world, to a duopoly and - in the USA - a monopoly. Monopolies create certain efficiencies but also certain dangers. The freight train of the MAX program carried a lot of momentum. It still does. Dang good chance that a flawed aircraft, which may actually not be fixable, still gets rammed down everyone's throats, instead of actually killing the program.
I have no animus to Boeing at all. Great company, with huge historical success and legendary contribution to aviation. Boeing may be the only company that can survive flat-out scrapping an aircraft type.
Before I get crowd-attacked, let me ask this:
Can the landing gear be made longer to accommodate moving the engines backward and eliminate the drag issue underlying this whole fiasco? I don't think so, due to width of the fuselage and the spacing of the engine pylons.
Can a telescoping landing gear be designed that would accommodate the width of the fuselage and the spacing of the engine pylons.... maaaaaaaaaaaaybe.
Can the airliner be made as safe as the NG in its current configuration, even with software fixes? ......... hmmmmm
Is this fair to the pilots and crew, not to mention the traveling public, as we get forced to fly the MAX for the next 25 years? .......hmmmmmmm
Does an entire globe-full of airlines keep up 5,000 orders for a plane that strongly appears to be a safety retrogression? In our current political state of "no rules" and disrespect for the rule of law .... ????????
This is a very ugly moment, for sure.
JohnKrist wrote:A plane should not fly itself into the ground, switch flicked off or not.
JohnKrist wrote:dragon6172 wrote:JohnKrist wrote:Well, this plane wasn’t really unsupervised, was it?
Neither was AF447
Point being?
XT6Wagon wrote:anfromme wrote:From there on, the main input by the crew was to pitch up, even though the stall warning was sounding all the way through.
.
No, the stall warning would shut off at high angles of attack. It would turn on as the nose dropped and the plane could measure airspeed again. So pulling up turned *OFF* the stall warning.
DeltaMD90 wrote:Way too much speculation going on from people without the proper expertise and hard facts from scene. Why can't we say "we don't know at this point??osiris30 wrote:As time has gone on I have continued to flesh out what *I* feel the chain of events is and to my mind now it starts before the take-off roll:
1) Either on prior flight or before commencing this flight; pilots of last flight or this flight disable MCAS as a precatuion (stab cut-off)
2) PIlots of this flight miss (or knew it was off), but fail to trim plane correctly.
What is your background? Are you in the airlines and/or a Boeing pilot? Granted I have not worked for the airlines, and I am not currently a MAX pilot (but I did fly 737-800s for a few years) and I have a VERY hard time believing what you are so sure or here
1: the previous pilots that supposedly got this malfunction and threw off the stab switches didn't relay this info to maintenance and/or maintenance didn't relay this info to the pilots/it wasn't seen in the write ups?
2: what do you mean "disable MCAS as a precaution?" As in they had flight control problems or uncommanded nose drops and switched the stab cutoff switches? That would make it even more unbelievable they simply forgot to tell maintenance/maintenance didn't immediately ground the plane/didn't tell this crew/this crew missed the write up? Or do you mean they disabled it "just in case"?
It's been a couple years since I flew the 737 but I'm 99.5% sure that would disable MCAS........ but also the pilots' electric trim and autopilot leaving you with only the obnoxious wheel. I have a hard time believing they would go through all that or if the airline's SOP would even allow that
3: then you say the mishap crew perhaps "missed" that the stab cutoff switches were off? Did they miss the write up that undoubtedly would have existed? Did they also just overlook these switches being set incorrectly in their cockpit flows/checklists? Did they also not set takeoff trim in the green band, something you also hit in the checklist before every flight or was it already coincidentally in the green band?
Or "they knew it was off," I'd be surprised if ET lets their pilots takeoff with these switches tripped or the pilots did it on their own accord, could be wrong but that does not sound right at all.
On top of all that, all that stuff that would draw their attention to trim, they fail to set it correctly? It's not some complex equation or something rarely done, you get the trim calculated out every single flight and it should fall in the green band
I'm not saying all that is impossible but it doesn't pass the sniff test. I'd say you should go back to the drawing board... but why? Why over speculate and come up with an answer? There are way too many unknowns, I as a former 737 pilot wouldn't feel comfortable speculating off the very little info we have, why can't we just say "we don't know" and wait for more info?
The speculation doesn't help much and makes us all talk in circles. The level of certainty you exhibited makes it even worse
But maybe I misunderstood your points or you have a lot more expertise in the area, maybe ET does things a lot differently than I'd imagine (if what you outlined is the case I'd say they're extremely incompetent)
kayik wrote:...
It is not going to be like "we upgraded the software, let's fly". Certification will take ages. Given its credibility, FAA's decision is not enough, European authorities and Asians should be convinced, as well.
.
Wallhart wrote:This isnt a minor issue, this is something that was so obvious that if there was a fault etc it could put the plane in danger that you have to ask how the hell did this not come up in risk assessment.
747megatop wrote:It is as simple as Mercedes, BMW or Toyota putting in a feature where, it accelerates the car when you hit the brake pedal and people arguing that the driver did not have enough experience or should have flipped some switches to disconnect that feature!!!!
dtw2hyd wrote:kayik wrote:...
It is not going to be like "we upgraded the software, let's fly". Certification will take ages. Given its credibility, FAA's decision is not enough, European authorities and Asians should be convinced, as well.
.
They have been working on software fix since Nov '18. Boeing Defense Systems has vast experience with software to control airframes lacking static stability. Most modern fighter planes are inherently unstable for various reasons. So it is not impossible with just software fix for Boeing. Just tighten the loose ends and make it more intuitive to human pilots.
I think any reasonable fix will be quickly accepted and frames should flying again very soon. No one wants (or) can afford to keep these grounded for a long time.
There will be a judgment call on the cost of major MAX redesign (vs) clean sheet design. If the redesign costs too much Boeing may roll out the new plane and let customers swap orders.
dtw2hyd wrote:kayik wrote:...
It is not going to be like "we upgraded the software, let's fly". Certification will take ages. Given its credibility, FAA's decision is not enough, European authorities and Asians should be convinced, as well.
.
They have been working on software fix since Nov '18. Boeing Defense Systems has vast experience with software to control airframes lacking static stability. Most modern fighter planes are inherently unstable for various reasons. So it is not impossible with just software fix for Boeing. Just tighten the loose ends and make it more intuitive to human pilots.
I think any reasonable fix will be quickly accepted and frames should flying again very soon. No one wants (or) can afford to keep these grounded for a long time.
There will be a judgment call on the cost of major MAX redesign (vs) clean sheet design. If the redesign costs too much Boeing may roll out the new plane and let customers swap orders.
Interflug74 wrote:Why not putting an 200hrs pilot on an already safe Plane, that was made even safer?
osiris30 wrote:1&2) disabled as a precaution. Not saying it happened but the plane sure looks mistrimmed based on the take off roll AND inability to climb.
3) Yes. I am suggesting that MAY have happened. Pilots have taken off in all kinds of incorrect configurations before. I am not saying this happened, but it wouldn't be without precident would it?
I am at a loss to explain take off performance unless the aircraft was out of trim. Given the airspeed the got up to on the data we have that thing should have been able to climb like a rocket.
dtw2hyd wrote:...Boeing Defense Systems has vast experience with software to control airframes lacking static stability. Most modern fighter planes are inherently unstable for various reasons. So it is not impossible with just software fix for Boeing. Just tighten the loose ends and make it more intuitive to human pilots...
Finn350 wrote:CO953 wrote:smartplane wrote:It's a feature Boeing added to perpetuate grandfathering. It is a requirement for certification, in order to mimic, within approved tolerances, the flight behaviour of the NG.
The MAX, within approved tolerances mimics the NG. The NG, within tolerances mimics the Classic. The Classic, within approved tolerances, mimics the 100/200. But the ultimate parent is the 100/200, which after applying multiple layers of tolerances, bears little or no resemblance to the flight behaviour of the MAX, even with electronic cloaking to make it seem so.
What you're describing is the logical endpoint of a once-vibrant American (and global) aircraft-manufacturing industry which narrowed itself, at least in the Western world, to a duopoly and - in the USA - a monopoly. Monopolies create certain efficiencies but also certain dangers. The freight train of the MAX program carried a lot of momentum. It still does. Dang good chance that a flawed aircraft, which may actually not be fixable, still gets rammed down everyone's throats, instead of actually killing the program.
I have no animus to Boeing at all. Great company, with huge historical success and legendary contribution to aviation. Boeing may be the only company that can survive flat-out scrapping an aircraft type.
Before I get crowd-attacked, let me ask this:
Can the landing gear be made longer to accommodate moving the engines backward and eliminate the drag issue underlying this whole fiasco? I don't think so, due to width of the fuselage and the spacing of the engine pylons.
Can a telescoping landing gear be designed that would accommodate the width of the fuselage and the spacing of the engine pylons.... maaaaaaaaaaaaybe.
Can the airliner be made as safe as the NG in its current configuration, even with software fixes? ......... hmmmmm
Is this fair to the pilots and crew, not to mention the traveling public, as we get forced to fly the MAX for the next 25 years? .......hmmmmmmm
Does an entire globe-full of airlines keep up 5,000 orders for a plane that strongly appears to be a safety retrogression? In our current political state of "no rules" and disrespect for the rule of law .... ????????
This is a very ugly moment, for sure.
In the short term, there will be a simple software fix to address the specific MCAS design fault. In the long term, Boeing will replace the 737 with a new clean sheet design. They had been contemplating that already before this debacle, and this is the final push for earnestly starting design work for a clean sheet. There is no point to make additional changes to the 737 frame (it would be adding lipstick over lipstick as some members here call it). Irony here is that as a consequence of these mishaps, A320neo will get a potent rival from Boeing.
DeltaMD90 wrote:osiris30 wrote:1&2) disabled as a precaution. Not saying it happened but the plane sure looks mistrimmed based on the take off roll AND inability to climb.
3) Yes. I am suggesting that MAY have happened. Pilots have taken off in all kinds of incorrect configurations before. I am not saying this happened, but it wouldn't be without precident would it?
I am at a loss to explain take off performance unless the aircraft was out of trim. Given the airspeed the got up to on the data we have that thing should have been able to climb like a rocket.
Disabled as a precaution? By the airline? By the pilots? That sounds like a completely unrealistic solution. Again, you'd have a plane without autopilot and without electric trim. I'd be absolutely shocked if ET allowed this or the pilots thought that was a good idea. In fact, if ET went to such lengths, they probably wouldn't have even bothered to fly them in the first place and just grounded them right off the bat. This makes no sense
You seem to be connecting a lot of dots really early on. There may be 20 different things that happened, and that's assuming [u]we have no inaccurate information currently.[u]
And yes, pilots have taken off in incorrect configurations before. Trust me, a slightly untrimmed 737 isn't going go bonkers when you lift off. It may cause you to rotate a bit too fast or require more back stick pressure, but it's not like it would be completely uncontrollable. It gets harder and harder the further you get from the green band for takeoff... But what are you suggesting? In addition to not knowing about a gripe on a previous flight, and in addition to them overlooking these switches/wanting them off for some crazy reason, and in addition to them being out of the green band for takeoff, it was trimmed to full nose forward or back or something? Which again, that alone would be annoying and more difficult (but not impossible to control)
Think you're way off the mark here. A lot of stuff isn't making sense, let's just stick to what we know (and can confirm btw! Perhaps some of the FR24 info or something else is a bit off or faulty) and not connect dots for the sake of connecting dots
Further more I want everyone to just remember it's possible to fly these aircraft out of trim and even without hydraulics. While I never had that in real life (thankfully) I practiced it in the sim. I wouldn't be surprised if confusion or disorientation came into play and I don't know about the MAX (only the NG) but trim alone shouldn't be able to overpower the pilots (can fight or disorient though)
osiris30 wrote:
I was pretty clear in my initial post that I am proposing the trim cut off switches were thrown by either the last crew or this crew as a precaution. Who the hell said anything about disabling auto-pilot? Just auto-trim... Not sure where you are getting this from, did I misword something in my post that has lead you to suggest they turned off the entire AP system? I am merely suggesting someone hit stab cut-off. Before you say 'wow that would be so weird I have never heard of it', there was a report in the Nasa database of an AA flight crew doing EXACTLY that, for EXACTLY this reason. (edit: I may be getting the soources or airlines mixed, but it was reported in this thread already, just not going to search for it).
speedking wrote:Hmm.. You are flying at 2000ft with 400kts. Stick shaker on. Screens lit like a Christmas tree.
MCAS kicks in, plane starts to drop. Column too heavy to hold back with two hands.
Now you need to troubleshoot, make a decision to switch off the trim, take one hand off from the column, reach behind to switch the trim off, start manually rotating the trim while flying with one hand with a column too heavy to hold back.
Is this physically possible? How much time one would have for this before...Boom!
How fast does a plane drop 2000ft if it is flying at 400kts and you push it down?
flybucky wrote:I updated my chart based on the FR24 data:
[list]
[*]Started plotting earlier at the begin of takeoff roll instead of when FR24 indicated "airborne". I am doubtful FR24's "airborne" is accurate since the ground speed was only 93 knots, and the plane was only 1900 ft from threshold, only 15% of the runway length. The runway does rise in the middle.