Failure is Not an Option! SRE Lessons 50 Years after the Apollo 13 Flight
summary
An oxygen tank explosion cripples the service module, leaving no power or fuel; the Saturn V’s instrument unit automatically extends a stage burn to compensate for a failed engine at launch, and the lunar module becomes a lifeboat for three crew for five days. Engineers build a duct-tape CO2 adapter procedure from available parts, run IBM real‑time trajectories to retarget reentry, and later trace the root cause to a dropped tank, then add stainless sheathing, plumbing fixes and a third tank.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 2:53Apollo mission architecture
- 6:25Training and preparation
- 9:39Engineering observability
- 12:30Early flight challenges
- 17:07The Apollo 13 crisis
- 20:50Solving technical problems
- 27:01Post-mortem and root causes
- 33:53Business impact and lessons
- 37:24Conclusion
related talks
44mFailure Is Always An Option
55mSpace Shuttle
41mSoftware in Space: Lessons Every Developer Can Learn From
58mProgramming and Technology in Amateur Space Exploration
46mWhat the Soviet Space Program Taught Me About Digital Product Design
34mFrancois Martin: One Small Test for Man, One Giant Leap for Software Quality
29mMicroservices above the Cloud—Designing the International Space Station for Reliability
46mWhat the Soviet Space Program Taught Me About Digital Product Development