The pilot’s operating handbook (POH) or airplane flight manual (AFM) checklists help make certain the airplane is configured properly before beginning the takeoff roll. Professional flight crews supplement this “hardware” checklist with a pre-takeoff briefing covering the “software” considerations, the pilot decision-making process that accompanies takeoff. Examples include: What are the unique hazards affecting takeoff? What performance expectations apply to this departure? How will I know if I’m not getting the performance needed? What is the route, and what altitudes to use getting from the airport to cruise? What will you do in the event of an emergency?
If you’re not a career pilot, you likely haven’t been trained in formal pre-takeoff briefings. Yet we know the ultimate outcome of a flight depends on the decisions we make, the software of flying. I’ve tried for years to come up with a quick, concise pre-takeoff briefing. I queried friends in the airlines, corporate and military to see what they used, in the hopes I could apply it to my flying. Everything I found was too complicated to adapt for single-pilot training and enthusiastic incorporation into everyday flying. So how to develop an easy, single-pilot-friendly pre-takeoff briefing checklist?
ASK THE EXPERTS
I could have come up with a checklist on my own, but I’d vastly prefer to have something that benefits from the input of many experienced instructor pilots. So I put together a breakout-group exercise for flight instructors at a recent American Bonanza Society training event. I challenged the instructors in breakout groups to create a usable, concise pre-takeoff briefing checklist consisting of no more than seven steps. Their faces told me they thought this would be a challenge indeed.
The result was a great discussion and a white board full of suggestions for pre-takeoff decision verification. As a group, we looked at the common elements and narrowed it down not to seven but four basic steps to a pre-takeoff briefing. The result is what I call the T-E-N-E (“teeny”) checklist. The sidebar at the top of the opposite page breaks down what the acronym stands for.
SANTA FE DEPARTURE
Just as with the takeoff itself, there are a lot of decisions involved in the T-E-N-E checklist. As with any risk-management analysis, you shouldn’t be making these decisions at the hold-short line. The T-E-N-E checklist is a structure for considering all these items during your preflight planning, plus a format for quickly reviewing and reinforcing those decisions just before you take off.
By way of illustration, let’s say I’m taking off in a Beech Baron from Santa Fe, N.M. (KSAF) to Wichita, Kan. Skies are clear and winds are light for departure, but clouds partially obscure the mountains east of the field on a direct route of flight. As I prepare for the journey, I consider all these items, plus many more. The sidebars on this and subsequent pages of this article extract one of the four elements of the T-E-N-E checklist format and expand on at least one theme.
On a proposed flight like this, there’s a lot more to consider than if launching on a trip or two around the pattern, and every bit of it potentially is vital to a safe takeoff and departure. Consciously thinking about it as you plan your departure, however, makes it possible to quickly make most of the decisions before you’re actually flying the airplane. Use the T-E-N-E checklist to remind you to review all this information in an abbreviated fashion just before taking off, like this:
“I’m making a high density altitude takeoff in a fairly heavy airplane in a high traffic area. I’ve confirmed all checklist items are complete. I have a slight crosswind from the right.”
“I’ll attain about 23 inches manifold pressure at full throttle and lean the engines to approximately 1300 degrees F EGT. I should be at 60 knots at five stripes down the runway and lift off about 11 stripes down the runway.” (It can help you evaluate performance if a willing front-seat passenger is briefed to count runway stripes aloud during your takeoff roll.) “At liftoff I’ll raise the nose to VYSE. I’ll delay gear retraction until I confirm a sustained positive rate of climb.”
An alternate method is to estimate your liftoff spot using references off the left side of the runway, where you can see it during liftoff, and then a second reference about halfway to that spot. This works well on contaminated or unpaved runways, which often are shorter with non-standard markings, if any. You may even have to pace off this distance before you get into the airplane—you need to select these references with some degree of accuracy.
After reaching 400 agl, I’ll turn southeast toward the VOR and climb to 11,000 feet unless directed otherwise. On course is southeast from the VOR once reaching 11,000 feet. Alternately, if conditions permit, I’ll request ATC for a visual climb, assuming obstacle clearance responsibility myself. If granted, I’ll turn left toward my first fix while climbing to 11,000 feet. Otherwise, and if I need to climb in the hold, the hold at SAF has an inbound course of 334 and an outbound heading of 154. Hold entry will be by teardrop with an initial heading of 120.”
“Any failure to meet power targets on the runway means an abort. Any power loss in the air: PUSH and HOLD; if able to climb, do it straight ahead to the 7500-foot pattern altitude and return to land. If unable to climb or a total engine power failure, PUSH attitude and HOLD heading, identify and verify the failed engine and feather its propeller, climb to at least 7500 feet before making only very small changes in heading, and aim slightly left if needed for an off-airport landing. Best-case, single-engine climb rate will be approximately 200 fpm in zero-sideslip flight. If I need to return for any other reason, climb straight ahead to 7500 feet.”
Remember this “teeny” pre-takeoff checklist and incorporate it in your preflight planning. It’s quick, it’s easy and it’s a great last-minute reminder of the many decisions you make preparing for every takeoff.