Ethiopian airliner down in Africa
Join Date: Mar 2019
Location: Europe
Posts: 32
Likes: 0
Received 0 Likes
on
0 Posts
Wrong on all counts.
a. The 737 is not a computer controlled aircraft by any stretch of the imagination. It is the original fly-by-wire aircraft (yup - 5mm steel cables).
b. The Indonesian, Ethiopian(?), A320, A340, and many other incidents demonstrate that the pilots were NOT able to be the last line of defence. Quite the reverse.
c. AF447 could easily have been saved by computer software. If Normal-law drops out because of input errors, the aircraft defaults to Alternate-law, which is a basic control system running on attitude and power. It would take Airbus a couple of years to knock up this new Alternate-law, which assumed no pilot assistance.
d. The Sioux DC10 crash was easily flown with a computer (just on engines, with no controls). They knocked up that new software inside a year.
Silver
a. The 737 is not a computer controlled aircraft by any stretch of the imagination. It is the original fly-by-wire aircraft (yup - 5mm steel cables).
b. The Indonesian, Ethiopian(?), A320, A340, and many other incidents demonstrate that the pilots were NOT able to be the last line of defence. Quite the reverse.
c. AF447 could easily have been saved by computer software. If Normal-law drops out because of input errors, the aircraft defaults to Alternate-law, which is a basic control system running on attitude and power. It would take Airbus a couple of years to knock up this new Alternate-law, which assumed no pilot assistance.
d. The Sioux DC10 crash was easily flown with a computer (just on engines, with no controls). They knocked up that new software inside a year.
Silver
And how many times did the pilots save the airplane from the automation?
Join Date: Nov 2002
Location: Northern Europe
Age: 45
Posts: 152
Received 0 Likes
on
0 Posts
Also the case with Lion Air, that plane would have crashed without pilots as well, only sooner. And the day before, the pilots had even saved that plane from the failing automation.
I fully agree!
While the NTSB is a great Organisation (the worldwide benchmark when it comes to flight safety) and beyond the slightest doubt, the FAA has presented themselves time and again mainly as a lobbyist for the industry. Safety does not appear to be anywhere near the top ten on their agenda. And that is nothing new. Sadly.
While the NTSB is a great Organisation (the worldwide benchmark when it comes to flight safety) and beyond the slightest doubt, the FAA has presented themselves time and again mainly as a lobbyist for the industry. Safety does not appear to be anywhere near the top ten on their agenda. And that is nothing new. Sadly.
SkyGod
Join Date: Aug 2000
Location: Palm Coast, Florida, USA
Age: 67
Posts: 1,542
Likes: 0
Received 10 Likes
on
1 Post
Didn’t think so..
Sort of...
MCD inspired by the brilliant crew handling of the Sioux City incident, using thrust vectors, then worked out a system they called “fly by fire” where the control inputs were sent tho the engine fcus instead of the flight controls. Visiting pilots were invited to try it in flight and apart from a little lag, were very impressed.
I don’t know whether the system was marketed, however.
I don’t know whether the system was marketed, however.
Join Date: Feb 2009
Location: Seattle
Posts: 379
Likes: 0
Received 0 Likes
on
0 Posts
2. Use manual pitch trim to re-establish trim to the point of not needing to hold column.
3. If stabilizer runs airplane nose down again, recognize it as inappropriate and arrest by using manual pitch trim to stop MCAS stabilizer motion and move stabilizer back to trimmed position. (No need to sit idly by and watch 10 seconds of stabilizer motion taking you away from trim go in when you have determined that is not appropriate.)
4. Call for PNF to toggle stabilizer cutout switches and discuss managing pitch trim via manual trim wheel for the balance of this flight.
5. Make sure that this event is squawked in a manner that assures:
- The source of the errant stabilizer motion is identified and corrected prior to the next flight
- The next crew to fly this bird knows full well what was encountered on this flight and what was done to work around it.
Join Date: Jan 2008
Location: Irvine, CA
Posts: 94
Likes: 0
Received 0 Likes
on
0 Posts
While there is not yet sufficient information to draw a clear link between the ET accident that is the subject of this thread and MCAS I am deeply troubled by the amount of misinformation regarding MCAS that is being spread here. Reluctantly I offer the explanation below without any suggestion that this system contributed to the tragedy in Ethiopia this last weekend. The truth will be revealed by the recorder data and the full investigation. I strongly implore those who do not know MCAS details to stop providing incorrect information here or anywhere else. Posing questions is fine, but please do not state as fact that about which you are not sufficiently knowledgeable.
MCAS Operation Clarification
MCAS is triggered when all of the following are true:
A. Sensed AOA exceeds a flight condition based activation threshold
B. Flaps are fully retracted (i.e., up)
C. Autopilot is not engaged
When triggered, MCAS commands nose down stabilizer as a function of how much AOA has exceeded the activation threshold and the current Mach number. For large exceedence of the MCAS activation AOA threshold, MCAS will command 2.5 degrees of stabilizer at low Mach number but less than 1/3rd of that at cruise Mach number (gradual Mach number based schedule between). For a lesser exceedence of the MCAS activation AOA threshold the size of the stabilizer increment will be proportionally less. MCAS stabilizer command will be stopped immediately upon pilot activation of pitch trim. (Pilot trim input also serves as MCAS reset - see next paragraph.)
Once MCAS has commanded one increment of stabilizer motion, it will not command more until it has been reset. MCAS is reset if any of the following occur:
1. Pilot makes a manual trim command. (MCAS will not re-activate until there have been 5 continuous seconds without pilot trim command.)
2. AOA drops below MCAS activation threshold and MCAS has run stabilizer in the airplane nose up direction taking out the increment of airplane nose down command it inserted earlier.
3. Autopilot is engaged and then disengaged.
Without pilot trim input, MCAS will not run the stab more than one increment (up to 2.5 degrees) unless MCAS is reset via either 2 or 3 above.
Talk of MCAS running the stabilizer for 10 seconds, pausing for 5 seconds, and then running it again repeatedly without pilot trim input are patently incorrect.
MCAS Operation Clarification
MCAS is triggered when all of the following are true:
A. Sensed AOA exceeds a flight condition based activation threshold
B. Flaps are fully retracted (i.e., up)
C. Autopilot is not engaged
When triggered, MCAS commands nose down stabilizer as a function of how much AOA has exceeded the activation threshold and the current Mach number. For large exceedence of the MCAS activation AOA threshold, MCAS will command 2.5 degrees of stabilizer at low Mach number but less than 1/3rd of that at cruise Mach number (gradual Mach number based schedule between). For a lesser exceedence of the MCAS activation AOA threshold the size of the stabilizer increment will be proportionally less. MCAS stabilizer command will be stopped immediately upon pilot activation of pitch trim. (Pilot trim input also serves as MCAS reset - see next paragraph.)
Once MCAS has commanded one increment of stabilizer motion, it will not command more until it has been reset. MCAS is reset if any of the following occur:
1. Pilot makes a manual trim command. (MCAS will not re-activate until there have been 5 continuous seconds without pilot trim command.)
2. AOA drops below MCAS activation threshold and MCAS has run stabilizer in the airplane nose up direction taking out the increment of airplane nose down command it inserted earlier.
3. Autopilot is engaged and then disengaged.
Without pilot trim input, MCAS will not run the stab more than one increment (up to 2.5 degrees) unless MCAS is reset via either 2 or 3 above.
Talk of MCAS running the stabilizer for 10 seconds, pausing for 5 seconds, and then running it again repeatedly without pilot trim input are patently incorrect.
So MCAS activates, due to faulty AoA sensor reading.
Pilot resets the system by applying counter trim.
MCAS rolls again... (repeat, while airplane accelerates and finally MCAS wins...)
Why does MCAS run the stab? Why not offset the elevator?
Will MCAS also reset, if it is switched off and switched on again?
Why does MCAS not also read - for instance - vertical and horizontal speeds and their trends first, instead single-pointedly relying on the AoA reading and deciding the airplane is about to stall and start fu****g with the stab?
Join Date: Mar 2010
Location: Often in Jersey, but mainly in the past.
Age: 79
Posts: 7,808
Received 135 Likes
on
63 Posts
That post suggests that using the electric trim button (presumably the most convenient practice) generates issues. Whereas, after toggling the stab off, the geriatric trim wheel solves all problems?
Oh, and using primary flying controls instead of autopilot settings, I assume?
Oh, and using primary flying controls instead of autopilot settings, I assume?
Join Date: Mar 2010
Location: L.A.
Age: 56
Posts: 579
Likes: 0
Received 0 Likes
on
0 Posts
1. Pilot makes a manual trim command. (MCAS will not re-activate until there have been 5 continuous seconds without pilot trim command.)
Talk of MCAS running the stabilizer for 10 seconds, pausing for 5 seconds, and then running it again repeatedly without pilot trim input are patently incorrect.
Talk of MCAS running the stabilizer for 10 seconds, pausing for 5 seconds, and then running it again repeatedly without pilot trim input are patently incorrect.
And I have to ask again, because nobody has answered - why would anyone invent a system that gives full nose-down trim? It goes against all aviation history and procedures. Remember the old adage - NEVER FLY WITH THE TRIMMER. And yet here is Boeing effectively using the trimmer as a primary flight control - deliberately placing the aircraft out of trim, instead of keeping it in trim.
That is why all other aircraft have stick-pushers, so you fly the stall with the primary flight controls, not the trimmer. The difference? Assisting the stall with the trimmer leaves you out of trim for the subsequent dive - with 60 kg of pressure on the stick, and 60 turns of the trim before you get back to something that is flyable. Conversely, when a stick pusher relents, you are still in trim, and can recover and fly away with ease. So why did Boeing chose such an absurd system for the 737-Max? Are Boeing really penny-pinching to such a degree? They should have taken a leaf out of the British Midland book - quote: "if you think safety is expensive, try having an accident..."
Silver
Join Date: Mar 2014
Location: United States
Posts: 2
Likes: 0
Received 0 Likes
on
0 Posts
Suppose MCAS isn't the CAUSE
Suppose MCAS isn't the CAUSE, but is also a VICTIM OF the root cause. If you feed MCAS defective inputs one result of that is that it will do what it was intended to do - it'll pitch down. Suppose whatever is mangling the MCAS inputs is also mangling the airspeed data displayed to the crew. In other words, the computing and indicating systems on the aircraft are displaying defective information which the crew and MCAS are acting upon. Troubleshooting MCAS in this situation won't get you much because MCAS isn't the CAUSE - it's an EFFECT of a fault elsewhere. I'd like to see the logic chain between the outdoor sensors and the displays and systems. I'll bet there are multiple computing boxes in that chain where defective air data can be produced *without detection* by the crew - or the MCAS.
Join Date: Feb 2009
Location: Seattle
Posts: 379
Likes: 0
Received 0 Likes
on
0 Posts
That post suggests that using the electric trim button (presumably the most convenient practice) generates issues. Whereas, after toggling the stab off, the geriatric trim wheel solves all problems?
Oh, and using primary flying controls instead of autopilot settings, I assume?
Oh, and using primary flying controls instead of autopilot settings, I assume?
You are correct about not having autopilot once the stabilizer is cutout. Without electric stabilizer control from the autopilot stabilizer offload logic, autopilot functionality cannot be provided.
Join Date: Jan 2019
Location: Belfast
Posts: 36
Likes: 0
Received 0 Likes
on
0 Posts
1. First thing is pull the column to put in the between 5 to 8 degrees of airplane nose up elevator needed to offset the MCAS stabilizer increment.
2. Use manual pitch trim to re-establish trim to the point of not needing to hold column.
3. If stabilizer runs airplane nose down again, recognize it as inappropriate and arrest by using manual pitch trim to stop MCAS stabilizer motion and move stabilizer back to trimmed position. (No need to sit idly by and watch 10 seconds of stabilizer motion taking you away from trim go in when you have determined that is not appropriate.)
4. Call for PNF to toggle stabilizer cutout switches and discuss managing pitch trim via manual trim wheel for the balance of this flight.
5. Make sure that this event is squawked in a manner that assures:
- The source of the errant stabilizer motion is identified and corrected prior to the next flight
- The next crew to fly this bird knows full well what was encountered on this flight and what was done to work around it.
2. Use manual pitch trim to re-establish trim to the point of not needing to hold column.
3. If stabilizer runs airplane nose down again, recognize it as inappropriate and arrest by using manual pitch trim to stop MCAS stabilizer motion and move stabilizer back to trimmed position. (No need to sit idly by and watch 10 seconds of stabilizer motion taking you away from trim go in when you have determined that is not appropriate.)
4. Call for PNF to toggle stabilizer cutout switches and discuss managing pitch trim via manual trim wheel for the balance of this flight.
5. Make sure that this event is squawked in a manner that assures:
- The source of the errant stabilizer motion is identified and corrected prior to the next flight
- The next crew to fly this bird knows full well what was encountered on this flight and what was done to work around it.
So on any occasion on climb after TO and this was to occur, this would be your modus operandi? Stick shaker or not? Low or erroneous ASI reading or not? Just pull against MCAS and tell PNF to start flicking switches? I know where you're coming from, but, unfortunately it's just not always as simple as the way you're portraying. At 1000ft you dont have much room to play with in the first place, which in itself adds pressure. Again, confirmation bias, people had commented earlier that "look out the window, you'll know if you're close to stall". Say for example this captain who had 8,000 hours of instruments reading correctly, the one time he gets put in a scary position he's meant to look out the window and say to his 200 hour FO "plane is wrong, at 1,000ft I can tell our speed is good". No, his confirmation bias will be, "we're about to stall, the readings must be right, what the f***??".
Thread Starter
189 pax now have an Italian holiday extension FOC
Join Date: Oct 2017
Location: Vienna
Posts: 143
Likes: 0
Received 0 Likes
on
0 Posts
Or... your flaps got stuck so you are landing with flaps 0, you are on short final, hit a bird directly into AoA, mcas repeatedly applies 2.5 degrees trim while you are a few hundred feet AGL, because clearly that is safe at low mach numbers?
What could possibly go wrong?
Join Date: Jan 2008
Location: Hotel Sheets, Downtown Plunketville
Age: 76
Posts: 0
Likes: 0
Received 0 Likes
on
0 Posts
While there is not yet sufficient information to draw a clear link between the ET accident that is the subject of this thread and MCAS I am deeply troubled by the amount of misinformation regarding MCAS that is being spread here. Reluctantly I offer the explanation below without any suggestion that this system contributed to the tragedy in Ethiopia this last weekend. The truth will be revealed by the recorder data and the full investigation. I strongly implore those who do not know MCAS details to stop providing incorrect information here or anywhere else. Posing questions is fine, but please do not state as fact that about which you are not sufficiently knowledgeable.
MCAS Operation Clarification
MCAS is triggered when all of the following are true:
A. Sensed AOA exceeds a flight condition based activation threshold
B. Flaps are fully retracted (i.e., up)
C. Autopilot is not engaged
When triggered, MCAS commands nose down stabilizer as a function of how much AOA has exceeded the activation threshold and the current Mach number. For large exceedence of the MCAS activation AOA threshold, MCAS will command 2.5 degrees of stabilizer at low Mach number but less than 1/3rd of that at cruise Mach number (gradual Mach number based schedule between). For a lesser exceedence of the MCAS activation AOA threshold the size of the stabilizer increment will be proportionally less. MCAS stabilizer command will be stopped immediately upon pilot activation of pitch trim. (Pilot trim input also serves as MCAS reset - see next paragraph.)
Once MCAS has commanded one increment of stabilizer motion, it will not command more until it has been reset. MCAS is reset if any of the following occur:
1. Pilot makes a manual trim command. (MCAS will not re-activate until there have been 5 continuous seconds without pilot trim command.)
2. AOA drops below MCAS activation threshold and MCAS has run stabilizer in the airplane nose up direction taking out the increment of airplane nose down command it inserted earlier.
3. Autopilot is engaged and then disengaged.
Without pilot trim input, MCAS will not run the stab more than one increment (up to 2.5 degrees) unless MCAS is reset via either 2 or 3 above.
Talk of MCAS running the stabilizer for 10 seconds, pausing for 5 seconds, and then running it again repeatedly without pilot trim input are patently incorrect.
MCAS Operation Clarification
MCAS is triggered when all of the following are true:
A. Sensed AOA exceeds a flight condition based activation threshold
B. Flaps are fully retracted (i.e., up)
C. Autopilot is not engaged
When triggered, MCAS commands nose down stabilizer as a function of how much AOA has exceeded the activation threshold and the current Mach number. For large exceedence of the MCAS activation AOA threshold, MCAS will command 2.5 degrees of stabilizer at low Mach number but less than 1/3rd of that at cruise Mach number (gradual Mach number based schedule between). For a lesser exceedence of the MCAS activation AOA threshold the size of the stabilizer increment will be proportionally less. MCAS stabilizer command will be stopped immediately upon pilot activation of pitch trim. (Pilot trim input also serves as MCAS reset - see next paragraph.)
Once MCAS has commanded one increment of stabilizer motion, it will not command more until it has been reset. MCAS is reset if any of the following occur:
1. Pilot makes a manual trim command. (MCAS will not re-activate until there have been 5 continuous seconds without pilot trim command.)
2. AOA drops below MCAS activation threshold and MCAS has run stabilizer in the airplane nose up direction taking out the increment of airplane nose down command it inserted earlier.
3. Autopilot is engaged and then disengaged.
Without pilot trim input, MCAS will not run the stab more than one increment (up to 2.5 degrees) unless MCAS is reset via either 2 or 3 above.
Talk of MCAS running the stabilizer for 10 seconds, pausing for 5 seconds, and then running it again repeatedly without pilot trim input are patently incorrect.
Join Date: Feb 2009
Location: Seattle
Posts: 379
Likes: 0
Received 0 Likes
on
0 Posts
Actually, this 'talk' is perfectly correct. When the MCAS system is activated erroneously, the pilot will inevitably make a trim input. And if your trim input is insufficient to counter the MCAS input, as was the case on the Indonesian, you rapidly end up with full nose down trim.
And I have to ask again, because nobody has answered - why would anyone invent a system that gives full nose-down trim? It goes against all aviation history and procedures. Remember the old adage - NEVER FLY WITH THE TRIMMER. And yet here is Boeing effectively using the trimmer as a primary flight control - deliberately placing the aircraft out of trim, instead of keeping it in trim.
That is why all other aircraft have stick-pushers, so you fly the stall with the primary flight controls, not the trimmer. The difference? Assisting the stall with the trimmer leaves you out of trim for the subsequent dive - with 60 kg of pressure on the stick, and 60 turns of the trim before you get back to something that is flyable. Conversely, when a stick pusher relents, you are still in trim, and can recover and fly away with ease. So why did Boeing chose such an absurd system for the 737-Max? Are Boeing really penny-pinching to such a degree? They should have taken a leaf out of the British Midland book - quote: "if you think safety is expensive, try having an accident..."
Silver
And I have to ask again, because nobody has answered - why would anyone invent a system that gives full nose-down trim? It goes against all aviation history and procedures. Remember the old adage - NEVER FLY WITH THE TRIMMER. And yet here is Boeing effectively using the trimmer as a primary flight control - deliberately placing the aircraft out of trim, instead of keeping it in trim.
That is why all other aircraft have stick-pushers, so you fly the stall with the primary flight controls, not the trimmer. The difference? Assisting the stall with the trimmer leaves you out of trim for the subsequent dive - with 60 kg of pressure on the stick, and 60 turns of the trim before you get back to something that is flyable. Conversely, when a stick pusher relents, you are still in trim, and can recover and fly away with ease. So why did Boeing chose such an absurd system for the 737-Max? Are Boeing really penny-pinching to such a degree? They should have taken a leaf out of the British Midland book - quote: "if you think safety is expensive, try having an accident..."
Silver
The FO had an MPL not an ATPL, The program provides for 70 hours of actual flight time and 130 hours of simulator training. From an earlier post of a pilot who actually flew with ET he stated that most MPL holders had roughly 230 total hours before they were released to Line (vs. Training) captains.
Probably a discussion for "elsewhere", but MPL does seem to be a bit of a "short cut" affair.
Join Date: Dec 2017
Location: home
Posts: 42
Likes: 0
Received 0 Likes
on
0 Posts
The wide range of views on here is something I applaud - rather I am concerned by some people who do not live in the real world - this one here.
MPLs are a fact of life- I fly EasyJet and Ryanair and the FOs often look like they should still be at school. Same on SpiceJet and Go-Air in India. I don't see them going away. The US seems to be out of step if anything by still insisting on more experience- I am surprised commercial pressure hasn't led to the same there.
Aeroplanes must be built such that they can be flown by these crews - safely operated all over the world. As I said yesterday, I am not sure certification bodies are doing their duty here.
MPLs are a fact of life- I fly EasyJet and Ryanair and the FOs often look like they should still be at school. Same on SpiceJet and Go-Air in India. I don't see them going away. The US seems to be out of step if anything by still insisting on more experience- I am surprised commercial pressure hasn't led to the same there.
Aeroplanes must be built such that they can be flown by these crews - safely operated all over the world. As I said yesterday, I am not sure certification bodies are doing their duty here.
It is time for the Regulators and Airlines to realise that flying a jet isn't the simple task that they keep trying to delude themselves into believing, in the name of cost cutting. Hopefully this is the accident that is the turning point in refocusing training and money spent on pilot training.
Last edited by greenfields; 12th Mar 2019 at 22:05.