The complexity of success and failure: the story of the Gimli Glider
summary
A detailed retelling of the Gimli Glider shows how a unit conversion in kg vs volume combined with a taped-out FQ channel and misleading gauges leads to taking on about 45% fuel, then gliding for 17 minutes to an abandoned airbase turned racetrack. Monitoring, redundancy, and documentation all fail to provide the needed context, but improvised use of a glider pilot’s forward slip plus hydraulic workarounds and quick decision making prevent a crash, no serious injuries occur, and the airliner flies for 25 more years.
AI-written summary · about
chapters (20)
- 0:00Introduction to the Gimli Glider
- 1:02Beyond the first story
- 1:44Fuel gauge troubles before flight
- 3:33Manual fuel calculations
- 5:48Handoff and miscommunication
- 7:57Redundancy and failover confusion
- 9:45Redundancy creating complexity
- 11:30Checklists and documentation limits
- 13:39Documentation cannot ensure safety
- 14:20Investigation and lost resolution
- 16:08Expertise saves the day
- 17:33Success and failure intertwined
- 19:18Glider pilot’s forward slip maneuver
- 21:31Backup plans fail
- 23:22Blame despite success
- 24:45Conflicting goals in landing
- 26:15Nose wheel and tire damage
- 27:38Landing with minimal damage
- 28:44Humans as the resilient part
- 29:07Q&A and wrap-up
related talks
01h 01mFly the Enterprise: Applying Aviation Lessons to DevOps Teams
25mMayday! Software Lessons From an Aviation Disaster
44mPlanning for & Handling Failures from Open Hardware, Aviation, to Production at Google
50mLearning in Production (or Why the Apollo 11 Landing Nearly Failed)
30mPilot your Project: Avoiding Anti-Patterns While Handling Incidents and Planning
48mDynamic Non-Events
32mEscalating complexity: DevOps learnings from Air France 447
27mExplosive overflow: Lessons from rocket science