Fresh setback for Boeing's 737 MAX

trader4@optonline.net wrote in news:513bbc83-4475-4460-90dd-
aaa4861b42af@googlegroups.com:

when there are
other measures being implemented to prevent MCAS from causing
runaway trim?

The software fix.. OK

THIS is additional system assistance.

Next you will say that is what got us where we are.
 
trader4@optonline.net wrote in news:513bbc83-4475-4460-90dd-
aaa4861b42af@googlegroups.com:

Once that is done, the Max should be no more likely
to experience runaway trim than any other 737.

You are truly stupid.
 
On 03/07/2019 00:58, DLUNU wrote:
Chris <xxx.syseng.yyy@gfsys.co.uk> wrote in news:qfe6u9$2ev$1
@gioia.aioe.org:

Perhaps, but in the case of both crashes, mcas forced the nose down
at low altitude, where there was not enough height for recovery by
the roller coaster method.

Roller coaster is not was not NEVER was a "method", ya dope. It is a
description of what was recovered from not the method of recovery.

No - he is right. The SOP for recovery where there is runaway trim that
is beyond the physical ability of the pilot to adjust manually is to fly
a specific curve to take most of the forces off the flight control
surfaces making them easier to move at the right time. eg.

http://www.b737.org.uk/runawaystab.htm#rc

The big problem is that you have to trade altitude and time for the
opportunity to use this method (which incidentally seems to have been
largely omitted from the modern manual). Altitude to spare was the one
crucial thing that a plane does not have shortly after take-off.

The Ethiopeans were the worst off in this respect since they were
already at 7000' and in thin air before they even left the ground.
It is an outcome of a control method (cockpit actuation) which has the
HUGE problem of being too slow, and the loading increases on ALL craft
experiencing such an issue.

The out of trim recovery procedure described as roller coaster was
developed on the 707 - it has been around for a long time.

Trouble is that even when Boeing thought they had fixed it the simulator
session demonstrated *another* independent critical trim failure.

--
Regards,
Martin Brown
 
On Wednesday, July 3, 2019 at 4:12:47 AM UTC-4, Martin Brown wrote:
On 03/07/2019 00:58, DLUNU wrote:
Chris <xxx.syseng.yyy@gfsys.co.uk> wrote in news:qfe6u9$2ev$1
@gioia.aioe.org:

Perhaps, but in the case of both crashes, mcas forced the nose down
at low altitude, where there was not enough height for recovery by
the roller coaster method.

Roller coaster is not was not NEVER was a "method", ya dope. It is a
description of what was recovered from not the method of recovery.

No - he is right. The SOP for recovery where there is runaway trim that
is beyond the physical ability of the pilot to adjust manually is to fly
a specific curve to take most of the forces off the flight control
surfaces making them easier to move at the right time. eg.

http://www.b737.org.uk/runawaystab.htm#rc

The big problem is that you have to trade altitude and time for the
opportunity to use this method (which incidentally seems to have been
largely omitted from the modern manual).

Agree with all and from what I've read you can leave out "largely". What I read, it's totally gone.


Altitude to spare was the one
crucial thing that a plane does not have shortly after take-off.

The Ethiopeans were the worst off in this respect since they were
already at 7000' and in thin air before they even left the ground.

It is an outcome of a control method (cockpit actuation) which has the
HUGE problem of being too slow, and the loading increases on ALL craft
experiencing such an issue.

The out of trim recovery procedure described as roller coaster was
developed on the 707 - it has been around for a long time.

Trouble is that even when Boeing thought they had fixed it the simulator
session demonstrated *another* independent critical trim failure.

--
Regards,
Martin Brown
 
trader4@optonline.net wrote in
news:32c2a04b-fd33-45e0-a272-cf0b9539e49c@googlegroups.com:


Agree with all and from what I've read you can leave out
"largely". What I read, it's totally gone.

Oh looky! This FAT ASSED loser DORK wannabe has so much time, he can
sit and read flight op manuals.

You a pilot, punk?
 
Martin Brown <'''newspam'''@nezumi.demon.co.uk> wrote in news:qfho1q
$1nh2$1@gioia.aioe.org:

The big problem is that you have to trade altitude and time for the
opportunity to use this method

The bigger problem is the reason you are using it is because of a non
timely control situation to start with and you are claiming to be able
to control it into those arcs.
 
On Thursday, July 4, 2019 at 6:29:07 AM UTC-4, DecadentLinux...@decadence.org wrote:
Martin Brown <'''newspam'''@nezumi.demon.co.uk> wrote in news:qfho1q
$1nh2$1@gioia.aioe.org:

The big problem is that you have to trade altitude and time for the
opportunity to use this method

The bigger problem is the reason you are using it is because of a non
timely control situation to start with and you are claiming to be able
to control it into those arcs.

Quite amusing that at the same time you posted the above,
you directed this at me:


"Oh looky! This FAT ASSED loser DORK wannabe has so much time, he can
sit and read flight op manuals.

You a pilot, punk? "


Oblivious to the obvious hypocrisy.
You're such a riot!

Insert cursing here.
 

Welcome to EDABoard.com

Sponsor

Back
Top