I think there are two threads here. There's the questions for the report - complex interactions between systems and pilots.
Then there's the 'keep it simple stupid' of not letting it happen to you.
PF must fly the aircraft at all times!! Simple as that. If the autopilot's engaged on the approach you should still be covering the controls and scanning the instruments as you would on a manual approach.
What I see an awful lot of when training people is that PF feels he/she is not doing enough if they are 'simply' flying the aircraft. There's an almost guilty need to be seen to be doing more.
But give the PF a slight distraction as the autopilot is levelling off, and there's a good chance they'll bust their altitude. Why? Because they're not actually flying the aircraft!! Ask any trainer worth their salt.
Next time you're PF, have a good honest look at how often you're not actively flying the aircraft and then think about this thread.
Looking to a wider perspective, I think there can be problems with the emphasis on systems knowledge over good old fashioned airmanship and CRM in type training. I've experienced over zealous trainers showing off their own technical skills and perhaps nit-picking when pilots fly 'ugly' but safely, ie, not using the automatics in the sophisticated way they'd like.
I'm not for a moment saying systems knowledge isn't important, but we have to be clear where it lies in our list of priorities, given that there is only ever a finite time to be spent on training.
The thing I hear myself saying over and over in the sim is 'just fly the thing'. I think we need a re-emphasis on the basics.
I'll admit at times when I've moved to a new type that my technical knowledge of the systems has not been what I'd like it to be. But I've felt confident in my safety because I know it's still just an aeroplane that conforms to some very basic laws of physics like all others.
Fly the aeroplane.
Last edited by Maximum; 8th March 2009 at 11:29.