Edit:

  • article title update, bump not bomb jolt’
  • added comma

DENVER — An engine cover on a Boeing 737 operated by Southwest Airlines ripped open just after taking off from Denver International Airport Sunday morning.

The Houston-bound Southwest flight took off from DIA around 7:45 a.m., and returned to the airport 30 minutes later, landing safely. No injuries were reported.

  • stoy
    link
    fedilink
    arrow-up
    71
    arrow-down
    10
    ·
    8 months ago

    It has been said a lot these last few months, but it is worth repeating untill Boeing stops dicking around…

    “It is Boeing, I ain’t going”

    • Rhaedas@fedia.io
      link
      fedilink
      arrow-up
      44
      arrow-down
      6
      ·
      8 months ago

      It’s also important to try to avoid jumping to conclusions without the facts. If this is a new 737 and there’s a manufacturing issue, then rake Boeing over the coals. They do have problems. But if this is an older plane that had either maintenance issues, then go after Southwest first unless it’s a Boeing responsibility. And of course, things do happen beyond anyone’s control too, and engines that fail for any reason but don’t take out the rest of the aircraft is a bit of a win for design.

    • mercano@lemmy.world
      link
      fedilink
      arrow-up
      17
      arrow-down
      1
      ·
      8 months ago

      The story doesn’t mention the age or variant of the plane, but there’s a good chance this is an issue with Southwest maintenance, not Boeing (or their subcontractors) construction.

      • stoy
        link
        fedilink
        arrow-up
        41
        arrow-down
        2
        ·
        8 months ago

        Some quick googling got me the details.

        1. The article mentions the flight number.
        2. Since I didn’t know the airline code of Southweast, I googled Southwest and the flight number.
        3. Google flights showed me the full flight number.
        4. Putting that into Flightradar got me a list of the last flights of this flight, one showing a deviation.
        5. Going in there gave me the registration number of the plane that flew that flight and data about the type of plane.
        6. Searching FAA registry gave me all details of the plane.

        It is a Boeing 737-8H4, delivered in 2015, so an alomst decade old plane, meaning it was probably an issue with maintenance this time.

        Doesn’t mean I would fly a Boeing plane untill the stop dicking around.

          • Optional@lemmy.world
            link
            fedilink
            arrow-up
            8
            arrow-down
            4
            ·
            8 months ago

            They wouldn’t but then people ragging on Boeing are also correct. So.

            Shall we all wait for the next disaster? Keep scrolling to find out!

            Hey what was that union that Reagan destroyed to avoid paying them? I forget.

          • stoy
            link
            fedilink
            arrow-up
            8
            arrow-down
            5
            ·
            8 months ago

            You are aware of the other recent high profile accidents with Boeing planes and the issues with Boeing mgmt?

            This incident may not be related, but based on the other issues I remain steady in my resolve that if it is Boeing I ain’t going.

            Untill the focus of Boeing shifts from it’s share value and back to engineering, I will be very careful about getting on a Boeing flight.

            • Zipitydew@sh.itjust.works
              link
              fedilink
              arrow-up
              8
              arrow-down
              4
              ·
              8 months ago

              I’m aware of a number of airlines experiencing random mechanical issues on Boeing aircraft they’ve owned for years. And 1 issue that was a new plane which is still under investigation and likely was Boeing’s fault

              I and my team of about 25 engineers travel for work constantly. Weird mechanical issues happen way more than the public realizes. Saying all of it has been Boeing’s fault is factually incorrect.

              • stoy
                link
                fedilink
                arrow-up
                7
                arrow-down
                2
                ·
                8 months ago

                You are absolutely right that claiming it is all Boeing’s fault is incorrect, I never claimed that it was.

                However, since the MD/Boeing merger, Boeing mgmt has acted reckless with safety.

                They have pushed the margins of safety too far and we are starting to see the issues now.

                I realize that you and your team may not have a lot of choice about what plane you can fly on, but I have, and I will pick flights based on the plane.

                • Zipitydew@sh.itjust.works
                  link
                  fedilink
                  arrow-up
                  5
                  arrow-down
                  1
                  ·
                  8 months ago

                  I get it. And I’m probably an oddball with being fascinated about flying even before I started traveling for work. Now it’s something I do for fun to track planes I’ll be on.

                  So to me the only thing that’s changed recently is the news getting clicks running any story they can about Boeing. They could have been for years if they wanted to. But it’s one of the current hot topics now.

                  And even now the news should be shitting on the airlines directly much moreso than Boeing. All issues I’ve heard of since the door blowout would have been a maintenance problem. Especially United. It seems like those fuckers in particular have cut corners. I avoid them in general when booking regardless of plane type.

      • Adderbox76@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        For some reason I read that as “Boeing killed Jon Benet” and was thinking well that’s a conspiracy theory I hadn’t heard before…