Authorities investigating the disaster plan to look into what caused the black boxes to stop recording, South Korea's transport ministry says.

Summary

A Jeju Air Boeing 737-800 crashed at Muan International Airport, South Korea, killing 179 people, with only two crew members surviving. The black boxes stopped recording four minutes before the crash.

Authorities are investigating the cause of the malfunctioning black box. They suspect a bird strike, as feathers were found in one engine, and video footage confirmed a bird impact. However, the exact cause of the crash remains elusive.

Investigators are probing why the landing gear wasn’t deployed, the role of power failure in missing black box data, and the construction of the airfield wall the plane hit.

  • catloaf@lemm.eeEnglish
    31·
    2 days ago

    The swiss cheese model says that a bunch of failures have to line up just to make one bad thing happen, but in this case it seems like only a few failures lined up and a bunch of bad things happened. This is highly unusual.

    • lemmyng@lemmy.caEnglish
      32·
      2 days ago

      This is highly unusual.

      Depends on the field you’re in. In IT cascading failures are common.

      My gut tells me that there was also a sensor failure and that the pilots were operating on erroneous information, which caused them to take actions that ended up compounding the problem.

    • Maggoty@lemmy.worldEnglish
      1·
      1 day ago

      Only a few that we know of so far.

      But here’s the list I’m tracking -

      Video footage and teardrop go around suggests neither engine was producing thrust.

      Possible smoke in cabin making an already hard go around harder

      Runway on wrong side of go around for primary pilot to have good visibility

      Airport did not staff anti bird crew correctly

      Airport does not have state of the art anti bird systems

      Pilots decided on a go around instead of putting the bird struck plane on the ground for unknown reason. (Generally you continue your approach if you can) The unknown reason could be pilot error or a mechanical failure.

      That’s quite a lot to go wrong already.

          • lemmyng@lemmy.caEnglish
            8·
            2 days ago

            I know you joke, but likely not far from the truth. I was talking about misleading sensors, and this is an example of that - either my client didn’t get a response from the server indicating that the comment was received and retried, or my server didn’t get a response on OP’s server. Either way miscommunication happened, and the result (repeated comments, and from what I can see received at different times too) is much worse than the desired result (one comment entry only).

        • lemmyng@lemmy.caEnglish
          5·
          2 days ago

          I didn’t, but now I’m paranoid that whatever caused the comment to be sent multiple times is still going on 😅

        • lemmyng@lemmy.caEnglish
          10·
          2 days ago

          Very odd, I swear I wrote the post only once. I was having slowness loading the page - maybe there was a problem with my client not being able to get a response from the server and retrying, or the server processing the post multiple times (timestsamps are odd too)? Kind of serendipitous though - one system not getting the data it expects, and defaulting to a behaviour that is unintended.

      • bambooEnglish
        4·
        2 days ago

        Not sure what’s going on but this comment has been posted like 10 times from your account on this thread