Geocaching Revisited

Hunting for hidden treasures.

Back in 2005, I discovered geocaching, an outdoor activity where people use a GPS to find hidden containers of trinkets. I wrote about my thoughts on the topic — and some big plans that never came to fruition — in some detail here. Because part of the game is to pull something out of a cache and replace it with something else, I started gathering items to share. Among these were some “travel bugs,” which are basically serial numbered tags you can affix to an item so it can be tracked. The tracking is mostly done on the Geocaching.com Web site. That’s also were you can find a list of geocaches just about anywhere in the U.S.

And that’s the interesting thing: these things are everywhere. Did you drive more than 10 miles to work today? I bet you passed at least a dozen of them within 3 miles of your car. There’s one a block from my house in Wickenburg and one 4/10 of a mile from my RV here in Quincy. As this map shows, they’re all over the place:

Geocaches Near Me
My RV is just about dead-center in this map. The little box and question mark icons indicate geocaches in the area. The smiley face icon is a geocache I found that I logged.

For some reason, I find the proliferation of these little boxes of hidden “treasure” fascinating. It emphasizes how big the world really is. It also reminds me a bit of a walk my husband, Mike, and I had along the rim of the Grand Canyon once. We got off the beaten path and walked right along the rim, far from where the tourists wander. We happened to stop for a rest on a rock outcropping. And there, tucked under an overhang with a beautiful view of the canyon, was an urn of cremated remains. How long had it been hidden there? We didn’t know. It was like an uncharted geocache. Seems like a good final resting place to me.

Geocaches are hidden. They’re tucked away in painted coffee cans, sealed lengths of black PVC pipe, and plastic Tylenol bottles. In the old days, ammo cans were popular, but I think the value of these has prevented their widespread use — too likely to be stolen if found. (I bought 3 nice-sized ammo cans from a seller in Beatty, NV some years back to create my own geocaches; I still have them.) Caches are hidden in bushes, under rocks, and among the remains of pioneer trash heaps. You’re not likely to stumble upon any of them by accident. You have to look for them. And even with GPS coordinates, they’re not always easy to find.

For some reason, I brought my bag of geocache goodies along with me on my trip to Washington this year. I guess I thought I’d try it again. I didn’t think much of it until the other day when a Twitter friend, @PlagiarismToday, started tweeting about his weekend geocaching activities. It got me thinking about it. I pulled out my bag and took a look inside it. I had a GPS with me, and an Internet connection to get information about local caches, so I had everything I needed to try again.

So I went out yesterday to search for three caches. I found three, but not the original three I’d set out to find.

  • Ryann’s Hide was the first cache I’d hunted for in over 5 years. Although I’m using a newer GPS (a Garmin GPSMap 60c) than I did in 2005, I soon realized that precision was something that needed patience. As I walked, the GPS would guide me, but I quickly overshot the location. Seems that the GPS could not keep up with my movement. I needed to slow down and let the signals catch up. Zooming in on the map gave me ever-increasing detail. Standing still, gave me ever-increasing precision. Once I caught on, I was able to zero in on the location. The cache was alongside a two-track road that led down a hill to a fishing spot. The road was closed to unauthorized vehicles. It started on the edge of an orchard and curved down into a very pleasant wooded area. (I think I need to explore further down that trail.) The container was a painted coffee can with a plastic lid. I pulled out a plastic car and replaced it with a tiny stuffed teddy bear. I entered my Geocaching.com user name in the log book, closed everything back up, and replaced it exactly where I’d found it. Success!
  • Quincy Valley Rest Area II was a bit easier to find — once I got on the correct side of the rest area fence. It was a nicely made cache container consisting of a short length of black PVC pipe with a screw-top on one end. Inside was a baggie with the logbook, some plastic dinosaurs, and a very nice shell. I took the shell and replaced it with an emery board with advertising for a nudist colony on it. (I really don’t remember where I got such a thing, but it is pretty funny — and clean.) I logged my visit and closed it all back up. Success!
  • West Bar Overlook is the one I really wanted to find. It’s located on Babcock Bench, high above one of the orchards I dried several times this summer. The entry on Geocaching.com provided lots of photos and information about the geologic significance of the spot. I’d brought along my camera, planning to get some shots from its perfect vantage point. Unfortunately, the two-track access road that appeared to link the cache area with pavement was inaccessible. Not only was there a locked gate across the road, but there were lots of tall weeds making the start of the trail a bit questionable for someone wearing shorts during snake and tick season. I’ll either try again next spring, before the weeds grow so tall or possibly try to visit via helicopter. I already scouted the power lines in the area. So this was a failure.
  • Rust Everywhere was my consolation prize. I’d already imported its GPS coordinates into my GPS, so I knew approximately where it was. But because I hadn’t planned to look for it, I didn’t have the details — like a basic description of what it looked like. Having a location but no description makes things a bit tougher. Patience and perseverance paid off, though. The cache was a label-less Tylenol bottle hidden well among rocks. I pulled out a kid’s hair clip and replaced it with a computer chip, logged my visit, and put it back. Success!

In all, it was a nice way to spend the afternoon. I was at it for about two hours and it got me out and about. To onlookers, I must have looked pretty silly, walking around while studying a GPS. But I got to find a neat place — that wooded trail — and get some exercise and fresh air. I hope to do more tomorrow.

I also think that it would be a great family or small group activity. A way to combine socialization with exercise. Working together to complete a challenging task.

I do have a geocaching project lined up. I’m going to release one of my travel bugs into the wild with the mission of traveling down to New Orleans, LA. That’s where @PlagiarismToday lives and does his geocaching. He, in turn, is going to send one my way. We’ll see which one completes its mission first.

I’ll likely blog about the progress here.

How to Set Up and Share a SPOT Messenger Page

It’s included in the Track Progress service, so why not?

SPOT Personal TrackerI’ve been using a SPOT Personal Tracker for the past two years. It was recommended to me by a helicopter pilot friend. We both fly in remote areas — the kinds of places that if you go down, rescuers are probably not going to find you before it’s too late.

Think I’m kidding? Check out this Cessna, which was not located for 31 months. I was just one of dozens of local area pilots who looked for this plane whenever I was in the area where it disappeared.

And what pilot can forget the disappearance of Steve Fawcett? Millions of dollars and lots of high-tech search techniques were used to try to find his plane. Over a year passed before a hiker found Fawcett’s ID and the wreckage was eventually found.

I didn’t want to end up like either one of these unfortunate flights. Even if I suffered a fatal crash, I wanted to be found as soon as possible. And if I simply went down and needed help, I wanted help to be able to find me without relying on cell phone signals.

The SPOT Service

So I bought a SPOT Personal Tracker and subscribed to two services:

  • Basic Service enables the SOS (AKA 911), Help, and Check-in/OK features of the unit. That requires a button push to send the message. This service costs $100/year and is required to use the device.
  • Track Progress drops “breadcrumbs” of your location every 10 minutes so others can track you. The track progress feature automatically plots your location signals on a map that’s accessible online. You can create a shared page, give the URL to whoever you want, and let them track you. The benefit of this — as far as I’m concerned as a pilot — is that if I go down suddenly and am incapacitated, people tracking me will not only know where I was within the previous 10 minutes of my mishap, but they’ll likely know which way I was going. Plus, if the unit is intact, it will continue to broadcast my location every 10 minutes. This non-moving signal should help them pinpoint my location — even if I’m dead. This extra service costs $50/year. While I have another pilot friend with a SPOT who doesn’t use it, I think every pilot who uses this device should cough up the extra dough for this service. You can’t always press a button when you need help.

I need to stress here that this is not a device designed for aviation. It’s really designed for “adventure activities” or travel — for hikers and campers and mountain climbers and kayakers. For folks who get out in the wilderness. Of course, pilots who fly in remote areas can benefit from the device and there are plenty of stories of how it may have saved aviator lives. Just keep in mind that it is not an approved FAA tracking device and that flight plans should always be filed and opened for remote area flights. And, if you’re an airplane pilot who flies at altitudes where FSS Flight Following is possible, why not use that service? Unfortunately, Flight Following is not usually available at the altitudes at which I fly my helicopter.

Creating a Shared Page

Of course, having a SPOT Personal Tracker with the Track Progress feature means a Share Page (example shown below) is included with your subscription fee. It makes sense to set up this page and share it’s URL with the folks who need to know where you are. You can also share it with the world at large if you’re like me and don’t care who knows where you are when you’re on the go.

Shared Page
Some recent activity; I did 20-minute helicopter rides the other day.

Setting up a SPOT shared page is easy. Assuming you’ve already set up your account on the SPOT Web site and have activated your device, just follow these steps:

  1. Sign into you account at FindMeSpot.com.
  2. Share TabClick the Share tab near the top of the page.
  3. Under SPOT Shared Pages, click the Create Shared Page link.
  4. Create Page SettingsSet the options in the Create Shared Page window that appears. Be sure to enter a Shared Page Name and select your SPOT device. Under Security, you can specify whether the page is Public or requires a Password to access. Personally, I recommend keeping it Public. You can always limit who you give the URL to. It would be terrible if someone needed to access the information and couldn’t remember the password.
  5. Select one of the options at the bottom of the page to determine how you’ll notify the people you want to share the page with about the page’s URL:
    • If you select Send the shared page myself option (recommended), a message appears, telling you that anyone with the link can view your shared page. Click Create Now to complete the process.
    • If you select Have SPOT send the shared page, a form appears for you to enter up to 50 e-mail addresses and create a custom e-mail message. Be sure to keep the Send a copy to you check box turned on so you get the URL, too. Click Send Now to complete the process.
  6. URL CreatedAt the bottom of the page, a very long URL should appear. Triple-click it to select it and chose Edit > Copy (or press Command-C (Mac) or Control-C (Win)) to copy it to the clipboard. We’ll use it in a moment to test the link and create a short URL.

Shared PagesIf, for some reason, you didn’t get the URL or you need to access it again in the future, click the Shared tab (shown above) and then click the Manage Shared Pages link under SPOT Shared pages. You can click the name of the shared page to display it. You can then copy the link for that page from the Web browser’s address bar.

Creating a Short URL

http://share.findmespot.com/shared/faces/viewspots.jsp?glId=0aISLWHRq9KlETLqzcfFGQuD8VboS6R8O is not exactly the kind of URL that’s easy to share with friends. Fortunately, URL shortening services enable you to create a custom URL for any page. Although this step isn’t required, it’s certainly recommended.

Although I originally created my short URL with the TinyURL service, you can use any service you like. Bit.ly makes even shorter URLs, but it requires an account to create a customized one. So in this example, I’ll use TinyURL again.

  1. Point your browser to TinyURL.com.
  2. TinyURLPaste the URL for your shared page in the top text box.
  3. Enter a short word or phrase that’s easy to remember in the bottom text box. In this example, I’ve entered the N-number for my helicopter. My original URL used FindMaria.
  4. New TinyURLClick Make TinyURL!
    A message like the one shown here appears, confirming that the new URL was created. You can now give this much shorter URL to family and friends.

Share Your SPOT Page!

Are you already using a SPOT device? If you’ve got a page set up, share it here. Use the Comments link or form for this post. No need to enter any HTML tags; just enter the complete URL. Once your comment has been approved, your shared page will appear. I’d also love to hear comments about the device — good or bad.

The Big Detour

Or why a one-hour helicopter flight took four hours.

Seattle weather sucks. I can’t say it any other way.

I arrived there last Thursday and experienced rain every single day while I was there. A helicopter flight to Bremerton for breakfast was switched to a much closer destination simply because low clouds made it impossible to get to Bremerton. In a helicopter, for pete’s sake.

By Sunday, I’d had enough. I hooked up the RV and crossed the Cascade mountains to the east side. The Columbia River Valley is [usually] much drier. I set up camp in my usual spot at Colockum Ridge Golf Course and opened all the RV windows to let some fresh, warm, dry air in.

The Mission: Get My Helicopter to the East Side of the Cascades

Of course, my helicopter was still in Seattle. As it ages, parts are starting to fail. This year, it was (so far) the auxiliary fuel pump (again), the muffler (cracked), the upper bearing (worn out), and the engine support do-dad (drooping). Add to that the cost of overhauling the magnetos and I was looking at about $10K of repairs. In the past two months.

So don’t anyone ask me why it costs so much to fly a helicopter.

The repairs were finished on Tuesday afternoon. Although weather was still an issue in Seattle, I needed the helicopter on the east side. My contracts don’t start until June 10 or so — pushed back because of unseasonably cold weather — but there was a slight chance I might be able to pick up a week’s worth of work farther south if the helicopter was available.

So on Wednesday morning, I boarded a Horizon Airlines flight in Wenatchee (EAT) for Seattle (SEA). My friend Don, who’d graciously hosted me and my RV the previous week, picked me up at the airport, let me buy him lunch, and dropped me off at Seattle’s Boeing Field (BFI). After chatting in the office for a while and checking the usual dismal weather, I met with the mechanic, gave the repairs a quick look, preflighted, and took off.

First Attempt

It was about 1 PM and the clouds were low. In the hilly terrain along the I-90 corridor, I managed to keep my altitude at 300-500 feet above the ground with the cloud bottoms a comfortable distance above me.

First Try

The view shortly before I decided to turn back. Unfortunately, my point-and-shoot Nikon insists on focusing on raindrops.

But I didn’t get very far. As I moved eastward over I-90, visibility started to deteriorate. I wasn’t much past Renton’s airspace when I saw a thick rain shower ahead of me over the Interstate. I’d been taught at the Grand Canyon that if you can see through it you can fly through it. I couldn’t see through this one. And I wasn’t anywhere near the pass I’d have to slip through to get over the Cascades. Obviously, this wasn’t the way to go.

I doubled back, calling in to Renton’s tower to get permission to transition along the east side of their airspace. I figured I’d head south — possibly as far at the Columbia River — and go around the mountains. That would turn a 45-minute flight into a 2-1/2 hour flight (at least). But as I traveled south, I could see that the visibility situation was worse than the weather radar indicated. I got past Auburn and knew I couldn’t complete the flight at that time.

I had two choices:

  • I could return to BFI and hang around in the mechanic’s office and wait until the weather got better. I had no transportation there, so I’d be stuck there. If I got stuck there all day, they’d eventually kick me out and I’d have to either fly out or get a cab to a motel and return the next day for departure.
  • Don's Heliport

    Don’s Heliport, photographed with his helicopter on the “pad” on a nicer day.

    I could fly to my friend Don’s private helipad in Auburn. He’d already told me I could do that if I needed to. There I’d find a comfortable place to hang out with friends and both a television and wifi to check the weather. I’d also be able to draw on Don’s weather local experience to determine the best time to make another attempt. If an overnight stay was required, they had a nice guest room.

Which would you pick?

The trouble was, Don’s heliport — although logged into the FAA airport database — was not on my GPS. I’d only flown in once with him — as a passenger. I knew some of the landmarks. But I also knew that it was completely surrounded by tall trees and impossible to see until you were literally right on top of it. So I had to go hunting. In the rain. I figured I had about a 50% chance of success.

I did eventually find it. It took about 10 minutes. On the ground, Don heard me and quickly pulled his truck and trailer out of the landing pad. He’d just gotten it out of the way when I spotted it. I circled around to make the steep approach. I came in a bit too slow and steep, but I made it work. Not bad for the first landing.

We checked the weather together and decided I should wait a few hours. I accompanied them on a few errands. It was raining the whole time. We got back and checked the weather again. Radar showed a huge storm system moving northwest from the other side of the Cascades. My buddy, Jim, who had started a cherry drying contract in Mattawa, would probably be flying. We looked at the Washington State Department of Transportation Web site traffic Web cams in the passes. We checked Duats and got information for Stampede Pass, which was not far from the pass on I-90 that I’d be crossing. Conditions changed by the minute.

Second Attempt

Finally, at 6 PM, I decided to try again. I said my goodbyes, started up the helicopter, and climbed up through the trees. The scene from up there was surreal. Wispy patches of thin clouds rose here and there from the tops of the tall pines. To the west and south, the sun had broken through the low clouds, illuminating the ground with rays of light. To the north, I could clearly see the Seattle skyline. To the east, however, things weren’t as rosy. There were scattered rain showers and patches of fog.

My initial plan had been to follow Route 18 to I-90, but Route 18 led right into a thick rain shower. So I punched Bandera (4W0) into my GPS and took a route that was southwest of 18, heading east northeast. I hit I-90 just before it made a sharp turn into a canyon. The clouds were very low there and I’d have to fly about 200 feet over the freeway to enter the gap. While there was a chance that the ceilings could rise right beyond that point, it was impossible to tell from my position a mile or so away. And I was still 7 miles from Bandera, which was still several miles from the pass. The likelihood of getting through there without hitting wires was slim to none.

Afternoon Clouds

Another crappy photo, but it should give you an idea of those wispy clouds coming up through the trees.

I turned around and retraced my route to Don’s place. To the south, there was a lot of bright sunlight. I was pretty sure I could go that way and follow the Columbia River around the mountains. But the flight would take 2-1/2 hours and I’d have to stop for fuel. Sunset was at 8:45 PM. It was already 6:30 — too late to make the attempt.

Of course, I’d forgotten to mark Don’s place as a waypoint on my GPS, so I had to hunt for it again. I found it a bit quicker and made a much better approach and landing. I was there for the night.

I’d been gone 30 minutes.

First Two Attempts

My first two attempts on a Seattle sectional chart. Red is my first try, blue is my second.

Third Attempt

I woke to fog. We checked the weather on the Internet and on television. We also called another pilot who lived nearby and had a better view of the sky to get her input. By then, I was so sick of checking the weather that it ceased to have meaning for me. After all, few of our sources gave me the information I really needed: how high were the could bottoms above the ground? What was the visibility in the mountain passes? A direct flight to Quincy from Auburn was less than 100 nautical miles. Although I couldn’t make a direct flight, my goal was to make it as direct as possible.

You need to understand here that this isn’t the first time I’ve had to take the helicopter across the Cascades. It was going to be my seventh. Weather had been an issue on four of those previous flights, but never this bad. I just wasn’t willing to accept it.

So when the fog cleared and our contact a few miles away reported ceilings of about 500 feet, I decided to try again. Don topped off my fuel tanks with another 15 gallons of fuel. I said goodbye again, started up, and climbed back up through the trees.

Nice Weather

This is the nicest bit of weather I came across. This shot was taken about 15 miles south of Auburn at 9:18 AM.

Up top, I was surrounded by poor visibility. I could probably see 3 miles, but not much more. I was certain that I’d be wasting my time if I tried for the I-90 passes again. So I headed south toward Portland, OR. As I flew, the weather improved.

As I flew, I never lost hope of getting across the mountains another way. Although my general direction was south, I kept trying to find passages that would take me more to the east. I followed one particular valley for quite a while, climbing ever so slightly along the way. Then my way was blocked by clouds touching the tops of the tall pines all around me. Discouraged, I turned around to backtrack out of the valley.

View from Above the Clouds

View from above the clouds. I was probably heading westbound when I took this shot after aborting my first canyon passage. 9:30 AM

A big hole in the clouds opened up, revealing blue sky. I pulled pitch, pulled the cyclic back, and climbed out at about 1200 feet per minute. Above the low clouds, the view was disheartening. The cloud tops varied in height and another layer of clouds seemed to meet them on the horizon to the east. The bright, snow-covered top of Mount Rainier seemed to taunt me, shining in the sun less than 30 miles away. On a previous westbound flight, I’d flown above the clouds just north of the peak, dropping down into a valley on the west side to complete my flight. It didn’t look as if I’d be as lucky to find a path back through the clouds on the east side that day so I wasn’t about to attempt it.

I caught sight of a lake to the west of my position through another big hole in the clouds. I dumped the collective and glided down at 1700 feet per minute, banking right and then left to dodge clouds on my way down. Safely under the clouds again, I continued south.

Eventually, I hooked up with Route 12, another of the roads that crosses the Cascades. I followed it eastbound in a pleasant valley dotted with homes, farms, and lumber mills. The clouds overhead were low but mostly broken, so there was plenty of sunshine — enough to turn off the heat and crack the air vent. I tracked my position on the sectional chart. White Pass was at 4500 feet. If I could get through that, I’d be able to follow the road to Yakima.

I passed the last town in the valley and the road began climbing into the mountains. I climbed with it. Then I decided to take a chance above the clouds again. I climbed up through a big hole, reaching 6,000 feet before coming out on top of the lowest layer. The clouds were taller here, some of them starting to show signs of convective activity. Although I was atop many of them, I had to fly around others. My GPS assured me that the road was beneath me, but I couldn’t see it. I also couldn’t see Mount Adams, which I knew was very nearby. The clouds were thick to the east. I knew that to an onlooker, I probably looked like a tiny speck of red among the giant puffy clouds and rocky peaks around me.

And that’s when I scared myself. I flew into a sort of box canyon of clouds. The only way out was back the way I’d come and down. I dumped collective and pulled the cyclic over. Within a moment, I was banking hard to the right at at least a 60° bank angle, descending at 1000 feet per minute. Adrenaline rushed into my system, making my entire body feel the dire emergency situation I was in. In less than 15 seconds, I was clear of all danger, but it would be at least 30 minutes before that adrenaline rush was completely gone.

I won’t do that again.

I flew back to that nice little town with the initial thought of landing there at its airport and waiting for the weather to improve. But I realized what an idiotic idea that was. The weather there would not improve soon enough and the town was too small to have a motel or even fuel at its airport. So I continued on my way, backtracking along Route 12, westbound through the valley.

At Randle, there was a road that cut south through the mountains. It looked like it might be a shortcut to the Columbia River Gorge east of Portland. I still had half tanks of fuel so I figured I’d give it a try. Soon I was flying through a spectacularly beautiful little valley, over a rushing river. Every once in a while, I’d catch sight of the paved road between the tall pine trees. The road climbed and I climbed with it.

Then the inevitable — a wall of clouds right behind a ridge. I circled, looking for the road, wondering which way it went. The neat thing about mountain roads is that they’re usually built on the easiest path to cross mountains. That’s what makes them so good as navigation tools when you need to fly a helicopter over some mountains.

When I spotted the road, I was surprised to see that it was covered with deep snow. It was obviously closed for the winter. I followed it slowly to the top of the ridge to take a peek over. If the land dropped down behind it and the clouds stayed high, I could continue. But if there was another ridge blocked by clouds behind this one, I’d have to go back. Again.

I was lucky. The ridge was the highest point on the road. The land fell away beyond it and the road fell with it. I popped over the top only 50 feet from the treetops and descended into a valley on the other side.

I punched Hood River into my GPS. I’d need fuel somewhere and Hood River seemed as good a place as any to get some. It was still 40 miles out. I flew directly toward it, put off by the amount of cloud cover all around me. I’d been hoping for clear skies in the Columbia River area but I wasn’t going to get them.

Mount St. Helens

A crappy, over-the-shoulder shot of Mount St. Helens. (You try taking decent photos while flying a helicopter.)

At one point, I saw Mount St. Helens over my right shoulder. It was covered with fresh snow.

Eventually, I changed my fueling destination to The Dalles. I hit the Columbia River abeam Hood River and followed the Columbia eastbound. I landed at The Dalles, called Don to assure him I was okay, and went inside to use the bathroom while the FBO guy fueled my helicopter.

I thought the worst of it was over. I even said that to the FBO guy before starting up again. But although the worst of it was over, there was still weather ahead. Unfortunately, I hadn’t taken the time to check the weather again while at The Dalles. So the low clouds and heavy rainstorms I had to fly through for the next hour or so were an unpleasant surprise.

Spot Messenger Track

As this SPOT Messenger track shows, my route from Seattle to Matawa was anything but direct.

It was cloudy but not raining when I landed in Mattawa to visit with my friend Jim. He and his wife drove me to a local restaurant where I could get something to eat and drink. We wound up spending at least 2-1/2 hours there, talking about flying and drying cherries and politics. As I was getting ready to leave, it started drizzling. Jim, who’d flown 2-1/2 hours the day before, smiled and thanked the rain gods. If the rain kept up, he’d fly again later in the day.

From Mattawa, it was only 20 minutes back to my base in Quincy. I overflew what looked like an AStar drying cherries on the north side of Mattawa. (Why he was drying while it was raining was beyond me.) In Quincy, I landed on a concrete pad at the ag strip across from the golf course where I’m camped out. The clouds were thickening in the area. I hitched a ride to the campground, got my truck, and put the padded blade covers on the helicopter.

It was good to get back to my comfy RV and Alex the Bird. I slept very well that night.

Wickenburg to Seattle by Helicopter: Day 3 AM

Bryce Canyon to Salt Lake City, UT.

I woke to a beautiful day at Bryce Canyon. Of course, I didn’t know it at the time. It was still dark. The weather forecast had called for overcast, so when I looked out into the predawn sky and saw only grayness, I assumed the area was clouded over. But as the day brightened, I realized that it had been just a thin cloud that hid the stars from view. It cleared out to reveal a blue sky.

I grabbed my camera and walked from my cabin to the rim trail. A bunch of folks were there in bunches at viewpoints. Shivering against the cold, I joined a pair of Canadians with the same idea I had: shooting the rock formations in the early morning light. I spent the next hour walking the rim, photographing the view. I’ll share some of those photos in another blog post.

Knowing from the previous day’s experience that I wasn’t likely to get a good meal at the lodge’s restaurant, I went back to my cabin, packed up, and checked out. A while later, I was leaving the park and pulling into the parking lot at Ruby’s Inn.

Ruby’s is a tourist trap. I can’t say it any other way. Every little town outside a National Park is full of them. Ruby’s, like so many of the good ones, has it down to a science. Buffet breakfast designed to satisfy the Americans and awe the Europeans and Asians. Clean comfortable seating. Huge gift shop. WiFi. I settled down in a booth, got tired of waiting for a server, and just served myself from the buffet. The price was far above average so, in true American fashion, I ate a lot more than I should have to get my money’s worth. Sometimes, I’m a real idiot.

After topping off the rental car’s fuel tank, I drove to the airport. By that time, the morning was truly beautiful, with clear skies and light winds. To the north, I could see a hint of some clouds. The weather in Salt Lake City — which I’d checked while at Ruby’s on my iPad — was overcast with showers. I wondered how long I’d be flying before I reached the southern edge of the weather.

I settled my bill with the FBO, left them the car keys, and went out to the helicopter. After a preflight that included checking for ice on the blades (some frost, but it was melting fast in the sun), I climbed aboard and started up. It took a good ten minutes to warm the engine. Then I was lifting off, heading northwest toward Panguitch.

I’d planned this leg of the flight days before and had repeatedly wondered whether It was a good route. Sometimes I do that. I decide on one thing and repeatedly have second thoughts about my decision. Is that a woman thing? I don’t know. But this time, I stuck with it.

Near Bryce Canyon

An example of one of the red rock canyons northwest of Bryce, as seen from the air.

The landscape was immediately amazing. I was coming off the plateau on which Bryce “Canyon” sits. Bryce is not really a canyon at all. It’s more like a mesa with incredible red rock formations around much of its exposed sides. Coming down off the northwest side, I passed over and near dozens of red rock canyons, many of them deep and narrow slot canyons. It would have been interesting to explore, but I was on a schedule and didn’t have time. So I continued on.

I descended at least a thousand feet off the plateau into the valley in which Panguitch and its small airport (U55) sits. The town looked tiny from my perspective. I didn’t overfly it. Instead, I turned north to join up with Highway 89. I’d follow that at least halfway to Salt Lake City.

North of Panguitch

Canyon between Panguitch and Circleville, UT over Highway 89.

The flight took me along the Sevier River, through a narrow canyon and into a wider valley beyond. The towns along here were few and far between: Circleville, Junction, Marysvale. At Marysvale, my chart advised me that there was a Letter M visible from the sky. Sure enough, it was there, bigger than life. I wondered about the pilots who used such landmarks as navigation tools. I also thought it might be cool to display the chart and photo of this landmark side by side in a blog post, so I snapped a photo. (Sorry about the glare. And yes, I really did think about this while I was flying.)

Marysvale on the Chart Letter M

Colorful Canyon Wall

How does this happen?

I went through another canyon. This one had some great color on one rock wall. Really pretty. I’m not sure how color like this happens, but I’m willing to bet that a geologist would really enjoy flying low-level in a helicopter through an area like this. The earth’s geology is laid bare for all to see.

I should mention here that the whole time I was flying, I was in a valley between mountains 10,000 feet and taller. There was plenty of snow atop those mountains. And the clouds were beginning to gather not far above them, thickening with every mile north that I traveled. They were friendly, white, puffy clouds, the kind that get nasty on summer days when convective activity builds them taller and taller.

Reflections in a Lake

Reflections in a glassy calm lake.

I flew by a number of small lakes. The wind was perfectly calm down there — it was easy to see from the quality of the reflections of the mountains and sky. I got a few shots through the bubble. This is the best of the bunch.

Not long afterward, the weather closed in. The clouds thickened and blotted out the sun and sky. They also started to drop, getting ever closer to where I was flying. By the time I got to Provo (KPVU), it was raining and I was flying only a few hundred feet below the clouds. I called the Provo tower and asked to transition along I-15. The controller cleared me for the transition and the radio settled back into unbroken silence until I reported I was clear to the north.

See what I mean about low clouds in this video.

I shot a video in this area using my Flip video camera. It’s crappy — hell, it isn’t easy to take any photos while flying a helicopter so cut me some slack here. It does give you a pretty good idea of what the weather was like. The video sweeps from left to right across the cockpit, ending at my right shoulder. The weather improved somewhat as I closed in on Salt Lake City airport.

I called into Salt Lake City when I was about 11 miles out. The controller told me to call Salt Lake City approach. So I switched frequencies and repeated my call. I was told to proceed along I-15. Three minutes later, they told me to contact the tower on yet another frequency. I dialed in and wound up speaking with the original controller. “Welcome back,” she said.

Salt Lake City Airport DiagramI told her I was unfamiliar but had a good airport diagram. I told her I was going to the Million Air FBO and had a pretty good idea of where it was. She cleared me to land when I was still a few miles out.

Salt Lake City is like two airports in one. There are two big runways for commercial airliners on the west side. And then there are two smaller runways for general aviation on the east side. My destination on the airport was on the southeast corner. I came in right of the taxiway parallel to runway 35. I weaved my way around some parked planes and came in for a landing on the ramp. A line guy came out and guided me to a spot 10 feet away from where I’d touched down. Whatever.

I’d been in the air for a full hour.

I shut down as the pilot I was meeting at Salt Lake stepped out of the FBO into the rain. A while later, we’d be starting a long flight to Seattle together.

But that’s another story.

What It’s Like to Tow a 15,000-lb Fifth Wheel Trailer 1,500 miles

Or why I’ll never be a long-haul trucker.

I’m writing this from the relative comfort of the desk in my RV. I just completed a 3-1/2 day drive from Arizona to Washington State and am parked alongside a very large garage adjacent to a private heliport at a friend’s house in Auburn.

I’m resting.

The drive was a lot more difficult than I imagined. Difficult enough for me to blog about it. In detail.

No, I’m not going to give you turn-by-turn driving instructions and list the sights I saw along the way. No one really wants to read stuff like that. If you’re at all interested, you can read about the first two days of the drive here. I wrote that two days ago when I was still relatively fresh.

Instead, I’ll tell you why I’m exhausted and why I’m glad I don’t have to drive again tomorrow.

Towing: the Basics

My RV is a 36-foot long Montana Mountaineer fifth wheel. Because our 2001 Chevy Silverado 3/4 ton pickup already had a gooseneck hitch receptor on it, I converted the RV’s hitch to a gooseneck. Well, I didn’t do it. The folks I bought the RV from did it. It makes it a bit tricky to hook up — still not sure how I’m going to line it up when I need to hitch it alone — but it does keep the pickup’s bed free of a bunch of extra hardware.

The trailer is 15,000 pounds max gross weight. I didn’t weigh it before this trip — I wanted to, but didn’t get around to it. (There’s a scale at the local dump in Wickenburg, so it wouldn’t have been so tough. Weigh the truck alone, then weigh the truck with the trailer and do the math.) I don’t think it’s fully loaded, but I bet it still close enough to 15,000 pounds to make the weight debate moot.

The truck can pull the weight. Its manual says it can and it can. I push a button on the gear shift lever to turn on the towing package feature and the Duramax diesel and Allison transmission do the rest. It stays in a lower gear so I can get it up to highway speed and then shifts back down into a lower gear when I brake for engine braking.

It takes a while for the truck to get up to highway speed. Normally, the truck is remarkably peppy for a diesel. That’s one of the things I like about it. But add 15,000 pounds and it’s working hard. 0 to 60 takes about 30 seconds. If I’m on flat road. Add an uphill climb and I might not even get it up to 60.

Add a downhill coast and I’ll have trouble keeping it below 60. And that’s the problem.

The Trick is to Avoid Using the Brakes

Imagine a freight train barreling along at 50 miles an hour. Now imagine some idiot stalled at a crossing on the tracks. He’d better get his ass out of the car and hope his insurance is up-to-date.

I once spoke to a train engineer for Conrail in New Jersey. He told me that if there’s something on the tracks, they don’t even bother trying to stop. Why? Because they won’t be able to stop in time anyway. It could take over a mile for a freight train moving at cruising speed to come to a complete stop. Why? Because of the inertia of all that weight moving at cruise speed.

As I gained experience at the helm of my own personal freight train, I quickly learned that my main goal should be to drive in such a way that I minimized the use of the brakes. There are three reasons for this:

  • It takes a long time to stop — or even to slow down. The less often you need to stop or slow down, the better off you are.
  • Using the brakes wastes fuel. Look at it this way: you pump a lot of fuel through the engine at high RPMs in a lower gear to get the damn thing moving. If you hit the brakes, not only are you throwing away all the stored energy in your weight and speed, but the engine is going to downshift again and use more fuel at high RPMs to slow you back down. May as well punch a hole in the fuel tank and let it drain out.
  • Using the brakes wears down the brakes and works the engine. You have to press harder on the brakes to get a reaction out of them. That means you’re wearing them down more. And with engine braking, the poor engine is working hard even when you’re slowing down. Is that fair?

It’s the Stress that Exhausted Me

The difficulty in slowing down or stopping is where all the stress comes in.

The entire time I was driving, I was on alert. I needed to know that I had to stop or slow down before I had to stop or slow down. So I looked at every other vehicle around me — as well as traffic lights and stop signs when I wasn’t on the freeway — with a critical eye. Is that guy in front of me going to hit his brakes? Is the idiot next to him going to cut me off? Is that traffic light up ahead going to turn yellow before I get to it? Is that school bus up ahead going to stop?

Even when I was on straight, flat freeway with no other vehicles around me, I couldn’t relax. At one point, a dog ran into the freeway in front of me. A dog! Like that freight train engineer, I knew I wouldn’t be able to stop in time. If he didn’t get out of the road, I’d run right over him, just like a freight train. There’s no way I’d try to swerve at 60 MPH with all that weight behind me. I leaned on the truck’s horn. Fortunately for the dog, he ran back where he came from without becoming my victim.

So all day long, hour after hour, I was tensed up, fully alert and ready to react before I needed to. It exhausted me.

Now Add Some Mountains

The route I chose was mountainous. In Death Valley, I was 230 feet below sea level. Near Mammoth Lakes, CA, I was at over 8,000 feet above sea level. For three days, it seemed like all I did was climb up and down mountains.

Up wasn’t a big deal. Press the pedal and burn fuel in second or third gear, trying to maintain a decent speed so as not to annoy the people behind me. It didn’t matter if there was a curve up ahead — I probably wasn’t going fast enough to make negotiating it a problem.

But down…well, that’s another story entirely. The Chevy has never been a good coaster — my 1994 Ford F150 is far better at that — but add 15,000 pounds and gravity can turn anything into a coaster. I had to use the brakes going downhill just to prevent the speed from climbing higher than I could handle. The transmission did its part, of course, but that wasn’t enough on the 9% grade (not a typo) coming down into the Panamint Valley in Death Valley National Park. In second gear, with the engine red-lining, I was still pumping the brakes to keep the speed below 50 miles per hour as I negotiated curves on a two-lane road that hugged the side of a cliff.

You want to talk stress? I can’t imagine anything more stressful than that.

Add Rain

Actually, I can: wet pavement on those curvy downhill stretches.

The rain started on Day 3 and haunted me for the whole day. That’s the day I descended from the mountains in Northern California into southern Oregon. There was this one stretch just south of Ashland on I-5…a lengthy downhill ride hugging the side of a mountain with curves marked for 50 mph. Bad enough dry, but nightmarish when wet and surrounded by tractor-trailer trucks. Who the hell designs highways like that?

I’m an Arizonan. I don’t drive in rain because it doesn’t rain. When it does rain, the roads are slick because of oil accumulation. It’s terrifying. How slick were these roads? I didn’t know and I didn’t want to find out. I just struggled to keep my speed down, imagining the horrific crash if the trailer decided to slide a different direction than the truck was going.

Overreacting? Perhaps.

Reading this, you probably think I’m a sissy. But I have a lot of miles under my belt — I’ve driven clear across the country more times than I can count and have made 3-1/2 round trips from Arizona to Washington since 2005. I’ve driven everything from motorcycles to this rig, including hundreds of different rental cars.

But driving this rig was unlike anything else I’d ever driven. It wasn’t like my Ducati, which I could whip around curves by tossing my weight around. It wasn’t like my Honda S2000, which red-lines at 9,000 RPM and has just the tiniest bit of body roll in curves. It wasn’t even like the Chevy without its load, able to accelerate or stop quicker than you’d think a truck should.

Just the knowledge that slowing down or stopping was going to be so tough had me on edge the entire time.

And that’s what kept me safe.

But when it’s time to return to Arizona, I know one thing for sure: I’ll be planning the route with the straightest, flattest roads I can find.

Congratulations! You’ve made it to the end of yet another lengthy blog post here on An Eclectic Mind. If you got this far, you must have gotten something out of what you read. And isn’t it nice to read Web content that isn’t full of annoying ads?

How about doing something to show your appreciation? I’d love it if you’d add a comment at the end of this post to share your feedback with me and others. But I’d really love it if you’d visit my Support page and chip in a few dollars to help cover the cost of hosting this blog and motivate me to keep writing new, interesting content. It’ll only take a moment and I really would appreciate it!