Skip to main content Accessibility help
×
Hostname: page-component-8448b6f56d-mp689 Total loading time: 0 Render date: 2024-04-18T02:37:22.462Z Has data issue: false hasContentIssue false

9 - Learning from crisis: NASA and the Challenger disaster

Published online by Cambridge University Press:  04 June 2010

Arjen Boin
Affiliation:
Stephenson Disaster Management and Public Administration Institute, Louisiana State University
Arjen Boin
Affiliation:
Louisiana State University
Allan McConnell
Affiliation:
University of Sydney
Paul 't Hart
Affiliation:
Australian National University, Canberra
Get access

Summary

Introduction: did NASA learn from the Challenger disaster?

On 1 February 2003, the Columbia Space Shuttle disintegrated during the final stages of its return flight to earth. The drama unfolded live on television: spectacular pictures of the doomed flight were punctuated by reactions of devastation and loss. It was in some ways a familiar drama. Seventeen years before (28 January 1986), Space Shuttle Challenger had exploded within 2 minutes of its launch. The Challenger disaster was etched in the minds of an entire generation of American schoolchildren, who watched the launch in their classes (the teacher Christa McAuliffe was on board to teach elementary school students from space).

Both disasters were studied by a presidential commission. Both commissions were scathingly critical of the National Aeronautics and Space Agency (NASA). The Rogers Commission, which studied the causes of the Challenger disaster, criticised the space organisation for not responding adequately to internal warnings about the impending disaster. The Columbia Accident Investigation Board (CAIB) found that little had changed since the Challenger disaster: ‘By the eve of the Columbia accident, institutional practices that were in effect at the time of the Challenger accident – such as inadequate concern over deviations, a silent safety programme, and schedule pressure – had returned to NASA’ (CAIB 2003: 101). The inescapable conclusion emerging from the CAIB report is that NASA failed to learn the obvious lessons flowing from the Challenger disaster, which caused the demise of Columbia (see, e.g. Vaughan 2005).

Type
Chapter
Information
Governing after Crisis
The Politics of Investigation, Accountability and Learning
, pp. 232 - 254
Publisher: Cambridge University Press
Print publication year: 2008

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

References

Adams, G., and Balfour, D. 2004. Unmasking administrative evil. 2nd edn. New York: Sharpe.Google Scholar
Argyris, C., and Schön, D. A. 1978. Organizational learning: a theory of action perspective. Amsterdam: Addison-Wesley.Google Scholar
Augustine Committee. 1990. Report of the advisory committee on the future of the U.S. Space Program. http://history.nasa.gov/augustine/racfup1.htm.
Blount, S., Waller, M. J. and Leroy, S. 2005. Coping with temporal uncertainty: when rigid, ambitious deadlines don't make sense. In Starbuck, W. and Farjoun, M. (eds.) Organization at the limit: lessons from the Columbia disaster. Oxford, UK: Blackwell, pp. 122–39.Google Scholar
Boin, A., and 't Hart, P. 2000. Institutional crises in policy sectors: an exploration of characteristics, conditions and consequences. In Wagenaar, H. (ed.) Government institutions: effects, changes and normative foundations. Dordrecht: Kluwer Press, pp. 9–31.CrossRefGoogle Scholar
Boin, A., Hart, 't P., Stern, E. K. and Sundelius, B. 2005. The politics of crisis management: public leadership under pressure. Cambridge, UK: Cambridge University Press.CrossRefGoogle Scholar
Brändström, A., Bynander, F. and Hart, 't P. 2004. Governing by looking back: historical analogies and crisis management. Public Administration 82(1):191–210.
Columbia Accident Investigation Board. 2003. Columbia accident investigation report. Burlington, Ontario: Apogee Books.
Farjoun, M. 2005. Organizational learning and action in the midst of safety drift: revisiting the space shuttle program's recent history. In Starbuck, W. and Farjoun, M. (eds.) Organization at the limit: lessons from the Columbia accident. Oxford, UK: Blackwell, pp. 60–80.Google Scholar
't Hart, P., and Boin, A. 2001. Between crisis and normalcy: the long shadow of post-crisis politics. In Rosenthal, U., Boin, A. and Comfort,, L. K. (eds.) Managing crises: threats, dilemmas, opportunities. Springfield, IL: Charles C. Thomas, pp. 28–46.Google Scholar
Johnson, S. B. 2002. The secret of Apollo: systems management in American and European space programs. Baltimore, MD: Johns Hopkins University Press.Google Scholar
Klerkx, G. 2004. Lost in space: the fall of NASA and the dream of a new space age. New York: Pantheon Books.Google Scholar
Kraft Commission. 1995. Report of the space shuttle management independent review team. www.fas.org/spp/kraft.htm.
Kranz., G. 2000. Failure is not an option: mission control from Mercury to Apollo 13 and beyond. New York: Simon & Schuster.Google Scholar
Logsdon, J. M. (moderator). 1999. Managing the moon program: lessons learned from project Apollo. Proceedings of an oral history workshop, conducted July 21, 1999. Monographs in Aerospace History, Number 14. Washington, DC: NASA.Google Scholar
McCurdy, H. E. 1993. Inside NASA: High technology and organizational change in the U.S. space program. Baltimore, MD: Johns Hopkins University Press.Google Scholar
McCurdy, H. E. 2001. Faster, better, cheaper: low-cost innovation in the U.S. space program. Baltimore, MD: Johns Hopkins University Press.Google Scholar
McDonald, H. 2005. Observations on the Columbia accident. In Starbuck, W., and Farjoun, M. (eds.) Organization at the limit: lessons from the Columbia disaster. Oxford, UK: Blackwell, pp. 336–46.Google Scholar
Murray, C., and Cox, C. B. 1989. Apollo: The race to the moon. New York: Simon and Schuster.Google Scholar
Perrow, C. 1994. The limits of safety: the enhancement of a theory of accidents. Journal of Contingencies and CrisisManagement 2(4):212–20.Google Scholar
Perrow, C. 1999. Normal accidents: living with high-risk technologies. Princeton, NJ: Princeton University Press.Google Scholar
Petroski, H. 1992. To engineer is human: the role of failure in successful design. New York: Vintage Books.Google Scholar
Presidential Commission on the Space Shuttle Challenger Accident. 1986. Report to the president by the presidential commission on the space shuttle Challenger accident. Washington, DC: Government Printing Office.
Rosenthal, U., Boin, A. and Bos, C. J. 2001. Shifting identities: the reconstructive mode of the Bijlmer plane crash. In Rosenthal, U., Boin, A. and Comfort, L. K. (eds.) Managing crises: threats, dilemmas, opportunities. Springfield, IL: Charles C. Thomas, pp. 200–215.Google Scholar
Sagan, S. D. 1993. The limits of safety: organizations, accidents, and nuclear weapons. Princeton, NJ: Princeton University Press.Google Scholar
Space Shuttle Independent Assessment Team (SIAT). 2000. Report to associate administrator. Washington, DC: NASA.
Starbuck, W., and Farjoun, M. (eds.) 2005. Organization at the limit: lessons from the Columbia accident. Oxford, UK: Blackwell.Google Scholar
Stern, E. K. 1997. Crisis and learning: a balance sheet. Journal of Contingencies and Crisis Management 5:69–86.CrossRefGoogle Scholar
Vaughan, D. 1996. The Challenger launch decision: risky technology, culture and deviance at NASA. Chicago: University of Chicago Press.Google Scholar
Vaughan, D. 2005. System effects: on slippery slopes, repeating negative patterns, and learning from mistakes? In Starbuck, W., and Farjoun, M. (eds.). Organization at the limit: lessons from the Columbia disaster. Oxford, UK: Blackwell, pp. 41–59.Google Scholar
Vaughan, D. 2006. NASA revisited: theory, analogy and public sociology. American Journal of Sociology 112(2): 353–393.CrossRefGoogle Scholar
Wolfe, T. 2005. The right stuff. New York: Black Dog and Leventhal Publishers.Google Scholar

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

Available formats
×