Failsafes and Safety Fails
summary
A 2003 Broad Meadows EMU quietly rolls away while the driver changes ends, POTS telemetry shows initial movement after ~2 minutes and escape from platform, then minutes later the uncontrolled set reaches 75 km/h and hits train 8141 with eight minor injuries and four brief hospitalizations. The investigation by the Australian Transport Safety Bureau cites outdated procedures, inconsistent driver practice, lack of real‑time observability, and that key backups — POTS position of train system and the braking hierarchy — are failsafe dependent on active cab, leading to a mandate to use the park brake.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:48Setting the Scene
- 5:03Runaway Begins
- 11:32Failsafe Analysis
- 16:12Decision Making
- 22:54Lessons Learned
- 27:37Conclusion
related talks
31mFailsafes and Safety Fails: How to crash a train and other lessons for software engineers
53mMayday Mark 2! More Software Lessons From Aviation Disasters.
01h 01mFly the Enterprise: Applying Aviation Lessons to DevOps Teams
25mMayday! Software Lessons From an Aviation Disaster
53mMayday! Software lessons from aviation disasters
36mMove fast Build things… Safely!
36mIncident insights from NASA, NTSB, and the CDC
42mHow to not kill people