Aviation Weather 1.2.5

A Dashboard widget for pilots.

I’ve used this widget in the past and really like it. It uses your Internet connection to retrieve official TAF and METAR information for airports you enter into its interface.

From Aviation Weather 1.2.5 on Dashboard widgets:

About Aviation Weather Get current weather conditions as well as weather forecasts with the “Aviation Weather” dashboard widget. The widget shows weather data (METAR and TAF) which is used by pilots for their flight preparations. ”Aviation Weather” lets you choose any airport weather stations from its built-in database by either name or ICAO (4-letter) code. Data will be shown in its original format or translated into easy understandable texts. You can define up to 4 preset stations.

The preset feature is handy. Just program in the four airports you visit most and getting the weather at your destination is as quick as two clicks. Highly recommended for pilots.

Sunrise & Sunset in iCal

Must-have data — at least for me.

It may sound strange to folks who live in the world of alarm clocks and wrist watches, but my life’s calendar is managed by the sun. I wake early — before sunrise this time of year — and I sometimes can’t do things until after the sun has come up. As a pilot, I also need to know when the sun will rise and set so I can schedule sunrise and sunset flights, night flights, and photo flights, all of which depend on the sun for timing.

Each year, I export the daily sunrise and sunset information from Time Palette, a shareware application that provides various almanac information, into a FileMaker Pro database I created, which turns the exported data into real dates and times. I then export the Sunrise and Sunset info as separate FileMaker Pro files. I import those into iCal Filter, which enables me to export them back out as iCal .ics files. I open those file to import the information into iCal, thus displaying sunrise and sunset times on my iCal calendar.

Although it seems like a lot of work, I only do it once a year and then I’m set for the entire year.

If you’re interested in the .ics files for your location, I could probably be charmed into whipping up the files for you in exchange for one of the items on my Amazon.com wish list. (I really like surprises.) I might even throw in the moonrise/moonset times; I’m working on adding them, too.

Flying to Sedona (again)

A helicopter flight that has become routine.

As I write this, 36% of the site visitors who have taken the time to vote in my Most Interesting Topics Poll (that’s 11 people so far; I’m hoping for continued growth in that vote count) have said that Flying is the most interesting topic on this site. So I decided to devote this morning’s blog session to a flying article.

(For those of you just tuning in for the first time, among the hats I wear is a commercial helicopter pilot hat. I operate a Single Pilot Part 135 helicopter tour and charter company out of Wickenburg, AZ — Flying M Air.)

I flew yesterday. I flew three passengers from Wickenburg to Sedona and back. The passengers were originally from Russia and now live in the U.K. They’re staying at the Flying E Ranch, one of Wickenburg’s remaining three guest ranches.

I can’t get excited about this flight. It was so routine. After all, by now I must have flown from Wickenburg to Sedona and back at least 50 times.

The only thing unusual about the flight yesterday was visibility. In Arizona, it’s clear and sunny almost every day. Not only can I usually see the Weaver Mountains about 15 miles to the north, but I can usually see them clearly — that means I can distinguish rocks and canyons and other features from 15 miles away. But yesterday was different. It was hazy, as if a thin gauze had been stretched across my eyes. As I drove to the airport at about 10:00, it was apparent why: there was moisture in the air. There was condensation on my Jeep and even a little frost down where the horses were munching their morning meal. Imagine that. Moisture.

My passengers arrived early, all bundled up for the 50°F temperatures we expected in Sedona. After giving them their preflight briefing and loading them on board, I started the helicopter and waited for it to warm up. A few minutes later, we were on our way, climbing to the northeast into hazy skies.

The air was smooth, the sights were the same as usual (except for the haze) and I pointed them out faithfully to my passengers. They didn’t talk much, which is always a danger with me. I wind up talking to fill the silence, telling them more about the area than I usually do. I had three passengers on board, so I had to make sure I pointed out things on both sides of the helicopter — normally, with just two on board, I put them on the same side of the helicopter so I only have to point out things on one side.

We crossed the Weaver Mountains not far from the hidden cabins I’d discovered years before. Then we followed the Hassayampa River up toward Prescott, crossing the Bradshaws. My passengers were thrilled by the sight of snow on the north side of the moutains. I was thrilled by the fact that the haze had cleared out and it was a nice, clear day up there.

As we got close to town, I reported in to the tower at Prescott Airport. I planned to follow Route 69 a bit and then head toward the pass atop Mingus Mountain. This would have me cutting as much as one mile into Prescott’s airspace. (I normally go around it so I don’t have to talk to the tower, but our heavy weight had our airspeed a bit slower than usual and I wanted to save a few minutes of time.) We were over Prescott Valley when the tower pointed out a Baron about 400 feet above us, crossing in front of us. I descended about 500 feet — I was high because of all the mountains I’d have to cross — to stay out of his way. Then the tower cut me loose and I climbed up and over Mingus Mountain, reaching my highest elevation of the flight: about 8,000 feet.

West SedonaFrom there, I started a 1,000 fpm descent to the northwest, descending past the former ghost town of Jerome. I told my passengers about the first time I’d been there nearly 20 years ago when only a handful of people lived there. Now it was a booming tourist town, with art galleries and restaurants in the old buildings perched along its hillside. I showed them the open pit mine, then continued northwest to the red rocks. We did a red rocks tour on the way into Sedona, avoiding the flight path of the helicopter tour operators there, and landed at the airport.

Uneventful.

Of course, I’d been so concerned with getting my credit card terminal to work at the airport that I’d forgotten to bring a book or my laptop so I’d have something to do while my passengers went on their Jeep tour. Duh. After the Jeep picked them up, I walked over to Sedona’s restaurant for lunch. (I don’t think I can recommend the Chicken Alfredo with Broccoli; too thick and starchy, although the chicken was cooked nicely.) Then back to the terminal to wait.

I wound up renting a car from the car rental guy there. $20 for up to 3 hours (I think). I didn’t even have it two hours. I drove down off Airport Mesa and hit the New Frontiers grocery store at the bottom of the hill. It has a magnificent selection of cheese and a very knowledgeable cheese guy behind the counter. I tasted some cheeses and wound up buying them all. I also bough brussels sprouts on the stalk — something that’s simply not available in Wickenburg.Then into “uptown” Sedona to visit a bookstore (the Worm) which seemed to have fewer books than I remember. And coffee at the coffee shop across the street. Then back to the airport so I’d be there when my passengers returned.

I talked to everyone who worked at the airport. The car rental guy, the AZ Adventures helicopter tour guys, the FBO guys, and the Maverick helicopter tour guy. That kept me busy even after my passengers returned from the Jeep tour and went to have lunch at the airport restaurant. By 3:30 PM, they were back and it was time to go.

The return trip was almost as routine. The haze had moved in a bit and we were flying right into the sun. My hat was under my seat, so I had to shade my eyes with my hand once in a while. Instead of heading straight for the southern end of Mingus Mountain, we headed southeast to Oak Creek Village. My front seat passenger had his camera out and the red rocks were being illuminated by that gently filtered afternoon sun. The views out that side of the helicopter were great. I flew just past Oak Creek VIllage before turning to the southwest, back into the sun. The mountains rose as dark shapes silhouetted against the hazy light.

I didn’t have as much to say on the way back. Part of that was my intercom system, which was creating static again. (I have to fix that! It’s driving me nuts!) So I had the squelch set so it was less likely to make noise. My passengers weren’t talking anyway. They were just looking; the daughter, who was probably close to 18 years old, had her iPod on under her headset and probably wouldn’t have heard what we were saying anyway.

The farther south we flew, the worse the haze got. It was definitely brownish in color toward the Phoenix area — smog trapped in an inversion. At one point, we could clearly see a dark line in the sky that marked the inversion layer. Very unusual.

I flew them over Crown King, a tiny town in the Bradshaw Mountains. The main reason I go that way on the way back is that you can normally see Wickenburg Airport from the Crown King area — a distance of about 23 nautical miles. But not yesterday. The haze was so complete that if I didn’t have my GPS set to Wickenburg (or at least a heading in mind) I would have strayed off course. I simply couldn’t see that far away. Even Lake Pleasant was difficult to see from the air, although I did point it out for my passengers as we flew about 10 miles north of its northern edge.

We were over the Monte Cristo mine on Constellation Road when I was still trying to figure out exactly where we were. When I saw the mine shaft and buildings, I thought I’d stumbled upon a mine I’d never seen before. Then I recognized it and was surprised that we were so close to town. Less than 10 miles to the airport, according to my GPS. I could just about make out reflections downtown and the scars of the earth around the airport.

I flew over town and then headed out to Flying E to show them the ranch where they were staying from the air. (That’s something I do for people staying in our local hotels and guest ranches.) Then we landed by the fuel pumps at the airport. I cooled down and shut down.

Routine.

After a while, flying the same route over and over does become routine or — dare I say it? — boring. Sedona is a place of incredible beauty and the best way to appreciate its beauty is to see it from the air. Yet when you’ve seen it as many times as I have, the impact of all that beauty fades. That’s one of the things I talked to the FBO guys in Sedona about. They both agreed that when they’d first come to Sedona, they were amazed at its beauty. Now, living with it all around them every day, it simply isn’t a big deal.

I felt like that when I flew at the Grand Canyon, too. Don’t get me wrong — it never got so boring that I’d prefer to fly elsewhere. I just wished I had the freedom to alter my flight path for a slightly different view or a new way of seeing things.

And here in Wickenburg. The upstairs front windows of my home look out over the Weaver Mountains in the distance. When I first moved into the house, I thought it was a view I’d never grow tired of. But I did. Kind of. I’m not sure why.

I’d be interested in hearing from other pilots who fly in beautiful places and have somehow lost sight of that beauty because of routine. Use the Comments link.

The Most Difficult Task I Had Today

And I still can’t figure out why.

I spent about 2 hours today putting together an advertisement for Flying M Air‘s Southwest Circle Helicopter Adventure to be printed in a German publication.

I didn’t have to translate it. The advertising company sent me a translation of some text I’d sent them months ago. Trouble is, I couldn’t figure out what the text said. It took a while to find the original message asking for the translation. Oh. That’s what I wrote. Okay. Now at least I knew what I was advertising.

The Finished Ad at about 1/2 sizeTrouble was, the existing ad I wanted to modify for this job had the wrong photos. That means I had to get new photos. Then I couldn’t get the style of the new photos to match the photos I wanted to keep. So I had to find the original versions of all the photos and prepared them all over again from scratch. But I couldn’t remember out how I’d done it in the first place. So I had to figure it out.

Then I realized I rotated some of the images the wrong way and redid them. Then I had to re-rotate them again because I was right the first time. The drop-shadows completely baffled me. I couldn’t remember how I’d done them and I had to try doing it a few different ways before I got the desired results.

Then I had to squeeze in the text. Ever notice how it takes more, longer words to say something in German than in English?

Of course, I’m doing all this in Photoshop, which isn’t exactly the friendliest environment for laying out text and graphics elements. InDesign would have been better. But the old file was in Photoshop, so that’s what I thought I’d use to save time. Wrong!

Anyway, I’m done. You can see the ad here.

Now let’s just home I get some calls from Germans who speak English and want to take a 6-day helicopter excursion.

A Professional Pilot?

I’m not impressed.

Yesterday, my friend Ray flew me down to Mesa, AZ, in his airplane so I could pick up my helicopter, which was down there for its big annual inspection. While we were taxiing from Ray’s hangar to Runway 23 in Wickenburg, we heard the following exchange between two pilots on Wickenburg’s frequency:

Premier 1-2-3 (not the exact call sign; Premier is a small “corporate” jet): Wickenburg, this is Premier 1-2-3. Is there anyone there?

PanAm 5 (not the exact call sign; PanAm is a flight school based at Deer Valley Airport (DVT) that does a lot of practice landings at Wickenburg): This is PanAm 5 at Wickenburg.

Premier 1-2-3: Can you tell me the winds down there?

PanAm 5: The winds are shifting around a little, but they’re mostly out of the southwest at about 5 or 6 knots.

Premier 1-2-3: Oh, great. Thanks….So that means you’re using Runway 26 down there? Is that the runway number?

PanAm 5: It’s actually Runway 23.

Premier 1-2-3: Oh, thanks. We don’t have any approach charts or anything for Wickenburg so we’re kind of flying by the seat of our pants.

Yes, he really said that.

The radio went quiet for a few moments, then another pilot called to say he was 5 miles north, inbound for landing.

Premier 1-2-3: Premier 1-2-3 is about 3 miles south. We’ll be making left traffic for Runway 23.

Pan Am 5: Actually, it’s right traffic for Runway 23 at Wickenburg.

Premier 1-2-3: Okay. Thanks. Right traffic for Runway 23.

At this point, the FBO attendant came on the radio to provide wind and unofficial altimeter setting information. (It’s a good thing the altimeter setting is unofficial, since it’s off by nearly 100 feet.) She asked if the jet wanted fuel on landing and he told her he didn’t, that he was just dropping off some passengers.

We were holding short behind a PanAm plane when the jet came in, zipping past us. He was nearing the other end of the runway where the terminal was when the FBO woman came on again to ask if he knew where to park to discharge his passengers. He told her he’d been there before, then advised everyone that he was off the runway.

Ray and I had been discussing this jet pilot’s lack of professionalism while we were waiting. Both of us knew that one of a pilot’s responsibilities for a flight, as stated in Part 91 of the Federal Aviation Regulations (FAR’s). From Section 91.103, Preflight Action: “Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight.” Surely that must include runway numbers (which are determined by magnetic course headings) and traffic pattern information. This information is available on the Sectional Chart and in the Airport/Facilities Directory, both of which are required to be on board for commercial flights. They’re also available on the Web on various airport information Web sites and on the FAA’s Web site. Heck, I’m a helicopter pilot and I’m supposed to avoid fixed wing traffic when I land at airports, yet I usually know the runway numbers and traffic pattern information just so I can get an idea of where planes might be.

This guy simply hadn’t done his homework.

The PanAm plane in front of us took off. Ray rolled onto the runway. As the PanAm plane drifted to the north of the centerline (likely because of the wind), we took off and headed south.

I’ve since given the exchange a bit more thought. What if the Jet was arriving after 4 PM, when the FBO was closed, and the traffic pattern was empty. Where would he have gotten his information. He was only 5 miles out on his first call; would he have had time to look at his chart or A/FD? Or would he have assumed Runway 26 from memory, made a left traffic pattern low over the homes on the southeast and east sides of the airport, and adjusted his approach only when he realized he was on the wrong heading — 30° off? Approaching at a heading of 260 would have put him right over the homes on Broken Arrow Road — the homes of people already complaining about noise now that the runway is 1500 feet closer to their homes. Would his action have had a long-term impact on the airport?

The point here is, all pilots are responsible for gathering information about the flight — including the airport they intend to land at. This guy acted irresponsibly and was fortunate enough to have people on the ground that could provide him with the information he needed.

But as any pilot knows, you’re not always lucky. You need to do your homework before you get on board and start the engines.