Real Life Flying: Planning and Executing a Complex Helicopter Charter Flight

It’s not all fun and games.

On Wednesday, the assistant for one of my new clients called. She wanted to know about my availability the following Monday. Her boss wanted to take two companions with him on a flight to seven off-airport landing zones within 100 air miles of his office.

This wasn’t the first flight I’d done for this client. The previous Monday, just the two of us had gone flying to two off-airport landing zones. Two days later, he’d added a companion for a flight to one of those landing zones but had added off-airport pick up and drop off locations. Now, it seemed, he was putting me to the test by filling the helicopter with people for a whirlwind tour of a bunch of properties.

The first two flights were relatively simple, but this last one required some serious information gathering, planning, and math. And that’s the part of real world flying that the flight schools kind of gloss over in their sales presentations and training.

In this post, I want to dissect the planning required for this trip to give folks an idea of what they really need to know to become commercial helicopter pilots.

Feasibility with a Weight Limitation

The very first question that had to be answered was whether or not the flight was possible with my equipment. I fly a Robinson R44 Raven II, which is a remarkably capable helicopter. But every ship has its limitations and I knew as soon as I heard “three men” that I might be bumping up against one of them: weight.

My helicopter, with its new bladder fuel tanks installed, now weighs 1517 empty. Max gross weight — which must include me and the fuel I need to fly, along with my passengers and their stuff — is 2,500. So the first thing I needed to do was calculate the total weight of my passengers plus me, some under-seat gear I usually bring along, and the helicopter and subtract it from the max gross weight.

I asked how much the passengers weighed and got the following information: W: 180, D: 190, A: 240

Normally, I’d add 10 pounds to each person’s weight because everyone lies, but in this case, I knew the numbers were reliable. These folks often fly in a small airplane piloted by my client and I was confident that he got accurate weights from them. I could also weigh them before taking them onboard, but at this point, I wanted to see if the flight was even feasible before I hung up the phone with my client’s assistant.

I did the math on a piece of scratch paper. Me + gear + passengers + helicopter = 2,327 pounds. That’s less than 2,500, so we can fit.

But, of course, we still need to take on fuel — and it has to be enough fuel to get us where we’re going, as well as an airport where we can get fuel if we need it. So more math: 2,500 pounds max gross weight – 2,327 pounds payload (without fuel) = 173 pounds available for fuel.

100LL fuel weighs 6 pounds per gallon. How much could I take? 173 pounds ÷ 6 pounds per gallon = about 28 gallons of fuel.

How long could I fly with 28 gallons of fuel? The helicopter burns 15 to 18 gallons per hour, depending on load. I assumed we’d burn a lot since we would be heavy and I’d be flying at maximum cruise speed. So 28 gallons ÷ 18 gallons per hour = about 1.5 hours.

How far could we go in 1.5 hours? I felt confident that I could maintain an average cruise speed of at least 100 knots. 100 x 1.5 = 150 nautical miles.

Was there fuel available within range? Yes. (After all, it isn’t as if we were flying in the wastelands of Nevada or the Navajo Nation.)

So after all this math, what did I know? I knew that the flight was possible. I could book it.

Planning the Flight So I Know Where to Go

The next challenge was knowing exactly where I had to go. For the previous two flights, we’d had lots of fuel on board and no time issues. I planned the flight based on estimated waypoints, then let my client point me in the right direction to our destinations and guide me to the desired landing zone. Although this worked, it wasn’t the most efficient way to plan and execute a flight. (I can assure you that having a client point in the right direction and say things like, “Do you see that poplar tree?” when you can see about 200 poplar trees within the next five miles is not a very good method of homing in on a destination.) I needed more data in advance.

Although the assistant had initially identified the properties with their names and general locations, that information was pretty meaningless to me. I wanted GPS coordinates that would get me to the property so we could minimize flight time by flying direct. So I did what any computer-literate pilot would do: I asked for addresses.

She sent me a list of the property addresses. One by one, I plugged them into Google Maps. I dropped markers and wrote down the GPS coordinates. I then created waypoints in Foreflight on my iPad and plotted the route. It came out to a total of 205 nautical miles. Clearly, we’d need a fuel stop, but if I planned it right, we’d only need one.

Here’s my thinking on this. I was going to be making several off-airport landings into landing zones I’d never seen before. They could be confined spaces, like the location where I was supposed to pick up my client at the start of the flight. (More on that in a moment.) In a confined space, I’d need to make a steep approach and steep departure. This could be difficult to do with a heavy ship, especially as the day warmed up and performance started to decrease. To maximize safety, I wanted the minimum amount of fuel on board when I needed to make these landings and departures.

The First PlanThe plan I came up with (illustrated here) was to visit the first four properties, which would take us to our farthest point from home. While my clients tended to business at that last property, I’d buzz over to the airport to get fuel. Then I’d come back to get them and we’d hit the other two properties on the way home. This fit in well with my client’s plan.

This assumed, of course, that I did all my fuel calculations properly and we could go that far. By staying on course throughout, I’d have a much better chance of making it work. Otherwise, we could refuel at an earlier stop — most of the landing zones were near a few airports with fuel.

Knowing When to Say No

The First Landing ZoneOf course, the very first landing zone was going to be a problem. It was in truck loading zone on the side of a hill. There were various obstacles in three directions and a steep approach/departure was required. This was my client’s workplace (or near it) and he wanted me to pick up him and his companions there.

I didn’t feel comfortable taking off from that landing zone at max gross weight. It was just too tight with no room for error. So I did something some pilots think you can’t do: I said no to the client.

And the client did something that only the best clients do: he said okay. He asked if I could pick him up there and pick up his companions at the airport nearby, which was on the way. Since I knew I’d have no trouble departing from the big ramp area at the airport at max gross weight, I agreed. Problem solved.

Calculating CG to Determine Passenger Seating

So now I knew that the flight was possible and I had a flight plan to make it work. Next, I needed to know where my passengers had to sit to keep the aircraft within CG.

An R44 helicopter is not easy to load out of lateral CG, but longitudinal CG is another story. Unfortunately, I’m not a small person. Put another very big person up front with me with other folks in the back and a light load of fuel and you’ll get an out of CG situation. (This is just one of many reasons why it’s important for a helicopter pilot to stay slim.)

Out of CGNow, I like to be able to put the biggest person up front with me. Big people usually need more space, including more legroom, and the front seat has more legroom. But when I put 240-pound A up front with me, the CG plot points were outside the envelope. That means that I might not have enough aft cyclic to arrest forward motion. In other words, I might not be able to stop.

In CGSo I recalculated with the big guy in the back. The plot points slipped back inside the envelope. Problem solved.

I do want to point out here that in most cases, it really doesn’t matter where passengers sit in my helicopter. It’s just when we’re heavy with a big person up front that there’s a possible problem.

Getting the Fuel Right

Before I conducted the flight, I needed to fuel the helicopter. (I have a fuel transfer tank on my truck that I use when I’m in Washington.) And I needed to be very precise about how much fuel I added. I wanted to add as much fuel as I could to wind up with no more than 28 gallons on board when I picked up the client’s companions at the airport.

More math.

I figured that between warm up (twice), shut down (once), and travel time to the client and then to the airport from his LZ, I’d run the engine about 30 minutes. At 16 gallons per hour — a good estimate for burn rate during solo or otherwise lightweight flight — I’d burn 8 gallons. So when I left my base, I should have 28 + 8 = 36 gallons on board.

Unfortunately, my helicopter does not have precise fuel gauges. Although they’re pretty accurate, they don’t tell you how many gallons are on board. You have to “guestimate” based on the gauges and your knowledge of how the helicopter operates. I’ve been flying this helicopter for 7-1/2 years now, so I have a pretty good handle on it. I figured I had about 6 gallons on board. That means I needed to add about 30.

Another unfortunate thing is that the fuel meter on my truck’s fueling system is inaccurate. It always understates how much fuel is being pumped. I figure it was understating fuel pumped by about 10%. So if I wanted to add 30 gallons, I needed to measure out 33 gallons with the meter.

I can’t make this stuff up.

And yes, if I were smarter, I’d have an accurate stick for the tanks. But I simply haven’t gotten around to making one.

Conducting the Flight

I was due to pick up my client at 7:00 AM at the first landing zone, which was 20 minutes away. I like to get there early whenever possible — it’s never a good idea to make the client wait — so that meant I needed to leave my base at 6:30 AM.

I needed to remove the blade tie-downs, add fuel — I’d gotten back after dark the night before and was too tired to do it then — and preflight. Then I needed to start up and warm up. So after slugging down an excellent cup of coffee, I walked out of the mobile mansion at 6:10 AM.

(That’s another thing flight schools don’t mention — clients don’t usually have bankers’ hours.)

At the Ag StripIt was a beautiful morning — cool with calm winds. I’m based at an ag strip and I was very surprised that the pilot wasn’t flying. After all, the sun had been up for over an hour and the conditions don’t get any better for spraying crops.

In addition to fueling and doing all my usual preflight stuff, I also cleared every bit of unneeded equipment out of the helicopter. As I loaded this stuff into my truck, I realized that I’d probably been underestimating its weight for quite some time.

The flight to the client’s LZ was uneventful. I arrived right as planned, at 6:50 AM, and shut down to wait.

My client arrived right about 7 and climbed aboard. A short while later, we were picking up his companions. My reading of the fuel gauges had me right around 28 gallons.

Mattawa

Benton City

Ice Harbor

Saddle Mountain

We started with the two landing zones I’d already visited with the client. Because they were working at one property, we landed in a slightly different location nearby. But rather than hit the third landing zone, my client asked to skip over it to the fourth. He suggested that we get fuel after that one and, while I was refueling at the airport, he and his companions would drive to the other property. Because they normally fly in a small plane to that airport, they keep a car there.

Using Foreflight for guidance, I found the next property and then followed my client’s directions to a suitable landing zone. It was another tight spot at the bottom of a hill, surrounded by trees and fruit boxes. I was glad I wouldn’t have to take off at max gross weight from that spot.

But as I shut down the engine and they drove off with the man who’d met them there, I started wondering whether we’d actually make the next airport. It seemed that our fuel consumption was higher than I expected. It could have been the added time for the cool down and warm up at each destination. I studied the gauges and didn’t like what I saw. The airport was 15 miles away. I should have enough fuel to make it with the reserve, but would I? Would I see the dreaded low fuel light?

Of course, I worried for no reason. We made it to the airport with fuel to spare. The biggest challenge was finding the FBO ramp at an airport I’d only been to once before — and that time, from a completely different direction. They drove off in their car and I shut down, then went inside to place a fuel order. Then I had lunch: a granola bar and a bag of cookies.

(Yep, that’s another thing the flight schools don’t tell you about: the joys of finding a meal (or a clean bathroom, for that matter) when on a job.)

By the time they returned, time was short. My client had to be back at the office by 1 PM for a meeting. We had enough time to visit one more property, then headed back home. I dropped my client off first, made an easy departure from that confined space with light fuel and just the two bigger men on board, and then dropped them off at the airport.

When I lifted off solo with only about 10 gallons of fuel on board and no extra junk under the seats, the helicopter seemed to leap into the sky, tilting backward at a crazy angle. But that’s only how it seemed after being so heavy all day long.

I was back at my base by 1:30 PM.

Looking Back

I’d flown a total of 3.1 billable hours and had landed at five different off-airport landing zones, two of which I’d never been to.

This was not a difficult job, although planning did require a lot more effort than most of my jobs do. Just figuring out where I was going based on street addresses was a chore that took at least 30 minutes to complete.

But most of our flight time was spent over farmland with very little time over “remote” areas. That takes a lot of stress out of the flight. In the event of a problem, I could always set down at a farm for help. Not so with many of the flights I do in Arizona — some of which are in areas so remote that aircraft have been known to disappear for over a year.

My client and his companions also made the trip very enjoyable. Although they talked business most of the flight, they also joked around with me and answered my few questions about some of the farms and orchards we flew over. After years of flying in Arizona’s desert, it’s quite refreshing to get a view of a whole different world from my seat. Having passengers who can help explain what I’m seeing really makes the flight enjoyable for me.

But I like this client for a more important reason: he understands the value of the service I offer with my helicopter. On the way back, we talked about how much time it would have taken to drive to the same places. They agreed it would have taken at least 7 or 8 hours just do do the driving. We did it in six, including stops as long at 30 minutes in some places. And although my client could fly faster in his plane, he can’t land at each of the properties. He has to spend additional time driving between them and the closest airport. A helicopter can land onsite — that saves time, too.

For people who know that time is money, money spent flying is money well spent.

Sometimes, I REALLY Love My Job

I experience a “magic moment” in the course of doing my summer job.

A little backstory…

Cherry drying (or blowing) is one of those things most folks don’t know about. The short version is this: in the two to three weeks before the cherries are ready to harvest, if they get rained on they can split or rot, making them unmarketable. If a grower loses 50% or more of his crop to splits or other water damage, he won’t bother picking at all and the entire crop is lost.

So to protect the crop from this kind of damage, growers hire helicopter pilots with helicopters to stand by during the period before harvest. When it rains, they call us out to hover low over the trees. Our downwash blows the tree branches and shakes the water off the fruit, “drying” it. It’s tedious work that requires a good bit of concentration to deal with wind and obstructions. And it can be dangerous — in fact, there were three crashes in the area last year, one of which took a young guy’s life.

This is my fifth season doing this kind of work.

It was late afternoon on a day with drifting storm clouds. I was on call for cherry drying and had already gone out once, earlier in the day.

When I wasn’t flying or prepping the helicopter, I’d spent a good part of the day watching the weather radar on my iPad. Various colored blobs were drifting across from the west, after a gradual shift from their southwest to northeast direction earlier in the day. Rain varied in intensity from a light drizzle to torrential downpour. Every time a storm hit or missed an area, there would be another one right behind it to possibly do the same. Sometimes the rain was so intense that the storm would drain itself and the colored blob would fade as it tracked across the screen.

I was only on contract with one orchard: a 30-acre block of mostly very mature trees near the Columbia River. The grower was very careful about his orchard and, during the vital period, normally spent all day just about every day among his trees. Sometimes he’d mow the long strips of grass in the aisles between them. Other times he’d tinker with the tractors and other equipment he needed to care for his crop. Still other times, he worked on his shop, patching insulation, repairing a roof, adding a wall. Smart phones and good cell service — not to mention a good pair of eyes — had made it relatively easy for him to track the weather throughout the day. But he occasionally called or texted me at my base seven air miles away, where I had a better look at the sky and a bigger screen to watch the radar blobs.

I saw the storm coming on radar and confirmed it with a look outside. It was across the river to the west, heading right for the orchard. While there was a chance it might rain itself out before it arrived, I suspected it might not. Already still suited up from my flight a few hours before, I headed back to the helicopter to pull off the blade tie downs and prepare to fly.

Low CloudsThe sky was intensely dark out toward the river and the storm was definitely heading in my direction. But what was even scarier was the low hanging cloud near me that seemed to be swirling gently like something from a Weather Channel tornado special. I watched it for a while, wondering whether the storm was really intense enough to get a tornado going. It didn’t seem to be.

My phone rang. It was my client. “Work your magic,” he said.

It took me a second to comprehend his words. “It didn’t even start raining here,” I said.

“It poured like hell on the orchard,” he told me. “It’s stopped now. Come on out and dry.”

I hung up and moved my truck out of the way. By the time I was hurrying back to the helicopter, big raindrops were falling on me. The swirling cloud was gone.

I started up and began the warm up process. It wasn’t until I was pulling on my helmet that I realized I’d forgotten to take my door off. This could be a problem if the sun came out and it warmed up; the helicopter would become like an oven every time I faced the sun. But the sky was dark and that didn’t seem likely. Ah, little did I know…

By the time I lifted off the pad, the rain was dumping on me. The cockpit bubble was wet with a million drops. I pushed the cyclic forward and accelerated into my climb. The drops ran off the sides, clearing the window enough to see. I turned to the west and flew right into a wall of hard rain.

When I flew at the Grand Canyon back in 2004, we had a sort of mantra for dealing with heavy rain: if you can see through it, you can fly through it. This rain was so intense that I could barely see brightness in the sky beyond it. I was flying at about 200 feet off the ground — just high enough to clear the local power lines but probably not high enough to clear the high-tension power lines I knew were up ahead. The air was remarkably calm, so at least I didn’t have to deal with turbulence. I climbed cautiously, heading west, flying at 110 knots, focused on reaching the orchard quickly.

The sky brightened. The rain lessened. Then I was through the storm, on the other side, flying into what looked like a beautiful day.

A really beautiful day.

Ahead of me, the sun was shining brightly, sending patches of light through broken clouds onto the yellow-green hillsides beyond the Columbia River. Some low-level clouds were floating at my altitude over the river and beyond. Wisps of clouds were wrapping themselves around hilltops like winter scarves around thick necks. The sky had a kind of three-dimensionality I rarely get to see.

And over my right shoulder, back in the dark storm I was passing, was a double rainbow.

There are times that I can only classify as magical — times I wish I could bottle up and save, just so I can open them up to re-experience them when I need a little magic in my life. This was one of those times.

I realized, in a flash of clarity, that I really loved doing what I do.

I call myself a writer, but in all honesty, there’s no way I can express, in words, the feeling I get when I experience one of these moments. I can try to describe what I see. I can try to paint a picture for my reader to see something similar in his own mind as he reads my words. But in truth, there’s no way to share this kind of experience after the fact. It’s a moment in time and space — something that becomes part of me. It’s like a happy little secret I’m forced to bear, unable to share it with anyone else.

It’s moments like these that make my life worth living.

I cleared the big wires, reached the edge of the plateau, and lowered the collective almost to the floor to start a steep descent down to the river. The water was smooth, reflecting the clouds in a magnificent sky. Everything below me looked fresh and clean and wet. I descended at 1200 feet per minute over the river, then pulled the cyclic back gently to slow my airspeed and descent rate. Coming in over the orchardI came in over the orchard in a grand, swooping arc, settling in at the southeast corner in a hover over trees nearly as old as I am.

And then I got down to work, hovering back and forth, up and down the rows of trees, performing the tedious task I was paid to do.

From my seat only a few feet above the treetops, I could clearly see the bright red fruit and the droplets of water clinging to them. I could see my downwash shaking the tree branches all around me. Everything was very wet, but with only one pass, most of that water was shaken and blown down to the ground.

Sunset Cherry Dry

Golden Light

I stole glimpses of the river and sky and cliffs. It was early evening on a Washington day when the sun would set well after 8:30 PM. The sun played peek-a-book with thin strips of clouds. The sunlight illuminated the cliff faces in a golden light.

On the ground out on the road in front of the orchard, my client stood outside his truck, snapping photos with his camera. Inside the front passenger seat, I saw his mom. She waved once but, with both hands fully occupied, I couldn’t wave back. Later, the truck was in the orchard, near the shop building. The photos started arriving on my cell phone, which was docked in a cradle within reach, a while later. I wouldn’t be able to see them until much later.

It took over an hour to do the whole orchard. It always does. It’s a tough dry, with trees of varying ages and heights, a gentle slope, a deep gully, and some nasty wires right at rotor height along one side of the orchard. I spend a lot of time flying sideways so I can keep low on a downhill stretch without getting my tail rotor in the trees behind me. But finally I was done. I did what I think of as my “victory lap,” a fast, low-level flight diagonally across the orchard, gaining speed before pulling the cyclic back to start a steep climb up the cliff face.

At the top of the cliff, thin clouds were thickening, forming a fog layer that would soon be too thick to pass through. I squeezed through a gap in the clouds and pointed the helicopter east, toward my home base.


Note: Many thanks to Patrick, my client, for providing the in-flight photos that appear in this post and on Facebook.

Malaga Springs to Martin Scott by Helicopter

Another nosecam video.

On Saturday, I spent a good portion of the day flying between Martin Scott Winery in East Wenatchee, WA and Malaga Springs Winery in Malaga, WA. I use my helicopter to offer wine-tasting tours for part of the summer season. These are just two of the four (so far) wineries that have suitable landing zones for me and encourage me to bring people there.

As shown in the map below, the two wineries are on opposite sides of the Columbia River. To drive from one to the other, it’s 12.5 miles and will take (according to Google Maps) about 31 minutes. Malaga Springs is a bit tough to find and the last 1.4 miles is on a gravel road. I drove to it just the other day and was convinced I was going the wrong way when I spotted a winery sign that said “Keep the Faith” and encouraged me to continue on my way.

Martin Scott to Malaga Springs

By helicopter, however, it takes less than 2.5 minutes on a direct flight across the river.

Yesterday, I flew nine people from Martin Scott to Malaga Springs and back. For some of those flights, I had my GoPro “nosecam” set up and turned on. Since it’s been so long since I shared a “nosecam” video, I threw one together Saturday night and uploaded it Sunday morning. Here it is:

Interested in a wine-tasting tour by helicopter? Learn more on Flying M Air’s Web site.

Why I Spent $11,524 to Replace Perfectly Good Fuel Tanks on my R44 Helicopter

The short answer: Lawyers.

I’m not sure when the brouhaha began.

It might have been right after this crash, when a helicopter operating at or near gross weight at an off-airport landing zone in high density altitude situation by a sea level pilot crashed, killing all four on board and starting a forest fire that raged for two days.

Or it could have been earlier, after this crash, which I blogged about here, when a helicopter operating 131 pounds over the maximum gross weight for an out of ground effect hover by a brand new helicopter pilot low-level at an off road race crashed, severely injuring all three people on board.

I’m sure it was before this crash, when a 250-hour pilot landed to “relieve himself” at an off-airport landing zone with a density altitude of at least 11,000 feet, then panicked when he got a low rotor horn and aux fuel pump light at takeoff and botched up a run-on landing on unsuitable terrain, severely injuring himself and his wife.

These three cases have two things in common (other than pilots who did not exercise the best judgement): the helicopters were R44s and the crashes caused fires that injured or killed people.

Crash an Aircraft, Have a Fire

Of course, if you crash any kind of aircraft that has fuel on board hard enough into terrain, a fire is likely to result. Fuel is flammable. (Duh.) When a fuel tank ruptures, fuel spills. (Duh.) If there’s an ignition source, such as a spark or a hot engine component, that fuel is going to ignite. (Duh.)

I could spend the rest of the day citing NTSB reports where an airplane or helicopter crash resulted in a fire. But frankly, that would be a complete waste of my time because it happens pretty often.

Don’t believe me? Go to http://www.ntsb.gov/aviationquery/index.aspx, scroll down to the Event Details area, and enter fire in the field labeled Enter your word string below. Then click Submit Query and check out the list. When I ran this search, I got more than 14,000 results, the most recent being a Cirrus SR22 that crashed on April 27, 2012 — less than 2 weeks ago.

The Knee Jerks

But Robinson reacted in typical knee-jerk fashion. After issuing a ridiculous Safety Notice SN-40, “Postcrash Fires,” that recommended that each helicopter occupant wear a “fire-retardant Nomex flight suit, gloves, and hood or helmet,” they began redesigning components of the helicopter’s fuel system. First they redesigned the fuel hose clamps and issued Service Bulletin SB-67, titled “R44 II Fuel Hose Supports.” Then they redesigned the rigid fuel lines to replace them with flexible lines and issued Service Bulletin SB-68, titled “Rigid Fuel Line Replacement.” And then they redesigned the fuel tanks to include a rubber bladder and released Service Bulletin SB-78 (superseded by SB-78A), the dreaded “Bladder Fuel Tank Retrofit.”

Why “dreaded”? Primarily because of the cost of compliance, which was estimated between $10,000 and $14,000.

Originally released on December 20, 2010 (Merry Christmas from the folks at Robinson Helicopter!), Robinson did give us some breathing room. The time of compliance was set to “As soon as practical, but no later than 31 December 2014.” I did the math and realized that my helicopter would likely be timed out — in other words, back at the factory for overhaul — before then. But the February 21, 2012 revision moved the compliance date up to December 31, 2013. At the rate I was flying — about 200-250 hours per year — it looked as if I’d still be flying it when December 2013 rolled along.

Is it Required?

I talked to my FAA POI. He’s the guy that oversees my Part 135 operations. He’s a good guy: reasonable and easy to talk to. He doesn’t bother me and I try hard not to bother him. After all, he’s got bigger operators with bigger headaches to worry about.

We talked about the Service Bulletin. Neither of us were clear on whether the FAA would require compliance for my operation. After all, it was a Service Bulletin, not an Airworthiness Directive (AD), which is definitely required.

We left off the conversation with acknowledgement that I didn’t have to do anything at all for quite some time. We’d revisit it a little later.

Pond Scum

Around this time, I was contacted by a lawyer representing the family of the 250-hour pilot who crashed in the mountains because he had to “relieve himself.” This guy had seen my blog posts about my problems with my helicopter’s auxiliary fuel pump — perhaps this one or this one or possibly this one. Or maybe all three.

He was looking for an “expert witness” to provide information about the problems with the fuel pump. It was clear that he was trying to pin the blame for his clients’ injuries on the fuel pump manufacturer and Robinson Helicopter. Not on his client, of course, who had caused the accident by making a series of very stupid decisions. Apparently, Robinson is supposed to make idiot-proof helicopters.

I got angry about the whole thing — lawyers shifting the blame to people who don’t deserve it — and responded as you might expect. I also blogged about it here.

I didn’t make the connection between lawyers and bladder fuel tanks. I believed — and still believe — that it’s not unreasonable for post-crash fires to occur in the event of an aircraft accident. It’s part of the risk of being a pilot. Part of the risk of flying.

The Buzz and Insurance Concerns

Meanwhile, the Robinson owner community was buzzing with opinions about the damn bladder fuel tanks. Some folks suggested that they’d been developed as a means for Robinson to make money off owners in a time when helicopter sales were slow.

Maybe I’m naive, but I don’t think that’s the case. I think Robinson was just trying to protect itself from liability. By offering this option, it would be up to the helicopter owner to decide what to do. If the owner didn’t get the upgrade and had a post-crash fire, Robinson could step back and say, “The new fuel tanks might have prevented that. Why didn’t you get them? Don’t blame us.” And they’d be right.

And that got me thinking about my insurance. So I called my insurance agent, who was also a friend and helicopter pilot. The year before, he’d managed to come up with an excellent and affordable policy for R44 owners and I’d switched to that policy as soon as my existing policy ended. Would I be covered if I didn’t get the tanks installed right away? He told me that of course I’d be covered. The compliance date wasn’t until December 31, 2013.

Buy Now, Save Money?

I also talked to my mechanic. He told me that the tanks were on back order and it could take up to eight months to get them. I was also under the impression that the cost of the tanks was going to rise at the end of 2011. And that if I ordered the tanks, I wouldn’t have to pay for them until they arrived. I figured that once they arrived, I’d store them until I was ready to have them installed. Or maybe even hold onto them until overhaul.

So I ordered them in late December, right before the Robinson factory closed for the holiday break.

I’d been misinformed. I had to pay for them up front: $6,800. Merry Christmas.

And, oh yeah: the price didn’t go up, either.

A Horrifying Scenario

Time went by. I thought about the damn tanks on and off throughout the winter months. In February, during my occasional checking of accident reports, I saw this report about an R44 with a post-crash fire. It got me thinking about liability again.

And then I started thinking about lawyers, like that sleezebag who had contacted me. And my imagination put together this scenario:

My helicopter crashes and there’s a fire. One of my passengers is burned. Although my insurance covers it, the blood sucking legal council my passenger has hired decides to suck me dry. He claims that I knew the fuel tanks were available and that they could prevent a fire and that I neglected to install them. He puts the blame squarely on me. My insurance, which is limited to $2 million liability, runs out and the bastard proceeds to take away everything I own, ruining me financially forever.

Not a pretty picture.

Is this what Robinson intended? I’d like to think not. But I’m sure that as I type this, some lawyer in Louisiana is working on a case using the logic cited above. The pilot might be dead, but his next of kin won’t have much left when the lawyers are done with him.

I started thinking that I may as well install the damn tanks — just in case.

Dealing with Logistics

In late March the fuel tanks were delivered. It cost another $310 for shipping. The two boxes weren’t very heavy, but they were huge. I had them delivered directly to my mechanic.

And then I started thinking about logistics. I had originally expected the tanks to arrive during the summer while I was gone for my summer work in Washington state. I figured I’d have them installed at my next annual or 100-hour inspection near year-end. But here they were, waiting for installation any time I was ready.

But when would I be ready? My mechanic said it would take about 10 days (minimum) to install them. Because the tanks had to be fitted to the helicopter, it was a multistep process:

  1. Remove the old tanks.
  2. Put on the new tanks and fit them to the helicopter. (Metal work required.)
  3. Remove the new tanks.
  4. Paint the new tanks.
  5. Reinstall the new tanks.

Most of that time was taken up with getting the tanks painted and waiting for them to dry.

Logistics is a major part of my life. I’m constantly working out solutions for moving my helicopter and other equipment to handle the work I have. I’m also constantly trying to schedule any maintenance at a time when I’m least likely to need to fly. This spring was especially challenging: I had to get my truck, RV, and helicopter up to Washington before the end of May. I also had to go to Colorado to record a Lynda.com course before the end of May.

So on April 13, I flew the helicopter down to my mechanic in Chandler and asked my friend Don to pick me up (in his helicopter) and take me home to Wickenburg. Then, the same day, I started the 3-day drive in my truck with my RV to Washington. I arrived on April 15. A week later, on April 22, I took Alaska Air flights to Colorado, where I stayed for another 6 days. Then, on April 28, I flew directly back to Phoenix. Don picked me up at the Sky Harbor helipad and dropped me off at Chandler. All the work on the helicopter was done and it looked great. I flew the helicopter back to Wickenburg that morning. Two days later, on May 30, I picked up passengers in Scottsdale and began the 2-day flight to Washington. We arrived on May 1.

ItemCost
Fuel Tanks$6,800
Shipping$310
Tank Installation$3,960
Tank Painting$454
Total Cost$11,524

The installation and painting had cost another $3,960 and $454 respectively, bringing my total for installing the damn bladder fuel tanks to $11,524.

I Blame the Lawyers

So, yes, I spent $11,524 for tanks that might only benefit me in the event of a crash. No guarantees, of course.

I didn’t need the tanks. They didn’t make flight any safer or better. They only might make crashing safer.

And the only reason I did this is so that a lawyer couldn’t point his finger at me and blame me for ignoring a Service Bulletin that wasn’t wasn’t required by law until (maybe) December 31, 2013.

The only reason I did this was to possibly prevent a lawyer from taking away everything I own, everything I’ve worked hard for all my life, in the unlikely event that my helicopter crashed and a fire started.

Do you want to know why aviation is so expensive? Why it costs so much to fly with me? Ask the lawyers.

About the Golf Ball Drops

Your questions, answered.

Yesterday, I did a golf ball drop. I have another one scheduled for today. And I’ve done at least three of them in the past. (You can read a blog post that details one of them and see a video of another drop embedded in this post.) Here’s a shot from my helicopter’s skidcam to give you a better idea of what it looks like:

Golf Ball Drop

The Tweets

Last night, when I tweeted:

Today’s golf ball drop had 2100 balls. Just learned that tomorrow’s will have 4900. Can you even IMAGINE that many golf balls? Not me.

I got two replies:

mjburian
I don’t understand (but I’m intrigued). You’re dropping them from altitude? Where? Individually?

Daniel_Loxton
Wait, what? Why would someone drop golf balls (or any solid object) out of a helicopter? http://www.youtube.com/watch?v=ST01bZJPuE0

(The link is to a pertinent WKRP in Cincinnati video clip; watch it if you haven’t seen it before.)

So I figured I’d explain what this is about.

Golf Ball Drop Explained

A golf ball drop is usually a charity or fund-raising event. The fundraisers “sell” numbered golf balls for a set price. The balls are taken up in a helicopter and dropped from 200-300 feet onto a target which is normally a standard sized golf hole or cup. Often, a ring of lines is drawn around the target on the grass to mark different levels of prizes. The ball(s) that go in the cup or are within the rings or are even just closest to the center of the target win the prize(s). The money left over after paying for the helicopter, the balls, and the prizes makes up the proceeds from the fund-raising event.

Normally, this is a big spectator event. After all, who doesn’t like helicopters? Who wouldn’t want to watch something being dropped out of one? It’s a fun way to raise money.

Safety Issues

As a safety-conscious pilot, I do everything in my power to make the flight as safe as possible. The dropper sits behind me, strapped in with his door off. All the other helicopter doors are on to limit the possibility of loose items flying out another door.

The balls are usually stored in bags or boxes on the seat beside the dropper. He drops them out the open door — which is on the side opposite of the helicopter’s tail rotor. The balls generally go straight down, but some do bounce off the skid. I’ve never had one bounce dangerously, but I do leave my door on in to prevent one from bouncing back into the cockpit and getting under my pedals.

Below us, the target area is clear of all people and non-essential equipment. I allow only one passenger — the dropper — on board and run with minimum fuel to keep the aircraft light. I point into the wind during the hover.

The only real danger to the flight is the out of ground effect hover right smack dab in the middle of the deadman’s curve. In the unlikely event of an engine failure, things would get ugly fast.

Yesterday’s Drop

Yesterday’s drop was done at the CrackerJax Family Fun Park less than 1/2 mile from Scottsdale Airport. This required additional coordination with the Scottsdale Tower, since CrackerJax is right under the helicopter approach path to the airport.

It was done to raise money for the notMYkid charity. There were a total of 2,100 balls preloaded into 11 very nice drawstring canvas bags. Due to the size and weight of that many balls — an estimated 400 pounds that would not fit in the left rear passenger seat — we did it in two drops, with a hot loading of the balls between the drops.

The photo above is from my helicopter’s skidcam, which I’d rigged up specifically for the flight. On hindsight, I wish I’d pointed it down more; maybe I’ll try a different angle for today’s drop of 4,900 balls — it’ll likely take 3 or 4 drops to do them all.

It’s All in a Day’s Work

Do I like doing golf ball drops? I like doing anything different and interesting, especially if it’s something that can entertain spectators, too. There were very few spectators for yesterday’s drop, but I expect at least 100 for today’s.

And I really can’t knock getting paid to fly.