Mayday Mark 2! More Software Lessons From Aviation Disasters.
summary
Aviation safety history and case studies show concrete software lessons: global fatal crashes peak at 230 in 1970 and fall to ~49 by the 2010s (about 1 death per 10 million passengers), thanks to changes like crew resource management cuts pilot-error crashes. Deep dives include Air France 447 stall due to iced pitot probes and automation limits on Airbus A330, a Boeing/Airbus automation split, and an operations story where RabbitMQ 1,000,000-message resync causes 8-minute outage illustrating redundancy creating surprising single points of failure.
AI-written summary · about
chapters (24)
- 0:00Introduction
- 1:13Talk overview
- 2:16Aviation history 1903-1950
- 4:00Plane crash causes 1950-2019
- 7:19Crew resource management
- 10:31Fly-by-wire technology
- 13:01Airbus vs Boeing automation
- 16:54Aviation and AI parallels
- 17:36Air France 447 case study
- 24:48Human interaction with systems
- 25:52RabbitMQ cluster failure
- 28:38Air France 447 breakdown
- 34:20Human-centric system design
- 35:44Cognitive load in UX
- 37:08Copa Airlines 2011 case study
- 39:53Consistency over correctness
- 40:14Assumption blindness B737
- 42:45Stress in aviation
- 43:50Passenger behavior Manchester
- 45:36Stress in software systems
- 46:40Alert fatigue in systems
- 47:21Checklist compliance Delta
- 49:10De Havilland Comet myth
- 50:35Takeaways and closing remarks
related talks
51mMayday Mark 2! More Software Lessons From Aviation Disasters.
53mMayday! Software lessons from aviation disasters
56mLearning from Disaster
25mMayday! Software Lessons From an Aviation Disaster
42mHow to not kill people
26mThe top IT failures in history
30mPilot your Project: Avoiding Anti-Patterns While Handling Incidents and Planning
36mIncident insights from NASA, NTSB, and the CDC