Real Life Flying: Researching Client Requests

Doing your homework is part of flying safely — and legally.

This afternoon, I got a call from a potential client. He’s the manager of a country club that does catering for weddings and other big events. He wanted to know if it were possible for me to land my helicopter on the country club property after dark, pick up a couple — say a new bride and groom — and fly them around Phoenix for about 45 minutes before dropping them off at a hotel with a helipad or an airport where a limousine would be waiting. He also wanted to know whether it was okay for them to have some wine while aboard the aircraft.

Off the top of my head, I said, yes, we should be able to do that. But then I listed the things I’d have to check out before giving a definitive answer.

I thought this might make a good topic for a blog post for commercial helicopter pilots interested in real life helicopter missions. You see, commercial helicopter flying is not always as easy as picking up two passengers at an airport, flying them around for a while, and returning them to the starting point. So, as an example, I’ll discuss the things that come into play for this particular kind flight.

Landing Zone

Mansion LZ

Off-airport landings are something I’m accustomed to. Photo by Jon Davison.

First and foremost is the safety of the landing zone. How big is it? Is it level? Are there obstacles such as trees, buildings, or wires? What are my approach and departure paths like? Can it be controlled to prevent onlookers from coming too close or walking behind the aircraft? How about neighbors? Are there homes in the area? Is it close to another airport where air traffic control might be an issue? Since landing and departing will be at night, can the landing zone be properly lit so I can find it and land safely on it?

I made an appointment to meet with the client to see the landing zones he had in mind. Hopefully, one will work. I also checked the location of the country club using the satellite view of Google Maps. Although its golf course is indeed surrounded by homes, there’s also a nearby freeway and shopping center that’s likely to be empty at night. I could see some possible approach and departure paths, but could not judge obstacles, such as light posts or wires.

As for a destination hotel — if one is found, I’ll have to go through the entire process there, too. It’s more likely, however, that I’ll just land them at Deer Valley Airport, which is my home base.

Local Ordinances

Of course, no off-airport landing would be possible without a lot of hoop-jumping if there were a local ordinance that prohibited off-airport landings. Scottsdale has such an ordinance, enacted, primarily, to prevent local helicopter pilots from doing asinine things like landing in residential subdivisions. (I guess it was done one too many times.) Wickenburg’s ordinance isn’t quite as restrictive; it states that landing is possible with the permission of the Police Chief. When I asked the Police Chief about this some years ago, he had no idea what I was talking about.

The client said that the mayor the country club’s city is a member, so if there was an issue, he might be able to get permission on an as-needed basis. But when I hung up the phone with him, I started making other calls. First, the local police, to see if they knew of any ordinance. They directed me to the city’s compliance office. They told me they had no ordinances, but that I should check with the FAA. I already know that the FAA is fine with landing a helicopter on private property, as long as it is done safely and in accordance with any related FARs.

So this would not be an issue for this particular location. No hoop-jumping necessary.

Passenger Loading

Night Flight Over Phoenix

The lights of Phoenix are beautiful at night. Photo by Jon Davison.

The client wants to use the helicopter as part of the event’s entertainment. At the predetermined time, the guests would be guided to “the patio” (wherever that is) where they could watch the helicopter come in for a landing. The bride and groom would climb aboard and the helicopter would take off, perhaps doing a quick circle of the area before departing.

This sounds great and its sure to make a memorable wedding party. But passenger loading could be an issue here.

Is the client willing to wait for the helicopter to cool down and shut down before the passengers are loaded? And then wait again while the helicopter starts up, warms up, and spins up before departure? If the wait is okay, the pilot (me) can do the passenger briefing and loading. While this might not make for good entertainment, it is the safest option.

The other option is “hot loading,” where the passengers board the helicopter while the engine is running and blades are spinning. Many people will simply not do hot loading, but I will — provided there’s a qualified ground crew to escort all passengers to their seats and ensure they’re buckled in. That means operating with someone on the ground — likely my husband — who would arrive before me and handle briefing and loading duties.

While you might think I prefer the first option, I actually prefer the second. It minimizes the amount of time I’m on the ground and ensures a qualified person is there to handle my next concern: crowd control.

Crowd Control

I firmly believe that a spinning helicopter is more dangerous on the ground than in the air. My tail rotor is literally invisible when it’s spinning — even at idle speed — and if someone walked into it, they’d be dead. That’s why I always set down in a landing zone with my tail pointed away from where people are most likely to be. Any helicopter pilot who doesn’t do this is looking for trouble.

Unfortunately, when landing in an uncontrolled area, there’s nothing to stop people from running up behind the helicopter. There’s a restaurant in Peoria, AZ that I used to land at for lunch quite often. It’s in a relatively remote area with lots of open desert around it. I always landed just outside the parking area with my tail rotor facing away from the building. The last time I landed there, however, a bunch of kids on off-road motorcycles saw me come in and began swarming around the helicopter as I was shutting down. Good thing my husband was with me to keep them clear. I haven’t gone back since.

When I inspect the landing zone, I’ll try to determine how well it can be controlled. And then I’ll put a plan in place to control it for my arrival. Having a reliable and experienced ground crew person will certainly help when the time comes for me to operate there.

Alcoholic Beverages

The final request that requires research is the glass of wine during the tour. FAR 135.121(a) states:

No person may drink any alcoholic beverage aboard an aircraft unless the certificate holder operating the aircraft has served that beverage.

This means they can’t bring their own alcohol aboard — it’s also why you can’t legally bring your own alcohol aboard an airliner!

If you’re wondering who the “certificate holder” is, well, so am I. It’s either me personally — since I have a single pilot Part 135 certificate and I’m the pilot — or it’s my company, Flying M Air. If it’s me, serving wine while I’m at the controls of a helicopter will be nearly impossible. If it’s my company, I can theoretically have an employee or agent of my company serve the alcohol for me, preferably right before we take off.

If there are any pilots out there who have real knowledge about this, please do use the Comments link or form to share what you know with me. Otherwise, I’ll just ask my FAA Primary Operations Inspector (POI). He’ll either tell me or help me figure it out for myself based on what I know.

One thing I do know: if I can’t legally serve alcohol on the flight, I won’t. No client request is more important than my certificate.

FAR 135.121(b) and (c) offer two other rules regarding alcohol:

(b) No certificate holder may serve any alcoholic beverage to any person aboard its aircraft if that person appears to be intoxicated.
(c) No certificate holder may allow any person to bard any of its aircraft if that person appears to be intoxicated.

That means I can’t serve them if they’re drunk and I can’t even allow them to board the aircraft if they’re drunk. This is something I need to make sure the client knows. It would be a shame if I brought my shiny red helicopter in for a landing at the big party and the bride or groom was too shitfaced from champagne to fly. (It would be a bigger shame if one of them puked on my leather seats.)

The Other Usual Stuff

Every flight has the usual collection of pilot tasks before it can be completed. I’m talking about things like calculating weight and balance, getting weather and NOTAM information, creating a flight plan, preflighting the aircraft. I might want to do a daytime landing at the landing zone in advance, just to make sure I was familiar with it. There’s lots of the usual responsibilities, none of which can be taken lightly for any flight.

This Is What It’s All About

This should give most folks an idea of what goes into planning what seems like a simple mission. Any pilot faced with a client request like this who doesn’t look into these things — at a minimum — is simply not doing his job.

I’ll know by Saturday, when I review the landing zone, whether we’ll be able to work for this client. I hope so. It would be great to have some regular gigs like this throughout the year.

Ash Scattering Woes

Things don’t always go as planned.

I did an ash scattering the other day. Normally, that wouldn’t be a big deal. I’ve done ash scatterings before. (Read about two of them here and here.) But this one didn’t go exactly as planned.

By ash scattering, I mean the aerial scattering of cremains. Cremains is short for cremated remains. That’s what the next of kin get in a baggie and a box when someone is cremated. An ash scattering normally refers to scattering those remains over a large tract of empty land.

My Technique

I should start out by saying that I have ash scattering from a helicopter down to a science. After several trials, I’ve got a technique that works like a charm — for most scatterings, anyway. I get some tissue paper — the kind of paper you might put inside a gift box around a shirt or other item of clothing. I spread it out. The family (or friend) pours the cremains onto the paper. They gather up the corners and sides and twist them at the top to make a kind of paper package of the departed’s remains. This is all done inside, where there’s no chance the wind will foul things up.

Then we climb into the helicopter with the person responsible for scattering the cremains sitting behind me. All doors are on. I start up and fly to the location where the remains will be scattered. I climb to at least 1,000 feet over the target area. Then I bring the helicopter into a high hover — or at least a very slow flight speed.

We close all vents except the one in the ash scatterer’s door. The whole time we’ve been flying, he’s been holding the cremains in its paper package on his lap with the top still twisted closed. He untwists the top and grasps the package by its top. He slips it out through the vent and tosses it gently away from the helicopter.

The package is closed at first, but as it begins its tumbling descent, the wind whips it open. The ashes explode from the paper in a poof and drift away with the wind. The paper also falls to the ground, but since it’s thin, uncoated tissue paper, it’s likely broken down by the elements within a few months or a year.

I like this technique for several reasons:

  • It scatters the ashes with a certain amount of dignity. (One of my clients even bought their own tissue paper. It was printed with a pattern of shoes because the woman who was being scattered had liked shoes.)
  • It prevents the ashes from blowing back into the helicopter when dumped out.
  • It prevents the ashes or their packaging from creating a danger to the helicopter’s tail rotor or other parts.
  • It does an amazing job at scattering the ashes over a wide, open area.

Unfortunately, I didn’t use this technique on Saturday.

Saturday’s Scattering

Saturday’s ash scattering mission was tough for two reasons:

  • The next of kin were the adult children of the two cremated people they wanted to scatter. They were not small people. The lightest one weighed in at 216 pounds. Add me and you have four fatties on board.
  • The ashes were to be scattered over the family orchards, which covered a mere 30 or 40 acres and were surrounded by other farmland and orchards.

Clearly, I’d have to fly lower and use a different technique to scatter the ashes over such a small area. And because we were so heavy, I’d have to drain all but about 15 gallons of fuel out of the helicopter so I had the power I needed to fly low and slow without getting into trouble with the power curve.

We kept it simple. The ash scatterer would sit behind me and dump the two bags of ashes out through his vent. He’d do everything possible to make sure the bag opened on the outside of the helicopter. I made sure he clearly understood what would happen if he let go of the bag and it got into the tail rotor.

I examined both bags of cremains before the flight. The technology has come a long way. The mom’s ashes, created five years ago, were of a sand-like consistency, with very few grains larger than a tiny pebble. The dad’s ashes, created only recently, were powder-like.

We were all in good spirits when we did the flight. I took them out over the target area and made a high reconnoissance as they pointed out the orchard blocks. Apples, pears, and cherries. (Wash your fruit, readers!) The wind was coming from the west at about 7 miles per hour and would really help me deal with the weight I was carrying. I could point into the wind and fly on a diagonal while the scattering was being done behind me. But also to the west was a set of high tension power lines. If I got into a settling with power incident — which I’d have to identify before it became a problem — I’d have to avoid the wires on any kind of escape route. The best thing to do would be to keep moving at a speed above ETL. I’d come in from the northeast for my pass.

With that plan made, the ash scatterer prepared the first bag. I came in over the northeast corner of the first orchard block about 200-300 feet up. On my word, he began dumping ashes out of the helicopter. I could see through the corner of my eye how they streamed behind us. I pointed the helicopter into the wind and flew almost sideways to keep the ashes away from the aircraft as well as I could. I was probably doing about 20 knots ground speed.

The second bag had a small hole in it, which was discovered when the ash scatterer’s sister handed him the bag. (And yes, I still have bits of Mrs. B all over the back seat of the helicopter.) Those remains followed the first. I only had one moment when there was a power issue and I resolved it quickly by picking up speed.

Then we were done.

We made a pass over the family home before returning to the airstrip where I’m based for the summer. I set down on the concrete pad, cooled the engine, and shut down.

Cremains on Helicopter

The white dust you see is the cremated remains of Mr. & Mrs. B.

But it wasn’t until we got out of the helicopter that I noticed a fine dusting of Mr. and Mrs. B on the right side of my helicopter.

The family wasn’t the least bit upset about their parents hitching a ride on the side of the helicopter. Or even about bits of mom in the back seat. They were more concerned about cleaning it up for me. But I told them I’d take care of it, after making sure vacuum use wouldn’t bother them.

Then I did a complete walk around of the helicopter, opening up panels to make sure there were no traces of cremains inside any of the compartments. I also looked in the fan scroll area behind the engine. It looked clean, too. The only thing that looked as if it could be a problem was the air inlet behind the right passenger door. As shown in the photo below, it apparently got a heavy dose of dust.

The Extent of the Dusting

I flew the helicopter at least two more hours that day. I gave some rides to a grower’s kids and three hired hands. I flew to Cave B to join the ash scatterers for a celebratory lunch. I flew up the Columbia River as far as Chelan, where I spent the day with a friend, and flew back at high speed along the Waterville Plateau, landing at dusk in 95° heat.

The helicopter flew fine. Cylinder head temperature was up a bit more than average on the last flight of the day, but I figured that was due to my high speed and the hot temperatures. I’d seen it that high before when flying during Arizona summers. It wasn’t anywhere near red line — it was just a bit higher than the tickmark on the gauge where it normally sits.

I’d hoped that Mr. & Mrs. B would get blown off the aircraft, but they didn’t.

Cremains in Air Filter
Cremains sucked into the air intake on the side of the helicopter. The filter will be replaced today.

The air filter had me worried. It would likely need to be replaced. I called my Seattle mechanic on Sunday morning. He proceeded to tell me about all the damage that could be caused by the cremains. Best case scenario: none of it got into the engine. Worst case; it did and was already grinding away at moving engine parts. I was told that symptoms of a problem would include increased oil use and overheating. He promised to overnight the filter for Tuesday delivery.

I went out to the helicopter with a sponge and bucket of clean water and sponged Mr. & Mrs. B off the side of the helicopter. Today, when I go out to change the filter, I’ll bring along a vacuum and inverter so I can vacuum Mrs. B out of the back seat.

And I’ll monitor the helicopter’s operations closely in flight, keeping an eye out for overheating and other indications of a problem.

You can bet that the next time I scatter cremains, I’ll do it with tissue paper and a high altitude drop.

Weight & Balance Woes

Or why I had to turn down a potentially lucrative charter flight.

One of the things I’ve said again and again is that it’s nearly impossible to load a Robinson R44 helicopter out of CG. Nearly, but not completely.

What is CG?

For those of you unfamiliar with the term CG, it stands for center of gravity. All aircraft have a specific center of gravity or point at which they could (theoretically) be lifted and hung level. While an aircraft doesn’t need to be in exact balance to fly, there are limitations to which it can be loaded out of balance. These limitations form an envelope of acceptable loading and if you’re loaded within this envelope, you’re said to be within CG or simply in balance. The aircraft controls are rigged with this in mind.

If you load an aircraft out of CG, you’re asking for trouble. For example, if I load my helicopter too heavy on one side, I could run into trouble in a turn by not being able to move the cyclic enough in the opposite direction to come out of the turn. After all, all controls have limits, normally defined by a physical stop. Running out of right cyclic while trying to come out of a left turn would be very scary indeed. Of course, I probably wouldn’t get to that point because I’d feel the problem as soon as I pulled up into a hover — I simply wouldn’t be able to keep the aircraft from drifting left.

[Note to all you flight instructors out there; if I completely mangled this description — since I’m not a CFI — feel free to step in to clarify in the Comments. This is my understanding after 10 years and 2,000+ flying hours, but I never had to teach it to anyone.]

Pilots are required to have an aircraft Weight and Balance (W&B) calculation on board for every flight. This is part of the Federal Aviation Regulations (FARs) in the U.S. In non-commercial flight, it’s usually enough to have the W&B for the empty aircraft. But in commercial flight, there are usually requirements for an individual W&B to be calculated for each flight with the given load.

So yes, when you fly on a commercial airliner, there’s a computer program somewhere that’s spitting out a W&B calculation for your flight. Your pilot has it in his possession in the cockpit.

Now you might say, “Hey, wait a minute. How do they know what I weigh?” They don’t. They’re allowed to use estimates. It all depends on the airline’s Operating Specifications (Ops Specs), which are established with the FAA.

I have Ops Specs, too, but I’m not allowed to estimate for my Part 135 Charter work. That’s why I ask for the name and weight of each passenger when I book a flight.

Four Fatties is Too Many

When I asked for names and weights yesterday while booking what was supposed to be a 2-hour aerial survey charter, I got three weights that I knew would be trouble:

A: 240 lbs
B: 220 lbs
C: 195 lbs

That’s 655 pounds of passengers alone.

Add the pilot (who is trying hard not to reveal her weight; don’t do the math, guys!) and you could only put on about an hour and 20 minutes worth of fuel to stay below the 2500 lbs max gross weight — the absolute maximum weight of the aircraft at takeoff time — limitation of my Robinson R44 Raven II.

Of course, the situation gets worse when you factor in the simple fact that all passengers lie about their weight. Every single one of them. If I put a scale out and made them stand on it, I guarantee anyone over 200 lbs. has shaved at least 10 pounds off their weight when reporting it. They either don’t figure the weight of their clothes or they’re in denial about their weight or they’re afraid that I’ll say they weigh too much. Even folks under 200 lbs are guilty of this. So I routinely add 10 pounds for each passenger. That 30 pounds corresponds to 5 gallons of 100LL fuel or 15-20 minutes of cruise flight.

Since I’m really supposed to have 20 minutes more fuel on board than I expect to need — per FAA reserve requirements — I was really sunk. Apparently, I’d be able to load up my passengers and just enough fuel to take us on a brief flight around the departure airport.

This is just the weight portion of the equation, which is easy enough to do. Add empty aircraft weight to passenger, baggage, and pilot weight. Then add the weight of required fuel. If the number exceeds 2500 lbs, something’s got to come off the aircraft. It can’t be the pilot and it can’t be the fuel required to complete the mission. Simple as that.

How the CG Stacks Up

While I could have done the math in my head, I did it as part of a complete CG calculation. It’s a pain in the butt do to one of those manually, but I have a spreadsheet solution that I worked up to do it for me. I punch in the weights and amounts of fuel and it draws the CG envelope with points for takeoff weight and empty fuel weight. So while manually doing this task would likely take 15-20 minutes of calculator punching, I can do it in about 30 seconds. I can also easily play “what if” by changing fuel quantities and moving the passengers into different seats.

Here’s what I got for the proposed flight and 2 hours of fuel on board:

Weight and Balance Example

Note that both points (square and triangle) are outside the boundaries of the CG envelope. The red line indicates the rotor mast. The points clearly indicate that the CG is way forward. In other words, I’m front-heavy. If I pick up to a hover, I’m likely to start drifting forward immediately. I may hit the back stop of the cyclic when I try to stop that forward motion. In other words, I won’t be able to stop.

Of course, the aircraft is also 100 lbs over weight.

Just for grins, I moved the passengers around in a what-if scenario. I’d put the biggest guy up front, since that’s where the leg room is. After all, maybe he’s not fat. Maybe he’s a former professional basketball player. It doesn’t matter for my calculation how tall a person is — all I care about is weight. But if he’s got long legs, he’s likely to be miserable in the back seat.

So I put the light guy up front and got something like this:

Weight and Balance Sample

A little better, but not safe or legal. But I kept playing. I really wanted to do this flight. The only thing left to fiddle with was the fuel, so I started off-loading fuel on my worksheet until I got within weight limitations. I needed to drop 99 pounds to get down to 2500 takeoff weight. That’s 16.5 gallons or about an hour’s worth of fuel. This what-if scenario would produce be for a short flight, with only 56 minutes of fuel on board:

Weight and Balance Example

And this is where the sad truth of the matter emerged. It didn’t matter how little fuel I had on board — we would always be out of CG for this flight. Too many fatties on board. Both points remain outside the envelope.

I called the client back and told him the problem. I said that together, we weighed too much. I gave him two options: leave one of the passengers behind or fly with a company that had larger aircraft. I suggested a company based in Scottsdale. He wasn’t happy, but he understood.

I’ll be interesting to see if the big fatty (A in my list above) gets left behind. If he does, we’ll be good to go — with full tanks, as you can see here:

Weight and Balance Example

Another Day, Another Flight

Adding to my flight journal.

It was 1 PM yesterday afternoon when the Concierge of a downtown Phoenix resort confirmed a Phoenix tour for two at 3 PM, departing from Scottsdale Airport. The helicopter and I were in Wickenburg.

I took down the particulars, hung up, and went into my office. I created a flight plan and the weight and balance I needed to be legal for my Part 135 charter work. Then I took a very quick shower, dressed in black jeans with a button-down Flying M Air logo shirt and black shoes, and fled to the airport with my paper work.

The Flight Down

Things were quiet (as usual) at Wickenburg Airport when I arrived. I opened my hangar and did a preflight. Everything looked fine, but I was low on fuel. I swapped out the old Airport/Facilities Directory with the current one — again, required to be on board for all Part 135 flights — got in the golf cart, and towed the helicopter out to the fuel island. A while later, I had 3/4 tanks of fuel and was warming the engine on one of the “helipads” on the west end of the ramp.

The tow cart owned by one of Wickenburg’s other helicopter owners — there are four of us here — was on the pad beside mine. I wondered where he’d gone and whether he was having fun. Unlike me, he can afford to fly anytime he likes. Flying is costly and I’ve gotten to the point where I only fly when I have to — or have someone else picking up the tab.

That day’s flight was out of Scottsdale Airport, which was about 35 minutes away by helicopter. I wished they’d chosen Deer Valley Airport, which was 10 minutes closer, but I offered the option of Scottsdale and they’d taken it.

[This map, which I created at the request of one of the concierges, shows my Phoenix-area pickup locations. It’s interactive, so you can click a blue bubble to learn more about a location or zoom in to see the exact pickup location.]

There was no one in the pattern when I brought the rotors up to 100% RPM and made my departure call. I took off over the ramp, followed the taxiway parallel to Runway 05, and climbed out quickly. I dialed Deer Valley (DVT) into my GPS as I turned to the southeast. Soon I was flying over town and past my friend Tom’s ridgetop home just south of town on my way to the city.

Flying conditions were good. Very little wind, a few high, thin clouds. I’d checked the weather as part of my flight plan and knew the winds were light and variable all over the valley. It was also warm — 75°F. It would be an easy and comfortable flight.

I flew at about 400 AGL over rolling cactus-covered hills. Down below me, here and there, were RVs and ATVs making the most of our public land. The dust from a dirt bike traced the line of a trail in the near distance.

E25 to SDLI was halfway to Deer Valley when my TIS woke up and began picking up signals from Sky Harbor. I was very surprised to see a target at my altitude just a few miles away. I looked but didn’t see anyone in the sky there. I was tuned into the Northwest/Northeast practice area frequency (122.75), as I’d be passing right through the Northwest practice area. A flight instructor made a radio call to announce that he was doing ground reference work over the Quintero Golf Course at 2800 feet. My altitude. What the hell was a plane doing down in helicopter territory?

I made a call with my location and altitude about a minute later. I got a bit of pleasure when I saw the altitude indication for his target on my GPS climb several hundred feet. Scared ya.

I didn’t have to worry about airplane traffic as I passed between the hills on the southwest side of Lake Pleasant. None of the training airplanes would dream about being that low. A rocky desert terrain, surprisingly green from winter rains and studded with tall saguaro cacti passed beneath me in a blur. Out on the lake, there were dozens of sailboats — not very common on a lake normally filled with motorboats and jet skis. I descended with the terrain, made another call as I passed south of the New Waddell Dam and Lake Pleasant, and continued southeast.

I tuned my GPS’s comm to the Deer Valley ATIS and listened for the altimeter and runway in use. I wasn’t landing, but I wanted to know what the other traffic would be doing. When I cleared the area near Pleasant Valley Glider Port (P48), I turned more southbound toward Deer Valley. I crossed Carefree Highway a second time and tuned in Deer Valley’s North Tower.

“Deer Valley Tower, Helicopter Six-Three-Zero-Mike-Lima, nine to the northwest with Gulf, request transition along the canal toward Scottsdale.”

“Helicopter Six-Three-Zero Mike-Lima, Deer Valley Tower. Proceed as requested at or below two thousand. Deer Valley altimeter Three-Zero-One-Four. Report over the canal abeam the tower.”

I repeated the altitude restriction and headed toward where the Central Arizona Project canal crosses I-17, just inside Deer Valley’s airspace. The canal crosses both runway centerlines remarkably close to runway ends, but the altitude restriction put me below the landing traffic. It wasn’t that busy at Deer Valley anyway — probably fewer than four planes in the north traffic pattern.

I dropped down to 1800 feet as I hooked up with the canal and began following it southeast bound. The water was glass-like and reflected the few clouds high overhead. I wondered whether the people whose homes backed up against the canal were bothered by a helicopter flying past their backyards.

I made my call abeam the new tower. It’s been in operation about a year now and is huge, towering over the desert floor on the north side of the airport, midfield. I was told to monitor the south frequency. I’d already dialed it in and pushed the radio’s switch button.

I popped up about 100 feet to give myself extra space as I crossed some high tension power lines, then dropped back down to 1800 feet again. By then, I was crossing the runway center lines. Once clear, I called the south tower, requested a frequency change, and got it.

I listened to the Scottsdale ATIS on my GPS comm while I tuned into the tower frequency on my main comm. They were landing on runway 21 and the altimeter was the same. I punched Scottsdale (SDL) into my GPS.

I keyed my mic. “Scottsdale Tower, Helicopter Six-Three-Zero Mike-Lima, six to the northwest over the canal, request landing at the terminal with Alpha.”

The controller was a woman. Although I think I recognized her voice, she obviously didn’t recognize my N-number. She asked if I was familiar and I told her I was. Then she told me to continue inbound and report 2 miles west.

I left the canal and steered more southbound so I could come in more from the west. Now I was passing over homes and freeways, a good 500-700 feet off the ground. I heard the controller talking to another helicopter landing at Westworld for the Barrett-Jackson auction going on there. Then a jet getting an IFR clearance. Then I was about 2-1/2 miles to the northwest.

I called in. The controller cleared me to land, instructing me to stay east of the runway and taxiway. I repeated the landing clearance and restriction back to her. It was only after I’d released the mic button that I realized we both meant west. I debated calling her to clarify, but I knew that she meant west because to remain east, I’d have to cross the runway to the side opposite the terminal. So I didn’t call her. Instead, I just came in over the air park buildings, turning to parallel the runway on the west side for landing. A while later, I was setting down on the ramp with a Landmark Aviation guy in front of me, directing me as if I were some kind of commercial airliner. Silly.

The Tour

My passengers showed up a while later. I was waiting in the terminal for them. I’d wiped down the cockpit bubble to get the few bugs off before going inside to meet them.

They were a pair of newlyweds, in town for the big football game. Cardinals against Philadelphia, I think. He was in real estate and had been in helicopters a few times before. He was also a fixed wing pilot. She’d been in a helicopter only once before. I gave them the safety briefing and loaded them on board. He let her sit up front while he sat behind her.

One Tour of PhoenixMy passengers wanted to see a mix of desert beauty with cacti and city. I had already planned to take them up to Lake Pleasant and the flight out there would give them all the desert they wanted — and more. Then I planned to take them south, past the Cardinals Stadium. We’d finish up with a flight up Central Avenue, then right on Camelback so they could see their hotel from the air. From there, we’d return to Scottsdale Airport.

The flight was supposed to take 50 to 60 minutes. That’s how I advertise it. I don’t do the same route each time. It really depends on the passengers and the weather and the time of day. Since these folks were staying in a hotel on Camelback, I figured I’d stay north of Sky Harbor so I could easily fit an overflight into my plan. Since I was shorting up the distance that way, I’d have to lengthen it with a flight up to the lake.

Timing is always tricky. You come in too short and the passengers could get pissed off. You come in too long and you’re throwing money away. The trick is finding that happy medium — and being smart enough to adjust speed along the way to make it work.

This particular plan required me to talk to Scottsdale, Glendale (GEU), Sky Harbor (PHX), and Scottsdale airports’ control towers. I had to use six different radio frequencies and change my transponder squawk code twice. It was almost choreographed, like a dance, with very little time between communications points to change frequencies, think of what to say, say it, listen for the response, and react accordingly. All the time, I was narrating a tour, pointing our places of interest, and answering questions. My passengers were very talkative and I had to isolate them three times to hear instructions from a controller.

I like talkative passengers. It gives me a way to read their satisfaction about a flight. I really hate passengers who just sit there quietly. You never know if they’re happy.

Main highlights on this flight included horses in people’s backyards in Scottsdale, open range cattle and cattle ponds, dirt bikers, the lake and sailboats, the canal, Cardinals Stadium, mobile homes on the west side of Phoenix, Central Avenue “skyscrapers,” Camelback Mountain, the resort where they were staying, the mall where they’d used their American Express card the night before, and pools.

The flight took about 52 minutes. I consider that short, but my passengers were happy. I think they had something scheduled afterwards. I walked them back into the terminal, got paid, and left.

The Flight Home

The flight home was about the same as the flight out, but in reverse. I managed to screw up the frequency for the north tower at Deer Valley (should have been 120.2 but I was listening to silence on 122.2) and was off-radio for about 2 minutes. I realized the error and fixed it just as the controller was trying to raise me. I got scolded and felt like an idiot — especially since one of my friends was flying in and probably heard the whole exchange. Sheesh.

Hot Air Balloons from AboveNorthwest of there, I passed some hot air balloons being inflated. Since one was already fully inflated and I worried about the effect of my downwash, I kept my distance as I circled to take this shot with my Treo. Then I dropped down and skirted the empty desert, low level. I passed by some horses that may or may not have been wild — they didn’t seem the least bit interested in me. More campers, more quads, more lines of dust in the distance. I climbed back up to 500 feet AGL when I reached the homes on the outskirts of Wickenburg. I overflew my house and saw Mike on the driveway, waving up at me, before landing at the airport.

I put the helicopter away, feeling tired, hungry, and thirsty. I’d flown 2.2 hours and had earned enough to make one half of a helicopter loan payment.

A Perfect Storm

Why I’ve been neglecting this blog.

I don’t have much time to write this — and that’s the reason I haven’t been writing more regularly. I like to compose at least 5 blog posts a week, yet this is only my third in just over a week. The last post — a video — doesn’t really count, since I didn’t write anything.

So why the neglect? As I mentioned above: time.

Every once in a while, life throws a perfect storm at us. You know what I mean — it’s a period of time when everything seems to go crazy at once.

In my case, it was the following, which have all occurred since July 29:

  • Completion of the annual revision of one of my books (ongoing throughout this period).
  • Reposition my helicopter from Quincy, WA to Seattle, WA.
  • Reposition my camper from Quincy, WA to Page, AZ.
  • Brief 3-day catchup period at home in Wickenburg, AZ.
  • Distribute the animals among multiple boarding facilities.
  • Trip to Seattle, WA.
  • Reposition helicopter from Seattle, WA to Page, AZ.
  • Set up housekeeping in my camper in Page, AZ.
  • Entertain an overnight guest in a very tiny camper.
  • Deal with FAA, airport manager, and local tour operators in Page regarding tour, photo flight, and charter work in Page, AZ (ongoing).
  • Provide moral support for my sister, who has been laid off from her banking job.
  • Three photo flights from Page to Monument Valley.
  • Start of new book with August deadline.
  • Three trips to medical facilities in an attempt to diagnose some severe back pain.

It’s this last thing that’s really gummed up the works. I did something to my back while I was home and the pain became unbearable after the commercial flight to Seattle the next day. I was in an urgent care clinic there where I got prescriptions for drugs I couldn’t take because I had to fly. The pain has varied from annoying but bearable to absolutely crippling every day since then, with one day so bad I was in the hospital emergency room. It hurt to sit and since I need to sit to write, I couldn’t work on the new book — let alone write blog entries.

Miraz hit the nail on the head in her Twitter comment to me, when she said, “Pain is so time consuming and draining.” Wow. I’d never really thought of it like that — probably because I’ve never been in such severe pain for so long.

So now I’m behind in just about everything, racing against the clock to finish a book that’s due tomorrow. (It ain’t gonna happen.) The pain is under control — yesterday was the first day that it was tolerable throughout the day — and physical therapy starts on Monday.

Please bear with me. I do have lots to write about. When I get this book off my plate and catch up on my FAA stuff, I’ll be back with some interesting (I hope) new content here.