Originally Posted by
Redbird611
I tend to think there should be enough systems comprehension to know why the checklist/ECAM is telling you to do something. Nobody should attempt to "John Wayne it" with systems knowledge, but if you understand why you're flipping a switch it can help prevent errors and keep you out of trouble. In a no-****, no-time, multiple failure emergency that isn't in the QRH, good systems knowledge might help you accomplish some of that pilot shiznit. We don't need engineer level knowledge, but I do wonder if we've dumbed it down a little too much.
If you never had to do a single molecule through the system explanation you may be lacking in a general sense of how a fuel or pneumatic system works but a pack is a pack and an engine is an engine. I can't tell you exeacly how many valve are between the high pressure bleed and the out flow valve but I know there are some and the purpose is protecting the sytem and guiding the air where you want it. Also, some I have absolutely no control over and some I use every day. We would get more benefit from immediate action cards with memory items on them. When the stuff hits is no time to try to remember sequence and nomenclature. Read and do. Period. If its not OK to use the everyday checklist by memory wtf are we thinking for critical situations?
Checklist discipline... unless your life is on the line.
I still keep the 737 stab trim runaway hard copy in my bag for that 5th leg of the day or Vegas redeye.