NASA Challenger
Featuring Roger Boisjoly, Diane Vaughan
The night before Challenger launched on January 28, 1986, engineers at Morton Thiokol begged NASA to delay. Forecast temperatures were colder than any prior launch, and the O-rings that sealed the rocket booster joints had a documented sensitivity to cold. Every previous flight that survived erosion had quietly become evidence that the risk was acceptable. The engineers were overruled. Seventy-three seconds after liftoff, the shuttle broke apart.
This case matters because the same pattern shows up in boardrooms, not just launch control. It sharpens the decision every operator eventually faces: what to do when the person closest to the danger raises an inconvenient objection and the room wants to move forward. The Rogers Commission found the warning signals had been present for years. How an organization filters out its own best information, and what it takes to keep that from happening to you, is the question the app leaves in your hands.
Frequently asked questions
What caused the NASA Challenger disaster?
The Challenger broke apart 73 seconds after liftoff on January 28, 1986, because the O-rings sealing the rocket booster joints failed in unusually cold temperatures. Engineers at Morton Thiokol had begged NASA to delay the launch, citing the O-rings' documented sensitivity to cold. They were overruled.
Who warned NASA not to launch Challenger?
Engineers at contractor Morton Thiokol, including Roger Boisjoly, warned NASA the night before launch that forecast temperatures were colder than any prior flight and the O-rings could fail. The Rogers Commission later found the warning signals had been present for years. Sociologist Diane Vaughan analyzed how the organization normalized the risk over time.
Why is Challenger an example of normalization of deviance and groupthink?
Every previous flight that survived O-ring erosion had quietly become evidence that the risk was acceptable, so the organization gradually treated a known danger as normal. When engineers raised an inconvenient objection, the room wanted to move forward and filtered out its own best information. That blend of normalization of deviance and groupthink drove the fatal decision.
What can operators learn from the Challenger disaster?
The lesson is to decide in advance how you will respond when the person closest to the danger raises an inconvenient objection and the rest of the room wants to proceed. Organizations filter out their own best information when they normalize risk, and keeping that from happening takes deliberate process. CaseBook turns this into a move you apply to your own company, with an AI coach that reads your answer.