How a Tripod Can Make You a Better Photographer

My take.

Last month, my husband Mike and I went to a photography lecture at the Desert Botanical Gardens in Phoenix. (If you’re in the Phoenix area and have never been to the DBG, treat yourself; you won’t be disappointed.) The lecture was given by Arizona Highways magazine photo editor Jeff Kida and covered photographing wildflowers. (Jeff took the excellent portrait of me that you’ll find on this Web site and elsewhere; I wrote more about him and this photo in February.) We’d had a very wet winter and although the desert was greening up at the time, no one was sure whether we’d have a good wildflower season. So far, it’s turned out to be spectacular in certain parts of the Phoenix area, including Wickenburg, where I live.

Poppies and Desert Chicory

Desert chicory’s white flowers among golden poppies. (Click for a larger image.)

The lecture included a discussion of equipment and that equipment list included a tripod. I have a tripod — in fact, I’m ashamed to say that I have numerous tripods, far more than any one person should have. (I was always looking for the right tripod and have finally zeroed in on a good combination with a Manfrotto tripod and ball head.) And I agree that everyone serious photographer should have a tripod.

But then Jeff said something I’d never thought about. I wish I could remember his exact words. The gist was that using a tripod would automatically improve your photographs.

Whoa. This was something that interested me. Although I have all these darn tripods, I don’t use them very often. Maybe I should.

A Tripod Eliminates Camera Shake

I mostly use them for low-light situations when I absolutely must have a tripod. After all, a tripod’s main purpose is to hold the camera steady to take the shot. When used with a cable release (or similar device) or the camera’s built-in timer, motion from external sources should be eliminated. The final image should be clearer. But that was low light. Surely on a bright sunny day — just about every day here in Arizona — a tripod wouldn’t be necessary.

I also put a lot of faith in my camera’s VR (vibration reduction) lenses. I have two of them now and I can clearly hear the VR motor kicking in when I prepare to take a shot. Surely that would help keep my camera steady for each shot.

Poppy Blanket

A blanket of poppies and other wildflowers cover a hillside in the Sonoran desert near my home. (Click for a larger image.)

But since that lecture, I’ve been giving my photography a lot of thought. For the past two years, I’ve noticed a serious decline in the clarity of my photos. I was beginning to think it was the camera (a Nikon D80, now 3-1/2 years old) or my preferred lens (a Nikon 16mm-85mm zoom). Perhaps one or both of them needed adjustment or cleaning. I even went so far as to print out warranty repair authorizations for both of them in preparation for sending them back to Nikon for inspection, cleaning, and possible repair.

Perhaps the problem wasn’t my equipment. Perhaps it was me. Maybe I think I’m holding the camera steady for each shot or that there’s enough light to get the image, but maybe I’m moving the camera when I “snap” the photo by pressing down on the shutter release. Maybe I’m ruining my own photos. Or at least preventing them from being as good as they could be.

I decided to experiment by using my tripods and cable release more often. By ensuring that there’s no camera shake when images are being captured, I can eliminate camera shake as a cause of my problem. If the problem persists, I know it’s either bad focusing on my part or the camera’s. Since I don’t have the best vision, I trust my camera’s autofocus feature to get the focus right. So either I’m not telling the camera to focus on the right thing (my fault) or the camera can’t focus properly (the camera’s fault). Using a tripod would help me troubleshoot the source of the problem.

Using a Tripod Forces You to Slow Down and Compose Properly

Vulture Peak Poppies

This is my secret poppy place on the east side of Vulture Peak near Wickenburg, AZ. (Click for a larger image.)

I went on a photo shoot the other day out in the desert near my home. The poppies were blooming and I knew exactly where to find a lot of them. (Hint: Getting there requires a Jeep, ATV, or horse.) We took the Jeep out and found the poppies right where I expected them. We also found lupines, chicory, and a bunch of other flowers I didn’t even know existed.

The big problem with the site is that the flowers covered a steep hillside. Setting up a tripod was a royal pain in the butt. I admit that I cheated and took quite a few shots the lazy way. But then I remembered my mission and went through the bother of setting up my tripod and cable release and framing the photos. It slowed me down considerably. But I reminded myself that I wasn’t in a race. The best light was already gone for most of the day and the flowers weren’t going anywhere.

And that’s when I realized that using a tripod had yet another benefit: it forced me to slow down and pay close attention to what I was doing. It forced me to try harder to make every shot count. Because of all the extra time and effort required to make each photograph, I was motivated to put more effort into composition.

Could that be what Jeff meant?

The Jury is Still Out

The few photos on this post are among those I made that day. In general, I’m more pleased with the quality of the images. But I’m not done testing to see if the problem is with me or my camera. It’ll take more photo shoots with the tripod to convince me.

In the meantime, it’ll be interesting to see if I can shoot better photos just because I’m using a tripod.

Any thoughts on this? I’d really like to get some feedback from other photographers.

Walking the Fence

Part of ranch maintenance — even for our tiny “spread.”

About 10 years ago, interested in finding a summer place where we could go with our horses to escape the summer heat of the Phoenix area, we purchased 40 acres of ranch land in northern Arizona. Our lot at Howard Mesa Ranch is high desert land atop a mesa between Williams and Valle, AZ, about 40 miles south of the Grand Canyon.

Originally, we had high hopes of putting a vacation home up there. Our lot has 360° views that include Red Butte and the north rim of the Grand Canyon to the north, Mount Trumbull and its companion mountains on the Arizona strip to the west, Bill Williams Mountain to the south, and the snow-covered San Francisco Peaks to the east. We envisioned a 2-story home with a loft bedroom and big windows looking out over the views.

In preparation, we got a pair of water tanks, put in a septic system, and had the entire place fenced off with a 4-strand wire fence (smooth wire top and bottom, barbed wire in the middle per the CC&Rs). When we came up with our horses, they had 40 acres to wander and graze on.

But things change. We never built our vacation home. Maybe we will one day in the future, but I don’t know when that day will come. In the meantime, we camp out there on long weekends throughout the year. We’ve spent numerous July 4th weekends, several Christmases, and even one Thanksgiving at our off-the-grid retreat.

Like this weekend. We came up, mostly to check on the place and take care of some maintenance tasks. There’s a shed on the property that needs to be checked on regularly. And, of course, the fence.

Mike at Fence

Mike standing by the east side of our fence. That’s the San Francisco Peaks in the distance.

We walk the fence each time we’re up here. There’s over a mile of it, so it makes a nice walk. We’d put up the fence to keep our horses in, but now it worked primarily to keep the open range cattle out. I didn’t keep the elk out, though. They could — and did — jump the fence. Sometimes, their weight on that top strand of wire would shift the fence posts and bend the stays between them. Walking the fence meant repairing problems caused primarily by the elk.

In the old days, when we still had horses, Mike would ride the fence on horseback. He’d saddle up his horse and my horse would follow them. I’d busy myself with some other task, leaving them to get the job done without me. But with the horses gone, the walk would take longer. Jack the Dog wouldn’t be enough company for Mike. So I went along with them.

I carried a roll of wire, Mike carried the fencing tool. We walked the fence line, stopping occasionally to straighten stays, bang post deeper into the earth with a big rock, or tighten wires. It was easy to see where the elk had jumped the fence. It wasn’t just one or two elk, either. It was likely an entire herd. We didn’t mind the elk on our property. After all, they didn’t damage anything, like cows would.

Except the fence, of course.

Frost Heave

The southeast corner fence post. Over the years, frost heave has pushed the post up.

The fence had been professionally installed by a company based down near our Wickenburg home. They’d come up about a year after we’d brought the property and camped out until the job was done. The workers probably enjoyed being away from the low desert heat for a week or so. I wonder what they thought of the dark sky with its billions and billions of stars at night, or the coyotes that trot through the property as if they own it.

On the whole, the fence guys did a great job. Where they dropped the ball, however, is on the corners. Sure, they dug about three feet into the ground and secured those corner fence posts with concrete. But what they didn’t count on was frost heave, which is something you just don’t see down in the Phoenix area. Each winter, the ground freezes solid. As the soil freezes, it expands. It pushes up whatever it can to make room. Over the years, it has pushed the corner fence posts out of the ground. The fence is still sound, but the four corner posts no longer stand properly. One of these days, we’ll have to fix them.

Dead Animal

One of two partial skeletons we found while walking the fence.

Along the way, I caught sight of something odd about 200 feet from the fence. I went to investigate. It was the partial skeleton of a medium sized animal. Based on its size, skull, and the length of its neck, I think it may have been a young elk or perhaps a mule deer. There was no sign of antlers, so I don’t think it was an antelope. The bones had been picked clean, as you can see in this photo. The legs and entire hindquarters were missing. Mike found the lower jaw about 30 feet away. We think it may have been injured jumping the fence — or perhaps had starved when the ground was snow-covered — and the coyotes and birds had finished it off. Later, not far from the north side of the fence, we found another partial skeleton that also included the neck and part of the skull. Another unfortunate animal. I wonder how many others are within our 40 acres — or beyond it.

As we walked, it was clear that a lot of snow had laid upon the ground for a long time. The long, dried grasses were flattened out as if they’d borne the weight of deep, heavy snow for weeks on end. I could imagine animals jumping the fence, looking for food. I could imagine young or weak or injured ones dying, providing food for the carnivores and carrion eaters.

It took about 90 minutes to walk the fence and make the necessary repairs. By then, it had clouded up a bit and we were ready to take a break in the warmth of our camping shed. The job was done — until next time.

Another Lazy Job Seeker

It’s so easy for them these days, but they still take the lazy way out.

When I was getting ready to graduate college with a BBA in the early 1980s, my school provided some advice about how to look for a job and prepare for an interview. There were basically two different paths:

  • For a posted job opening, research the company to see whether it would be a good “fit.” The write a cover letter to send in with your resume that explained how you not only qualified for the position but could bring additional benefits to the company.
  • For a company you wanted to work for that didn’t have any posted job openings, research the company to learn more about it. Then write a cover letter to send in with your resume explaining what job or department or division interested you and how you could benefit the company.

There’s an underlying theme here: research the company. Learn about it. Understand what it did and how you might fit in. Even if the job you were looking for wasn’t available, the person on the receiving end of your cover letter and resume might realize that you’d done your homework and that might make enough of an impression to forward your resume to someone who was hiring people like you.

In those days, researching a company meant going to the library, tracking down annual reports, and combing through the periodicals Index to find articles about the company. It meant microfilm and microfiche. It mean spending an hour or two or even more to gather enough information to become informed about the company and sound that way if a phone call came. If you got an interview, it was back to the library to learn even more.

These days, we’re lucky — oh, so very lucky — to have the Internet. Researching a company is as easy as visiting its Web site or Googling its company name. All the information you could possibly want — and more! — is there, at your fingertips, in the comfort of your dorm room, living room, or a coffee shop.

Yet people still continue to take the lazy way out, sending generic e-mail messages to anyone they find online that might possibly have a job for them. In many cases, they don’t even bother to research the company and possibly job openings while they’re on that company’s Web site. Instead, they zero in on the Contact Us page or link and paste in their job request.

Here’s the most recent gem to cross my e-mail inbox:

I am seeking an internship position in the helicopter industry and was wondering if your company has any positions available in Phoenix. I am approaching my senior year in my Bachelor’s Degree in Aviation Administration and training for my Instrument and Commercial Rotorcraft Rating. I am very interested in doing an internship with your company so any information would be greatly appreciated.

Contact FormI should note here that this e-mail message was sent using a form on Flying M Air’s Web site, which is reproduced here as an image (reduced to fit). At the very top of the form is the parenthetical statement, “Note to Pilots: We are not hiring.” I added this when I got tired of getting e-mail messages very similar to the one quoted above. I figured I’d just tell them up front that no jobs were available so they wouldn’t waste their time — or mine. Evidently, reading the page the form was on was too much for this soon-to-be-college graduate.

I composed a response:

You’re “very interested in doing an internship” with my company? Really? What do you know about my company?

I’m sure you sent this same message out to every helicopter operator in the Phoenix area who you could contact. Copy and paste makes it pretty easy these days. Are you just as interested in working for all of them?

And tell me: when you used the contact form on our Web site, didn’t you see where it said “Note to Pilots: We are not hiring?” Did you think that somehow did not apply to you? Or did you skip over all the information about my company and that note right above the form so you could quickly fire out yet another generic request for work?

Did you ever think that maybe you should put a little more effort into your job hunt? That some people in the industry aren’t interested in hiring lazy people who can’t be bothered to learn about a company or read available information about job openings — or lack thereof?

Still interested in doing an internship for my company?

We’re not hiring.

I’ve said it before and I’ll say it again: I can be a real bitch. But I didn’t send this. Instead, my husband and I agreed on a better response:

Information about job availability can be found on our Web site.

This is actually a more evil response. It will require him to do some work:

  1. Figure out what our Web site is. I didn’t include a signature line with the URL and my e-mail domain name does not match that of my company.
  2. Search the site to find the one place — which is right above the form he used to contact me — where it says we’re not hiring.

And why shouldn’t he put a little effort into a job hunt? Won’t he be required to work if he gets a job?

Weight and Balance: A Primer for Passengers

Or why you shouldn’t lie to your pilot about your weight.

The other day, I booked a scenic flight for three passengers. At the time of the booking, I took the passenger names and weights — as I always do. Here’s what I was told:

Joe: 200 lbs
Bill: 200 lbs
Sally: 150 lbs

Why Pilots Ask for Weights

You might be wondering why a pilot needs the weight of passengers on a flight. After all, when you book a flight on United or US Airways, they don’t ask how much you weight. Why should a helicopter pilot care?

First of all, you should be aware that the airlines do care about weights. Weight information is required to calculate aircraft weight and balance (W&B) at takeoff and landing. The airlines are allowed, however, to use a blanket estimate for each person’s weight. This is set forth in an Advisory Circular issued by the FAA. (I found AC 120027C dated 1995, but I think this has been recently revised to account for heavier passengers; can’t find the new info, though.)

As a Part 135 operator of a small aircraft, I’m required to calculate an accurate weight and balance for each flight I conduct. The calculation is complex and customized to my aircraft. If I had to do it manually, it would take a good 15-20 minutes — with a calculator. Fortunately, I’ve created an Excel worksheet that does the number crunching and calculations for me, so the whole process, which I can do on my laptop, takes less than 5 minutes and spits out a required flight manifest and flight plan at the same time.

Weight and balance is important for safe flight. An aircraft is loaded out of CG (center of gravity) could fly erratically or have impaired controls. For example, if my helicopter is loaded too heavy up front, I might not be able to pull the cyclic back far enough to arrest forward movement in flight. That would make stopping and landing very difficult indeed.

Likewise, an aircraft loaded beyond maximum gross weight will not perform to specifications and could suffer structural damage. For example, if my helicopter is carrying a heavier load than what’s specified in my Pilot Operating Handbook (POH) and legally allowed, I might not be able to hover in ground effect or take off with a climb rate sufficient to avoid obstacles.

What a Weight and Balance Calculation Looks Like

A weight and balance calculation includes a bunch of very large numbers that are subsequently divided to make much smaller numbers. The result is plotted on a graph surrounded by boundaries often called an envelope. The goal is for the plotted points and the line often drawn between them to be within the envelope.

Here’s what the W&B calculations and envelopes look like for the charter flight with Joe’s party with 1/2 tanks of fuel on board:

Weight & Balance

Note that the plotted square and triangle are within the envelope for both Longitudinal and Lateral Weight and Balance. I can look at these two graphs and see that based on how I’ve seated the passengers, we’ll be a little heavy in front and on the pilot’s side. But the weight distribution is within the range my aircraft and its controls can handle.

It’s Not a Time to Be Vain

Weight and age are the two things people are least likely to be truthful about. As a pilot, I don’t care how old you are — I’ve flown with passengers aged 6 months up to 95 years — but I do care how much you weigh. Lying is not in your best interest at all.

But because I assume people will lie, I automatically add 10 pounds to each passenger’s stated weight when calculating my W&B. So here’s the revised W&B looks like for Joe’s party:

Weight and Balance

Now we’re starting to get closer to the limits. The weight is way up front now — almost at my limit. Still okay to fly, still legal. But I know that there’s very little wiggle room.

I know from experience that I can make the situation better by putting a lighter person up front. So maybe I’d put Sally in the seat beside me. Here’s what that looks like:

Weight and Balance

That looks a lot better. See how the two boxes in the top graph have shifted to the right? That means the weight is shifted aft. More balanced.

But I also know from experience that some men are unlikely to take a back seat to their wives. And I know that big guys don’t fit very well in the back seat of my helicopter. There was a pretty good chance that the guy who’d booked the flight and was paying for it would not sit in the back.

Getting it Wrong Can Make it Dangerous

Unfortunately, not everyone underestimates weight by just a pound or two. Sometimes, they’re very wrong. Consider Joe’s party. Turns out that they’d underestimated weights by at about 20 pounds per person. Now my W&B calculation looks like this:

Weight and Balance

Ouch. As you can see here, the two plotted points on the top graph are just outside the envelope for forward CG. That means that the aircraft would be too nose-heavy for safe flight.

How could I fix the problem? Again, I could shuffle around the passengers, putting the lightest one up front. I could take the contents of the pilot’s baggage compartment and shift it to the baggage compartment for one of the back seats — or leave it behind. Loading less fuel would not help — although it would reduce the weight of the aircraft (and the endurance time), it wouldn’t resolve the CG issue.

How do I know all this? By playing what-if with my Excel spreadsheet and observing the results.

Don’t Lie to Your Pilot

What bothers me sometimes is the flippant attitude some passengers have about weight. These people were a good example. The man who booked the flight didn’t take any of it seriously. He just threw some numbers at me to answer my question. I could tell when I laid eyes on them that they were heavier than reported. One passenger confirmed his weight at 220; the other passenger’s wife confirmed his weight at 220. 20 pounds is not a small error. It’s 10%.

In this case, it was the difference between a safe flight and a potentially unsafe one.

What they don’t realize is that underestimating or just plain lying about weights can make a flight dangerous. They can put their lives at risk by providing incorrect information. Is it worth it? Just so a stranger thinks you weigh less than you really do?

I don’t think so.

[Another] Predawn Flight to Scottsdale

Flying before the day begins.

I had an early flight in Scottsdale yesterday. Three passengers wanted a custom tour of the Phoenix area.

The man who booked it kept asking to do it earlier and earlier. First 8 AM. Then 7:30 AM. Then 7:00 AM. And then 6:30 AM. “We’ll meet you at 6:15 AM,” he finally said. “Will the pilot be ready to fly right away?”

I assured him that the pilot would be ready to fly within 10 minutes of meeting them. I didn’t mention that the pilot would be me. I hung up, glad he hadn’t shifted the flight another fifteen minutes earlier.

The helicopter was in Wickenburg. Although I’ve been storing it in Deer Valley for most of this season, I took the month of March off. There were a few reasons for it, including two trips (that were eventually postponed). So I had to fly the helicopter down to Scottsdale from Wickenburg — a 35-minute flight — before meeting the clients. When I calculated my departure time, I realized I’d have to leave my house by 5:00 AM to make it on time.

I set my alarm for 4:20 AM. I woke up at 3:30 AM. I showered and thoroughly enjoyed a cup of coffee with Alex the Bird and Jack the Dog. Then I packed up my laptop and flight manifest, shut off the lights, and stepped out to start my day.

It was dark outside. The moon had set, but I could see stars. That meant it was clear. The weather forecast looked as good as it usually does, so I wasn’t expecting any difficulties on the flight. The only questions were about the client: Had he lied about the weights of the passengers? Would he really give me 90 minutes of flight time, making the trip worthwhile? (He wasn’t paying for my ferry time, so a short flight would make the trip a loss.) Would he really be at the airport by 6:15?

I drove to the airport in my Ford truck, passing just a few cars and trucks along the way. The green-white-green-white sweep of the rotating beacon cut through the night as I pulled into the drive. I paused long enough to enter a combination on a keypad and wait while the metal gate rolled aside with a beep-beep-beep. Then I steered the truck down the asphalt drive, turned into the first row of hangars, made a broad U-turn, and parked in front of my hangar’s left door, with my headlights facing out. Even though the motion-sensor lights we’d installed over the hangar door went on, I’d need my truck’s headlights to see the combination on the padlock that secured the hangar. Once unlocked, I rolled the right door all the way open on the track and flicked on the lights. The big box hangar filled with light and the steady hum of the overhead fluorescents. I killed the lights on my truck before they killed the battery.

I’d done most of my preflight the afternoon before, after washing the helicopter and putting it away. I’d debated leaving it out overnight, but decided against it in case the client cancelled at the last minute. If I’d left it out, it would have saved me 15 minutes of time that morning. Instead, I had to use the ground handling equipment — a golf cart, a tow bar, and a set of ground handling wheels — to get the helicopter out onto the ramp. I backed the golf cart out of the hangar, towing the helicopter out nose first. Then I turned off the lights in the hangar and rolled the big door shut, securing it with the padlock again.

It was quiet and dark as I backed the cart out onto the ramp. Some of the overhead lights out on the ramp don’t work. It didn’t matter much to me — I wouldn’t park under any of them anyway. I needed room for my rotors to spin; it simply didn’t make sense to park next to a pole. But the ramp was too dark to see what I was doing. I had to turn on the golf cart’s headlights to unhook the tow bar. I’d never used them before and was rather surprised to find that they worked.

With the ground handling equipment out of the way, I climbed into the cockpit and went through my startup procedure. It took two tries to start the engine; not enough priming the first time for the cold. The engine roared to life and I flicked the appropriate switches to get the blades turning, battery charging, and radios working. I clearly heard the relatively high-pitched whine the engine — or something else back there — makes when it’s cold out. I knew from experience that the sound would go away as the engine warmed up. I turned on the navigation lights, which also illuminated the instruments. The green position light beneath my door reflected in the dusty surface of my side window.

I plugged my iPod into the intercom system. I’d listen to music on the way down.

It took a long time for the engine to warm up. While I waited, the guy in the hangar across from mine drove up and parked in front of his hangar. It was 5:30 in the morning — a full hour before sunrise — and the guy didn’t have a plane. What the hell was he doing there? He spent more time at the airport than most aircraft owners did, usually just sitting in his truck and talking on the phone. It creeped me out.

When the cylinder head temperature had sufficiently warmed, I did my mag check and needle split. I loosened the frictions and brought the engine and rotor RPM up to 102%. I was ready to go.

It was still very dark.

I made my radio call: “Wickenburg traffic, helicopter Six-Three-Zero-Mike-Lima is on the ramp, departing to the southeast.” I flicked on my landing lights, surprised, as always, by the sudden glow and the brightness of the dust particles swirling around in my downwash. Then I lifted into a hover, used the pedals to point the nose at the taxiway, and eased forward, climbing gently. When I reached the taxiway, now eight feet off the ground, I banked right and followed the pavement on a heading of 50°.

Wickenburg at Night

This photo by Jon Davison of us landing at Wickenburg at night gives you an idea of what the view from the cockpit looks like with the runway lights on.

The landing light shined down on the taxiway and out ahead of me as I gathered speed and altitude. I was about a quarter of the way down the taxiway when I realized I’d neglected to turn on the runway lights. I pressed the mic switch seven times. Nothing happened. I tried again, more slowly. The runway lights came to life: two strands of glistening white pearls turning to orange and then to red as they receded into the distance. The taxiway lights, glowed blue in a pair of light strings to their right beneath me. Beyond them was the dark void of empty desert and the greedy dreams of a failed real estate project. Aligning myself with the taxiway lights, I climbed out into the night. I flicked the switch to kill the landing lights.

The lights of Wickenburg spread out before me like a handful of gems cast into the desert by a giant. As I gained altitude to clear the invisible mountains just south of the town’s center, the distant glow of the Phoenix area came into view on the horizon, blocked here and there by the dark shapes of mountains that lay between me and the city beyond. I continued to climb. My goal would be to clear all those little mountains so I wouldn’t have to worry about hitting them in the dark.

I’ve flown the route between Wickenburg and Scottsdale many times. I even flew it at least one other time before dawn. But this time, I was tuned in to the darkness and silence of the night. I pressed the play switch on my iPod, letting some classic rock accompany the steady hum of my engine and the beat of my rotor blades. I climbed to 4,000 feet MSL — more than fifteen hundred feet over the desert below me — and leveled out. I was clear of all mountains between me and my destination.

Once away from Wickenburg, below me was only the darkness of the empty desert. With no moon, there was barely enough starlight to make out the meandering lines of dry washes and the occasional dirt road. Without visual landmarks, I realized I didn’t know where I was. Was that the Santo Dominguez Wash? Or one of the lesser washes in the area? And how about those lights to the left? Campers? Or that ranch off Constellation Road, viewed from a different angle? Only my GPS and the view of Phoenix’s lights spread out in the distance before me assured me that I was heading in the right direction.

The sky brightened ever so slightly as I glided southeast. The air was calm and smooth; my helicopter could have been a skiff floating on glassy water. I crossed over a well-defined dirt road that had to be Castle Hot Springs Road. Then I recognized the lights of the Quintero golf course and vehicles on Carefree Highway. The brightening sky reflected in Lake Pleasant, far to my left.

After ten minutes of flying over empty desert, I was returning to civilization: the northern reaches of Peoria.

I descended through 3500 feet, feeling ridiculously high above the ground as the glow from lights below me started reflecting in the inside of my cockpit bubble. I turned up the brightness on my instrument lights just a bit. Still descending, I flicked the radio to listen to the ATIS at Deer Valley. It was 5:50 AM and the tower was still closed. The automated weather observation system reported calm winds and an altimeter setting of 30.04. I adjusted my altimeter while listening to the recorded voice of the controller who’d closed the tower the night before. The tower would open at 6 AM. I wondered whether I’d reach the airport before then. I tuned the radio to the common traffic advisory frequency for Deer Valley, made a radio call with my position ten miles out, and continued on a course that would take me right over the top.

Lights at Night

The lights of the Phoenix area, at night. Photo by Jon Davison.

To the south, the brightness of lights on the ground intensified. The area was packed with new subdivisions, some completed before the housing bubble burst while others still had empty, weed-filled lots beneath their street lamps. It was a sharp contrast to the empty desert I’d been flying over for most of the trip. It amazed me that people wanted to live like that — packed like sardines into bulldozer-groomed lots — when there was so much beautiful desert, with rolling hills, cactus, and natural landscaping only a half mile away. The wide open spaces are what drew us to Wickenburg in 1997, but even that small town wasn’t immune to the greed of developers. Town planning restrictions were overturned on a case-by-case basis — often against voter’s wishes — for favored developers, resulting in smaller and smaller lots. Land zoned as horse property was rezoned to keep horses out and make lots too small to have them anyway. The retirees bought second homes in town to escape the cold of the midwest, doubling the population — for half the year, anyway. A friendly little western town turned into a retirement community right before our eyes. All of our young friends moved on to places like Colorado and New Mexico and California, leaving us with the retirees.

But I’m not ready to retire from life.

I descended to 2500 feet — a good 500 feet above where I normally flight during daylight hours — and leveled off. At five miles out, I made another call to Deer Valley traffic. I was now crossing into Deer Valley’s airspace; if the Tower had been occupied, I’d have to establish radio communication with the controller. I was the only one on the radio though — no one else spoke up. I crossed over the Central Arizona Project (CAP) canal where it meets the I-17 freeway. The sky, now quite bright, reflected in its smooth waters, drawing a bright line to the southeast.

Two miles from Deer Valley, I made another position call. No answer. I was close enough to see the tower; there was some light up there. Towers are normally kept dark so the controllers can see outside without bothersome reflections. A moment later, the airport’s two runways stretched out below me. I didn’t bother turning on the lights; I wasn’t landing and didn’t need them. But I could still see them quite clearly in the predawn light. It was about 5:58 AM and I expected the tower to open at any minute. I used the radio to announce that I was over the top and transitioning to Scottsdale. No answer. I glided on my way, descending down to 2300 feet.

Horizon

In this last shot by Jon Davison, you get an idea of how the horizon looks before dawn. (This shot was actually taken after sunset.)

Now the lights were bright below me as I flew over one subdivision after another. I crossed the Loop 101 freeway. Ahead of me, I could see the rotating beacon at Scottsdale Airport, about 12 miles away. The black bulk of the mountains on the horizon were well defined with sharp edges against the bright sky. Four Peaks was clearly identifiable by its four individual peaks.

I used my second radio to listen to Scottsdale’s ATIS while remaining tuned into Deer Valley. That airport was still closed, too. The automated weather system reported light winds and an altimeter setting just a few hundredths off from Deer Valley’s. The recorded controller’s voice warned of an unlighted 150-foot construction crane and advised that the tower would open at 6 AM. I flicked the recording off.

Now I was wondering about my client again, wondering whether he’d show up on time, whether he’d lied about his weight, whether he’d give me more than the 90 minutes of flight time he promised. I’d know soon enough.

The sound of a telephone dial tone came through the radio in three short bursts. Then the Deer Valley controller came on. He sounded tired and depressed, as if he’d just woken up to bad news, as he read the standard tower opening statement over the radio. It was long. I was still in his airspace, so I listened. At the end, he said, “Helicopter Zero-Mike-Lima, traffic ahead and to your left is a helicopter at twenty-five hundred feet. Frequency change approved.”

I’d already seen the helicopter flying west along the north side of the Loop 101. I replied: “Zero-Mike-Lima has that traffic in sight. Changing frequencies. Have a good day.”

I switched over to Scottsdale tower with the flick of a button. A female controller with a bright, bubbly voice was giving instructions to a jet preparing to take off.

I waited until she was finished and the pilot had replied, then made my call: “Scottsdale Tower, helicopter Six-Three-Zero-Mike-Lima is seven to the west off Deer Valley landing at the terminal.”

“Helicopter Zero-Mike-Lima, proceed inbound, report a half mile west.”

“Will report a half mile west, Zero-Mike-Lima.”

I continued inbound, crossing over Route 51. The sky was much brighter now; dawn was only 30 minutes off. I continued my descent to 2000 feet, roughly 500 feet over the ground. I listened to the tower talk with a female airplane pilot with the call sign “Traffic Watch” and wondered what kind of traffic she could watch from an airplane. Maybe I’d misheard them. She was using Runway 3.

Then I was less than a mile out and ready to start my final approach. I reported my position and was cleared to land on the ramp with the usual “use caution; ramp uncontrolled” and “remain west of the runway and taxiway at all times.” I repeated the “remain west” restriction as I steered to the south, descending. When I was abeam the approach end of runway 3, I swung northeast and lined up with the ramp, parallel to runway 3 and the taxiway beside it. I came in behind all the jets parked on the ramp and hover-taxied beyond them to transient parking for small airplanes. I set down at the end of the “Reserved” row and started my shutdown procedure.

In front of me, the terminal’s empty windows reflected the bright glow of the predawn sky, along with the flash of my helicopter’s strobe light. It wasn’t night anymore, but it wasn’t really day, either. It was that in-between time, the time of day when you put the secrets of the dark night behind you and prepare to embrace the day. It’s a special time, a time that’s always calm, always reflective. A time that makes me feel good to be alive.

I shut down and went inside the terminal. It was 6:10 AM.

And in case you’re wondering, the passengers did show up, they lied by a total of 50 pounds about their weights, and they flew with me for a full two hours.