My Experiences (So Far) as a Self-Publisher

Making it up as I go along.

I’m in the middle of my third self-publishing project since October and, of the three projects, this is the most challenging. But what’s more interesting, perhaps, is what I’ve experienced and learned along the way.

Project One: The Test


This is actually the revised cover for this book; the first one was just too awful.

The first project, Making Movies: A Guide for Serious Amateurs, went remarkably well, despite the twists and turns along the way. From the start, I’d wanted to publish the book in both ebook and print formats. I built an InDesign CS3 template and used it to lay out the book. The text and illustrations were already written; they’d been published online and I got rights back for them. I struggled a bit to create the epub and Kindle mobi formats I needed to publish the ebooks on the iBookstore, Amazon.com, and BN.com, but with the help of an excellent Lynda.com course by Anne-Marie Concepcion, I succeeded.

I took a wrong turn with the print edition of that book. For some reason, I thought MagCloud would provide a good solution. MagCloud is a print on demand (POD) printer which also sells through its website. The quality of MagCloud’s work is excellent — they print in full color and the work really does look good. But they’re also terribly expensive. My 64-page book cost 20¢ per page to produce, making it far too costly for its size. It would not be possible to sell at a retail price that included a cut for me. And, frankly, the book that resulted didn’t have the kind of look and feel I wanted.

Clearly, I had to either give up on the idea of printing the book or find another POD printer.

So the first book, which was done as a sort of proof of concept to see if I could actually get a self-published title out there, was a limited success.

Finding a New POD Printer

I had already done some research on POD printers. I did not want to go with Amazon’s CreateSpace service because it was acting as a publisher instead of a printer.

There’s an important distinction there:

  • A publisher pays an author a royalty percentage on every book sold — even if the author buys the book.
  • A printer charges the publisher a fee for each book printed; the publisher earns money based on the difference between the book’s selling price and the amount it cost to print.

I felt that the CreateSpace percentage was not very generous; they were obviously set up for self-publishers who needed a lot of help with manuscript preparation. I didn’t need help. I’ve been preparing camera-ready book pages since my first Visual QuickStart Guide back in 1995.

CreateSpace also offered a free ISBN for those who didn’t have them. That’s a huge stumbling block for many self-publishers. Apparently the prices for ISBNs have risen to cash in on the self-publishing craze. Fortunately, I set up my publishing company, Flying M Productions (formerly Giles Road Press) back in 1994 and have all the ISBNs I need. So that didn’t attract me to CreateSpace, either.

Finally, I just wasn’t willing to jump into bed with Amazon.com — unless I had to.

Lulu wasn’t an option. Too costly and I’d heard rumors that Amazon.com wouldn’t sell Lulu books. (Wish I could remember where I’d heard that so I could link to source for you.)

I wanted a more professional-level POD printer, one that worked with real publishers and not the average self-publisher. What I wound up with was Lightning Source. This is a real printer, one that assumes you know what the hell you’re doing. Best of all, they’re part of Ingram, the company that catalogs books for resellers and libraries. Publishing with them would automatically get my book listed for sale in all retail outlets. They had a great deal of flexibility with book sizes and styles, from small to large, from softcover to hardcover, from black and white to full color.

And their prices were reasonable.

As a test, I redid my Making Movies book as a black and white title, redesigned the cover, and sent it in. The proof came back looking great and the book cost about 1/4 what it did through MagCloud. I was very happy. I’d found my POD printer.

The Logo

I had developed a series of books — Maria’s Guides — and I felt that I needed branding to go with it. So I started looking for a designer to come up with logo.

I already blogged about my Elance nightmare. My advice: don’t waste your time.

A friend of mine, learning of the problem I had with Elance, mentioned on a list she subscribes to that I was looking for a designer. I was contacted by one. I looked at his Web site. I liked what I saw. We chatted back and forth. We came up with a budget. I signed a contract. I paid him 1/3 up front. And then the trouble began.

He’d spend days laboring over what should be a simple task, like choosing a font I liked. I loaded up a bunch of fonts, picked about 10, and sent him samples in a PDF. He then proceeded to make sample “word marks” using four fonts I didn’t have. I liked only two of them; buying those fonts would have added another $150 to the project budget. I told him to pick one of my fonts and that I’d send him the typefaces to work with. He did so, grudgingly. Two weeks gone.

Then it was time to come up with the graphics to go with the word mark. No matter what I suggested, he pushed back, telling me I was wrong. I was getting pissed off very quickly. Finally, I emailed him, told him to keep my 1/3 deposit, and to forget the project. I never heard from him again. I’m beginning to think that’s how he earns a living: 1/3 of a job at a time.

Maria's Guides LogoIn the end, I took one of the fonts I liked and threw together a simple graphic word mark. It would have to do for now.

My Deal with the Devil

I guess it was around Christmas time that Amazon announced a new program for its customers. If you were an Amazon prime member and you owned a Kindle (not another device with the Kindle app), you could borrow ebooks for free.

This freaked out a lot of authors and publishers — at least at first. After all, if people could read our books for free, how would we sell books and make money?

It soon became clear that only a limited number of publishers would allow Amazon to use their titles this way. My publishers were not among those participating. Amazon had obviously used this well-publicized offer to get more people to buy Kindles.

Of course, when publishers made it clear that they weren’t interested because there wasn’t any money in it, Amazon stepped up to the plate and created the Kindle Direct Publishing (KDP) Select program. They’d put $500,000 in a special account each month. Publishers that put titles into the KDP Select program and allowed Amazon Prime members to borrow them for free would get a cut of this big pie based on the percentage of borrows their books got. So suppose there were 1000 borrows during the month and a publisher’s book accounted for 16 of them. The publisher would get 16/1000th of the $500,000. Of course, the numbers would be much bigger than that and the percentages much lower. But the potential for sales was there.

Of course, there was a catch: you’d have to give Amazon an exclusive on ebook sales. That means it could not be sold as an ebook anywhere else. And you’d have to commit for three full months.

A friend of mine who self-published the novel Soléa, decided to give this a try. Since my book sales weren’t exactly stupendous, I figured what the hell? I’ll try, too.

So I took the book off the iBookstore and BN.com. And I turned off the PDF ebook option on MagCloud. And I enrolled Making Movies into the KDP Select program.

That’s when things started getting weird on my sales reports. The report would show sales with an average selling price of 9¢ per copy. (I’d priced the book at $3.99.) When I contacted Amazon about that, they said it was due to price matching. I responded that (1) they had an exclusive on the title, so there was no one to match with and (2) the book had been (and would again be) available at the same price everywhere; no one discounted it. I’m still waiting for an update on that.

And then there was the positive sales with the negative royalties. WTF?

Oh, and about Amazon’s royalty percentage…the 70% is only for sales in 6 countries that, for some reason, have favored status. If you sell to any of the other countries in the world, your rate drops to 35%. I’m still trying to figure out how they can justify that.

Needless to say, when the 3 months is up, my book will be yanked out of KDP Select so I can get it back in the iBookstore and BN.com. And no, none of the other titles will ever be part of KDP Select.

Project Two: Fine-Tuning the Process


I fine-tuned the cover design to make the book name larger.

My second project, Sorting Excel Data: The Basics & Beyond, went more smoothly. Encouraged by what I’d read about InDesign CS5.5 and its ebook publishing features, I upgraded. I ported my InDesign template to the new version, fine-tuned it, and wrote a 114-page book with dozens of illustrations.

The writing took about four days and went very smoothly. I felt good about the template design, especially since I watched the CS5.5 version of Anne-Marie’s Lynda.com video and adjusted my template to take advantage of new features.

Once the InDesign file was done — including title page, copyright page, table of contents, and index, I was ready to publish. I budgeted two days: one for the print edition file submission and one for the ebook file submissions to Amazon.com (Kindle mobi), Apple iBookstore (iBooks epub), and BN.com (NOOK epub).

I had the print edition’s files, including the cover, submitted before noon. After lunch, I knocked off the three other submissions. It went that quickly.

The iBooks edition was available first. It appeared in the iBookstore less than 2 hours after submission. The Kindle version appeared the next day. The NOOK version appeared the day after that.

I got my proof from Lightning Source a week later. I approved it the same day.

At this point, I felt that I had the process down to a science. Only a bit more fine-tuning and it would be perfect.

Project Three: The Challenge

I knew as soon as I heard about iBooks Author that I wanted to do a book about it. I downloaded the software the same day. I learned it over the next two days.

I spoke to one of my publishers about doing a book. They were interested — at first. Then they got spooked about the EULA that everyone is whining about; I addressed some of those issues in this blog post. By the time they confirmed that they weren’t going to do a book about it, I was already 1/4 into my own book. You see, I never really thought we could come to an agreement on the book, so I’d started writing it for Maria’s Guides.

This is going to be a much longer book — likely 200 pages. I’m about 1/3 finished now. Although I’m trying to stick to the basics, I don’t want to disappoint readers by leaving important information out. So it will be quite a complete guide.

I’m thinking of changing the dimensions of the printed book to bring it more in line with trade paperback titles I’ve written in the past. This won’t affect my ebook editions, however. It won’t even delay them; they’ll go out first — likely sometime next week.

There will be a “multi-touch” version of the book available for iBooks readers. That’ll have a separate ISBN and likely more multimedia content. I’ll do that after the print edition goes to the printer.

Motivation…and Uncertainty

The real challenge, however, is motivation. As I’ve aged, I’ve developed a remarkably short attention span. I get bored with any project that takes more than a week or so to complete. Normally, there’s an editor out there, waiting for the next chapter. This time, there isn’t. It’s just me. I’m the author, the editor, and production person, and the publisher.

No one — except me — will know if I slack off and put this project aside.

But the worst part about it is the complete uncertainty. When I write for another publisher, I get an advance on royalties. If the book doesn’t sell well, they don’t take that advance away. In other words, I’m compensated for my work no matter what.

Not so with self-publishing. You only get paid when your work sells.

So I could be working my ass off on a book that no one will buy. A book I’ll never make money on.

It’s a terrible gamble, one that nags at me. In the back of my mind, I’m constantly wondering if I’m wasting my time.

But to help prevent me from slacking off, I’ve publicly announced the book — not only here but on a variety of other places. I’ve had potential readers contact me, telling me that they’re waiting. They’re motivating me to finish.

So I’ll finish.

And maybe in a few weeks or months, I’ll blog an update to this story to let everyone know what else I’ve learned.

Why Are We Still Powering Down All Electronic Devices on Airliners?

There’s no real reason for it.

A Twitter/Google+ friend of mine, Chris, linked to an article on the New York Times website today, “Fliers Still Must Turn Off Devices, but It’s Not Clear Why.” His comment on Google+ pretty much echoed my sentiments:

I do all my book reading on an iPad, and it’s annoying that I can’t read during the beginning and end of a flight, likely for no legitimate reason.

This blog post takes a logical look at the practice and the regulations behind it.

What the FAA Says

In most instances, when an airline flight crew tells you to turn off portable electronic devices — usually on takeoff and landing — they make a reference to FAA regulations. But exactly what are the regulations?

Fortunately, we can read them for ourselves. Indeed, the Times article links to the actual Federal Aviation Regulations (FAR) governing portable electronic devices on aircraft, 121.306. Here it is in its entirety:

121.306 Portable electronic devices.

(a) Except as provided in paragraph (b) of this section, no person may operate, nor may any operator or pilot in command of an aircraft allow the operation of, any portable electronic device on any U.S.-registered civil aircraft operating under this part.

(b) Paragraph (a) of this section does not apply to—

(1) Portable voice recorders;

(2) Hearing aids;

(3) Heart pacemakers;

(4) Electric shavers; or

(5) Any other portable electronic device that the part 119 certificate holder has determined will not cause interference with the navigation or communication system of the aircraft on which it is to be used.

(c) The determination required by paragraph (b)(5) of this section shall be made by that part 119 certificate holder operating the particular device to be used.

So what this is saying is that you can’t operate any portable electronic device that the aircraft operator — the airline, in this case — says you can’t. (Read carefully; a is the rule and b is the loophole.) You can, however, always operate portable voice recorders, hearing aids, heart pacemakers (good thing!), and electric shavers (?).

So is the FAA saying you can’t operate an iPad (or any other electronic device) on a flight? No. It’s the airline that says you can’t.

Interference with Navigation or Communication Systems

In reading this carefully, you might assume that the airline has determined that devices such as an iPad may cause interference with navigation or communication systems. After all, that’s the only reason the FAA offers them the authority to require these devices to be powered down.

But as the Times piece points out, a 2006 study by the Radio Technical Commission for Aeronautics found no evidence that these devices can or can’t interfere. Sounds to me like someone was avoiding responsibility for making a decision.

In the meantime, many portable electronic devices, including iPads, Kindles, and smart phones have “airplane mode” settings that prevent them from sending or receiving radio signals. If this is truly the case, it should be impossible for these devices to interfere with navigation or communication systems when in airplane mode. And if all you want to do with your device is read a downloaded book or play with an app that doesn’t require Internet access, there should be no reason why you couldn’t do so.

And can someone really make the argument that an electronic device in airplane mode emits more radio interference than a pacemaker or electric shaver?

And what about the airlines that now offer wi-fi connectivity during the flight? You can’t have your device in airplane mode to take advantage of that service. Surely that says something about the possibility of radio interference: there is none. Evidently, if you’re paying the airline to use their wi-fi, it’s okay.

What’s So Special about Takeoff and Landing?

Of course, since you are allowed to use these devices during the cruise portion of the flight, that begs the question: What’s so special about takeoff and landing?

As a pilot, I can assure you that the pilot’s workload is heavier during the takeoff and landing portions of the flight. There’s more precise flying involved as well as more communication with air traffic control (ATC) and a greater need to watch out for and avoid other aircraft.

But in an airliner, the pilots are locked in the cockpit up front, with very little possibility of distractions from the plane full of seat-belted passengers behind them — even if some of them are busy reading the latest suspense thriller or playing an intense game of Angry Birds.

Are the aircraft’s electronics working harder? I don’t think so.

Are they more susceptible to interference? I can’t see how they could be.

So unless I’m wrong on any of these points, I can’t see why the airlines claim that, for safety reasons, these devices need to be powered off during takeoff and landing.

It’s a Control Issue

I have my own theory on why airlines force you to power down your devices during takeoff and landing: They don’t want their flight attendants competing with electronic devices for your attention.

By telling you to stow all this stuff, there’s less of a chance of you missing an important announcement or instruction. Theoretically, if the aircraft encountered a problem and they needed to instruct passengers on what they should do, they might find it easier to get and keep your attention if you weren’t reading an ebook or listening to your iPod or playing Angry Birds. Theoretically. But there are two arguments against this, too:

  • You can get just as absorbed in a printed book (or maybe even that damn SkyMall catalog) as you could in an ebook.
  • If something were amiss, the actual flight/landing conditions and/or other screaming/praying/seatback-jumping passengers would likely get your attention.

But let’s face it: airlines want to boss you around. They want to make sure you follow their rules. So they play the “safety” card. They tell you their policies are for your safety. And they they throw around phrases like “FAA Regulations” to make it all seem like they’re just following someone else’s rules. But as we’ve seen, they have the authority to make the rule, so it all comes back to them.

And that’s the way they like it.

How Cell Phones Fit Into This Discussion

Cell phone use is a completely different issue. In the U.S., it isn’t the FAA that prohibits cell phone use on airborne aircraft — it’s the FCC. You can find the complete rule on that in FCC regulation 22.925, which states (in part):

22.925   Prohibition on airborne operation of cellular telephones.

Cellular telephones installed in or carried aboard airplanes, balloons or any other type of aircraft must not be operated while such aircraft are airborne (not touching the ground). When any aircraft leaves the ground, all cellular telephones on board that aircraft must be turned off.

There are reasons for this, but an analysis of whether or not they’re valid is beyond the scope of this discussion.

I just want to be able to read books on my iPad from the moment I settle into my airliner seat to the moment I leave it.

First Maria’s Guides Book Now Available

I’ve rolled the dice on this crazy gamble. Let’s see where it takes me.

I’ve owned the MariasGuides.com domain name for a while now with the idea of expanding into the short, inexpensive ebooks that I know readers are hungry for. Unfortunately, until recently, I’ve lacked the time and motivation to put it all together and make it happen.

All that changed this week. With a light flying schedule and no new book or video projects on the near horizon, it seemed like a good time to take the plunge and begin developing the Maria’s Guides series.

I began with a topic I first wrote about last year: creating watchable video. I took the original articles, revised and updated them, and laid them out in a format compatible with the MagCloud print-on-demand service. I also made sure my InDesign files were ready for ebook exporting in the EPUB format so I could easily prepare the book for various ebook formats: Kindle, iBooks, Nook, etc. For help with that, I consulted the excellent Lynda.com course, “InDesign CS4 to EPUB Kindle and iPad,” by Anne-Marie Concepcion. (I’m still on InDesign CS4; a CS5 title is also available.)

The printed version of the book is available today, along with a special MagCould iPad app version. Use the link below to check it out and see a free preview online. The Kindle and iBooks ebook versions should appear over the next week or so. I still need to work out how to get them online using the tools available to me. I suspect I’ll be watching a few more of Anne-Marie’s videos this afternoon.

Of course, the Maria’s Guides website needs a complete overhaul. It’s seriously outdate and has broken links. That’ll likely be next week’s big project. It’s a real pleasure working on stuff like that in my new Phoenix office; the Internet speeds here are about 15x what I suffered with in Wickenburg.

I’m also looking for suggestions for new Maria’s Guides titles. What would you like to see me write about? Use the comments feature for this post to share your suggestions. Keep in mind that they don’t need to be computer related.

Making Movies: A Guide for Serious Amateurs

By Maria Langer in Maria’s Guides

64 pages, published 21 OCT 2011

Tired of turning raw video footage into ho-hum productions that make people yawn? Or, worse yet, just putting raw video out there and hoping for the best? If so, this guide is for you. It clearly explains how to research, plan, shoot, assemble, edit, and fine-tune video productions for just about any purpose. Richly illustrated with stills from an example movie, it’ll get you on the right track to making movies that’ll inform, entertain, and impr…

Highest Duty

A book review.

Highest DutyLast night, I stayed up late to finish reading Highest Duty by US Airways pilot Chelsey B. “Sully” Sullenberger. Captain Sullenberger was the pilot in command of US Airways Flight 1549, which landed with no loss of life in the Hudson River on January 15, 2009.

I’d been wanting to read the book for a while but I kept putting it off. I wanted it to be my first purchased ebook experience. I was supposed to get a Nook for Christmas, but the idiots at Barnes & Noble were completely clueless about customer service and timely order fulfillment, so I canceled the order. I wound up with an iPad in April. After weighing the benefits and drawbacks of ebook reader software — iBooks, Kindle Reader, and B&N Reader — I decided to go with the Kindle software and ordered the Kindle edition of the book from Amazon.com. From what I hear from Twitter friends, the iPad makes a better “Kindle” than Amazon’s Kindle.

On Heroes

I’ve always been intrigued by Captain Sullenberger’s modesty and apparent reluctance to bask in the limelight of his extraordinary experience. People call him a hero but he [rightly] refuses that title. He quotes from a letter he received after his Hudson River landing: “I see a hero as electing to enter a dangerous situation for a higher purpose, and you were not given a choice.”

I agree with this definition of a hero. Captain Sullenberger did what he had to do and was fortunate enough to have the knowledge, experience, demeanor, and team to carry it off successfully. His love and respect of life — including, of course, his own — is what motivated him to do everything he could to succeed.

In many ways, that’s better than being a hero. When a terrible situation was thrust upon him by circumstances he could not change, he rose to the occasion and emerged victorious, saving the lives of 105 people. Along the way, he gave the rest of us hope — after the terrorist attacks of 9/11, in the midst of a serious economic recession, with wars going on in the Mideast — he showed us what people can accomplish when put to the test. He gave us the happy ending we all needed.

It Wasn’t a “Miracle”

Another thing that intrigued — and, I’ll admit, pleased — me about Captain Sullenberger was his failure to credit his success to the intervention of some supernatural being. I’m talking about God.

I can’t tell you how sick I am of seeing famous athletes and celebrities and just plain people thank God for something good happening to them. Scored a record number of goals in a basketball game? Thank God! Won a Grammy? Praise Jesus! Tornado took out the house next to yours but left yours unscathed? God was watching out for you!

It makes me sick. People don’t want to give themselves credit where credit is due. They work hard, they train, they practice, but they give God credit for getting the ball through the hoop. They learn music, they practice singing, they get a great producer who helps package their material, but they give Jesus credit for winning that Grammy. They don’t want to admit that luck has a place in our lives — good luck preserves one house while bad luck takes the one next door away. What of the people who lost the basketball game or the Grammy or their home? Did God simply not like them as much? And what about when these winners get their own dose of bad luck — injury, illness, scandal, death? Did God change his mind about them?

Captain Sullenberger, however, did not thank God or any other supernatural being for the positive outcome of his Hudson landing. At least I didn’t hear him do so in any article, interview, or elsewhere. I wanted to read the book to be sure that he didn’t thank God within its pages. He didn’t.

And that just makes me respect him even more.

The Story

The book mingles autobiographical material with events from the day of the landing. The autobiographical material was presented in a roughly chronological order, but did bounce around a lot with side stories, including references to the Hudson landing. I’m not sure that was the best approach, but it did keep me reading.

Captain Sullenberger is clearly a true pilot. He entered aviation because of his love of flying. From his start as a teen, he took aviation seriously, learning what he could to be a better, safer pilot. He understands the importance of knowing an aircraft’s systems inside and out. He understands the value of studying past accidents to prevent future ones. He also understands that all the things that happen in our lives define who we are and how we will react in a given situation.

Flight 1549 from Wikipedia

This iconic photo of US Airways Flight 1549 in the Hudson River by GregL originally uploaded to Flickr can be found on Wikipedia under a Creative Commons 2.0 license.

A detailed discussion of the events of January 15, 2009 begin about 60% through the book. The story is riveting. He combines his narrative of what happened with references to his past that he believes influenced him to make certain decisions. For example, his knowledge of research into why military pilots sometimes ejected too late is part of why he decided not to worry about saving the airplane by attempting an airport landing and instead concentrate on saving the people by landing in the river. (There’s a lot more to his decision than that; this is just part of what went into it.)

Throughout this part of the book are bits and pieces of the cockpit transcript, recorded by microphones during the flight — the so-called “black box” data. Even though I knew how it would end — don’t we all? — I found the details fascinating. It was a great example of teamwork between Captain Sullenberger and his first officer, Jeff Skiles. Later in the narrative, it was clear that the flight attendants were also part of the team, helping passengers off the plane in as orderly a manner as possible.

The aftermath of the experience also made interesting reading. Getting an inside look at the mail Captain Sullenberger received from people on the plane — as well as many people who had no direct connection to the flight or its passengers at all — revealed the psychology of people. I’m not the only one who appreciated the happy ending to that seemingly doomed flight.

The Soapbox

One of the complaints people have had about the book is the soapbox aspect. Captain Sullenberger believes that airline pilots are not treated as well as they should be by their employers considering the hours and responsibilities of their work. He believes that pay cuts and pension cuts are making it ever more difficult to attract and retain quality pilots who actually care about their work. He suggests that airline pilots are like bus drivers of the sky.

Although I don’t have intimate knowledge of the airline industry, as a professional pilot who has worked for a large tour operator, I know exactly what he means. Aviation employers don’t care how good a pilot is. As long as the pilot meets insurance requirements and can do the job, all that matters is how much that pilot costs. In my experience, many employers would rather hire a cheap, entry level pilot than a seasoned professional who costs more. They don’t see the benefit of the experience. They’re gambling, of course, on the equipment and circumstances of flight — when something goes wrong, will the entry level pilot have the experience and knowledge to bring the aircraft and passengers back safely?

In the airline industry, pilots are locked into their employers for seniority. If they leave one airline, they lose all seniority and start at the bottom at their new employer. This prevents experienced pilots from looking for better jobs. It stagnates the employee pool. And although Captain Sullenberger didn’t mention this, it prevents good ideas from one airline from migrating to another.

Captain Sullenberger does discuss how many airline employees have simply stopped caring about anything other than what’s in their job description. As budget cuts reduce non-essential staff, customer service suffers. Captain Sullenberger talks about his personal experiences going the “extra mile” to help passengers who can’t get the help they need from other airline employees. He talks about how most airline employees are simply tired of doing other people’s jobs. He doesn’t blame them — he hints that they’re underpaid for what they’re supposed to do — but he does decry the system that results in this poor attitude.

He also believes that budget cuts have the potential to reduce safety. A good example of this is the emergency procedures book that his first officer needed to consult on the loss of both engines. In the past, the book had numbered tabs that made it easier to find content. The airline, in a cost-cutting measure, had stopped including the tabs, making it necessary to thumb through the book and look at individual page headings to find content. In the slightly more than three minutes the cockpit crew had to land the plane without engines, every second was valuable. Yes, this flight had a happy ending — but could other flights be lost due to cost cutting measures like this? It certainly makes you wonder.

My feelings about Captain Sullenberger’s soapbox are mixed. I didn’t like reading his complaints, but, at the same time, I knew they were valid. And I know that his experience and the interviews, articles, and books that come from it are the perfect way to get the message out.

While Captain Sullenberger was careful not to criticize his airline, it’s clear that US Airways is just as bad as the others when it comes to matters of pilot compensation and cost-cutting. Perhaps his insight will help make the situation better?

Sadly, it probably won’t.

Thumbs Up

In all, I give the book two thumbs up. While it’s especially good reading for pilots and others interested in aviation, I also think it makes a good guide for young people who want to make something of their lives. And for the rest of the world, it’s a great look at one of the most amazing emergency landings we’ll likely ever see.