Originally Posted by Notanatp
(Post 10553498)
The climb was arrested when flaps retracted. The climb was shallow to begin with. Look at the Reuters graphics comparing the ET302 accident flight climb profile with other flights leaving Addis Ababa and with the Lion Air 610. (Google "graphics reuters Ethiopia-airplane") The graphic shows that one other flight out of Addis Ababa had a similarly shallow departure climb and had to go around the east side of the mountain to the southeast.
Also, it looks to me like they pitched up was pretty high immediately after wheels off and then the PF forced the nose down with forward control column pressure. As I have commented previously, I believe ET302 was over Regulated Take Off Weight. The Preliminary Report says they were below RTOW, but if you look at the weight and balance information, they assumed around 167 lbs./pax, INCLUDING carry-on bags. If you use 190 lbs./pax, they were over by around 2,000 lbs. And if that's correct, then the reason appears to be that they were ferrying fuel (to save money by not paying for it in Nairobi?). Perhaps this was standard EA practice and explains the shallow climb of one of the other flights shown in the Reuters graphic. If they were overweight, and it affected take-off and initial climb performance, then that might explain why the crew failed to retard the throttles, even after the overspeed clackers started going off at 05:41:20 and 05:41:32. In any event, the time required to respond to activation of MCAS, or recognition of any stab trim abnormality, appears to be irrelevant to both JT610 and ET302. Both crews may have been startled initially, but both crews maintained control of their aircraft for minutes, not seconds, and any initial delay in recognizing that there was a stab trim problem wasn't what caused the loss of the airplanes. |
airlaw question : If the American FAA certified the B737-MAX but say Canada,EASA, Mexico didn't, could a MAX operate into those territories to/from the US? How about overflights?
G |
Originally Posted by groundbum
(Post 10553655)
airlaw question : If the American FAA certified the B737-MAX but say Canada,EASA, Mexico didn't, could a MAX operate into those territories from/from the US? How about overflights?
G So I expect it would be just USA (airspace) domestic restricted. It would also put FAA in a class of it's own - new type certifications will be a very long process in every other country forevermore. It has been a long path since the moon landing 50 years ago, not all steps since have been forward ones. |
Regarding over RTOW: Its not a PA-32, its a jet. 2 tonnes over is 1.5% more mass and not significant on two engines. At all. Re air law. Historically regulators accept country of origin certification. I can’t recall a type for which approval was withheld by a regulator apart from some ex Soviet types. I think if approval were to be specifically withheld then overflights would be disallowed. I guess we just might see what happens if the Trump/China foolishness gets anymore out of hand. |
Originally Posted by MurphyWasRight
(Post 10552439)
One can hope that the Lion air and Ethiopian investigators did such testing early on before it became widely known and discussed.
In fact the Ethiopian accident suggests that the crew was not fully aware and ready to pounce on MCAS, although in that case partial knowledge may have been deadly if it led to disabling electric trim before achieving neutral trim. |
I can’t recall a type for which approval was withheld by a regulator apart from some ex Soviet types. Boeing fitted a larger fin and rudder in consequence. |
Originally Posted by GlueBall
(Post 10553687)
Without having to THINK, an experienced captain with sufficient manual flying skills would not need to know if MCAS, ordinary runaway stab trim or ambiguous autopilot stab trim inputs were causing the uncommanded nose-down trim. Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand and simultaneously ordering the F/O to cut off the electric stab trim switches, or doing that by himself, while simultaneously clicking off the A/P and A/T.
If that simple, the fix was months ago - not still in the waiting or the need to think! The problem is bigger than an experienced captain. |
Originally Posted by GlueBall
(Post 10553687)
Without having to THINK, an experienced captain with sufficient manual flying skills would not need to know if MCAS, ordinary runaway stab trim or ambiguous autopilot stab trim inputs were causing the uncommanded nose-down trim. Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand and simultaneously ordering the F/O to cut off the electric stab trim switches, or doing that by himself, while simultaneously clicking off the A/P and A/T.
You are a perfect example of an armchair expert, now you know all the facts, with 20:20 hindsight. And dare I say it, quite likely with a strong vested interest. How very convenient to come on here and be the expert about what they all should have done. |
Originally Posted by GlueBall
(Post 10553687)
Without having to THINK, an experienced captain with sufficient manual flying skills would not need to know if MCAS, ordinary runaway stab trim or ambiguous autopilot stab trim inputs were causing the uncommanded nose-down trim. Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand and simultaneously ordering the F/O to cut off the electric stab trim switches, or doing that by himself, while simultaneously clicking off the A/P and A/T.
The above does not mention the need to first get the aircraft in trim -before- cut off of electric trim which appears to be the fatal action by Ethiopian crew. Although not confirmed yet it appears that they were unable to use the manual trim wheel once they activated the cutouts. Not trying to re-open a long running discussion just pointing out that things are never as simple as one might hope. |
Originally Posted by GlueBall
(Post 10553687)
Without having to THINK, an experienced captain with sufficient manual flying skills would not need to know if MCAS, ordinary runaway stab trim or ambiguous autopilot stab trim inputs were causing the uncommanded nose-down trim. Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand and simultaneously ordering the F/O to cut off the electric stab trim switches, or doing that by himself, while simultaneously clicking off the A/P and A/T.
|
Originally Posted by GlueBall
(Post 10553687)
Without having to THINK, an experienced captain with sufficient manual flying skills would not need to know if MCAS, ordinary runaway stab trim or ambiguous autopilot stab trim inputs were causing the uncommanded nose-down trim. Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand and simultaneously ordering the F/O to cut off the electric stab trim switches, or doing that by himself, while simultaneously clicking off the A/P and A/T.
The stabilizer manual trim wheels rotate at a rapid rate when there is a runaway stab condition. I doubt a knee or hand would be able to hold the stab trim wheel. Moreover, there isn't really a sufficient gap between the pedastal and the wheels to get any grip on the wheel. Most certainly a pilot could get a severe hand injury in trying to hold the wheel, without using the handles which are folded into a section of the wheel (s). |
Originally Posted by GlueBall
(Post 10553687)
Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand...
|
Originally Posted by CurtainTwitcher
(Post 10553523)
Is 2000 lbs / 900kg over RTOW on two engines going to have a dramatic impact on the climb performance to the extent it is discernible in a newspaper graphic (Reuters link to graphics), especially given the scale? Single engine, yes, but that wasn't the scenario.
https://cimg2.ibsrv.net/gimg/pprune....83dc75cb58.png The Reuters graph is labeled "GROUND Altitude From Addis Ababa’s altitude of 7,625 feet" and they claim it's based on "altitude data from the flight, released by Flightradar24". It seems to suggest that the aircraft reached only about 500 feet AGL before MCAS activated, and it almost touched the ground as a result. Everything I've seen so far contradicts that. The FR24 data is the ADS-B reported pressure altitude, and needs to be corrected based on the actual pressure at the time of the flight, otherwise the graph will show the plane departed from 425 feed below ground level. If you do that, the FR24 data looks like this, quite different from the Reuters graph: https://cimg7.ibsrv.net/gimg/pprune....a1dde2215a.png I'm not sure if the ADS-B reported pressure is corrected based on the AOA and airspeed. If it is, then even my graph would not be accurate, showing lower altitudes, the actual altitude would be higher. On the DFDR traces from the preliminary report the computed left and right pressure altitudes diverge progressively, reaching more than 1000 feet difference as the speed increases. This could make even the altitude loss from my graph show as worse than it actually was. The aircraft could be at 1500 feet AGL, when ADS-B would show it at 500 feet AGL. In any case, it shows that at 05:40:00Z, when MCAS first activated, the aircraft was already descending. Finally, I scaled the altitude graph from the preliminary report, compressing the time axis 10 times, to get a scale factor more similar to the Reuters graph and my graph: https://cimg7.ibsrv.net/gimg/pprune....129fcd7216.png The blue trace is the corrected pressure altitude from the right side, with the functional AOA sensor, the red trace is from the left side, with the broken AOA sensor. Each vertical division is 1000 feet. The red trace seems to match the FR24 data, so it seems the ADS-B information was incorrectly adjusted due to the broken AOA sensor. According to the trace from the right side, with the functional AOA sensor, the aircraft actually reached about 1500 feet AGL before it started descending, and only lost about 250 feet of altitude, instead of 450 feet like the FR24 data shows. |
Originally Posted by GlueBall
(Post 10553687)
Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand . . .
|
Not a pilot here but a quick search reveals this - (acknowledgements to Youtube)
Only bit missing was an exclamation of 'just fly the darn plane' |
Originally Posted by GlueBall
(Post 10553687)
Without having to THINK, an experienced captain with sufficient manual flying skills would not need to know if MCAS, ordinary runaway stab trim or ambiguous autopilot stab trim inputs were causing the uncommanded nose-down trim. Such trim anomaly at low altitude would automatically trigger a self-preserving INSTINCTIVE response of stopping the trim-in-motion forward moving stabilizer wheel either with his knee, right thigh or right hand and simultaneously ordering the F/O to cut off the electric stab trim switches, or doing that by himself, while simultaneously clicking off the A/P and A/T.
|
Originally Posted by Takwis
(Post 10554033)
Actually, it's quite a bit more instinctive than that. And it doesn't involve any "Wild Alaska" maneuvering. All the Captain has to do is pull back on the yoke, and forward trim stops. The Control Column Cutout Switches stop "opposing trim inputs." This is true on every manual flight controlled Boeing since the "Dash-80". The pilots FRM for the MAX still says it is true for the MAX, even though it is not. Boeing removed a foundational, instinctive way for the pilot to over-ride undesirable trim trim inputs, put it under the control of some junior level automation programming, and didn't tell anyone.
|
I realized how confusing the situation would have been for the Ethiopian captain after working on my comment comparing the differences between the pressure altitudes computed on the left side and the right side.
The broken AOA indicator messed up the computed pressure altitude on the captain side so severely that it was showing the aircraft much lower than it actually was, more than 1000 feet lower as the speed increased, reaching almost 3000 feet difference during the final dive. At some point after the MCAS activation the aircraft was slightly climbing, but the captain pressure altitude was showing the aircraft as failing to climb, despite the increasing speed. Also the indicated airspeed was lower on the left side than on the right side by up to 25 knots. So overall the instruments were presenting to the captain a situation much worse than it actually was. It's not the same thing if you are at 1500 feet, you lose 250 feet of altitude, and then the aircraft slowly starts climbing, compared with what the captain was actually seeing: being at around 950 feet and losing 450 feet of altitude, then the aircraft not climbing at all, despite the increasing speed. With that in mind, even ignoring other factors, it becomes more understandable why the captain didn't reduce thrust. And I think determining quickly which side had the unreliable airspeed and altitude information, and using the information from the other side, is one thing that could have prevented the accident. |
Originally Posted by MemberBerry
(Post 10554081)
And I think determining quickly which side had the unreliable airspeed and altitude information, and using the information from the other side, is one thing that could have prevented the accident.
|
Meber Berry referring to the height the PF was seeing.
it becomes more understandable why the captain didn't reduce thrust. Re Takwis' post. You win the internet trophy for simplest explanation of this matter. This and that, followed by, but pulling back, MCAS wins. |
All times are GMT. The time now is 00:56. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.