Check Ride Prep Time

I get ready for my sixth Part 135 check ride.

Some of you may know that I hold what’s called a “Single Pilot Part 135” certificate. This is an FAA certificate that allows me to perform operations that a regular Part 91 pilot can’t perform. For example, I can pick you up at Airport A and drop you off at Airport B. I can also take you for a sightseeing tour more than 25 miles from our starting point. This might not seem like a big deal, but it’s very difficult — if not downright impossible — to build a business in aviation without the capabilities offered by Part 135.

There are three kinds of Part 135 certificate: Single Pilot, Single PIC (I think that’s what it’s called), and Basic. Single Pilot means there’s just one pilot doing all the Part 135 work. I can have two pilots in my company, but only one of them — me — would be able to do Part 135 flying. The other would have Part 91 limitations. A Single PIC is for companies with aircraft that require two pilots; one is always the pilot in command, but the second officer could be any qualified pilot. A Basic Part 135 certificate is not very basic at all. It allows multiple pilots in a company to operate under Part 135. It also requires all kinds of paperwork, training programs, and personnel.

I was a Part 135 pilot when I worked at the Grand Canyon. The company I worked for did all operations under Part 135 and had a basic certificate. I took my first Part 135 check ride with their check pilot. It wasn’t a huge deal.

When I ordered my R44, I applied for a Single Pilot Part 135 certificate. In February 2005, I took my first check ride for that certificate. Since then, I’ve taken a check ride with an FAA inspector every February. My 2009 check ride is tomorrow.

The check ride is like any other commercial check ride. There’s an oral part that lasts 1-2 hours. Then there’s a flight part that lasts about an hour. I’m expected to get all the important questions right and to fly safely, to commercial helicopter pilot standards.

Every year, the flights get easier. I don’t think it’s because they’re going easy on me. I think it’s because I’m getting to be a better, more confident pilot.

In FlightI now have over 800 hours on my R44 and I’ve flown just about every one of them. There’s something magical about flying the same aircraft all the time. You get to know its little quirks. And you can fly it without thinking — it’s as if it’s an extension of my hands and feet. I climb in, strap myself in, start the engine, and fly. It does what I tell it to do without me laboring over it. That’s a really great feeling.

Anyway, one of the reasons I haven’t been blogging as regularly as I usually do lately is because I’m prepping for my check ride. Cramming. I can never remember weather minimums — we don’t have much weather here in AZ — and I have to try again to remember them for tomorrow. Not that it matters much. The rules for airplanes don’t apply the same way for helicopters. But I’ll try to remember and hopefully get it right when I’m asked.

The rest should be pretty easy.

I’ll let you know how I did tomorrow afternoon.

Weather Flying

Two trips to Sedona in challenging weather.

One of the best things about being a pilot in Arizona is the weather. It’s darn near perfect just about every day. What else could a pilot ask for?

So when weather moves in, it’s a big deal. Especially when you need to fly in it.

Wickenburg to Sedona

Saturday’s flight had been booked a month in advance. Three friends from Phoenix wanted a day trip up to Sedona. To save money, they drove up to Wickenburg — which was on the way to their weekend place in Yarnell anyway — to start the flight at my home base.

I’d spent Friday night in Phoenix for Mike’s company Christmas party. When I woke at 6 AM, it was dark and rainy. But I had my laptop with me and wasted no time checking the weather. I’d told my client that I’d call him by 8 AM if we needed to cancel. If he didn’t hear from me, it was a go.

The forecast called for chance of showers before 11 AM, then partly cloudy. More showers after 11 PM. Sounded good to me. OUr flight would depart Wickenburg at 10 AM and we’d arrive in Sedona around 11, when any weather in the area would be moving out.

The drive home to Wickenburg was long but the weather was definitely clearing. There was some flooding on State Route 74 (Carefree Highway) not far from I-17. Nothing I couldn’t drive through, though.

At 9:30, when I pulled the helicopter out of the hangar and fueled it, there was still a layer of clouds sitting atop the Weaver Mountains. That wasn’t good.

Let me explain my usual route from Wickenburg to Sedona by air. I depart to the northeast, crossing the Weaver Mountains just east of Yarnell. Then I continue northeast, following the path of Route 89 through the Bradshaw Mountains and over the town of Prescott. Then I head skirt along the southern edge of Prescott Airport’s airspace and cross over the top of Mingus Mountain at the pass so I can descend right past Jerome. Then it’s north until I reach the red rocks and east until I reach Sedona Airport. I chose the route because it’s relatively direct, it shows downtown Prescott and Jerome from the air, and it completes a “red rock tour” outside of Sedona’s noise-sensitve areas and away from other helicopter traffic. The return flight is much more direct. I fly southeast over Oak Creek, then head southwest to Wickenburg, crossing the southern end of Mingus Mountain and the Bradshaws at Crown King or Towers Mountain, and passing east of the Weaver Mountains. You can see this usual route on the chart below; it’s the blue route.

Wickenburg to Sedona

You may have noticed that the word “mountain” is used extensively in the above paragraph. That’s because there are a lot of mountains here. The ones I have to cross range in elevation from 5000 to 8000 feet. While that’s not a big deal on a typical Arizona day, it is a big deal when the clouds are sitting at 6000 feet. All pilots know about mountain obscuration — mountains hidden by clouds. And smart pilots avoid it.

So one look at the Weaver Mountains made me wonder how much detouring I’d have to do that day and what the clouds looked like in the valley beyond the mountains.

But there was plenty of detour space. I could avoid the mountains entirely by flying around the west end. That would add time to the flight, which was billed at a flat rate. Not in my best interest, but neither is hitting a “granite cloud.”

By the time my passengers arrived, however, the clouds had lifted a bit. And since they really wanted to see Yarnell from the air, I headed that way. When we got close, I saw a clear path beneath the clouds and a clear valley beyond it. I popped over the ridge and even circled their weekend home once so they could get photos of it from the air. Then we continued on our way.

In the valley between the Weaver and Bradshaw Mountains, I’d estimate the cloud bottoms at 6,000 feet. I was flying at 5,400 feet, 600 to 800 feet off the ground, so I had plenty of space. But I decided to file a pilot report, since the weather forecast had nothing about the low clouds.

A pilot report — for those readers who are not pilots — is a report of observed conditions where a pilot is flying. Normally, pilots file pilot reports when they encounter unexpected conditions, like low ceilings, turbulence, or icing. These were low ceilings and they were low enough to get an airplane pilot in trouble. They were worth reporting. It’s unfortunate that more pilots don’t file pilot reports since, once filed, they appear on weather briefings for the area and they’re a valuable source of information for other pilots.

I think that hearing me talk to the Prescott Flight Service Station on the radio about the weather scared my passengers a bit. When I was finished, my client said, “If the weather is too bad, we can do this another day.”

I assured him that the weather did not pose any danger to flight. I then told him how interesting to me it was since I’m so accustomed to flying in perfect weather.

Meanwhile the tops of the Bradshaws were socked in pretty good, so I decided to go around the west side of Granite Mountain. That took us over the Williamson Valley Road area of Prescott and Chino Valley. From there, it was a straight shot past the northwest end of Mingus Mountain (which was also cloud-covered) to the red rocks. I did my usual tour, listening to my passengers ooh and aah. (It really is beautiful out there, even when the weather is overcast and otherwise ugly.) Then I landed at the Sedona Airport.

It was cold and windy there. We walked to the terminal and my passengers left me to have lunch at the airport restaurant, which overlooks the rock formations around Airport Mesa. I chatted with the FBO folks, placed a fuel order, and settled down with the IFR training material I’m reading in preparation for getting my instrument rating.

I got a call from one of the Phoenix-area resorts I occasionally do business with. They had a couple who wanted to do a Sedona Tour the next day. We agreed on times and my contact said she’d fax me the reservation form. As I hung up, I was glad I hadn’t delayed this flight for a day, making me unavailable for the next day’s flight.

I read about IFR flight instruments. It wasn’t terribly exciting. After about 20 minutes, I happened to look out a window. It was snowing outside, just southeast of the airport. One of the low clouds was dumping a flurry of flakes. While snow didn’t bother me, the fact that I couldn’t see through the snowfall did.

When I flew at the Grand Canyon, the pilots had a saying: if you can see through it, you can fly through it. I couldn’t fly through this little snowstorm.

Of course, I didn’t have to go that direction, either. So went outside and had a good look. There were little snow squalls here and there in every direction.

I went over to the computer they’ve got set up for flight planning and got on the National Weather Service Web site. The forecast had changed. There was now a 50% chance of snow showers. Duh.

Things looked good to the west. Although there was falling snow out that way, I could see sunshine beyond it near Mingus Mountain. That meant the snow was localized. It would probably blow through.

And it did. But other snow blew in to take its place.

Still, when my passengers returned, I didn’t want to wait around. I’d seen a good clearing to the west and I wanted to be through it before the situation at Sedona worsened. So we loaded up, started up, warmed up, and took off.

We were in snow showers almost immediately. Visibility wasn’t bad, though, and the air was still smooth. It was safe. It was just…well…different.

We got clear of Sedona’s weather and popped into the sun. But there was still a cloud atop Mingus Mountain, so crossing over the top on the way back wasn’t an option. And the weather radar I’d looked at showed me that conditions were better to the west than to the east, so I should avoid my usual return route. So after taking a low-level pass alongside the ghost town of Jerome, I headed northwest to retrace our route back the way we’d come.

We hit a bunch of snow along the west end of Mingus Mountain. I must have been flying in it for close to 10 minutes. My passengers were very quiet. But I kept chatting — as I usually do — to keep them at ease. Then the snow cleared out and we were flying with the clouds at least 1,000 feet above us. I looked for and found the indian ruins on top of one of the mesas in the area and pointed it out to them. A sort of consolation prize for taking the same route each way. When we got closer to Prescott, I thought I might be able to overfly it and follow Route 89 back to the Yarnell area. But by this time the wind had picked up and flying along the foothills of Granite Mountain was tossing us around a bunch. And since I couldn’t see the pass south of Prescott that I needed to slip through, I didn’t know it’s conditions. I didn’t want to look and see — I’d already done too much detouring on this flight and it was quickly losing profitability. If conditions were bad at the pass, I’d just have to come back, thus adding at least 20 minutes to the flight time. So I steered us around the west side of Granite Mountain again.

Ahead of me, in the Yarnell area, the clouds looked low again. So I detoured to the west some more, around the west end of the Weaver Mountains. That put us in the valley near Hillside. The clouds seemed to move up as we descended down to 4000 feet. I followed Hillside Road to Congress Mine, then detoured once again to the Hassayampa River just so see how it was flowing. From there, we made a quick pass over the town of Wickenburg before landing.

It was mostly cloudy but cold when we got out of the helicopter. It had been an interesting flight for me, but not one I was anxious to repeat. It had taken 30 minutes longer than the round trip flight usually takes and about 15 minutes longer than my budget for it. I hadn’t lost money, but it hadn’t been a very profitable flight, either.

But my passengers really enjoyed it and maybe I’ll see them again.

Scottsdale to Sedona

The next day is a good example of how quickly weather can change. I was scheduled to fly from Scottsdale to Sedona with two passengers at 2 PM.

I checked the weather shortly after getting up that morning. Partly cloudy, 10% chance of showers, high 46°F. Not bad at all.

I checked the weather again at 10 AM. It was the same. My passenger called right after that. I told him about the weather and that we were good to go. He promised to meet me at the airport at 2 PM.

At noon, I prepared my flight plans and manifests. I checked the weather again. Now it was mostly cloudy with a 50% chance of show showers. Dang!

I dug deeper into my weather resources. Flagstaff looked bad, with low visibility forecast right around the time we’d get to Sedona. Flagstaff is only 20 miles from there, but its up on a higher plateau. Was the altitude part of the problem? Would it be clear in Sedona? I called the FBO and asked what the weather was like. He said it was cloudy and that a small storm had passed through, but it was okay then. I got back online and looked for Webcams. I found a few in Sedona and they all showed good visibility. One of them even looked as if there was a little sunshine.

I called my passenger and left a message on his cell phone. Then I called the concierge who had booked the flight and told her the situation. I said I didn’t think it was a safety issue, but I thought the weather might make the views a bit less appealing. (Wow, did that turn out to be an understatement!) She wanted to cancel. She tried to reach the passengers, but couldn’t. I told her I needed to leave Wickenburg by 1 PM to get to Scottsdale on time.

I was warming up the helicopter on the ramp at Wickenburg when my cell phone rang. I answered it. It was the Concierge. She’s spoken to the passengers and they were still good to go.

So I went.

It was cloudy in Wickenburg but there were very low clouds atop the Weaver Mountains. I didn’t have to go that way. I had to go to Scottsdale, which is southeast. I passed through heavy rain in North Phoenix. I was sunny in Scottsdale when I landed, but it soon started to pour. I was wet when I got into the terminal.

Scottdsale to SedonaLet me take a moment to review my flight route from Scottsdale to Sedona. I fly northwest to Lake Pleasant and follow the shoreline up past the Agua Fria River to Black Canyon. Then I follow I-17 (mostly) to the southeast end of Mingus Mountain. I follow the mountain’s northeast slope to Jerome, then head north to the red rocks. I do my red rocks tour and land. The return trip takes us through Oak Creek and Camp Verde before climbing up along I-17 and following that back all the way to Phoenix. Again, it’s the blue line in this illustration.

I met my passengers, gave them a briefing, and loaded them up. One of them looked startled that the helicopter was so small. I talked to the tower and we took off to the north.

I could immediately see that the weather in the vicinity of Lake Pleasant would be anything but pleasant. So I headed north up into the mountains. The area was remote and undeveloped. All the little runoff channels were full of water, with waterfalls everywhere. It would have been kind of cool to fly lower and really see them, but I needed to climb to clear mountains ahead of us and I definitely didn’t want to get caught in the area if weather moved in.

It rained on us. It was mostly a light rain. The drops were pushed off the helicopter’s bubble by the force of the wind.

I couldn’t get much speed because my passengers (and I) were heavy and I’d topped both tanks off in Scottsdale. (You can never have too much fuel when weather is questionable.) We were not far from max gross weight.

We hooked up with I-17 just south of Cordes Junction. The freeway was covered with water — you could tell by the splashing of the car and truck tires. The clouds were low. North, along I-17, they seemed even lower. I couldn’t see the Bradshaws at all. I flew to Arcosante and circled it, telling them what it was all about. I also told them that I didn’t think I could go any farther toward Sedona. I was actually heading back along I-17 when I decided to take another look. I swung the helicopter around and, sure enough, the clouds had lifted enough for me to see the pass down into the Verde Valley. “Let’s give it a try,” I said.

Conditions improved a bit as I reached the pass. The clouds were much higher over the valley — primarily because the valley is much lower. I descended through the pass right over I-17. I skirted along the foothills of Mingus Mountain as I normally would, but lower. The top of the mountain was completely obscured. We reached Cottonwood and I still couldn’t see Jerome. It was in the clouds.

So I altered my course and headed northeast toward the first red rocks I could see. I’d start the tour there.

I should mention here that my passengers didn’t seem the least bit concerned about the weather. They were from British Columbia in Canada and they live, as one passenger told me, “in a rain forest.” Sadly, they’d come to Arizona for sunshine and it had been cloudy and/or raining since they arrived. They commented on all the terrain we passed over, asking me a lot of questions. Apparently he wants to buy a place here and she’s not convinced it’s a good idea. They did appreciate the views, especially when we got right up to the red rocks. I did a modified tour, going into a canyon I usually avoid, mostly because it was clearer than some of the other areas I do go.

It was snowing hard at the airport, and since they hadn’t been very interested in landing anyway, I decided to recommend against it. By big worry was that the weather would worsen while we were on the ground and that we’d be stuck there when the sun set in less than 2 hours. Then I’d have to pay a car service to take them back and I’d have to spend the night in Sedona. None of this would impress the Concierge that had booked the flight. My passengers understood the situation and agreed that it was best to continue. So we flew around Airport Mesa, getting a few last good looks of Sedona, and headed toward Oak Creek. We were only in snow for about 5 minutes.

The return trip was relatively uneventful, After crossing over Camp Verde, we climbed along the path of I-17. I’d been tempted to follow the Verde River south — it looked pretty clear that way — but did not want to get trapped in that canyon by weather, especially since my flight plan had me going a different way. When we came out atop the mesa north of Cordes Junction, I was surprised to see that the ceilings had risen by at least 500 feet. In the distance, toward Lake Pleasant, the sky was bright. Whatever had been there had cleared out. I headed toward the light.

A while later, we flew along the northwest side of the Agua Fria River. I showed them the ruins atop Indian Mesa and flew down the west side of the lake. We caught sight of a rainbow about 10 minutes out from Scottsdale.

My flight home was quick and easy. By 5 PM, the helicopter was tucked way in its hangar, clean from the rain.

In-Flight “Emergency”…

…on a check ride.

There’s no better way to test a pilot on his or her knowledge of emergency procedures than to simulate an in-flight unusual situation. I hesitate to use the word emergency here, because what most check pilots simulate is not really a full emergency. It’s more of a situation that requires the pilot’s attention, knowledge of procedures, judgement, and action.

Real Throttle Chops are a Thing of the Past

Gone (or almost gone) are the days when helicopter flight instructors or examiners did “throttle chops.” A throttle chop is a simulated engine failure in which the instructor or examiner twists the throttle to idle suddenly during flight. The engine and rotor RPM needles split and the rotor RPM needle immediately starts to drop. The student or pilot in command is required to immediately enter an autorotation. The experts estimate that the pilot has about two seconds to react properly. Failure to react could lead to unrecoverable low rotor RPM, which is a very bad thing.

Flight instructors and examiners pretty much stopped doing real throttle chops — the kind with absolutely no warning to the student — when helicopters started crashing. It seemed that in some cases, the student pilot or pilot in command wouldn’t react fast enough and the instructor or examiner didn’t either. Or, in some rare cases, the sudden reduction in power caused the engine to hiccup and really fail. Now most instructors usually warn the student in advance. Some slowly reduce the throttle, which leads to an audible change in engine sound that warns the student — not to mention that he or she can usually feel the adjustment in his or her collective hand. Others do a throttle chop and enter the autorotation at the same time, not even giving the student a chance to react.

Robinson Helicopter issued several safety notices recommending against throttle chops (see SN-27 and SN-38). The company even amended its Pilot Operating Handbook so practice autorotations would be done with just a tiny needle split rather than a full throttle-to-idle setting. (Not a very good simulation of an engine failure, if you ask me.)

So What’s an Instructor/Examiner to Do?

One of the instructor/examiners I’ve worked with in the past was extremely fond of failing instruments or illuminating warning lights. This particular instructor, who works for Robinson Helicopter, has a whole collection of circuit breaker tricks that he uses on unsuspecting students. He’ll pull an engine tach circuit breaker so the engine tachometer drops to 0 during flight. No lights, just that dead gauge. He does it to see how long before the pilot notices and whether the pilot knows what do do about it. He’ll do the same for other gauges that are important but not vital to safe flight.

I took my commercial check ride with this particular instructor/examiner and he made me do a run-on landing with “failed” engine tachometer, rotor tachometer, and governor (switch the governor off to simulate). The trick was to make very small collective inputs and hope the mechanical correlator would keep the RPM within range; listening to the sound of the engine helped a tiny bit. But I still managed to make that low rotor RPM horn go off as we approached the runway surface. Evidently, I exercised enough finesse, because although he was disappointed that the horn had come on, he didn’t fail me for it. Personally, I like to see him do it perfectly.

(A side note here. What real-life situation would require you to land with all that stuff inoperable? The only thing I can think of is a complete electrical failure. But even then, I think there’s some trick in the Robinson wiring scheme that keeps the tachs alive. Just can’t remember what it might be right now. Guess I need to look it up.)

My Recent Mechanical Failure

I’ve taken 6 check rides since I started flying about 8 years ago: 1 private, 1 commercial, and 4 Part 135s. There’s usually some kind of simulated failure during a flight. So when the Aux Fuel light came on during my most recent check ride on Thursday, my first inclination was to ask the examiner, “Did you do that?”

“What?”

We were doing an instrument approach at Williams Gateway Airport and I think he was paying more attention to my altimeter (I was supposed to be at 1880 feet) than anything else.

“That light,” I replied.

He saw the light. “No,” he said.

I didn’t believe him and asked him again. He repeated that he wasn’t responsible.

“Is the circuit breaker out?” I asked.

He looked down at the bank of circuit breakers at the base of his seat. “Yes.”

“Okay, it’s not a big deal,” I said. “It’s the auxiliary fuel pump. It’s a redundant system and we don’t need it for flight. The book says land as soon as practical. Do you want to push the circuit breaker back in?”

“No.”

(For the record, I would have.)

“Well, how about if we land here and have Kelly look at it?” I suggested. Kelly is my helicopter mechanic. By some unbelievable stroke of luck, we were landing at the airport where he was based and it wasn’t 5 PM yet.

He agreed that would be a good idea and talked to the tower for me. He then directed me to parking. I set it down in one of the helicopter parking spaces that Silver State uses. He pushed the circuit breaker back in. It popped back out. He got out to track down Kelly while I cooled down the engine and shut down.

Long story short: Kelly pulled off the side panel and found that one of the bolts on top of the fuel pump was loose. He removed the pump, bench tested it, tightened up the bolts, wrote up a logbook entry on a sticker for me, and sent us on our way. The whole process took a little more than an hour. The pump sounded much better when I primed the engine for startup and the light didn’t come on again as we did some more maneuvers at Williams Gateway and flew back to Scottsdale.

I passed the check ride. I like to think that the failed fuel pump helped me. It showed that I knew enough about the procedure to stay calm and make the right decision about it. In a way, it was a real-life “emergency” during the flight. Again, I don’t like to use the word emergency because there was never really any danger — unless, of course, the engine-driven fuel pump went bad, too. Then we’d have a problem.

Postscript

I flew back from Scottsdale with no further fuel pump problems.

The next day, I did a 50-minute scenic flight with two passengers on board. We were about 45 minutes into the flight — less than 5 miles from the airport — when the darn light came back on. I finished the tour — which was basically on the way to the airport anyway — and landed. When I pushed in the circuit breaker, it popped right out again.

When my passengers were on their way, I visited Ed, my local mechanic. I asked him to take a look at the pump when he had a chance, then put the helicopter away in my hangar, which is just down the row from his. He called with the bad news a while later. The pump was seized. I’d have to get a new one. I called the factory at 2:30 PM (their time) and managed to get it on a UPS truck for overnight (Saturday) delivery to Wickenburg. With luck, it’ll arrive as planned (Saturday deliver is a very iffy thing in Wickenburg) and Ed will put it in. I’ll be flying again on Sunday.

Unfortunately, it’ll take the flights I have scheduled on Sunday, Tuesday, and Thursday just to pay for the new pump.