nucleation

CASE-138: Challenger to Columbia: NASA corrected its launch decisions and its safety organization after 1986, and the Columbia board found in 2003 that related organizational failure mechanisms had recurred, while its lessons-learned system was little used in between

4 min read

Properties10
StatusActive
Version2
Standingdocumented
Kindspecimen
Tagsoperations-research, society-and-governance, epistemology
Linewill-organization
SupportsCLAIM-422 — A successful corrective act, an executable procedure and a maintained organizational capacity are three different things, so an organization can record a correction, even rewrite its rules, without the corrected capacity being maintained
IllustratesCLAIM-403 — A contribution's admission to an organization's inquiry, its recognition in apt terms, its credibility, its uptake into judgements, and its contributor's part in revising the standards of uptake are separable, each possible without the later ones, so an organization can widen access while every channel by which a less authoritative contribution could change the criteria of authority stays closed
Reported inLIT-734 — History As Cause: Columbia and Challenger, LIT-1378 — NASA: Better Mechanisms Needed for Sharing Lessons Learned, LIT-1393 — Report of the Presidential Commission on the Space Shuttle Challenger Accident, NOTE-1088 — GAO — NASA: better mechanisms needed for sharing lessons learned, NOTE-1090 — Rogers Commission — Report on the Space Shuttle Challenger accident, THEORY-140 — The Columbia Accident Investigation Board found that the institutional causes of the Challenger accident had not been fixed and recurred in Columbia's: in both, evidence that the design was not performing as expected was repeatedly reinterpreted as acceptable, each decision seeming correct in itself and each survived anomaly justifying the next flight, while budget and schedule pressure, consensus sign-off, a hierarchy that kept dissent from rising and a safety organization dependent on the program it oversaw sustained the pattern for twenty years and undid post-Challenger reforms
Cited as “grounds” byCLAIM-030 — An organized whole's operative intention is not the expectation of its members' intentions; it is produced by systemic mechanisms that can evolve apart from what the members intend

Graph View

The case

Before. O-ring erosion on the solid rocket boosters’ field joints had been seen on earlier flights and accepted flight by flight. On the eve of the launch of 28 January 1986, Morton Thiokol’s engineers recommended against launching in the cold; Thiokol’s management reversed the recommendation after NASA pushed back. Challenger broke apart 73 seconds after launch. The Rogers Commission (LIT-1393) traced the failure to that history (chapter 6, “An Accident Rooted in History”) and called the safety program “silent” (chapter 7).

After. NASA created a headquarters safety, reliability and quality assurance office in 1986 and a NASA Safety Reporting System in 1987. A25 called the first a “constitutional correction”, a change in who can object, beside the technical correction of the joint. In 2002 GAO (LIT-1378) found NASA’s lessons-learned system little used by its managers and no assurance that lessons were applied.

Columbia. Columbia broke up on re-entry on 1 February 2003. The Columbia Accident Investigation Board found that Challenger’s organizational causes had not been fixed. In the record’s reading of its chapter: evidence that the design was not performing as expected was reinterpreted as acceptable, each survived anomaly justified the next flight, and the safety organization depended on the program it oversaw. The record holds this as THEORY-140 (Proposed), from the board’s chapter (LIT-734). Diane Vaughan’s account, which named the normalization of deviance, is LIT-715 (Unavailable).

What it shows

  • A warning’s standing changes as it moves. A25: “The warning didn’t simply fail to enter the institution. Its evidential and practical standing changed as it passed through the institution.” That is CLAIM-403’s separation of admission, recognition, credibility, uptake and a part in revising the standards, in one night’s teleconference.
  • A correction recorded is not a capacity maintained. The rules and the office changed after 1986; the capacity they were for had eroded by 2003. A25: “Institutional learning is not complete when an organization changes its rules.” This is CLAIM-422’s case.
  • Success is evidence relative to the regime that scored it. Each survived flight was read as evidence the joint was acceptable. A37: “outcomes evaluated under particular conditions can be overgeneralized into claims about the competence of the organization itself” (CLAIM-416).

What it does not show

  • One unchanged cause. The board’s finding, as THEORY-140 reads it, is a recurrence of related organizational failure mechanisms over twenty years, not a single mechanism that sat unaltered between the two accidents. (Title narrowed the same day after a review the owner relayed.)
  • Why the correction decayed. THEORY-140 gives the board’s answer; this case does not test it.
  • The exchange’s details that were not checked. Its “2001 GAO review” and “January 2002 review” are taken to be one report, GAO-02-195. Its name for the 1986 office differs slightly from the office’s name at the time.

Note of 2026-10-22: the two reports, read

  • Where the launch decision is. The teleconference and the decision to launch are in the Rogers report’s chapter V, “The Contributing Cause of The Accident”; chapter VI is the history and chapter VII “The Silent Safety Program”, whose body says the safety staff “was never mentioned” (LIT-1393, p. 152).
  • The 1986 office and the 1987 reporting system are not in Rogers. The report only recommends “an Office of Safety, Reliability and Quality Assurance to be headed by an Associate administrator, reporting directly to the NASA Administrator” (p. 199). That NASA created it, and the Safety Reporting System, need another source.
  • GAO-02-195 is not about Challenger. It was prompted by the 1999 Mars failures and never discusses Challenger or the post-1986 reforms. What it supports is narrower than “little used”: NASA “monitors the system to determine the number of times it is accessed … but does not collect information on the number of times lessons are applied to a program or project” (LIT-1378, p. 21). The exchange’s “2001 GAO review” is probably the separate interim report GAO-01-1015R, which the 2002 report cites.
  • The normalization of deviance, first hand. THEORY-140, held from the Columbia board, has its Challenger half in the Rogers report: NASA and Thiokol “accepted escalating risk apparently because they ‘got away with it last time.’” (p. 148), with safety offices “under the supervision of the very organizations and activities whose efforts they are to check” (p. 161). The report could be added as a second source of THEORY-140.

Backlinks