Boris spatsky
Established Member
- Joined
- Oct 8, 2010
- Posts
- 1,860
Dear JB, Boris and WT,
Any thoughts on this story from the NZ Herald today:
<snip>
The AAIB report said: "Although the pilots' actions suggested that they were under the impression the autopilot had disengaged at the moment of the lightning strike, recorded data showed that it had remained engaged."
The report said no technical problems were found with the plane, which is now back in service, and that pilot training now included simulations of this incident.
The AAIB investigation is continuing, looking at crew training, autopilot design, and any "human factors".
cheers
I am not familiar with the actual incident that they are discussing, but in this case it would seem (without reading the entire report), that the crew became task saturated and had an expectation that the autopilot had disengaged, when in fact it had not. Ultimately, the appropriate response was to disengage the autopilot and hand fly the aircraft. Even if you thought it was not connected, most pilots would still press the disconnect button in this case to be sure, especially once it started descending at 9500 feet per minute. It would appear that they had some form of automation dependancy which almost caused Controlled Flight Into Terrain (CFIT).
Automation, in most circumstances, will reduce workload; however, in some circumstances it can increase workload to the detriment of the flight. In these cases, it can be more prudent to disconnect the automation. In the end, every plane is a plane and can be hand flown (although I am not an Airbus guy so could stand to be corrected if that is not factually correct on an Airbus level!).
If you are interested, go to youtube and watch 'Children of Magenta', especially the first 3 minutes. It is a lecture by a senior AA pilot about the pitfalls of automation. Informative viewing.