On Truck Problems and Unbelievably Good Luck

They say we make our own luck, but how could I in this case?

I’m up in Central Washington State on a number of cherry drying contracts. My only means of transportation — unless you want to count my bicycle — is my husband’s 2001 Chevy Duramax Diesel pickup. It’s a great truck, well cared for and very reliable.

The other day, I started noticing that it was having trouble starting. It would start, but it needed more cranking than usual. I attributed that to my bad habit of listening to the stereo with the engine off while working on the helicopter. I figured that if I stopped doing that, the problem would go away after my next long, battery-charging drive to Wenatchee or Ephrata to fill the transfer tank with 100LL.

Yesterday was my big errands day. The weather was supposed to be good. I planned to do my laundry at 7:30 AM, then head up to Wenatchee to get some fuel, a new mattress for the RV, and some groceries. And maybe some sushi for lunch.

These grand plans came to a grinding halt when I turned the key in the truck. I waited, like a good girl, until the glow plug indicator (a diesel thing) had gone out, turned the key, and got the sound of an almost dead battery trying in vain to crank a diesel truck engine. Not enough juice.

Of course, I tried it a few more times. It just got worse.

I dialed my husband in Arizona. I figured I’d ask him if he’d ever experienced this kind of problem before and whether he had any tips on how I should start troubleshooting. But he wasn’t answering his phone.

And that’s when my next door neighbor here at the campground appeared, standing at the front of his travel trailer, wiping the sleep from his eyes. “Having trouble?”

He’d heard the dismal cranking sound and had come out to see if he could help. I produced a pair of jumper cables — the Girl Scout motto is “Be Prepared,” after all — and opened the hood. But instead of him pulling his pickup over to mine, he walked over with what looked like a brand new car battery. He put it on the ground beside the truck. Then he went back to his truck and came back with a battery tester. He tested both batteries in my truck. (Yes, it has two.) “They’re both a little low, but they should be okay. Sometimes it’s the connections. A loose wire or a gunked up terminal. Then the battery doesn’t charge right. You have terminals on the sides, but the ones on the top are better because they’re easier to keep clean.” He went on in the same vein, telling me more about car batteries than I ever wanted to know.

It was then that I remembered what this man did for a living: he traveled around the northwest, collecting and recycling car and truck batteries. In other words, he was a car battery expert.

How could I be so lucky?

We jump-started the truck from the battery he’d brought over and let it run for a while. That confirmed that the problem was not the starter. He pointed out where the connections could be a problem. I shut off the truck, then turned the key and restarted it. I asked him where I should go to get it fixed. He told me that if I took it to a car place, they’d probably try to sell me another battery, which I didn’t need. He was pretty sure I just needed my terminals cleaned. He said he could do it.

A Bad BoltTen minutes later, he was pulling off the terminal connectors and cleaning them with his wire brush. (For the record, I also had a wire brush in my toolbox.) One connector had quite a bit of corrosion — it might have been the culprit all along — and needed to be replaced; he pulled a new one out of his truck and did the job. (Do you know anyone who keeps new terminal bolts for side battery connections handy? Can you say Maria is lucky?)

We chatted while he worked. We talked about the geology of the area. He collected petrified wood and knew all about the Missoula Floods that had carved coulees through the volcanic rock of the area. “You should see them from the air,” I said.

“Yeah, that must be great.”

“When you’re done, I’ll take you and your wife.”

Ancient LakeSo when he was finished and I had everything put away, he followed me to the ag strip where the helicopter is parked. I had to do some interior reconfiguration — remove my helmet and the oil bottles under the front seat that I’m using for ballast, add headsets — and then we all climbed in. I took him and his wife for a 20-minute flight around the area that included downtown Quincy, Crescent Bar on the Columbia River, Quincy Lakes, the Gorge Amphitheater, and Frenchman’s Coulee. Along the way, I learned that he and I had the same birthday (different years) and that he’d won a helicopter ride when he was a kid in the late 1950s. He took pictures and said he’ll send me copies.

I really appreciated the way he stepped up and offered to help me with my truck problems. It’s nice to see that there are still people who are willing to come to a stranger’s assistance when they can. Most people couldn’t be bothered. Or they’d worry about liability.

He really appreciated the helicopter ride. He wouldn’t take any money for the parts or his hour or so of time in making the repair. This morning, before he and his wife headed out to their next campground, he stopped by to thank me yet again.

But it was me who needed to thank him again. Not only had he fixed my truck for free, but he’d given me a good excuse to go flying on a nice day — for a change.

The Trouble with Troubleshooting

I troubleshoot a Photoshop CS3/Mac OS X 10.6.3 problem.

Yesterday, after composing a blog post on my MacBook Pro, I went into my office with an SD card full of photos with every intention of choosing one or two to include in the post. I copied the photos to my hard disk along with my GPS track log and geotagged the ones I could tag. Then, after using QuickLook to make a preliminary selection, I opened five images with Photoshop CS3.

Or at least I tried to.

The problem was that Photoshop wouldn’t launch. It kept “unexpectedly quitting.”

And so began more than 2 hours of troubleshooting that culminated with my making an appointment today to visit the Arrowhead Apple Store down in Peoria, 50 miles from my home.

If you’re having this problem and are looking for a solution, read this post that I wrote this morning for Maria’s Guides.

This post is mostly about what a pain in the butt troubleshooting can be.

My troubleshooting process began with a Google search for Photoshop CS3 with Mac OS 10.6.3. I suspected the problem had to do with my update to 10.6.3 the previous week and I turned out to be right. There were discussions going on in the Apple forums about the problem. The most promising was titled “Installed 10.6.3 and now Photoshop CS3 won’t open.” The thread originator posted a quick description of the same problem I was having and got (so far) 167 responses.

Sadly, the responses were distributed over 12 individual pages, so I’d scan a page, click Next, and wait for the next page of responses to load before I could continue scanning. I don’t have a fast Internet connection in Wickenburg, so it was time consuming and tedious.

But it’s the content of the responses that I have a problem with. Only about 1/3 of them were of any use. The rest fell into one or more of the following categories, listed here with my comments.

  • Did you restart your computer? A person who can find and post a request for help in an Apple forum is likely smart enough to try restarting the computer before looking for outside help.
  • I’m using Photoshop CS3 with Mac OS 10.6.3 and I’m having that problem, too. Okay, what else can you tell us to help us troubleshoot?
  • I’m using Photoshop CS3 with Mac OS 10.6.3 and I’m not having that problem. So the rest of us are imagining it? Why not provide some info so we can learn how our systems differ from yours?
  • Did you try doing ABC? This comment might be helpful the first time ABC is suggested, but when it’s suggested a half dozen times and people have already reported that it doesn’t resolve the problem, it is a waste of time. Please read all the suggestions and the responses before adding your own.
  • It’s Apple’s fault. They don’t test updates. Don’t waste my time with this bull.
  • It’s Adobe’s fault. Their software sucks. Don’t waste my time with this bull, either.
  • It’s because you’re using a Mac. This problem doesn’t happen on Windows. What the hell are you doing on an Apple forum? Go play with Bing.
  • XYZ Program is better for photo editing than Photoshop. You expect me to toss a costly program I’ve been using for 15 years just because of a [likely minor] incompatibility issue? Get real.

It would be great if Apple’s forums had a way to vote down unhelpful comments so only the helpful ones appeared. I think we could have weeded out at least 100 of the comments that hid the solution. Or, better yet, offer some way to flag the comment that actually contains the “answer.” After all, the discussion thread was marked “answered,” so someone must have recognized one of the posts as a solution.

Adobe’s Web site had a TechNote that offered three possible solutions. One, which suggested turning off Rosetta, did not help me, since Rosetta was not enabled for Photoshop. I’m pretty certain the problem is related to an incorrectly entered serial number after having my logic board replaced two years ago. That’s what’s taking me and my 40 pound, 24″ iMac down to Peoria in two hours. Evidently, there’s no way for an end user to fix a serial number issue.

The net result of all this is that I lost two hours of my life to a troubleshooting exercise and will lose another three hours making a trip down to the Phoenix area to get a problem fixed on my Mac that was introduced by Apple.

Side benefit/drawback: I will get my hands on an iPad so I can give it a test drive. If they’re in stock, I’ll likely walk out of the store $500 poorer.

On Stiff Mixture Control Arms

The saga comes to an end…I hope.

If you follow the helicopter-related posts in this blog, you may know that I’ve been having a problem with my helicopter’s mixture control. My usual interface with this device is the red knob with a button on my instrument panel. Push the knob to get fuel flowing. Pull the knob to shut down the engine. Don’t mess with the knob in flight.

Simple enough, until it got stiff and then broke. I wrote about it here and here.

Mixture Control ArmTurns out, the reason the mixture cable became fractured is because the mixture control arm (lavender in this image) on the fuel control was too stiff. When I pushed or pulled the mixture control in the cockpit it was buckling and fraying. Pushing it in may not have resulted in full rich fuel, which could result in the engine running hot and lead to even more problems.

Good thing we caught it!

Fuel ControlEd, Wickenburg’s very best airplane mechanic, followed up by pulling the fuel control and fixing it, following instructions of the device’s manufacturer in Wichita, KS. Here’s what it looked like sitting on his workbench with the offending arm removed for repair. This is a lot more of my helicopter’s innards than I usually like to see. But it was interesting to see the piece I’d found an illustration of for this blog (see above) in a place where it was clearly recognizable.

Ed has since put everything back together. I was busy yesterday with the Endurance Ride, so I didn’t fly. And I don’t want to bother Ed on a Sunday. But come tomorrow morning, I’ll be at the airport with the helicopter out on the ramp. I’ll start it up and Ed will likely look at everything from below as its running to make sure the mixture is indeed full rich. I’ll pull the mixture and he’ll watch it work. And then he’ll sign off on it.

And give me a bill. (Ah, the joys of aircraft ownership!)

Of course, if things don’t go as planned, you’ll likely read more about it here.

No Flying this Weekend

It could be worse.

Robinson Mixture ControlThe other day, I reported a mechanical problem with my helicopter. In summary, the mixture control had been kind of stiff and it made a weird noise when I pulled it out. When my mechanic attempted to lubricate it, the mixture cable snapped.

The photo here shows a Robinson Raven II instrument panel very similar to mine. I’ve circled the mixture control. Remember: push in to allow fuel flow, pull out to stop fuel flow. Airplanes have similar controls. Airplane pilots adjust this in flight — that’s called leaning the engine. Helicopter pilots generally do not do this. It’s either in and the engine is running or out and the engine is stopped.

I didn’t make a big deal out of it then because it seemed to be a simple enough fix. We ordered the replacement cable from the factory and I figured that Ed, my local mechanic, would get that sucker installed not long after it arrived.

The more amazing thing to me — at least at the time — is that I’d proactively found and set about resolving a minor mechanical problem before it got me stranded somewhere inconvenient. The timing couldn’t have been better. The day before, I’d written an article for HeliNews about that exact topic. I was pleased that I’d learned a lesson.

Mixture Control SchematicWell, things are never as easy as they should be. Ed got the cable and went to work installing it. He soon ran into problems. The cable wouldn’t move smoothly. It wouldn’t go in all the way. He’s pretty sure we’ll have to order the entire cable assembly today. (This image, taken from Robinson SB-55, shows where the mixture cable attaches to the fuel mixture control. I highlighted the cable and its sheath in red. We ordered just the cable and it is apparently having trouble moving in the original sheath.)

Today is Friday. Although they could overnight the part for Saturday delivery, Ed doesn’t normally work on Saturdays. So I’ll save a few bucks on shipping and get it delivered Monday. With luck, it’ll be just what Ed needs and he can install it then.

Until it’s installed, there’s no flying for me.

But that doesn’t seem to matter much. I have no flights scheduled for this week and I have plenty of writing work to do. (I’m developing my third course for Lynda.com and have an open request for short how-to articles to fill for one of my publishers.) This weekend, I’m volunteering at the annual Land of the Sun Endurance Ride by marking horse butts with numbers, making my famous vegetarian bean soup, and timing in the 50-milers at the 25-mile manditory break. It’s almost a good thing that the helicopter is down for maintenance; less of a distraction for me.

I do want it running soon, though. Murphy’s Law of helicopter charter operations states that the most calls for your service will come in when you’re least able to meet customer needs. It must be a sign of the economy that my phone hasn’t started ringing off the hook yet.

A Flying Kind of Day

And proof that I apparently can learn a lesson.

I flew to Prescott, AZ today. I had to get my transponder’s biennial check and my annual medical exam done. Both my avionics shop and AME are based at the field.

How to Start an R44 Raven II

The first indication that I’d have a less than perfect day came when I started up the helicopter on the ramp at Wickenburg. The main part of the startup procedure on an R44 Raven II goes like this:

  1. Turn on the master switch. This provides electrical power to the aircraft.
  2. Push in the mixture to full rich. This enables fuel flow to the engine.
  3. Turn the key to Prime and count off the seconds. This uses the auxiliary fuel pump to prime the engine. The number of seconds depends on conditions such as outside temperature (cold means more priming) and engine temperature (already warm means less priming). This is something you get a feel for when you fly the same aircraft in all kinds of conditions.
  4. Turn the key to Both. This turns on both magnetos.
  5. Pull the mixture completely out. This cuts fuel flow to the engine.
  6. Push the starter button while slowly pushing in the mixture. The idea is that when the engine catches, the mixture should be full rich. This can be tricky, but most pilots get the hang of it pretty quickly.

When these steps are completed, the engine should be running. You then follow up with a bunch of other stuff to get the blades spinning and everything else working.

This morning, when I pushed in the mixture (step 2), it felt different — like it was scraping on something. It felt okay when I pulled it out again (step 5). Then it felt weird when I pushed it back in (step 6). The engine didn’t catch, so I repeated steps 2 through 6 again with a bit more priming. (It was cold out.) The mixture still felt weird when I pushed it in.

I debated whether I should shut down and talk to my local mechanic, Ed, about it. But then I convinced myself that the stiffness of the mixture cable was probably due to the cold. I finished my warmup and departed to the north.

Flight to Prescott

E25 to PRCPrescott is 30 minutes north of Wickenburg. It’s a “mile high” city, with an airport at 5,000 feet elevation. The airport is home to Embry Riddle Aeronautical University, as well as two helicopter flight schools. It’s a busy place, with three runways and a tower that occasionally splits radio coverage to two frequencies to handle the traffic load.

I’ve flown to Prescott more times than I can count over the past nine years. This morning, I planned a direct route. I departed from the ramp at Wickenburg and crossed the runway low level, heading 017°. Then I began my climb toward the first of two mountain ranges I had to cross: the Weavers. I had about 15 miles to climb from 2400 feet at Wickenburg to the 5,500 feet (minimum) I’d need to cross the mountains just east of the flat-topped Antelope Peak.

I was past Wickenburg within minutes, climbing at nearly 500 feet per minute at 100 knots. It was just after 8 AM and the sun was still low in the sky, casting deep shadows on the cactus-studded Sonoran desert below me. I listened to my iPod, catching up on Future Tense podcasts. The miles passed quickly. Soon I was crossing the Weavers and leveling off at 6,000 feet.

Now I was over the high desert, passing Yarnell, Peeples Valley, Kirkland Junction, and Wilhoit. I began another climb, to 7500 feet, to cross over the Sierra Prieta Mountains. There was snow on the north sides of the hills in the mountains below me. Ahead of me was the town of Prescott and the wide, flat areas of the Chino and Prescott Valleys.

I tuned into Prescott’s ATIS and used its altimeter reading to set my altimeter. Then I keyed the mic to call the tower. “Prescott Tower, Helicopter Six-Three-Zero-Mike-Lima is nine to the south with Zulu, request landing at Mile High Avionics.”

“Helicopter Six-Three-Zero-Mike-Lima, Prescott Tower, proceed inbound for landing on the numbers of Runway Three-Zero. Report two miles out.”

I read back the instructions and modified my course to come in from the southeast, pushing down the collective to begin my descent. I was cruising at 120 knots, descending at about 300 feet per minute. My course took me over the south end of Watson Lake and the Granite Dells. I was three miles out and had both the tower and runway end in sight when the tower came back on the radio.

“Helicopter Zero-Mike-Lima, cleared to land on the numbers of Runway three-zero. You can then taxi down the runway to exit at echo-three and taxi to Mile High.”

I read back the important parts of the instructions, wondering whether echo-three was prominently marked. Helicopter pilots rarely deal with taxiway exits, so we don’t usually study airport diagrams to learn them.

I exited at the right intersection and taxied over to the big ramp on the back side of Mile High Avionics’ hangar. I cooled down and shut down. The blades were still spinning as the big accordion doors opened. A short while later, we had the ground handling wheels on the helicopter and were pushing it into the hangar.

Errands in Prescott

It was 8:45 AM and the avionics guys were ready to get to work on my helicopter. My doctor’s appointment was at 10:00 AM right across runway 30. The only way to get there was to make a five-mile drive around the airport.

The avionics guys very kindly gave me a pickup truck to use while they worked on the helicopter. I headed over to the doctor’s office to see if I could get my medical exam taken care of early. It was a good thing I did. The doctor took ill not long after my exam. As I was leaving with my new medical certificate, an ambulance was arriving to take him away.

I’d like to think that taking my blood pressure and having me read an eye chart didn’t give him a heart attack.

I took the pickup to a hardware store in Chino Valley, where I picked up some weed pre-emergent. I have a gravel “helipad” at our Howard Mesa property and we’ve had some serious problems with tumbleweeds there. I wanted to get the problem under control this year.

Then I went to breakfast at the airport restaurant. Bacon, egg, and cheese on an English muffin. Yum.

I was back at the avionics shop by 10:30 AM. The helicopter was done. I paid up and the avionics guys helped me pull the helicopter back outside.

Next Stop, Howard Mesa

When I started up the helicopter, the mixture problem was just as bad as it had been that morning in Wickenburg. But now it wasn’t cold. There was no excuse for it. I was getting concerned.

PRC to Howard MesaThe tower cleared me to depart to the southwest, parallel to Runway 21, which the planes were using. A plane had just taken off and was climbing out. The controller had me switch to the north tower frequency and that controller instructed me to make my right turn, staying low level to depart to the north. I was at 5300 feet, about two miles north of the airport, when the controller asked what my altitude was. I told him and he replied with “Frequency change approved. Have a good day.”

I thanked him and wished him a good day, thinking that that last exchange had been a little weird.

I listened to an episode of Skeptoid on my iPod as I flew north, over Chino Valley and Paulden. I was heading toward the west side of Bill Williams Mountain and would have to climb to about 7500 feet to get up onto the Colorado Plateau. I was abeam Williams’ Clark Memorial AIrport before I saw it. I was already on frequency and made a courtesy call to the empty airspace.

There was a lot of snow on the ground. I started wondering whether there would be snow on my landing zone. And whether it was wise to spread pre-emergent when I might blow it away when I took off. And whether there was something wrong with my mixture control that would prevent me from starting up when I was ready to leave.

This last thought was weighing heavily on my mind. I didn’t want to get stranded at Howard Mesa. Sure, I could always start up the heat in the shed and wait for Mike to rescue me, but I wasn’t interested in a repeat of my 2004 mesa-top helicopter repair.

I began to slow down and descend when I was still two or three miles out from Howard Mesa. By the time I flew over my place, I was only about 200 feet off the ground. I was surprised to see the windsock hanging almost limp. There were patches of snow on the ground and a series of partially melted animal tracks across the snow-covered driveway. I swung around, made a tight turn to the right, and came in for a final approach from the north. I set down behind the shed, pushed the collective full down, and opened my door to see how my skids were set in the snow and ground. I didn’t want to sink into any muck (again). It looked solid enough.

And then I made a radical decision: I wasn’t going to shut down. Instead, I cooled down the engine and throttled it down to idle RPM. I tightened the cyclic and collective friction. And I stepped out to take care of my chores, leaving the helicopter running.

Now before you other pilots start scolding me, remember this: there was almost no wind and I was on private property in the middle of nowhere with no one around. The cyclic and collective friction on my helicopter do what they’re supposed to; neither control moves when they’re tightened up. The blades had enough spin to keep them from drooping. I was facing where I needed to go, so there was no reason to walk behind the helicopter. There really was no danger. Really.

I offloaded the pre-emergent and brought it into the shed. Then I fetched the two small pieces of furniture I’d come to get. I put one on each of the rear seats, fastening them down with the seatbelts. I climbed back in, double-checked the doors, and fastened my seatbelt. I think I was out of my seat for about four minutes.

I loosened the frictions and spun up. Then I very slowly and carefully lifted the collective, just in case some of that mud was trying to suck me down. The helicopter lifted straight up. I pulled more pitch, pushed the cyclic forward, and took off between two trees.

Mixture Problems Back in Wickenburg

Howard Mesa to E25I flew a direct route back to Wickenburg, detouring only a tiny bit around Granite Mountain. I listened to NPR’s Wait Wait…Don’t Tell Me! podcast.

There were three planes in the pattern when I arrived — all flight training planes doing touch and goes on Runway 5. I came in behind the last one and set down on one of the helipads on the west end. When I shut down, I recorded a total of 2.2 hours of flight time for the day.

I fetched my cart and towbar and brought the helicopter back to the hangar. As I was getting ready to back it in, I noticed that oil had been leaking on my muffler. I got down on the ground and took a closer look. Oil was dripping in the vicinity of the starter motor. A leak somewhere. That could explain why I’d been using more oil than usual later. I decided to see if Ed wanted to look at it.

He came over with me. While he was checking that out, I told him about my mixture control. We backed the helicopter into the hangar and he looked underneath while I pulled the control knob in and out. It made a weird kind of squeaking noise when I pulled it out.

Let me explain how the mixture works. It’s a knob that’s attached to a long cable. The knob is in the cockpit. You pull it toward you to cut fuel; you push it in to add fuel. AIrplane pilots know mixture controls very well, since they often have to “lean” the mixture in flight. Robinson pilots don’t do that. It’s either full mixture while flying or pulled mixture when the engine is shut down.

Ed also had a service bulletin to take care of for me. Since he didn’t have any planes to work on, we figured it would be a good time for him to take care of the SB, lubricate the mixture cable, and see if he could find the oil leak.

I spent some time updating my log book, then drove off to get my hair cut. When I got back, Ed shared some bad news. He’d been working on the mixture and, when he pulled it, the cable broke.

With a broken mixture cable, my helicopter wasn’t going anywhere.

A Lesson Learned

I took the news well. You see, I’d spent a good part of the day before writing an article about how inconvenient some mechanical problems can be. I’d concluded that preventative maintenance could have saved me a lot of bother.

In this instance, I’d identified a potential problem with the mixture control. Even though it still worked, I’d asked my mechanic to take a look at it at the first opportunity. Sure, he’d broken it, but if he hadn’t, I probably would have.

And maybe that break would have been on top of a mesa.

Or when taking charter clients to Sedona or the Grand Canyon.

Any mechanical problem that occurs anywhere other than at home base with a mechanic around is a mechanical problem you want to avoid. Writing that article had reminded me of that simple fact.

And I managed to remember it for a full day.

Anyway, we ordered the cable. It should arrive on Thursday. Ed will fix it then. In the meantime, I hope he tracks down that leak.