Single Pilot Cockpit Techniques, Part III

Use your autopilot.

I give you the conclusion first, and if that’s all you need, fine, but autopilots are much misunderstood and therefore misused, and are worth some further thought.

The Basics. Autopilots are classified by axis, one, two, and three, corresponding to the three axis about which the aircraft rotates: roll, pitch and yaw. A simple, one axis autopilot, often called a wing leveler, controls the roll axis. A two axis autopilot controls roll and pitch, and in its simplest form is therefore both a wing leveler and pitch hold, with altitude hold, altitude preselect, heading hold and nav tracking being useful complements to the basic roll and pitch commands. A three axis autopilot (often erroneously used to describe a “full” autopilot with altitude hold and preselect and all nav and approach functions), is normally only found on turbine powered multiengine aircraft, and provides for engine out control by the autopilot: the third axis, yaw, provides the rudder power to maintain directional control with an engine out and varying degrees of power from the remaining engine or engines. Even with the third axis of control, it normally is only coupled when in the approach and go around modes: climb, cruise, and descent are normally uncoupled from the yaw axis and still require manual rudder input or rudder trim on the part of the pilot. (The reasons for this are very complex and have to do with autopilot certification standards, balancing autopilot functionality with negative consequences of autopilot failures, a very technical topic beyond the basics of autopilots.)

Some aircraft have yaw dampers (or dampeners), which is not an autopilot per se but does use the rudder to counter unwanted yawing, usually caused by unwanted rolling motions. Sweep winged aircraft are particularly susceptible to this uncomfortable rolling, yawing motion—the dreaded Dutch Roll—which on earlier swept wing aircraft could reach uncontrollability if left unchecked: one of the required maneuvers on the Boeing 727 type rating check ride was to regain control after the yaw dampener had been turned off and a big yaw intentionally induced. As I remember, the yaw damper was a no-go item. But a yaw damper is not part of the autopilot system and is not powerful enough to negate the adverse yaw resulting from an engine out.

Any autopilot is better than no autopilot, but the minimum for single pilot VFR flight is a single axis, or wing leveler, type autopilot (and with a heading hold or heading bug could be quite useful), while the minimum for IFR flight would be a two axis with at least heading hold and altitude hold. Each allows you to let go of the aircraft in order to do all the other things a single pilot has to do: read charts, set power, lean mixtures, write down frequencies, keep a flight log, pick up the pencil that dropped on the floor, change fuel tanks, look ahead and so on and so on. The reason I believe you need both heading hold and altitude hold for IFR is because altitude control is so much more critical on an instrument clearance than it is on a VFR flight. If the altitude nudges upward or downward a hundred feet or so VFR while looking away, you haven’t violated an assigned altitude clearance, the aircraft is still firmly under control, and a little pressure or pull on the control column will easily get it back on altitude again. But the same thing IFR is a serious enough deviation from your assigned altitude to either cause problems with ATC if left uncorrected, or take so much attention that whatever it was that you needed to do besides fly the aircraft doesn’t get done.

Pilots often feel that using the autopilot is a sign of weakness—a crutch—and if the best pilot in the airplane is the autopilot, there is some truth to that. An autopilot is no substitute for basic flying skills which, in the case of an instrument rated pilot means more than just being able to hold altitude and heading, but also being able to shoot accurate approaches to minimums. And there is no substitute for hand flying to keep those skills tuned. But assuming your basic flying skills are acceptable, and you could hand fly the airplane throughout its full profile from climb out through the approach if necessary, there is absolutely nothing wrong with using the autopilot so that you can concentrate on the rest of the job—managing the flight—without the distraction of having to constantly keep scanning and correcting. That’s what it’s there for.

A couple of examples from the world of turbine aircraft may help illustrate this. The Cessna Citation SP is certified for single pilot operation, but only if the autopilot is functional. Makes sense. And let me tell you a little secret: It is an incredibly easy airplane to fly, much simpler than a typical reciprocating general aviation twin. The straight wing is as forgiving as a Cessna Skylane, with near centerline thrust an engine out is very easy to handle, and the power couldn’t be easier to manage: one power control, push forward for more, pull back for less. The fuel is either on, off, or crossfeed. The rest of the aircraft systems can be covered in a day of ground school. And the FAA still requires a fully functioning autopilot to be flown single pilot.

MNPS (Minimum Navigational Performance Specification), the document that describes equipment and procedures necessary to fly from FL 290 to FL 410 over the North Atlantic, one of the most heavily trafficked, non-radar controlled airspaces in the world, specifies that an autopilot be used at all times when in that airspace. Aircraft separation along these tracks is predicated on accurate tracking of course and very accurate maintenance of altitude, and it simply won’t allow for a pilot’s momentary lack of concentration. Anytime you’re in congested airspace, you would be wise to do the same.

At ATA Airlines, we trained to hand fly approaches to below standard minimums, and were required to demonstrate, on our check rides, the ability to hand fly an engine out approach to minimums and then do a go around. But in line flying it was ATA’s policy to do all approaches to minimums on the autopilot, and to do all Cat II (below standard minimums) and Cat III approaches (no minimums) using not just one but all autopilots, which in the case of the Boeing 757 meant all three autopilots (two for the Lockheed 1011). The reason for that was mostly redundancy—if one failed at normal minimums the approach could be continued to an autoland on the remaining autopilot or autopilots—but also accuracy: each autopilot monitored the other both for deviations from standard and for increased accuracy. If airline pilots have to use three autopilots in certain circumstances, I wouldn’t feel too bad using one. Again, that’s what it’s there for.

So train by hand flying and practice by hand flying when conditions allow, but the rest of the time, use your autopilot. It’s one of the best ways to make your job easier, your results better and, all things considered, be a better pilot.

Single Pilot Techniques, Part II

A previous post, “Single Pilot Techniques, Part I,” attempted to set the stage for this second part by comparing the differences between adding cockpit crewmembers and subtracting them. The conclusion was that it is a relatively simple matter to add crewmembers, adding a copilot to a single pilot operation or a flight engineer to a two pilot operation, but it is much more difficult to reduce crewmembers. I won’t attempt to summarize the full argument here, but the most important point is that the lessons learned in reducing from three man crews back to two man crews (and, of course, that means women as well), can be applied to the single pilot cockpit as well.

The main problem in reducing crewmembers is not, as you might think, increased workload, but reduced redundancy: as aircraft systems were simplified, the two man crew was able to take on systems management, just as the three man cockpit of an earlier era was able to take on what was formerly the navigator’s functions as long range navigation systems were simplified and improved. What was lost was the extra set of eyes and ears. Procedures and policies had to be created to compensate for this diminished back up capability. Those same policies and procedures, plus an additional safeguard that I will suggest toward the end of this post, can be used to compensate for the complete lack of another set of eyes and ears in the single pilot cockpit.

By way of introduction to those policies and procedures, let me relate a little story as background. Two years ago one of my very best friends, Claudio Guerra, chef/restaurateur and aircraft owner/pilot, and I were planning on flying his Cessna 310 from 7B2, Northampton Airport (Massachusetts) to Oshkosh, and then on to Half Moon Bay on the west coast where his wife and daughter were visiting friends, also not far from our apartment in San Francisco. As part of our preparations we went out flying together to help me get familiar with his airplane. If Claudio was nervous flying with a retired airline pilot and former flight instructor he didn’t show it, but he did get a little apologetic doing the before takeoff checklist: he went through a little drill, one he had memorized and that moved from one part of the cockpit to another, taking care of all the essential pre takeoff items, without a checklist. Then he took the checklist out and said, “I have all the checklists memorized, so I don’t really need this, but whenever I’m flying with passengers I take it out and go through it again just so they don’t worry.”

Actually, while I think he should do it that way every time, passengers or not, what he was doing was exactly what a careful single pilot should do. He had developed a cockpit flow for each phase of flight, and backed it up with a checklist. (There is a reason checklists are called “check lists”: they check that things have been done: they are not “to do” lists, although there are times when we use them that way; the Before Start checklist, for example, is often in reality a “to do” list, and that’s okay because nothing else is going on at that point.) Flow patterns with back up check lists are two of the key elements developed by the airlines for two man cockpits to compensate for the lack of a third crewmember.

Let me give you an example of how flow patterns and checklists work, one taken from the ATA Boeing 757 manual. Checklists normally follow the flight profile: before engine start, engine start, taxi, before takeoff, and so on. At each of those points there is a flow pattern established for each crewmember with a check made to insure that everything is set for that phase. This example is the check at top of descent, or just as you are getting ready to start down. The flows are divided between the pilot flying and the pilot not flying (or pilot monitoring, as it was later called: management and training types love to play with words, as if getting exactly the right word will make everything alright. We argued for years, for instance, whether the parking brake would be “set” or “parked.”) For the pilot flying the flow is:

Ensure shoulder harness is ON.

Push the EICAS [Engine Indicating and Crew Alerting System] Recall switch to display existing Alert Messages.

Arm the Autobrake Selector as required.

At 18,000 feet the Captain will place the Wing Landing Lights ON and at the Captain’s discretion any other lights ON.

Passing FL 180 call “DESCENT CHECK.”

For the pilot not flying the flow is:

Place seat belt selector to ON or flash if already ON

Check the performance of the pressurization system and verify that destination airport elevation is set.

Return the lower EICAS to secondary engine display.

Ensure shoulder harness is ON.

Read the DESCENT checklist.

So at this point the cabin is being prepared for approach and landing, the pilots are legal (shoulder harnesses required for approach and landing), the pressurization has been set to start a gradual cabin descent to destination altitude, the overall aircraft systems status has been verified okay (or dealt with previously), the autobrakes system has been set up and the lights are on leaving positive control airspace. And all of this was done from memory, using a basic flow pattern which is top to bottom in this case—seat belt sign and pressurization controls are on the overhead panel, the EICAS is in the center middle panel, the autobrakes lower left panel, then, at FL 180, back up for the landing lights—with the checklist called for after the flows are complete.

So what does the actual DESCENT checklist look like?

Guess what the first item is? Challenge: SEAT BELT SIGN Response: ON

The next item? Challenge: PRESSURIZATION Response: SET

Followed by: Challenge: RECALL Response: CHECKED

Challenge: SPEED AND ALTITUDE BUGS Response: SET & CROSSCHECKED

Challenge: ALTIMETERS TRANSITION LEVEL Response: [local altimeter setting] CROSSCHECKED

Challenge: APPROACH BRIEF Response: COMPLETED.

The first three items confirm that the flow pattern was accomplished successfully; the last three cannot be done from memory, as part of a flow, since they will be different each time: speed and bugs depend on landing weight, altitude bugs on the approach expected, the local altimeter setting is given as part of the descent clearance to an altitude below the transition level (FL 180 in the US), and, of course, the approach briefing depends on the approach; the checklist makes sure these keys items have all been done.

So what does this have to do with single pilot operations? Most single pilot aircraft don’t have seat belt signs, certainly don’t have flight attendants, seldom have pressurization systems or system status monitors or autobrakes and are seldom operated in positive control airspace. But they still need to be prepared for approach and landing; this is the beginning of another phase of flight, from cruise to descent, so this is still a good place for some checks. Fuel management is the first that comes to mind: do fuel pumps need to be on for the descent, is fuel on the fullest tank or on the mains if required for anything other than level flight? What about pitot heat or carb heat? Will the descent descend into visible moisture at or near the freezing level? Will windshield defrost be needed? Is the current altimeter setting set, have you checked the destination weather and/or ATIS, is there an arrival procedure if IFR or nonstandard pattern if VFR, and so on. Each aircraft will have different areas of concern, but all will need to be prepared for approach and landing, and top of descent is a good place to start.

Here is a possible flow for the Piper Twin Comanche C, a relatively representative general aviation single pilot aircraft, beginning at the top left and working left to right, top to bottom:

Altimeter set
Power for descent set
Engine instruments checked
Fuel quantity checked
Vacuum checked
Ammeter checked
Autopilot set as required
Windshield heat as required
Landing lights as required
Pitot heat as required
Cowl flaps closed
Fuel Mains selected

This may sound like a lot to do and to remember, but it’s not with an organized flow. This flow starts with the altimeter, right in front of the pilot (and certainly doesn’t preclude checking all the primary flight instruments including resetting the heading gyro to the magnetic compass, if not slaved, but that check can and should be done on a regular basis anyway). It then moves across the panel to the throttles for descent, a quick check of engine temps and levels right under the MP and RPM gauges, down to the fuel quantity gauge, then down a level and back to the left to start over again, checking vacuum and ammeter gauges, the autopilot in the center (on or off? trimmed? altitude preselect set?), over to the far right again to check windshield heat, then down again, to the lower level of the panel, left to right, checking lights, pitot heat, and cowl flaps. Finally, down to the floor, where the fuel selectors are on the Comanche, to select or verify fuel on the mains, which are required for takeoff, climb, descent and landing.

You would then want to back up your descent flow with a written checklist. This would probably not need to repeat every item on the flow, but would want to hit the important points and add any items that should be done here that do not fit into a flow, items like checking weather and airport information. One possibility might be:

Altimeter SET
Autopilot AS REQ
Windshield heat AS REQ
Pitot heat AS REQ
Cowl flaps CLOSED
Fuel ON MAINS
Weather CHECKED
Airport/approach CHECKED

Flows and corresponding checklists should be established for each of the key phases of flight:

Before start
Before taxi
Before takeoff
Climb
Cruise
Descent
Before landing
After landing
Shut down

These flows and checks are key to safe two man cockpit operations, and will also work well with single pilot operations. But I said at the beginning that there was something else I would talk about toward the end to supplement these flows and checks for the single pilot operator. First I want to review what we normally take completely for granted, but what is worth thinking about for a moment anyway, and that is, why do we have checklists? The obvious reason is to make sure we have done everything we’re supposed to do to prepare the aircraft for safe flight. That’s true, of course, but there is a simpler and more fundamental reason: we do it to keep from killing ourselves.

Way back when I first starting flying professionally and was transitioning from recips to jets, one of my captains said something that made a big impression on me at the time. He said, “There are four things that, if not set properly, will kill you on takeoff in a jet: speed brakes, trim, flaps and slats, and the parking brake.” He went on to elaborate: "If the speed brakes are out on takeoff, it won’t fly; If the trim is miss set, it either won’t rotate when you want it to, or will when you don’t; If the flaps and slats aren’t set for takeoff, it won’t fly, and if the parking brake is set it may move but it won’t accelerate normally. They can all kill you. So every time, just before I push up the power, I do a quick scan: speed brakes stowed, trim set, flaps and slats for takeoff, parking brake released. Haven’t killed myself yet.”

Takeoff for a reciprocating engined straight wing aircraft is different, so when your primary flight instructor emphasized the importance of correctly setting the trim and flaps for takeoff, it wasn’t because your Cessna 152 or Cherokee 140 wouldn’t fly if they weren’t set properly, it was because he or she was trying to instill good habits. But there are two key points here that are relevant to checklists and flows for all pilots. The first is that all of these critical items should have been taken care of well in advance of taxiing onto the runway and bringing the power up as part of the normal Taxi/Before Takeoff flows, and if they weren’t they should have been caught when the checklist was read. The second is that even if they weren’t done and weren’t caught, this last double check will catch the really big ones, the ones that left undone will kill you.

A final double check is what pilots flying by themselves can do to, in effect, back themselves up: after all the flows have been done, and after all the checklists have been completed, at each of the key phases of flight they can make a quick scan to make sure the really big things, the things that left undone will kill you, have been done. And it needs to become a habit that is done every time to be effective.

I’m not going to attempt to cover what those items should be for a bunch of different types of aircraft, but I can give you an example that I am hopeful will be a model for you to develop final checks for whatever type of aircraft you do fly. Again the example will be based on the Piper Twin Comanche, for no better reason than that I happen to have a manual handy.

First, what are the critical phases of flight? Obviously takeoff and landing are, but are there others? There certainly are other times enroute when the opportunity to do something catastrophic presents itself: descending too soon or too low on an instrument approach or trying to land at the wrong airport VFR, for instance, but those aren’t aircraft problems—problems with the configuration or functionality of the aircraft—those are pilot problems. And while forgetting to raise the gear after takeoff or leaving the power set to climb power at cruise or reducing the power to descent but forgetting to reset or disengage autopilot would be serious errors, they probably aren’t going to kill you. Not right away anyway—you have time to correct and recover. So I think it is safe to limit the really critical phases of flight to takeoff and landing.

We’ve already gone over what can kill you in a jet on takeoff, but what about the Twin Comanche? Speed brakes aren’t a factor and the Twin Comanche is normally flown flaps up for takeoff (except for a short field takeoff which I don’t recommend for any twin and certainly not for the Twin Comanche where best angle of climb and minimum control airspeed are the same), so flaps are not usually a killer here either. So what is? Fuel for one. The Twin Comanche can only use fuel from the mains for takeoff, and, of course, there has to be fuel in those tanks. What does happen if the gear handle is in the UP position on takeoff? Of course it shouldn’t be, but if it is, as soon as some weight comes off the struts but before it can fly, the gear will try to retract, with what could be disastrous consequences. (Okay, it probably won’t kill you, but it’s a major accident for sure.) Finally, is the directional gyro in agreement both with the magnetic compass and with the runway? Why is this critical? What if it is set wrong and you fly the wrong heading after takeoff. Worse, what if you’re on the wrong runway, one that is too short, or is closed, or one that has power lines at the end, or that intersects another runway being used for landing? It only has to happen once.

That’s probably it for critical items for a VFR takeoff –you’re not trying to redo the entire Before Takeoff Checklist, just a last minute double check of the items that can kill you. For an IFR takeoff I would add a last minute check of the vacuum pressure and the ammeter: vacuum pumps are notoriously unreliable, which is why the Twin Comanche has two, and a quick last minute check that neither of the red buttons on the vacuum gauge is visible would confirm that they are both working, and with the ammeter gauge right beside it a quick check of alternator output insures you’re not going to be on battery power just as you fly into the clouds. Both vacuum and electrical power are essential to safe instrument flight.

So for a VFR takeoff the last minute check would be directional gyro heading, runway and compass agree (all at the top of the panel), drop down to check the gear handle down, across to the far right to check fuel quantity and then down to the floor to check that the fuel selectors are on the mains. For an IFR takeoff (and I would do it this way every time if instrument rated, just to be consistent) after checking the DG I would drop straight down and check the vacuum gauge, the ammeter and then go on to gear handle, fuel quantity and main tanks. That should keep you from killing yourself on takeoff.

Now, landing. I find it sometimes useful to carry an argument to its logical extreme to check its validity: if it seems to make sense a little bit, then it should still make sense if extended to its most extreme case. For example, Daily Saving Time: Good Idea or Bad? (My daughters dread the changeovers each year because they know they’re going to have to listen to me go off again on how stupid I think it all is. So there’s my answer already.) If Daily Saving Time is a good idea because it gives us an extra hour of daylight at the end of the day, then wouldn’t two extra hours be even better? Why not carry the argument to its logical extreme and add 12 hours? Then we could have day light all night long.

In the case of determining critical items for landing, the logical extreme would be to ask what would happen if we did absolutely nothing? If nothing adverse happened, then there wouldn’t be any critical items. So what would happen if we adjusted the power and airspeed as necessary to land, but left everything else as it was at cruise, not even checking the engine gauges, only responding to whatever happens? For the Twin Comanche at cruise the gear would be retracted, the flaps up, the power would be 75% or less, the prop would be back—RPMs would be reduced—the fuel could be set to any tank, mains, aux, tip, with anything from almost full to almost no fuel in it, the boost pumps would be off and the cowl flaps would probably be partially if not fully closed. So let’s assume either a total idiot or the laziest pilot every known starts down from cruise and doesn’t do anything. What would happen?

Initially, probably nothing would happen. But at some point fuel management, or mismanagement, would probably rear its ugly head: fuel wouldn’t flow evenly from an aux tank or tip tank on the descent or approach, and power would fluctuate. Or it might simply run empty. So in response our star pilot would presumably do what he knows he should have done and turn the boost pumps on and select fuel from the main tanks which we hope still have fuel in them. Still alive. So everything is going fine again and now he is on approach or in the traffic pattern and everything is still fine: power is well below max for maneuvering and descending so the prop rpms being reduced isn’t a factor, and, surprisingly, the mixture still at the lean setting for cruise doesn’t seem to be causing any roughness because the power level is reduced well below max, and the cowl flaps being closed are also not causing too much of a problem for the same reason. So Captain Clueless continues on around, lines up on final, or breaks out on approach, trucks on down to the runway, crosses over the numbers, reduces power for landing and the landing gear warning horn goes off. Now he has a problem: the mixture is lean, the props are not set for go around power, he is closer to stall speed than he thinks because the flaps aren’t out and the only thing that is going to save him from a gear up landing is a go around and the aircraft is not configured to do that. He may be able to save it by pushing everything forward or he may not: a second’s hesitation or pushing only the throttles up and the next thing he’s going to hear is props striking the runway. Or the worst case scenario, one engine powers up right away and the other hesitates. The next sound is going to be louder than props hitting concrete.

So, surprisingly, when you look at this extreme case, there actually isn’t that much that is absolutely critical on approach and landing, but there are some, and that’s what we want to be sure we double check on short final. (You may be wondering why the lack of flaps didn’t already get him before the gear not being down did, and they might have if he weren’t careful with his speed control and angle of bank, but the simple fact is that landing flaps for general aviation aircraft don’t decrease the stalling speed all that much; their may function is glide path control. For the Twin Comanche, for instance, the difference between clean and dirty stall speed is only 6 knots, and at a recommended approach speed 30% above the dirty stall speed, that still leaves a good margin—not something to do intentionally, but it won’t kill you.) What will kill you, or as a minimum hurt you and your airplane, is running out of gas at a low altitude, trying to land with the gear up, and trying to do a go around with less than full power. So I would say that the critical items, the items requiring a last minute double check for the Twin Comanche would be: props and mixtures full forward, gear down green light, and fuel on mains. (Sounds a lot like the old GUMP checklist, doesn’t it?) And you could develop a quick scan for this double check by reaching over to make sure the props and mixture controls were full forward, a quick downward glance for the green light, and then reach down to feel for the fuel selectors on the mains. And I would make a point of running this double check at the same point each time, maybe right after lining up on final, or as soon as possible after breaking out on approach. If you do that every time, you’re never going to unexpectedly run out of gas on final or land gear up, and you’re always going to be able to extract yourself if, for any reason, landing is not possible.

These are techniques, borrowed from airline practice, for safe single pilot operations: develop cockpit flows for all key phases of flight, back up your flows with checklists, double check the critical items before every takeoff and landing. Anything else? These techniques will take you a long way, but there are a couple of other things you can do, and they both are meant to counter complacency, distraction, and boredom. One is to stay involved, and by that I mean do things: keep a log, check the weather, get the whiz wheel out and compute the true airspeed or the pressure altitude, experiment with different prop and power settings, reset the mixture, figure the winds aloft, ask ATC if they have winds for any other altitudes and get the performance manual out to see if it’s worth climbing or descending, anything to stay involved. Don’t just sit there.

The other thing, and I learned this from one of my check captains transitioning from copilot to captain on the Boeing 727, maybe the same one who inspired the heading and title for this blog, is to look around. Don’t just sit there staring at the primary instruments in front of you. Look around. All the time. Look up, look down, look to the left, way left to the side panel, right to the entry door and latch, even look back. To paraphrase Yogi Berra, “You’d be surprised what you can see if you just look.” You’ll catch a thing or two, a switch out of place, a breaker that has popped, a latch that isn’t catching completely, and you may even be inspired to get out the flight manual and review how something works that you see that you don’t normally use, like an alternate air selector. You are providing your own set of extra eyeballs, the ones that are missing because you don’t have a copilot or a flight engineer. It’s not easy flying without help. These techniques should make it easier.

Greeters

I wrote about my last flight as an airline pilot in a post called “Last Flight,” published in September 2007. What I didn’t mention there was that as I exited the aircraft, going through the terminal, I was greeted by locals who meet every military flight coming and going through Bangor International Airport, thanking the troops for what they have done and what they will do. It’s a program that started during Desert Storm and has continued every day and night of the year since—Thanksgiving, Christmas, New Year’s, doesn’t matter.

I was reading The Wall Street Journal this morning, as I do almost every morning, and I came across a review of a show to be shown on PBS on Veterans’ Day, November 11, at 900pm, Eastern Time. It is part of a series called P.O.V. and the specific show is called “The Way We Get By.” The show is about the greeters, what they do and why they do it. It sounds great. It’s about time these people were better known, and I hope it inspires others. PBS gets a rap for being the “nuanced crowd’s” network of choice, but this sounds like the right thing to do on Veterans’ Day.

This photo was taken as I was leaving the aircraft, looking back. It is being fueled and catered for the leg outbound to Shannon. The greeters are just behind me. The troops had already deplaned to stretch their legs, and, if they were smart, have one of the Bangor Airport snack bar's famous lobster rolls. It would have to last them for a year, when they came back through Bangor, and were thanked again.

Single Pilot Cockpit Techniques, Part I

We all start out in single pilot aircraft. That doesn’t mean single seat aircraft, it means aircraft that only require one pilot to be flown. (And that doesn’t mean they can’t be flown by two pilots—most aircraft do have dual controls—only that they were designed to be flown by a single pilot.) We first encounter the reality of a single pilot aircraft on the day our flight instructor steps out and says, “I think you’re ready to do this on your own. Take it around three times and taxi back here. Have fun.” Suddenly the airplane is empty and you have your first experience with single pilot operation.

Aircraft that require two pilots come in two varieties, those that are designed that way from the beginning, and those that are required to be operated that way by the regulatory part under which they are operated. Those that are designed to be operated by two pilots do not have to have all pilot controllable items—switches, levers, circuit breakers, knobs—accessible from the left seat, they only have to be accessible from one seat or the other. A dead give away to whether an aircraft was designed to be flown by one pilot or two is to look at the gear control lever: if it’s on the left side of the cockpit it’s a single pilot aircraft; if it’s on the right side it’s a two pilot aircraft. (Professional pilots often use the phrase, “I pulled gear for so and so…,” meaning “I was a copilot for so and so.”) Aircraft flown by two pilots have what every first solo pilot wants: someone to help. So for the pilot going from a single pilot aircraft to a dual pilot aircraft, the transition is fairly straight forward and simple: just keep doing what you always have, but let your copilot help. Help can include everything from “pulling gear,” letting you concentrate on flying and not having to reach blindly for the gear handle or glance away at a critical moment, to handling the radios, keeping track of the flight log and fuel management, programming nav computers, digging approach plates out, or anything else you want him or her to do. In professional practice, pilot often “swap legs”, alternating flying and non flying duties, and in the co-captains arrangement (my least favorite mode of crewing) they alternate seats as well, the captain for each leg alternating and sitting in the left seat. (It is my least favorite because it often leads to blurring the line between the pilot in command and the second in command. But that’s a story for another day.)

There aren’t any aircraft being designed any more for a three man crew (I guess I have to say “three person crew,” but when these aircraft were being designed, “three man crew” was how they were described), but there used to be lots, in fact the three man crew was a crew member or two less than those before them that also had navigators and radio operators. The third crewmember was a flight engineer, a non flying position, and his (or her) primary job responsibility was aircraft systems management, primarily the engines but also all systems associated with those engines: electrical, hydraulic, pneumatic, fuel, pressurization. It was a big job because these were big airplanes with very complex systems, multiple redundancies, and very specific troubleshooting and reconfiguring checklists. The transition from a two man aircraft to a three man aircraft was not so simple: you had more help, but how you put that help to work, and how you divided the duties while insuring that someone was still primarily responsible for flying the aircraft and nothing else wasn’t obvious: it had to be learned.

To see how this works, imagine yourself as the Captain in the left seat of an L-1011 at cruise altitude and everything is going along just fine, nice and quiet, when suddenly your flight engineer says, “Hey boss, I think we’re losing C system—the fluid level is less than half and dropping steadily.” Exactly what this means isn’t the point: in fact, the C system on the 1011 is the main hydraulic system, the one that powers all the flight controls and operates the gear and the nose wheel steering, and while there are backups, and while the gear can still be manually lowered (but not raised) and while the aircraft can still be controlled (by any one of three other hydraulic systems) even if the system is lost completely, losing C system is one of the big ones. (“Big ones” as in the Gary Larson cartoon where the captain announces to the passengers, “Well folks, we’ve got a warning light on up here, and dare if it isn’t one of the big ones.”)

The point is, how are you going to handle the problem? Just before this problem arose, you were the pilot flying—it was “your leg”—the copilot was the pilot not flying, the one handling the radios and the paperwork, and the engineer was leaning back in his chair with his feet on his desk looking at his panel like he always does. So what do you do now? If you try to help the engineer out, who’s flying the airplane? You could have the copilot try to help him out, but as a practical matter it is a lot harder for the right seat pilot to turn around and see what the engineer is doing than it is for you, you just have to turn sideways in your seat, and in any case, do you really want to just turn this problem over to the two of them while you just sit there? Probably not, so what you do is you say to the copilot, “I’m going to work the problem with the engineer. Your airplane.” meaning you, the copilot, are now the pilot flying, and the copilot would acknowledge the transfer by saying, “My airplane.” This means he has to handle the radios and paperwork as well for awhile, but at cruise that shouldn’t be a problem, and he can always ask for a little help if he gets overloaded, and it leaves you free to turn around in your seat and work with the engineer on the problem, going through the checklist carefully, agreeing on what you are seeing—a lot of checklists are, in reality, troubleshooting trees, with lots of “If this, then do this, if not, then do this” type commands—and confirming that he has his finger on the correct switch before pushing it: this would not be a good time to inadvertently disconnect one of the other hydraulic systems. So a big part of being a captain with a three man crew is learning how to best manage that crew, and the best way to learn it is as a copilot, watching captains deal with the problems that do come up. The next best way is in training, and the least best way is The Hard Way, or what we euphemistically call “experience”. The point is, going from a single pilot operation to a two pilot operation was fairly intuitive, but going on to a three crew operation was not.

So traditionally, meaning during the time I was coming up as a pilot, the normal progression was from student pilot to single pilot in command, then to copilot and captain of a two man operation and then eventually at some point usually through the same steps to captain of a three man crew (often with a stop along the way as the second officer, as pilots who are trained and serve as flight engineers are called in airline jargon). But over time things changed; As manufacturers learned to take advantage of computers and more robust, more reliable, and ultimately simpler aircraft systems, the flight engineer, or second officer, was eliminated, first on large two engine aircraft such as the Boeing 757 and 767, and then on all aircraft, Airbus 330/340s, MD-11s, 777s, even later models of the 747. And crews that had flown for years with three crew members, and who had gotten good at working together and relying on each other, had to learn to make do with just two crewmembers again. And that turned out to be a whole lot harder than learning to go from a single pilot to a dual pilot operation.

The main difference between going from a single pilot operation to a two pilot operation, versus going from a three man crew back to a two pilot operation, is that the single pilot is already used to having to do everything himself, whereas the pilot of a three man crew is used to having, and working with, lots of help. The single pilot who suddenly finds himself with a copilot has to learn to use that help, and the pilot who suddenly loses his flight engineer has to learn to make do with just the two of them. Each has some learning to do, but it is very different for each.

One of the main differences is that the three man crew is used to having back up: with three crew members, someone is always looking out for the other two, whether it is the flight engineer monitoring the radios or the captain backing up the flight engineer on his panel or the copilot monitoring the captain as he flies an approach. A good sort of dependency develops among an experienced crew—I can’t begin to count the number of times in my 727 or 1011 flying where one crewmember caught a mistake that the two others had overlooked, and no one crewmember had a monopoly on it—each made mistakes, and each caught mistakes. I used to say, as part of my standard crew briefing with pilots and flight engineers I hadn’t flown with before, “If you see something you don’t like or don’t understand or something that doesn’t seem to make sense, speak up. If it’s a mistake developing and we can correct it and keep it right here in the cockpit, it isn’t a mistake,” meaning if we can correct it before there are any negative consequences—something someone outside the cockpit is aware of—we’ve done our job.

The problem with that, with what I call a beneficial dependency, is that when you go back to the two man crew, you have to learn certain techniques to compensate for the fact that you don’t have that backup anymore. With a two man crew you are, of course, aware of what the other pilot is doing, but each has his job responsibilities and neither has the luxury of being able to just sit back and monitor the other. The airlines were very concerned with this lack of backup capability when the two man aircraft came back into their fleets, much more so than they were with the more obvious question of whether the aircraft could be flown safely and reliably without a flight engineer. So they developed some very specific policies and procedures to insure flight safety with just two pilots. Those policies and procedures are the subject of my next post, “Single Pilot Cockpit Techniques, Part II,” because those techniques also apply to pilots flying by themselves without any help at all.

Bonding

About to head out for Day Three marshaling for The Presidents Cup, and wanted to let you know that yesterday, before the start of play, I had a nice long conversation with Freddie Couples. He was on his way to the driving range and as he went by my position I said, “Good luck,” and he said, “Thank you.” And Michael Jordan in one cart, and Greg Norman in another, almost ran me down on the 18th fairway in a hurry to get to 17 where an important match was winding down. It’s a big fairway and I still somehow managed to find the one spot where they needed to go. But they smiled as they went by and we’re all still pals. All in all, I’m having a pretty good time.

Cleared for The Break

This post is about aviation, but it starts out with golf.

Specifically, it starts out with the first practice day, Tuesday, October 6, 2009, for The Presidents’ Cup golf tournament, held at Harding Park in San Francisco, California. This is a match play event between the 12 highest ranking golfers from the United States versus the 12 highest ranking golfers from the rest of the world, except Europe. (The reason Europe is excluded is because the more famous Ryder Cup pits the US versus the best European golfers. The Presidents’ Cup is, therefore, a “Ryder Cup” for the rest of the world.)

My wife and I volunteered to be marshals for the event, marshals being the people who control the foot traffic and tell people to be quiet and stand still while the golfers are hitting and putting, and yesterday we were assigned the task of controlling a fairway pedestrian crossover, using ropes to open the crossway when there were no golfers taking shots or walking down the fairway. All in all, a great way to see a lot of great golf, and great golfers. (And celebrities too. Michael Jordan for one, former Presidents Bill Clinton and George HW Bush for another.) But, and this is big, this is also Fleet Week in San Francisco, meaning the Blue Angels are in town. And, in fact, manning my gate early on with nothing much to do because the golfers were still several holes away, I heard an aircraft noise that had that sound that is hard to describe but is the sound that military fighter aircraft have and civilian air transports do not. I looked up, and there, out past the golf course running north up the shore line, were seven gold and blue F-18s, six in tight formation, one solo behind: The Blue Angels demonstration team plus the two seat, support and training aircraft. I mean, here I am, on a great golf course, a beautiful fall day with temperatures in the high 60’s, watching some of the most famous golfers in the world (yes, Tiger Woods, but also Freddie Couples, Greg Norman, Ernie Els), while The Blue Angels fly by. For me, at least, you just couldn’t make up a more perfect setting.

That evening, watching the local news, both to see what they covered of the first day of golf but also to see if they had anything on The Blue Angels, there were pieces on both, and for the Blue Angels they noted that they had arrived at San Francisco International Airport (KSFO/SFO) after having done a flyby up the coast and over The Bay. The film coverage showed the flight of six as they made their break for their visual approach and landing. It was a beautiful sight, as only a precision break can be, and it got me to thinking about breaks in general and memories of specific breaks.

The first question that always comes up is, “What is a break?”, and the second is, “Why do they do them?” (other than that they just look like an awful lot of fun to do, and they can, so they do). The Break was originally developed as a tactical maneuver to avoid enemy fire around the base when returning from a mission. The idea was to approach the field, in formation, at pattern altitude but at a high rate of speed. This obviously made it harder for ground fire to hit the aircraft, but left them still in formation and going too fast to land. The maneuver that resulted in their being separated, in trail, and slowed down, was called The Break, and it was done by having each aircraft, one at a time, roll into a 90 degree bank angle, turn 180 degrees, and roll out level on downwind. The 90 degree banked turn dissipated the speed very quickly—an airplane generates essentially zero lift at 90 degrees of bank so the only way to maintain level flight is to trade a lot of airspeed—and, it kept the aircraft within the general confines of the base. With each aircraft breaking off in a carefully timed sequence it put the formation in trail, and from that point on the approach and landing was conventional, a descending base leg, lined up and on speed/on glide path on final, flare over the numbers, landing one after the other.

Whether The Break is still a necessary return to base maneuver is a good question—most bases, both Air Force and Navy, are located well away from any potential enemy—but the tradition continues: fighters always arrive in formation and land after having been cleared for The Break. I saw this on a regular basis after I first upgraded to Boeing 727 Captain at ATA. ATA had a contract with the Air Force to fly personnel to and from Nellis Air Base, North Las Vegas, to Tonopah Air Base, which was near the little town of Tonopah, Nevada, but was, in fact, actually part of a giant restricted area in the interior of Nevada. Tonopah air base was a highly classified test center for stealth aircraft, but the area included everything from underground nuclear test sites to high speed, low level training runs. By the time ATA had the contract to ferry people back and forth the stealth program at Tonopah was publicly acknowledged, but still, parts were highly classified, a base within a base that you could see from the flight line but no one went into without proper clearance. And I mean no one. It was surrounded by fences, spot lights, guard towers, warnings about mines between the fences and machine guns armed to fire at any intruder. So I never got to go in there. But I did get to see a lot of aircraft departing and arriving, both F-117s at Tonopah, and F-16s and F-15s at Nellis. Since Nellis was also the home of the Thunderbirds, the Air Force demonstration team, we occasionally got to see The Break done to perfection, but it was always a sight to see, no matter who was doing it.

Later on I transitioned to Captain on the L-1011, which went all over the world. One of my favorite stops was Naval Station Rota. Rota is near the ocean in southwest Spain, orange, olive, Sherry and Flamenco country. Rota is a joint Spanish-US base (see previous post, “Azores,” for more on joint air bases) and the Spanish had a squadron of Harrier fighters based there. The Harrier is a vertical takeoff and landing fighter, and you have to see these things to believe them, flying fast like a fighter one second, and hovering and taxiing like a helicopter the next. The Break, for them, started normally, approaching the field in formation at high speed, just like fighters always do, breaking off one by one to line up downwind. But when they came across the threshold to land they were still about 50 feet in the air, doing about 50 knots. They decelerated to zero knots by the end of the runway, and, from a hover, rotated in place 90 degrees and taxied in to their spot on the ramp, descended the last 50 feet, and shut down. You just couldn’t believe your eyes: the fighter you just saw going by at 250 knots or so slowing to zero and landing from a hover.

On one of my last trips to the simulator for B-757 training we had some extra time at the end and the instructor asked if there was anything I wanted to try with the remaining time. I said, “Sure, I’d like to see what it’s like to fly The Break. So I lined it up with the runway several miles out at 1500 feet, shoved the throttles forward to accelerate to red line speed, chopped the power over the far end of the runway, rolled into a 90 degree turn, rolled out on downwind below maximum flap extension speed and from there on it was just another visual approach. Kind of disappointing. I think the thrill of The Break comes from, first, being in formation: this is the wolf pack coming back from the kill, with the Alpha Wolf leading the break with his pals following; second, it’s just a lot more exciting to see aircraft roll into 90 degree banked turns, one after the other, than it is to actually do one. Still, it’s got to be a thrill to come back to the field at high speed, in formation, and to hear the controller say, “Cleared for The Break.”

Azores

I watched a food program on the Azores the other night, and watching it brought back good memories of the many times I had been to the Azores flying for ATA. The Azores, a 300 mile long series of islands formed by mountain tops sticking out of the ocean, with Pico, at over 7000 feet, the highest, are technically part of Portugal, but they are a long way from Portugal, well out in the North Atlantic, and have a history and culture somewhat different from the mainland. Because the islands were settled over a period of several hundred years, and because the distances between them are considerable, each island developed somewhat separately with its own traditions and culture. (The locals say they can still tell which island someone is from by the way they talk.) The islands have also become popular vacation spots for the Portuguese, both European Portuguese and Portuguese-Americans, many of whom have summer homes on the islands.

ATA (then American Trans Air) used to have a weekly run every summer out of BOS to both Ponta Delgado on the island of San Miguel, and to Lajes on the island of Terceira—the Boston-New Bedford area is home to many Portuguese-Americans, many originally from the Azores, having migrated there to work in the fishing industries. (I am amazed at what an impact the relatively small country of Portugal has had all over the world—if there is saltwater with fish in it, you will find a Portuguese community. Hawaii, for instance, has a large Portuguese component to its culture.) These flights were extremely popular with the Portuguese-American community for two reasons: one, they were a lot cheaper, being charters, than the scheduled airlines were; two, they were direct flights to the Azores—the only other way to get to the Azores from the US was to go to Europe first, normally Lisbon (Lisboa in Portuguese), and then fly back, a two day affair. So they always went completely full, and since everyone was usually going for a fairly long stay, and since everyone had family there for whom they were taking gifts from America, they were also some of the heaviest loads we ever flew.

Since the Azores were formed from volcanic peaks sticking out of the ocean, as a rule there aren’t many good places for airports. The airport at Ponta Delgado, for instance, was hacked out of the side of the mountain. It is also fairly short (for an L-1011, anyway), and had steep drop-offs at both ends. It was more like an aircraft carrier than an airport, and after a long night of flying, and having just broken out under a heavy overcast after shooting a non-precision, non-radar approach to see that little strip of runway clinging to the side of the mountain, the landings that resulted were also often closer to aircraft carrier landings than they were to air carrier landings. But it was all great fun, and the kind of thing that pilots love to do.

The exception to this rule is Lajes airport, on the big island of Terceira. Terceira is like the island of Maui (Hawaii), in that both were formed when two volcanoes were joined by the outflow from one of them, forming large, relatively flats areas in between. This created a perfect spot, in both cases, for airports.

Lajes is long enough to be an emergency landing site for the space shuttle, and wide enough to handle a B-52 (300 feet wide, versus the more common 150 feet). It was also the first place the pilot of an Air Transat Airbus 330 (August, 2001) headed when he lost power to both engines after a fuel leak over the North Atlantic, taking advantage of its huge runway to execute a safe, power off landing. Lajes has been used as a refueling stop since WWII, and has been a permanent, shared air base for the Portuguese and US Air Force ever since. And that was the other reason for my many trips to the Azores, military charters, Lajes being a regular stop on the US military world wide transportation circuit.

Unlike many shared facilities in the world, where the US military presence is often tolerated but not welcomed, the relationship between the Portuguese and US military at Lajes was very harmonious. (I put this in the past tense because I haven’t been to Lajes for several years now, and I assume this is all still true, but I’m looking back here.) For instance, the two air forces shared a common officers club with a pretty good golf course. You could get an American hamburger or Portuguese grilled squid in a tomato, garlic sauce in the clubhouse, and you could pay for it with either dollars or escudos (now euros). There were no hassles getting on or off the base, and air traffic control was equally professional and courteous regardless of whose air force was handling it.

The only real challenge to Lajes were the winter winds, and since the military operates year round, they couldn’t be avoided. Terceira is in the middle of the ocean, and the winds coming across the North Atlantic can be ferocious in the winter. Compounding this was the physical location of the airport, in the flat part of the island but snuggled up against a long ridge formed by the smaller of the two volcanoes, which caused the wind to curl up and over it and create a strong crosswind in the middle of the runway, while the larger volcano caused the prevailing winds to swirl in the opposite direction. The result was often three entirely different winds over the length of the runway, a headwind at touchdown, a crosswind midway, and a tailwind towards the end. Except sometimes they swapped, and the headwind became a tailwind and the crosswind would switch to the other side—you never really knew, but with three windsocks, one at each end and one in the middle—you at least had some clues. Fortunately, the L-1011 was probably the best aircraft ever made for handling these kinds of conditions, and while you often had a hand full of airplane and couldn’t take anything for granted, you also knew you had an aircraft that could handle virtually anything and would do whatever you asked it to do. It was a challenge but it was also great fun. (I wrote a post in 2008 titled “Track Up” about a particularly nasty approach into Oakland airport. The difference there was that I was then flying a B-757, and while the 757 is a terrific airplane, better than the 1011 certainly in terms of reliability, automation, and efficiency, it is no 1011 when it comes to gusty, crosswind landings. But I was new to the 757 at that point and I didn’t know that yet and expected more from it.)

The nearest town to the Lajes airport was a little place right on the water called Pria. Pria is a very typical little Azorean fishing village with great restaurants and cafes and it was all pretty cheap, too. One summer evening, handing off the aircraft we brought in to the crew taking it out, the outgoing captain said they had found a really great place to eat and we had to check it out, it was just down the beach from the hotel, wasn’t marked real well, but it looked like a big beach house of some sort and was the only one along that stretch, and we just had to try it.

Crew often pass along tips like this because they are always looking for places friendly to American crews and accommodating of our preferences (like separate checks, and not having to wait until 9 o’clock to eat, and menus we can understand), and someone always gives them a nickname like The Broken Chair or The Red Door and everyone knows where they are and what to expect there. I thought I knew every place to eat in Pria, but this sounded like it was worth checking out, and it didn’t even have a nickname yet.

So after checking in and cleaning up we—my copilot and my flight engineer and I—headed down the beach to look for this place. We found a place that had to be it, but to say it wasn’t marked well was an understatement—it wasn’t marked at all. It looked like a private house, with no signs or menus posted or anything that indicated it was a restaurant. It was still early in the evening (but late for us, and we were hungry), so we climbed up the stairs to a veranda and peaked inside and we could see what looked like it could be a restaurant, with a small bar and lots of tables and a door that could have gone to a kitchen, but we still weren’t sure. Then someone appeared inside and saw us peaking in, and came over and opened the door. We said we had heard that this was a good restaurant and wondered if we could get some dinner. He said something vague like, “Come on in, have a seat at the bar,” and disappeared. So we sat there for awhile and eventually someone else came out and asked us what we wanted to drink, and I think we had some beers, and slowly a few more people did come in, older couples mainly, and pretty soon we could smell good food smells, so that seemed promising, but we still hadn’t seen a menu or a waiter.

By now we were getting really hungry, and a little puzzled as to what exactly was going on, so I asked if we could see some menus. Whoever he was at the bar said, “Oh, there are no menus.” I said, “How are we going to know what to order?” and he said something to the effect of “Everyone just gets pretty much the same thing, but if you want I can take you to the kitchen and show you what we have.”

So I said, “Great,” and off we went, the three us, following this guy around in the kitchen and there were big pots of all kinds of good looking and good smelling things all around and I keep asking what each was and he keeps saying, “Oh, you don’t need to know the names, it’s not important,” and I’d say, “But I want to remember what it is so I know what to order,” and he says, “”Oh, don’t worry about that,” and finally we just gave up and figured what will be will be and hoped for the best, which at that point we were so hungry a spoon to lick would have been fine.

So we sat down at a big table, room for probably eight, and someone else comes over and says, “You will want to drink wine with dinner, and here in the summer we always drink Vino Verde, so do you want to order some Vino Verde?” I had never heard of Vino Verde but I knew it meant Green Wine and that didn’t sound so good, but it didn’t seem like it was really a question or a choice, and I looked at the other two guys and they just shrugged, so I said, “Sure, Vino Verde.” (It is actually a very light, slightly sparkling, slightly sweet wine that is perfect in warm weather with spicy food. And it does have a green tinge to it.)

Then, I don’t really remember in exactly what order, other people arrived and some sat down with us at our table, and slowly food started to arrive in big bowls, food I recognized from our kitchen tour, and more Vino Verde arrived and at this point, still having not seen a menu or a price list or any attempt to keep track of who ordered what, we just gave in and started eating and drinking and not worrying about how it was all going to work out. The men at our table, mostly older and very distinguished looking with very good English, seemed to know a lot about aviation and American Trans Air, and we had a great time talking and enjoying the food, which just kept arriving until I realized that we had something from every pot in the kitchen. Towards the end of the meal a very elegant man arrived at our table, dressed with a silk scarf and an expensive looking sweater with a jacket draped over his shoulders and offered us an after dinner drink. We still didn’t know what any of this was going to cost, and had had plenty of Vino Verde anyway, so we thanked him and declined, but he insisted, sat down and we all talked for awhile, still not knowing who anyone was.

Eventually, getting late, we thanked everyone for their company and said we needed to pay and get on our way, and no one seemed to pay much attention to any of that, and finally I said to one of the men who had been at the table since the beginning, and who seemed to be kind of a leader, that this was a wonderful restaurant, but very unusual, and he said, “Well, it isn’t exactly a restaurant. Do you know where you are?” And I said, “Well, I thought it was a restaurant, but I guess not. So where are we?” He said, “We are all generals in the Portuguese Air Force. I am the Chief of Staff. The man who offered you the after dinner drinks is a priest and also the Head Chaplain for the Portuguese Air Force. We all have summer homes here on the island and this is our private club.”

Needless to say we very embarrassed and apologetic, but he said, “No, no problem at all—we see each other enough and it is good to talk to other pilots and it’s our club and we can welcome whomever we want. We hope you enjoyed your evening.”

We never did see a bill but we did leave some money that we hoped went to the staff. I think we played golf the next day. I don’t really remember. We never did give it a nickname.

Big World, Small World

Back in the “old days,” back when transitioning from domestic to international flying usually meant also transitioning from two and three engine narrow body aircraft like the DC-9 and the 727 to three and four engine wide body aircraft like the L-1011 and the 747, one of the first things you noticed was that “the world gets bigger and the runways get shorter.” That’s how a senior captain once described the experience to his very inexperienced 1011 First Officer, me. What he meant was, you start to cover very large distances when you can fly at Mach .85 for nine hours, and you realize what a big place the world is. You also discover that to do that—to carry that much weight in terms of fuel to go that far with a big airplane full of people and bags—that you also need a lot more runway both to takeoff and land. Where you might have been pretty comfortable with a 7000 or 8000 foot runway before, 7000 feet was now a short runway.

But the more you fly and the more people you fly with, the smaller the world gets as well. (But it doesn’t make the runways any longer.) You meet so many people in aviation, and often spend quite a bit of time with them, get to know them well, and then things change—you change aircraft, or bases, or companies, and you never or seldom see them again. But you do meet and see other people who often knew the same people you did. In aviation, it is both a big world and a small world.

I remember, for instance, back in 2004 or 2005, doing a Honolulu turn out of San Francisco on the 757 for ATA, talking to my copilot who, it turned out, grew up in New London, New Hampshire. I told him that I knew New London very well, having lived just a few miles away in Hanover, New Hampshire for four years when I flew corporate jets for AMCA International out of Lebanon, New Hampshire. It turned out that he knew several of the other AMCA pilots as well, no surprise there, but what was a real surprise was that he also knew one of the captains I had flown with at a previous job, Cub Snively, because Cub was also from New London and one of his sons was my copilot’s best friend from childhood. He also told me that, sadly, Cub had died a few years earlier. (Pilots often seem to die young—I joke that it’s the coffee—but more likely it’s the strain we put on our bodies being awake at all sorts of odd hours combined with years of extra radiation bombardment. Or maybe it’s nothing, maybe we just remember the ones who die young.)

I’m thinking about all this right now because I got an email the other day from another former AMCA pilot, Keith Hasperg, who found me because he had stumbled across my blog. I hadn’t talked to Keith in many, many years, going back before ATA, but often thought about him, for two reasons: One, he was one of the funniest and smartest people I had ever known, and two, he was one of the best pilots I had every flown with, a very skilled pilot, but, unlike most “naturals,” very careful and conservative as well. So it was great to hear from him again. But he also had bad news—another of the AMCA pilots, Nate Lake, had died in July of 2007, and I had fallen so out of touch with Nate that I didn’t even know he had died—I just assumed I could call him any time I wanted or go up to New Hampshire and that he would be there. It struck particularly hard because Nate really was one of the best pilots I had ever known, and taught me an awful lot about how to fly airplanes well, simply by his example and his tactful, always diplomatic “suggestions” for better ways of doing things. He was also a great friend, and that doesn’t always happen.

I remember asking Nate once how it was he was able to hand fly the aircraft so well, exactly on altitude and airspeed—you almost couldn’t tell if the autopilot was on or not when Nate flew, except his hand flying was, if anything, smoother than the autopilot. He said that when he was in Navy primary flight training that they trained in tandem seat aircraft, and that his primary instructor carried a small stick with him. Communication was difficult from front to back, so this guy would just tap him on the helmet whenever he saw anything he didn’t like, like the altitude being off by 20 feet. Nate said it just got easier to never let anything deviate than to put up with that d… stick. What it really was was Nate’s careful way of telling me that anyone can do it, you just have to try.

After I left AMCA, I got into aviation writing and eventually got a contract to do what would turn out to be the first edition of my navigation book, The Aviator’s Guide to Modern Navigation. The first person I consulted before starting was Nate Lake because he was also a trained Navy navigator. He read all of my chapters in draft form and caught many mistakes and made many helpful suggestions. I owe him a lot. If it hadn’t been for aviation being such a small world, I never would have found out what a big world it is. If I have any excuse for not having gotten in touch with him later, it was that I thought he would live forever.