Travel Insanity

Too many miles, too little time.

I’m just recovering from a crazy week with too much travel in too short a time span.

Our Flight Path

Our flight path, recorded on my iPad with GPSTrack. Can you tell where we did some scud running?

It all started last Saturday, when I flew with two companions from Phoenix, AZ to Wenatchee, WA by helicopter in one day. It was almost 11 hours of flight time with mostly very brief stops for fuel. Although I had very little stick time — one of my companions did almost all the flying — I was still alert and able to fly at a moment’s notice.

It got a little tense when we had to do some scud-running in Oregon that lasted far longer than I like to be spending scud running — as if I like it at all. It never got dangerous, but more than a few times, I began scouting the remote hillsides around us, looking for a place to set down and wait it out. I was very glad when the terrain finally descended, dumping us in an area where we could get back on course.

We spent the night in Wenatchee and I parted company with my travel companions, leaving them to catch an early flight to Seattle while I took care of other things locally.

Sunday was relatively restful. I needed to reposition the helicopter to Quincy, WA, where I’d be spending part of my summer. That was just a 15-minute flight. Then I spent some time socializing at Ferguson Flying Services, where my helicopter is parked in Quincy, and the Colockum Ridge Golf Course, where my RV would be parked soon. Then a friend/client picked me up and drove me the 5 miles to his winery in town, where I spent the afternoon socializing with him, his family, and the folks who came for wine tasting. A nice, mellow afternoon.

But at 4:15, the craziness started again. I got a lift to Wenatchee Airport, where I caught a flight to Seattle with a connecting flight to Phoenix. My husband picked me up there at about 10:30 PM. Overnight at our Phoenix condo.

Monday morning, bright and early, we were on our way back up to Wickenburg. I spent the day finishing up some work on a chapter of my book and then packing. It wasn’t until nearly 9 PM that night that we were done and pulling the RV out of the hangar where it lives most of the year. We left it parked in front for the night.

Welcome to NevadaAt 6:45 AM, I was in the driver seat of the truck with Alex the Bird in the seat beside mine. We were starting a 1,295-mile drive from Wickenburg, AZ to Quincy, WA. My goal was to make Jackpot, NV that first day — a distance of 725 miles. I spent most of those miles on Route 93, a two-lane road with speed limits up to 70 miles per hour. There was no traffic and certain stretches of the road were straight and flat as far as the eye could see. We made Jackpot before nightfall. After dinner n the casino, I spent the night in the RV with Alex in comfort — in the casino parking lot.

My Rig, in Jackpot, NVThe next morning, I woke at 6:15, which is late for me. Anxious to get on the road, I rushed around making my coffee and Alex’s breakfast and then buttoning up the RV for another day on the road. It wasn’t until after I topped off the fuel tank across the street from the casino that I realized it was an hour earlier; that part of Nevada is on Mountain Daylight Time. So I got a very early start. I left Route 93 behind in Twin Falls, ID, and hopped on I-84. The route was mountainous and the truck sucked diesel at an alarming rate as I struggled to maintain speed up hills. I left the interstate just past Pendleton and got back on smaller, traffic-free back roads to head north. After 10 miles on I-70 and the last five miles through familiar farmland, I rolled into the parking lot at the Colockum Ridge Golf Course RV Park just after 3 PM.

My Route

My route, as captured by GPSTrack on my iPhone.

I was fortunate to have had good weather all the way. Towing 13,000 pounds of fifth wheel RV on wet pavement is no fun — as I learned last year. It was just starting to rain when I finished hooking up my utilities at 4 PM.

Do I need to say how exhausted I was? I’d snacked my way from Wickenburg to Quincy, eating only snacks on my low-carb diet: jerky, almonds, and cheese sticks. The only real meal I’d had was at the casino in Jackpot. My digestive system was a mess for the next two days.

And of course, I developed a bad cold, which I think I’m just coming out of now.

But on the bright side of this, I managed to get all my assets in position for the first half of the cherry drying season. I set up my RV office and yesterday I managed to knock off another chapter of the book I’m working on. I’m also in the area early enough to set up helicopter tours and wine tasting trips with the local wineries.

It’s been a rough week, but now I’m settled in. It feels good to be at my home away from home.

Pelicans

Absolutely prehistoric looking.

Back early in May, I finished up a week in Ventura, CA, where was I updating my Twitter course for Lynda.com. Although Twitter’s feature set didn’t change much since I recorded the second version of course in April 2010, the interface has. The course really needed an update to bring it back into sync with the way the service looks. It should be published shortly. If you have any interest in Twitter, I hope you’ll check it out.

A Backstory

High-Flying PelicanThe folks at Lynda.com put authors up in an area hotel. The first few times I came out here, they put me in a Holiday Inn Express near Ventura Harbor. I really liked my room, which was on the first floor with big windows overlooking the marina. There was a lot of life there — people walking, birds flying, boats, dogs, joggers.

Then, a little over a year ago, they switched to a hotel in Oxnard. Admittedly, it was a nicer facility with better accommodations for us. The rooms were little L-shaped suites roughly the same size as the Holiday Inn’s, but more modern and upscale. And the Internet service was about 5000% better. (Okay, so maybe I exaggerate, but it was better.)

Trouble is, it also lacked everything I liked about the Ventura Harbor place. The place was condo-like, with square 2-story buildings, each having eight units. The windows were small. There were balconies, but no reason to sit on them — and no furniture to sit on. The place was heavily wooded and it seemed dark and dank, like an unpleasant rainforest that was constantly shedding leaves and branches all over the property.

So on this last trip, I asked to stay at the Holiday Inn again. And the nice folks at Lynda.com booked my room there.

The Pelicans

High-Flying PelicanWhich brings me to the pelicans.

It’s odd that I don’t remember them, but they must have been here all along. They fly over the marina every evening, scouting the water between the boats for fish foolish enough to swim close to the surface. When the see their prey, they tuck their wings and dive, landing in the water with a great splash. They bob to the surface, often busy swallowing a fish.

Pelicans are absolutely prehistoric looking. I mean seriously — what other bird looks more like a pterodactyl?

I spent one afternoon after work walking around the marina, settling down in a spot where I could wait to photograph them. Unfortunately, I didn’t bring the appropriate equipment. All I had with me was my 16-85mm lens, which is a great multi-purpose lens but a pretty crappy lens for photographing wildlife. My 70-300mm lens was home. So was my monopod and my tripods.

Pelican Over WaterIn other words, I wasn’t properly equipped.

Still, I made the best of it. What you see here are among my best shots, taken late in the afternoon as the sun was sinking low on the horizon. One thing I learned that afternoon is that pelicans don’t like to dive when someone is standing nearby with a camera. Ah, if only I had my long lens and monopod! Next trip. (If you’re a Lynda.com subscriber, please do give my courses lots of positive feedback so I can some back and record more; next time, I’ll bring that lens.)

The shots here are the best I took that afternoon. Please pardon the ugly watermark, but I’m really sick of seeing my work on other people’s websites without attribution.

Enjoy.

More Blog Posts…Soon

Still very busy, getting ready to relocate, but the end is near.

First of all, you need to understand that I really do like writing in this blog. It makes me feel good to post something each morning as I enjoy my morning coffee. Whether it’s a poorly disguised rant or a detailed account of my latest helicopter trip, it feels good to get the words out and share them with others. I am, after all, a writer at heart and writers need to write.

And that’s actually what I’m doing. I’m working on a revision to a 600+ page book and am about 3/4 finished. There’s a very tight deadline — one I’m not sure I’m going to make this time (don’t tell my editor) — and I’ve been working my ass off on it, getting very burned out in the process. I’m not complaining; this one book earns a whole year’s income so it’s worth what I put into it. But it does leave me too tired and burned out to write in this blog — and not really enough time to do it right anyway.

But the end is near! I’ll soon be repositioning my helicopter and RV to Washington State for the summer. (My house-sitter is already installed to care for the fish and backyard birds and keep an eye on things.) Once there, I’ll finish up the book and have a lot more time for other projects, including some videos and, of course, this blog.

Between now and then, I’ll be making two trips from Phoenix to Washington. On one, I’ll be a passenger in my own helicopter for a day or two. On the other, I’ll be driving my “rig” on a two to three day journey through Arizona, Nevada, Idaho, and Washington. On both trips, I won’t be writing about computers. So I expect to have a clear enough head to share some stories about the trips. Maybe some photos, too. With both hands free in the helicopter, I’ll have no trouble taking photos.

So bear with me just a little longer. New blog posts will come soon. I promise.

Too Busy to Blog (again)

Just a quick note to let blog readers know that I’m a bit tied up with work right now and too busy to blog. So although you might find a few “Interesting Links” posts as I stumble across interesting things on the Web during my workday, it might be a few more days before you see a full-blown blog post from me. Bear with me; I have lots to say and just need the time to say it.

On “Air Vortexes”

The media stumbles over a basic aerodynamic aspect of helicopter flight.

I was on Twitter Thursday evening when manp, one of my Twitter friends, tweeted:

So, what is this ‘vortex’ condition with ‘higher than expected temperatures’??? @mlanger any idea?

To be honest, I had no clue what he was talking about. But I Googled “vortex condition with higher than expected temperatures” (don’t you love Google?) and saw an article about the helicopter that went down during the Bin Laden assault in Pakistan. Moments later, manp sent me a link to a Bloomberg article titled “Helicopter Carrying SEALs Downed by Vortex, Not Mechanical Flaw or Gunfire.” The first paragraph read as follows:

A United Technologies Corp. (UTX) Black Hawk helicopter carrying U.S. Navy SEALs to Osama Bin Laden’s hideout was downed by an air vortex caused by unexpectedly warm air and the effect of a high wall surrounding the compound, not mechanical failure or gunfire, according to U.S. officials and a lawmaker.

Whoa. What a mishmash of information. You have to read further into the article where the phenomena they’re trying to explain — vortex ring state — is explained at least two more times by people who actually have a clue what it is. But that first paragraph sure is misleading. It makes it seem as if there was come kind of weird warm air vortex in the compound that brought the helicopter down.

Any vortexes, however, were caused by the helicopter itself. My educated guess of what happened, based on this article and knowledge of helicopter aerodynamics, is this:

As the helicopter was descending inside the 18-foot walls — a descent that was likely nearly vertical — it encountered a setting with power — or vortex ring state — condition. This occurs when the helicopter settles into its own downwash. This may have been made worse by the change in the flow of air due to those 18-foot walls — as suggested in the article. It may also have been made worse by the outside air temperature being warm.

This image from the FAA’s Rotorcraft Flying Handbook helps illustrated what the vortexes are and how they manifest themselves in a hover far above the ground and close to the ground:

Hover Vortexes

As the Rotorcraft Flying Handbook explains:

Vortex ring state describes an aerodynamic condition where a helicopter may be in a vertical descent with up to maximum power applied, and little or no cyclic authority. The term “settling with power” comes from the fact that helicopter keeps settling even though full engine power is applied.

In a normal out-of-ground-effect hover, the helicopter is able to remain stationary by propelling a large mass of air down through the main rotor. Some of the air is recirculated near the tips of the blades, curling up from the bottom of the rotor system and rejoining the air entering the rotor from the top. This phenomenon is common to all airfoils and is known as tip vortices. Tip vortices consume engine power but produce no useful lift. As long as the tip vortices are small, their only effect is a small loss in rotor efficiency. However, when the helicopter begins to descend vertically, it settles into its own downwash, which greatly enlarges the tip vortices. In this vortex ring state, most of the power developed by the engine is wasted in accelerating the air in a doughnut pattern around the rotor.

Vortex Ring StateIn addition, the helicopter may descend at a rate that exceeds the normal downward induced-flow rate of the inner blade sections. As a result, the airflow of the inner blade sections is upward relative to the disc. This produces a secondary vortex ring in addition to the normal tip-vortices. The secondary vortex ring is generated about the point on the blade where the airflow changes from up to down. The result is an unsteady turbulent flow over a large area of the disc. Rotor efficiency is lost even though power is still being supplied from the engine.

There are three ways to recover from settling with power once you’re in it:

  • Cut power – you can’t settle with power if you don’t have power. This is usually not a good option when you’re very close to the ground.
  • Lower the collective – this reduces the blade pitch. This is also not a good idea close to the ground, since it will result in a descent.
  • Get some lateral airspeed – this breaks you out of the vortex ring state so you’re not settling in your own downwash. This is not possible when you’re surrounded by an 18-foot wall.

(They train us to recover from settling with power using a combination of the second two methods, but we always practice at altitude, since you can get a good descent rate going if you’re really into it. Indeed, settling with power is a serious danger during aerial photo missions requiring hovering at high density altitudes or heavy weights.)

So the pilot did the only thing he could: land hard. Fortunately, although his hard landing damaged the helicopter, it didn’t cause injuries to to men on board. They were able to complete their mission and come home safely. And they left a souvenir lawn ornament in Bin Laden’s yard.

I realize that this is a pretty complex topic and it’s probably not reasonable to expect the press to get it right. But I personally believe that all technical content published in the media should be reviewed by an expert — or at least someone knowledgeable — to make sure it’s not misleading or unclear to the layperson who will read it.

manp is a pilot — although not a helicopter pilot — and he couldn’t figure out what they were talking about. I can only imagine how much that opening paragraph confused the average reader.