📺 Stream EntrepreneurTV for Free 📺

Uber Self-driving Car Involved in Fatal Crash Couldn't Detect Jaywalkers In findings from the National Transportation Safety Board, the vehicle's system failed to detect pedestrians who were not crossing in a designated crosswalk.

By Steve Dent

entrepreneur daily

This story originally appeared on Engadget

Aaron Josefczyk/Reuters via engadget

Uber's self-driving car that struck and killed a pedestrian in March 2018 had serious software flaws, including the inability to recognize jaywalkers, according to the NTSB. The US safety agency said that Uber's software failed to recognize the 49-year-old victim, Elaine Herzberg, as a pedestrian crossing the street. It didn't calculate that it could potentially collide with her until 1.2 seconds before impact, at which point it was too late to brake.

More surprisingly, the NTSB said Uber's system design "did not include a consideration for jaywalking pedestrians." On top of that, the car initiated a one second braking delay so that the vehicle could calculate an alternative path or let the safety driver take control. (Uber has since eliminated that function in a software update.)

Related: Police Release Footage From Fatal Uber Self-Driving Car Crash

Although the [system] detected the pedestrian nearly six seconds before impact ... it never classified her as a pedestrian, because she was crossing at a location without a crosswalk [and] the system design did not include a consideration for jaywalking pedestrians.

Uber's autonomous test vehicles may have failed to identify roadway hazards in at least two other cases, according to the report. In one case, a vehicle struck a bicycle lane post that had bent into a roadway. In another, a safety driver was forced to take control to avoid an oncoming vehicle and ended up striking a parked car. In the seven months prior to the fatal crash, Uber vehicles were involved in 37 accidents, including 33 in which other vehicles struck the Uber test cars.

When Uber resumed testing in December 2018, it used significantly revised software. According to the NTSB, Uber did a simulation of the new system using sensor data from the fatal Arizona accident. It determined that it would have detected the pedestrian 289 feet before impact and had four seconds to brake before impact at a speed of 43.2 mph. The average stopping distance for a human is about 130 feet at that speed, including reaction time, so it seems likely that the vehicle would have been able to stop in that distance.

Related: Avoid Chatty Drivers With Uber Black 'Quiet Mode'

The NTSB will meet on November 19 to determine the cause of the accident that occurred in Tempe, Arizona in March of 2018. Prosecutors have already absolved Uber of criminal liability, but are still weighing criminal charges against the driver.

Want to be an Entrepreneur Leadership Network contributor? Apply now to join.

Editor's Pick

Business Ideas

63 Small Business Ideas to Start in 2024

We put together a list of the best, most profitable small business ideas for entrepreneurs to pursue in 2024.

Employee Experience & Recruiting

Feed Your Company Spirit with This $200 Restaurant.com eGift Card That's Only $35

Use it at thousands of restaurants around the U.S.

Living

Show Mom You Love Her with Two Dozen Roses for $25

Rose Farmers is offering a limited-time deal on delivered roses for Mother's Day.

Data & Recovery

Get 500GB of Lifetime Cloud Storage for a One-Time $120 Payment

Boost your bottom line by getting an enormous amount of cloud storage for life without recurring fees.

Social Media

How To Start a Youtube Channel: Step-by-Step Guide

YouTube can be a valuable way to grow your audience. If you're ready to create content, read more about starting a business YouTube Channel.

Devices

Stay Focused and Accessible with These $40 Conduction Headphones

These headphones sit on top of your ears, so you can take calls while staying tuned into your surroundings.