PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   Rumours & News (https://www.pprune.org/rumours-news-13/)
-   -   Ethiopian airliner down in Africa (https://www.pprune.org/rumours-news/619272-ethiopian-airliner-down-africa.html)

OldnGrounded 18th Mar 2019 17:24


Originally Posted by Sailvi767 (Post 10422717)
They had a much easier choice, comply with the QRH for runaway trim . . .

Except that MCAS activation doesn't present as runaway trim (not continuous and can be briefly interrupted by operation of column trim switches), so it wasn't recognized by at least two crews. Then there's the problem of trimming manually, perhaps from full nose-down, at high speed and low altitude, while trying to fly the airplane -- with any number of other distractions bombarding the senses and causing distraction and confusion.

This has been discussed exhaustively and compellingly in these threads, but some still insist that the problem is pilot error. I suppose it's OK for individual pilots to think that way, but, when engineers, manufacturers, regulatory authorities, etc. do, the result is all too likely to be catastrophic loss.




M2dude 18th Mar 2019 17:53


Originally Posted by FGD135 (Post 10422018)
Quite commonplace, really, for critical airborne systems to use only one sensor, and only raw data at that. Examples:

Turkish Airlines flight 1951, 25 Feb, 2009. B737-800 where one radar altimeter was malfunctioning. The data from the sensor went to zero, the computers thought the plane was on the ground, so they reduced the engine power to idle. The result was a stall at low altitude where many occupants were killed. The idiotic thing was that not only were the computers using just one radar altimeter sensor, they were making no effort to inspect it for reasonableness or filter it against spikes. The data was showing valid heights but then instantly started showing zeros!

Qantas flight 72, 7 Oct, 2008. Airbus A330. Pilot's side air data computer had a momentary spike in the angle of attack data. Silly computers took this as indicating the aircraft was suddenly stalling, and at a speed of about 450 knots, pushed the nose down. Passengers were thrown into the ceiling and many were seriously injured. The idiotic thing was that the computers were using completely raw data and could therefore believe that the angle of attack could, in the space of one second, change from sensible values to a stalling angle. Also idiotic that the computers would happily perform a manouever of such violence.

Well I've only been an aviation professional for 52 years, so what do I know. :) Seriously though, the Turkish Airlines case illustrated poor failure monitoring within the RADALT (Not to MENTION complete crew unawareness and monitoring) of IAS. RAD ALT inputs to AFCS typically is used for gain gearing and throttle retard and usually have good self monitoring (But not in this case of course).
The QANTAS A330 case has yet to be completely and adequately explained ADIRU fault, the suspect was a data labelling issue. (GREAT airmanship by the QANTAS crew however). The ADIRU functions certainly are monitored and compared.
For ANY flight control system, ALPHA as well as Ps & Pt inputs are invariably monitored.. The absence of an Alpha disagree function of MCAS is at the very best negligent to the extreme, as has been the whole frantically rushed throwing together of this appalling system. Pilots and passengers deserve FAR better than this.

flyingchanges 18th Mar 2019 18:06

How many times does it have to do the same thing before you consider it to be continuously doing something you do not want. My number would be 2.

fgrieu 18th Mar 2019 18:11

The Seattle Times runs an article with some bold claims, including that factual errors have crept in the certification process, and where raised to the attention of Boeing and FAA days before the ET302 crash. It is not paywalled where I stand.

silverstrata 18th Mar 2019 18:16


Originally Posted by flyingchanges (Post 10422549)
It is runaway stab trim...
Maybe not all at once, but if it is not doing what you want, then it is out of control.

Clearly MCAS is not a runnaway trim condition, otherwise we would be reaching for the cut-out switches every time the speed-trim operated. I think some people here do not realise that the trimmer doing its own thing is operations normal.

And the auro-trim systems are always mis-trimming the aircraft (the trim inputs by the speed-trim system are always wrong, and you always have to re-trim manually). So at what point does ‘operations normal’ become ‘operations abnormal’? At what point do you assume that the trimmer has gone awry..??

Silver

abdunbar 18th Mar 2019 18:33


Originally Posted by DaveReidUK (Post 10422187)
Interesting graphic.

The altitude spike where the aircraft dips below the runway surface(!) accompanied by a single, instantaneous 2000+ fpm ROC value is clearly an artifact (unless Newton got it all wrong), probably coinciding with rotation.

There is a similar, spurious altitude spike towards the RH edge of the plot, which you have wisely ignored - that one is easier to account for because a distance-vs-time plot shows the aircraft flying backwards at that point (i.e. it's a timestamp anomaly rather than bad ADS-B data).

In addition to often mentioned lack of fidelity in the ads-b info available on the internet. It is normal to see a VSI indication dip slightly at rotation. well, it used to be, not familiar with the most recent 15 years of aircraft development.

dufc 18th Mar 2019 18:37

Any reason there is not a warning light on the 737 MAX to indicate MCAS has activated?

Chesty Morgan 18th Mar 2019 18:38


Originally Posted by flyingchanges (Post 10422771)
How many times does it have to do the same thing before you consider it to be continuously doing something you do not want. My number would be 2.

Ever flown a 737?

Organfreak 18th Mar 2019 18:41


Originally Posted by dufc (Post 10422805)
Any reason there is not a warning light on the 737 MAX to indicate MCAS has activated?

I can think of one reason: It was meant to be a secret! :*

gearlever 18th Mar 2019 18:41


Originally Posted by silverstrata (Post 10422776)


Clearly MCAS is not a runnaway trim condition, otherwise we would be reaching for the cut-out switches every time the speed-trim operated. I think some people here do not realise that the trimmer doing its own thing is operations normal.

And the auro-trim systems are always mis-trimming the aircraft (the trim inputs by the speed-trim system are always wrong, and you always have to re-trim manually). So at what point does ‘operations normal’ become ‘operations abnormal’? At what point do you assume that the trimmer has gone awry..??

Silver

Thx Silver for clearification:ok:

Nomad2 18th Mar 2019 18:46

The single most powerful control surface on a transport jet is the THS.
Why Boeing would give control of it to a subsystem, like the MCAS is hard to understand.

No amount of hauling (or pushing) on the elevator is going to save you if the THS isn't where it should be.

abdunbar 18th Mar 2019 18:48

Does anyone know? If you have a 737 Max , airborne, flaps up, really high speed, full nose down trim, electric stabilizer trimming motors shut off, how much back pressure does it take to raise the nose with the elevator? While applying this large force to the elevator, how much force is required to turn the stabilizer trim hand wheel? How many turns of the hand wheel per degree of stabilizer trim. In other words, is it possible to get into a position in which it is impossible to recover, not enough elevator authority due to force required and or inability to retrim the stabilizer manually due to it binding from a combination of speed and forces being applied through the elevator.

Nomad2 18th Mar 2019 18:56

You have to put the THS back where it should be.
Until then, you remain in upset territory, or 'in the ****' as most pilots call it.

Ian W 18th Mar 2019 18:57


Originally Posted by abdunbar (Post 10422817)
Does anyone know? If you have a 737 Max , airborne, flaps up, really high speed, full nose down trim, electric stabilizer trimming motors shut off, how much back pressure does it take to raise the nose with the elevator? While applying this large force to the elevator, how much force is required to turn the stabilizer trim hand wheel? How many turns of the hand wheel per degree of stabilizer trim. In other words, is it possible to get into a position in which it is impossible to recover, not enough elevator authority due to force required and or inability to retrim the stabilizer manually due to it binding from a combination of speed and forces being applied through the elevator.

As FCEng says in post #1946 you cannot overcome the StabTrim with elevator at high speed.

dozing4dollars 18th Mar 2019 19:05


Originally Posted by silverstrata (Post 10422776)


Clearly MCAS is not a runnaway trim condition, otherwise we would be reaching for the cut-out switches every time the speed-trim operated. I think some people here do not realise that the trimmer doing its own thing is operations normal.

And the auro-trim systems are always mis-trimming the aircraft (the trim inputs by the speed-trim system are always wrong, and you always have to re-trim manually). So at what point does ‘operations normal’ become ‘operations abnormal’? At what point do you assume that the trimmer has gone awry..??

Silver

I haven’t flown a 73 but on the 72 (if I recall correctly) during a runaway, the first instinctual response was to apose the runaway with opposite elevator. This ingaged the trim brake. The noise of the brake verses the runaway trim was a giveaway to use the cutout switches.

I don’t think this would happen as the MCAS does not activate the brake. All that sim training on runaway stab wouldn’t help because it’s not a runaway.

The stall horn and stick shaker would make pulling back and trimming nose up counter to all training that a pilot receives from initial stall recovery in a Cessna with a stall horn through to transport aircraft.

Two responses to two different stimulus. One Stall Recovery and one Unreliable Airspeed mask the third undocumented MCAS.

To learn anything from any accident you need to have empathy for those involved. Not just the pilots but the line mechanics, Boeing and FAA engineers. The true villains, senior management, board members and yes, even politicians will never be held accountable

The USA government shutdown that both political parties participated in was also a factor.

... and hence, the voters like you

abdunbar 18th Mar 2019 19:12


Originally Posted by dozing4dollars (Post 10422831)


I haven’t flown a 73 but on the 72 (if I recall correctly) during a runaway, the first instinctual response was to apose the runaway with opposite elevator. This ingaged the trim brake. The noise of the brake verses the runaway trim was a giveaway to use the cutout switches.

I don’t think this would happen as the MCAS does not activate the brake. All that sim training on runaway stab wouldn’t help because it’s not a runaway.

The stall horn and stick shaker would make pulling back and trimming nose up counter to all training that a pilot receives from initial stall recovery in a Cessna with a stall horn through to transport aircraft.

Two responses to two different stimulus. One Stall Recovery and one Unreliable Airspeed mask the third undocumented MCAS.

To learn anything from any accident you need to have empathy for those involved. Not just the pilots but the line mechanics, Boeing and FAA engineers. The true villains, senior management, board members and yes, even politicians will never be held accountable

The USA government shutdown that both political parties participated in was also a factor.

... and hence, the voters like you


I understand all that, and yes, I vaguely remember the trim brake. but the question is still this. Is there a conceiveable way to load the stabilizer to the point that it cannot manually be trimmed back to a point were elevators will work again?

Azgalor 18th Mar 2019 19:17

I know it may look a bit stupid but I need to clarify that. I would like if someone who flies 737 could reply.
Why Boeing put MCAS to MAX? As I understood there was problem with pitch moment created by engines at some occasions. But is it possible to fly without it and it will be just difficult or it is impossible to handle the aircraft without MCAS? I though it is there just to be safer and easier for pilots but I have read many strange things about that. But I think that is just mess made up by media.

megapete 18th Mar 2019 19:18


Originally Posted by abdunbar (Post 10422837)
I understand all that, and yes, I vaguely remember the trim brake. but the question is still this. Is there a conceiveable way to load the stabilizer to the point that it cannot manually be trimmed back to a point were elevators will work again?

I also wonder if the forward position of the engines, which gives a pitch up moment at high angles of attack, and led to the addiction of MCAS, could possibly give a pitch down moment at low angles of attack?

FCeng84 18th Mar 2019 19:19


Originally Posted by abdunbar (Post 10422817)
Does anyone know? If you have a 737 Max , airborne, flaps up, really high speed, full nose down trim, electric stabilizer trimming motors shut off, how much back pressure does it take to raise the nose with the elevator? While applying this large force to the elevator, how much force is required to turn the stabilizer trim hand wheel? How many turns of the hand wheel per degree of stabilizer trim. In other words, is it possible to get into a position in which it is impossible to recover, not enough elevator authority due to force required and or inability to retrim the stabilizer manually due to it binding from a combination of speed and forces being applied through the elevator.

I cannot speak to the potential for binding of the horizontal stabilizer control (either via electric motor or via manual turn of mechanical trim wheel) but I can shed some light on the first question. Where the stabilizer needs to be for trim is a function of all of the contributors to pitching moments that must be balanced. CG is the biggest factor and will have the most influence on where the stabilizer sits for trim(i.e., no column push or pull required for steady flight). How "out of trim" the airplane is with the stabilizer moved all the way to its airplane nose down limit depends on where you start (i.e., what position represents "in trim"). If the CG is at its forward limit, trim will involve a fair amount of airplane nose up stabilizer so there will be a larger increment of stabilizer travel from there to the nose down limit. If the CG is at is aft limit, trim will place the stabilizer much closer to the airplane nose down limit so the increment from there to full nose down will be smaller.

Also with regard to your reference to "very high speed" specifics make a difference as Mach effects come into play along with dynamic pressure. At cruise speeds and faster elevator travel is limited by actuator force capability. The faster you go the less the elevator can be deflected and thus the more critical it is to have the horizontal stabilizer near its trim position.

FullWings 18th Mar 2019 19:20


Clearly MCAS is not a runnaway trim condition, otherwise we would be reaching for the cut-out switches every time the speed-trim operated. I think some people here do not realise that the trimmer doing its own thing is operations normal.

And the auro-trim systems are always mis-trimming the aircraft (the trim inputs by the speed-trim system are always wrong, and you always have to re-trim manually). So at what point does ‘operations normal’ become ‘operations abnormal’? At what point do you assume that the trimmer has gone awry..??

Silver
DING DING DING We have a winner!

That’s one of the biggest elephants (gorillas?) in the room. By the time you’ve thought “hmm, that’s not quite right” at low-level the situation has gone from nuisance to critical. The 737 trim is on the move all the time, be it from pilot inputs or STS/MCAS/Autopilot. Clickety-clack is the most heard noise on a 737 flight deck as the trim wheel spins it’s merry way backwards and forwards. Add an unreliable airspeed scenario to the above and no wonder things go from bad to worse. I really feel sorry for the crews who were dumped in this situation. :(


All times are GMT. The time now is 06:49.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.