Tag Archives: war

Heli-Shopping

Posted on by
Comment

The latest craze? I wish!

You’ve probably heard of heli-skiing, where they take you to the mountaintop in the ultimate “lift”: a helicopter. And heli-hiking, where they take you by helicopter to a remote trailhead and pick you up someplace equally remote. Well, thanks to one of my regular passengers, I’ve now started doing heli-shopping trips.

Here’s the deal.

Wickenburg has serious limitations on its shopping opportunities. Sure, there’s a great supermarket (which even has a Starbucks now, if you can imagine that) and there are a handful of shops down and around town for buying souvenirs, items for your home, and gifts. And even a little boutique.

But for hard-core shoppers, that might not be enough. For these people, it’s Scottsdale or bust.

Scottsdale, by car, is a good 90-minutes from Wickenburg. And that’s if you don’t hit any traffic and push the speed limit a bit. But by helicopter, it’s only 30 minutes away. The obvious benefit for the shopper: less time in the car, more time in the shops.

Last year, a couple who flies with me every time they come to stay at one of Wickenburg’s guest ranches, drove down to Scottsdale for a shopping day. The weather was awful and rainy and since people who live in Arizona don’t know how to drive on wet roads, the traffic was terrible. When they got to the shops, she got right down to business while he tried, in vain, to get a seat at one of the mall restaurants for lunch and a few hours of reading time. But the mall was packed and he couldn’t get a seat, so he wound up in their rental car in the covered parking garage, reading by the car’s dome light. Then, when she was finished shopping, they had another long, miserable drive back to Wickenburg.

This unhappy memory stuck with them. So this year, when they came to visit, they asked me if I could simply fly her down to Scottsdale, while he did something in Wickenburg that he enjoyed: a round of golf.

I’m never one to turn down a good charter, so yesterday at 10:30 AM, I was winding up Three-Niner-Lima with my eager passenger on board. We had an uneventful flight down to Scottsdale, landed, and locked up the helicopter on the ramp. Then, since I had only one passenger and my Scottsdale airport car is a two-seater, I drove her down to the Scottsdale Fashion Mall and let her loose by herself for four hours. Then I spent the time doing some errands, having a nice lunch, and doing a bit of shopping on my own.

I picked up my passenger at 3:30 and drove back up to Scottsdale Airport. I put the car away and we carried our bags back to the helicopter. I stowed everything under the seats and, a few minutes later, we were heading north for a slightly different route back to Wickenburg that would include an overflight of Lake Pleasant and Castle Hot Springs. We were back on the ramp at Wickenburg in time for cocktail hour at the ranch.

Mission accomplished. In style.

Heli-shopping isn’t for everyone. For one thing, it ain’t cheap, so potential heli-shoppers have to be really serious about their shopping time. And shoppers simply have to say no to that great deal on an end table at Restoration Hardware — or anything else that won’t fit in the helicopter.

But heli-shopping is more than just transportation to the shops awaiting your discretionary spending dollars. It’s a scenic flight from one world (the sleepy retirement community of Wickenburg) to another (the busy city of Scottsdale). The transition from town to open, empty desert to suburbs to city is something to see. And you won’t believe the kinds of things you can see from the air that are simply invisible from the road.

Heli-shopping takes shopping to new highs. Pun intended.

In-Flight “Emergency”…

Posted on by
3

…on a check ride.

There’s no better way to test a pilot on his or her knowledge of emergency procedures than to simulate an in-flight unusual situation. I hesitate to use the word emergency here, because what most check pilots simulate is not really a full emergency. It’s more of a situation that requires the pilot’s attention, knowledge of procedures, judgement, and action.

Real Throttle Chops are a Thing of the Past

Gone (or almost gone) are the days when helicopter flight instructors or examiners did “throttle chops.” A throttle chop is a simulated engine failure in which the instructor or examiner twists the throttle to idle suddenly during flight. The engine and rotor RPM needles split and the rotor RPM needle immediately starts to drop. The student or pilot in command is required to immediately enter an autorotation. The experts estimate that the pilot has about two seconds to react properly. Failure to react could lead to unrecoverable low rotor RPM, which is a very bad thing.

Flight instructors and examiners pretty much stopped doing real throttle chops — the kind with absolutely no warning to the student — when helicopters started crashing. It seemed that in some cases, the student pilot or pilot in command wouldn’t react fast enough and the instructor or examiner didn’t either. Or, in some rare cases, the sudden reduction in power caused the engine to hiccup and really fail. Now most instructors usually warn the student in advance. Some slowly reduce the throttle, which leads to an audible change in engine sound that warns the student — not to mention that he or she can usually feel the adjustment in his or her collective hand. Others do a throttle chop and enter the autorotation at the same time, not even giving the student a chance to react.

Robinson Helicopter issued several safety notices recommending against throttle chops (see SN-27 and SN-38). The company even amended its Pilot Operating Handbook so practice autorotations would be done with just a tiny needle split rather than a full throttle-to-idle setting. (Not a very good simulation of an engine failure, if you ask me.)

So What’s an Instructor/Examiner to Do?

One of the instructor/examiners I’ve worked with in the past was extremely fond of failing instruments or illuminating warning lights. This particular instructor, who works for Robinson Helicopter, has a whole collection of circuit breaker tricks that he uses on unsuspecting students. He’ll pull an engine tach circuit breaker so the engine tachometer drops to 0 during flight. No lights, just that dead gauge. He does it to see how long before the pilot notices and whether the pilot knows what do do about it. He’ll do the same for other gauges that are important but not vital to safe flight.

I took my commercial check ride with this particular instructor/examiner and he made me do a run-on landing with “failed” engine tachometer, rotor tachometer, and governor (switch the governor off to simulate). The trick was to make very small collective inputs and hope the mechanical correlator would keep the RPM within range; listening to the sound of the engine helped a tiny bit. But I still managed to make that low rotor RPM horn go off as we approached the runway surface. Evidently, I exercised enough finesse, because although he was disappointed that the horn had come on, he didn’t fail me for it. Personally, I like to see him do it perfectly.

(A side note here. What real-life situation would require you to land with all that stuff inoperable? The only thing I can think of is a complete electrical failure. But even then, I think there’s some trick in the Robinson wiring scheme that keeps the tachs alive. Just can’t remember what it might be right now. Guess I need to look it up.)

My Recent Mechanical Failure

I’ve taken 6 check rides since I started flying about 8 years ago: 1 private, 1 commercial, and 4 Part 135s. There’s usually some kind of simulated failure during a flight. So when the Aux Fuel light came on during my most recent check ride on Thursday, my first inclination was to ask the examiner, “Did you do that?”

“What?”

We were doing an instrument approach at Williams Gateway Airport and I think he was paying more attention to my altimeter (I was supposed to be at 1880 feet) than anything else.

“That light,” I replied.

He saw the light. “No,” he said.

I didn’t believe him and asked him again. He repeated that he wasn’t responsible.

“Is the circuit breaker out?” I asked.

He looked down at the bank of circuit breakers at the base of his seat. “Yes.”

“Okay, it’s not a big deal,” I said. “It’s the auxiliary fuel pump. It’s a redundant system and we don’t need it for flight. The book says land as soon as practical. Do you want to push the circuit breaker back in?”

“No.”

(For the record, I would have.)

“Well, how about if we land here and have Kelly look at it?” I suggested. Kelly is my helicopter mechanic. By some unbelievable stroke of luck, we were landing at the airport where he was based and it wasn’t 5 PM yet.

He agreed that would be a good idea and talked to the tower for me. He then directed me to parking. I set it down in one of the helicopter parking spaces that Silver State uses. He pushed the circuit breaker back in. It popped back out. He got out to track down Kelly while I cooled down the engine and shut down.

Long story short: Kelly pulled off the side panel and found that one of the bolts on top of the fuel pump was loose. He removed the pump, bench tested it, tightened up the bolts, wrote up a logbook entry on a sticker for me, and sent us on our way. The whole process took a little more than an hour. The pump sounded much better when I primed the engine for startup and the light didn’t come on again as we did some more maneuvers at Williams Gateway and flew back to Scottsdale.

I passed the check ride. I like to think that the failed fuel pump helped me. It showed that I knew enough about the procedure to stay calm and make the right decision about it. In a way, it was a real-life “emergency” during the flight. Again, I don’t like to use the word emergency because there was never really any danger — unless, of course, the engine-driven fuel pump went bad, too. Then we’d have a problem.

Postscript

I flew back from Scottsdale with no further fuel pump problems.

The next day, I did a 50-minute scenic flight with two passengers on board. We were about 45 minutes into the flight — less than 5 miles from the airport — when the darn light came back on. I finished the tour — which was basically on the way to the airport anyway — and landed. When I pushed in the circuit breaker, it popped right out again.

When my passengers were on their way, I visited Ed, my local mechanic. I asked him to take a look at the pump when he had a chance, then put the helicopter away in my hangar, which is just down the row from his. He called with the bad news a while later. The pump was seized. I’d have to get a new one. I called the factory at 2:30 PM (their time) and managed to get it on a UPS truck for overnight (Saturday) delivery to Wickenburg. With luck, it’ll arrive as planned (Saturday deliver is a very iffy thing in Wickenburg) and Ed will put it in. I’ll be flying again on Sunday.

Unfortunately, it’ll take the flights I have scheduled on Sunday, Tuesday, and Thursday just to pay for the new pump.

Being a Responsible Blogger

Posted on by
2

With regular readers comes responsibility.

This morning, I noted that the feed for this blog has exceeded 100 subscribers. The 100 mark is a milestone for any blogger, and it’s no different for me — even though I’ve been at it for some time now.

I’ve been blogging for over three years and my blog doesn’t exactly follow all of the “rules” of blogging. I’m talking about the “stick to one topic” rule and “blog multiple times a day” rule. People say rules are meant to be broken, but that’s not why I break these rules. I just blog the way I want to blog and don’t really pay attention to the rules.

My Original Blog as a Separate Entity

My blog started out as a separate entity from my personal Web site, a way to share whatever I was thinking about or doing with people who might be interested. It was a personal journal, slightly filtered for the public. It was a way for me to record my life so I’d have something to look back on in the distant future. I didn’t care if anyone read it and was often surprised when someone I knew commented about something I’d written in my blog.

Back in those days, my blog wasn’t something I worked hard at; the entries just came out of me, like one-sided conversations with friends. Perhaps it has something to do with my solitary work habits — many people gather around the “water cooler” at work to trade stories about their weekends or opinions about world affairs. There’s no water cooler in my office and no co-workers to chat with. My blog may have been my outlet for all these pent-up stories.

Blog + Site = ?

A little over a year ago, I combined my blog with my personal Web site. I did it to make my life a little easier. I’d already decided to use WordPress as my Web site building tool. Why not just make my personal blog part of the site?

My Web site has been around in one form or another since 1994. I built it to experiment with Web publishing and soon expanded it to provide a sort of online résumé and support for my books. Support for my books often meant additional tips and longer articles about some of the software I’ve written about. This is fresh content of interest to people who use that software, even if they don’t buy or read my corresponding books. Since writing this content is relatively easy for me, I have no problem offering it free to anyone who wants it (as long as they don’t steal it and pass it off as their own; see my © page).

One of the great things about blogging software is that it automatically displays the newest content on the Home page and archives older content by category and date. In the old days, I’d have to manually create new pages for every article I wanted to put on my Web site and then add links to them. It was time consuming, to say the least. Sometimes too time consuming to share even the quickest little tip with visitors. So I didn’t publish very many articles. But the time-consuming, hand-coding aspect of my site is gone, and it takes just minutes to put any content online, whether it’s a link to an interesting podcast I just listened to about iPod microphones or a multi-part series of articles explaining how to use WordPress as a content management system.

What’s odd about the merging of the two sites is that my personal blog entries now commingle on the Home page with my book support entries. So these 100+ subscribers are seeing (and possibly reading) all kinds of stuff coming out of my head. (Now that’s a scary thought!)

My Responsibility

As my blog/site audience grows, my responsibility to provide good content for readers also grows.

The way I see it, when only a half-dozen people read my blog regularly, it was okay to bore them with stories about my horse eating corn cob stuff out of the bottom of my bird’s cage or rants about the quality of “news” coverage. Now, with over 100 regular readers, I need to think more about what would interest my audience and concentrate on producing the articles they want to read. (You can help me by voting on this poll.)

And that’s when blogging becomes work. That isn’t necessarily a bad thing, but it does take more effort on my part.

And it may push me far from the original purpose of my blog: a journal of my life. That’s something to think about, too.

The Other Blogs

I just want to take a moment here to comment on some of the other blogs I’ve seen out there. The vast majority of them are a complete waste of bandwidth. Some exist to echo the sentiments of others and show very little original thought. Others are complete blather, written in a style that makes me mourn for the failure of our educational system. Like chat room comments. Ugh. I don’t see why people waste their time writing this crap and really can’t see why people waste their time reading it.

But there is a small percentage of blogs that provide good, informative, or at least interesting content, written in a way that’s easy to read and understand. Those are the blogs that serious bloggers should be reading and learning from. Those are the blogs we should try to emulate, not by simply copying or linking to content, but by adding our own original material to the blogoshere.

That’s my goal and my responsibility as a blogger. If you’re a blogger, is it yours, too?

Web Site vs. Blog

Posted on by
10

What’s the Difference?

Today I got a phone call from our local newspaper’s “business advocate” — the guy who writes stories about business. He was researching an article about blogging and figured that I was the most active blogger — if not the only blogger — in town, so I might be able to to provide some information about it. He wasn’t aware that I’d co-authored a book about WordPress blogging software (WordPress 2: Visual QuickStart Guide) in 2006 and he probably wasn’t aware that I wrote Putting Your Small Business on the Web back in 2000. He probably also doesn’t know that I’ve written four books about Web authoring software (various versions of PageMill, now defunct) and that I’ve been building and managing Web sites since 1994 (although I’m not crazy enough to do it for a living).

We stumbled a bit in our conversation. He referred to my Web site, wickenburg-az.com, as a blog. (The site has been around since 1999, predating the blogging phenomena by at least 3 to 4 years.) I responded that it wasn’t a blog, that it was a Web site built with blogging software. And then he asked me what the difference was.

I had to think about it. What is the difference between a Web site and a blog?

They’re very much alike.

Let’s take a look at the similarities.

  • Web sites and blogs are both published on the Web and can be read with any Web browser. This gives them the same basic look and feel and similar user experiences. Web sites built with blogging software can look and feel just like a blog, even if that’s not what they are intended to be.
  • They depend on good, useful content. Web site visitors and blog readers come to read content. If the content is good and meets their needs, they’ll be back for more. If the content sucks, they won’t.

But they are different.

Of course, I needed to explain how they were different — not how they were the same. The response I came up with centered around the purpose of visitors coming to to the site, but there are more differences.

  • Web site visitors come to a site to look for specific information. That information does not need to be new. It just needs to be what the visitor is looking for. For example, I visit the HP Web site when I need a new driver for one of my printers. I know it’ll be there and I don’t care if it’s been there for five years. People visit wickenburg-az.com to get basic information about Wickenburg: what it’s like, what to do there, etc. But blog readers visit or subscribe to blogs to get fresh information or insight on topics that are important to them. I read ProBlogger, for example, because it has timely articles that can help me understand how to be a better blogger. People visit aneclecticmind.com to read articles like this one about blogging, or other articles about flying, or even other articles about what it’s like to live in a place like Wickenburg — all from my point of view.
  • Blogs tend to be more opinion-based than Web sites. Sure, HP is going to tell you on their Web site that their printers are the best, but what would you expect? On my blog, I’ll tell you what I think about my HP printer and compare it to other printers I might own or have experience with. I’ll also tell you what I think of Apple Geniuses or local restaurants or life revolving around the Internet. (Although some locals might find this hard to believe, I keep most of my negative opinions of Wickenburg out of wickenburg-az.com. Most.) The opinion aspect makes blogs more personal than a Web site.
  • Blogs rely on fresh content. It’s commonly accepted that a blogger should post at least 3 to 5 new entries a week. Web sites, on the other hand, are more static and don’t require as much updating. Their visitors don’t expect it, either.

Does it matter?

Who knows? But it’s made me think about blogging a bit more than usual lately. And I’m sure it will lead to a few more articles here about what makes a blog a blog in the near future.

On Geniuses

Posted on by
6

Why I don’t Genius Bar hop and other comments regarding my recent hard disk problem.

One of my jobs as a blogger is to produce at least one blog entry a week. As you may have noticed if you follow this blog, it looks like I’ve been slacking off lately. Well, I just want to take a few moments to assert that looks may be deceiving.

Last week was a busy one for me. I finally got my computer back up and running after its second hard disk crash in a year. This crash was far more serious than the last and required the geniuses at the Apple Store to fix.

Now I know that lots of Mac pros laugh at the word “genius” when applied to the Apple Store’s tech support folks. And I do agree that it would be difficult to call any of them geniuses in the true sense of the word. (Think Einstein.) But if you were to compare their computer skills to the average Mac user’s, they could indeed be considered geniuses. They know a lot more about the current computer models than 95% of Mac users. Sadly, I fit into that 95% these days. I could tell you all kinds of things about fixing a Mac II cx or a PowerMac 7100/66 — and that’s because I used to teach a course about troubleshooting those computers running System 7. Nowadays, my troubleshooting capabilities are limited to what I need to know — like much of my other knowledge — and I don’t really need to know all the things the geniuses need to know to do their daily fix-it jobs.

So I’m not uncomfortable applying the word genius to many (but not all) of them. To me, some of them really are geniuses when it comes to diagnosing and fixing Mac problems.

I’ll also be the first to say that the capabilities of an Apple Store genius staff on any given day for any given store is hit or miss. It all depends on each staffer’s experience, knowledge, and interest in the topics he or she needs to know. I was at the Genius Bar in the Chandler, AZ store on Monday and the geniuses that day were pretty good. One of them was a super genius, the one who helped me was definitely above average, and the guy working the iPod slot was about average. (Let’s face it: it doesn’t take much skill to fix an iPod problem. Every iPod should come with a cheat sheet printed on back that explains how to reset it; that will resolve 95% of an iPod’s problems. The iPod guy probably resets a lot of iPods in a day. I’ve gotten so good at it that I can reset mine with one hand while flying my helicopter. Darn vibrations lock it up more often than I’d like to admit.)

I’ve had repeatedly bad luck at the Biltmore Apple Store in Phoenix, which is at least 30 miles closer to my house. The two times I tried to get assistance there, the lead Genius didn’t seem interested in looking deeply into my problem and didn’t seem to care whether it was resolved or not. On my fried motherboard problem, it seemed that she spent more time telling me how much it would cost to fix the problem than diagnosing what the problem was. This, coupled with her obvious lack of sympathy, made me doubt her diagnosis, so I had to go to another store (Chandler) to get a second opinion. I got a bad taste in my mouth (so to speak) from the experience. And that’s why I don’t go to the Biltmore store anymore.

Oddly enough, sympathy for my problem seems to be important to me. My main work computer or “production” machine (currently a Dual G5) is like a partner to me. It holds onto the projects I’m working on, it has the tools I need to get the job done as smoothly as possible. When it works right, we’re a team getting the job done. When it starts acting up, I get concerned. It’s not just a machine on the fritz. It’s a work partner feeling ill. What’s the problem? Can I fix it before it becomes critical? Is its motherboard about to go (again)? Or its hard disk? Will I lose data? Will I need to take it to the hospital (fix-it place) to get it working right again? How long will we be apart? And, of course, the selfish questions, like how long will I be unable to work?

The geniuses at the Chandler store are always sympathetic to my problem. They understand that my computer isn’t just a machine I use for e-mail and to surf the Web. They understand that its hard disk contains lots of important information — including books in progress — and the tools I need to get my work done. They understand that without my production computer, there’s very little real work I can do. And even though they don’t necessarily push any harder to complete a job for me than they do for anyone else, they make it seem as if my problem is one of the most important ones they’ll tackle that day. And they soothe me with reasonable reassurances that make it easier to face the 90-mile drive home and wait for their call.

This time around, the problem was a toasted hard disk. Personally, I believe it has something to do with my Firewire ports — it occurred while my iSight was plugged in and I was attempting to suck something off a portable Firewire hard drive. (My motherboard problem also manifested itself when working with multiple Firewire devices, including an iSight, so I’m very wary of using it these days.) They replaced the hard disk — which IS something I could have done myself if I really wanted to — and managed to get about 50% of the data off my old hard disk before it ceased to function at all. This cost me dearly, but the way I see it, I was paying for my own stupidity. If I’d had my entire Home folder backed up, recovery wouldn’t have been necessary at all and I could have saved the $150.

What hurts even more is that I’d written an article for Informit.com about backing up with Fetch before I had the problem and neglected to utilize my own instructions to protect myself.

The computer was done the next day and my husband, Mike, picked it up on his way home. It isn’t exactly on his way — he works about 15 miles north of there — but it was a lot more convenient for him than for me to make the 180-mile round trip drive. On Wednesday morning, I set about restoring the whole computer to it’s normal setup. I didn’t like the way the Apple folks had set up the machine — for some reason I was really bugged about my home folder being called maria (note the lowercase) rather than its usual mlanger (which I’ve used on all my computers for years). (Is that anal or what?) So I pulled off the recovered data, reformatted the hard disk, and spent the next two days installing software and updates. The updates were particularly painful now that I’m on the super-slow wireless Internet connection I whined about elsewhere in this blog. The 139 MB Mac OS X 10.4.8 combined updater took quite a while to suck off the Internet before I could install it.

Fortunately, I managed to pull e-mail messages, endo settings and contents, ecto contents, and some other stuff off my PowerBook. My iCal and Address book data was already set up to synchronize with .Mac, so getting all that data moved over was very easy. The only thing of real value that I lost was Chapter 6 of my Excel 2007 for Windows book, which I’d been working on for the second time. (The first revision went bad and I started from scratch. So today I look forward to starting my Chapter 6 revision for the third time. I knew it would be the book’s Chapter from Hell, but I couldn’t imagine how hellish it would be.)

By Friday, the computer was 90% back to its old self and I was working on it regularly instead of my laptop. So I was out of commission for two full weeks. I blame myself for that, too, letting the disk recovery software run as long as I did before finally bringing it to the geniuses.