John Barnett had worked for Boeing for 32 years, until his retirement in 2017.

In the days before his death, he had been giving evidence in a whistleblower lawsuit against the company.

Boeing said it was saddened to hear of Mr Barnett’s passing. The Charleston County coroner confirmed his death to the BBC on Monday.

It said the 62-year-old had died from a “self-inflicted” wound on 9 March and police were investigating.

  • blahsay@lemmy.world
    link
    fedilink
    arrow-up
    101
    arrow-down
    2
    ·
    8 months ago

    I’ll never fly in a Boeing again after hearing this. Unless the ceo gets arrested 🤔

    Kayak lets you search via plane model fyi

    • smb@lemmy.ml
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      2
      ·
      8 months ago

      thanks for the info about kayak, very appreciated!!

      me same, i would never again willingly book a flight with a boeing airplane.

      in my mind that B. company got the status of a criminal organization >20 years ago when they afaik refused to fix a problem with sensors and the computer overriding pilot control which crashed the plane just after takeoff while pilot could not do anything against it. back then however the discussions were about computers overriding pilot control, not about a company intentionally risking lives.

      Now they seem to me to still refuse to fix the problems and instead rename planes so that one cannot avoid their deathtraps unless not at all flying with their aircrafts. so i choose to only book flights with aviation companies that do not have B. planes at all. I decided to in future rather use a car or boat instead, if only B. planes are available.

      i would not be surprised if the current “technical event” would be the actual same cause that “forced the nose down” over 20years ago, to me it sounds exactly like the same until now, it might just luckily have happened by chance high enough in the air so that the “nose forced down by computer” problem could somehow be solved with enough time where they had only seconds in that crash two decades ago.

      • raspberriesareyummy@lemmy.world
        link
        fedilink
        arrow-up
        25
        ·
        8 months ago

        20 years ago when they afaik refused to fix a problem with sensors and the computer overriding pilot control which crashed the plane just after takeoff while pilot could not do anything against it

        Erm. Are you talking about something OTHER than the changed 737-MAX design and the MCAS system? Because those two related crashes happened in late 2018 and early 2019 - 5-6 years ago. Got a link to the >20 years ago incident you are talking about?

        • sanpedropeddler@sh.itjust.works
          link
          fedilink
          arrow-up
          7
          ·
          8 months ago

          The only crash I know of thats similar to what they’re talking about happened in an airbus plane, and during landing not takeoff. The pilots tried to pull up on their side sticks to avoid crashing, but the plane ignored the input because it would have overcorrected and caused the plane to stall. As a result they crashed onto the runway.

          That isn’t to say Boeing doesn’t have a history with such things. Look into United Airlines 811 in 1989. Improper design caused a massive chunk of the fuselage to be ripped out in flight, throwing 9 people into the ocean and causing a rapid decompression. Initial investigations said the cause was human error, but the family of one of the victims researched it themselves and found out that wasn’t the case.

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

            Can’t find an airbus crash on landing with that description - do you have a year, place, or flight number?

            And of course, Boeing and Airbus also have had bad design decisions - just think of the A400-M…

              • raspberriesareyummy@lemmy.world
                link
                fedilink
                arrow-up
                3
                ·
                8 months ago

                Thanks. Reading up on that however, reads like not so much a negligent design, but a lesson learned from a new scenario that hadn’t caused an issue before.

                PS: I cringed hard at the use of “male” in the description of the pilot & copilot on the wikipedia page - seems some incel wrote that…

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

                  I would’ve assumed it should have been designed to dampen the input to a point where it isn’t dangerous, instead of ignoring it entirely. There could be a reason they didn’t do that which I’m not seeing, but that seems like a good idea at first glance.

                  • raspberriesareyummy@lemmy.world
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    8 months ago

                    I agree but we both have the luxury of hindsight. I think it’s really difficult to always anticipate all failure scenarios in advance. I am saying that as someone who just discovered had a “bug” in his software discovered that caused a buffer overflow because I didn’t anticipate a buffer as small as 32 Kilobytes in a data link that was designed for 32 Megabits per second :)

        • BlitzoTheOisSilent@lemmy.world
          link
          fedilink
          arrow-up
          6
          ·
          8 months ago

          Not the person you responded to, but they may be talking about the Boeing 787 Dreamliner, which I believe the FAA grounded (I could be misremembering the John Oliver points about it) after several incidents within the first few months of release.

        • smb@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          8 months ago

          what i meant was decades ago, not the “recent” crashes of 2018…

          i tried to find it but didn’t yet. there are way more plane crashes than i thought i would have to go through…

          looking at “new technology” introduced (as it was quite new) i stumbled over this article and remembered that the “three computers voting” (while the pilot may only take place in that voting - as a minority …) was part of the discussions back then (which is not written in that article however, but i found one piece, yay!):

          https://archive.seattletimes.com/archive/?date=19950605&slug=2124705

          i feel like i could remember something wrong like it maybe was not a takeoff but possibly a go-around where the crash happened… not sure i won’t yet give up searching, but i have to stop for now…

          edit: i am not saying it was a 777, i just found a piece of my 20year old puzzle…

    • misspacfic@lemm.ee
      link
      fedilink
      arrow-up
      7
      ·
      8 months ago

      good call on kayak.

      just tried it out by excluding MAX models of aircraft and it worked. unfortunately, that severely limits options, but hey, it’s possible.

    • dangblingus@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

      I just looked at a regular domestic Air Canada flight from Pearson to YVR… $1500 fucking dollars to catch an Airbus over a Boeing. Seems like the demand to not be on a Boeing plane is driving plane tickets into the stratosphere.

      • blahsay@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        That’s just air Canada.

        Their new motto: ‘We’re not happy till you’re not happy’