View Single Post
Old 27th Apr 2019, 14:57
  #4440 (permalink)  
HundredPercentPlease
 
Join Date: Jun 2003
Location: UK
Posts: 2,191
Originally Posted by 737 Driver View Post
some very basic airmanship technique
Getting a bit bored of multiple posts slagging off these pilots.

We get it. You think they were sub-standard. You would have used your greater "airmanship" to keep the basic parameters in line and therefore the aircraft flying.

Your lack of appreciation of human factors in a real scenario with real line pilots in the real world is what you should address. After-the-event-heroism is ever so easy.

My suggestion is to slice the event up into small time slices. In each slice - look at the information presented, the probable solution, the required actions and the workload. Then in the next slice, base your model on a modification of the previous slice - increasing or decreasing the factors, and extrapolating the data flows. So if it starts with a stall indication, then keep the "it's a stall" flowing, until (given the workload estimate) the information is sufficient to demonstrate to the pilots that it's not a stall. Doing this, you will discover that the pilot with reduced workload will process new information earlier.

In my model, the captain wanted to get the thing cleaned up, then reduce the workload, then work out what was wrong. They cleaned up - he used the a/p to reduce the workload, and as they were starting to diagnose the aircraft bit them. His workload reduced his SA (along with the stick shaker) to a critical point. The pilot failed due to excess workload, not due to lack of "airmanship".
HundredPercentPlease is offline