Indonesian aircraft missing off Jakarta
Ok, I did not know the Max has a new stall assistance system. As mentioned before, the STS normally trims down after take off, so it would be operating in the same manner as the new stall system. So again the tech log entry about STS appears incorrect.
And why did Boeing incorportate a stall assistance system that trims, instead of using a stick pusher? This seems to go against the normal rules for flying. You fly the aircraft with the control column, not the trimmer.
A stick-pusher acts on the control columm, to increase speed, and withdraws its influence instantaneously to allow you to recover from the dive. A stall trimmer will trim you down, but leave that nose-down pressure on and impede your recovery from the dive.
A stick pusher is flying the control column, in the normal manner; while a stall trimmer is flying the trimmer. Is this how the new stall system works? I cannot find details on-line.
Silver
On a normal flight you would expect the STS to trim ANU during acceleration as it is trying to keep the aircraft at the previous speed. The previous captain said the STS was trimming incorrectly, so different from normal, so AND. The MAX has a new MCAS system, that will trim AND if it senses a low speed situation. There were reports the AOA on the captain side was giving erroneous high AOA values, leading to stick shaker as well, if the MCAS used these faulty values it could have kept on trying to trim AND every time the pilots stopped using elevator trim (if the even tried to override the airplane trim inputs manually). This could have resulted in the stabilizer being full AND, and the elevators not having enough authority to keep the nose up. The aircraft trim input could be stopped by using the elevator trim or, more permanentely, by the cutout switches (apparently is has been confirmed this would stop the MCAS from trimming.
TLDR: I think the STS trim being wrong write up was "correct", because the STS will during acceleration trim ANU not AND.
Join Date: Jan 2015
Location: Jakarta
Posts: 10
Likes: 0
Received 0 Likes
on
0 Posts
Per twitter com/ jonostrower the 737 MAX MCAS system runs the stabilizer at 0.27 deg/sec regardless of speed/mach. The amount of nose down stab motion provided by MCAS is listed as "up to 2.5 degrees. MCAS uses the stab trim motors and is disabled via selecting stab cutout.
Last edited by LaissezPasser; 14th Nov 2018 at 04:24. Reason: grammar
The B737 FCOM states:
How does that differ from the operation of MCAS when approaching a stall? MCAS seems to be based on AOA while STS is based on IAS, but is there any other major difference, such as trim rate, duration, range of trim operation, etc? Would a pilot of a MAX aircraft who knew about MCAS handle the JT610 scenario any differently to one who did not?
As airspeed decreases towards stall speed, the speed trim system trims the stabilizer nose down and enables trim above stickshaker AOA. With this trim schedule the pilot must pull more aft column to stall the airplane.
Join Date: Jul 2014
Location: Harbour Master Place
Posts: 662
Likes: 0
Received 0 Likes
on
0 Posts
The B737 FCOM states:
How does that differ from the operation of MCAS when approaching a stall? MCAS seems to be based on AOA while STS is based on IAS, but is there any other major difference, such as trim rate, duration, range of trim operation, etc? Would a pilot of a MAX aircraft who knew about MCAS handle the JT610 scenario any differently to one who did not?
How does that differ from the operation of MCAS when approaching a stall? MCAS seems to be based on AOA while STS is based on IAS, but is there any other major difference, such as trim rate, duration, range of trim operation, etc? Would a pilot of a MAX aircraft who knew about MCAS handle the JT610 scenario any differently to one who did not?
Net result is actually very simple: Airspeed Unreliable NNC memory items, THEN stab trim cutoff switches.....CUTOFF
Originally Posted by JRBarrett
I’m still very curious as to why a system that is designed to automatically change the aircraft configuration without pilot input (via stab trim) would act based on the output data of only one of the two AOA probes. The stick pusher, which also activates based on AOA, requires both probes to agree that a stall is imminent before it will trigger, specifically because AOA probes can and do malfunction.
There’s an old saying about the word “assume”, and there is no ‘pusher’ on any 737 model. Including the MAX8.
Pilots were kept in the dark. One has to ask why? What reason would you have to not disclose an additional system? https://www.seattletimes.com/busines...ion-air-crash/
One question worth asking is does this additional system affect the type certificate? If the answer to that is yes then it opens a whole new can of worms.
One question worth asking is does this additional system affect the type certificate? If the answer to that is yes then it opens a whole new can of worms.
Join Date: Nov 2018
Location: Brisbane
Posts: 20
Likes: 0
Received 0 Likes
on
0 Posts
Now that the new MCAS is firmly implicated, I wonder why it was implicated on the MAX. One possible reason was that it was considered to be required by transport airworthiness certification via section 25. But looking through section 25 it is hard to find which exact requirement. The full regs can be easily googled (can't post as am probationary)
The previous requirement for STS is fairly easy to understand, as section 25.173 calls for "(c) The average gradient of the stable slope of the stick force versus speed curve may not be less than 1 pound for each 6 knots". Effectively the certification standard demands the aircraft emulate (some!) characteristics of a theoretical longitudinally stable aircraft which would have:
a) COG significantly ahead of the Neutral point
b) generally have the trimmed horiz stab flying at significantly lower AoA than the wing (probably to the point of downward lift at the tail)
However for modern air transports, which are desired to have optimal efficiency, it should be best to operate at near neutral longitudinal stability (i.e. just stable). In this configuration the tail is generating very little lift in either direction and hence very little drag. "Manual flight" is really "Simulated longitudinally stable manual flight necessary to conform to 25.173", which is confusing because as other posters have noted, this is really a less-automated mode instead of a manual mode. It's not so relevant to this thread anymore, but the STS seems more regulatory than useful really...changing the stab trim position via STS does not really create a more longitudinally stable aircraft and the pilot is likely to respond by removing the trim input anyway to avoid unwanted altitude excursions. This leaves him back with a slightly stable aircraft which would probably cause fatigue if pilots were expected to fly whole sectors in "manual mode", but of course they are not.
So why MCAS? It is not a speed stability system, it appears to be a beefed up stall prevention system. If the MAX COG has crept further back, it's stability margin has decreased but I don't see why an antistall stab trimmer becomes a good idea or a regulatory requirement. Looking through the stall/stall warning sections (25.201, 25.203, 25.207) there is a preference for aggressive pitch down at stall which may have something to do with it:The airplane is considered stalled when the behavior of the airplane gives the pilot a clear and distinctive indication of an acceptable nature that the airplane is stalled. Acceptable indications of a stall, occurring either individually or in combination, are—
(1) A nose-down pitch that cannot be readily arrested;
(2) Buffeting, of a magnitude and severity that is a strong and effective deterrent to further speed reduction; or
(3) The pitch control reaches the aft stop and no further increase in pitch attitude occurs when the control is held full aft for a short time before recovery is initiated. If anyone has a better understanding of how MCAS is dictated by section 25 airworthiness would be very interesting to hear.
The previous requirement for STS is fairly easy to understand, as section 25.173 calls for "(c) The average gradient of the stable slope of the stick force versus speed curve may not be less than 1 pound for each 6 knots". Effectively the certification standard demands the aircraft emulate (some!) characteristics of a theoretical longitudinally stable aircraft which would have:
a) COG significantly ahead of the Neutral point
b) generally have the trimmed horiz stab flying at significantly lower AoA than the wing (probably to the point of downward lift at the tail)
However for modern air transports, which are desired to have optimal efficiency, it should be best to operate at near neutral longitudinal stability (i.e. just stable). In this configuration the tail is generating very little lift in either direction and hence very little drag. "Manual flight" is really "Simulated longitudinally stable manual flight necessary to conform to 25.173", which is confusing because as other posters have noted, this is really a less-automated mode instead of a manual mode. It's not so relevant to this thread anymore, but the STS seems more regulatory than useful really...changing the stab trim position via STS does not really create a more longitudinally stable aircraft and the pilot is likely to respond by removing the trim input anyway to avoid unwanted altitude excursions. This leaves him back with a slightly stable aircraft which would probably cause fatigue if pilots were expected to fly whole sectors in "manual mode", but of course they are not.
So why MCAS? It is not a speed stability system, it appears to be a beefed up stall prevention system. If the MAX COG has crept further back, it's stability margin has decreased but I don't see why an antistall stab trimmer becomes a good idea or a regulatory requirement. Looking through the stall/stall warning sections (25.201, 25.203, 25.207) there is a preference for aggressive pitch down at stall which may have something to do with it:The airplane is considered stalled when the behavior of the airplane gives the pilot a clear and distinctive indication of an acceptable nature that the airplane is stalled. Acceptable indications of a stall, occurring either individually or in combination, are—
(1) A nose-down pitch that cannot be readily arrested;
(2) Buffeting, of a magnitude and severity that is a strong and effective deterrent to further speed reduction; or
(3) The pitch control reaches the aft stop and no further increase in pitch attitude occurs when the control is held full aft for a short time before recovery is initiated. If anyone has a better understanding of how MCAS is dictated by section 25 airworthiness would be very interesting to hear.
Join Date: Apr 2008
Location: Birmingham
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
The B737 FCOM states:
How does that differ from the operation of MCAS when approaching a stall? MCAS seems to be based on AOA while STS is based on IAS, but is there any other major difference, such as trim rate, duration, range of trim operation, etc? Would a pilot of a MAX aircraft who knew about MCAS handle the JT610 scenario any differently to one who did not?
How does that differ from the operation of MCAS when approaching a stall? MCAS seems to be based on AOA while STS is based on IAS, but is there any other major difference, such as trim rate, duration, range of trim operation, etc? Would a pilot of a MAX aircraft who knew about MCAS handle the JT610 scenario any differently to one who did not?
Join Date: Sep 1999
Posts: 541
Likes: 0
Received 0 Likes
on
0 Posts
I stand by the theory that this is not MAX specific and that Boeing have been caught out on a technicality only(albeit a very embarassing one).
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Join Date: Nov 2016
Location: uk
Posts: 17
Likes: 0
Received 0 Likes
on
0 Posts
I stand by the theory that this is not MAX specific and that Boeing have been caught out on a technicality only(albeit a very embarassing one).
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
I stand by the theory that this is not MAX specific and that Boeing have been caught out on a technicality only(albeit a very embarassing one).
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Join Date: Feb 2000
Location: Alaska, PNG, etc.
Age: 60
Posts: 1,550
Likes: 0
Received 0 Likes
on
0 Posts
I stand by the theory that this is not MAX specific and that Boeing have been caught out on a technicality only(albeit a very embarassing one).
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Its difficult to theorize without any data but I am guessing STS doesnt actually exist on the MAX but has been replaced by the "enhanced" MCAS,which actually performs the same or very similar function(s).The accident report will have to use the new name MCAS and since no pilots actually have any FCOM data on that system but only on its presumably very similar predecessor, STS,its a difficult but mandatory admission for Boeing to make before the investigation continues.
However,we know that the previous commander recognized the unwanted insidious trim and actually noted it in the tech log as STS input simply because he had never heard of MCAS.The NG AMM clearly describes how STS will trim to the stops under certain conditions if the pilot doesnt intervene.
The fact that it hasnt happened on the NG doesnt mean it cant; rather,it just means the specific sequence hasnt lined up yet,or if it has it was controlled by the crew.Suppose 610 hadnt crashed (for example if the AoA failure had been right side on 610,then there wouldnt have been any trim down as FCC A would have been controlling...1st flight of day) and Lionair maintenance got it right on the 5th attempt and finally fixed the fault.Would there be an AD?..............
Its those holes in the swiss cheese again that have to line up for an accident to occur.
Point being,that whether we choose to call it STS or MCAS,unwanted insidious trim contributed to this accident. Insidious because its not actually a runaway.Insidious because it can be overriden ..Insidious because the AP stab trim motor is quieter and slower.Insidious because the noise of the continuous stick shaker was highly distracting.
I see that the press are out in fulll force proclaiming Boeing causes air disaster...well,they may well be in for a bit of trouble, but this accident was avoidable and the crew wouldnt need to know the difference(s) between STS/MCAS to do so.The previous flight proves that.
Join Date: Mar 2010
Location: L.A.
Age: 56
Posts: 579
Likes: 0
Received 0 Likes
on
0 Posts
The way I understand it from reading here:
On a normal flight you would expect the STS to trim ANU during acceleration as it is trying to keep the aircraft at the previous speed. TLDR: I think the STS trim being wrong write up was "correct", because the STS will during acceleration trim ANU not AND.
On a normal flight you would expect the STS to trim ANU during acceleration as it is trying to keep the aircraft at the previous speed. TLDR: I think the STS trim being wrong write up was "correct", because the STS will during acceleration trim ANU not AND.
It is safer that way....
Silver
Join Date: May 2014
Location: In thin air
Posts: 186
Likes: 0
Received 0 Likes
on
0 Posts
Fuselage contributing to lift
The wing lift is associated with drag, called lift-dependent drag or 'induced' drag. It is a function of the wing aspect ratio and the spanwise lift distribution. To minimize induced drag you want to have a high aspect ratio and ideally an elliptical spanwise lift distribution. The drop-off of lift near the tip causes the tip trailing vortices.
If the lift dropped to zero at the wing roots you would effectively have two wings with half the aspect ratio and twice the induced drag as the complete wing, and 'tip' vortices at the tips and wing roots.
That doesn't happen. The spanwise lift distribution is continuous across the fuselage except perhaps a slight dip. In other words, the fuselage contributes to the overall lift.
The wing lift is associated with drag, called lift-dependent drag or 'induced' drag. It is a function of the wing aspect ratio and the spanwise lift distribution. To minimize induced drag you want to have a high aspect ratio and ideally an elliptical spanwise lift distribution. The drop-off of lift near the tip causes the tip trailing vortices.
If the lift dropped to zero at the wing roots you would effectively have two wings with half the aspect ratio and twice the induced drag as the complete wing, and 'tip' vortices at the tips and wing roots.
That doesn't happen. The spanwise lift distribution is continuous across the fuselage except perhaps a slight dip. In other words, the fuselage contributes to the overall lift.
Last edited by Gysbreght; 14th Nov 2018 at 08:57. Reason: correction of typographical error
Join Date: Mar 2010
Location: L.A.
Age: 56
Posts: 579
Likes: 0
Received 0 Likes
on
0 Posts
The MCAS function becomes active when the airplane Angle of Attack exceeds a threshold based on airspeed and altitude. Stabilizer incremental commands are limited to 2.5 degrees and are provided at a rate of 0.27 degrees per second. The magnitude of the stabilizer input is lower at high Mach number and greater at low Mach numbers. The function is reset once angle of attack falls below the Angle of Attack threshold or if manual stabilizer commands are provided by the flight crew. If the original elevated AOA condition persists, the MCAS function commands another incremental stabilizer nose down command according to current aircraft Mach number at actuation.
That seems a lot of trim to me. Try flying at 5,000 and 250 kt, and then mis-trimming forward by 2.5 degrees. You will be struggling.
Strikes me that Boeing designed this stall-trim system assuming that the aircraft would be slow and approaching the stall, when 2.5 degrees of trim would be acceptable. But at 250 kt in a normal climb, 2.5 degrees of trim becomes a liability. And if it gives you another 2.5 degrees of trim, you are uncontrollable.
Sounds like Boeing made this system on the cheap. The reason aircraft have stick pushers, is because the push is instantaneous, on the stick, and its withdrawal is instantaneous too - so you can pull out of the dive. But if you ‘push’ via a trim input, you cannot easily undo that trim - and so you cannot easily recover from the dive. And as a basic flying principle, we always fly with the stick, and trim out the stick pressure. You never fly with the trimmer, which is what this system is trying to do.
Furthermore, an erroneous stall-trim input at 250 kt (due faulty AoA indication) will give huge stick forces that the system did not intend - and perhaps the designer and test pilots never considered. A faulty stick push can be easily overcome with stick pressure - it was designed that way, and haveing already got the T-shirt on that one, the aircraft is easily flyable. But if a system gives you 2.5 of trim, and then another 2.5 of trim, you are going down, because the stab-trim is much more powerful than the elevator. Did anyone ever test this...?
Silver
Join Date: Mar 2010
Location: L.A.
Age: 56
Posts: 579
Likes: 0
Received 0 Likes
on
0 Posts
The reason most aircraft fly with 2.5 degrees pitch up, is that we do not fly at max speed. If you flew at MMO plus 3%, which is the max testing design speed, you would probably find that the fuselage had a zero pitch angle. (A negative fuselage angle would induce some efficiency and stability problems.)
Silver
Join Date: Mar 2010
Location: L.A.
Age: 56
Posts: 579
Likes: 0
Received 0 Likes
on
0 Posts
And regards rhe STS, people here saying it is controlled by speed. It is a bit more complex than that, as the inputs to the STS are:
Stab position.
Thrust lever position.
Airspeed.
Vertical speed.
Time after take-off (more than 10 seconds)
Time after manual trim (more than 5 seconds)
N1 more than 60%.
No autopilot.
Elevator trim requirements
Silver.