Cruise Robotaxi Was Involved in a Crash in San Francisco That Resulted in Injuries

Cruise robotaxi was involved in a crash in San Francisco that resulted in injuries 6 photos
Photo: Cruise
Driverless Cruise robotaxis stopped working in San FranciscoDriverless Cruise robotaxis stopped working in San FranciscoDriverless Cruise robotaxis stopped working in San FranciscoDriverless Cruise robotaxisDriverless Cruise robotaxis
One day after the California regulators allowed Cruise to operate a commercial robotaxi service, one of the company’s self-driving vehicles was involved in a crash that resulted in multiple injuries. The accident happened on the night of June 3, but details only emerged this Wednesday.
Self-driving technology is still a controversial chapter, with Tesla taking most of the flak. Despite the impression that the American EV maker is the only one pushing automated driving, other companies are also working hard at cracking self-driving. And just like Tesla, their efforts and reputation are sometimes thrashed by accidents caused by less-than-perfect technology.

Cruise, a robotaxi company backed by General Motors, has recently received a milestone permit to offer commercial autonomous driving ride-hailing services in San Francisco. One day after the license was issued, a Cruise vehicle operating autonomously was involved in a crash at the intersection of Geary Boulevard and Spruce Street in San Francisco. The Cruise vehicle made a left turn in front of an oncoming Toyota Prius, which led to a crash that injured the occupants of both cars.

In a report filed with the California Department of Motor Vehicles, Cruise said its self-driving vehicle stopped in the roadway before completing its left turn and was stationary when struck. According to Cruise, the other car’s driver was to blame, as they were speeding and the Prius had continued straight from a right-turn lane. Unfortunately, the details could not be independently verified.

A spokesperson for the San Francisco Police Department could not find an incident report related to the crash Wednesday and said it was possible no report was generated. Approached by Automotive News, a Cruise spokesperson declined Wednesday to say why the AV stopped before completing its turn. Many questions remained unanswered, though, so it’s impossible to say for sure who was to blame for the crash.

Cruise is no stranger to accidents and incidents, despite Tesla taking all the limelight regarding self-driving crashes. According to an NHTSA report, Cruise vehicles were involved in 23 crashes from July 2021 to May 15, 2022. In April, one of the company’s autonomous vehicles blocked the path of a San Francisco Fire Department truck en route to a blaze.

The same month, a police officer pulled over a Cruise vehicle because it was operating without headlights on at night. The car then repositioned itself before the traffic stop was complete. And only a week ago, dozens of Cruise vehicles clustered at a city intersection, blocking the traffic for hours.
If you liked the article, please follow us:  Google News icon Google News Youtube Instagram
About the author: Cristian Agatie
Cristian Agatie profile photo

After his childhood dream of becoming a "tractor operator" didn't pan out, Cristian turned to journalism, first in print and later moving to online media. His top interests are electric vehicles and new energy solutions.
Full profile


Would you like AUTOEVOLUTION to send you notifications?

You will only receive our top stories