PPRuNe Forums - View Single Post - Ethiopian airliner down in Africa
View Single Post
Old 10th Mar 2019, 11:37
  #54 (permalink)  
SigWit
 
Join Date: Sep 2018
Location: Somewhere
Posts: 38
Likes: 0
Received 0 Likes on 0 Posts
Originally Posted by bunk exceeder


So they never got to 10,500, hence no turn. Where FR shows the flight ending and Bishoftu are NOT the same place. It has a “density altitude” feel to it. You know, the guy who shoots a moose and loads it into his Piper Cub, grossly overloading it, on a hot and high day. He gets just enough juice to lift off in ground effect but is never able to climb out of it. Trees getting bigger....

Was the correct Perf data entered into the FMC? As trees get bigger, the temptation to pull back more, despite insufficient power, becomes enormous, hence many of these things ending in a stall/spin situation. Then there’s that MCAS “unpublicized” feature. This explains it well:

https://theaircurrent.com/aviation-s...em-mcas-jt610/

If, meaning IF, they had insufficient power and pulled back a bit too much, right into the MCAS zone of operation, which would definitely not help right then, well, there are a couple of potential links in the old chain. Or Swiss cheese holes. I’m surprised that a thing that moves your trim around when you’re in a bad corner of the envelope could
be deemed as too much information for the pilots, hence not make it into the manual.

Judging by the FR24 raw data their forward speed kept increasing, which does not point to any performance problems.
The question is why they couldn’t convert to forward speed into altitude.
SigWit is offline