Fly the Enterprise: Applying Aviation Lessons to DevOps Teams
summary
QF32 suffers an uncontained engine failure when a mis‑drilled fuel stub leaks, turbine fragments shred a cable bundle and dozens of systems fault within four seconds; crew follow a 30-second throttle‑back checklist, declare pan‑pan, run diagnostics, and use five cockpit crew to delegate tasks and land an hour and a half later with 469 people safe. Investigation yields a 400+ page report, 40 faulty pipes found, design and software fixes (turbine overspeed protection, pipe wall increase), and clear lessons: pair checklists, pilot flying / pilot monitoring, and formal incident retrospectives.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:35Modern Aviation Safety
- 7:43Checklists
- 11:57Checklist structure
- 12:58Checklist example
- 15:43Checklists from normal events
- 18:11Captain vs First Officer
- 19:47The L1011 Incident
- 22:07Pilot and CoPilot
- 33:55Total CRM
- 36:32Fivestep assertive statement process
- 39:55Aviation incident investigation
- 41:03What do you investigate
- 43:38State of the systems
- 44:44Planning briefing
- 46:36Human factors
- 49:50Reasons
- 52:00Manual Fuel Balancing
- 53:23Fuel Leak
- 55:41Crash
- 57:13Safety Recommendations
related talks
25mMayday! Software Lessons From an Aviation Disaster
25mLessons from flying for engineering leadership
53mMayday! Software lessons from aviation disasters
01h 01mSwiss cheese, teamwork and other things we should learn from the aviation industry
01h 00mLearning from Disaster
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
32mEscalating complexity: DevOps learnings from Air France 447
42mHow to not kill people