Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Wednesday November 06 2019, @11:59PM   Printer-friendly
from the just-switch-off-and-start-it-again dept.

Submitted via IRC for SoyCow1337

In review of fatal Arizona crash, U.S. agency says Uber software had flaws

WASHINGTON (Reuters) - An Uber self-driving test vehicle that struck and killed an Arizona woman in 2018 had software flaws, the National Transportation Safety Board said Tuesday as it disclosed the company’s autonomous test vehicles were involved in 37 crashes over the prior 18 months.

NTSB may use the findings from the first fatal self-driving car accident to make recommendations that could impact how the entire industry addresses self-driving software issues or to regulators about how to oversee the industry.

The board will meet Nov. 19 to determine the probable cause of the March 2018 accident in Tempe, Arizona that killed 49-year-old Elaine Herzberg as she was walking a bicycle across a street at night.

In a report released ahead of the meeting, the NTSB said the Uber Technologies Inc vehicle had failed to properly identify her as a pedestrian crossing a street.

That accident prompted significant safety concerns about the nascent self-driving car industry, which is working to get vehicles into commercial use.

In the aftermath of the crash, Uber suspended all testing and did not resume until December in Pennsylvania with revised software and significant new restrictions and safeguards,

A spokeswoman for Uber's self-driving car effort, Sarah Abboud, said the company regretted the crash that killed Herzberg and noted it has “adopted critical program improvements to further prioritize safety. We deeply value the thoroughness of the NTSB's investigation into the crash and look forward to reviewing their recommendations.”

The NTSB reported at least two prior crashes in which Uber test vehicles may not have identified roadway hazards. The NTSB said between September 2016 and March 2018, there were 37 crashes of Uber vehicles in autonomous mode, including 33 that involved another vehicle striking test vehicles.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by All Your Lawn Are Belong To Us on Friday November 08 2019, @09:12PM (3 children)

    by All Your Lawn Are Belong To Us (6553) on Friday November 08 2019, @09:12PM (#918037) Journal

    Nope. I know that intersection where that accident happened. I used to work there. Looking both ways doesn't cut it for a car rolling at 45. You'll see the car and then you'll be toast before you can leap out of the way..... But a really alert driver could pull a swerve maneuver that would miss the pedestrian.

    --
    This sig for rent.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by All Your Lawn Are Belong To Us on Friday November 08 2019, @09:35PM

    by All Your Lawn Are Belong To Us (6553) on Friday November 08 2019, @09:35PM (#918047) Journal

    Google map of that area: https://www.google.com/maps/place/Tempe,+AZ/@33.4377844,-111.9448791,428m/data=!3m1!1e3!4m5!3m4!1s0x872b0898a6aa80e3:0xa2dd4aad392cb41f!8m2!3d33.4255104!4d-111.9400054 [google.com]

    It's weird to look at it twenty five plus years after I worked there. Some things have changed significantly in the area... but the facility I worked at and its buildings and the roads (Washington, Mill, West Center Parkway, Priest Drive, Project Drive) are all there, although the facility has changed a bit too. Nostalgia Lane. I can't even guess how many hundreds of times I drove that area on patrol.

    IIRC it was on Washington just where it curves, west of Mill. The map doesn't show very well that there is a downward slope to the road as it is curving to the West and before Center Parkway, and the net effect is that it is something of a blind curve. There is also a pedestrian walkway to the West as the curve finishes. Anyway, a really dicey place to cross even if you're in that crosswalk.

    --
    This sig for rent.
  • (Score: 2) by Snotnose on Friday November 08 2019, @10:57PM (1 child)

    by Snotnose (1623) on Friday November 08 2019, @10:57PM (#918068)

    I'm gonna have to call horse shit on this. If the road is built for 45 mph traffic then the turns can't be that sharp. Even if Uber was in one of the best handling sports cars of the world then at 45 MPH any pedestrian not stumbling drunk has plenty of time to either see the oncoming car, or hear the damned thing. Face it, if a sports car is doing 45 MPH turns during a time trial there is plenty of both tire and engine noise.

    I don't recall reading the Uber that killed her was doing a time trial in a speedy sports car.

    I seem to have dug my heels in on the pedestrian was at fault here. And ya know what? I think I'm right. She may have had the right of way, the Uber software/hardware may have been faulty, there may have been dodgy lighting at the intersection, the Uber driver may have been swiping left/right on their phone. But what it comes down to is the pedestrian was jaywalking at night, the Uber had it's headlights turned on following all traffic laws. To me the pedestrian is at fault. The Uber driver may have also been at fault, but at least s/he can come out of prison and have a life. The pedestrian that can't be bothered to look both ways, notsomuch.

    --
    I came. I saw. I forgot why I came.
    • (Score: 2) by All Your Lawn Are Belong To Us on Monday November 11 2019, @04:21PM

      by All Your Lawn Are Belong To Us (6553) on Monday November 11 2019, @04:21PM (#918975) Journal

      No, I'll stand a little corrected on it, the accident happened after the curve and drop. (Though yes, that curve and drop is actually too fast for 45. It's not a matter of the turn being sharp but that you just can't see what's coming ahead of you in the spot I was referencing. And I've driven that road so I'll stick to that. The spot where the accident happened is just after that, though.)

      I don't think the pedestrian had the right of way where the accident happened. First, Arizona law never grants a right of way but only directs when a right of way shall be yielded. But second Arizona law only specifically directly that right of way shall be yielded to pedestrians in crosswalks (marked or unmarked). There is a crossing zone in the neighborhood there but the video below shows the victim wasn't in it. The driver could still be at fault, though, because Arizona law says that a driver will exercise due care to avoid striking a pedestrian:

      AZ Rev Stat ยง 28-794 (2015)
      Notwithstanding the provisions of this chapter every driver of a vehicle shall:
      1. Exercise due care to avoid colliding with any pedestrian on any roadway.
      2. Give warning by sounding the horn when necessary.
      3. Exercise proper precaution on observing a child or a confused or incapacitated person on a roadway.

      The video shows driver's eyes shows they were not on the road in the moments before the impact. That was not due care in my book. YMMV.

      (Dashcam video [youtube.com] of the accident embedded in a news story. Can be disturbing and discretion is advised).

      ARS 28-701 (I won't quote it) is also the catchall that drivers shall always use "reasonable and prudent" speed and drivers will always control their speed in a way that no collisions shall ever occur with pedestrians, objects, or other vehicles. In other words, it doesn't matter what speed is posted. In the vast majority of cases, including here, if you have a collision you have not driven at reasonable and prudent speed to avoid it.

      So sure, the pedestrian was at fault for picking that spot and then committing to it. The pedestrian could have dropped the bike and jumped out of the way. But no, the neither the driver nor Uber is innocent in this. The driver did what every driver who uses the service will do and that is exactly what they are told not to do - take their attention from the road. And there is no way a computer is ever going to be able to pick a 'reasonable and prudent' speed to avoid a collision. Thus by default the computer controlling the car is in violation.

      More to the point the horrified look on that driver's face shows that what happened here will stay with her the rest of her life. And the pedestrian is still dead.

      --
      This sig for rent.