Menu

Space shuttle Columbia: what could have been

Lee Hutchinson, who was a system administrator at Boeing at the time of the space shuttle Columbia disaster in 2003, looks back at that tumultuous time in a long but absolutely fascinating article for Ars Technica:

In August 2003, the Columbia Accident Investigation Board (CAIB) issued its final report. Behind the direct cause of the foam strike, the report leveled damning critiques at NASA’s pre- and post-launch decision-making, painting a picture of an agency dominated by milestone-obsessed middle management1. That focus on narrow, group-specific work and reporting, without a complementary focus on cross-department integration and communication2, contributed at least as much to the loss of the shuttle as did the foam impact. Those accusations held a faint echo of familiarity—many of them had been raised 17 years earlier by the Rogers Commission investigating Challenger’s destruction.

The report also asked a team at NASA to figure out what a rescue plan might have looked like:

To put the decisions made during the flight of STS-107 into perspective, the Board asked NASA to determine if there were options for the safe return of the STS-107 crew.

The rest of the article explains the possible rescue plan in detail. If you have any interest in science or space exploration this is a must-read.

I found the article particularly interesting because I had just finished reading my favorite novel of the year so far: The Martian by Andy Weir. The article echoed a lot of the concepts mentioned in the novel, which gave me a new appreciation for the story. I highly recommend this surprisingly plausible and funny book as well.


  1. See, this is a problem everywhere, not just in software development… 

  2. This too.