A Speck of Red

My helicopter, at the orchard.

Yesterday, after doing some cleanup in my camper, which is now parked at the orchard near my helicopter, I took a drive up the hillside behind the orchard. The road winds up and around, though thousands of acres of fruit trees. When I reached the tall antenna with its scary guy-wires, I spotted a trail from the main road. I parked the truck, grabbed my camera, and went for a tiny hike.

The goal was to shoot the orchard from the hillside behind it. I found a perfect spot and took this photo.

Orchard and Helicopter

CloseupIn the foreground, you can see the orchard’s upper reservoir. Farther down, beyond many cherry trees, is a smaller, algae-covered pond. There’s a parking area on the close side and you can see my trailer parked there. On the far side is a tiny, bright red speck. That’s my helicopter.

To be fair, my helicopter’s cockpit cover is on it, so it’s not fully exposed. I assume it would be a lot easier to see with the cover off. Before I relocate, I’ll pull the cover off, drive back up to this spot, and get a shot. Hopefully, it’ll be a crisper day and I’ll get up there while the light is still good.

In the close-up, you can see the taco truck that arrived not long after I left the orchard. The folks quit working at 10 AM (they start at 5 AM) because of excessive heat. It got up to 107°F in Wenatchee yesterday; I assume it got up to at least 100°F at the orchard some 1500 feet higher in elevation. The guys — mostly Mexican farm workers — were quitting for the day. The grower offers them soda pop and beer at day’s end; I assume they get lunch from the truck.

The helicopter is parked at the edge of the pond with one skid on the gently sloping embankment. A nice easy slope landing site. (And no, it won’t fall into the pond.) There’s a road between it and the shelter (dark reddish). They use the area for staging the cherries — loading them on a flatbed truck for transport up to the chillers and refrigerator truck in the main packing area. I’ll probably get some video footage of the operation later in the week for anyone who is interested. It’s amazing how much work goes into bringing cherries to market. Hard to imagine how anyone can make a profit with prices this year as low as $1/pound.

My Summer (So Far) in Cell Phone Photos, Part I: June 2009

A look at what I’ve been snapping.

I need to make one thing clear: I don’t do serious photography with the camera on my BlackBerry. Although the photos are far superior to the ones I made with my Treo, they’re still crap.

Instead, I use my phone’s camera to document the weird or funny or cool or scary things that I see when I’m out and about. The other day, when I finally synced my BlackBerry to my iMac again, nearly two months worth of photos were copied to iPhoto. I realized that they might make an interesting look back at my summer so far. So here they are, with descriptions.

June 18, 2009

Pilot GregThis is Greg, a fellow helicopter pilot. He’s posing with in a kid’s ride at the Wenatchee Valley Mall in East Wenatchee, WA. Greg’s not a small guy. I still can’t believe he crammed his body into that little ride.

Greg is my insurance check pilot. I just switched to a new insurance company and it requires that I take an annual check flight with an approved pilot every year. It doesn’t matter that I take an official Part 135 check ride with an FAA inspector each year. That’s not good enough. The inspector can take away my pilot certificate. Greg can tell my insurance company not to insure me.

So I met Greg and we went flying together. He put me through the drill and didn’t raise any complaints. He signed the paperwork. I bought him lunch.

June 20, 2009

Wild Horse Wind FarmThis is one of the windmills at the huge Wild Horse Wind Farm between Ellensburg and Vantage on the Vantage Highway in Washington State. It huge. There’s a visitor’s center up there that I really recommend for family outings. It’s also nice and cool up there.

I wrote extensively about my visit this year and included some videos in this blog post.

Logger BurgerOn the way back to where I was staying in Quincy, WA, I stopped off in Vantage at Blustery’s for a “Logger Burger.” You’re looking at a hamburger with bacon, cheese, ham, and fried egg. Breakfast, lunch, and dinner on one big bun!

June 23, 2009

SeafodIf you’re looking for seafod, you’ve come to the right place: Inna’s in Wenatchee, WA. (Personally, I prefer seafood.)

You’d think they’d proofread this giant menu in their window before putting it on display, but I guess not. Or maybe they did and spelling isn’t one of their strong suits. Whatever.

The food is supposed to be good there, but this menu error showed me that they’ve got no attention to detail. I haven’t eaten there yet.

Owl Soda FountainI did, however, treat myself to a hot fudge sundae at the Owl Soda Fountain across the street. They claim it’s an authentic soda fountain, but I think it looks too new and shiny. It certainly has that feel about it.

Am I the only person who remembers real soda fountains? I mentioned the one I grew up with in this very old blog post. (I still drink egg creams regularly; got the ingredients for one in my fridge right here at the hotel.)

June 29, 2009

Heli Base in ChelanMike came out for a visit at the end of June and we flew Zero-Mike-Lima (far right) up to Chelan. We parked in the “heli base” between the hangars there, with two other red R44s. The one in the middle belongs to my friend, Jim, who has a helicopter company a lot like mine based in Coeur d’ Alene, ID. The one on the left belongs to the company his roommate was flying for — I think they’re out of Spokane, WA.

Of course, we were all up here for cherry drying season. They got to live in a nice little house in a resort community. I got to live in a trailer on a golf course in the middle of farmland. (Do I sound jealous? What do you think?)

What I like about this shot is that it doesn’t show the Hughes 500 parked behind the helicopter on the far left. So I can pretend it was Robinson Parking Only. Or Red Helicopter Parking Only. Whatever.

I had my good camera with me and took a bunch of much better shots. This is the one I sent to TwitPic, though.

Heli BaseI also sent this one to TwitPic. I thought the sign was funny. When I sent it to TwitPic, someone commented on it, thinking my helicopter was the only one there. It was actually one of four, but happened to be the one parked behind the sign.

June 30, 2009

Applewood GrillI had my birthday lunch at the Applewood Grill in Wenatchee, WA. It’s in a wonderful old stone building near the railroad tracks. I’m sure it’s got all kinds of historic significance that I failed to look into while there. We sat outside on the patio in the shade. It was a nice day. The food wasn’t bad, either.

RV ShoppingLater, we went RV shopping in Wenatchee. We walked into one RV after another, going up in size and luxury with each step. This is the kind of 5th wheel model we’re considering as a trade-in for our sad little camper. This one was 32-feet long, had Corian countertops in the full kitchen, two La-Z-Boy recliners, a sofa bed, a table with four chairs, desk, a flat screen television, and king-sized bed, and a full bathroom. I could live in something like this.

Afterwards, we did a little Web surfing and I found the best designed and most informative Web site I’ve ever visited: KeystoneRV.com. Seriously: you should check this out. It answers all the questions you might have about these RVs except for the most important one: how much will it cost?

Mona Vie, anyone?I shot this one in a Wal-Mart parking lot mostly for the amusement of my skeptic friends. You either get it or you don’t. I’m not explaining the joke.

To be continued….

Best Comments for July 2009

Highlighting what other people have to say here.

I thought I’d try something new this month — a blog post that features excellent comments from blog readers. These are comments that really add something to the blog — or set me straight when I needed it.

You see, a blog is made good, in part, by the comments people share for the blog posts. Oddly, many folks tend to skip over the comments when they read a blog’s post. But in some cases, they’re missing out on some of the best content. My ever-popular post, “The Helicopter Job Market,” is a good example. It has over 100 comments that form an excellent discussion among helicopter pilots. Anyone who reads the post but skips the comments is losing out.

Anyway, I thought I’d highlight some of the best comments that have come in over the past month and include links to both the post and the comment. Here goes.

On July 10 and 11, Mark and Crispian Jago commented on my post, “Some Skeptic Resources on the Web.” Both of them provided links to other podcasts I wasn’t aware of, thus expanding my knowledge of these things.

On July 15, Jodene commented on my post, “Indian Eyes,” which included a video of a weird animated indian face atop a building in Wenatchee. She explained what indian was all about:

There used to be a Skookum apple packing shed where the Office Depot is today. The big Indian with the rotating eyes was their mega-mascot and it became a town mascot as well over the years. I know the shed existed into the late 70’s or early 80’s. I believe when the Skookum shed was torn down and replaced w/ the Office Depot a deal must have been made to keep the sign. (Kind of like the Citgo sign in Boston.)

Rene also provided some information about the Skookum apple packing plant.

On July 17, Jonathan commented on my post, “Please Don’t Drag Me Into Your Life.” The post was a rant and it was very cynical and a bit mean. Jonathan gently pointed out that the person I was criticizing may had a perfectly good excuse to be fully participating in Twitter when her mother might be on her deathbed. He took me down a notch, which I deserved, but he did it in a completely inoffensive way. In part:

I guess there’s an off chance her mother was asleep and this woman couldn’t sleep, but was still at the hospital. So to kill some time she’s surfing around the net maybe? I mean, we’ve all surfed aimlessly in the midnight and early hours right?

Maybe she just needed a relief from all the drama and she was using the net as an outlet….

On July 23, Fred B commented on the post, “Alfalfa Field.” His comment shared a wealth of information about alfalfa production and baling, including a direct reply to another commenter’s question. Here’s part of what he had to say:

Alfalfa is a very productive crop (often yielding 3-4 cuttings a season, and is rich in nutrients). The flip side is that it requires a lot of irrigation and removes a lot of nutrients from the soil. In order to give the soil a break, alfalfa is usually rotated every 5-6 years with a different crop (wheat, red clover, corn, various grasses, etc.), hence the observed switch from wheat to alfalfa. I imagine the owner will stick with the perennial alfalfa crop for a few years now before switching back to wheat….

These aren’t the only comments for this month. There were quite a few more. My post, “Fraud Alert: East Coast Mobile Style” continues to get many hits and comments every week. It’s interesting to read the experiences of the victims and how their credit card companies are (or aren’t) helping them.

I urge regular (and new) readers here to participate by posting comments on posts whenever they have something to add. I’m one person and I don’t know everything. It’s great to get additional information, feedback, and input from readers.

In addition, if you’re really interested in a topic, you can use the check box under your comment to subscribe to future comments. This doesn’t add you to any list I use for anything. It’s all handled internally by a WordPress plugin. There’s no spam. The only time you’ll get e-mail is when there’s a new comment. It’s easy to turn off, too; there are instructions in the e-mail you receive.

In the meantime, if you have any comments about this new feature here, please use the Comment link or form to let me know.

And thanks for helping me make my blog more interesting than I could make it on my own.

Writing in the 21st Century

A look back at the evolution of writing for publication.

Yesterday, my 72nd printed book went to the printer. For the first time ever, not a single sheet of paper was printed, mailed, or marked up during the writing and editing process for one of my books.

I’ve been a freelance writer since 1990. Most of my work — all of my books and 95% of my articles — has been about using computers. Yet for the first few years I wrote books about using computers, the manuscript files I created weren’t even used for the production of the book.

In the “Old Days”…

Back in the old days, my manuscripts had to be submitted in standard manuscript format. That means I wrote them in Microsoft Works (in the beginning) or Word using a plain font like Courier with double-spacing. What came out of my [$2,000] laser printer printer was a document that looked as if it had been typed on a typewriter by a very careful typist. Hundreds of pages. I was required to submit two printed copies of the manuscript to my editor.

In those days, Staples sold “manuscript boxes.” These were cardboard boxes designed to hold stacks of paper that were 8-1/2 x 11 inches. I’d print two copies of the manuscript, stack them one atop the other in this manuscript box, and mail them to my editor.

One time, in order to make a deadline, I sent the manuscript copies to Manhattan with my next door neighbor, who worked there. She then called a courier company to deliver the manuscript to the publisher’s offices in the Columbus Circle area.

In all honesty, I can’t remember how edits were handled. I don’t even recall getting any marked up copies of that early work. I think I got the galleys, though. They were printed (of course) and I wasn’t allowed to make many changes to them.

The Rise of E-Mail

Around the time of my fourth book (third solo book) in 1992 or 1993, e-mail was starting to get big. I still recall my shock and surprise when I sent an e-mail message to someone and got a response within an hour. Whoa!

That’s the book I started sending manuscript chapters via e-mail to my editor. The idea was that she’d review the chapters as they came in. This really saved my ass when my hard disk crashed and I lost everything on it. I was able to recover all those files from my editor and keep working. But when it came time to final submission, it had to be printed and mailed in: 2 copies, double-spaced.

Database Publishing with FileMaker Pro on the Web

This is one of the few books I wrote and laid out using FrameMaker. Its cross-referencing tools couldn’t be beat back in 1998.

When I started writing Visual QuickStart Guides for Peachpit Press in 1995, I also began doing layout. In the beginning, I used QuarkXPress, but I soon switched to PageMaker and finally to InDesign. I did a number of other books for Peachpit and for AP Professional (Claris Press, FileMaker Press) using FrameMaker, which I still think was the best layout tool out there. (InDesign is getting closer; thank heaven it finally added cross-referencing tools in CS4.)

For the early books, I’d create the chapter files, print them out, and mail them to my editor. Marked up copies would be FedExed back. I’d make the changes in the files. When the project was done, I’d send them a Zip disk or, later, burn a CD on my [$700] CD burner with all the files. That disk would travel by mail or FedEx on top of a stack of printed pages. In the beginning, they wanted 2 copies, but later they began using their own copier to make the copies they needed.

Word Files from Templates

Quicken 99: The Official Guide

This was the first book I wrote that made extensive use of Word templates.

Time went on. For the books I didn’t lay out, Microsoft Word became the standard. At first, I submitted files with the usual double-spaced, plain vanilla formatting. But some of my publishers got fancy and started sending templates with styles and macros and buttons built in. Although these files were always created on a Windows PC, they worked fine on my Mac. They usually came with detailed instructions for use; by applying the styles and submitting the files, my formatting would ease the task of getting it typeset on their system. Some of my publishers had terribly antiquated systems that required a lot of effort on the part of the production staff.

The use of Microsoft Word meant that my manuscript could go through a series of editors — copy, technical, and proofreader — with all edits clearly identified using the revision feature. I’d get edits back, review them, and either accept or reject them. Then I’d send them on to the next editor. The process was long and tedious, with lots of editing and a manuscript file that looked like a colorful mess of type. Often one editor’s changes would be changed back by another editor. Whatever.

I was required to send printed manuscript pages for most of the 1990s, but the files were transferred by e-mail, with a backup copy of all files on CD sent along with the printouts. I also got all galleys printed. That was often a lot of paper — hundreds of pages. In the mid 2000s, I started bringing the one-sided pages to my local copy shop to have them cut and padded; I’d use the back side of each page as scratch paper.

The Rise of PDFs

In the mid 2000s, I started seeing galleys as PDFs. I’d review them onscreen — no easy task when you have a smallish monitor and can’t read an entire page at once — then print out the pages with problems, mark them up, and send them into my editor. One of the reasons I bought a 20″ monitor a while back was to be able to proofread page by page.

Around the same time, Peachpit wanted to send me markups of my laid out book pages as PDFs. I resisted for quite a while because reviewing edits and making changes to the laid out page files with just one monitor was such a pain in the ass. My office now has a pair of 24″ monitors connected to one computer so I can review corrections on one screen while making corrections to manuscript pages on the other.

The End of Paper

200907212014.jpg

My most recent book was written and edited without an exchange of paper.

The book I finished yesterday (Mac OS X 10.6 Snow Leopard: Visual QuickStart Guide) was the first one that had absolutely no exchange of paper. I’d create book pages using InDesign and turn chapters into PDFs. I’d upload the PDFs and a zipped folder full of chapter files to Peachpit’s secure and private FTP server. The chapter files were my offsite backup — I did all of my work on this book from a camper or hotel and did not have a spare hard drive to back up to. My production and tech/copy editor would review the PDFs, mark them up with Acrobat — they use the full version, which I don’t have — and put them in a different folder on the FTP site. I’d download them, review them, and make manuscript page changes. Then I’d upload new PDFs to yet another folder and send fresh zipped files. My indexer got her own set of PDFs with accurate page numbers as we finalized pagination from one chapter to the next. When all editing was done, I updated the InDesign book file and its individual chapter files to finalize cross-references. (This is also the first Visual QuickStart Guide I’ve written that has cross-references to actual book pages rather than chapters.) I generated my table of contents and laid out the index when it arrived from my Indexer yesterday morning. Although I was still handling edits on Wednesday morning, by 10 AM yesterday (the next day), my editors at Peachpit had all the final files. By 5 PM the same day, the printer had those files.

I expect to see printed books within 3 weeks.

There are a lot of folks who see printed books as a terrible waste of paper. Although print publishing is definitely on the decline, there are many people — myself included — who prefer reference work in printed format. I don’t think print publishing will ever completely die.

I’m very pleased, however, that the production process didn’t add any more paper waste to landfills or recycling centers. I, for one, don’t need any more scratchpads.

Anyway, I thought some writers out there might be interested in the evolution of the writing/production process as seen by an “old timer” like me.

I’m just glad I never had to use a typewriter for my writing work. Using one in college was bad enough.

Not Ready for Solo?

This one is too absurd to pass up without comment.

I was going through the NTSB reports for helicopters today, looking for a specific accident in Arizona that hasn’t yet been listed on NTSB.gov. I did, however find this report that seems to indicate a training problem with a solo student pilot that has 64 hours of helicopter flight time:

According to the pilot, she departed Frederick Municipal Airport (FDK), Frederick, Maryland, about 0745, with an intended destination of Lancaster Airport (LNS), Lancaster, Pennsylvania. The pilot reported that she conducted the cruise portion of the flight at an altitude of 3,000 feet above mean sea level (msl), at an airspeed of approximately 110 knots. After she established communications with the LNS air traffic control tower, and was getting ready to begin her descent to the airport, the pilot noticed that the vertical speed indicator was indicating a descent of approximately 1,000 feet per minute, and that the airspeed was approximately 120 knots. The pilot “raised the collective” pitch control in an effort to reduce or stop the descent, but the helicopter did not respond as the pilot expected, and the descent continued. She determined that she would not be able to reach LNS, and selected a field suitable for a landing. The helicopter landed hard in a soybean field approximately 8 miles west-southwest of LNS. It remained upright, and the engine continued to run after touchdown, until the pilot shut it down using normal shutdown procedures.

The preliminary report goes on to say that when investigators tested the aircraft’s engine, they didn’t find anything wrong with it. It was up to date on all maintenance, the fuel samples were clear, and there was no evidence of a problem.

Is it me or is the problem as simple as what can be gleaned from the above-quoted paragraph? Let’s review:

  • The helicopter was descending at 1000 feet per minute, which is pretty quick, but not nearly as quick as an autorotation or a steep descent from altitude. (I commonly descend at at least 1500 feet per minute when coming off the Weaver Mountains (4500 feet) to Congress (3000 feet) toward Wickenburg (2400 feet).)
  • The helicopter’s airspeed was up to 120 knots from 110 knots. That’s fast, even for an R44. I normally cruise at 110 knots when alone; I have to push pretty hard to get it up to 120 knots without adding power or beginning a descent.
  • The pilot “raised the collective.” Helicopter Flying 101 says that when you pull pitch (raise collective) on a helicopter with a governor or a correlator (or both, as this helicopter has), you’re increasing power.

So the pilot is already zooming through the sky, but she adds power to stop the descent? Doesn’t she understand how the cyclic works? Pull it back to slow down. If you keep your power setting the same, you should also slow your descent rate.

Here’s what I think happened, based on the information provided in the preliminary report and a little research. The pilot was cruising at 3,000 feet. She was “getting ready to begin her descent” to an airport at an elevation of 403 — a required descent of 2600 feet. What she didn’t realize is that she had already begun the descent. Possibly with the airport in sight, she’d pushed the cyclic forward, perhaps to adjust the sight picture of the horizon before her. (This is something I recall doing more than once when I was a new pilot descending from altitude, so I can understand how she might do it, too.) The net result of a forward movement of the cyclic without a power change is to speed up and descend — which is exactly what happened. With a power setting of 18 to 20 inches of manifold pressure, she could easily get into this situation.

Rather than attempt to slow down by pulling the cyclic back, she elected to arrest descent by adding power. This would only make the problem worse if she didn’t add aft cyclic. It was probably a flare near the bottom — perhaps drilled into her by numerous practice autorotations — that slowed her down and enabled her to touch down without slamming any harder into the ground.

What should she have done? As soon as she realized she was going so fast and descending, she should have added aft cyclic. This should both slow her down and reduce her descent rate. It doesn’t matter how much power is available; if the rotors are not stalling, the helicopter will fly. Gentle aft cyclic should enable her to get a better idea of what the problem is — if there is indeed a problem.

But it’s hard to imagine a power problem if there’s no loss of RPM or yawing to the right — neither of which is mentioned as a symptom of the problem. And believe me, if a Robinson has low rotor RPM, you’ll know it — the damn horn starts blaring at 97% RPM; she would have had enough power to fly with RPM as low as 85% (or probably lower).

What do I take away from this? This solo student pilot was not prepared for her solo flight. She evidently did not understand how the controls work together to manage airspeed and climb or descent rates. (This may have something to do with her experience as an airplane pilot.) When she noticed the descent rate and high speed, she possibly panicked and did the first thing that came into her mind: raise the collective to stop the descent. But if she had been properly trained and knew what was going on, she would have reacted properly by simply pulling the cyclic back to slow down and reduce the descent rate.

As a result, a helicopter is destroyed, the NTSB is required to waste time and resources to investigate, and a student pilot, although lucky to be alive, has an accident on her record.