Tommay85
Well-Known Member
Yeah I see what you're getting at, I would throw your example into my "immediately unsafe condition" condition. Hitting another plane would be pretty unsafe if that was the reason they wanted you to hold altitude.As mastery of both is so key. It is never an "if," but when you're going to mash the wrong button at some point and have to unscrew yourself. Recognition of the FMA as well as seeing the pitch/power changes that you expect to see is absolutely critical. For example, if you are told to discontinue the approach on the 320 but maintain current altitude and "tap TOGA" just out of rote habit, you've just screwed yourself into a 1000 foot high parabola if you try to button click your way out of it. Or, you can just go "ah shiat!" and turn off the AP and not have to do paperwork.
Including your anticipated level of automation in your briefing I think is a good thing so the other guy can anticipate and hopefully trap any errors that may come up... and also if your plan changes, let your partner know so they can be on the same page. Team environment!
