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.

Wickenburg to Seattle by Helicopter: Day 2

Page, AZ to Bryce Canyon, UT.

I’d flown to Lake Powell on Thursday afternoon so I could be ready for a photo flight at 6 AM on Friday.

I spent the night at the Holiday Inn Express in Page. I’d been there before and when I was there this time, I remembered why I hadn’t been back: the damn walls are paper thin. My room was at the far end of the hall, adjacent to a back entrance. The ice machine was in a corridor there, up against my wall. Not only did I hear the sound of people filling their coolers at 3 AM, but I heard the sound of the machine filling with water and the damn motor running. Add the guy upstairs walking at odd hours and you can figure out why I didn’t get much sleep.

But at 5:30 AM, I was at the airport, preflighting the helicopter. At 6 AM, I met my client and flew him and his wife around the lake for 1.3 hours. When he canceled his afternoon flight due to the unseasonably cold weather, I found myself done for the day at 8 AM — a full 12 hours before I expected.

I went back to the helicopter, put the door on, and tied down the blades. Then I headed back to the hotel. I was expecting the weather to deteriorate, so I didn’t see any point to staying in Page. After all, I lived there for two months back in 2008 so it wasn’t exactly a tourist destination for me. I started thinking about heading north, but wasn’t anxious to spend the night in Salt Lake City. Then I considered flying as far as Bryce Canyon, which was on the way and less than an hour flight. I worked the phone and the Web via my iPad. A while later, I had reservations for a cabin at Bryce Canyon Lodge and a rental car at Bryce Canyon Airport.

I packed up and checked out. I had some second thoughts when I stepped outside and saw what a beautiful day it had become, but my room at Bryce was expensive and non-refundable. I was committed.

Wahweap MarinaI was airborne by 10 AM.

I flew northwest at first, eager to check out the new resort that was built not far from Big Water, UT. I’d heard a lot of buzz about it and had actually met someone who worked there the night before at Blue Buddha. From the air, it didn’t look like much, tucked away against some sandstone cliffs. I still don’t understand what all the hoopla is about.

After flying over, I dropped down low and turned north toward Wahweap Creek. I crossed Highway 89 just east of Big Water and dropped down even lower, into the creek bed. I knew the area well. There were no wires and no homes. I great spot for some low-level canyon flying on a beautiful day with minimal winds.

I followed the course of the creek — which was mostly dry, of course — northwest, passing the famous Wahweap Hoodoos at low level. (You can see a video of one of my canyon flights here.) Then I continued up the canyon, beyond where I’d ever flown before. It twisted and turned, rising gently into the flat-topped mesas beyond it. My GPS had Bryce Canyon punched in, so when it appeared the canyon was taking me too far off course, I pulled back gently on the cyclic and began climbing out. I needed a 2000-foot climb to clear the mountains around me. That put me over some typical high-desert terrain with lots of rocks and scrubby trees. In the distance, I could see more mountains — and weather.

I didn’t realize it then, but weather would haunt me for the entire flight from Wickenburg to Seattle.

Sedimentary Rock RidgesI was now squarely in the middle of my middle-of-nowhere route from Page to Bryce Canyon. There were absolutely no signs of civilization below me or anywhere within sight. Instead, an ever-changing terrain revealed itself below me. Hills and mesas were cut deeply by canyons of exposed red rock. Sedimentary rock thrust up from the ground at odd angles, forming layered ridge lines that stretched for miles. Ancient sand dunes turned to rock stood revealed by the erosive forces of wind and rain over millions of years.

Ancient Sand DunesThe view seemed to change every five minutes, revealing wonder after wonder. I wanted to detour and explore. I wished more than ever that I’d installed my helicopter’s nose camera before departing Wickenburg the day before.

As I look at these hastily snapped photos now, while writing this blog post, I realize how truly amazing the terrain in the desert southwest is. I’m spoiled — I see this kind of stuff all the time. While dramatic rock formations still amaze me, I can compare each of these photos to a similar scene somewhere else I’ve flown. The tilted ridge line repeats itself over and over north of the San Juan River in southeastern Utah, not far from Mexican Hat. The solidified sand dunes can also be found near the Glen Canyon dam, atop the Paria Plateau near The Wave, and throughout Capital Reef National Park.

Discovering amazing new formations while flying from point to point is a treat. But it makes me sad that I do these flights alone. I can’t seem to sell folks on the wonder of flight through this area. They’d rather spend their money being one of thousands on a cruise ship or fry on the beach at an all-inclusive resort than experience a unique, once-in-a-lifetime journey through the southwest, 500 feet above the ground in a helicopter. These photos hint at what they’re missing.

But I digress.

As I flew, the clouds thickened. I saw the same signs of rain or snow in the clouds ahead of me. I was heading right for the weather. Tuned into Bryce’s common traffic advisory frequency (CTAF), I heard a charter plane make a call for landing. Still 20 miles out, I asked the pilot what the conditions were. She reported that there was weather to the west of the airport but visibility at the airport was still good. I checked my power settings to make sure I was getting my best speed. I was moving at 110 knots airspeed with a slight tailwind. I wanted to be on the ground before the weather moved in. There were no airports between me and Bryce.

Near Bryce CanyonI finally began seeing signs of civilization: paved roads, ranches, towns. There were plenty of red rock cliffs and hoodoos with roads — paved and unpaved — winding around them. Funny how people go to National Parks to see the sights when the same sights — or better ones — can be found right down the road.

I climbed with the terrain and was finally able to pick up Bryce Airport’s (KBCE) AWOS frequency. Winds 8 MPH gusting to 15, good visibility. But I could see a storm moving in from the west and wondered whether it would beat me to the airport. I looked at my GPS anxiously; I was only 4 miles out and still couldn’t see the airport. But then I spotted the big old hangar and zeroed in on my landing zone on the ramp. I made my radio calls, crossed the approach end of the runway, and landed in a T-spot.

You can see my approximate route on SkyVector by clicking here.

I shut down, gathered my things together, tied down the blades, and locked up. Then I went into the terminal to place a fuel order and arrange to get my rental car.

I’d spend the rest of the day exploring Bryce Canyon National Park on horseback and by car. But that’s another story.

Helicopters 101: Flight Planning

The basics of cross-country flight planning for helicopters.

Articles in the Helicopters 101 series:
Flight Planning
CG
Weight
Hover Charts
Ground School

Recently a reader of this blog wrote to suggest that I cover cross-country planning as a blog topic. I searched my archives and found that I already had. My post, “Flight Planning,” goes into a great deal of detail about the process I use to prepare for Part 135 charter flights, which require a complete flight plan. But that’s probably not what this reader was talking about. I think he was more interested in the nuts and bolts of creating a flight plan.

This weekend, I have to make three relatively long cross-country flights:

  • Wickenburg, AZ (E25) to Page, AZ (PGA) – 189 nm direct
  • Page, AZ (PGA) to Salt Lake City, UT (SLC) – 232 nm direct
  • Salt Lake City, UT (SLC) to Seattle, WA (BFI) – 601 nm direct

I’ve flown the route from Wickenburg to Page and back numerous times. I’ve done Salt Lake CIty to Page once and Seattle to Salt Lake City once. I figured I’d use the PGA to SLC flight, which I’ll be doing alone, as an example of how I plan a flight.

Weather

A few days before the scheduled flight, I start checking the weather along my route. I use the National Weather Service’s NOAA Web site for weather information. After all, the NWS is the source of all the weather data for the United States. That’s where the Weather channel and Duats and the FAA get raw weather data. Although each weather reporting organization may interpret it slightly differently, it’s all based on the same stuff. And the NWS site doesn’t bombard me with obnoxious advertising.

A lot of folks use the Aviation Weather link to get aviation weather information. I don’t — at least not a few days out. Remember, I’m flying a helicopter. I’m 500 – 1000 feet off the ground. I don’t care much about upper level disturbances, the jet stream,or icing in clouds. I’m not getting anywhere near that stuff.

Page Weather

The graphic weather forecast for Page on the morning this post was written.

What I’m interested in is forecasted conditions for the departure and arrival airports, as well as any cities in between. So, in this case, I would check out the weather forecast for Page, Salt Lake City, and possibly Richfield, which is roughly halfway between the two. I’ll pay close attention to the forecast for my day of travel, as well as the day before and after.

What I see today is relatively poor forecasted conditions for Saturday, the day of my flight, with chance of rain or snow at each location. Not what I want to see, but remember, it’s a forecast. It will probably change. I have to hope it gets better.

Route

Next, I plan out my route. Although I listed straight-line distances at the beginning of this piece, I seldom fly in a straight line. Instead, I try to find a route that’s a compromise between a straight line — which, out in the desert, usually means doing a lot of flying in the middle of nowhere — and following roads — which is where people will be if I need help.

Now I need to make it clear that unless there’s a road going the way I need to go, I’m not going to follow roads to get from Point A to Point B. I don’t want to go out of my way — at least not too far. Helicopters are expensive to fly and I’m not made of money. The time budget for this trip is 2 hours — that’s what the client paid for — and I’ll need all of it and then some. So what I want is a compromise that puts me near roads for part of my trip.

I plan my route with charts. World Aeronautical Charts (WACs) are very handy for long cross-country flight planning. But sectionals offer more detail.

Of course, I cheat. I use SkyVector.com. It puts the charts onscreen and enables me to do some very basic flight planning — mostly distances and directions. As the site warns — probably with the advice of lawyers — it’s not for navigation or preflight use. But I use it for preliminary planning. It really helps me get a good idea of where I need to go.

Options

The pink line at the bottom is the direct route from Page to Brice; the red and blue lines are my two options for continuing northbound without overflying 10,000 foot mountains.

In this case, I’m seeing that a direct flight from Page (PGA) to Bryce Canyon (BCE) would take me 57 nm mostly over remote, high desert terrain, climbing from about 4300 feet to over 7000 feet. No major mountain ranges to cross along the way — and that’s good.

From there, I can follow the East Fork of the Sever River and the road beside it northbound between a pair of mountain ranges topping out at over 10,000 and 11,000 feet, then follow a pass that’ll hook me up with Highway 89. This map shows it as the red route. That’s the way I flew last time and the only drawback I recall was the rough air in that pass.

The other option is to continue on almost the same heading to Panguitch (U55), which will hook me up with Highway 89. I can then follow that northbound between two mountain ranges topping out at 11000 feet, staying slightly lower in overall altitude and sticking with a well-traveled road. This map shows it as the blue route.

Completed Route

My planned route, roughed out on SkyVector.

I continue this process for the entire trip. This one’s pretty easy; I’ll be following Route 89 most of the way. When I get to the outskirts of Salt Lake City, I’ll be following I-15. This turns my 232 nm trip into a 259 nm trip and adds at least 15 minutes of flight time. But I’ve minimized my flying time over the middle of nowhere without detouring too much out of my way. The WAC charts I pasted together here from SkyVector screenshots give you an idea of what the entire route looks like. I can also see that my flight without wind could be as long as 2-1/2 hours. My helicopter’s endurance is just 3 hours, so I need to consider the possibility of needing a fuel stop if I hit headwinds. Fortunately, there are plenty of airports with fuel along the last 50 miles of my route.

By the way, the main benefit to following a road when you enter busy airspace and don’t know the local reporting points is that you can state your position to ATC in relation to the road. For example, “Helicopter Zero-Mike-Lima is ten miles south over I-15” is a very definite location.

Once I get a rough outline of the course, I go into detail with sectional charts. I buy them as needed for my cross-country flights. I’ll check to be sure there’s no special airspace or weird activity (think gliders and ultralights) along the way. I’ll also look for charted power lines — not that I’ll remember them when the flight time comes. I’ll make a cheat sheet of airport names, designators, elevations, and frequencies so they’re easy to enter into my GPS for added navigation assistance during flight.

Although I don’t usually mark up my local charts (Phoenix sectional and terminal area chart), I don’t mind taking a highlighter to the Las Vegas and Salt Lake City Sectionals I’ll use for this trip. I’ll also have a Salt Lake City terminal area chart on hand. Before I start my flight, I’ll fold them all neatly to expose the route. With just one hand to fiddle with charts, it’s much easier to prepare before lift off.

Destination Information

On this particular trip, I’ll be landing at Salt Lake City Airport, a Class Bravo airport I’ve never landed at before. I’ll need to know where on the airport I’ll be landing so I don’t sound like a complete idiot when I talk to the tower.

Airport Diagram

The airport diagram for SLC. General aviation is handled in the southeast corner, not far from the I-15 freeway.

I could pull out my Airport/Facilities Directory and look up the airport, but that green book is already stowed in the helicopter for the trip. So instead, I’ll hop online to the FAA’s AeroNav Services (formerly NACO) web site. Once there, I’ll click the link for Free Digital Products and then click d -TPP and Airport Diagrams on the page that appears. (Note that you can get a PDF of the page(s) for a specific airport from this site, too.) I’ll use links and search to get the Airport Diagram for SLC, which will be downloaded as a PDF. I can print it out for future reference and put it with my charts.

I’ll also go to AOPA Airports and get information for SLC. I’m interested mainly in FBOs. I was told to go to Million Air, so I want its location, frequency, and phone numbers. AOPA Aiports also shows a zoomed in satellite image of the FBO’s location, making it easy to mark on the airport diagram.

While I’m at the AOPA Airports site, I’ll also jot down the phone numbers for the AWOS or ASOS systems along my route. I’ll program these into my cell phone. This way, if I need up-to-date weather information for a specific airport, I can get it by simply calling. This has come in handy in the past in marginal weather conditions. I have quite a few airports stored in my computer and phone.

Note that I always get airport frequency information from FAA sources: up-to-date charts or the Airport/Facilities Directory. No online database that isn’t maintained by the FAA is guaranteed to be accurate. There’s nothing worse than trying to land at a towered airport and having the wrong frequency for it. I’ll also update my Garmin 420‘s database before this flight. I have an annual subscription, but I often skip updates because they’re such a pain in the butt to install.

Final Planning

I’ll keep watching the weather all week. If it starts to look like its getting worse, I’ll start thinking about rescheduling my trip. In all honesty, the only thing that would stop me from doing the flight would be winds in excess of 40 miles an hour (possible, but not likely), low clouds (definitely possible), or freezing rain (possible). Although I mostly fly in great weather here in the desert, I’ve flown in ugly weather, too. A fair weather pilot should not be flying for hire.

The day before the flight, I’ll call Million Air and tell them to expect me. I don’t have to do that, but it’s better than just dropping in. They’ll also give me some insight about where to land/park. I’ll note it on my airport diagram.

The day of the flight, I’ll check the weather again. This time, I’ll use Duats.com. I’ll punch in my flight plan airports and let Duats tell me the official aviation weather and notams and give me a more precise (official) flight plan that factors in the wind.

Could I do it by hand? Yes, if I had to. But I don’t so I don’t.

I’ll also make my fly/no fly decision.

I’ll file a flight plan via Duats. I might forget to open it when I take off, though. I often do when I fly by myself. But I have a Spot Messenger that broadcasts my location to a Web site that my husband monitors. I think that’s better flight following than I could get from the FAA without climbing to 12,000 feet. (Keep in mind that I don’t have oxygen and the R44 vibrates like a coin op motel bed at altitudes above 9500 feet.)

That’s About It

That’s all there is to it. The longer the flight, the more variables to consider. This is a pretty short one. The flight from Salt Lake City to Seattle is another story. Lots of variables there. My co-pilot on that trip will plan and fly the entire route. I’ve already looked at the route he suggested and it seems fine to me. I’ll just follow along on the chart.

The main thing that makes this different from planning for an airplane flight is the altitude issue. Airplanes climb several thousand feet over terrain. Mountains don’t get in their way; they’re above the mountains. Helicopters generally don’t fly that high, so we often look for routes that take us around obstacles like 11,000 foot mountain ranges. We also have the luxury of being able to land almost anywhere if we have a problem