Wickenburg to Seattle by Helicopter: Day 1

Wickenburg to Page, AZ.

Regular readers of this blog who don’t follow me on Twitter might have been wondering where I’ve been. Did I fall off the face of the earth? Or finally, after six years, get tired of blogging?

Neither. I was making my annual helicopter repositioning flight to Washington State.

This year, I got an early start, piggy-backing my long cross-country flight at the end of a photo flight at Lake Powell. A photographer was willing to pay for the 4-hour round trip ferry time for me to get the helicopter from the Phoenix area to Page, AZ. At the end of that flight, I continued north to Salt Lake City instead of heading home. This put me several hours closer to my destination. At Salt Lake City, I picked up Jason, a low-time CFII interested in building R44 time for much less than the cost of renting. With Jason at the controls, we continued to Seattle.

The trip can easily be summarized by the number of days it took to complete. I’m putting it all down here, in four parts, while it’s still fresh in my mind. The photos aren’t terribly good due to glare through the bubble, but I hope the illustrate some of the terrain and weather we encountered.

In this first part, I’ll cover my trip from Wickenburg to Page, AZ. You can click here to see my approximate route on SkyVector.com.

I’ve made the trip from Wickenburg to Page (or Page to Wickenburg) countless times. It’s the kind of trip that I don’t even need to consult a chart to complete. I know the landmarks by heart.

But on Thursday, the weather promised to be a factor. Although it was sunny down in Wickenburg as I preflighted around 2:30 PM, the clouds were building to the north. I could see them thickening over the Weaver Mountains 15 miles away. And all the forecasts for all the points north of the Weavers called for high winds gusting into the 30s. It would be a bumpy ride.

So bumpy, in fact, that my friend Don and his wife decided not to join me on my trip to Page. Don’s got a helicopter very much like mine and he’d planned to fly up there with me, spend two nights, and let me show him around Lake Powell between my photo flights. But with the forecast so nasty, he bowed out. I didn’t blame him. No one wants to spend 2 hours getting thrown around the sky in a relatively tiny bubble of metal, Fiberglas, and Plexiglas.

And if wind wasn’t enough of a deterrent, the forecast also called for isolated showers and thundershowers north of I-40. So I knew I’d be dodging weather, too.

But I had a contract and my client had paid me to fly up there. I had a pilot waiting for me in Salt Lake City for a Saturday departure. The weather would have to be impossible to fly through to prevent me from making the flight.

So at 3:30 PM, I took off from Wickenburg (E25) into a 15 mph wind from the west and turned out to the north.

Wickenburg RanchI climbed steadily at about 200-300 feet per minute, gaining altitude slowly to clear the 5,000 foot Weaver Mountains ahead of me. Below me, I could see the scars the near-bankrupt developers had left on the desert where Routes 93 and 89 split off. Greed had scraped the desert clean, built a golf course, and then let the grass wither and die. Where there was once pristine rolling hills studded with cacti and small desert trees, there was now flattened dirt, void of vegetation, shaped by bulldozers and men. A dust bowl on windy days covering hundreds of acres of Sonoran desert.

I continued to climb, looking out at the Weaver Mountains ahead of me. The clouds were low over the mountain tops and I could clearly see patches of rain falling. The wind was moving the weather along at a remarkable pace. I picked a spot to cross the mountains, preferring the place where Route 89 climbs into Yarnell over the more direct crossing at the ghost town of Stanton and the valley beyond it. I knew from experience that the wind would be setting up some wicked turbulence in that valley as it gusted over Rich Hill and Antelope Peak. I braced for the turbulence I expected as I topped the hill at 5,000 feet MSL and was surprised when I wasn’t blasted.

That’s not to say there wasn’t turbulence. There was. But it was the annoying kind that bounces you around every once in a while just for the hell of it. The kind that makes flying unpleasant but not intolerable. The kind pilots just deal with.

Ahead of me was Peeples Valley, which was remarkably green. Our winter and spring rains had fallen as snow up there and it wasn’t until the warm weather began arriving that the grass could start sucking it up. The result was a carpet of new green grass that made good eating for the open range cattle and horses up there. All it needed was a little sun to give the illusion of irrigated pasture. But the sun was spotty, coming through breaks in low-hanging cumulous clouds.

Peeple's Valley to KirklandThe weather up ahead gave me a good idea of what I’d be facing for much of the trip: a never-ending series of isolated rain and snow showers. They appeared as low clouds with hanging tendrils of wispy precipitation. But unlike the gray rains hanging below summer rainclouds, these were white, making me wonder whether I was looking at rain or snow. With outside air temperature around 4°C (40°F), it could have been either. Or something worse; damaging hail or icy sleet.

I’d been taught at the Grand Canyon that if you can see through it, you can fly through it. But I didn’t think that rule applied to late spring storms at high elevations. I wasn’t going to fly through anything I didn’t have to.

Knowing which way the storms were moving made it easy to skirt around their back sides. Up near Kirkland, this put me several more miles west of my intended course. Before taking off, I’d punched the waypoint to our property at Howard Mesa into my GPS; I always fly over anytime I’m close, just to make sure everything is okay. Having flown the route dozens of times, I should be flying much closer to Granite Mountain. But that mountain was completely socked in by one of the storms, so I passed to the west of it, adjusted my course line with the push of two buttons, and continued northeast.

Near the Drake VORNear the Drake VOR, I detoured more to the east to avoid a rapidly approaching shower. Raindrops fell on my cockpit bubble and the 110 wind of my airspeed whisked them away. The sky was clearer ahead of me, although the tops of Bill Williams Mountain was still shrouded in clouds. The Prescott (KPRC) ATIS reported mountain obscuration and snow showers to the north, east, and west. I couldn’t see the San Francisco Peaks, which were likely getting more snow to extend the skiing season at the Snow Bowl.

Bill Williams MountainThen I was back out in the sun — a good thing, since the outside temperature had dropped to just over freezing and my cabin heat wasn’t able to keep up with the cold. I climbed up the Mongollon Rim just west of Bill Williams Mountain, trading high desert scrub for ponderosa pines. The mountain had recently been dusted with fresh snow. That didn’t surprise me; only three hours before, the airport at Williams (KCMR) had been reporting 1/4 mile visibility.

By now, the turbulence had become a minor nuisance that didn’t bother me much. I was listening to a genius mix on my iPod, hearing songs I didn’t even know I owned and trying to enjoy the flight. I was almost an hour into it and had more than an hour to go.

I reached Howard Mesa and flew over our place. Everything looked fine. I was surprised to see the wind sock hanging almost limp. Surely there was more wind than that.

I punched the next waypoint into my GPS; a point on the far east end of Grand Canyon’s restricted airspace. I wasn’t allowed to overfly the Grand Canyon below 10,500 feet. Since my helicopter starts rattling like a jalopy on a dirt road over 9,500 feet, that was not an option. Besides, one look out in that direction told me that no one would be flying anywhere near the Grand Canyon that day. All I could see to the north was a blanket of low clouds. I couldn’t even see Red Butte, a distinct rock formation that can normally be seen from 50 miles away. The Grand Canyon (KGCN) ATIS confirmed that things were iffy. The recording reported “rapidly changing conditions” and instructed pilots to call the tower for current conditions. You don’t hear that too often on an ATIS recording.

My course would take me east of that area, but the weather was also moving east. It soon became apparent that I was in a race against the storm. I was halfway to my waypoint when I realized that I wasn’t going to be able to go that way. Although there was a gap there between two storms, I knew from experience that gaps can disappear quickly, swallowing up whatever naive pilot slipped inside. The temperature had dropped down to 0°C and the clouds were only 300 feet above me as I zipped across the high desert, 500 feet off the ground. I’d have to detour to the east.

I aimed for the leading edge of the storm, hoping I could reach it and go around it. But the leading edge was racing eastward to cut me off. My course kept drifting eastward until I was heading due east. That would put me, eventually, over the Navajo and Hopi Reservations, far from any major road or town. I didn’t want to go that way.

I came down off the Coconino Plateau just southwest of Cameron. At least that’s where I figured I was. The low-hanging clouds had blocked all of my normal landmarks from view. To the north, where I needed to go, was a solid sheet of gray rainfall, blocking out whatever lay beyond it. As I descended from the plateau, still heading east, I began thinking of making a precautionary landing and waiting out the storm.

Then I saw a break in the storm with bright sunlight beyond it. It was still raining there, but I could clearly see my way through and what I saw looked pretty good. I banked to the north and entered the rainstorm. Soon, I was being pelted by rain. Visibility was still tolerable; I could see well enough to fly. Thankfully, there were no downdrafts to contend with. Just turbulence, rocking me around, punishing me for interfering with nature’s gift of rain. I held on and rode it out.

And that’s when the carbon monoxide detector light went on. On departure, I thought the heat had smelled a little more like engine exhaust than usual, but had put it out of my mind. The warning light brought it right to the front of my mind again. I opened my door vent and the main vent and pushed the heater control to the off position. I took stock of the way I felt: any symptoms of carbon monoxide poisoning? No, I felt fine. But soon I’d feel very cold.

Echo CliffsI passed through the rain and emerged on the other side with a clean cockpit bubble and likely very clean rotor blades. Ahead of me, now due north again, the sky was brighter and I could clearly see the Echo Cliffs. Before entering the storm, I’d punched Tuba City (T03) into my GPS to keep my bearings; now I punched in Page (KPGA) and was pleased to see that I was already right on course. I aimed for The Gap, a small town at the gap in the cliffs, right on Route 89, adjusted power to maximize speed, and sped forward, 500 feet off the high desert floor.

The rest of the trip isn’t very interesting. I did get some different views to the west, where the Grand Canyon was still covered by a thick blanket of clouds. It would be snowing there, especially over the North Rim. My usual path was at least 20 miles to the west, much closer to the Canyon. It included overflying the Little Colorado River Gorge and mile after mile of nearly deserted flatlands on the far west edge of the Navajo Indian Reservation. I was still over the reservation on this path, but the land below me was sculpted by wind and water into mildly interesting patterns. This was the western edge of the Painted Desert, which is not quite as picturesque as most people think.

The GapI crossed Highway 89 at The Gap and flew through the gap in the Echo Cliffs. I was now about 45 miles from Page, flying among three sets of high tension power lines that stretched from the Navajo Generating Station on Lake Powell to points south. There was a dirt road here that made a short cut to page — if you didn’t mind driving more than 40 miles on a dirt road. Navajo homesteads were scattered about. The sky was a mixture of clouds and patches of deep blue. I warmed in the sunny spots and cooled in the shadows.

It was after 5 PM and I was starting to worry about reaching Page in time to pick up my rental car at 5:30. I began making calls to the FBO from 25 miles out. No answer. A while later, another plane called in from the northwest. Other than that, silence.

I was fifteen miles out when Lake Powell came into view. It looked gray and angry under mostly cloudy skies.

I landed on the taxiway parallel to runway 33 and went right to parking. A line guy from American Aviation arrived with a golf cart to pick me up. I shut down and jumped in. It was 5:30 PM; the 200 NM flight had taken almost exactly 2 hours. I was just in time to get my rental car.

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

Photo Shoot at San Xavier Mission

A nice excuse to visit Tucson.

This past weekend, Mike and I took the camper down to Tucson, parked it at Gilbert Ray Campground (highly recommended) on the west side of the city, and joined the members of Arizona West Shutterbugs for a photo outing at the San Xavier del Bac Mission just off I-19 south of Tucson.

I’ll likely blog about the rest of the trip another time; for now I wanted to share some information about the photo shoot, as well as a few photos.

We were scheduled to meet the group at 7:30 AM at the mission. We’d spent the night nearby, so we were less than a half hour away when we started down there. We arrived at about 7:10; less than 15 minutes before sunrise.

The place was almost deserted. A few members of our group had arrived and were parked off to one side. We parked in the back of the parking lot so as not to block anyone else’s long shot of the mission.

It’s not my purpose to tell you about the mission. You can learn about it on the San Xavier del Bac Mission Web site or Wikipedia. So please don’t criticize me for being short on facts here. I’m typing this in a camper and have to literally dial-up (via my cell phone and Bluetooth) to go online and check facts.

Candles at San Xavier MissionIt was cloudy to the east when we arrived, so sunrise was pretty much a non-event. Although I did take some photos of the front of the building in first sun (or what we had of it), I detoured to a small shrine-like building on the west side of the main church building. My friend, photographer Ann Torrence, had suggested this. I took a number of photos of the multitude of statues in candlelight before light started creeping in through the door behind me. The one here was shot with one of the 10mm lenses we rented from BorrowLenses.com.

Only a few minutes later, a pickup truck backed up to the front of the church gates. There was a blue coffin in the back. A man set up a coffin dolly and several others carried the coffin over to it. People started assembling in front of the church. Any photographer present stopped taking photos in respect for the family and friends of the deceased. A priest in traditional Catholic priest garb came out. He spoke with the family, then stood in the doorway of the church and began the service. The sound of his voice echoed in the building behind him and for a while, I thought it was a trick of the acoustics. I later discovered that he was wearing a wireless microphone. So much for construction design miracles.

The service lasted about an hour. During that time, the rest of the photographers arrived and we swarmed all around the outside of the church, snapping photos just about everywhere. There were about a dozen of us. Most of us had tripods and digital SLRs, but there were a few folks shooting without tripods or with less sophisticated camera equipment. I’d come fully prepared with a tripod, my Nikon D80, and four lenses: 10.5mm fisheye, 10-24mm, 16-85mm, and 70-300mm. I mostly used the 10-24mm rented lens and my usual 16-85mm lens.

Virgin Mary at San Xavier MissionWhen the funeral ended, we paused as the blue coffin was loaded into the back of a Cadillac Escalade hearse — which I didn’t even know existed. As the mourners departed, the photographers swarmed into the church.

The mission is beautiful in a weird old Spanish/Native American way. It’s amazingly colorful and ornate, with dozens of statues of saints and angels. Spotlights are strategically placed to bring certain statues to life. Don’t get me wrong: you’ll need a tripod (recommended) or flash (not recommended) to get good photos in there — it’s mostly pretty dark. But with the right exposure, you can get some stunning images.

Altar at San Xavier MissionThe main altar area, which is shown here, is a crazy ornate masterpiece of southwestern art. Having grown up Catholic, I can’t imagine sitting through a mass amid such decorations. Yet the church is active and has mass daily. (No photography allowed during church services.)

St. Anthony at San Xavier MissionThere are also candles all over the place. The sale of candles is probably the church’s biggest fund-raiser. They’re not expensive — only $3 each — and they’re quite beautiful when lined up in racks near statues. I bought one in memory of my grandmother. I’m not religious, but she was. She would have liked the place, so I bought a candle and put in in front of Saint Anthony (or “S. Antonio,” as the label at the bottom of the statue said). My grandmother used to have a Saint Anthony statue in the guest room — my mother has it now — so Saint Anthony statues remind me of her.

San Xavier MissionBy the time we were finished inside, the sun was out and the sky was nearly clear. I shot this photo of the front of the mission, after waiting about 10 minutes for various tourists to meander in and out of my composition. This was shot at f/16 with a polarizer to enhance the color of the sky. There’s definitely some distortion in this shot, but I rather like it. It’ll probably end up in my photo blog.

San Xavier Mission PewsI also got a little creative, working with various elements inside and outside the main building. These two photos are examples. The first is of the backs of the church pews. They’re simple carved wood with this unusual scalloped edge. It was sad to see that more than a few people had carved words into the backs of them.

San Xavier Mission Wall DetailThis shot is a closeup of a scroll design in the stucco finish of a wall outside. I like textures and try to experiment with them in my photography. Although not very interesting, this is a good example.

These are only a few of the 100 or so photos (not including bracketed exposures) I shot at the mission. I’d like to go back and try for a sunrise shoot again.

If you plan to go, here’s some advice:

  • Bring a tripod. You’ll need one if you plan to shoot indoors.
  • Leave your flash at home. All it will do is make ugly shadows behind the statues.
  • Don’t plan on photographing any kind of church service inside the mission. It felt good when the priest came into the church a half hour after the funeral was over and thanked us for respecting the privacy of the mourners and waiting until they were gone before shooting. And there are signs outside that warn against any kind of photography during mass.
  • Go early. The earlier you go, the fewer people will be there to wander through your shots. And with a good sunrise, the front of the mission building would likely glow in that early morning light.
  • Go everywhere you can. There are lots of public areas. Explore them.
  • Leave behind a donation — or buy a candle in memory of a loved one. Entrance to the mission is free, but it’s certainly worth your support.

Two Kinds of Road Trips

Reflections on traveling long distance by car.

The TruckThis past week, I traveled with my sister as part of a convoy of vehicles moving her from New Jersey to Florida. The other vehicles included my dad in a Budget rental truck (see photo) containing the contents of my sister’s recently sold condo and my dad’s wife in an SUV. We buzzed down I-95 at highway speed, stopping only for food, fuel, and bladder demands.

If you’ve ever driven I-95 — or most freeways, for that matter — you know how mind-numbingly boring the trip can be. You’re moving at 55 to 75 miles per hour down a corridor that’s often straighter than an arrow shaft. Although there are occasional scenic vistas, they’re usually ruined by the tractor-trailer trucks you’re passing (or passing you). The main points of interest are the billboards and the variety of fast food joints and hotel chains at exits. The only excitement comes when some jackass cuts you off or something falls off the trailer in front of you.

The benefit of the interstate highway system is speed, of course. If there’s no construction or accidents or rush-hour traffic in a major metropolitan area, you can zip right along to your destination. We travelled almost exactly 1,000 miles over a day and a half. My dad routinely makes this drive to/from farther south without an overnight stop. It’s a lot of driving, though. And it just isn’t fun.

Each year, I drive from the Phoenix area to Central Washington State and back towing a travel trailer. It’s about 1,200 miles each way. Although Google Maps tries to put me on freeways for the entire trip, I don’t go that way. Instead, I take the back roads that criss-cross the western states. Last year, I was mainly on Route 93. This year, I was mainly on Route 95. These are long two-lane, so-called “blue highways” that pass through small western towns and cities. Along the way, you can get a feel for the landscape and the way folks live. There’s seldom any traffic and the speed limit is often as high as 65 mph so you can move from place to place at a reasonable pace. You can stop just about anywhere along the way and although your choices for meals and fuel and hotels might be limited, they’re not just the same chain establishments you’ll see along the freeway. It’s a whole different way to travel, a whole different experience.

What I like about the blue highways is the opportunities to stop at interesting spots along the way. Instead of pulling into a McDonald’s for lunch, I might stop in a parking area with a scenic view and have a picnic lunch there. Instead of staying overnight at a Super 8 motel adjacent to a truck stop or parking my camper in a Walmart parking lot, I might roll into a state park and camp alongside a creek. If there’s a historic site or roadside attraction, I can easily pull over to take some time there and enjoy it. I can change my route at any intersection. Best of all, I set the pace.

Back in 2005, I conducted what I like to call my “midlife crisis road trip.” I hopped into my little red Honda S2000 with some luggage and credit cards and hit the road for 16 days. I traveled almost every day, getting as far away from Arizona as Mt. St. Helens in Washington, western Montana, and Yellowstone National Park. I had a general idea of where I wanted to go, but no reservations and no need to be anywhere on any day. I slept in motels, hotels, rustic cabins, and even a yurt. I ate all kinds of meals, from crappy fast food and terrible coffee at drive-thru joints to fine dining at the foot of Mt. Shasta. I made side trips daily, visited parks, and talked to lots of strangers. I put more than 5,000 miles on my car, got two oil changes on the road, and even replaced the rear tires after wearing them out. (Z-rated tires just don’t last very long.) I had a great time — better than most vacations — and I’d do it again in a heartbeat.

While I realize that this week’s trip wasn’t for pleasure — the goal was to get my sister, her car, and her belongings from New Jersey to Florida in the minimum amount of time — it certainly did highlight the differences between my usual kind of road trip and motoring down the interstate between points A and B.

And it reminded me why I prefer the blue highways when enjoying the trip is more important than getting to the destination.

Book on Expedia, Get Stuck in a Middle Seat

Using Expedia may save a few bucks, but it lowers your status to one step above baggage.

Just a quick whine — and a warning for people booking flights with services such as Expedia.

I booked a round trip flight more than 10 days ago. One leg was a non-stop on Continental. The other was a flight with a plane change on American.

Although Expedia allowed me to see the available seats on my Continental flight, it would not allow me to choose one. Each time I tried, it ignored my selection and said I had to get my seat when I checked in.

This evening, I checked in. Still no seat assignment.

I called the airline. Although there had been at least 10 window seats available when I booked the flight and as recently as four days ago, I was offered a choice between two middle seats. And that’s what I’m stuck with: a middle seat.

Crap.

Airline travel already sucks. Who the hell wants to be stuck on a plane for 4-1/2 hours in a middle seat? Not me.

Lesson learned: Don’t book on Expedia. Don’t buy a ticket unless you can get your seat assignment when booking.