Philip Paxson’s family are suing the company over his death, alleging that Google negligently failed to show the bridge had fallen nine years earlier.

Mr Paxson died in September 2022 after attempting to drive over the damaged bridge in Hickory, North Carolina.

A spokesperson for Google said the company was reviewing the allegations.

The case was filed in civil court in Wake County on Tuesday.

Mr Paxson, a father of two, was driving home from his daughter’s ninth birthday party at a friend’s house and was in an unfamiliar neighbourhood at the time of his death, according to the family’s lawsuit.

His wife had driven his two daughters home earlier, and he stayed behind to help clean up.

“Unfamiliar with local roads, he relied on Google Maps, expecting it would safely direct him home to his wife and daughters,” lawyers for the family said in a statement announcing the lawsuit.

“Tragically, as he drove cautiously in the darkness and rain, he unsuspectingly followed Google’s outdated directions to what his family later learned for nearly a decade was called the ‘Bridge to Nowhere,’ crashing into Snow Creek, where he drowned.”

Local residents had repeatedly contacted Google to have them change their online maps after the bridge collapsed in 2013, the suit claims.

    • ShadowRam@kbin.social
      link
      fedilink
      arrow-up
      11
      arrow-down
      12
      ·
      edit-2
      1 year ago

      Yeah, how’s it Google’s fault that there were no signs? blocks? etc.

      9 years is excessive? sure maybe.

      But bridge collapse that evening while approaching it? Google’s Fault? No…

      So where do you draw that line where it’s Google’s Fault?

      1 day? 1 month? 1 year?

      Yeah, you can’t reasonable put a timeline on something like that.

      What happens if it was found out dude used an old paper map? Gonna sue that map company too?

      Just because Google has the ability to update maps quicker than old paper, doesn’t mean they are suddenly obligated to.

      • Zaktor@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        2
        ·
        1 year ago

        So where do you draw that line where it’s Google’s Fault?

        1 day? 1 month? 1 year?

        Why use these numbers when the number in question is 9 years?

        Yeah, you can’t reasonable put a timeline on something like that.

        I can certainly say that 9 years is too long to fail to update a map that contains a dangerous route.

        • ShadowRam@kbin.social
          link
          fedilink
          arrow-up
          6
          arrow-down
          10
          ·
          1 year ago

          I guess you missed the point.

          Yes, we can all certainly say that’s too long.

          But carry that thought farther as I explained.

          If you are going to make someone legally responsible for something like this, you need to draw a line where it is.
          So where do you draw that line?

          You reasonable can not, and that is because the premise that Google should be responsible for such a thing is ridiculous.

          This case is just a standard US justice system where they just ‘Sue everyone’ and see where the chips fall.

          • Zaktor@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            5
            arrow-down
            2
            ·
            1 year ago

            This is a ridiculous argument. We set limits on things all the time. That the limit will be arbitrary doesn’t mean there simply cannot be liability. 1 year is fine, 6 months is fine, hell, 1 month is fine. The company’s internal processes will expand or contract to fit legal liability.

          • zero_iq@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            You don’t need to draw a line for this case. You just need to decide if 9 years is too long.