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!

 

Why I Wear a Flight Suit to Dry Cherries

Just a precaution.

In a comment to yesterday’s post about my work drying cherries, Miraz asked:

Could you write a post about your Nomex flight suit. What is it? What’s special about it? Why don’t you just wear whatever you normally wear when flying?

A good topic for a post, so here it is.

First, Nomex. Wikipedia describes Nomex as follows:

Nomex (styled NOMEX) is a registered trademark for flame resistant meta-aramid material developed in the early 1960s by DuPont and first marketed in 1967.

It can be considered an aromatic nylon, the meta variant of the para-aramid Kevlar. It is sold in both fiber and sheet forms and is used as a fabric wherever resistance from heat and flame is required […] Both the firefighting and vehicle racing industries use Nomex to create clothing and equipment that can withstand intense heat. All aramids are heat and flame resistant but Kevlar, having a para orientation, can be molecularly aligned and gives high strength….

The Wikipedia piece goes on to list the different uses of Nomex fabric, including this statement:

Military pilots and aircrew wear flight suits made of over 92 percent Nomex to protect them from the possibility of cockpit fires and other mishaps.

A Pickle Suit

Here’s an example of a flight suit available on Flightsuits.com. (And no, it doesn’t come with the guy.)

It’s not just military pilots. Nomex is also widely used in flight suits worn by EMS pilots and crew members and law enforcement pilots.

A flight suit is usually a one-piece, zip up garment, often with many pockets, that is worn by pilots and aircraft crew members. While they come in many colors and styles, they’re usually a military green or khaki color. The green suits (see photo) are sometimes referred to by the folks who wear them as “pickle suits.”

Flight suits can be made of any fabric, but since they’re available in Nomex, it seems silly to wear one that doesn’t offer the additional protection of the Nomex fabric. And although they come in long sleeve and short sleeve styles, it also seems silly to have Nomex protection on only half of your arms when you can get full arm coverage.

At least that’s the way I see it.

Why does a pilot need protection at all? Well, it’s mostly to save your life (or even just your skin) in the event of a post-crash fire. And fires are definitely possible when you’re carrying fuel (which you should be) if you hit the ground hard in a crash.

Safety Notice 40Robinson Helicopter Company recommends that all pilots — and even passengers! — wear flight suits. Safety Notice 40 was released in July 2006, possibly in response to an accident with a post-crash fire in Texas. Robinson often releases Safety Notices in response to what it sees as dangerous or potentially dangerous situations. Safety Notices are not requirements; they’re suggestions. They’re also Robinson’s way of “covering its butt.” The company is owned by Frank Robinson and is self-insured. By recommending that we wear flight suits, Robinson Helicopter cannot be held accountable for burn injuries if we’re not following their recommendation.

That’s not to say it isn’t good advice. It is. But it isn’t exactly practical to require every person on board a flight to wear a flight suit. And while I might be tempted to wear a flight suit more often if I actually looked good in one, I don’t. Besides, I’ve decided on a more professional “corporate pilot” appearance for my charter flights: slacks with a polo shirt or pilot shirt.

It’s a matter of risk assessment. Tour and charter flying has much lower risk associated with it. I’m usually operating at airports, landing and departing from locations very suitable for that kind of activity. Flight profiles remain outside the “deadman’s curve.” There isn’t anything unusually risky about these flights. Even most of my photo and survey flights are relatively low-risk.

But hovering 5-10 feet over cherry trees at 5-10 knots ground speed puts me firmly into the deadman’s curve. If I have an engine failure, there’s nothing I can do to prevent a messy crash into the trees. With lots of fuel on board, a post-crash fire is possible. Wearing a Nomex flight suit seems like a pretty good idea.

Helicopter Helmet

A helicopter helmet like the one I wear. This is a low-cost model available from AviationHelmets.com.

So does wearing a helmet. I can’t tell you how many articles I’ve read in helicopter flying magazines about the importance of wearing a helmet on high-risk missions. The main thing that worries me is the flinging parts that might just enter the cockpit in the event of a crash. It would be awful to have a soft landing only to have a main rotor blade enter the cockpit and split your head open like a coconut. (Ick. What a terrible visual.) Or even to just clock your head on the door frame hard enough to cause serious damage. The helmet protects me against this.

But I don’t think my passengers would feel very comfortable if I wore it on a charter flight.

So, in answer to Miraz’s question, I wear a flight suit for cherry drying because of the increased risks associated with that kind of flying. I don’t wear it for other, less risky missions because I’m trying to maintain a “corporate pilot” professional look for my passengers. And I look like a big khaki sausage in my flight suit.

Fortunately, the cherry trees — and growers — don’t care what I look like.

The Deadman’s Curve

Why helicopter pilots balk when asked to hover at 50 feet.

Last year, I joined a listserve group of professional aerial photographers. These folks, who are based all over the world, have been working at their profession for years. I’m a relative newcomer to the aerial photography scene and arrive as a pilot — not a photographer. (I want to take photos, but it’s tough when my right hand is stuck holding the cyclic during flight.)

I introduced myself and an engaging conversation about flying helicopters ensued. As you can imagine, many of the photographers had worked with helicopters. One of them was even on board during a crash!

One of the photographers in the group told a story about photo flights he’d taken with helicopter flight school instructors. He included this comment:

I was shooting a lot of sailboat races at the time, so where I wanted it turned out to be in a hover at 20 to 50 feet above the water which made some of the instructors nervous. I told them to get over it.

A lot of pilots won’t work in what’s commonly referred to by helicopter pilots as the “deadman’s curve.” All helicopter pilots should know what this is, but here’s a brief explanation for those of you who aren’t familiar with helicopter flight.

The “Deadman’s Curve”

Height-Velocity Diagram for R44 HelicopterThe Height-Velocity diagram in the pilot operating handbook (POH) shows the combinations of airspeed and altitude at which an experienced pilot (or test pilot) should be able to make a safe autorotation in the event of an engine failure.

The diagram shown here is for a Robinson R44 helicopter, but they’re all very similar. The idea is to stay out of the shaded area. Generally speaking, you want either altitude or airspeed — or (preferably) both. Hovering at 20 to 50 feet puts you in the “deadman’s curve” — it’s a combination or airspeed (0 knots) and altitude (20 to 50 feet) at which a safe autorotation is not possible. So if the engine quits, you’re dead.

The height velocity diagram also clearly shows the recommended take-off profile. When a pilot does a “by the book” take-off, this is what he’s doing: picking up into a hover less than 10 feet off the ground and accelerating through 45 knots. Then pitch up slightly and climb out at 60 knots. (You can get an idea of this in my “Shadow Takeoff” video.) Doing a “straight up” take-off like you see in the movies or on television puts the helicopter smack dab in the middle of the deadman’s curve until he’s moving faster than 50 knots or has climbed several hundred feet.

Wondering how the chart is created? With test pilots and helicopters. If you take the Robinson Factory Safety Course, you’ll see videos of the flights they used to build the chart — including one flight that demonstrated what happens when you attempt an autorotation while inside the deadman’s curve.

My Experience with the Deadman’s Curve

I get some photo gigs because I’m willing to operate in certain areas of the deadman’s curve to meet my client’s needs. I’m a single pilot operator so I’m responsible for myself. Other organizations are responsible for their pilots and tell their pilots not to do anything that could be “unsafe.” This is often the situation at flight schools that do photo flights for extra revenue. Those pilots are usually the school’s CFIs, sometimes with only a few hundred hours of flight time. The school makes a rule — no operations under 300 feet — and all the pilots are required to comply.

Operating in the deadman’s curve requires that you have a lot of confidence in your engine and mechanic. The engine failure statistics on Robinson helicopters show that the engine — a Lycoming, after all — is very reliable. And I take meticulous care of my aircraft with two experienced mechanics to do the work. I’m confident in my aircraft. So I take the risk and I get the job.

But I do warn my passengers of the risks inherent in that type of flying. And If a maneuver puts me too close to obstacles or requires me to do something I think is beyond my skill level, I won’t do it. (I don’t have a death wish.)

Get Over It?

“Get over it,” is a pretty funny thing to say to a pilot when requesting (or demanding) that he perform a maneuver he’s not comfortable with or authorized to do.

The pilot who balked at hovering 50 feet off the ground was doing it for safety — his and his client’s. The photographer who told him to “get over it” was unfair to expect the pilot to operate where he was not comfortable. At the same time, the pilot should have clearly stated the limitations of the flight before accepting the job so the photographer wouldn’t expect the pilot to perform maneuvers beyond his normal operating scope.

Unfortunately, more than a few pilots will simply cave in under pressure to please the client. Sometimes this is can be a very bad thing that both the pilot and his client don’t live to regret.

A good pilot will evaluate the risks, make a decision, and stick to it. A pilot who is easily bullied by passengers (or management, for that matter) needs to look for a new career.

Misleading Statements in Popular Fiction

I actually wrote most of this post months ago and mothballed it to finish at a later date. But yesterday, I read something in a novel that made it clear how little the general public understands about helicopter operations.

In the story, the protagonists are passengers on a helicopter that’s running out of fuel. The lead protagonist tells the pilot to lose altitude. His reasoning:

Helicopters sometimes survived engine failures at a few hundred feet. They rarely survived at a few thousand.

The above statement is false. Reverse the facts and you get the correct statement, which I could word like this:

Helicopters rarely survived engine failures at a few hundred feet. They usually survived at a few thousand.

Why the difference? The H-V Diagram is a big part of it. Take a look. If a pilot is flying at 200-300 feet, he’ll have to be moving at at least 50 knots to stay out of the deadman’s curve. The H-V Diagram clearly shows that the higher you are and the faster you go, the farther you are from the deadman’s curve. Altitude and airspeed are two energy management components that can save a pilot’s life in the event of an engine failure.

If you’re operating outside the deadman’s curve, the thing that makes higher altitudes safer is time. If you’re cruising along at 500 feet AGL at 100 knots — a perfectly safe combination of altitude and airspeed, according to the H-V Diagram — you’re going to be on the ground a lot quicker than if you were doing the same speed at 1,500 feet AGL. That’s less time to correct any problems with your autorotation entry, pick a good landing zone, make a Mayday call, brief your passengers, etc. Now imagine cruising at the unlikely altitude of 3,000 feet AGL. In a good gliding helicopter, like my R44 or a Bell LongRanger, you have lots of time to set it up and do it right.

Clearly, higher is better.

There were some other errors in the book as far as the helicopter was concerned, but I’ll save them for another post. (It really does bug me when books, movies, and television send inaccurate messages about how helicopters fly.)

Why Not Get the Facts Straight?

Time passes. I don’t recall when I started writing this post, but I know I didn’t last long with the photographers in that group. They were very full of themselves and highly critical of newcomers. And some of them echoed the same uninformed ideas about the safety of helicopters that I hear everywhere else. Worst of all, they didn’t seem interested in learning the truth.

I wrote a post earlier this month titled “Why Forums Suck” that describes the atmosphere in this particular group. Maybe it’s me, but I simply don’t have patience for people who behave the way some of these guys (and women) did.

And, in case you’re wondering, I e-mailed the author of the book with the errors. I hope he didn’t think I was being rude. But I want him — and anyone else preparing material about helicopters — to get the facts straight before releasing it to the public. In his case, any helicopter pilot could have pointed out the problems I found and reported to him. A few minor changes to the manuscript would have made it accurate without impacting the story one darn bit.

I just wonder if other pilots who read the book were as irked about the errors as I am.

Probably not.

The Children of Men

Futuristic social commentary by P.D. James.

The Children of MenI just finished The Children of Men by P.D. James. James, who normally writes mysteries featuring her series detective, Adam Dalgliesh, wrote instead of a futuristic world 25 years after the birth of the last-born child. In the world of this book, there are no children, no babies, and no hope for new human life.

James paints a sad picture of that world. Schools are converted into housing for the elderly, colleges now teach courses of interest to adults who don’t have their time occupied by their offspring. Playgrounds are gone. The government is trying to centralize the population in big cities so it’s easier to provide services as the population dwindles and only a handful of elderly people are left.

[This might sound weird, but it reminded me a bit of the retirement town I live in. Of course, there are some children and young people here, but the majority of residents and voters are retired so there isn’t much emphasis on things that would benefit young people. The local school board, for example, was unable to pass a school bond in the most recent vote — people don’t want to foot the bill for education when they don’t have kids in the system. The local Center for the Arts released its 2007/2008 schedule last month, and for the first time since opening about 5 years ago, there isn’t a single family-oriented program on the schedule. Are they giving up on children here in Wickenburg?]

The book has a hero: 50-year-old Theo. Theo is first cousin of the Warden of England, Xan, a self-made dictator first elected as Prime Minister years ago. Xan makes extreme decisions that benefit the apathetic public, by enhancing safety and reducing the cost and bother of supporting the aging population. But a handful of people aren’t happy with his decisions and want to stop him. They go to Theo, hoping he can convince Xan to change things. To say much more would be a spoiler, but I will mention that there appears to be hope for the world when a woman becomes pregnant.

Netflix, Inc.Ad

I enjoyed the book’s fast pace after its initially slow start. A lot of background information was presented in the form of Theo’s personal diary before a third person narrator stepped in and picked up the story. It wasn’t a long book — I read it over a weekend — and the pages turned quickly. Now I’m waiting for the movie based on the book to appear in a Netflix envelope in my mailbox. I have a feeling that the movie will be a lot more exciting than the book, focusing on the events that occur after the pregnancy is discovered, Hollywoodized for maximum visual impact.

Did I like the book? Yes, I did. It made me think. And in today’s world of eye candy entertainment, that’s saying a lot.

Keeping Busy on the Left Coast

Where I’ve been for the past few days.

On Sunday, May 20, Mike and I climbed aboard Zero-Mike-Lima for a flight to the Los Angeles area. (It was a relatively uneventful flight and, if I find time, I will bore you with the details in another blog post.) We landed at Torrance Airport, where we had business to do, and took a cab to LAX, where we rented a car for the week. Zero-Mike-Lima is sitting at the ramp in Torrance, right in front of the Robinson Helicopter factory, waiting for our flight back to Wickenburg on Sunday.

We came out here primarily to take the Robinson Factory Safety Course, a 3-1/2 day course designed to educate helicopter pilots about how accidents occur — and how they can be prevented. This was my third time at the course and Mike’s first. I’ll probably be writing more about it in another blog post because I really think it’s worth covering in some detail.

We’ve been on the go almost since arriving in the area. In fact, other than sleep at night, the only rest we had was right after checking into our hotel in Torrance on Sunday.

On Sunday night, we went down to the Redondo Beach pier for a seafood dinner.

Monday, we were in class from 8 AM to 4 PM. Then we zipped into Los Angeles for a walk around the Farmer’s Market and Grove shopping center.

Tuesday, class from 8 AM to 4 PM. Then, after a quick walk around a mall to pick up a few things, we headed back into Los Angeles for dinner and some shows at The Magic Castle with my friend (and fellow author) Deb Shadowitz. We got in to our hotel at 1 AM.

Wednesday, class from 8 AM to 4 PM. Then we hopped in the car and headed south along the coast, ending up in San Clemente for a visit with our friend (and fellow helicopter pilot) Jim Wurth.

Thursday, class from 8 AM to 11 AM. Then, after a quick trip to the Verizon Wireless store for some bad news, we headed back to the Robinson factory for lunch and to wait for Mike’s flight. (Mine was on Tuesday, during class.) Then it was back in the car for a drive up the coast, with a quick stop in Venice, to our new hotel in Malibu.

As you can see, we’ve been pretty much on the go since Sunday morning. Actually, it’s been since Saturday morning, when we gave helicopter rides at Yarnell Daze.

So I haven’t had any time to write in my blog.

imageIt’s Friday morning and, as usual, I was up at about 5:30 AM. Our hotel is weird. It was probably an old hotel that was recently gutted and renovated. Our room has nice (fake) hardwood floors, clean white walls, and a king-sized bed. But not much else. Really. There’s no dresser, no chairs (other than on the little balcony), no table, no sofa. There are two night tables and one lamp. No clock. The TV is a 17 or 19 inch flat screen, mounted on the wall. There’s a 3 cubic foot refrigerator and a wire clothes rack on wheels as a closet. The place is trying to be “trendy minimalistic,” and although the effect is pleasant, it isn’t comfortable. We have views of the ocean from our windows, but no access to the beach. And the two lanes (in each direction) of the Pacific Coast Highway run right past the place. Cars, trucks, and motorcycles drive by throughout the day and night.

There’s Internet access via an unsecured network named “default,” but to get connected, you have to stand in a certain place in the room with your computer on the windowsill. I’ll probably use that to publish this entry.

This is the part of the trip I’ve been looking forward to: the part where Mike promised we’d just “take it easy.” We both expected this place to be on the ocean with access to the beach, so we’re very disappointed (to say the least). We’ll probably find another place later today. In my mind, “take it easy” means to relax in a comfortable place, read, write, or just chat. It doesn’t mean hopping in the car and driving all over the place. I know he’s not going to want to hang out here. I probably won’t either. So I’m not sure when I’ll find time to write again.

Stay tuned. More to come.

[composed in a hotel room in Malibu, CA with ecto]