Ethiopian airliner down in Africa
Join Date: Jan 2008
Location: uk
Posts: 857
Likes: 0
Received 0 Likes
on
0 Posts
This is a puzzling excerpt from the CVR. It appears that the FO had the right idea, in terms of getting control of the trim back via manual. By "not working" - I wonder what he meant.
(As I look at the Airspeed value, I keep thinking, will ask another question in a bit ...)
(As I look at the Airspeed value, I keep thinking, will ask another question in a bit ...)
Join Date: Mar 2019
Location: Canada
Posts: 72
Likes: 0
Received 0 Likes
on
0 Posts
I'm a real pilot, too. The one thing that really stands out to me in the prelim is that they didn't reduce power. I just took a nice big bite of humble pie regarding the first officer, so I'm not going to sling any more mud, but one could reasonably have assumed they would have done so, wouldn't you say? While trying to fight a nose-down situation? Unusual attitude recovery 101.
While attempting to sort out the trim situation, they didn't see that the airspeed kept increasing.
Join Date: May 2010
Location: Boston
Age: 73
Posts: 443
Likes: 0
Received 0 Likes
on
0 Posts
I've read the entire report and still see no mention of a bird (or other foreign object) strike to the left AoA sensor. Where did that tantalizing hint come from??? CVR?
Also, the media coverage (and even posts here) keep harping on the idea that all Boeing recovery procedures were followed, and yet they turned the trim cutout switches back ON in their desperation, which was certainly NOT part of the prescribed procedures. Seems as if that is some serious "dumbing-down" of the info.
Also, the media coverage (and even posts here) keep harping on the idea that all Boeing recovery procedures were followed, and yet they turned the trim cutout switches back ON in their desperation, which was certainly NOT part of the prescribed procedures. Seems as if that is some serious "dumbing-down" of the info.
The FDR data supports a sudden event on the AoA system with at least 2 hints that it was at the sensor:
1: Sudden jump to extreme non changing value until late in flight with partial freeing near end. Bird guts blew off?
2: Master caution anti ice caution and 'Primary AOA heat L' to off coincident with above. This is consistent with significant physical damage to AoA sensor causing an open in heater circuit.
I suspect there may be internal disagreement on the possible cause of this so they left it out but a bird strike is a strong contender in my view.
Could be the initial bird strike reports followed the above reasoning but may not be a way to dis/prove the theory.
Join Date: Dec 2015
Location: Cape Town, ZA
Age: 62
Posts: 424
Likes: 0
Received 0 Likes
on
0 Posts
I'm a real pilot, too. The one thing that really stands out to me in the prelim is that they didn't reduce power. I just took a nice big bite of humble pie regarding the first officer, so I'm not going to sling any more mud, but one could reasonably have assumed they would have done so, wouldn't you say? While trying to fight a nose-down situation? Unusual attitude recovery 101.
The high speed alone was not the direct cause of the crash, though it may have severely limited their options. In theory speed could have been reduced gradually, though it is not known what effect the reduction of engine thrust would have on pitch.
IMO the combination of speed, and the final MCAS activation of nose down trim was fatal. Conversely, MCAS activation at low speed earlier in the flight was recoverable, because they could trim up manually. The fault-tree is complex...
Edit: pilotmike If I remove the word slight will that make you happy?
Edit: In retrospect I stand by my statement for muiltiple reasons:
1. Pilots are not the only people who know about aerodynamics.
2. The discussion is around flight close to VMO, at which speed the aerodynamic forces far outweigh the pitch moment of the engine thrust.
3. Most discussion of engine pitch up moment is close to VMC, in which case the aerodynamic forces are proportionately small.
4. Most discussion of underslung engines centers around TOGA thrust, which could not be further from this flight regime.
Nobody has come up with any hard numbers, so these factors may remain an unknown.
Edit: Similar mention of speed/thrust from justthisonce
Last edited by GordonR_Cape; 4th Apr 2019 at 20:56.
Join Date: Feb 2011
Location: Grand Turk
Age: 61
Posts: 69
Likes: 0
Received 0 Likes
on
0 Posts
The biggest issue that I see from the data so far is the massive authority that MCAS has and how small the authority of the STS/ pickle switch is. Two massive MCAS AND trim adjustments in the space of 29 secs sealed the fate of the flight. If is not clear if it was possible to manually trim given the airspeed but unlikely due to control pressure. The ground proximity probably precluded thrust reduction or runaway trim recovery procedure.
The crew would have had to correctly diagnose the problem and flicked the trim disconnect switches in just over 60s from stick-shaker to unwanted MCAS AND. It seems the crew did not make all the right choices but hardly reckless driving either. I suspect that the overall picture is that that Boeing are asking way too much of their customers to fly this aircraft. It is an accident waiting to happen. Broadly speaking the data shows a horrible control system that does not work properly and could have been much more safely and better designed. It also shows that pilots may not always make all the best decisions when under high levels of stress.
Being a little flippant... a logical solution is to automatically disconnect electric trim if there is a left side stick-shaker condition... or instead of alpha vane disagree indication it could automatically disconnect MCAS (slightly more serious solution). Behind the systemic problems is the question of why the AOA sensors failed... is this a freak, or is there something more fundamental at work?
The crew would have had to correctly diagnose the problem and flicked the trim disconnect switches in just over 60s from stick-shaker to unwanted MCAS AND. It seems the crew did not make all the right choices but hardly reckless driving either. I suspect that the overall picture is that that Boeing are asking way too much of their customers to fly this aircraft. It is an accident waiting to happen. Broadly speaking the data shows a horrible control system that does not work properly and could have been much more safely and better designed. It also shows that pilots may not always make all the best decisions when under high levels of stress.
Being a little flippant... a logical solution is to automatically disconnect electric trim if there is a left side stick-shaker condition... or instead of alpha vane disagree indication it could automatically disconnect MCAS (slightly more serious solution). Behind the systemic problems is the question of why the AOA sensors failed... is this a freak, or is there something more fundamental at work?
Join Date: Dec 2013
Location: NN11
Posts: 13
Likes: 0
Received 0 Likes
on
0 Posts
First Lawsuit
COTCHETT, PITRE & McCARTHY, LL
https://www.cpmlegal.com/media/news/..._Complaint.pdf
IN THE UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF ILLINOIS EASTERN DIVISION
MICHAEL STUMO and NADIA MILLERON, as Personal Representatives of the Estate of SAMYA STUMO, deceased,
Plaintiffs,
v.
THE BOEING COMPANY, a Delaware corporation;
ETHIOPIAN AIRLINES, a foreign corporation;
ETHIOPIAN AIRLINES ENTERPRISE;
ETHIOPIAN AIRLINES GROUP, INC.;
and
ROSEMOUNT AEROSPACE, INC., a Delaware corporation;
Defendants.
A Claim against the FAA has also been filed by the same partners, ahead of a possible suit.
https://www.cpmlegal.com/media/news/..._Complaint.pdf
IN THE UNITED STATES DISTRICT COURT FOR THE NORTHERN DISTRICT OF ILLINOIS EASTERN DIVISION
MICHAEL STUMO and NADIA MILLERON, as Personal Representatives of the Estate of SAMYA STUMO, deceased,
Plaintiffs,
v.
THE BOEING COMPANY, a Delaware corporation;
ETHIOPIAN AIRLINES, a foreign corporation;
ETHIOPIAN AIRLINES ENTERPRISE;
ETHIOPIAN AIRLINES GROUP, INC.;
and
ROSEMOUNT AEROSPACE, INC., a Delaware corporation;
Defendants.
A Claim against the FAA has also been filed by the same partners, ahead of a possible suit.
The autopilot behaviour differed considerably from the Boeing documents:
By 05:38:45 the left AoA sensor was reporting (but not displaying) over 74deg AoA, yet the LH AP was engaged successfully some 37 seconds later and remained engaged until time 05:39:55. By that time MCAS had completed 3 discrete pitch-down trim inputs before the AP actually disengaged.
George the autopilot wants to go up whilst HAL the MCAS wants to go down.
Eeek.
By 05:38:45 the left AoA sensor was reporting (but not displaying) over 74deg AoA, yet the LH AP was engaged successfully some 37 seconds later and remained engaged until time 05:39:55. By that time MCAS had completed 3 discrete pitch-down trim inputs before the AP actually disengaged.
George the autopilot wants to go up whilst HAL the MCAS wants to go down.
Eeek.
One common pattern between the Lion air and Ethopian air crash is, that the later/last manual trim up commanded from the coloum switches are in both cases only short blips, followed by 5 second trim down from the MCAS system.
I find it hard to believe that both pilots clinging on the control coloums for their dare life to get nose up do not try harder/longer on the electric trim as long as engaged and not cut out.
I assume that there is more to the story.
I find it hard to believe that both pilots clinging on the control coloums for their dare life to get nose up do not try harder/longer on the electric trim as long as engaged and not cut out.
I assume that there is more to the story.
The autopilot behaviour differed considerably from the Boeing documents:
By 05:38:45 the left AoA sensor was reporting (but not displaying) over 74deg AoA, yet the LH AP was engaged successfully some 37 seconds later and remained engaged until time 05:39:55. By that time MCAS had completed 3 discrete pitch-down trim inputs before the AP actually disengaged.
George the autopilot wants to go up whilst HAL the MCAS wants to go down.
Eeek.
By 05:38:45 the left AoA sensor was reporting (but not displaying) over 74deg AoA, yet the LH AP was engaged successfully some 37 seconds later and remained engaged until time 05:39:55. By that time MCAS had completed 3 discrete pitch-down trim inputs before the AP actually disengaged.
George the autopilot wants to go up whilst HAL the MCAS wants to go down.
Eeek.
Aside from why the AP was successfully engaged, the three trim ND FCC commands (and one NU for good measure), DURING autopilot engagement are brief and likely STS driven - not MCAS. That comes after the AP is disconnected.
The first MCAS ND command occurs on deselection of the AP, and runs for 10 seconds as the system is expected to do. You can clearly see that in the FDR traces.
The crew then input a shorter NU pickle switch trim input (which did not equal the MCAS ND demaind).
MCAS reset and 5 seconds after the crew ceased their input, it runs again for less than 10 seconds this time, since the crew again provided NU pickle switch trim, which shut off MCAS for another 5 seconds, at which point the crew had selected the cutoff switches.
MCAS ran again (since it was reset) but had no effect, since it was disabled by the cutoffs.
At this point the aircraft was roughly pitch trim of 2.5 units (so ND). The crew then tried to use manual trim (which failed) and then hauled back on the column and tried to control the aircraft via the yoke.
Later two very short pickle switch inputs NU were input indicating the crew re-engaged the electric trim, but they were very short and had a very small effect on trim.
5 seconds later MCAS, having been reset by the crew electric trim input, and now being active again, ran for less than 10 seconds and seems to have been interrupted by the Left AOA value changing.
Unfortunately at this point the aircraft was very fast >375kts and the ND input was too much to overcome.
- GY
Join Date: Nov 2018
Location: madrid
Posts: 47
Likes: 0
Received 0 Likes
on
0 Posts
One common pattern between the Lion air and Ethopian air crash is, that the later/last manual trim up commanded from the coloum switches are in both cases only short blips, followed by 5 second trim down from the MCAS system.
I find it hard to believe that both pilots clinging on the control coloums for their dare life to get nose up do not try harder/longer on the electric trim as long as engaged and not cut out.
I assume that there is more to the story.
I find it hard to believe that both pilots clinging on the control coloums for their dare life to get nose up do not try harder/longer on the electric trim as long as engaged and not cut out.
I assume that there is more to the story.
Join Date: Nov 2012
Location: New York
Posts: 11
Likes: 0
Received 0 Likes
on
0 Posts
Join Date: Feb 2008
Location: Apple Maggot Quarantine Area
Age: 47
Posts: 100
Likes: 0
Received 0 Likes
on
0 Posts
Well, if I were the pilot, I would have set power to 75% N1. This is the reference value which is provided in the handbook, AKA the unreliable airspeed NNC, and it is a memory item that pilots are expected to execute without needing to reference the QRH. As a note, the QRH specifically states that stick shaker, overspeed warning, and airspeed low alerts may sound erroneously or simultaneously, and this situation is regularly practiced in the simulator.
Join Date: May 2010
Location: Boston
Age: 73
Posts: 443
Likes: 0
Received 0 Likes
on
0 Posts
Join Date: Jul 2005
Location: btw SAMAR and TOSPA
Posts: 566
Likes: 0
Received 0 Likes
on
0 Posts
I've read the entire report and still see no mention of a bird (or other foreign object) strike to the left AoA sensor. Where did that tantalizing hint come from??? CVR?
Also, the media coverage (and even posts here) keep harping on the idea that all Boeing recovery procedures were followed, and yet they turned the trim cutout switches back ON in their desperation, which was certainly NOT part of the prescribed procedures. Seems as if that is some serious "dumbing-down" of the info.
Also, the media coverage (and even posts here) keep harping on the idea that all Boeing recovery procedures were followed, and yet they turned the trim cutout switches back ON in their desperation, which was certainly NOT part of the prescribed procedures. Seems as if that is some serious "dumbing-down" of the info.
Join Date: Dec 2015
Location: Cape Town, ZA
Age: 62
Posts: 424
Likes: 0
Received 0 Likes
on
0 Posts
Why would pilots in a severe AND trim crisis merely blip the switches?
Is there any possibility that the extreme column forces could have interfered with the switches, either mechanically (including wiring etc) or biomechanically.?
By biomechanically I mean could the hand position and forces make the pilot believe he was pressing the switches when in fact he was not?
Is there any possibility that the extreme column forces could have interfered with the switches, either mechanically (including wiring etc) or biomechanically.?
By biomechanically I mean could the hand position and forces make the pilot believe he was pressing the switches when in fact he was not?
Not true at all. There is a long period where the trim is stable, and the cutoff switches have clearly been disabled, inhibiting MCAS. This is shown on the FDR. Later there is a sudden uncommanded nose down trim, consistent with MCAS. The only logical way this could have happened is for the switches to have been been enabled. To suggest that this is pure speculation, flies in the facts shown on the FDR.
Last edited by GordonR_Cape; 4th Apr 2019 at 19:43.
Join Date: Feb 2008
Location: Apple Maggot Quarantine Area
Age: 47
Posts: 100
Likes: 0
Received 0 Likes
on
0 Posts
At 05:43:11, about 32 seconds before the end of the recording, at approximately 13,4002 ft, two momentary manual electric trim inputs are recorded in the ANU direction. The stabilizer moved in the ANU direction from 2.1 units to 2.3 units.
That could not have happened if the cutout switches had not been turned back on.
Last edited by slacktide; 4th Apr 2019 at 19:22. Reason: spelling
Join Date: Oct 2011
Location: Lower Skunk Cabbageland, WA
Age: 74
Posts: 354
Likes: 0
Received 0 Likes
on
0 Posts
Join Date: Dec 2004
Location: Southern England
Posts: 109
Likes: 0
Received 0 Likes
on
0 Posts
Not only is turning the stab trim cutout switches back on NOT a part of the documented and approved recovery procedure, the FCOM specifically cautions against turning electric stab trim back on after it has been selected off.
"Ensure that the STAB TRIM CUTOUT switches are set to CUTOUT and stay in the CUTOUT position for the remainder of the flight."
It's disingenuous to state that the recovery procedure was followed, when it was only halfway followed, and other basic elements of pilotage were neglected. If they had monitored and controlled the airspeed within limits, and followed the published recovery procedure, they would have been able to manually trim the airplane using the trim wheel.
Regarding my language "monitored and controlled their airspeed." I know someone will pipe up about stick shakers and clackers and cockpit confusion. Yes, the left side airspeed was unreliable, and the left side stick shaker was going off. But the right side airspeed was not unreliable, and the BU airspeed was not unreliable, and the right side stick shaker was not going off. Isn't unreliable airspeed a well documented scenario which is regularly practiced in the simulator, with simultaneous shaker and clacker? Isn't it the second item on the very first page of the QRH? Are the appropriate initial pitch and power settings to be used during unreliable airspeed not memory items?
"Ensure that the STAB TRIM CUTOUT switches are set to CUTOUT and stay in the CUTOUT position for the remainder of the flight."
It's disingenuous to state that the recovery procedure was followed, when it was only halfway followed, and other basic elements of pilotage were neglected. If they had monitored and controlled the airspeed within limits, and followed the published recovery procedure, they would have been able to manually trim the airplane using the trim wheel.
Regarding my language "monitored and controlled their airspeed." I know someone will pipe up about stick shakers and clackers and cockpit confusion. Yes, the left side airspeed was unreliable, and the left side stick shaker was going off. But the right side airspeed was not unreliable, and the BU airspeed was not unreliable, and the right side stick shaker was not going off. Isn't unreliable airspeed a well documented scenario which is regularly practiced in the simulator, with simultaneous shaker and clacker? Isn't it the second item on the very first page of the QRH? Are the appropriate initial pitch and power settings to be used during unreliable airspeed not memory items?
Memory Items for Airspeed Unreliable?
Memory Items for Unscheduled Stab trim?
It appears the aircraft was never put back in trim after the initial MCAS input and although an attempt was made with the cutouts the aircraft was out of trim. Turned back on again contrary to advice (accept this is speculation at present) and the system was allowed to trim forward again.
Unfortunately these points will be lost to the majority on here who simply want to flame Boeing.
THUNDERTAILED
Join Date: Nov 1999
Location: L200
Posts: 325
Likes: 0
Received 0 Likes
on
0 Posts
Thoughts.
This aircraft had multiple pitot static malfunctions in the days prior to the accident as per the tech log quoted in the report. Altimeter and VSI erratic.
If they had had a bird strike on the vane, they would have noticed the thump and said something. I think we can rule a bird strike out. And frozen things. It was 17 degrees C on the ground.
Just after takeoff the crew got an almost immediate
Stick shaker
Airspeed disagree
Altitude disagree
F/D disagree
Which constitutes an unreliable airspeed non normal
(Together with an anti ice caution)
And did not apply the memory items for that , and seemed to be prepared to continue to FL320.
The trim problems started once the flaps were retracted , however the flaps seem to have been retracted despite the left stick shaker being continually active and the aircraft in an unreliable airpseed state which calls for a pitch and power setting with the flaps down (if I recall, 10deg NU, 85%N1) but the power wasn't reduced from 94% either.
The stabtrim cutout switches seem to have stopped the MCAS from moving the stab, but then the switches were re-engaged (2 ANU trims were recorded 2,5 min after the stab trim switches were set to cutout) and this then allowed the MCAS to pitch it down again.
As regards thrust and pitching moments I personally would prefer to take my chances with speedbrake, idle thrust and a bit of a dip than two engines at 94% when I'm pointing downhill.
And I don't think I'd be getting ATC involved until I had the beast back under some sort of control.
This seems to be more than an MCAS thing, it may be a pitotstatic adiru thing.
If one sensor gets extreme readings or if there's a sensor disagree, then no system should rely upon that sensor data.
Systems shouldn't rely on one sensor only.
This aircraft had multiple pitot static malfunctions in the days prior to the accident as per the tech log quoted in the report. Altimeter and VSI erratic.
If they had had a bird strike on the vane, they would have noticed the thump and said something. I think we can rule a bird strike out. And frozen things. It was 17 degrees C on the ground.
Just after takeoff the crew got an almost immediate
Stick shaker
Airspeed disagree
Altitude disagree
F/D disagree
Which constitutes an unreliable airspeed non normal
(Together with an anti ice caution)
And did not apply the memory items for that , and seemed to be prepared to continue to FL320.
The trim problems started once the flaps were retracted , however the flaps seem to have been retracted despite the left stick shaker being continually active and the aircraft in an unreliable airpseed state which calls for a pitch and power setting with the flaps down (if I recall, 10deg NU, 85%N1) but the power wasn't reduced from 94% either.
The stabtrim cutout switches seem to have stopped the MCAS from moving the stab, but then the switches were re-engaged (2 ANU trims were recorded 2,5 min after the stab trim switches were set to cutout) and this then allowed the MCAS to pitch it down again.
As regards thrust and pitching moments I personally would prefer to take my chances with speedbrake, idle thrust and a bit of a dip than two engines at 94% when I'm pointing downhill.
And I don't think I'd be getting ATC involved until I had the beast back under some sort of control.
This seems to be more than an MCAS thing, it may be a pitotstatic adiru thing.
If one sensor gets extreme readings or if there's a sensor disagree, then no system should rely upon that sensor data.
Systems shouldn't rely on one sensor only.