Mayday! Software Lessons From an Aviation Disaster
summary
A DC-8 spends 50 minutes in a low-altitude hold while crew fixates on a suspected gear problem, burning fuel until engines flame out and the aircraft crashes short of the runway; 181 people onboard mostly survive but 10 die. Investigators blame the captain’s failure of fuel-state monitoring and co‑crew’s failure to assert concerns, prompting mandatory crew resource management and assertiveness training from 1981 onward that deliberately flattens hierarchy and forces explicit cross‑checks.
AI-written summary · about
chapters (4)
- 0:00Introduction and background
- 4:54The case of flight 173
- 15:09Aviation lessons and CRM
- 20:04Situational awareness at work
related talks
53mMayday! Software lessons from aviation disasters
01h 00mLearning from Disaster
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
37mAir Crashes
01h 01mFly the Enterprise: Applying Aviation Lessons to DevOps Teams
43mHow to crash an airplane
56mLearning from Disaster
01h 01mSwiss cheese, teamwork and other things we should learn from the aviation industry