JetBlue, Blogging, and Normal Accidents

By Paul Kedrosky · Monday, February 19, 2007 ·
Everyone is rightly complaining about how little ongoing information there has been from JetBlue about its troubles. To a perhaps naive way of thinking, it seems like a classic opportunity (one right out of Scoble/Israel's Naked Conversations text) to use a company blog to humanize things and keep people updated on their efforts to get people out of airplanes, get back on schedule, etc.

So, are they doing it? Nope. Instead JetBlue has this flight operations update page, but it only has the most recent bulletin, with no archive of how the company has dealt with things on an ongoing basis. At least as baffling is that JetBlue CEO David Neeleman has a blog/flightlog, but he hasn't updated it since February 1st.

--------------------

Turning to a related issue, most observers are struggling with the question of how a widely-forecast weather problem a week ago led to such problems back on February 14th for JetBlue, and has also led to so many JetBlue cancellations today (Monday). Explanations offered vary, but most are some variant on "the company grew too quick, was under-staffed, and its systems and people couldn't cope with all the manual reschedulings".

Okay, but I still find that tough to handle. Even when things are going well, running a busy airline like JetBlue is a logistical nightmare. You don't get to 11,000 employees and a host of paired cities running this stuff with five guys and a Commodore 64. Granted, this was a series of crazy exceptions to normal fare, but it's still puzzle how it got so bad and propagated so far forward in time.

While I don't have a full explanation either, the entire incident sent me back to Charles Perrow's classic book about disasters in complex systems, Normal Accidents. Here is Perrow from Chapter 5 on Aircraft and Airways:
There are some unique structural conditions in this industry that promote safety, and despite complexity and coupling, technological fixes can work in some areas. Yet we continue to have accidents because aircraft and the airways still remain complex and tightly coupled, but also because those in charge continue to push the system to its limits.
That idea that this was a random event caused by pushing a complex system to its limits strikes me as good an explanation as any. In other words, however, while it was JetBlue this time that was stuck to a New York runway and fell off the map, it was a system error, so next time it could be any airline.
1