Why you've never been in a plane crash
Commercial aviation’s remarkable safety record is widely attributed to a “just” or blameless culture that prioritizes systemic learning over punishing individuals when accidents and near-misses occur. Commenters explore how formalized, non-punitive investigations, rich incident reporting and a focus on institutional responsibility have reduced crashes, contrasting this with sectors like software, healthcare, nuclear, and road transport where blame, secrecy, or weak regulation still dominate. Many argue that adopting aviation-style safety practices—especially rigorous postmortems, protection for honest mistakes, and attention to near misses—could significantly improve outcomes in those other high‑risk domains.
Aviation safety culture & “just culture”
- Commenters highlight aviation’s formalized “blameless” or “just” culture: focus on understanding what happened and fixing systems, not punishing individuals acting in good faith.
- This is framed as key to why commercial flying is so safe and why information about errors actually surfaces.
- Several people tie this to RCAs in other high‑risk domains (nuclear, maritime, chemical plants) and to the Swiss cheese model of layered defenses.
Blame vs accountability
- Strong discussion on nuance:
- “Blameless” does not mean no one ever bears responsibility, especially for rule violations, malice, or gross negligence.
- It does mean separating fact‑finding from punishment so that investigations are honest and system‑focused.
- MCAS, the Titanic, and the UK Post Office scandal are used as examples where organizational and regulatory failures matter more than individual scapegoats.
Institutional and systemic factors
- Debate about whether the PATCO mass firing damaged US ATC institutional knowledge and indirectly raised accident risk; some are skeptical given the time gap, others emphasize long‑term erosion of rigor.
- Boeing’s recent problems are widely seen as systemic: incentives, self‑certification, and pressure to avoid retraining led to unsafe designs, not just a few “bad actors.”
Analogies to software & engineering
- Many draw lessons for software engineering:
- Blameless postmortems, GitLab’s database incident, and public “SEV” reviews are praised.
- Others argue tech still often misuses “blameless” to shield clear process or even legal violations.
- Large subthread on whether software should be regulated like traditional engineering: liability for data breaches, codified minimum security practices, licensing, and whether “software engineer” should carry legal responsibility.
Near misses, CAST, and systems thinking
- Near misses are described as “gifts”: they reveal hazardous states without casualties and should trigger investigations.
- CAST / STAMP and systems‑thinking resources are recommended as ways to analyze interacting factors rather than searching for a single “root cause.”
Cars, roads, and broader safety culture
- Multiple commenters ask why car travel doesn’t adopt aviation‑style investigation and system redesign, given vastly higher road deaths.
- Suggested obstacles: fragmented responsibility, cultural resistance to restricting drivers, legal focus on individual fault, and entrenched car‑centric urban design.