Checklists can be life savers. That said, they are for use during evolutions where you have TIME to use them.
BUT, when your engine quits at less than 1000 feet…..that’s not the time to drag out a checklist.
So, you need to develop “FLOWS”. A Flow is a series of checks appropriate to a particular evolution or event. Flows need to be memorized and practiced…..and backed up by a checklist.
Example: An engine failure flow might be something like:
Fuel selector: switch, Carb Heat: Hot, Mags: Left only, right only, Both, And finally: Turn to a selected landing site.
The reason it’s called a “Flow” is that the items in a flow should be arranged in a sequence that starts in one spot and “flows” across (or around, or…) the cockpit.
I use flows ALL the time. In my plane, my before takeoff and before landing flows are identical:
Fuel selector: Both. (Selector is on tunnel between seats, so right hand feels it in proper position….no eye movement required).
Trim: Set (appropriate to evolution, and it’s just fwd. of selector)
Flaps: Set (just fwd of trim wheel)
Mixture: Set. (Not necessarily full rich if at high DA, and knob is farthest right of engine controls)
Prop: Fine pitch. (Prop lever is just left of mixture)
Carb Heat: as appropriate. (Just above and left of prop knob.)
Mags: On Both. (Just left of engine controls)
So, this flow starts on the floor to right of my seat, then forward, then directly up to farthest right control, then across to left.
This flow covers all the essential items in a sequence that’s easy to follow and recall. Repetition for every takeoff or landing builds it into your memory.
THEN if you have time, verify with a paper list.
So, you ask, “What about lights, or seat belts or……”. Lights on or off won’t kill me. Seat belts/harness should have been done already…..another checklist or flow?
Pre flight checklists: These things are great the first few (or many if like me you’re a slow learner) times you fly a particular plane, but after a while, this too becomes a flow.
Now, don’t assume that just because it says “Cessna 172” on the side that all 172s are the same. Example: late (R and S) model 172s have, what? 16 fuel drains……. So, be sure you’re “speaking the right language” for the specific plane you’re flying that day.
But, flows simplify the checklist conundrum and speed evolutions WHERE APPROPRIATE.
So, next time you’re around your plane, sit in the drivers seat, take out the checklist, and figure out some appropriate flows for different evolutions: Before takeoff, before landing, engine out, etc.
Now, when you’re flying, practice those flows, each time VERIFYING with checklist, until the flows are natural.
Finally, this applies to both flows and checklists: It’s really easy to Touch a control, read from a checklist or say what you’re checking out loud on a flow, but to not actually VERIFY the position of that control.
So, a flow should entail put your hand on the control, THINK: “is this in the correct position?”, then move on.
This is NOT rote stuff.
Include in flows only essential stuff. Leave non essentials to printed checklist.
Practice them.
MTV