A Near Miss at Wickenburg Airport

I witness — and perhaps help prevent — an accident at the airport.

This happened a few weeks ago, but “safe pilot” issues are on my mind lately, so I thought it might be a good idea to document the incident here.

I was at the airport chatting with Stan. We were standing on the ramp near where my helicopter was parked. I’d just come in from a flight.

As we were talking, two planes flew by overhead. They were so close that I assumed they were flying together. The first plane turned right into a downwind for Runway 23. The second plane turned left. I guess they aren’t together, I thought to myself.

As Stan and I chatted, I watched the two planes. The second plane was definitely flying a downwind for Runway 5. So both planes were flying downwinds for opposite runways.

Surely one of them will make a call and the other will hear it and the problem will be resolved before it’s a problem, I thought to myself.

But then both planes turned base. They did it at almost the same time. I pointed it out to Stan. A moment later, they were both on final. If they kept going, they’d meet in the middle of the runway with a lot of bent metal.

I rushed over to my helicopter, flicked the Master switch, turned on the radio, and put on my headset. I keyed the mike, and said, “Wickenburg traffic, there are planes on final for runway 23 and runway 5 at the same time.”

The plane on final for runway 5, now only 200 feet above the ground, banked to its right and started climbing. “I called on the radio,” a man’s voice said. There was no other voice. The other plane kept coming and landed.

“I made my radio calls,” the pilot who’d climbed out said. He was clearly getting pissed off.

“Maybe his radio is broken,” I said, trying to soothe him. But I suspected the truth: the other pilot was tuned into Wickenburg’s old frequency, 122.8, which had been changed over a year and a half — or three chart issues — ago.

The pilot still in the air made left traffic for runway 23 and landed. He made calls every step of the way. The other pilot taxied to parking. When he and his wife got out, I saw that they were older folks, probably retired, perhaps too cost-conscious to spend $8 on an up-to-date Phoenix Sectional Chart. Or too complacent to check the frequency before coming in.

By this time, Stan and I had said our goodbyes and Stan went on his way. I went over to the older couple to ask if they needed help parking their plane. I also asked if their radio was working right. They told me they thought it was. I told them what had almost happened — they were completely unaware of the other plane flying straight toward them over the runway. I asked if they were on the right frequency, pointing out that it had been changed about a year and half before. The pilot got a little flustered and said he was pretty sure they were.

I didn’t believe him, but I wasn’t about to challenge him. Not my job. I think my gently applied comments were enough to get him to either check the radio before takeoff or check the frequency. That’s all I wanted to do.

As for the second pilot, he taxied to fuel . To his credit, he didn’t approach the other couple.

The FAA rules regarding radio communications are clear: radio communications are not required in Class G airspace. So technically, the first pilot hadn’t done anything wrong.

But if the two planes had crashed and the NTSB had come in for an investigation, what do you think they would have found? Perhaps one plane’s radio tuned into the wrong frequency.

And who do you think would have been to blame for the accident? That’s a trick question, of course. The NTSB would have blamed both pilots. One for not communicating on the right frequency and both for not looking out for traffic.

If you’ve read as many NTSB reports as I have, know how they make their conclusions. If it’s not mechanical, it’s usually pilot error. And since radio communications are not required at Class G airspace, the pilot has the additional important burden of looking out for and avoiding other traffic.

What I learned from all this is that some idiots don’t use the radio when they should. They might have a good excuse: they don’t have a radio or it’s broken. (I once had to fly into Wickenburg with a broken radio and I snuck in as far away from the traffic pattern as possible, nearly hugging the ground until I got to the helipad.) Or they might have a bad excuse, like they had the wrong frequency tuned in or “it isn’t required so I don’t do it.” That’s sheer carelessness or stupidity.

Because you can’t depend on the radio to alert you to traffic, you have to keep a constant lookout for it, especially when you’re near an airport. Trusting your ears to alert you to traffic can kill you in Class G airspace, so I’m always looking out for other traffic. Why other pilots don’t, is a mystery to me.

I’m glad this turned out to be a non-event. But, at the same time, I’ll always wonder what would have happened if I — or someone else, for that matter — hadn’t been out there and taken action.

A Few Desert Gigs

I spend two Saturdays doing rides in remote desert locations.

One of the things I like to do to earn a little money with the helicopter is short rides at outdoor events. We did great at the Thunderbird Balloon Classic back in October, but that was held down near Phoenix and attended by people with money to burn. Up here on the edge of nowhere, people are a little tighter with their hard-earned money. As a result, I have to price the rides affordably and give each passenger a lot of bang for the buck. The margins are lower at these outdoor events, but I get a lot of satisfaction giving people their first helicopter ride or showing them something they can only see from the air.

The past two Saturdays each had gigs like that.

On December 30, I flew at the ghost town of Stanton. Stanton was a mining town established in the 1800s. At one point, it was a thriving community, with an opera house, hotel, and stage stop. Situated at the foot of the Weaver Mountains alongside Antelope Creek, it was a gold mining community. Legend has it that a man looking for a lost burro climbed to the top of what would later be known as Rich Hill and found gold nuggets the size of potatoes. Like any idiot from that time, he couldn’t keep quiet about his find and, before long, miners were flocking to the area to cash in. The town grew. It was named after a man named Stanton who, I believe, was involved somehow in the Wickenburg Massacre. (More on that another time.) The town was eventually abandoned when it became too difficult or costly to pull out more gold. Later, a group called the Lost Dutchman’s Mining Association bought the townsite. They installed caretakers, which prevented the town from being vandalized like most ghost towns in Arizona were. (For example, there’s really nothing left of nearby Octave, another ghost town.) As a result, the Saloon/Opera House, hotel, and stage stop still stand. They’re actually in use to this very day, maintained by the Lost Dutchmen group. And a campground has sprung up around the property, giving the group members a place to camp out during the winter months.

I’d flown at Stanton before and although it wasn’t a lucrative gig, it made a small profit and was a lot of fun. The Lost Dutchman have “outings” at Stanton a few times a year. The year-end outing is the big one. Everyone wants to see the “Potato Patch” at the top of Rich Hill but no one wants the all-day hike to get up there. I can get them up there and back in 8 minutes, so that’s what I did.

Flying at StantonSo on December 30, at 12:30 PM, I arrived at Stanton as scheduled and landed on a seldom-used road near the campground. My ground crew — Mike, John, and Lorna — got out and set up a little table. I shut down and waited for the crowd to gather. They came in pairs and trios and when I had at least 4 people waiting, I started up again. Lorna took the money — $30, including tax, per person. Mike and John gave the safety briefings and loaded up the passengers. Then I took off toward Wickenburg, climbing, climbing, climbing. I rounded the south end of Rich Hill and climbed up its east side. The passengers had excellent views of what was left of Octave and the mining activity going on in that canyon. Finally, 2000 feet above Stantons’ elevation, I rounded the north end of Rich Hill, still climbing. We were over the next valley, with Stanton far below us in the mouth of the canyon. I pointed out the Potato Patch and the miner types oohed and aahed. I started the descent, coming down at a rate of more than 1,000 feet per minute. On the way down, I pointed out Wickenburg, far to the south, and Congress, to the west. Also, North Ranch (which, you may recall, the management claims occupants are too old for helicopter rides) and the dairy farm. Even at a 1,200 feet per minute descent rate, I can’t get to Stanton without overflying it and turning back, making an elongated spiral to my landing zone.

We flew 22 people that day. Not bad for a gig less than 15 miles from Wickenburg. Even with a side trip to Lake Pleasant before the flight, we made some money.

On January 7, I was back in the desert with my ground crew. This time, we went to Robson’s Mining World in Aguila. This was my third gig out there for their anniversary celebration. Every year was a little better and this year, I’d dropped my price from $35 per person to only $30. I think that made a big difference. We gave about 50 rides.

The setup for this event was a little more deluxe. Robson’s was having its annual Anniversary celebration and they had lots of activities and food and vendors inside their “town.” John and Lorna took their truck out there, so we were able to bring a long a lot of extra supplies. Flags, banners, a table, some extra fuel. Our setup, alongside the road, was very noticable, especially since we got there early enough to keep the space in front of our table clear of cars.

Flying at Robson's Mining WorldI flew for a few hours, taking a break for lunch before starting up again and flying some more. The route started from our desert clearing, which was just big enough for Zero-Mike-Lima to fit comfortably, to the east alongside the base of the mountain behind Robson’s. I climbed as I flew, pointing out where Wickenburg would be if we could see it (we couldn’t), Vulture Peak, Congress, and Alamo Lake if we could see it (we couldn’t). Then I came along the back side of the mountain, crossing over a saddle on the west side. (There were a couple of guys and a dog working an old mine shaft up there and I wonder what they think of the helicopter flying over them every 10 to 12 minutes or so.) I came through the canyon where Robson’s is nestled, pointing out the trail to the petroglyphs along the way. I flew jsut to the east of town, where everyone could see me but not be bothered by the sound of the helicopter, before circling around to land back in my LZ.

The passengers were all thrilled. They always are. It’s a rewarding job.

When it seemed as if we were done and the event was winding down, I shut down and took a walk with Mike, John, and Lorna to enjoy the event. The crowds were gone and it was pleasant. We bought $1 ice cream cones (brings back memories, doesn’t it?) and watched the old engines run out back.

Later, when we were ready to leave, there were a few people gathered around the helicopter taking photos. Two men who were part of a party of three people wanted rides. Since they were going back to Wickenburg, I offered to take them there for the same $30 each. (That’s where being a Part 135 operator really pays off; I can do that kind of stuff.) They agreed and while their friend drove to Wickenburg, we took off, overflying Robson’s one more time as we headed back to Wickenburg.

I should be doing similar events like this down in Buckeye and up in Yarnell over the next few months. I’m hoping to pick up a few new gigs in the meantime.

If you’re reading this in Arizona and think you have at least a dozen people interested in taking rides at $30 to $40 per person (prices depend on distance to the gig), give me a call. You can learn more at the Flying M Air Web site.

Helicopter Safe Flight Altitudes

How some people try to make up — and enforce — FAA regulations.

Yesterday, Mike and I flew out to Wenden to give helicopter rides to our friend, Celia, and her family. Wenden is a farming community primarily inhabited by Mexican farm workers. Its a tiny desert town in what must be a fertile valley. Wells pump water into irrigation canals and the entire area is surrounded by a patchwork of farm fields. This time of year, the cotton harvest is over and big square bins of cotton line one field after another. Most of the fields are already plowed and readied for their next harvest; a few are even planted.

A straight-line route between Wickenburg and Wenden takes me right over the top of an airpark called Eagle Roost. Eagle Roost was the brainchild of a man with vision. He bought a section of land — that’s a mile square — in Aguila, another Mexican farming community. He laid in a north-south runway, paved it, and sold 5-acre lots all around it. Back when I first started coming to this area about 10-12 years ago, the lots were going for $8,000 each and the place wasn’t very impressive. They’re now worth considerably more, and most lots have been built up.

Eagle Roost is the home of mostly retired people who are (or were) pilots. Like Wickenburg, half the population disappears during the hot summer months. Although the development isn’t bad, the town of Aguila has nothing much to offer. There are one or two small convenience stores, three restaurants, and a motel. Most people speak Spanish. On weekday mornings men gather in predetermined places, waiting to be picked for work crews. On Tuesdays (I think), there’s a farmers market. The place has terrible flies during cantaloupe harvest. There’s nothing much to do, so most Eagle Roost residents seem to do a lot of internal socializing, gossiping, and drinking. When they need something, they drive 25 miles east to Wickenburg or about 75 southeast to Phoenix’s west valley.

We used to have friends out there, but after a disagreement with one of them, another one told me he didn’t want to be friends with me anymore. (And no, he isn’t a third-grader.) No loss, as far as I’m concerned.

Anyway, whenever I fly from Wickenburg to points west, like Wenden, Salome, Vicksburg Junction, or Quartzsite, I usually fly right over the top of Eagle Roost. I’ve been doing it since I got my first helicopter, back in October 2000. More than five years now.

Don’t get me wrong — I don’t fly out there often. I don’t have reason to. There’s not much west of Wickenburg to fly to. As I mentioned elsewhere, Wickenburg is on the edge of nowhere. West of there is nowhere. But I definitely do it at least a few times a year. In fact, I did it a few weeks ago when I flew out to Quartzsite to research possible landing zones for a gig there.

Now in case you don’t know, helicopters fly lower than airplanes. In fact, there’s no set minimum altitude for helicopter flight. When I’m in Wickenburg, in or around town, I normally fly at 500-700 feet above the ground, but when I’m out in the desert, I sometimes fly lower. This is so for two reasons. The main reason is so I can see the stuff I’m flying over — range cattle, people off-roading out in the desert, the trickles of water in a spring-fed canyon creek. If I wanted to get from point A to point B without seeing what I was flying over, I’d fly an airplane. And that brings up the second reason I fly low: to avoid airplane traffic.

It’s a common joke among helicopter pilots. You mention that you flew at a certain higher-than-usual altitude someplace and a fellow helicopter pilot says, “Why the hell were you all the way up there? That’s where the planes are.”

We also joke about nosebleeds.

If you’ve been following along, you’ve probably guessed by now that I fly over Eagle Roost — and most other places I fly over — at less than 500 feet above the ground. I did it yesterday, on the way out to Wenden.

Now although very few of Eagle Roost’s residents are active pilots, there are a few who do actually own planes and fly them. So I treat Eagle Roost about the same as I treat Wickenburg. It’s a Class G, uncontrolled airport. Common courtesy — but not FAA regulations — dictates that you listen in on the airport frequency as you approach and depart the area and make one or more radio calls to announce your intentions and solicit responses from other pilots in the area. So, on the way west, I tuned into Eagle Roost’s frequency about six miles west of Wickenburg. I made a radio call as I passed south of Forepaugh, a historic airport that seems to have had its name wiped from aeronautical charts.

A minute or two later, I heard a call from someone at Eagle Roost departing runway 17 with a downwind departure. I had to translate that into direction. Helicopter pilots don’t have much use for runways so we don’t pay much attention to runway numbers and directions. It takes thought to decipher what the pilot had said. Since runway numbers correspond with compass directions, the pilot was taking off on the runway that pointed roughly south. Downwind was the direction parallel to the runway, but going in the opposite direction he’d taken off. That meant he was departing to the north. We were east and still pretty far out, so we were no factor. Mike and I actually discussed this thought process yesterday, comparing notes about how airplane and helicopter pilots think.

There were no more calls from Eagle Roost and no more traffic. I made a call three miles east, giving my altitude and intentions: transitioning to the west. Then I made another call when I was over the airpark. Then we were west, speeding along at a healthy 110 knots to our destination, still 25 or 30 miles west.

I circled the town of Wenden to find Celia’s street. She lives in a house between two farm fields, off Alamo Lake Road. I followed Alamo Lake Road with my eyes, saw her house, judged the wind from a flag, and decided to come in from the west. I lined up with an east-west road that ran right past her house. It was a farm road, made to give access to the fields. But it was Christmas Eve day and a Saturday, so the fields were empty. No one was using the road. I landed in a huge cloud of dust about 50 yards from her front door, where she and her family had gathered when they first heard us coming. The breeze from the east was pretty stiff, so the dust cloud swept past me when I idled down, so it didn’t actually reach where everyone was standing.

Celia Takes a Helicopter RideI gave four rides, each with three people on board. It was Celia and her daughters and their husbands and kids. Mike handled the ground crew work. I gave short rides — there’s not much in Wenden to see — and everyone really seemed to enjoy it. I gave helicopter toys to the little kids. The dust was incredible on my takeoffs and landings and my fears were confirmed when I shut down in Wickenburg later on: a little more paint had been sanded off the blades.

When we were finished, Celia invited us in for burritos. But I had another charter at noon and wanted to get back to Wickenburg. So Celia gave Mike a package of burritos and he climbed on board. Soon we were on our way back to Wickenburg.

Of course, we flew over Eagle Roost again. We’d been on the same frequency since we’d left Wickenburg and there was no one talking on the radio. Mike and I kept an eye out for planes, as we usually do, and didn’t see any. I made my first radio call about 3 miles to the west and didn’t hear a thing from anyone in the area. But when I made my second call when I was overhead, the radio suddenly came to life.

“When you fly over the airport, fly above traffic pattern altitude,” came a man’s voice.

“Zero-Mike-Lima is a helicopter,” I told the person who’d called. “Helicopters fly below traffic pattern altitude.” No lie there.

“Helicopters have to follow the rules, too,” the voice said. If there hadn’t been an edge to it before, there was now.

“I’ll have to look that one up,” I replied.

“You do that.” Now definitely nasty. “The FAA would be interested.”

“Then I’ll ask the FAA,” I replied, thinking I might send my Part 135 contact at the Scottsdale FSDO an e-mail if I couldn’t find the rule. (Some people are afraid of the FAA. I’m not. All of my dealings with the FAA have been very fair and everyone I’ve worked with at the local FSDO has been very helpful and informative. So if this guy was trying to scare me, he wasn’t succeeding.)

By this time, I was about a mile or two to the east. The man, who Mike and I figured was on the ground because he didn’t provide an N-number, didn’t say anything else.

I looked at Mike. “Is there a rule like that?” I asked him.

“I don’t think so,” he replied.

“I’ll look it up,” I repeated. I have the 2006 FAR/AIM in my hangar. And we continued east, with the episode tucked in the back of our minds.

Unfortunately, that wasn’t the end of it. I was sitting with Mike and a few other pilots at a picnic table at Wickenburg airport, waiting for my noon charter and eating burritos when my cell phone rang. I looked down and saw a familiar phone number. When I answered it, I heard the voice of the Eagle Roost idiot who said he couldn’t be my friend all those years ago.

“I have absolutely no desire to talk to you,” I said. And I snapped the phone shut.

It started ringing again almost immediately. I pushed the button that would silence it. Then again. Sheesh! Some people just don’t get it. I turned the phone off.

We talked to the pilots we were with about the “rule” we’d been told about while over Eagle Roost. Mind you, we were sitting with three other active pilots — the kind that actually fly — and none of them had ever heard of such a rule for an airport in Class G airspace, let alone a private airpark that doesn’t even appear on current GPS maps.

I turned the phone on a while later and there were three messages on it. I let Mike listen to them. Two were from potential customers. The other was from the idiot at Eagle Roost. For some reason, this guy has become the “Godfather” of the airpark and everyone goes to him with their problems. And although the original cause of the breakup of our friendship years ago was because I hadn’t “minded my business” when his buddy was sleeping around behind my friend’s back, this guy has no problem minding other people’s business. He’d called to talk to me about flying over Eagle Roost. Supposedly, the guy who’d talked to me on the radio swore that there was another plane in the pattern. He claimed I was being dangerous and I’d been belligerent. And this former friend of mine had been assigned to talk to me about it. The hell with that.

One thing was already pretty obvious: the guy was lying about the plane, probably to cover up the fact that he didn’t know what he was talking about. I have four pieces of evidence to prove it:

  1. Neither Mike nor I, experienced, active pilots who were sitting in the front seat of an aircraft with virtually unlimited forward and side visibility, did not see another aircraft, even though we were both looking.
  2. No other pilot made a radio call. And yes, I do realize that the pilot could have been operating without a radio, but then who’s being safer: me with two radio calls or him with none?
  3. If the guy on the ground was so concerned about our altitude because of other traffic, why didn’t he mention the other traffic?
  4. How did the guy on the ground know there was other traffic if he was inside listening to his radio and the phantom pilot hadn’t made a call?

My charter passengers arrived right about the time Stan had the espresso machine fired up. I did two charters while everyone else went to Stan’s for a latte. By the time I was done an hour and a half later, Stan had closed up shop and most of the other pilots had gone home. I settled up with my passengers and locked up the helicopter on the ramp. I was schedule to fly Santa to a remote ranch at dawn on Christmas morning.

Mike said that the pilots gathered at Stan’s had discussed the “rule” at length. They all agreed that there was no such rule and that I hadn’t done anything wrong.

We had some repairs to make on our airport golf cart and Mike left to get the parts. While I was waiting, I washed the chicken dust off my car and spent about 20 minutes going through the FAR/AIM for the “rule.”

I found the helicopter altitude rule I’d already committed to memory: Helicopters may operate at an altitude lower than airplane minimum requirements as long as operations do not pose a danger to persons or property on the ground. This is paraphrased, of course — I don’t have the FARs in front of me right now. But this is the rule we’re taught and we discuss it at length. Although it seems like it’s a free pass to fly wherever you want, if something does happen and you have an emergency landing and someone on the ground gets hurt, the FAA could always say that you were not operating at a safe altitude. So safety is always the primary concern when choosing a minimum altitude. For a helicopter, that means operating within the safe area of the height-velocity diagram, a document that establishes safe altitude and airspeed combinations to make a power-off landing. Of course, terrain has a lot to do with it, too. There needs to be a flat open space within range to land. Like a farm field? Or a runway at an airpark? So as far as that rule was concerned, I was operating at a safe altitude.

I also found another helicopter rule that was pounded into my head when training: helicopters are to avoid the flow of fixed wing traffic. This is the rule that keeps helicopters low. In fact, whenever I operate in a Class D airspace — that’s an airport with a control tower —-and I want to approach my landing zone or cross over the top, I’m directed to stay below the traffic pattern altitude. Even when crossing over the top — and I can’t tell you how many times I crossed over the top of Scottsdale while working on on my private helicopter rating. Just the other day, when leaving Scottsdale Airport, the tower cleared me to depart and directed me to remain below 2,000 feet — or below the traffic pattern altitude. I come and go at Prescott below the TPA and, when I was training at Grand Canyon Airport to work for Papillon, I was constantly reminded by my instructor to stay below 7,000 feet MSL — below the traffic pattern altitude. (Of course, that put me right over the treetops, which wasn’t a comfortable place to be, at first.) As a result of all this work in Class D airspace, it’s become natural for me to cross airports below the traffic pattern altitude. I never expected to be told that there was a rule to the contrary.

I looked for, but did not find, any rule stating required — or even recommended — altitudes for any kind of aircraft operating in the vicinity of a Class G airport. So what the hell was this guy talking about?

I reported my findings to Mike as he worked on the golf cart. We went home, stopping at Safeway for some wine to take to Christmas dinner at a friend’s house the next day.

Belligerent. That word bothered me. I asked Mike if I’d been belligerent on the radio. He said I hadn’t but the guy who’d talked to me had definitely been belligerent. So I asked Mike to call the idiot at Eagle Roost and tell him I wasn’t belligerent.

Mistake. The guy talked poor Mike’s ear off. And, as usual, he didn’t believe anything Mike had to say. Talk about a trap door mind. One of his neighbors had sworn something to him, and the idiot, our former friend, was willing to believe him instead of us. Radio man said that a plane had been in the pattern and I had been belligerent. Period, end of story, trap door swings shut. Poor Mike listened to the idiot far longer than I would have. I felt bad for him when he finally hung up.

Like I said, no loss.

Tomorrow, I’ll give my FAA contact a call and ask him about this “rule.” He’s a helicopter guy, so he’ll know. And if there is no rule, I’ll just pretend the whole thing never happened.

PostScript

I called my POI at the Scottsdale FSDO and talked to him. Twice. He confirmed what I suspected: there is no rule in the FARs specifying an altitude for untowered airport overflights. That applies to both airplanes and helicopters. However, he added in his best FAA voice, a “prudent pilot” would overfly above the traffic pattern altitude. He went on to provide some examples of how overflight at a lower altitude could cause problems.

So I was right but I was wrong. And so was the guy on the ground.

In my opinion, if something happens while you’re flying in Class G airspace — like a midair collision or even a near miss or a forced go-around — then one of the pilots (at least) is not being prudent. It doesn’t matter what the situtation was: if a rule wasn’t broken but someone did something dumb that caused a problem, that someone wasn’t being prudent. But if nothing happens? Then is there a question of what’s prudent? I don’t know. But I do think that if the FAA felt strongly about altitudes at Class G airports, it should amend the regulations to specify an altitude. That would turn a gray area into black and white. What good are regulations if you can’t use them to guide you in your actions?

I also spoke to a fellow helicopter pilot who lives in the area. “Do you ever fly over Eagle Roost?” I asked.

“Once in a while,” he replied.

“What altitude?”

“Usually about 400 feet.”

So I wasn’t the only one. “Do you talk on the radio?” I asked.

“No.”

He didn’t add what we both knew: The regulations do not require communication in Class G airspace. But who’s being more safe? The pilot who attempts communication or the one who just buzzes through without a peep?

What is the lesson to be learned from this? It isn’t one the FAA would like.

The lesson is that when you overfly an airport without a published radio frequency, don’t talk on the radio. Eagle Roost’s frequency does not appear on any chart and the airport is not listed in the Airport/Facilities Directory, the only two documents a pilot is required to have onboard (and I’m not even sure the A/FD is required for all pilots, although it is required for Part 135 operations). If I hadn’t responsibly made my radio calls, the guy on the ground wouldn’t have even known I was flying over. He’d have nothing to get his blood pressure up. He wouldn’t have called the idiot to harass me. None of this would have happened. Heck, you wouldn’t even be reading a blog entry about it.

Fortunately, that’s not the lesson I learned. I learned that residents at private airparks are a bunch of whiners who like to boss around anyone within radio range. They like to make up stories about possible accidents and share them with anyone who will listen and take their words as gospel truth. And some of them even like to take it beyond the radio, with harassment by phone and in person.

As for me, I won’t overfly Eagle Roost again. It just isn’t worth the headaches that go with it.

Two Interesting Charters

I find that there’s more to flying helicopters than giving tours.

Lately, I’ve been getting calls from folks who want to use my helicopter for more than just transportation or tourism.

The first good assignment I got came a few months ago, when I flew a camera crew around the a carmaker’s test track in Arizona. I wrote about it in another blog entry. This past week, I did two more.

The first, on Tuesday, was for a professional photographer hired to take aerial and ground photographs of the new bridge being built over Burro Creek on state route 93. There’s already a beautiful bridge there and the construction crew is building a twin on the north side of it (the road runs pretty much east-west there). Burro Creek runs in a deep canyon there and the Sonoran desert landscape is breathtaking. The site is also far from civilization — about 55 miles north of Wickenburg and perhaps 20 miles south of Wickiup.

It was a cold morning when we left Wickenburg, so I left the helicopter’s doors on. It took us about 30 minutes at my top cruise speed (110-115 knots with two on board and full fuel) to reach the site. I set down in a fenced-in area where the construction folks were storing cactus to be replanted after work was done. I took the passenger door off while my client got his camera equipment out — a pair of Hasselblad medium format cameras with three different lenses. A construction truck pulled up and my client got out to talk to the driver. He came back and told me that the next time I landed, I could land on the new road right near the bridge. It was closed to traffic and was smoothly paved. We took off and began circling the bridges from various altitudes. My client snapped away, cranking the camera’s advance do-dad after each shot. He was perfectly at ease leaning out the door; he’d flown in many helicopters before. After about ten of fifteen minutes of that, I set down on the road near the bridge and shut down. (I had to set down on the edge of the road, as shown in the photo below, because the road was banked for a curve and the only real level spot I could find was at the very edge of the road.) My client climbed out, filled a smaller camera bag with equipment, and walked off to take his ground shots.

I pulled out my iPod and a book and settled down on the side of the road to read. Cars and trucks drove by and I wondered how many of them were headed to or from Wickenburg.

He was gone about 90 minutes. When he returned and finished fiddling around with his equipment, we climbed back on board and I fired the helicopter back up. The light had changed, so we did another 10 or 15 minutes of circles around the bridge at all different altitudes. Then he told me to head back and I broke off circling and headed back.He took some more photos on the way back — using up extra film on shots he thought he might be able to sell the construction folks. Then we set down on Eric Barnes’s dirt strip, on route 93 near the Santa Maria River, so I could put the door back on. With the door off, it was loud and my speed was limited to 100 knots. With it on, it was quieter and I could get it up to 120 knots. When we got back to Wickenburg, I’d put 1.4 hours on the Hobbs. My client paid for that, as well as for some waiting time.

Two days later, I was in Aguila, doing a job for the maker of a “breadcrumb” communications system. Breadcrumb systems, as they were explained to me, create a wireless network that can be used for voice, data, or video communications. The folks who hired me had an impressive system they wanted to mount in the helicopter. The idea was to have me fly around with the system and a few techs on board to see how well the system stayed connected to other breadcrumbs on the ground and how well video that one of my passengers shot could be seen at ground-based stations.

As the photo here shows, I had to remove both doors on the pilot side so they could mount the unit’s antenna. The breadcrumb box itself was positioned at the feet of the passenger behind me; you can barely see it in this photo because it’s just a flat box standing on one end. Although the unit can be powered by batteries, my helicopter has a 28 volt DC port that looks like a cigarette lighter port. The breadcrumb had a cable that could take this voltage, filter it, and step it down to the 12 volts it needed. So they just plugged it into my DC port. The boss of the operation wasn’t happy about the positioning of the antenna — he wanted to dangle it somehow under the helicopter’s body — but we soon proved that it was fine.

One of the techs also had a GPS and, at first, they wanted to mount it on my tailcone. They claimed that in the work they’d done with RC helicopters, they’d found that there was too much interference from the main rotor disk for the GPS to get a good signal. When I told them that my handheld GPS worked in the cockpit cabin, they decided (to my relief) to give it a try. (For the record, I would not have let them mount it on my tailcone. That’s much too close to the tail rotor! We might have mounted it on a skid if we had to.)

My passengers climbed aboard and we took off, flying circles around their base of operations at Robson’s Mining World. One guy in the back did the video while the guy beside him kept reporting on the status of the breadcrumb: green, blinking green, green, green, etc. We kept in touch with other breadcrumbs on the system at all altitudes and even when we flew behind a mountain. We only lost touch once, and that was for only a few seconds. The video went down to the guys on the ground, who clustered around a laptop set up on the hood of a car in the parking area. We did this for about 20 minutes, then landed.

I didn’t realize it then, but I was done with my assignment. What followed was about an hour spent giving everyone there a ride. I took them three at a time and did a 4-minute ride around the base, climbing up the mountain behind Robson’s and descending back into the desert for landing in my designated landing zone. When everyone had their ride, they told me to shut down and have lunch with them. Some other folks would be taking photos of the setup while I was eating.

I ate outside, with the guys from Rotomotion. They build RC helicopter systems to be used for surveillance and unmanned observation. The company founder started the company when he got frustrated that he couldn’t fly an RC helicopter. (Having owned one for a while, I know exactly how he feels; I couldn’t fly mine, either.) He wrote a computer program that would fly the helicopter for him. His company now builds helicopters that work with his Linux-based software system. They had three helicopters with them: a small electric model (on the table in this photo), a medium diesel model, and a large model powered by a chain saw engine.

The software is extremely cool. Once the helicopter is airborne, the software takes over and can hold it in an absolutely perfect out of ground effect hover. You can also tell it to go to certain coordinates at a certain altitude and it’ll go. It uses wireless communications to control an onboard camera or other equipment. If it loses its radio control signal, it’s programmed to return to its home base. Although they have a routine for software-controlled take off, they need a reliable but small altimeter to judge distance from the ground before a good landing program can be written. I have no doubt that they’ll add this feature soon. These guys definitely know what they’re doing.

While the rest of the group went off to go shooting out in the desert, a small group of us remained to watch the RC helicopters fly. A police officer from Chandler had come up to get a demonstration and we just watched. He said that the system has many applications in law enforcement and he seemed excited about it.

I went home a while later and put my dusty helicopter away. I’d logged 1.6 hours for the assignment — not much, but enough to make it worthwhile. And the technology I’d seen while I was out there was well worth the time spent.

Flying for Food

Mike tries to arrange a group outing for lunch.

We were at Stan’s house on Saturday afternoon when Mike said, “Let’s go fly together somewhere tomorrow.”

Stan’s wife, Rosemarie, and Dave, another local pilot, were there. Stan flies a Cessna 182 and Dave just got a second plane, an RV-4, that he needed to build time in before he could take up passengers. Mike is half owner of a Grumman Tiger.

What followed was a discussion of various responsibilities the next day. We finally decided to meet at the airport at 1 PM and fly somewhere for lunch. The “somewhere” wasn’t decided.

On Sunday morning, during breakfast, Mike and I started to discuss where we could fly. We brainstormed and came up with a list of airports within flying distance that had restaurants nearby:

Restaurants on Field:
– Prescott
– Falcon Field (2!)
– Payson
– Kingman
– Deer Valley
– Glendale
– Scottsdale
– Chandler
– Winslow (weird hours)

Restaurants within walking distance:
– Seligman
– Valle
– Chiriaco Summit (CA)

Restaurants within free shuttle distance:
– Parker (restaurant at the casino)
– Bullhead City (restaurants across river in Laughlin)

Quite a selection. (Note that Wickenburg isn’t on this list. Why someone with a few bucks doesn’t build a restaurant on the field is beyond me. I know why I don’t do it: I’ve already been through the employer nightmare in Wickenburg and have learned my lesson.)

Sunday morning progressed. We had chores to do around the house. We even cleaned a small part of the garage! Then Mike made the fatal error of attacking the mistletoe that had begun killing some of our mesquite trees. (Mistletoe is a parasitic plant and, if not periodically cut out of the trees it infests, it’ll kill the trees.) It was hard work that required him to stand in awkward positions with a heavy saw over his head. After 45 minutes of that, he was too tired to do anything. Including fly.

That didn’t bother me. I wanted to fly anyway. I felt pretty confident that I could get to the destination around the same time as the two planes. Zero-Mike-Lima cruises at 110 knots, but I could easily push it to 120 knots with only two people on board. I’d already called Jim to invite him to join us with his Hughes 500c. Although he wasn’t sure he would, it would be nice to have two helicopters with the two airplanes. I was hoping we’d go to Falcon Field; I really love the Italian restaurant, Anzio’s Landing, on the southeast end of the runway. And there’s plenty of parking right out front.

By the time we got to the airport at 12:40 PM, the wind had kicked up a bit. It was blowing across the runway at about 8 to 10 knots. Airplane pilots don’t like crosswinds. When no one had arrived by 12:55, I got the feeling that Mike’s plan wasn’t going to become a reality.

Jim was already there, working on his Beech 18. He bought the Beech a few months ago in Florida and managed to leak 10 gallons of oil from one of its engines on the ferry flight back to Arizona. Since then, he’d been working on finding and fixing the leaks. He thought he had it taken care of when he flew out to Blythe for some touch-and-goes the other day, but the left engine was still oozing. A bad O-ring on one of the cylinders. He has to pull the cylinder to fix it. In the meantime, he’s begun pulling just about everything else. Last month, he pulled out the floor and replaced it. He’s now waiting for new runners on which to mount the rear seats. Yesterday, when we arrived, he was pulling instruments out of the panel and rearranging them in more logical positions. His helicopter was not at the airport. His wife, Judith, had already said she didn’t want to come with us, so Jim had decided to work on the Beech — something he could probably do for the rest of his life if he wanted to.

Stan and Rosemarie drove up right around 1 PM. I was talking to Jim when they pulled up, so I missed the beginning of their conversation with Mike. But the end result was that they’d come with us in the helicopter. Dave wasn’t coming. So a flight that started with potentially four aircraft ended up with just one.

Of course, with the helicopter, the list of dining opportunities increases. Helicopters don’t need no stinkin’ runway. There were at least five more places we could eat:
The Wayside Inn, near Alamo Lake, is the destination for Flying M Air‘s “Hamburger in the Middle of Nowhere.”
Robson’s Mining World, in Aguila, has a nice little cafe.
– Wild Horse West, near Lake Pleasant, has great burgers.
– The Kofa Cafe, out in Vicksburg Junction, used to be very good, but I haven’t been back since
my first experience with the new owner.
– A truckstop on I-10 south of Vicksburg has a dirt strip out back where you can land and not dust the truckers.

Mike wanted to go to the Wayside Inn, so that’s where we went. You can read all about it in another blog entry. The food ain’t bad and the atmosphere is definitely different, especially if you live in a big city and don’t have much exposure to an off-the-grid lifestyle.

We flew by way of Robson’s, which was pretty quiet that afternoon. Robson’s big anniversary celebration is coming up on the first Saturday in January, and I think they get more visitors in that one day than they get all year long. I do helicopter rides out there during the event and it’s always a lot of fun. Then we followed Ballard Wash (I think) from its narrow start almost all the way to Alamo Lake. I circled the Wayside once, trying to find a flag to judge the wind, then realized there wasn’t much wind there and just set down in my usual spot near the intersection of two dirt roads and the old, unmaintained dirt strip. (If you ever fly out there in a small plane, I recommend landing on the road rather than the strip; it’s a lot smoother and better maintained.) I kicked up a huge cloud of dust that drifted to the east as I cooled down the engine and shut down.

We crossed the road and went into the restaurant. Everyone at the bar looked at us. “I knew it was you,” the waitress said.

“Yeah, well…” I said. Everyone laughed.

We had lunch among the fish photos and trophies. The place was relatively quiet. The last time we’d been in there with helicopters, a crowd had gathered and the restaurant was completely full. I guess having four helicopters and a plane parked outside is a bit of a draw to the locals. But that day it was just us and a man eating at the bar. A few people came and went.

We paid up and left. As I started up, a few people in ATVs parked at the end of the dirt strip, facing us, ready for a show. They were not rocket scientists. Not only had they parked right in front of me, forcing me to depart in a different direction so as not to overfly them, but they were close enough to get seriously dusted when I took off. I took off to the northwest, along the road to Alamo Lake.

We did a tour of Alamo Lake, then the Santa Maria River, and then Date Creek before heading into Wickenburg. It had been a nice little outing — even if we were the only aircraft to participate.