News

Thunderstorms are not to be taken lightly. I know you have probably heard that many times in your flying career. Weather related accidents account for approximately 25% of airline and GA accidents.

The Airman’s Information Manual suggests giving a 20 mile berth around thunderstorms. If you are an experienced aviator or a newbie please take this piece of advice seriously. At one flight school where I taught, we had the policy of maintaining a 25 mile buffer around isolated thunderstorms. A bit excessive you think? Maybe, but safety is a good thing!

On this particular day, I was operating a Bell Jet Ranger helicopter during a power line patrol. Power line patrol by itself offers numerous challenges. The job consists of flying along electric power transmission lines at approximately 40 feet above the ground at 40 knots. The crew consisted of me (the pilot) and an observer. The observer is an employee of the power company and it is his job to determine which line(s) will be patrolled during the given day. As I fly along the lines, the observer is checking for anything out of the ordinary such as broken, cracked, or even shot out insulators, excessively large bird nests at the top of structures, or woodpecker holes in wooden poles. The observer knows the lines and he is also a great help in letting me know there is a crossing, and potentially higher, line in our flight path. That makes him a true safety asset!
It was late afternoon during the summer and we were about to finish up for the day. We only had about another 10 miles of line to follow before calling it a day. Up ahead, I noticed an isolated thunderstorm near our power line. I could see the heavy rain falling below the anvil shaped leading clouds. It appeared to be well beyond the end of our day’s work so we pressed on.

As we drew closer to the thunderstorm, we were suddenly tossed up on our left side like a dog toy in mid-flight! It seemed like we were 90 degrees to our normal cruise attitude and, to make it worse, we had the doors off on that hot summer day. I was able to recover and we did an immediate about face and high tailed it home. Forget the rest of that line, tomorrow is another day.

The destructive force of thunderstorms cannot be overstated. In addition to extremely heavy rain, they can contain strong wind shear, large hail, and severe turbulence, each of which can damage or destroy an aircraft. Take care when one of these bad boys is near your flight path. Give it plenty of respect and a lots of room, for safety’s sake.

Alan VanDoren is a 7000 hour ATP pilot.  He has flown both fixed wing and helicopters as a police pilot, missionary pilot, flight instructor, and most recently as an EMS pilot.  He has flown in five countries around the world and also teaches university level aviation courses in his spare time.

Courtesy AOPA.org

We spend time training for them, but real-world emergencies are rare enough that it’s easy to get complacent. They don’t always happen to “other pilots,” though, and preparation can make a big difference when things don’t go as planned:
• What if you lose 500 rpm during takeoff, but the engine is running smoothly?
• What if the ammeter drops to zero during a flight in IMC?
• What if your left aileron develops a strong vibration in flight?
Our new seminar is full of expert tips on handling those “up here, but wishing you were down there” scenarios. We focus on how to keep abnormal situations from becoming full-blown emergencies, offer advice on keeping critical problems under control, and give our best advice on off-airport landings.

Find an AOPA Emergency Seminar near you!

• Monday January 11, 2016-The Woodlands Waterway, 7pm-9pm
  • 1601 Lake Robbins Drive, The Woodlands, TX 77380
• Tuesday January 12, 2016-Wyndham Houston West, 7pm-9pm
  • 14703 Park Row Blvd., Houston, TX 77079
• Wednesday January 13, 2016, Holiday Inn San Antonio Airport, 7pm-9pm
  • 77 NE Loop 410, San Antonio, TX 78216
• Thursday January 14, 2016, Omni Austin Hotel at Southwark, 7pm-9pm
  • 4140 Governor’s Row, Austin, TX 78744

Some of a pilot’s favorite words are heard on the ATIS:  “Winds, Calm.”  These words set off all sorts of happy bells and hallelujah choruses.  Most pilots spend their lives fighting the winds.  On those rare days when the winds are calm, great happiness ensues.

But, are calm wind landings more complicated then everyone thinks?  Well, they can be if the proper planning doesn’t go into them.

Let’s think about wind.  We have surface wind and we have winds aloft. Sometimes the surface winds are calm.  When this happens, certain airports have preferred calm wind runways which are supposed to be used in these conditions.  Winds aloft are almost never calm.  95% of the time, there is some kind of wind even 100-200 feet above the surface.

Here is the question pilot’s face when coming into an airport with calm winds: which runway do I use?  Do I use the calm wind runway?  Do I use the runway that is easiest to enter the pattern for?  Do I use the one with the shortest taxi?

A lot of technologically advanced aircraft have a wind indicator on the PFD. This tool is often forgotten in calm surface wind conditions.  On the contrary, this is probably the most important tool a pilot can have when figuring out which runway to use when the winds are reported calm.

Here’s why.  That wind indicator is showing the pilot what the winds aloft are. The winds aloft should determine what runway is going to be used.  If the wind indicator is depicting a south wind, then a south runway should be used.  Even if it is a 5 knot wind at pattern altitude, it’ll still be a headwind coming in on final approach.  If the north facing runway is used, that same 5 knot headwind can blow an airplane halfway down the runway before the ground speed drops off enough for it to land.

So, the next time you are coming into an airport and the winds are reported calm, take a look at your wind indicator on your PFD when deciding which runway to use.  It’ll probably save a few go arounds!

Cirrus CAPS pull #55 took place at the beginning of November over Fayatteville, AR.  From initial reports, it appears a clamp broke on the oil cooler, causing a loss of oil pressure.  It does not appear that the engine immediately quit, but an annunciator alerted the pilot that the engine was losing oil pressure.  At this point, it appears the pilot elected to do an emergency descent to an airport below him, but ended up not timing it right, missing the airport and pulling the parachute.

As an experienced Cirrus flight instructor, there appears to be some suspect decision making in handling this operation.  I teach in a Cirrus that if an oil light comes on, given that a pilot has some altitude to work with, it is a better option to physically shut the engine down, leaving control of the situation in the pilot’s hands.  This way, the pilot knows when the engine is stopping and is prepared for it, instead of the engine acting erratically and causing problems on the descent.

After checking the engine gauges and shutting the engine down, a pilot should establish best glide first, not nose down and descend at a high rate trying to make an airport.  Best glide gives the pilot many more options and a lot more altitude to work with, further allowing him/her to plan how to make an airport directly underneath the airplane.

To pontificate, it seems that if the pilot had adjusted the plane to best glide, instead of performing an emergency descent, there is the possibility that Drake Field would have been reachable, the chute would not have been needed, and the driver of the truck would not have had to visit the hospital.  Hindsight is 20-20, but this may be an overall training and decision making issue that may need further emphasis.

The initial NTSB report as well as a link to the CBS story is below.

http://www.cbsnews.com/live/video/pilot-forced-to-deploy-emergency-parachute-in-arkansas/

NTSB Identification: CEN16LA026
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 03, 2015 in Fayetteville, AR
Aircraft: CIRRUS DESIGN CORP SR22T, registration: N857SW
Injuries: 3 Minor, 1 Uninjured.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
On November 3, 2015, at 0950 central standard time, a Cirrus SR22T airplane, N857SW, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed on a road in Fayetteville, Arkansas. The pilot, pilot rated passenger and one person on the ground received minor injuries. One passenger in the back right seat was uninjured. The airplane was substantially damaged. The airplane was registered to WG Aviation LLC, Rogers, Arkansas, and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed. The flight departed from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, at 0934 and was en route to the Waco Regional Airport (ACT), Waco, Texas.

According to the pilot, after departure from ACT he leveled off around 10,000 ft mean sea level (MSL) and was in “VFR on top” conditions. The pilot noticed that the crew alerting system (CAS) flashed a yellow caution light for oil pressure; the engine was still producing power. The pilot notified air traffic control (ATC) of the issue and received vectors to the nearest airport, Drake Field Airport (FYV), Fayetteville, Arkansas. The pilot descended and maneuvered toward FYV as the CAS indicated a red warning light for oil pressure, which had dropped below 10 psi. The engine was producing inconsistent power as the airplane descended to 3,300 ft and FYV was still not in sight due to cloud coverage. The pilot was unable to maintain altitude and the airplane’s stall warning horned sounded. The pilot deployed the Cirrus airframe parachute system (CAPS) and descended to the ground. During the landing the airplane collided with a truck and then came to rest on a four lane road.

At 0953, the weather observation at FYV reported wind from 190 at 9 knots, gusting to 17 knots, 10 miles visibility, clear sky, temperature 61° F, dew point 57° F, and altimeter setting 30.11 inches of mercury.

An initial postaccident examination was conducted on November 4, 2015, in Fayetteville. Engine oil was observed on the underside of the fuselage. The oil cooler cross fitting was broken and oil was observed in the engine compartment.

The airplane’s recoverable data module and three data cards were removed and sent to the NTSB Vehicle Recorders Laboratory for download.

The airplane has been retained for further examination.

A few years ago I took off out of Chicago’s Dupage airport (KDPA) in a Bonanza headed for Deck Airport (9D4), a small uncontrolled airport about 60nm to the west of Philadelphia. It was late November and, unfortunately, due to some unexpected ice, I found myself flying a significant portion of the flight at 4-5,000 feet instead of the 11,000’ at which I had originally planned. This was an issue because I was burning significantly more fuel at 4,000’ than I would have at 11,000’. I did my fuel planning math and came to the conclusion that I would still make it to 9D4 with the required minimums. On I flew, watching the number on the totalizer decrease.

I arrived at 9D4 after dark. Although I didn’t think I would need one, I ended up having to fly an approach to get down below the cloud deck. My troubles weren’t over. After breaking out of the clouds, I was terrified to realize that the runway lights weren’t working.

Now, I had a problem. I was in a relatively unfamiliar area in marginal VFR at night and I was quickly running out of options as far as my fuel was concerned. Fortunately for me, 9D4 is located 14nm north of Lancaster Airport (KLNS), which is a towered airport with very nice approaches and facilities. Also working in my favor was the fact that Lancaster was reporting VFR. I headed as quickly as I could for Lancaster and landed uneventfully.

When I landed I had the required fuel minimums on the airplane, but I managed to scare myself pretty thoroughly. I realized that while I had been forced to deal with some unexpected complications: icing forcing me down several hours before my planned descent and inoperative runway lights that were not listed in the airport NOTAMs. I was very blessed that Lancaster was so close by and that I was able to land without having make an approach. Had LNS not been VFR, I could have easily burned through another 15 minutes of fuel maneuvering for and executing an approach. If, for some reason I’d had to go missed or perform a hold, I would have gone through my remaining fuel pretty quickly. To me, this is a classic example of “just because it’s legal, doesn’t mean it’s safe.” I realized I needed to change how I did my fuel planning.

Since then, I have enforced a personal minimum: 18 gallons must be on the Bonanza at the time I reach my destination. If things change un-expectedly enroute and I realize I won’t make it to my airport with at least 18 gallons, I stop. I had always tried to have an hour of fuel on board as a reserve, but having a hard number is an easy way for me to make decisions.

Having a fuel totalizer installed in an airplane is a really nice way to upgrade the panel and give the pilot a clearer idea of how much gas is being burned/ how much is remaining. The totalizer installed in our Bonanza is a JPI Fuel Flow 450. It has a lot of nice features which make fuel management chores much easier. If a totalizer is something that you are considering installing in your aircraft, or if you have one already, here are a few things that I’ve learned from my experience flying with them.

• While helpful, don’t rely too heavily on the totalizer to do your fuel math for you. Similar to the negative effect that using GPS navigation can have on a pilot’s ability to navigate via a chart, over dependence on digital fuel systems can lead to problems. A fuel totalizer should be telling you what you already know, not doing all your math for you. Do your fuel math and confirm it with the totalizer. If it failed, you should still know how much you have and how much is needed.

• Likewise, don’t rely completely on the accuracy of a totalizer. Technology isn’t perfect, and if the instrument isn’t quite calibrated correctly, the numbers could be wrong. Fuel information is absolutely critical, and thus warrants constant monitoring and double checking. When you do arrive at your destination, keep track of how much fuel the airplane takes and compare it to the numbers on the totalizer to verify its accuracy.

• Unless you are flying an airplane which has a “both” setting, you will still need to be keeping track of how much fuel is available in the aircraft’s individual tanks. For example: our Bonanza has two tanks, but the totalizer doesn’t keep track of that information. If I don’t remember to switch tanks, I can run one completely dry and the digital read out will indicate the remaining gas in the other tank. The totalizer won’t indicate anything about the individual tank quantity until the engine quits and the flow drops to zero.

Pictured below on the left is a fuel selector from a Piper Aerostar. The airplane has two selector valves and three fuel tanks. While the system is not difficult to use, it does require proper understanding and regular monitoring to ensure that the fuel is distributed correctly. The picture on the right is the selector out of an A36 Bonanza. I love the simplicity of the Bonanza’s fuel system, but it still takes attention and intention on the part of the pilot to keep track of how much gas is available on either side.

• The JPI unit that we have installed on our airplane even has an “hours and minutes remaining” screen as well as a “fuel required” screen. The totalizer actually talks to the GPS and is able to tell me how much gas I will need to get to my destination. Just remember that those numbers are computed only at the current flow and do not take into account the potential increases/ decreases in consumption which will occur as power settings are changed for descent and arrival into the airport. I may feel pretty good about my hours and minutes remaining when I’m sitting at 12,000 feet, but when center makes me descend to 5,000’ and I’m still an hour away from my destination, endurance will decrease. It also can’t take into account any additional flight time that may be required to shoot approaches, hold, or divert.

• Have you ever heard of “G.I.G.O?” It stands for “Garbage In, Garbage Out.” What it means is that the information which the fuel totalizer is giving the pilot is only as good as the information that the pilot gave it at the beginning of the flight. The totalizer in our Bonanza does not have any method of checking the quantity in the fuel tanks. At start up the pilot inputs the amount of fuel on board the airplane and the totalizer keeps track of how much is burned which is then subtracted from that inputted number. Ergo, if the amount of fuel is not updated or is incorrect, the fuel total numbers displayed will be inaccurate. If a pilot told the computer that the tanks had been topped off, but didn’t verify it, the fuel could be exhausted and the totalizer would still indicate that there was fuel available. It is, therefore, VERY IMPORTANT to confirm the airplane is fueled to the amount desired (visually if possible) and use the fuel gauges in the airplane to verify the accuracy of the totalizer.

• Use a timer: I like to use the timer on my phone to remind me when it is time to switch the fuel tanks. If I set the phone to vibrate and put it in my pocket, it will remind me to change tanks at the desired time if I haven’t remembered to otherwise. It’s also nice because I can write down exactly at what time (or quantity) I changed tanks so I can keep very accurate track of how much fuel I have in any given tank. This is especially helpful in airplanes that have more than two fuel tanks. Another option is setting the timer on a Garmin 430, 530, or G1000 to give an alert or message reminding the pilot to change tanks at a preset time.

It shouldn’t come as news to anyone that the importance of fuel planning cannot be overstated. I personally know multiple people who have run airplanes out of fuel because their planning wasn’t quite right or the weather changed and they were unwilling to take the time to stop. In the case of my Bonanza story earlier in this article, it was obvious to me before I even landed that I should have picked a fuel stop when it became apparent that I would arrive at my destination with less than my desired one hour margin.

The technology that we have now to help us keep track of our fuel usage is wonderful, but use it as an aid; not as your only source of fuel calculation. Remember to verify the amount of fuel on the airplane before you go because the number on the totalizer won’t mean anything if it doesn’t match the amount in the tanks! Above all, don’t be afraid to stop and get fuel when you need it. I’d rather have to tell the passengers that we need to stop for gas than deal with the potential consequences of running out.

Andrew Robinson is a 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania.  He flies Pilatus PC-12s and instructs in Beechcraft Bonanzas.