ShareThis Page
Uber driver, self-driving software not at fault in Pittsburgh crash, company determines |

Uber driver, self-driving software not at fault in Pittsburgh crash, company determines

| Wednesday, September 20, 2017 5:12 p.m
Nate Smallwood | Tribune-Review
Uber's self-driving car fleet is parked outside the company's office in the Strip District before a test drive for media on Sept. 20, 2017.

An internal investigation by Uber determined that neither its driver nor the self-driving SUV’s software were at fault in a recent crash in Pittsburgh, the company’s head of safety for its autonomous fleet said Wednesday.

Noah Zych, head of system safety, told reporters at the Pittsburgh headquarters of Uber’s Advanced Technology Group, that the company reviews data from any autonomous car involved in a crash as part of its internal investigation.

“We look to make sure, one, that our operators did the right thing in that circumstance, and two, that our software didn’t contribute in any way to the crash,” Zych said. “And in all the incidents that we’ve looked at so far, that has been the case.”

RELATED: Uber unveils second generation self-driving car in Pittsburgh

Uber idled its Pittsburgh fleet of self-driving cars for about three hours Monday after one collided with another car on the South Side. No one was injured, and witnesses said the crash looked like a fender bender.

Police have not released who was at fault in the crash. Sonya Toler, a spokeswoman for the Pittsburgh police department, said the crash report is not a public record.

Zych said following any crash involving a self-driving Uber, the company cooperates with police both at the scene and afterward. Uber will provide its assessment what happened to police, he said. The company also cooperates with any federal authorities interested in the incident.

Zych would not go into specific details about Monday’s crash, saying it’s the company’s policy to defer to local police to release information.

Toler, on Monday, said the driver of Uber’s Volvo XC90 was in full control of the SUV at the time of the crash.

A black Nissan Sentra was driving west on Sidney Street when it collided with Uber’s SUV, which had been traveling south on Hot Metal Street.

The crash happened about 8 a.m. Uber’s fleet was idled until 11 a.m.

Aaron Aupperlee is a Tribune-Review staff writer. Reach him at, 412-336-8448 or via Twitter @tinynotebook.

TribLIVE commenting policy

You are solely responsible for your comments and by using you agree to our Terms of Service.

We moderate comments. Our goal is to provide substantive commentary for a general readership. By screening submissions, we provide a space where readers can share intelligent and informed commentary that enhances the quality of our news and information.

While most comments will be posted if they are on-topic and not abusive, moderating decisions are subjective. We will make them as carefully and consistently as we can. Because of the volume of reader comments, we cannot review individual moderation decisions with readers.

We value thoughtful comments representing a range of views that make their point quickly and politely. We make an effort to protect discussions from repeated comments either by the same reader or different readers

We follow the same standards for taste as the daily newspaper. A few things we won't tolerate: personal attacks, obscenity, vulgarity, profanity (including expletives and letters followed by dashes), commercial promotion, impersonations, incoherence, proselytizing and SHOUTING. Don't include URLs to Web sites.

We do not edit comments. They are either approved or deleted. We reserve the right to edit a comment that is quoted or excerpted in an article. In this case, we may fix spelling and punctuation.

We welcome strong opinions and criticism of our work, but we don't want comments to become bogged down with discussions of our policies and we will moderate accordingly.

We appreciate it when readers and people quoted in articles or blog posts point out errors of fact or emphasis and will investigate all assertions. But these suggestions should be sent via e-mail. To avoid distracting other readers, we won't publish comments that suggest a correction. Instead, corrections will be made in a blog post or in an article.