Biography:Death of Elaine Herzberg

From HandWiki
Short description: First pedestrian fatality caused by self-driving car
Elaine Herzberg
Born
Elaine Marie Wood

Phoenix, Arizona, U.S.[1]
DiedMarch 18, 2018(2018-03-18) (aged 49)
Tempe, Arizona, U.S.
Burial placePhoenix, Arizona[1]
NationalityAmerican
EducationApache Junction High School, Apache Junction, Arizona[1]
Known forFirst pedestrian to be killed by a self-driving car
Spouse(s)Mike Herzberg (until his death); Rolf Erich Ziemann (until Elaine's death)[1]

The death of Elaine Herzberg (August 2, 1968 – March 18, 2018) was the first recorded case of a pedestrian fatality involving a self-driving car, after a collision that occurred late in the evening of March 18, 2018. Herzberg was pushing a bicycle across a four-lane road in Tempe, Arizona, United States, when she was struck by an Uber test vehicle, which was operating in self-drive mode with a human safety backup driver sitting in the driving seat. Herzberg was taken to the local hospital where she died of her injuries.[2][3][4]

Following the fatal incident, the National Transportation Safety Board (NTSB) issued a series of recommendations and sharply criticized Uber. The company suspended testing of self-driving vehicles in Arizona,[5] where such testing had been sanctioned since August 2016.[6] Uber chose not to renew its permit for testing self-driving vehicles in California when it expired at the end of March 2018.[7] Uber resumed testing in December 2018.[8]

On March 2019, Arizona prosecutors ruled that Uber was not criminally responsible for the crash.[9] The back-up driver of the vehicle was charged with negligent homicide.[10]

While Herzberg was the first pedestrian killed by a self-driving car,[11][12] a driver had been killed by a semi-autonomous car almost two years earlier.[13] A reporter for The Washington Post compared Herzberg's fate with that of Bridget Driscoll who, in the United Kingdom in 1896, was the first pedestrian to be killed by an automobile.[14]

The Arizona incident has magnified the importance of collision avoidance systems for self-driving vehicles.[15]

Collision summary

Herzberg was crossing Mill Avenue (North) from west to east, approximately 360 feet (110 m) south of the intersection with Curry Road, outside the designated pedestrian crosswalk,[16][17] close to the Red Mountain Freeway. She was pushing a bicycle laden with shopping bags,[2] and had crossed at least two lanes of traffic when she was struck[5] at approximately 9:58 pm MST (00)[16] by a prototype Uber self-driving car based on a Volvo XC90, which was traveling north on Mill.[18][19] The vehicle had been operating in autonomous mode[20] since 9:39 pm, nineteen minutes before it struck and killed Herzberg.[16] The car's human safety backup driver, Rafaela Vasquez,[2] did not intervene in time to prevent the collision.[21] Vehicle telemetry obtained after the crash showed that the human operator responded by moving the steering wheel less than a second before impact, and she engaged the brakes less than a second after impact.[16]

Cause investigation

The self-driving Uber Volvo XC90 involved in the collision, with damage on the right front side

The county district attorney's office recused itself from the investigation, due to a prior joint partnership with Uber promoting their services as an alternative to driving under the influence of alcohol.[22]

Accounts of the crash have been conflicting in terms of the speed limit at the place of the incident.[23][24] According to Tempe police the car was traveling in a 35 mph (56 km/h) zone, but this is contradicted by a posted speed limit of 45 mph (72 km/h).[25]

The National Transportation Safety Board (NTSB) sent a team of federal investigators to gather data from vehicle instruments, and to examine vehicle condition along with the actions taken by the safety driver.[26] Their preliminary findings were substantiated by multiple event data recorders and proved the vehicle was traveling 43 miles per hour (69 km/h) when Herzberg was first detected 6 seconds (378 feet (115 m)) before impact; during 4.7 seconds the self driving system did not infer that emergency braking was needed.[16] A vehicle traveling 43 mph (69 km/h) can generally stop within 89 feet (27 m) once the brakes are applied.[27] The machine needed to be 1.3 seconds (82 feet (25 m)) away prior to discerning that emergency braking was required, whereas at least that much distance was required to stop.[28] The system failed to behave properly.[16][29][30][31][32][33] A total stopping distance of 76 feet itself would imply a safe speed under 25 mph (40 km/h).[34] Human intervention was still legally required. Computer perception–reaction time would have been a speed limiting factor had the technology been superior to humans in ambiguous situations;[35] however, the nascent computerized braking technology was disabled the day of the crash, and the machine's apparent 4.7-second perception–reaction (alarm) time[16] allowed the car to travel 250 feet (76 m). Video released by the police on March 21 showed the safety driver was not watching the road moments before the vehicle struck Herzberg.[3][36]

Environment

<graph>

{ 

 //
 // ATTENTION: This code is maintained at https://www.mediawiki.org/wiki/Template:Graph:Street_map_with_marks
 //            Please do not modify it anywhere else, as it may get copied and override your changes.
 //            Suggestions can be made at https://www.mediawiki.org/wiki/Template_talk:Graph:Street_map_with_marks
 //
 // Template translation is in https://commons.wikimedia.org/wiki/Data:Original/Template:Graphs.tab
 //
 "version": 2, "width":350, "height": 250, "padding": 0,
 "signals":[
   // These signals allow us to quickly move the map within the image, e.g. to leave space for the legend

{"name":"legendWidth", "init": {"expr": "0"} }, 

   {"name":"legendHeight", "init": {"expr": "height"} },
   {"name":"imgWidth", "init": {"expr": "width-legendWidth"} },
   {"name":"imgHeight", "init": {"expr": "height"} },
   {"name":"imgXC", "init": {"expr": "imgWidth/2"} },
   {"name":"imgYC", "init": {"expr": "imgHeight/2"} },
   {"name":"imgTileSize", "init": {"expr": "256"} },
   {"name":"imgLat", "init": {"expr": "33.436637"} },
   {"name":"imgLon", "init": {"expr": "-111.942942"} },
   {"name":"imgZoom", "init": {"expr": "16"} },
   {"name":"picWidth", "init": {"expr": "180"} },
   {"name":"picHeight", "init": {"expr": "picWidth/2"} },
   {"name":"picXC", "init": {"expr": "imgWidth-(picWidth/2)"} },
   {"name":"picYC", "init": {"expr": "imgHeight-(picHeight/2)"} },
   {"name":"showMiniMap", "init": {"expr": "0"} }
 ],
 "data": [
   {
     "name": "data",

// Otherwise use the first unnamed argument for source values 

     "values": [  { "lat": 33.436637, 
    "lon": -111.942942, 
    "img": "wikirawupload:https://handwiki.org/wiki/images/thumb/1/10/Mapscaleline.svg/120px-Mapscaleline.svg.png", 
    "width": 50, 
    "height": 8, 
    "offsetX": 138, 
    "offsetY": 115, 
    "textAlign": "right", 
    "textDx": 22, 
    "textDy": -2, 
    "textColor": "grey", 
    "textFont": "Tahoma", 
    "textFontSize": 9, 
    "text":  "150m" }

, { "lat": 0, "lon": 0, "img": "wikirawupload:https://handwiki.org/wiki/images/thumb/0/0c/Red_pog.svg/10px-Red_pog.svg.png", "height": 10, "width": 10, "text": "", "textAngle": 0, "textAlign": "right", "textBaseline": "middle", "textDx": -7, "textDy": 1, "textFontSize": 12, "textColor": "#AA1205"


}


, { "lat": 0.1, "lon": 0.1, "img": "wikirawupload:https://handwiki.org/wiki/images/thumb/0/0c/Red_pog.svg/10px-Red_pog.svg.png", "height": 10, "width": 10, "text": "", "textAngle": 0, "textAlign": "right", "textBaseline": "middle", "textDx": -7, "textDy": 1, "textFontSize": 12, "textColor": "#AA1205"


} 































     ],
     "transform": [

       {
         "type": "geo",
         "projection": "mercator",
         "scale": {"expr": "imgTileSize/PI/2*pow(2,imgZoom)"},
         "translate": [{"expr": "imgXC"}, {"expr": "imgYC"}],
         "center": [{"expr": "imgLon"}, {"expr": "imgLat"}],
         "lon": "lon", "lat": "lat"
       },
       { "type": "formula", "field":"layout_x", "expr": "datum.layout_x + (datum.offsetX || 0)" },
       { "type": "formula", "field":"layout_y", "expr": "datum.layout_y + (datum.offsetY || 0)" },
       { "type": "formula", "field":"color", "expr": "datum.color || '#c33'" },
       { "type": "formula", "field":"textColor", "expr": "datum.textColor || datum.color" },
       { "type": "formula", "field":"strokeColor", "expr": "datum.strokeColor || '#ffe7e6'" }
     ]
   },
   {
     // Hack: single value data source for drawing/hiding images and other non-series elements
     "name": "dummyData",
     "values": [{}]
   }
 ],

// Legend only works if showLegend and colorScaleField are set 

 "marks": [
   {
     "type": "image",
     "from": {
       "data": "dummyData",
       "transform": [
         { "type": "formula", "field":"url", "expr": "'mapsnapshot:///?width='+imgWidth+'&height='+imgHeight+'&zoom='+imgZoom+'&lat='+imgLat+'&lon='+imgLon" }
       ]
     },
     "properties": {
       "enter": {
         "url": {"field": "url"},
         "xc": {"signal": "imgXC"}, "yc": {"signal": "imgYC"},
         "width": {"signal": "imgWidth"}, "height": {"signal": "imgHeight"}
       }
     }
   },
   {
     // Places an image of a given name and size at the [lan,lon] location
     "type": "image",
     "from": {
       "data": "data",
       "transform": [
         { "type": "filter", "test": "datum.img" },
         { "type": "formula", "field":"iconWidth", "expr": "datum.width || 0" },
         { "type": "formula", "field":"iconHeight", "expr": "datum.height || 0" },
         { "type": "formula", "field":"img",
           "expr": "if(!test(/^[a-z]+:\\/\\//, datum.img), 'wikifile:///'+datum.img, datum.img)" },
         // Ensure that either width or height parameter is passed to wikifile:// request
         { "type": "formula", "field":"img",
           "expr": "if((datum.iconWidth || datum.iconHeight) && !test(/[?&](width|height)=\\d/, datum.img),if(datum.iconWidth,datum.img+'?width='+datum.iconWidth,datum.img+'?height='+datum.iconHeight), datum.img)" }
     ]},
     "properties": {
       "enter": {
         "url": {"field": "img"},
         "xc": {"field": "layout_x"}, "yc": {"field": "layout_y"},
         "width": {"field": "iconWidth"}, "height": {"field": "iconHeight"}
       }
     }
   },
   {
     // Draw marks of a given color, shape, and size at the [lan,lon] location
     "type": "symbol",
     "from": {
       "data": "data",
       "transform": [{ "type": "filter", "test": "!datum.img" }]
     },
     "properties": {
       "enter": {
         "x": {"field": "layout_x"},
         "y": {"field": "layout_y"},
         // If colorScaleField is set, use color scaling, otherwise use the preset color value
         "fill": { "field": "color" },
         "size": {"field": "size"},
         "shape": {"field": "shape"},
         "stroke": {"field": "strokeColor"}
       }
     }
   },
   {
     // Draw text with the given color and size at the [lan,lon] location
     // See https://github.com/vega/vega/wiki/Marks#text for all parameter description (prepend "text" and capitalize them)
     "type": "text",
     "from": {
       "data": "data",
       "transform": [
         { "type": "filter", "test": "datum.text" },
         // Figure out if this is an LTR or RTL page. For LTR, show label to the right of the icon, left-aligned. For RTL, reverse.
         { "type": "formula", "field":"isLTR", "expr": "'‎' == '\\u200E'" },
         // If these values are not defined ("undefined" is not allowed, so test for truthiness and not 0)
         { "type": "formula", "field":"textDx", "expr": "if(!datum.textDx && datum.textDx != 0, if(datum.isLTR,8,-8), datum.textDx)" },
         { "type": "formula", "field":"textAlign", "expr": "if(!datum.textAlign, if(datum.isLTR,'left','right'), datum.textAlign)" },
         { "type": "formula", "field":"textBaseline", "expr": "datum.textBaseline || 'middle'" }
     ]},
     "properties": {
       "enter": {
         "text": {"field": "text"},
         "x": {"field": "layout_x" },
         "y": {"field": "layout_y"},
         "dx": {"field": "textDx" },
         "dy": {"field": "textDy"},
         "fill": {"field": "textColor"},
         "align": {"field": "textAlign"},
         "baseline": {"field": "textBaseline"},
         "radius": {"field": "textRadius"},
         "theta": {"field": "textTheta"},
         "angle": {"field": "textAngle"},
         "font": {"field": "textFont"},
         "fontSize": {"field": "textFontSize"},
         "fontWeight": {"field": "textFontWeight"},
         "fontStyle": {"field": "textFontStyle"}
       }
     }
   },
   {
     // Draw a low-zoom locator map frame
     "type": "rect",
     "from": {
       "data": "dummyData",
       "transform": [
         { "type": "filter", "test": "showMiniMap" }
       ]
     },
     "properties": {
       "enter": {
         "xc": {"signal": "picXC"}, "yc": {"signal": "picYC"},
         "width": {"signal": "picWidth", "offset":2}, "height": {"signal": "picHeight"},
         "stroke": {"value":"#fff"},"strokeWidth": {"value":6}
       }
     }
   },
   {
     // Draw a low-zoom locator map by using a premade world map image
     "type": "image",
     "from": {
       "data": "dummyData",
       "transform": [
         { "type": "filter", "test": "showMiniMap" },
         { "type": "formula", "field":"url", "expr": "1" }
       ]
     },
     "properties": {
       "enter": {
         "url": {"value": "wikirawupload:https://handwiki.org/wiki/images/thumb/a/ac/Earthmap1000x500.jpg/180px-Earthmap1000x500.jpg"},
         "xc": {"signal": "picXC"}, "yc": {"signal": "picYC"},
         "width": {"signal": "picWidth"}, "height": {"signal": "picHeight"}
       }
     }
   },
   {
     // Draw a zoom-out mark at the [lan,lon] location
     "type": "symbol",
     "from": {
       "data": "dummyData",
       "transform": [
         { "type": "filter", "test": "showMiniMap" },
         { "type": "formula", "field":"lat", "expr": "imgLat" },
         { "type": "formula", "field":"lon", "expr": "imgLon" },
         {
           "type": "geo",
           "projection": "equirectangular",
           "scale": {"expr": "180/2/PI"},
           "translate": [{"expr": "picXC"}, {"expr": "picYC"}],
           "center": [{"expr": "0"}, {"expr": "0"}],
           "lon": "lon", "lat": "lat"
         }
       ]
     },
     "properties": {
       "enter": {
         "x": {"field": "layout_x"}, "y": {"field": "layout_y"},
         "fill": {"value": "#c33"},
         "stroke": {"value": "#ffe7e6"},
         "size": {"value": 40}
       }
     }
   }
 ]

} </graph>

<maplink zoom="17" latitude="33.436637" longitude="-111.942942" text="[Interactive fullscreen map]">

[


{"type": "FeatureCollection", 

 "features": [


{ "type": "Feature", 

  "properties": {
   "title": ".", 
   "description": " 0.1,0.1",
   "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#AA1205" },
  "geometry": {"type": "Point", "coordinates": [0.1,0.1] }
}




























































] }

]</maplink>
Vicinity of Mill Avenue (running north–south) and Curry/Washington (east–west) in Tempe, Arizona

In widely-disseminated remarks that would shape the narrative about the crash, were later seen as prejudicial, she later regretted, and were subsequently contradicted by her own department, Tempe Police Chief Sylvia Moir was quoted stating the collision was "unavoidable" based on the initial police investigation, which included a review of the video captured by an onboard camera.[37][38][39] Moir faulted Herzberg for crossing the road in an unsafe manner: "It is dangerous to cross roadways in the evening hour when well-illuminated, managed crosswalks are available."[40] According to Uber, safety drivers were trained to keep their hands very close to the wheel all the time while driving the vehicle so they were ready to quickly take control if necessary.[41]

The driver said it was like a flash, the person walked out in front of them. His [sic] first alert to the collision was the sound of the collision. [...] it's very clear it would have been difficult to avoid this collision in any kind of mode (autonomous or human-driven) based on how she came from the shadows right into the roadway.

Lua error in Module:Multiple_image at line 163: attempt to perform arithmetic on local 'totalwidth' (a nil value). Tempe police released video on March 21, 2018, showing footage recorded by two onboard cameras: one forward-looking, and one capturing the safety driver's actions. The forward-facing video shows that the self-driving car was traveling in the far right lane when it struck Herzberg. The driver-facing video shows the safety driver was looking down prior to the collision.[5] The Uber operator is responsible for intervening and taking manual control when necessary as well as for monitoring diagnostic messages, which are displayed on a screen in the center console. In an interview conducted after the crash with NTSB, the driver stated she was monitoring the center stack at the time of the collision.[16]

After the Uber video was released, journalist Carolyn Said noted the police explanation of Herzberg's path meant she had already crossed two lanes of traffic before she was struck by the autonomous vehicle.[5] The Marquee Theatre and Tempe Town Lake are west of Mill Avenue, and pedestrians commonly cross mid-street without detouring north to the crosswalk at Curry.[19] According to reporting by the Phoenix New Times, Mill Avenue contains what appears to be a brick-paved path in the median between the northbound and southbound lanes;[19] however, posted signs prohibit pedestrians from crossing in that location.[42] When the second of the Mill Avenue bridges over the town lake was added in 1994 for northbound traffic, the X-shaped crossover in the median was installed to accommodate the potential closing of one of the two road bridges. The purpose of this brick-paved structure is purely to divert cars from one side to the other if a bridge is closed to traffic, and although it may look like a crosswalk for pedestrians, it is in fact a temporary roadway with vertical curbs and warning signs.

Software issues

Michael Ramsey, a self-driving car expert with Gartner, characterized the video as showing "a complete failure of the system to recognize an obviously seen person who is visible for quite some distance in the frame. Uber has some serious explaining to do about why this person wasn't seen and why the system didn't engage."[5]

James Arrowood, a lawyer specializing in driverless cars in Arizona, speculated that if the sensors were unable to determine it was a person they were detecting due to Herzberg walking her bicycle across the street, with the bicycle's metal parts between her and the sensors and thus the sensors interpreted her presence as that of another vehicle that was moving out of its right of way, the software may have decided to proceed after assuming that [the 'vehicle'] Herzberg would yield the right of way.[21] However, the context to his connecting statement in the footnoted article was left out of that article, as evidenced by the singular use of the word 'decided' rather than the entire statement, in the prefatory sentence in the article. Arizona law (ARS 28-793)[43] states that pedestrians crossing the street outside a crosswalk shall yield to cars but it was not Arrowood's intent to suggest that the sensors would presume a person had to move rather than the vehicle needing to brake, rather, the statement's full context was that the driverless vehicle's sensors might not have recognized her as a person due to the interference from the bicycle.[44][19] Per Arrowood, "The computer makes a decision. It says, 'Hey, there is this object moving 10 or 15 feet to left of me, do I move or not?' It (could be) programmed, I have a right of way, on the assumption that whatever is moving [presumably another vehicle] will yield the right of way."[21] The NTSB preliminary report, however, noted that the software did order the car to brake 1.3 seconds before the collision.

A video shot from the vehicle's dashboard camera showed the safety driver looking down, away from the road. It also appeared that the driver's hands were not hovering above the steering wheel, which is what drivers are instructed to do so they can quickly retake control of the car. Uber had moved from two employees in every car to one. The paired employees had been splitting duties: one ready to take over if the autonomous system failed, and another to keep an eye on what the computers were detecting. The second person was responsible for keeping track of system performance as well as labeling data on a laptop computer. Mr. Kallman, the Uber spokesman, said the second person was in the car for purely data related tasks, not safety. When Uber moved to a single operator, some employees expressed safety concerns to managers, according to the two people familiar with Uber's operations. They were worried that going solo would make it harder to remain alert during hours of monotonous driving.

Playback of self-driving system data at 1.3 seconds before impact. Distances shown in meters.

The recorded telemetry showed the system had detected Herzberg six seconds before the crash, and classified her first as an unknown object, then as a vehicle, and finally as a bicycle, each of which had a different predicted path according to the autonomy logic. 1.3 seconds prior to the impact, the system determined that emergency braking was required, which is normally performed by the vehicle operator. However, the system was not designed to alert the operator, and did not make an emergency stop on its own accord, as "emergency braking maneuvers are not enabled while the vehicle is under computer control, to reduce the potential for erratic vehicle behavior", according to NTSB.[16]

Sensor issues

Brad Templeton, who provided consulting for autonomous driving competitor Waymo, noted the car was equipped with advanced sensors, including radar and LiDAR, which would not have been affected by the darkness. Templeton stated "I know the [sensor] technology is better than that, so I do feel that it must be Uber's failure."[5] Arrowood also recognized potential sensor issues: "Really what we are going to ask is, at what point should or could those sensors recognize the movement off to the left. Presumably she was somewhere in the darkness."[21]

In a press event conducted by Uber in Tempe in 2017, safety drivers touted the sensor technology, saying they were effective at anticipating jaywalkers, especially in the darkness, stopping the autonomous vehicles before the safety driver can even see pedestrians. However, manual intervention by the safety drivers was required to avoid a collision with another vehicle on at least one instance with a reporter from The Arizona Republic riding along.[45]

Uber announced they would replace their Ford Fusion-based self-driving fleet with cars based on the Volvo XC90 in August 2016; the XC90s sold to Uber would be prepared to receive Uber's vehicle control hardware and software, but would not include any of Volvo's own advanced driver-assistance systems.[46] Uber characterized the sensor suite attached to the Fusion as the "desktop" model, and the one attached to the XC90 as the "laptop", hoping to develop the "smartphone" soon.[47] According to Uber, the suite for the XC90 was developed in approximately four months.[48] The XC90 as modified by Uber included a single roof-mounted LiDAR sensor and 10 radar sensors, providing 360° coverage around the vehicle. In comparison, the Fusion had seven LiDAR sensors (including one mounted on the roof) and seven radar sensors. According to Velodyne, the supplier of Uber's LiDAR, the single roof-mounted LiDAR sensor has a narrow vertical range that prevents it from detecting obstacles low to the ground, creating a blind spot around the vehicle. Marta Hall, the president of Velodyne commented "If you're going to avoid pedestrians, you're going to need to have a side lidar to see those pedestrians and avoid them, especially at night." However, the augmented radar sensor suite would be able to detect obstacles in the LiDAR blind spot.[49]

Distraction

On Thursday, June 21, the Tempe Police Department released a detailed report along with media captured after the collision, including an audio recording of the 911 call made by the safety driver, Rafaela Vasquez, and an initial on-scene interview with a responding officer, captured by body worn video. After the crash, police obtained search warrants for Vasquez's cellphones as well as records from the video streaming services Netflix, YouTube, and Hulu. The investigation concluded that because the data showed she was streaming The Voice over Hulu at the time of the collision, and the driver-facing camera in the Volvo showed "her face appears to react and show a smirk or laugh at various points during the time she is looking down", Vasquez may have been distracted from her primary job of monitoring road and vehicle conditions.[50] Tempe police concluded the crash was "entirely avoidable"[51] and faulted Vasquez for her "disregard for assigned job function to intervene in a hazardous situation".[50]

Records indicate that streaming began at 9:16 pm and ended at 9:59 pm. Based on an examination of the video captured by the driver-facing camera, Vasquez was looking down toward her right knee 166 times for a total of 6 minutes, 47 seconds[50] during the 21 minutes, 48 seconds preceding the crash.[52] Just prior to the crash, Vasquez was looking at her lap for 5.3 seconds; she looked up half a second before the impact.[51][53] Vasquez stated in her post-crash interview with the NTSB that she had been monitoring system messages on the center console, and that she did not use either one of her cell phones until she called 911.[16] According to an unnamed Uber source, safety drivers are not responsible for monitoring diagnostic messages.[54] Vasquez also told responding police officers she kept her hands near the steering wheel in preparation to take control if required, which contradicted the driver-facing video, which did not show her hands near the wheel.[50] Police concluded that given the same conditions, Herzberg would have been visible to 85% of motorists at a distance of 143 feet (44 m), 5.7 seconds before the car struck Herzberg. According to the police report, Vasquez should have been able to apply the brakes at least 0.57 seconds sooner, which would have provided Herzberg sufficient time to pass safely in front of the car.[52]

The police report was turned over to the Yavapai County Attorney's Office for review of possible manslaughter charges.[50] The Maricopa County Attorney's Office recused itself from prosecution over a potential conflict of interest, as it had earlier participated with Uber in a March 2016 campaign against drunk driving.[55] On March 4, 2019, Yavapai County Attorney released a letter indicating there is "no basis for criminal liability" against Uber Corporation;[56][57] that potential charges against the driver should be further investigated by Maricopa County Attorney; and that the Tempe Police Department should analyze the case to gather additional evidence.

Other factors

According to the preliminary report of the collision released by the NTSB, Herzberg had tested positive for methamphetamine and marijuana in a toxicology test carried out after the collision.[16] Residual toxicology itself does not establish if or when she was under their influence, and hence an actual factor.[58] Inhibited faculties can hypothetically factor into one's relative ability for last-minute self-preservation. However, her mere presence on the roadway far in the distance ahead of the car was the factor which invoked the machine's duty to brake;[28] the common legal duty to avoid her and other objects being general and preexisting.[30][33]

On May 24, NTSB released a preliminary incident report, the news release saying that Herzberg "was dressed in dark clothing, did not look in the direction of the vehicle... crossed... in a section not directly illuminated by lighting... entered the roadway from a brick median, where signs...warn pedestrians to use a crosswalk... 360 feet north." Six seconds before impact, the vehicle was traveling 43 mph (69 km/h), and the system identified the woman and bicycle as an unknown object, next as a vehicle, then as a bicycle.[59] At 1.3 seconds before hitting the pedestrian and her bike, the system flagged the need for emergency braking, but it failed to do so, as the car hit Herzberg at 39 mph (63 km/h).[60]

The forward-looking Uber dashcam did not pick up Herzberg until approximately 1.4 seconds before the collision, suggesting (as the sheriff did) that the crash may have been completely unavoidable even if Vasquez hadn't been distracted in the seconds leading up to the crash.[61]

However, night-time video shot by other motorists in the days following the crash, plus their comments, suggest that the area may have been better illuminated than the dashcam footage, viewed in isolation would suggest. This raises the possibility that Herzberg's appearing so late in the Uber video could merely be an indication that the camera had insufficient sensitivity or was otherwise poorly calibrated for the environment and setting in which it was operating. If these crowd-sourced re-creations are indeed representative of the visibility conditions on the actual night that the crash occurred, then Herzberg would have been visible to Vasquez as soon as there was a clear sight line had Vasquez only been looking ahead, refuting the assertion that the crash was unavoidable.[62]

Complicating things even further, there is evidence that suggests the discrepancies in visibility between the dashcam footage and the civilian re-creation submissions are not at all invented or illusory, but are, instead, real phenomena whose progenitor is purported to be the set of severely under-powered headlights installed on the car Vasquez was monitoring.[62] While all of these potential scenarios will likely affect any charging decisions and/or other legal actions (if they materialize at all), none currently have any objective validation or otherwise meaningful support, especially in relation to one another.

Coordination with state government

Prior to the fatal incident, Arizona Governor Doug Ducey had encouraged Uber to enter the state.[6] He signed Executive Order 2015-09 on August 25, 2015, entitled "Self-Driving Vehicle Testing and Piloting in the State of Arizona; Self-Driving Vehicle Oversight Committee", establishing a welcoming attitude to autonomous vehicle testing and an oversight committee for self-driving vehicles.[63][64] According to Ducey's office, the committee, which consists of eight state employees appointed by the governor, has met twice since it was formed.[6]

In December 2016, Ducey had released a statement welcoming Uber's autonomous cars: "Arizona welcomes Uber self-driving cars with open arms and wide open roads. While California puts the brakes on innovation and change with more bureaucracy and more regulation, Arizona is paving the way for new technology and new businesses."[65] Emails between Uber and the office of the governor showed that Ducey was informed that the testing of self-driving vehicles would begin in August 2016, several months ahead of the official announcement welcoming Uber in December.[6] On March 1, 2018, Ducey signed Executive Order (XO) 2018-04, outlining regulations for autonomous vehicles. Notably, XO 2018-04 requires the company testing self-driving cars to provide a written statement that "the fully autonomous vehicle will achieve a minimal risk condition" if a failure occurs.[66]

Aftermath

Uber

After the collision that killed Herzberg on March 18, 2018, Uber ceased testing self-driving vehicles in all four cities (Tempe, San Francisco , Pittsburgh, and Toronto) where it had deployed them.[5] On March 26, Governor Ducey sent a letter to Uber CEO Dara Khosrowshahi, suspending Uber's testing of self-driving cars in the state. In the letter, Ducey stated "As governor, my top priority is public safety. Improving public safety has always been the emphasis of Arizona's approach to autonomous vehicle testing, and my expectation is that public safety is also the top priority for all who operate this technology in the state of Arizona."[67] Uber also announced it would not renew its permit to test self-driving cars in California after the California Department of Motor Vehicles wrote to inform Uber that its permit would expire on March 31, and "any follow-up analysis or investigations from the recent crash in Arizona" would have to be addressed before the permit could be renewed.[7] Uber acknowledged that mistakes were made in its pursuit to ultimately create a safer driving environment.[35][68]

Later in the year, Uber issued a reflective 70-page safety report[35] in which Uber stated the potential for its self-driving cars to be safer than those driven by humans,[69] however some of their employees worry that Uber is taking shortcuts to hit internal milestones.[35] To be legal in all states[70] for private use, or anywhere at the commercial level,[32][33] the technology must hard code assured clear distance ahead driving.[30][31][71]

Uber returned their self-driving cars to the roads in public testing in Pittsburgh, Pennsylvania, on December 20, 2018. Uber said they received authorization from the Pennsylvania Department of Transportation. Uber said they were also pursuing the same with cars on roads in San Francisco, California , and Toronto, Ontario.[72][73] In December 2020, Uber sold its Advanced Technologies Group, which was researching automated driving systems, to Aurora Innovation.[74]

Other companies

The incident also caused other companies to temporarily cease road testing of self-driving vehicles. Nvidia CEO Jensen Huang has stated "We don't know that we would do anything different, but we should give ourselves time to see if we can learn from that incident."[75]

Legal actions

Legal woes for Uber were among the collision fallout. Herzberg's daughter retained the law firm Bellah Perez,[21] and together with the husband quickly reached an undisclosed settlement on March 28 while local and federal authorities continued their investigation.[76] Herzberg's mother, father, and son also retained legal counsel.[77] While a confidential settlement buried the liability issue, it suggested a sufficient legal cause of action. The abundance of event data recorders left few questions of fact for a jury to decide.[78]

Although the Yavapai County Attorney declined to charge Uber with a criminal violation in 2019 for the death of Herzberg,[79] a Maricopa County grand jury indicted the safety driver on one count of negligent homicide in 2020.[80] Her trial was planned for February 2021,[81] but has been delayed because the case was designated "complex" and the discovery process is ongoing.[82] In July 2023 Vasquez pleaded guilty to one count of endangerment, a reduced charge, and was sentenced to three years of probation.[83]

Regulation

The National Highway Traffic Safety Administration and the American Automobile Association had previously identified nighttime driving as an area for safety improvement.[84][85][86] This follows similar changes in attitudes against tolerating drunk driving, starting in the late 1970s through the 1990s,[87][88] and has occurred in concert with a cultural shift towards active lifestyles and multi-modal use of roadways which has been formally adopted by the National Association of City Transportation Officials.

See also

  • Mary Ward, the first person known to have been killed by an automobile
  • Bridget Driscoll, the first pedestrian death by automobile in Great Britain
  • Henry H. Bliss, the first automobile death in the Americas
  • Robert Williams, the first person known to be killed by a robot
  • Thomas Selfridge, the first person to die in an airplane crash

References

  1. ↑ 1.0 1.1 1.2 1.3 "In Memoriam: Elaine Marie Herzberg". http://www.sonoranskiesmortuaryaz.com/memsol.cgi?user_id=2089722. 
  2. ↑ 2.0 2.1 2.2 Will Pavia (March 21, 2018). "Driverless Uber car 'not to blame' for woman's death". The Times. https://www.thetimes.co.uk/article/driverless-uber-car-not-to-blame-for-woman-s-death-klkbt7vf0. 
  3. ↑ 3.0 3.1 Wakabayashi, Daisuke (March 19, 2018). "Self-Driving Uber Car Kills Pedestrian in Arizona, Where Robots Roam". The New York Times. https://www.nytimes.com/2018/03/19/technology/uber-driverless-fatality.html. 
  4. ↑ "Video shows moment of fatal Uber crash". BBC News. March 22, 2018. https://www.bbc.co.uk/news/world-us-canada-43497364. 
  5. ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 Said, Carolyn (March 21, 2018). "Video shows Uber robot car in fatal accident did not try to avoid woman". San Francisco Chronicle. https://www.sfgate.com/business/article/Uber-video-shows-robot-car-in-fatal-accident-did-12771938.php. 
  6. ↑ 6.0 6.1 6.2 6.3 Harris, Mark (March 28, 2018). "Exclusive: Arizona governor and Uber kept self-driving program secret, emails reveal". The Guardian. https://www.theguardian.com/technology/2018/mar/28/uber-arizona-secret-self-driving-program-governor-doug-ducey. 
  7. ↑ 7.0 7.1 Carolyn Said (March 27, 2018). "Uber puts the brakes on testing robot cars in California after Arizona fatality". San Francisco Chronicle. https://www.sfchronicle.com/business/article/Uber-pulls-out-of-all-self-driving-car-testing-in-12785490.php. 
  8. ↑ Hawkins, Andrew J. (2018-12-20). "Uber's self-driving cars return to public roads for the first time since fatal crash" (in en-US). https://www.theverge.com/2018/12/20/18148946/uber-self-driving-car-return-public-road-pittsburgh-crash. 
  9. ↑ "USA: Uber critiqué pour un accident fatal en 2018" (in en). Reuters. 2019-11-20. https://www.reuters.com/article/usa-uber-idFRKBN1XU0IC. 
  10. ↑ "Uber's self-driving operator charged over fatal crash" (in en-GB). BBC News. 2020-09-16. https://www.bbc.com/news/technology-54175359. 
  11. ↑ "Self-driving Uber kills Arizona woman in first fatal crash involving pedestrian". The Guardian. https://www.theguardian.com/technology/2018/mar/19/uber-self-driving-car-kills-woman-arizona-tempe. 
  12. ↑ "Uber halts self-driving car tests after death". BBC. https://www.bbc.co.uk/news/business-43459156. 
  13. ↑ Vlasic, Bill; Boudette, Neal E. (June 30, 2016). "Self-Driving Tesla Was Involved in Fatal Crash, U.S. Says". The New York Times. https://www.nytimes.com/2016/07/01/business/self-driving-tesla-fatal-crash-investigation.html. "the driver of a Tesla Model S electric sedan was killed in an accident when the car was in self-driving mode" 
  14. ↑ Kunkle, Fredrick (March 22, 2018). "Fatal crash with self-driving car was a first — like Bridget Driscoll's was 121 years ago with one of the first cars". The Washington Post. https://www.washingtonpost.com/news/tripping/wp/2018/03/22/fatal-crash-with-self-driving-car-was-a-first-like-bridget-driscolls-was-121-years-ago-with-one-of-the-first-cars/. 
  15. ↑ Umar Zakir Abdul, Hamid (2018). "A review on threat assessment, path planning and path tracking strategies for collision avoidance systems of autonomous vehicles". International Journal of Vehicle Autonomous Systems 14 (2). https://www.researchgate.net/publication/328707195. Retrieved 21 July 2019. 
  16. ↑ 16.00 16.01 16.02 16.03 16.04 16.05 16.06 16.07 16.08 16.09 16.10 "Preliminary Report – Highway – HWY18MH010". National Transportation Safety Board. May 24, 2018. https://www.ntsb.gov/investigations/AccidentReports/Reports/HWY18MH010-prelim.pdf. 
  17. ↑ Bensinger, Greg; Higgins, Tim (March 22, 2018). "Video Shows Moments Before Uber Robot Car Rammed Into Pedestrian". The Wall Street Journal. https://www.wsj.com/articles/video-shows-final-seconds-before-fatal-uber-self-driving-car-crash-1521673182. 
  18. ↑ "Self-driving Uber car hits, kills pedestrian in Tempe". ABC 15 Arizona. March 19, 2018. https://www.abc15.com/news/region-southeast-valley/tempe/tempe-police-investigating-self-driving-uber-car-involved-in-crash-overnight. 
  19. ↑ 19.0 19.1 19.2 19.3 Stern, Ray (March 19, 2018). "Tempe Police: Uber Self-Driving Car Didn't Brake 'Significantly' Before Killing Pedestrian". http://www.phoenixnewtimes.com/news/cops-uber-self-driving-car-didnt-brake-much-in-arizona-pedestrian-death-10247629. 
  20. ↑ White, Jeremy (March 20, 2018). "Police identify first pedestrian killed by self-driving car". The Independent. https://www.independent.co.uk/news/world/americas/selfdriving-car-death-autonomous-vehicle-crash-tempe-arizona-uber-elaine-herzberg-a8264311.html. 
  21. ↑ 21.0 21.1 21.2 21.3 21.4 Randazzo, Ryan (March 22, 2018). "What went wrong with Uber's Volvo in fatal crash? Experts shocked by technology failure". The Arizona Republic. https://www.azcentral.com/story/money/business/tech/2018/03/22/what-went-wrong-uber-volvo-fatal-crash-tempe-technology-failure/446407002/. 
  22. ↑ Garcia, Ureil J. (May 31, 2018). "Maricopa County Attorney's Office cites conflict in Tempe Uber death case". The Republic. https://www.azcentral.com/story/news/local/tempe/2018/05/31/maricopa-county-attorney-cites-conflict-tempe-uber-death-case/662072002/. 
  23. ↑ Gibson, Kate (March 20, 2018). "Arizona police: Pedestrian stepped in front of self-driving Uber before crash". https://www.cbsnews.com/news/uber-self-driving-car-crash-arizona-police-say-pedestrian-stepped-in-front/. 
  24. ↑ Walker, Alissa (March 20, 2018). "This is the moment when we decide that human lives matter more than cars". https://www.curbed.com/transportation/2018/3/20/17142090/uber-fatal-crash-driverless-pedestrian-safety. 
  25. ↑ Griggs, Troy (March 20, 2018). "How a Self-Driving Uber Killed a Pedestrian in Arizona" (in en-US). The New York Times. ISSN 0362-4331. https://www.nytimes.com/interactive/2018/03/20/us/self-driving-uber-pedestrian-killed.html. 
  26. ↑ "NTSB UPDATE: Uber Crash Investigation" (Press release). National Transportation Safety Board. March 21, 2018. Archived from the original on August 28, 2019. Retrieved March 27, 2018.
  27. ↑ See calculation method under Braking distance.
  28. ↑ 28.0 28.1 Isaac, Mike; Wakabayashi, Daisuke; Conger, Kate (August 19, 2018). "After Fatal Accident, Uber's Vision of Self-Driving Cars Begins to Blur." (in en-US) (print). The New York Times: p. B1. ISSN 0362-4331. https://www.nytimes.com/2018/08/19/technology/uber-self-driving-cars.html. "preliminary findings from federal regulators investigating the crash confirmed what many self-driving car experts suspected: Uber's self-driving car should have detected a pedestrian with enough time to stop, but it failed to do so." 
  29. ↑ Krishe, Tom; Billeaud, Jacques (June 22, 2018). "Uber driver streaming 'The Voice' just before fatal Arizona crash, report says". Chicago Tribune. Associated Press. ISSN 1085-6706. http://www.chicagotribune.com/business/ct-biz-uber-self-driving-car-crash-20180622-story.html. ""This crash would not have occurred if Vasquez would have been monitoring the vehicle and roadway conditions and was not distracted," the report says. A crash report also indicated that the self-driving vehicle was traveling too fast for the road conditions." 
  30. ↑ 30.0 30.1 30.2 Lawyers Cooperative Publishing. New York Jurisprudence. Automobiles and Other Vehicles. Miamisburg, OH: LEXIS Publishing. p. § 720. OCLC 321177421. http://legalsolutions.thomsonreuters.com/law-products/Legal-Encyclopedias/New-York-Jurisprudence-2d/p/100029357. Retrieved July 11, 2018. "It is negligence as a matter of law to drive a motor vehicle at such a rate of speed that it cannot be stopped in time to avoid an obstruction discernible within the driver's length of vision ahead of him. This rule is known generally as the `assured clear distance ahead' rule * * * In application, the rule constantly changes as the motorist proceeds, and is measured at any moment by the distance between the motorist's vehicle and the limit of his vision ahead, or by the distance between the vehicle and any intermediate discernible static or forward-moving object in the street or highway ahead constituting an obstruction in his path. Such rule requires a motorist in the exercise of due care at all times to see, or to know from having seen, that the road is clear or apparently clear and safe for travel, a sufficient distance ahead to make it apparently safe to advance at the speed employed." 
  31. ↑ 31.0 31.1 Leibowitz, Herschel W.; Owens, D. Alfred; Tyrrell, Richard A. (1998). "The assured clear distance ahead rule: implications for nighttime traffic safety and the law". Accident Analysis & Prevention 30 (1): 93–99. doi:10.1016/S0001-4575(97)00067-5. PMID 9542549. "The assured clear distance ahead (ACDA) rule holds the operator of a motor vehicle responsible to avoid collision with any obstacle that might appear in the vehicle's path.". 
  32. ↑ 32.0 32.1 "Section 2 – Driving Safely". Commercial Driver License Manual 2005. United States Department of Transportation. July 2014. pp. 2–15, 2–19, 2–26, 13–1. https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/docs/2005%20CDL%20Driver%20Manual%20-July%202014%20-%20FINAL.pdf. Retrieved October 4, 2018. "[pg 2-15] 2.6.4 – Speed and Distance Ahead: You should always be able to stop within the distance you can see ahead. Fog, rain, or other conditions may require that you slowdown to be able to stop in the distance you can see. ... [pg 2-19] 2.8.3 – Drivers Who Are Hazards: Vehicles may be partly hidden by blind intersections or alleys. If you only can see the rear or front end of a vehicle but not the driver, then he or she can't see you. Be alert because he/she may back out or enter into your lane. Always be prepared to stop. ... [pg 2-26] 2.11.4 – Vehicle Factors: Headlights. At night your headlights will usually be the main source of light for you to see by and for others to see you. You can't see nearly as much with your headlights as you see in the daytime. With low beams you can see ahead about 250 feet and with high beams about 350–500 feet. You must adjust your speed to keep your stopping distance within your sight distance. This means going slowly enough to be able to stop within the range of your headlights. ... [pg 13-1] 13.1.2 – Intersections As you approach an intersection: Check traffic thoroughly in all directions. Decelerate gently. Brake smoothly and, if necessary, change gears. If necessary, come to a complete stop (no coasting) behind any stop signs, signals, sidewalks, or stop lines maintaining a safe gap behind any vehicle in front of you. Your vehicle must not roll forward or backward. When driving through an intersection: Check traffic thoroughly in all directions. Decelerate and yield to any pedestrians and traffic in the intersection. Do not change lanes while proceeding through the intersection. Keep your hands on the wheel." 
  33. ↑ 33.0 33.1 33.2 "49 CFR 392.14 – Hazardous conditions; extreme caution.". US Code of Federal Regulations. https://www.law.cornell.edu/cfr/text/49/392.14. Retrieved December 14, 2018. "Extreme caution in the operation of a commercial motor vehicle shall be exercised when hazardous conditions, such as those caused by snow, ice, sleet, fog, mist, rain, dust, or smoke, adversely affect visibility or traction. Speed shall be reduced when such conditions exist. If conditions become sufficiently dangerous, the operation of the commercial motor vehicle shall be discontinued and shall not be resumed until the commercial motor vehicle can be safely operated. Whenever compliance with the foregoing provisions of this rule increases hazard to passengers, the commercial motor vehicle may be operated to the nearest point at which the safety of passengers is assured.". 
  34. ↑ "VA. § 46.2-880. Tables of speed and stopping distances.". State of Virginia. https://law.lis.virginia.gov/vacode/46.2-880/. "an average baseline for motor vehicle stopping distances...for a vehicle in good condition and...on a level, dry stretch of highway, free from loose material." 
  35. ↑ 35.0 35.1 35.2 35.3 Wakabayashi, Daisuke; Conger, Kate (December 5, 2018). "Uber's Self-Driving Cars Are Set to Return in a Downsized Test" (in en-US). The New York Times. ISSN 0362-4331. https://www.nytimes.com/2018/12/05/technology/uber-self-driving-cars.html. "The cars have reacted more slowly than human drivers and struggled to pass so-called track validation tests...Dara Khosrowshahi, the chief executive, acknowledged errors in Uber's earlier driverless car efforts. "We did screw up," he said in comments provided by Uber...as recently as a few weeks ago, the company's autonomous vehicle unit, Uber Advanced Technologies Group, or A.T.G., was still experiencing track testing "failures" on different versions of its software, according internal company emails. To match the reaction time of a human driver at 25 m.p.h., the cars needed to drive "20% slower than a human," Brandon Basso, a director at A.T.G., said in a Nov. 1 email. Even at slower speeds, the cars were passing only 82 percent of track tests, according to company documents...a test in early November ran Uber's vehicles through more than 70 categories at 25 m.p.h., they failed in 10 of them, including being slow to recognize another car that didn't yield." 
  36. ↑ Garcia, Uriel J.; Randazzo, Ryan (March 21, 2018). "Video shows moments before fatal Uber crash in Tempe". The Arizona Republic. https://www.azcentral.com/story/news/local/tempe-breaking/2018/03/21/video-shows-moments-before-fatal-uber-crash-tempe/447648002/. 
  37. ↑ Garcia, Uriel J.; Bland, Karina (March 20, 2018). "Tempe police chief: Fatal Uber crash likely 'unavoidable' for any kind of driver". The Arizona Republic. https://www.azcentral.com/story/news/local/tempe/2018/03/20/tempe-police-chief-fatal-uber-crash-pedestrian-likely-unavoidable/442829002/. 
  38. ↑ Schmitt, Angie (22 March 2018). "Video of the Fatal Uber Self-Driving Car Crash Upends the Victim-Blaming Narrative". https://usa.streetsblog.org/2018/03/22/video-of-the-fatal-uber-self-driving-car-crash-upends-the-victim-blaming-narrative/. 
  39. ↑ Stern, Ray. "Tempe Police Chief Regrets Premature Blabbing About Self-Driving Uber Crash" (in en). Phoenix New Times. https://www.phoenixnewtimes.com/news/tempe-police-chief-moir-ryff-uber-autonomous-driving-10556991. 
  40. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named SFC-180319
  41. ↑ "Former Uber Backup Driver: 'We Saw This Coming'" (in en-US). CityLab. https://www.citylab.com/transportation/2018/03/former-uber-backup-driver-we-saw-this-coming/556427/. 
  42. ↑ Farzan, Antonia Noori (March 22, 2018). "Self-Driving Uber Crash Highlights Bigger Problem: Metro Phoenix Is Hell for Pedestrians". Phoenix New Times. http://www.phoenixnewtimes.com/news/self-driving-uber-crash-highlights-bigger-problem-metro-phoenix-is-hell-for-pedestrians-10251695. 
  43. ↑ "A.R.S. 28-793. Crossing at other than crosswalk". Arizona State Legislature. https://www.azleg.gov/ars/28/00793.htm. 
  44. ↑ Gonzales, Richard (November 7, 2019). "Feds Say Self-Driving Uber SUV Did Not Recognize Jaywalking Pedestrian In Fatal Crash" (in en). https://www.npr.org/2019/11/07/777438412/feds-say-self-driving-uber-suv-did-not-recognize-jaywalking-pedestrian-in-fatal-. 
  45. ↑ Randazzo, Ryan (November 8, 2017). "Here are 6 reasons Uber is betting big on Arizona". The Arizona Republic. https://www.azcentral.com/story/money/business/tech/2017/11/08/uber-bets-big-phoenix-arizona-driverless-cars-support-center-6-reasons-why/800295001/. 
  46. ↑ Golson, Jordan (August 18, 2016). "Volvo and Uber ink deal to develop 'base vehicles' for autonomous cars". The Verge. https://www.theverge.com/2016/8/18/12541672/uber-volvo-partnership-autonomous-self-driving-car. 
  47. ↑ Said, Carolyn (September 14, 2016). "Uber's robot taxis hit the road in Pittsburgh". San Francisco Chronicle. https://www.sfchronicle.com/business/article/Uber-s-robot-taxis-hit-the-road-in-Pittsburgh-9220825.php. 
  48. ↑ Harding, Xavier (September 14, 2016). "We Got Behind The Wheel Of Uber's Self-Driving Car". Popular Science. https://www.popsci.com/uber-self-driving-car-pittsburgh-driverless. Retrieved March 28, 2018. 
  49. ↑ Somerville, Heather; Lienert, Paul; Sage, Alexandria (March 27, 2018). "Uber's use of fewer safety sensors prompts questions after Arizona crash". Reuters. https://www.reuters.com/article/us-uber-selfdriving-sensors-insight/ubers-use-of-fewer-safety-sensors-prompts-questions-after-arizona-crash-idUSKBN1H337Q. 
  50. ↑ 50.0 50.1 50.2 50.3 50.4 Coppola, Chris; Frank, BrieAnna J (June 21, 2018). "Report: Uber driver was watching 'The Voice' moments before fatal Tempe crash". AZ Central (USA Today). https://www.azcentral.com/story/news/local/tempe-breaking/2018/06/21/uber-self-driving-car-crash-tempe-police-elaine-herzberg/724344002/. "The documents indicate police are seeking manslaughter charges against Vasquez...."This crash would not have occurred if Vasquez would have been monitoring the vehicle and roadway conditions and was not distracted," the report says....A crash report indicated that the self-driving vehicle was traveling too fast for the road conditions." 
  51. ↑ 51.0 51.1 Somerville, Heather; Shepardson, David (June 21, 2018). "Uber car's 'safety' driver streamed TV show before fatal crash: police". Reuters. https://www.reuters.com/article/us-uber-selfdriving-crash/uber-cars-safety-driver-streamed-tv-show-before-fatal-crash-police-idUSKBN1JI0LB. 
  52. ↑ 52.0 52.1 Stern, Ray (June 21, 2018). "Self-Driving Uber Crash 'Avoidable,' Driver's Phone Playing Video Before Woman Struck". Phoenix New Times. http://www.phoenixnewtimes.com/news/self-driving-uber-crash-avoidable-drivers-phone-playing-video-before-woman-struck-10543284. 
  53. ↑ Lee, Timothy B. (June 22, 2018). "Police: Uber driver was streaming Hulu just before fatal self-driving crash". ars Technica. https://arstechnica.com/cars/2018/06/police-uber-driver-was-streaming-hulu-just-before-fatal-self-driving-car-crash/. 
  54. ↑ Stern, Ray (May 24, 2018). "NTSB Report Suggests Uber's Backup Driver More at Fault Than Car in Fatal Crash". Phoenix New Times. http://www.phoenixnewtimes.com/news/ntsb-report-uber-backup-driver-fatal-self-driving-crash-tempe-10453507. 
  55. ↑ Garcia, Uriel J.. "Maricopa County Attorney's Office cites conflict in Tempe Uber death case". The Republic. https://www.azcentral.com/story/news/local/tempe/2018/05/31/maricopa-county-attorney-cites-conflict-tempe-uber-death-case/662072002/. 
  56. ↑ Buono, Bianca (2019-03-05). "Yavapai County Attorney's Office concludes Uber is not criminally liable in last year's deadly crash involving a self-driving Uber vehicle in Tempe #12Newspic.twitter.com/wuzobbwZ3Q" (in en). https://twitter.com/BiancaBuono/status/1103053274297462784. 
  57. ↑ "No criminal charges for Uber in Tempe death; police asked to further investigate operator" (in en). https://www.azcentral.com/story/news/local/tempe/2019/03/05/no-criminal-charges-uber-fatal-tempe-crash-tempe-police-further-investigate-driver/3071369002/. 
  58. ↑ Bichell, Rae Ellen (July 30, 2017). "Scientists Still Seek A Reliable DUI Test For Marijuana". All Things Considered (National Public Radio). https://www.npr.org/sections/health-shots/2017/07/30/523004450/scientists-still-seek-a-reliable-dui-test-for-marijuana. "Though a blood test exists that can detect some of marijuana's components, there is no widely accepted, standardized amount in the breath or blood that gives police or courts or anyone else a good sense of who is impaired. ... "And it shocked everyone, including ourselves, that we could measure, in some of these individuals, THC in the blood for 30 days," says Marilyn Huestis, a toxicologist with the University of Maryland School of Medicine who recently retired from leading a lab at the National Institute on Drug Abuse. ... Conversely, another study showed that people who weren't regular consumers could smoke a joint right in front of researchers and yet show no evidence of cannabis in their blood. So, in addition to being invasive and cumbersome, the blood test can be misleading and a poor indicator of whatever is happening in the brain." 
  59. ↑ "Preliminary Report Released for Crash Involving Pedestrian, Uber Technologies, Inc., Test Vehicle" (in en-us). https://www.ntsb.gov/news/press-releases/Pages/NR20180524.aspx. 
  60. ↑ "How Uber's Self-Driving System Failed to Brake and Avoid Killing Elaine Herzberg" (in en-US). Streetsblog USA. May 24, 2018. https://usa.streetsblog.org/2018/05/24/how-ubers-self-driving-system-failed-to-brake-and-avoid-killing-elaine-herzberg/. 
  61. ↑ @TempePolice (March 21, 2018). "Tempe Police Vehicular Crimes Unit is actively investigating the details of this incident that occurred on March 18th. We will provide updated information regarding the investigation once it is available.". https://twitter.com/TempePolice/status/976585098542833664. 
  62. ↑ 62.0 62.1 Lee, Timothy B. (March 23, 2018). "Police chief said Uber victim "came from the shadows"—don't believe it" (in en-US). Ars Technica. https://arstechnica.com/cars/2018/03/police-chief-said-uber-victim-came-from-the-shadows-dont-believe-it/. 
  63. ↑ Ducey, Douglas A. (August 25, 2015). "Self-Driving Vehicle Testing and Piloting in the State of Arizona; Self-Driving Vehicle Oversight Committee". Office of the Governor Doug Ducey. https://azgovernor.gov/file/2660/download?token=nLkPLRi1. 
  64. ↑ Kang, Cecilia (November 11, 2017). "Where Self-Driving Cars Go to Learn". The New York Times. https://www.nytimes.com/2017/11/11/technology/arizona-tech-industry-favorite-self-driving-hub.html. 
  65. ↑ "Governor Ducey Tells Uber 'CA May Not Want You, But AZ Does'" (Press release). Office of the Governor Doug Ducey. December 22, 2016. Archived from the original on March 27, 2018. Retrieved March 27, 2018.
  66. ↑ Ducey, Douglas A. (August 25, 2015). "Advancing Autonomous Vehicle Testing and Operating; Prioritizing Public Safety". Office of the Governor Doug Ducey. https://azgovernor.gov/file/2660/download?token=6jUxyR_C. [yes|permanent dead link|dead link}}]
  67. ↑ Randazzo, Ryan (March 26, 2018). "Arizona Gov. Doug Ducey suspends testing of Uber self-driving cars". The Arizona Republic. https://www.azcentral.com/story/news/local/tempe-breaking/2018/03/26/doug-ducey-uber-self-driving-cars-program-suspended-arizona/460915002/. 
  68. ↑ Wakabayashi, Daisuke (March 23, 2018). "Uber's Self-Driving Cars Were Struggling Before Arizona Crash". The New York Times. https://www.nytimes.com/2018/03/23/technology/uber-self-driving-cars-arizona.html. "A video shot from the vehicle's dashboard camera showed the safety driver looking down, away from the road. It also appeared that the driver's hands were not hovering above the steering wheel, which is what drivers are instructed to do so they can quickly retake control of the car. ... Uber moved from two employees in every car to one. The paired employees had been splitting duties — one ready to take over if the autonomous system failed, and another to keep an eye on what the computers were detecting. The second person was responsible for keeping track of system performance as well as labeling data on a laptop computer. Mr. Kallman, the Uber spokesman, said the second person was in the car for purely data related tasks, not safety. ... When Uber moved to a single operator, some employees expressed safety concerns to managers, according to the two people familiar with Uber's operations. They were worried that going solo would make it harder to remain alert during hours of monotonous driving." 
  69. ↑ "Uber ATG Safety Report". Uber Advanced Technologies Group. https://uber.app.box.com/v/UberATGSafetyReport. "Self-driving vehicles hold the potential to drive more safely than a human driver. Computers can look in all directions at once, and they don't get distracted, fatigued, or impaired. (pg 13)" 
  70. ↑ * "Code § 321.285 Speed restrictions.". The State of Iowa. https://www.legis.iowa.gov/DOCS/IACODE/2001/321/285.html. "Any person driving a motor vehicle on a highway shall drive the same at a careful and prudent speed not greater than nor less than is reasonable and proper, having due regard to the traffic, surface, and width of the highway and of any other conditions then existing, and no person shall drive any vehicle upon a highway at a speed greater than will permit the person to bring it to a stop within the assured clear distance ahead, such driver having the right to assume, however, that all persons using said highway will observe the law." 
  71. ↑
    • Bove v. Beckman, 236 Cal. App. 2d 555 (California Appellate Court Aug 16, 1965) (""A person driving an automobile at 65 miles an hour on a highway on a dark night with his lights on low beam affording a forward vision of only about 100 feet was driving at a negligent and excessive speed which was inconsistent with any right of way that he might otherwise have had." (CA Reports Official Headnote #[8])"). See California Official Reports: Online Opinions
    • Ruth v. Vroom, 245 Mich. 88 (Supreme Court of Michigan December 4, 1928) ("It is settled in this State that it is negligence as a matter of law to drive an automobile at night at such speed that it cannot be stopped within the distance that objects can be seen ahead of it; and, if a driver's vision is obscured by the lights of an approaching car, it is his duty to slacken speed and have his car under such control that he can stop immediately if necessary. ... The rule adopted by this court does not raise merely a rebuttable presumption of negligence. It is a rule of safety. ... It is not enough that a driver be able to begin to stop within the range of his vision, or that he use diligence to stop after discerning an object. The rule makes no allowance for delay in action.").
    • Gleason v. Lowe, 232 Mich. 300 (Supreme Court of Michigan October 1, 1925) ("...every man must operate his automobile so that he can stop it within the range of his vision, whether it be daylight or darkness. It makes no difference what may obscure his vision, whether it be a brick wall or the darkness of nightfall. ... He must ... be able to see where he is going, and if his range of vision is 50 feet, if he can see 50 feet ahead of him, he must regulate his speed so that he can stop in a distance of 50 feet; if he can see 20 feet ahead of him, he must regulate his speed so that he can stop within 20 feet, and so on.").
    • Morris v. Jenrette Transport Co., 235 N.C. 568 (Supreme Court of North Carolina May 21, 1952) ("It is not enough that the driver of plaintiff's automobile be able to begin to stop within the range of his lights, or that he exercise due diligence after seeing defendants' truck on the highway. He should have so driven that he could and would discover it, perform the manual acts necessary to stop, and bring the automobile to a complete stop within the range of his lights. When blinded by the lights of the oncoming car so that he could not see the required distance ahead, it was the duty of the driver within such distance from the point of blinding to bring his automobile to such control that he could stop immediately, and if he could not then see, he should have stopped. In failing to so drive he was guilty of negligence which patently caused or contributed to the collision with defendants' truck, resulting in injury to plaintiff."...it was his duty to anticipate presence of others, [...] and hazards of the road, such as disabled vehicle, and, in the exercise of due care, to keep his automobile under such control as to be able to stop within the range of his lights").
    • Demerest v. Travelers Insurance Company, 234 La. 1048, 234 La. 1040 (Supreme Court of Louisiana April 21, 1958) ("the jurisprudence of this state is that: "when visibility is materially impaired because of smoke, mist, dust, etc., a motorist should reduce his rate of speed to such extent and keep his car under such control as to reduce to a minimum the possibility of accident from collision; and as an extreme measure of safety, it is his duty, when visibility ahead is not possible or greatly obscured, to stop his car and remain at a standstill until conditions warrant going forward.").
    • Lindquist v. Thierman, 216 Iowa 170 (Iowa Supreme Court May 15, 1933) ("it is evident that the words "within the assured clear distance ahead", as used in the statute, signify that the operator of the automobile, when driving at night as well as in the day, shall at all times be able to stop his car within the distance that discernible objects may be seen ahead of it.").
    • Page v. Mazzei, 213 Cal. 644 (Supreme Court of California 21 September 1931) ("Where a car has actually entered an intersection before the other approaches it, the driver of the first car has the right to assume that he will be given the right of way and be permitted to pass through the intersection without danger of collision. He has a right to assume that the driver of the other car will obey the law, slow down, and yield the right of way, if slowing down be necessary to prevent a collision. ( Keyes v. Hawley, 100 Cal. App. 53, 60 [279 Pac. 674].) Nor is a plaintiff required to yield the right of way to one a considerable distance away whose duty it is to slow down in crossing an intersection. See Official Reports Opinions Online").
    • Reaugh v. Cudahy Packing Co., 189 Cal. 335 (Supreme Court of California July 27, 1922) ("[The basic speed law] is but a reiteration of the rule, in statutory form, which has always been in force without regard to a statutory promulgation to the effect that drivers or operators of vehicles, and more particularly motor vehicles, must be specially watchful in anticipation of the presence of others at places where other vehicles are constantly passing, and where men, women, and children are liable to be crossing, such as corners at the intersections of streets or other similar places or situations where people are likely to fail to observe an approaching automobile."). See Official Reports Opinions Online
    • Whitelaw v. McGilliard, 179 Cal. 349 (Supreme Court of California December 4, 1918) ("The rule regarding right of way does not impose upon the person crossing the street the duty of assuming that the other will continue across an intersecting street without slowing down, as required by law. See Official Reports Opinions Online").
    • Booth v. Columbia Casualty Company, 227 La. 932 (Supreme Court of Louisiana April 25, 1955) ("The plaintiff having pre-empted the intersection had the right to proceed and under the well settled jurisprudence the automobile which first enters an intersection has the right of way over an approaching automobile and the driver who does not respect this legal right of the automobile which first entered the intersection to proceed through in safety, is negligent, even though the car thereafter entering the intersection is being driven on a right of way street.").
    • Fitts v. Marquis, 127 Me. 75 (Supreme Judicial Court of Maine March 15, 1928) ("If a situation indicate collision, the driver, who can do so by the exercise of ordinary care, should avoid doing injury, though this involve that he waive his right of way. The supreme rule of the road is the rule of mutual forbearance.").
  72. ↑ "Uber Puts First Self-Driving Car Back on the Road Since Death". December 22, 2018. https://www.ttnews.com/articles/uber-puts-first-self-driving-car-back-road-death. 
  73. ↑ "Michael Laris, The Washington Post, December 20, 2018. "Nine months after deadly crash, Uber is testing self-driving cars again in Pittsburgh"". The Washington Post. https://www.washingtonpost.com/transportation/2018/12/20/nine-months-after-deadly-crash-uber-is-testing-self-driving-cars-again-pittsburgh-starting-today/. 
  74. ↑ Domonoske, Camila (December 7, 2020). "After Once Touting Self-Driving Cars, Uber Sells Unit To Refocus On Core Businesses". NPR. https://www.npr.org/2020/12/07/944004278/after-once-touting-self-driving-cars-uber-sells-unit-to-refocus-on-core-business. 
  75. ↑ "Jensen Huang on the Uber Tragedy and Why Nvidia Suspended Testing". IEEE Spectrum. March 30, 2018. https://spectrum.ieee.org/view-from-the-valley/transportation/self-driving/jensen-huang-on-the-uber-tragedy-and-why-nvidia-suspended-testing. 
  76. ↑ Neuman, Scott (March 29, 2018). "Uber Reaches Settlement With Family Of Arizona Woman Killed By Driverless Car". National Public Radio. https://www.npr.org/sections/thetwo-way/2018/03/29/597850303/uber-reaches-settlement-with-family-of-arizona-woman-killed-by-driverless-car. 
  77. ↑ Schwartz, David (March 31, 2018). "More family members of woman killed in Uber self-driving car crash hire lawyer". Reuters. https://www.reuters.com/article/us-autos-selfdriving-uber/more-family-members-of-woman-killed-in-uber-self-driving-car-crash-hire-lawyer-idUSKBN1H700H. 
  78. ↑ Baltimore & Ohio R. Co. v. Goodman, 275 U.S. 66 (Supreme Court of the United States October 31, 1927) ("In an action for negligence, the question of due care is not left to the jury when resolved by a clear standard of conduct which should be laid down by the courts ... If, at the last moment, [he] found himself in an emergency, it was his own fault that he did not reduce his speed earlier or come to a stop.").
  79. ↑ Lee, Timothy B. (March 5, 2019). "Uber escapes criminal charges for 2018 self-driving death in Arizona". ars Technica. https://arstechnica.com/cars/2019/03/arizona-prosecutor-wont-charge-uber-for-2018-self-driving-death/. 
  80. ↑ Lee, Timothy B. (September 15, 2020). "Safety driver in 2018 Uber crash is charged with negligent homicide". ars Technica. https://arstechnica.com/cars/2020/09/arizona-prosecutes-uber-safety-driver-but-not-uber-for-fatal-2018-crash/. 
  81. ↑ "Uber's self-driving operator charged over fatal crash". BBC. 16 September 2018. https://www.bbc.com/news/technology-54175359. 
  82. ↑ Stern, Ray (May 12, 2021). "Trial Delayed for Backup Driver in Fatal Crash of Uber Autonomous Vehicle". Phoenix New Times. https://www.phoenixnewtimes.com/news/uber-crash-arizona-vasquez-herzberg-trial-negligent-homicide-charge-11553424. 
  83. ↑ Shepardson, David (28 July 2023). "Backup driver in 2018 Uber self-driving crash pleads guilty" (in en). Reuters. https://www.reuters.com/business/autos-transportation/backup-driver-2018-uber-self-driving-crash-pleads-guilty-2023-07-28/. 
  84. ↑ Varghese, Cherian; Shankar, Umesh (May 2007). "Passenger Vehicle Occupant Fatalities by Day and Night – A Contrast". National Center for Statistics and Analysis. Washington, DC: National Highway Traffic Safety Administration. https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/810637. "The passenger vehicle occupant fatality rate at nighttime is about three times higher than the daytime rate. ...The data shows a higher percentage of passenger vehicle occupants killed in speeding-related crashes at nighttime." 
  85. ↑ "Traffic Safety Facts: 2013 data". July 2015. http://www-nrd.nhtsa.dot.gov/Pubs/812169.pdf. "motor vehicle crashes in 2013 were the leading cause of death for children age 4 and every age from 16 to 24. ... An average of ... one fatality every 16 minutes. ... The estimated economic cost of all motor vehicle traffic crashes in the United States in 2010 (the most recent year for which cost data is available) was $242 billion. ... When quality of life valuations are considered, the total value of societal harm from motor vehicle crashes in the United States in 2010 was an estimated $836 billion. ... Speeding is one of the most prevalent factors contributing to traffic crashes." 
  86. ↑ McKernan, Megan (13 May 2015). "AAA Tests Shine High-Beam on Headlight Limitations". AAA Automotive Research Center. https://newsroom.aaa.com/2015/05/aaa-tests-shine-high-beam-headlight-limitations/. "AAA's test results suggest that halogen headlights, found in over 80 percent of vehicles on the road today, may fail to safely illuminate unlit roadways at speeds as low as 40 mph (64 km/h). ...high-beam settings on halogen headlights...may only provide enough light to safely stop at speeds of up to 48 mph, leaving drivers vulnerable at highway speeds...Additional testing found that while the advanced headlight technology found in HID and LED headlights illuminated dark roadways 25 percent further than their halogen counterparts, they still may fail to fully illuminate roadways at speeds greater than 45 mph (72 km/h). High-beam settings on these advanced headlights offered significant improvement over low-beam settings, lighting distances of up to 500 feet (equal to 55 mph). Despite the increase, even the most advanced headlights fall 60 percent short of the sight distance that the full light of day provides." 
  87. ↑ Leighton Walter Kille (October 5, 2014). "Transportation safety over time: Cars, planes, trains, walking, cycling". Harvard Kennedy School's Shorenstein Center and the Carnegie-Knight Initiative. http://journalistsresource.org/studies/environment/transportation/comparing-fatality-risks-united-states-transportation-across-modes-time. "Since 1980 the average horsepower of U.S. cars more than doubled, and speed limits have risen significantly, greatly increasing the potential for damage, loss of life and injuries. ... "One might argue that transportation equipment, and in particular the motor vehicle, must be the most dangerous machines that we interact with on a daily basis," the researcher states. "The annual toll in motor vehicle crashes exceeds the deaths resulting from the next most dangerous mechanical device, firearms, by about 40%."" 
  88. ↑ "Travelling Speed and the Risk of Crash Involvement". NHMRC Road Accident Research Unit, The University of Adelaide. p. 54. https://infrastructure.gov.au/roads/safety/publications/1997/pdf/Speed_Risk_1.pdf. "the relative risk of an injury crash when travelling at 65 km/h in a 60 km/h speed limit zone is similar to that associated with driving with a blood alcohol concentration of 0.05 g/100mL. By strange coincidence, if the blood alcohol concentration is multiplied by 100, and the resulting number is added to 60 km/h, the risk of involvement in a casualty crash associated with that travelling speed is almost the same as the risk associated with the blood alcohol concentration. Hence, the risk is similar for 0.05 and 65, as noted; for 0.08 and 68; for .12 and 72, and so on..." 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Biography:Death_of_Elaine_Herzberg&oldid=3409334"