When I began my ab initio training, it seemed to take forever to get off the ground. Working through the preflight, before-start, run-up checklists, step-by-step in the order provided seemed to take up a lot of time I wanted to spend airborne. Of course, with practice comes efficiency. Eventually I would complete the steps in the checklist by memory, and then verify they were complete using the checklist. Cut to my first job flying and there was a name for this method of checklist usage: flows.
WHAT ARE FLOWS?
Different companies and flight schools have different terms for types of checklists, but for the sake of this discussion I will keep it to two types: challenge-response and do-verify. Challenge-response involves doing the checklist line by line, similar to how I used to complete checklists during my initial training. There is a time and place for this method. A good example is preflight, where distractions can be mitigated and minimal time pressure exists. Do-verify involves completing the steps in a certain order and subsequently confirming everything is complete with the checklist. For the context of this article, the first step of the do-verify is the flow. The FAA does not define flows or publish generic guidance on them, but essentially they are a memory technique for completing checklist items or ensuring that the aircraft is configured appropriately for a given situation.
So far, I have associated flows with checklists and normal flight operations. Their usage can extend to normal or abnormal situations. Many aircraft publish memory items, which should be practiced and memorized as flows. Additionally, I would consider flows to include memory-aid techniques such as the ever-famous GUMP check many use to ensure landing configuration in complex aircraft.
I spoke earlier about transitioning from challenge-response to do-verify as I gained more experience. As I grew comfortable with this method, I saw two benefits. The first was everything was double-checked. I ran through the items, and then confirmed everything was in order using the checklist. Secondly, interruptions became less of an issue. If I read a checklist item that requires a step or two, it was easy to get distracted and lose your place. Either you end up restarting the checklist to ensure a step was not missed or you push ahead and hope for the best. (Not that I have ever forgotten a checklist item this way, but I have certainly heard of it happening.)
Eventually, I saw more benefits. I grew comfortable with the aircraft in a number of configurations, so if a switch was missed or inadvertently pressed, it was easier to catch. If a non-standard situation popped up, or something had to be done out of order, it could be quickly accomplished without losing situational awareness of the flight path. Now I can picture many pilots out there flying a Cub on floats who have no need for this diatribe on checklist usage, but in my experience it’s the pilots who are a little relaxed with checklist usage who utilize flows the most. Consistent checklist usage is still the best bet to mitigate risk.
As I try to discuss risk mitigation techniques, I often notice how some of these techniques result in opening up new avenues for risk. Something that is important to remember is overall reduction of risk is the end goal, so do not let the perfect get in the way of the good. In this case, the biggest downside in my experience is checklist complacency. See the sidebar on page 15 for ways to combat this.
Maybe it is just the huge aviation nerd in me, but developing a flow is actually a fun process. Initially, whenever I am flying a new aircraft, I see if the manufacturer has any published memory items. Then I sit in the aircraft and chair-fly the procedure, seeing how the patterns look. The flow for engine failures in the Skyhawks I flew during my initial training was a backward-shaped L, beginning at the floor-mounted tank selector and ending with the ignition at the instrument panel’s lower left. This allowed easy memorization of a five- or six-step procedure, and more importantly, it is something that can be easily recalled in times of extreme stress.
Once the memory items are taken care of, it’s worth reviewing the other abnormal and emergency items. Some items, like anything involving smoke or fire, should probably be committed to memory whether it be a flow or acronym. It may seem like I am pushing for a lot of memorization, but it is strategic.
For example, during a flight review, I don’t ask applicants to recite each and every airspeed they may use. If there is a placard or marking on the ASI (and the applicant knows about it), that’s good enough for me.
Memory can be a tough thing, though. How often do we study for an event (like a written test or checkride), complete that event, and then experience the proverbial brain dump? Some may be able to juggle all those numbers and procedures, but I sure can’t. So we save that precious processing power for no-time items.
Like the aforementioned smoke and fire, some procedures need to be done immediately to prevent emergencies from getting any worse. Additionally, that situation may lead to your hands being too full to even reference a checklist. Combined with the stress a true emergency presents, a well-designed flow can be life-saving.
FOLLOW THE SEQUENCE
A good flow moves through the cockpit in the most sequential order possible. This might not always be easy, because steps that need to be completed in a certain order may jump around. But if you can make a pattern, and that pattern ensures all the steps are completed and indications are checked, it will be a lot easier to complete in a timely fashion and it will stick more readily than memorizing the steps one by one.
Another benefit is you can design flows that consider two different outcomes. For example, in one of the aircraft I flew, there was an engine troubleshooting flow that took two different steps depending on the fuel flow. If there was still fuel flowing, we would take Path A. Otherwise, Path B would be appropriate.
Now, flows can be used for more than just abnormal and emergency situations. The nice thing about flying your own aircraft is you can design your own checklists and procedures. Using the manufacture’s guidelines, you can design a flow that makes sense for your cockpit layout and the way you fly.
An example of how I implemented a flow that saved me a lot of headaches more than once was a quick pre-preflight. I knew that once I dropped my bag off, if I had to add oil or there was a major issue—such as tire damage, bird strike, etc.—it would take some time to resolve, and so I should take care of it sooner than later. So before even entering the aircraft, I would check the engine oil level and ensure no major damage occurred to the aircraft since it was last flown. If I found a low oil level, I knew I would have to allocate time to find a ladder and grab oil from the hangar so the aircraft stayed properly stocked. Obviously, a low oil level in some airplanes is a lot quicker to solve, but the example stands. I essentially worked in an extra walk around, outside of requirements of the company or manufacturer, strictly for my convenience. The convenience also prevented me falling behind during the preflight, which I personally find helps prevent rushing.
While thinking about and conceptualizing this article, I thought of all the different flows I have used in the different airplanes I flown. Some were self-taught, others were company requirements and many I picked up as recommendations from fellow pilots. Usually they were the result of missing something or optimizing a procedure after experience in an airplane.
This is another reason why I always advocate flying with others when the opportunity comes up, and it does not have to be with someone more experienced that you. I often learn a new technique from a pilot fresh in a new role, especially considering the potential for new perspectives. Additionally, it is always a good idea to perform some small after-action report when a mistake comes up.
Like most of us, I am still waiting to fly the proverbial perfect flight. Since it has not happened, each flight presents a learning opportunity. If you find yourself the victim of not verifying something or forgetting to flip a switch, consider adding a flow to your toolkit to prevent the mistake from happening again. It is a great way to keep working toward that (probably impossible) perfect flight.
After a career as a Part 135 pilot, flight instructor and check airman, Ryan Motte recently got hired by a major airline and is now flying as a Part 121 first officer.