Oh, Deer (Part 2)

Fuel Planning

ByAndrew Robinson December 2, 2015February 11, 2016

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.

Oh, Deer (Part 1)

ByAndrew Robinson March 7, 2017April 5, 2017

As far as I knew when I woke up, October 26, 2016 would be an ordinary day for me. It was a Wednesday, and I was scheduled to fly our Company’s BE58 Baron on a charter from Wings Field (KLOM), a non-towered airport just north of Philadelphia, to Pittsburgh International Airport (KPIT) and spend the day there waiting for my 3 passengers to finish up their meetings. The plan was to fly them back to Wings that evening and then make the short hop back to home base at Lancaster, PA. (KLNS).

It was a flight that I had done countless times, and I was comfortable with the airports, the passengers, and the airplane. Everything went smoothly that morning and my short flight from Lancaster to Wings was uneventful. I even made it there in time to spill coffee all down the front of my pants before my passengers arrived. The weather was clear, calm and beautiful as we loaded into the Baron and the sun was just starting to come up as I taxied toward runway 24 for departure. I was departing VFR and had an IFR plan on file which I intended to pick up with Harrisburg Approach once we were airborne. According to my calculations, I was on schedule to be drinking my coffee at the Pittsburgh FBO right around 8:30.

At 7:05, I advanced the throttles for departure. A few moments later, I received a very unpleasant surprise. I was quickly approaching rotation speed when 2 deer ran onto the runway directly in front of the aircraft. It was still dark enough that I was relying on my landing/ taxi lights to illuminate the runway for take-off.  As a result, I was unable to see the animals before it was too late. I don’t remember making a conscious decision to pull back on the yoke, but it was that or plow directly into them at about 85 knots. I pulled up as quickly as I could and the airplane rotated immediately.  A fraction of a second later I heard and felt a sickening THUD.

There was no doubt that I had hit one of them, but, somewhat unbelievably, the airplane was climbing as though nothing had happened. I put the nose down to get the airspeed back up and began to try and piece together what damage the airplane had sustained. Based on the noise and the feeling of the impact, my suspicion was that I had hit the deer with the left main landing gear. A review of the instrumentation showed no abnormalities and the airplane was behaving normally, so I didn’t suspect any damage to the airframe/ flight controls. I couldn’t see anything out the windows that looked unusual, and somewhat unbelievably I still had 3 green lights.

After gaining a safe amount of speed and altitude, I turned around and told the passengers that we had hit a deer. It was obvious that we had hit something and I was sure that they wanted to know what was going on. Then, I checked all my indications again and satisfied with what I was seeing, tried to bring up the landing gear. No dice. When I pulled the gear lever to the up position, the master “GEAR UP” warning light came on and I got a horn. There was never any change in the 3-green indication and the gear motor never came to life at all.

At this point it was obvious that, minimally I was going to have to divert to Lancaster and have the maintenance guys look at the airplane to see if anything was broken. I figured that they would either give me the green light to continue or I would just jump into one of our PC12s and complete the trip while they worked on the Baron.

The landing gear’s refusal to come up was my first indication that there was substantial damage. I set course for Lancaster and called our Chief Pilot. After explaining the situation to him, we agreed that KLNS was the best option and that he would let the maintenance guys know that I was coming.

The logic was that proceeding to Lancaster would allow a visual check of the landing gear by maintenance people as well as the tower and result in the safest outcome if an emergency landing were required. Lancaster would likely have better services available in terms of emergency responders and, not to mention, I was fairly certain that there was a dead deer on the only runway at Wings that I didn’t feel like hitting for a second time. In addition, the relatively long runway at Lancaster combined with light traffic at that time of day made it the ideal option to divert to.

I again turned around to brief the passengers. I told them that we were going to have to make precautionary landing before continuing to our intended destination and that I would be performing a few low passes for the tower.

Due to the drag from the landing gear, the flight to Lancaster seemed to take forever. The long cruise home, however, gave me time to try and reach someone on the ground at Wings in hope of having the runway inspected and cleaned off before other traffic tried to use it. After several attempts to raise anyone on the Unicom/ CTAF frequency, I called Philadelphia Approach for help instead. Philly answered right away and I explained to them what had happened. I requested that they call over to Wings on the phone or send someone out to check the runway. They told me that they would get it done and asked if there was any other way that they could assist me. I told them I was headed to Lancaster and that I appreciated their offer, but didn’t require any further assistance. I then switched over to Lancaster Tower and let them know that I was about 15-20 minutes out, but I would need to perform a couple of passes to have them check my gear. The tower cleared me for a low approach over runway 26.

I arrived at LNS at about 7:30. I performed my first low pass by the tower, not really expecting anything to appear out of place. I figured I had bent something or damaged the squat switch, but not much more. I climbed to pattern altitude and awaited the good word. Shortly after the fly-by, Tower reported that the left main gear didn’t appear to be down and locked. They suggested that I make another pass. The airport maintenance personnel chimed in, reporting the same. We had just started discussing whether cranking the gear a little by hand might help when Philly approach called the Lancaster tower on the phone.

Philly informed Lancaster that someone had inspected the runway at Wings and found the left main strut and wheel in the grass. I quickly concluded that cranking the gear down probably wouldn’t help!

To Be Continued…

(Read Part 2 Here)

Andrew Robinson is an airline pilot for Piedmont Airlines.  He is a former 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania.  He instructs in Beechcraft Bonanzas.

Lightspeed Headsets and Modern Audio Panels

ByHank Gibson February 1, 2018February 9, 2018

I love Lightspeed headsets.  They are very comfortable, durable, and reasonably priced.  Plus, when you call Customer Service, you are actually talking to someone who works for the company and knows what they are talking about.

One thing to watch out for with Lightspeed headsets is the Mono vs. Stereo option.  On the Zulu 3, there is a very small control panel underneath the battery compartment to change from Mono to Stereo.  If you have any kind of modern audio panel, you will definitely want to do this.  Here’s why.

I was flying in a Cirrus SR22 G5 last fall with a Garmin 350 Audio Panel.  Everything worked fine talking to the ground and tower controllers.  Once I took off and was switched to approach, everything went quiet.  I could hear the approach controller, but couldn’t transmit.  I thought my headset had bit the dust. There was another set in the plane that I switched to, but I thought the transmit function of mine was out.

I sent the headset back to Lightspeed for repair.  The headset was still under their 5 year warranty, which is really nice!  I got it back a few days later, plugged it in to another Cirrus, and still had nothing.  I was getting frustrated, but then a light went on.  One of my colleagues had mentioned something about mono and stereo in the Lightspeed.  I popped the batteries out, flipped the switch over to stereo, and wa-la!  Everything was fully operational.

If you get Lightspeed headsets, you’ll want to make sure it is set on Stereo, as they all come from the factory on Mono.  If you get a PFX, there is an easy access button on the side of the battery unit to switch from Mono to Stereo.

Aviation News: The Formation of ONE Aviation

ByHank Gibson April 30, 2015May 1, 2015

Earlier this month, Eclipse Aerospace and Kestrel Aircraft merged to form ONE Aviation.  Most pilots are familiar with Eclipse, who makes the Eclipse 550 jet, but not many have heard of Kestrel Aircraft.

Kestrel Aircraft is run by Alan Klapmeier, co-founder of Cirrus Aircraft and brother to Dale Klapmeier, who still runs Cirrus.  Klapmeier joined Kestrel in 2010 and brought innovation to the K350 Turboprop design that Kestrel was developing.  Kestrel has been lacking in investors to further their project, but the merger will help a lot in getting more funding.  Klapmeier assumed the CEO role for ONE Aviation.

The merger will also help bring more innovations to the Eclipse 550.  The original Eclipse Jet was a miserable failure and the company went into bankruptcy in 2009. The Eclipse Jet came back to market in 2013 as the Eclipse 550 with many much needed improvements, including making GPS a standard amenity.

Klapmeier and his genius will lead ONE Aviation in good directions.  The K350 will come to market a lot sooner as more investors will be drawn to the company, while the Eclipse 550 will continue to see new and innovative developments.

Cirrus SR22 Owner Completes First Solo

ByHank Gibson July 31, 2014

Congratulations to Monte James who, on July 31, 2014, completed his first solo flight!  Monte is the owner of N565TV, a 2007 Turbonormalized Cirrus SR22.  N565TV is a G3 model with an Avidyne panel.  Monte was very excited to complete his solo flight.  He reported very good landings during the flight (he even said the last landing, which was probably his best yet, caused him to break into laughter!).  Texas Top Aviation’s Hank Gibson, Monte’s instructor, took pictures and continued the tradition of cutting Monte’s shirt tail to commemorate the flight.

Congratulations to Monte!