RogerBW's Blog

Why Planes Crash Case Files 2003, Sylvia Wrigley 04 May 2026

2016 non-fiction, aviation history. Wrigley looks into a number of aircraft incidents.

While Without a Trace concentrates on disappearances, these incidents are a deliberately wide-ranging selection. There's a Cessna floatplane that stalled and crashed without mechanical failure, and it transpired that the pilot believed it was unstallable and didn't try to practice the procedures for recognising and recovering from the state. There's an actual documented case of a cell phone interfering with flight (the pilot decided to leave a message while flying a tricky approach in bad weather and essentially died of distraction; I've heard of a similar incident near Vienna). There are bird, missile and lightning strikes, and flying into weather that was too much for the airframe.

The one that struck me most, though, was the small Irish carrier's ATR-42 that made an emergency diversion after one engine shut down from fuel starvation. Their rigorous equipment failure reporting requirements (the plane was marked as unflyable until a tech had seen the problem and signed off on it as non-critical, and getting a tech could get several hours if it wasn't at their home field) led to a culture of simply not reporting failures at all if they didn't seem of vital importance. Combine that with crew incompetence in rarely-used procedures, and the ever-fatal "get it done" mentality (passengers were already delayed and annoyed), and you get assumptions and errors.

This resonates with me particularly because, although I'm not working with safety-critical machinery, and although my present employers are very reasonable in their demands of me, I have often met this attitude in co-workers and superiors. Never mind what went wrong, just reset it and get it up and running again. (Thus destroying much of the evidence of what went wrong, making it harder to work out an actual fix.) I view with admiration the aviation safety organisations that set up another aircraft to match the configuration of the one that crashed, then instrument it to work out just what's happening in each phase of manoeuvre. And I have certainly met the people who view safety rules as an external imposition to be worked round, getting in the way of the important business of computering.

Add A Comment

Your Name
Your Email
Your Comment

Note that I will only approve comments that relate to the blog post itself, not ones that relate only to previous comments. This is to ensure that the blog remains outside the scope of the UK's Online Safety Act (2023).

Your submission will be ignored if any field is left blank, but your email address will not be displayed. Comments will be processed through markdown.

Search
Archive
Tags 1920s 1930s 1940s 1950s 1960s 1970s 1980s 1990s 2000s 2010s 2300ad 3d printing action advent of code aeronautics aikakirja anecdote animation anime army astronomy audio audio tech aviation base commerce battletech bayern beer boardgaming book of the week bookmonth chain of command children chris chronicle church of no redeeming virtues cold war comedy computing contemporary cornish smuggler cosmic encounter coup covid-19 crime crystal cthulhu eternal cycling dead of winter disaster doctor who documentary drama driving drone ecchi economics en garde espionage essen 2015 essen 2016 essen 2017 essen 2018 essen 2019 essen 2022 essen 2023 essen 2024 essen 2025 existential risk falklands war fandom fanfic fantasy feminism filk film firefly first world war flash point flight simulation food garmin drive gazebo genesys geocaching geodata gin gkp gurps gurps 101 gus harpoon historical history horror horrorm science fiction hugo 2014 hugo 2015 hugo 2016 hugo 2017 hugo 2018 hugo 2019 hugo 2020 hugo 2021 hugo 2022 hugo 2023 hugo 2024 hugo 2025 hugo-nebula reread humour in brief avoid instrumented life javascript julian simpson julie enfield kickstarter kotlin learn to play leaving earth linux liquor lovecraftiana lua mecha men with beards mpd museum music mystery naval noir non-fiction one for the brow openscad opera parody paul temple perl perl weekly challenge photography podcast poetry politics postscript powers prediction privacy project woolsack pyracantha python quantum rail raku ranting raspberry pi reading reading boardgames social real life restaurant review reviews romance rpg a day rpgs ruby rust scala science fiction scythe second world war security shipwreck simutrans smartphone south atlantic war squaddies stationery steampunk stuarts suburbia superheroes suspense talon television the resistance the weekly challenge thirsty meeples thriller tin soldier torg toys trailers travel type 26 type 31 type 45 typst vietnam war war wargaming weather wives and sweethearts writing about writing x-wing young adult
Special All book reviews, All film reviews
Produced by aikakirja v0.1