A New Lens

But Mike gets to use it first!

I’d treated myself to a new camera lens late last month. When I returned from Washington last week, it was waiting for me at home.

Product ImageThe lens is a Nikon 16-85mm f/3.5-5.6G AF-S DX ED VR Nikkor Wide Angle Telephoto Zoom Lens. It’ll replace the 18-55mm lens I bought on eBay last year — the same lens that crapped out on me about two months ago. (Another reason not to buy used camera equipment on eBay.) That lens was cheap and it felt cheap — lightweight and plasticky. This lens was costly and it has a weighty, quality feel to it.

But that’s not why I bought it. It was the Amazon reviews that convinced me. Although I’ll never rely on reviews there to buy a book — I’ve been burned before, in more ways than one — I find that reviews of camera equipment are generally fair and reliable. It’s easy to identify fanboys and people with a gripe against the company. Weed those out and you can get some solid opinions of the products. In this case, just about all owners liked the lens.

But it was comments like these that sold me:

I have both the 18-135 and the 18-200, yet this lens has become my everyday go to lens for most of my photography. …Given the great sharpness (especially in the 16-50mm range), VR, and almost total lack of noticeable CAs, I can highly recommend the 16-85 for a general purpose, on-the-camera-all-the-time lens. – D80Shooter

I think 16-85mm VR and 70-300 VR lenses is probably all amateur like me needs, with light and compact 16-85mm VR lens mounted on camera most of the time. – Alex

This is how I was using the 18-55mm lens — as an everyday lens. This one promised more flexibility with better optics.

Of course, when I got back to Wickenburg, I had just 3 days to do a ton of stuff. I didn’t have time to play with the lens other than to snap a few photos in the kitchen to check the focal length range. Photography would have to wait.

New Bryce CanyonWhen we flew to Seattle on Friday, the new lens was in my camera bag with the rest of the camera equipment I take on the road. But with the back problems that have been slowing me down, I didn’t have time to do anything fun in Seattle, despite the fact that we had the whole day there. (I spent much of it sleeping off some painkillers.) The next morning, we began our helicopter flight from Seattle to Page. I was sitting up front, handling navigation while Louis flew. I had my hands full with directions for our scud-run south. I didn’t realize it at first, but Mike was sitting in back, snapping photos with the new lens. He continued to do so on both days of the flight and got quite a few good shots from the air. This photo, taken just outside of the Bryce Canyon area, is especially attractive to me because of the shadow created by the big, puffy, low clouds.

N630MLat Spanish ForkMy photography was limited to shots taken on the ground, like this photo of my helicopter at the Spanish Fork, UT airport. Although the photo doesn’t seem too interesting in this low-res shot, it’s really impressive in full-resolution, with clear detail of the clouds — enhanced with the use of a circular polarizing filter on the camera (not in Photoshop) — and dramatic mountains in the background. I think it’s my new favorite picture of my helicopter.

I’ll be uploading the best photos from the flight to my gallery at Flying M Photos.

I’m in Page, AZ now, planning to spend the next month and a half flying tours around Lake Powell and Monument Valley. (You can learn more about my summer flying gigs on the Flying M Air Web site.) I’m also working hard this month to complete my 72nd book, which, unfortunately, I can’t talk about here. So while I’ll be very busy through August, I should have free time in September to go exploring. Antelope Canyon is less than 5 miles away and I expect to spend several mid-day sessions in Lower Antelope Canyon. There’s also an interesting rock formation called The Wave within 50 miles of here — not sure where yet — and if my back heals up, I’ll take a hike there. This new lens should be perfect for these tight locations, since it offers a really wide view without much distortion. (My fisheye lens can take some cool photos, but its a limited use lens.) I might also charter an airplane for some aerial photo work. Airplanes are extremely limited for this kind of work — helicopters are so much better — but it might be worthwhile to give it a try.

If you have a lens like this, I’d love to hear from you. Use the Comments link or form for this post to share your thoughts.

The Deadman’s Curve

Why helicopter pilots balk when asked to hover at 50 feet.

Last year, I joined a listserve group of professional aerial photographers. These folks, who are based all over the world, have been working at their profession for years. I’m a relative newcomer to the aerial photography scene and arrive as a pilot — not a photographer. (I want to take photos, but it’s tough when my right hand is stuck holding the cyclic during flight.)

I introduced myself and an engaging conversation about flying helicopters ensued. As you can imagine, many of the photographers had worked with helicopters. One of them was even on board during a crash!

One of the photographers in the group told a story about photo flights he’d taken with helicopter flight school instructors. He included this comment:

I was shooting a lot of sailboat races at the time, so where I wanted it turned out to be in a hover at 20 to 50 feet above the water which made some of the instructors nervous. I told them to get over it.

A lot of pilots won’t work in what’s commonly referred to by helicopter pilots as the “deadman’s curve.” All helicopter pilots should know what this is, but here’s a brief explanation for those of you who aren’t familiar with helicopter flight.

The “Deadman’s Curve”

Height-Velocity Diagram for R44 HelicopterThe Height-Velocity diagram in the pilot operating handbook (POH) shows the combinations of airspeed and altitude at which an experienced pilot (or test pilot) should be able to make a safe autorotation in the event of an engine failure.

The diagram shown here is for a Robinson R44 helicopter, but they’re all very similar. The idea is to stay out of the shaded area. Generally speaking, you want either altitude or airspeed — or (preferably) both. Hovering at 20 to 50 feet puts you in the “deadman’s curve” — it’s a combination or airspeed (0 knots) and altitude (20 to 50 feet) at which a safe autorotation is not possible. So if the engine quits, you’re dead.

The height velocity diagram also clearly shows the recommended take-off profile. When a pilot does a “by the book” take-off, this is what he’s doing: picking up into a hover less than 10 feet off the ground and accelerating through 45 knots. Then pitch up slightly and climb out at 60 knots. (You can get an idea of this in my “Shadow Takeoff” video.) Doing a “straight up” take-off like you see in the movies or on television puts the helicopter smack dab in the middle of the deadman’s curve until he’s moving faster than 50 knots or has climbed several hundred feet.

Wondering how the chart is created? With test pilots and helicopters. If you take the Robinson Factory Safety Course, you’ll see videos of the flights they used to build the chart — including one flight that demonstrated what happens when you attempt an autorotation while inside the deadman’s curve.

My Experience with the Deadman’s Curve

I get some photo gigs because I’m willing to operate in certain areas of the deadman’s curve to meet my client’s needs. I’m a single pilot operator so I’m responsible for myself. Other organizations are responsible for their pilots and tell their pilots not to do anything that could be “unsafe.” This is often the situation at flight schools that do photo flights for extra revenue. Those pilots are usually the school’s CFIs, sometimes with only a few hundred hours of flight time. The school makes a rule — no operations under 300 feet — and all the pilots are required to comply.

Operating in the deadman’s curve requires that you have a lot of confidence in your engine and mechanic. The engine failure statistics on Robinson helicopters show that the engine — a Lycoming, after all — is very reliable. And I take meticulous care of my aircraft with two experienced mechanics to do the work. I’m confident in my aircraft. So I take the risk and I get the job.

But I do warn my passengers of the risks inherent in that type of flying. And If a maneuver puts me too close to obstacles or requires me to do something I think is beyond my skill level, I won’t do it. (I don’t have a death wish.)

Get Over It?

“Get over it,” is a pretty funny thing to say to a pilot when requesting (or demanding) that he perform a maneuver he’s not comfortable with or authorized to do.

The pilot who balked at hovering 50 feet off the ground was doing it for safety — his and his client’s. The photographer who told him to “get over it” was unfair to expect the pilot to operate where he was not comfortable. At the same time, the pilot should have clearly stated the limitations of the flight before accepting the job so the photographer wouldn’t expect the pilot to perform maneuvers beyond his normal operating scope.

Unfortunately, more than a few pilots will simply cave in under pressure to please the client. Sometimes this is can be a very bad thing that both the pilot and his client don’t live to regret.

A good pilot will evaluate the risks, make a decision, and stick to it. A pilot who is easily bullied by passengers (or management, for that matter) needs to look for a new career.

Misleading Statements in Popular Fiction

I actually wrote most of this post months ago and mothballed it to finish at a later date. But yesterday, I read something in a novel that made it clear how little the general public understands about helicopter operations.

In the story, the protagonists are passengers on a helicopter that’s running out of fuel. The lead protagonist tells the pilot to lose altitude. His reasoning:

Helicopters sometimes survived engine failures at a few hundred feet. They rarely survived at a few thousand.

The above statement is false. Reverse the facts and you get the correct statement, which I could word like this:

Helicopters rarely survived engine failures at a few hundred feet. They usually survived at a few thousand.

Why the difference? The H-V Diagram is a big part of it. Take a look. If a pilot is flying at 200-300 feet, he’ll have to be moving at at least 50 knots to stay out of the deadman’s curve. The H-V Diagram clearly shows that the higher you are and the faster you go, the farther you are from the deadman’s curve. Altitude and airspeed are two energy management components that can save a pilot’s life in the event of an engine failure.

If you’re operating outside the deadman’s curve, the thing that makes higher altitudes safer is time. If you’re cruising along at 500 feet AGL at 100 knots — a perfectly safe combination of altitude and airspeed, according to the H-V Diagram — you’re going to be on the ground a lot quicker than if you were doing the same speed at 1,500 feet AGL. That’s less time to correct any problems with your autorotation entry, pick a good landing zone, make a Mayday call, brief your passengers, etc. Now imagine cruising at the unlikely altitude of 3,000 feet AGL. In a good gliding helicopter, like my R44 or a Bell LongRanger, you have lots of time to set it up and do it right.

Clearly, higher is better.

There were some other errors in the book as far as the helicopter was concerned, but I’ll save them for another post. (It really does bug me when books, movies, and television send inaccurate messages about how helicopters fly.)

Why Not Get the Facts Straight?

Time passes. I don’t recall when I started writing this post, but I know I didn’t last long with the photographers in that group. They were very full of themselves and highly critical of newcomers. And some of them echoed the same uninformed ideas about the safety of helicopters that I hear everywhere else. Worst of all, they didn’t seem interested in learning the truth.

I wrote a post earlier this month titled “Why Forums Suck” that describes the atmosphere in this particular group. Maybe it’s me, but I simply don’t have patience for people who behave the way some of these guys (and women) did.

And, in case you’re wondering, I e-mailed the author of the book with the errors. I hope he didn’t think I was being rude. But I want him — and anyone else preparing material about helicopters — to get the facts straight before releasing it to the public. In his case, any helicopter pilot could have pointed out the problems I found and reported to him. A few minor changes to the manuscript would have made it accurate without impacting the story one darn bit.

I just wonder if other pilots who read the book were as irked about the errors as I am.

Probably not.

Aerial Photos from Our Las Vegas Flight

Better late than never.

Back in the beginning of March, while my mother-in-law was visiting us from New York, I flew the three of us from Wickenburg to Las Vegas by helicopter.

I chose my favorite route for that flight: straight to Lake Havasu City and up the Colorado River all the way to Lake Mead, then west to McCarran Airport. The flight went well, but strong headwinds turned what should have been a 1.8 hour flight into a 2.5 hour flight. (It also made the flight a bit rough in some places.) Mike, sitting in the back, had my old PowerShot camera. Here are a few of the photos he took along the way. I chose the ones where you can see details within the cockpit to put the scenes in perspective. It’s also kind of cool (at least to me) to see the instruments and gauges in the panel.

Here’s Lake Havasu City. That’s London Bridge below us — the real thing, brought over from England in the 1970s. I always start my upriver flights with an overflight of the bridge.

Much farther up the river, we reached Hoover Dam and the bypass bridge, which is still under construction. Hoover Dam, in case you don’t know, holds in Lake Mead. The white line right above water level is about 60 feet tall and marks the high water line. (The water level is way down.) We would have gotten some better photos of the dam and bridge if the area weren’t so darn congested. There was a tour helicopter high over the dam and a pair of military helicopters that would be cutting right between us, less than 500 feet over my head. I didn’t waste much time there.

After crossing the southwest corner of Lake Mead, I headed west toward the city. Here’s a shot as we were getting ready to cross Lake Las Vegas. If you’ve got sharp eyes (or the full-sized photo) you can see the Las Vegas skyline on the horizon on the right side of the photo.

Air Traffic Control at McCarran instructed me to fly toward the Stratosphere when I was still 15 miles out. I wound up flying just south of it — my altitude was below the glassed-in restaurant/ amusement level of the tower. (At the time, I recall wondering what people looking out at us must have been thinking.) I’m particularly fond of this shot because it’s so damn surreal.

We made our approach to McCarran flying down I-15, then descending between Luxor and Mandalay Bay to land on the ramp. I have video of it from my POV.1, but I don’t think it’s all that good. I’ll have to do it again one of these days with the camera mounted in its new position. (More on that another time.)

21 Lawyers and a Mansion on a Mountainside

Two flying jobs in one day.

I spent most of yesterday flying — and that’s not an exaggeration. I was in the cockpit almost nonstop from 8 AM through 5 PM. During that time, the helicopter was on the ground waiting for less than two hours — and most of that time was for either fueling or waiting for passengers.

The Plan

I’d been booked to fly a series of 30-minute tours for a bunch of lawyers in Phoenix for a conference. The woman who made the arrangements started a dialog with me about it at least four months ago, and I admit I didn’t think the job would happen. But about a month and a half ago, she finalized. There would be 21 passengers — that meant 7 individual flights of 30 minutes each. Three and a half hours of flight time. That’s the kind of job you just don’t want to turn down. Best of all, I received payment by check a week before the flight. So I was booked for 12 noon out of Deer Valley Airport in Phoenix.

The day before that flight, I got a phone call from a local video producer. He needed a helicopter to fly a job on the same day. (Why does this always happen? Nothing major for a week or two and then two job possibilities at the same date and time?) I explained that I was only available before 11:30 AM or after 5 PM. He said he’d call back. When he did, he said the morning slot would work best, since the home he needed to video from the air faced east. After a few more phone conversations with him and his camera guy, I was booked for 8:45 AM out of Falcon Field airport in Mesa.

The Photo Shoot

Sunrise Hangar Shot by Jon DavisonEarly yesterday morning, Mike and I were at the airport, pulling the helicopter out and fueling it up for the flight down to Falcon Field.* Mike was coming with me for the Phoenix Tour portion of the day; I needed someone reliable to safely “hot” load and unload my passengers, since shutting down after each flight would be far too time consuming. He wanted to fly with me on the photo shoot, but I would have a cameraman and director onboard and the added weight of a fourth person would have severely restricted my performance. As it turned out, we didn’t have room for him — the cameraman brought all kinds of stuff with him that took up the other seat.

Mountainside HouseThe flight down to Falcon Field was relatively uneventful. We took a route that scouted around the south sides of Deer Valley’s and Scottsdale’s airspace. Normally, I’d fly between Squaw Peak and Camelback, but I wanted to preview the area I’d be flying for the photo shoot. I’d found it on Google Maps; as you can see here in a Google Maps satellite view, it’s on the side of a mountain at the end of a canyon. (I don’t want to identify the house in question or even provide details on where it is. Even though it’s in a gated community, I know there are people who read this blog and have nothing better to do than track down the places I write about.) From there, we continued on to Falcon Field, where I landed on a helipad at the base of the tower and shut down.

The film’s director, Anthony, was already there. He’d been told to meet us at 8:30. We’d been told 8:45. Evidently, the cameraman had been told 9:00. He arrived at 9:15. He’d had some trouble with the camera mount and his gyro. Mike, Anthony, and I chatted while we waited. He told us that the house in question was a rental and the video was for promotional purposes.

The cameraman, Will, arrived with all kinds of equipment. We brought it all out to the helicopter and helped him prepare it. He climbed into a very serious harness with the thickest web straps I’d ever seen. That turned out to be a good thing, since he depended on that to keep him from falling out and he did most of his work with both feet on the skids. (I’m glad he was sitting behind me where I couldn’t see him.) He also had a helicopter pilot helmet, which he said made it possible for him to get his head closer to the camera. The camera was quite large and he put additional equipment on the back seat beside him, as well as on the floor in front of that seat. Anthony sat up front next to me, with a video monitor he could use to see and direct Will’s camera work. Will’s door was off, of course.

Both of them had spent extensive time in a helicopter doing this kind of work, but Mike gave them the safety briefing anyway. Then I started up, warmed up, and took off.

To say the shoot was tricky is an understatement. The house in question was the highest one on the hill, but it was still below the ridge lines nearby. It was also at the end of a canyon. I couldn’t hover for long abeam it because (1) if I got into settling with power, there was no place to escape to, (2) hovering that low would put me too close to neighboring homes, and (3) 10-15 mph winds from the south over the nearest ridge set up nasty turbulence at that level in the canyon. So although I was able to give them plenty of low, slow passes, I had to keep moving, keeping my speed above 20-25 knots so I wouldn’t slip below ETL. I also couldn’t get as low as they wanted.

I should mention the effect they were trying to achieve: Zoom in on a guy on the balcony who is talking to the camera. Make it look as if the camera guy is standing with him — not on a helicopter hovering 200 yards away. Then pull back to reveal the home and mountainside from the helicopter. They called it a “snap.” It sounds like a great shot, but it was nearly impossible to achieve. I don’t know if they expected me to hover out of ground effect 100 feet away from the house in a canyon with neighboring homes nearby in 10-15 mph winds, but I’m not an idiot. While it might be possible for a 10,000 hour pilot who didn’t worry about safety or noise flying a twin-engine turbine, it wasn’t possible for me to do it safely in a loaded R44.

There was some confusion with the actors, too. Anthony did all of his communication by cell phone and text messaging, but apparently there were a lot of lost instructions. I won’t go into details, but some of it would have been funny if they weren’t paying me to watch it from the air. So it didn’t come off exactly as planned. But they assured me that they got plenty to work with. I hope so. We were on point for more than 90 minutes — and I’m sure I’m going to get phone calls on Monday morning.

From there, Anthony wanted to shoot his office, which was near Scottsdale Airport. I asked where it was in relation to the tower. About a half mile northeast. I got permission from the tower to enter their airspace and move into permission. I had to stay low-level to keep away from other traffic, so we were about 300-400 feet up. It turns out, his office is a block away from the taxiway at Scottsdale airport. I reported on point to the the tower and did two circles while Will shot video.

Then we peeled off to shoot someone else’s house just inside Scottsdale’s space. By this time, Scottsdale Tower had cut me loose with a “Frequency change approved,” and I was pretty much free to do what I wanted. Unfortunately, this required some low (300-400 feet), slow flight over a golf course and the folks on the fairway stopped to give us some dirty looks. More phone calls on Monday, I suppose.

We were back at Falcon Field at 11:20, just 10 minutes before I wanted to be out of there. I’d flown 2.2 hobbs hours — more than twice the time we’d originally estimated for the flight. I had to cool down and shut down. Mike put the door back on and we all helped Will get his camera stuff out while he disconnected his harness. There was a lot of hand shaking all around before they left. I got a fuel truck over to top off both tanks, settled my fuel bill, and started up for the flight to Deer Valley.

The Phoenix Tours

We were supposed to be at Deer Valley by 12 noon. We were late, arriving at about 12:10 PM. I hate to be late. Being late tells the person waiting for you that he’s not important. Nothing could be further from the truth, especially in this case. So I sent Mike in while I was shutting down on the east helipad. Fortunately, the client was very understanding. Since I was already fueled, we were ready to go. Our first flight departed Deer Valley at 12:20 PM.

They wanted a tour of Phoenix that would last 30 minutes. Frankly, it would have been easier to come up with a tour that lasted only 15 minutes. Deer Valley is due north of downtown and I could have done a loop down to McDowell, back over their hotel — they were staying at the Biltmore — and back to Deer Valley. But they wanted 30 minutes and I wanted to deliver it. So I came up with a route that included quite a bit of the west side of Phoenix. The highlight out there was Cardinals Stadium, where they played the Super Bowl this past February. Although the roof was closed, the grass field was outside and I was able to explain how they moved it in and out as needed for games. On one flight, the sprinklers were even on. The grass looked perfect from 500 feet up.

Here’s a Google Maps image of the exact route. You can follow this link for an interactive version.

Phoenix Tour

The flight was challenging because I had to pass through three different towered airport airspaces: Deer Valley (Class D), Glendale (Class D), and Phoenix Sky Harbor (Class B). To make things a little easier, on one of the first flights, I told the towers at Glendale and Phoenix that I’d be doing the same thing six more times.

The tower at Sky Harbor was especially friendly. After the third flight through, the controller could no longer hold back his curiosity. “What are you doing, anyway?” he asked as I exited to the north.

“Half-hour tours of Phoenix from Deer Valley Airport,” I replied.

“Sounds like fun. See you later.”

“Ill be back in 35 minutes,” I told him.

Glendale tower’s controller asked me if I was on traffic watch, probably because I was following the Loop-101 south to I-10. The question surprised me, so I just told him no, but didn’t say what I was doing.

My passengers were very nice and very friendly. They’d come from all over the world: New York, Seattle, Portland, San Diego, Sidney, and Shanghai, to name a few cities. I pointed out sights. They asked questions about what we were seeing and how the helicopter works. They all seemed to enjoy the flight. I estimate that about a third of them had never been on a helicopter before. About a third had never been to Phoenix before, either.

On the last flight, I took some video of the entire flight with my POV.1, from departure to landing. Because the sun was low — it was about 4 PM when I took off — the westbound video isn’t very good. And by the time I got faced the other way, there were bugs on the lens. I probably have a few good clips from the video, though. I decided that I want to try repositioning the camera to the front of the helicopter, pointing straight out. Although the video from my side isn’t bad, I usually make a conscious effort to put the best view on the other side, where two people are sitting. So my view isn’t as good as what the passengers see and the video doesn’t represent their flight as well. Need to work on that.

The Flight Home

After the last tour, I didn’t even bother shutting down. We had enough fuel for the flight home — I’d refueled after the fourth flight. Mike escorted the last group to safety and they made their way back into the terminal. He climbed on board and we took off.

We landed at Wickenburg just after 5 PM. When I shut down and checked the Hobbs meter, I realized that I’d flown 7-1/2 hours that day. I was exhausted.

*Flying M Air stock photo by Jon Davison.

The View from Above

I remember that not everyone knows what the world looks like from 500 feet up.

The other day, while I was down in Surprise, AZ, doing a bit of “analog shopping” — that’s the kind of shopping where you physically walk into a store and look around and maybe buy something but maybe don’t, as opposed on online shopping, which is how I usually buy things other than food or fuel — I suddenly realized that most people don’t have any idea what the area around their homes, schools, or businesses looks like from the air. Right now, I can’t remember what triggered that thought, but I do recall that it hit me hard — hard enough to remember, anyway. I told myself to give the idea some thought and blog about it.

Chances are that you are one of the people who haven’t seen your local environment from the air and you probably don’t think that’s a big deal. Most people haven’t. And that’s what hit me so hard: that the pilots of small aircraft are a minority, not just because they fly, but because they’ve seen so many things from above.

The View from My Seat

I started flying in 1998 or 1999 (need to check my log book to be sure). Back then, I spent most of my flight time just thinking about flying. I was taking lessons to learn how to fly and didn’t have much time to admire the view. But the time I could fly, the view had become second nature.

Off the Grid HouseSo yes — I know what a subdivision looks like from the air. And a school with ball fields. And a park and a town pool. I’ve seen all kinds of backyards, from perfectly trimmed, walled-in plots of grass or decorative rock to sprawling, weed- and junk-filled patches of desert. I’ve seen small downtowns, both dead and alive. I’ve seen where the pavement turns to dirt and what lies five miles beyond. Or ten. Or fifty.

Glen Canyon DamI’ve seen desert lakes and rivers winding through canyons. I’ve seen dams along the Colorado and canals stretching as far as the eye can see. I’ve seen, from the air, natural wonders, like the Grand Canyon, Meteor Crater, the Little Colorado River Gorge, the Grand Falls of the Little Colorado River, and Rainbow Bridge. I’ve flown beside red rocks in Sedona and Monument Valley buttes. I’ve peeked into open pit mines from above and have felt as small as a speck flying down the emptiness of Death Valley. Recently, I’ve flown over Alaskan glaciers blanketed with fresh, pristine snow that went on for twenty, thirty, or forty miles without so much as a footprint to disturb it.

I’ve seen so many things from the air — often from 500 to 1000 feet up — that when I’m on the ground, I can often envision what the place might look like from the air.

Dale LakeThat doesn’t mean I’m bored with the view. While I’ll admit that spending 20 minutes to cross an empty valley in some of the more remote areas of Nevada and California can get pretty dull, there’s always something interesting to notice along the way. Perhaps it’s a deserted homestead, half blown away by wind or covered by sand. Or some ATVs speeding along a transmission line road, sending up a cloud of dust that reveals their position. Or maybe it’s just an odd rock formation, jutting out of the otherwise flat terrain like the ruins of a half-sunken ship.

I wish I could share these images with others, but it’s tough. When I fly, my right hand is always on the cyclic. Cameras are designed to be used with the right hand. Although I’ve become pretty good at taking photos with my left hand, only a small percentage of those shots really show what I’m seeing, without glare and reflections from the cockpit bubble. And sometimes the interesting things I fly by go by very quickly — too quickly to snap a photo. Like the Indian cliff dwelling I passed on a flight from Howard Mesa to Scottsdale at least a year ago; I was in too much of a hurry to circle back and see it again — or get the GPS coordinates. I haven’t found it again.

I write about many of my flights in this blog. If I have photos, I share them. If you’re new to this blog and want to read a few of my better efforts, be sure to check out these:

There’s more, but I’ll let you find them for yourself. Clicking the Flying link under Blog Topics in the sidebar will get you started.

But neither the words nor the photos can truly share the experience of flight or the view from above.

Why I Give Rides

When I first started Flying M Air, I depended on ride gigs to generate income and help cash flow. I soon learned that, in general, giving short rides at a carnival or airport event is a lot more trouble than it’s worth.

First there’s the bother of setting up the event, making sure the landing zone is close enough to the action to be visible to attendees, but far enough away to be safe. The approach and departure routes, which are often the same, need to be clear of obstructions. I need to be able to point the helicopter’s tail away from where people might be waiting or walking when I set down. The insurance paperwork and fees are minor concerns after that.

But the hard part is the flying. It’s grueling work, sitting in the seat for hours on end with a takeoff and a landing every 10 to 15 minutes. With three people on board, we’re usually close to max gross weight and, on a hot day with a crosswind or tailwind, just getting off the ground is challenging.

Once we get off the ground and start on our little tour of the area, though, it’s worth it. More than half the people I fly on rides have never been in a helicopter before. At some events, more than half my passengers are kids. I have the unique opportunity to introduce these people to helicopter flight. And as they chat among each other in the helicopter and ask me questions, I get a glimpse of what they’re seeing through their eyes.

And that’s why I do rides.

While people do some quick math and think I’m making a fortune on every rides gig, the reality is very different; I can usually net more money doing a few trips to the Grand Canyon or Sedona than I can at a rides gig — and that flying is easy.

More Stories and Photos to Come

I’m doing a cross-country flight in mid-May with another pilot. We’re flying from Wickenburg, AZ to Seattle, WA. This will be my longest cross-country flight to date — previously, my longest flight was from Wickenburg to Georgetown, CA. Because that other pilot will be doing most of the flying, I’ll have my door off and my good camera ready. I plan to take lots of pictures and write about the flight in detail.

I’m sure that much of what I have to show and tell will appear here.