Self-Driving Cruise Taxi Is Broadsided By a Prius in San Francisco and No One Knows What Happened
Image: General Motors
A little more than a month ago, GM’s Cruise received a permit to start charging passengers for rides in its autonomous, driverless robotaxis. It was a major milestone for the service. A day later, on June 3, one of those robotaxis was involved in a crash in San Francisco, where occupants in both vehicles sustained minor injuries, per a California DMV report surfaced by Automotive News.
The report contains Cruise’s own testimony of what transpired, and it places the blame pretty solidly on the human driver. According to the company, the taxi was attempting a left turn in front of an oncoming Toyota Prius on the intersection of Geary Boulevard and Spruce Street when the two collided. The Prius was in the rightmost turning lane but traveled straight through the intersection while speeding and, at some point before the crash — it’s not exactly clear when — the Cruise vehicle stopped. From Cruise’s filed report:
As it approached the intersection, the Cruise AV entered the left hand turn lane, turned the left turn signal on, and initiated a left turn on a green light onto Spruce Street. At the same time, a Toyota Prius traveling westbound in the rightmost bus and turn lane of Geary Boulevard approached the intersection in the right turn lane. The Toyota Prius was traveling approximately 40 mph in a 25 mph speed zone. The Cruise AV came to a stop before fully completing its turn onto Spruce Street due to the oncoming Toyota Prius, and the Toyota Prius entered the intersection traveling straight from the turn lane instead of turning. Shortly thereafter, the Toyota Prius made contact with the rear passenger side of the Cruise AV.
Cruise filed that “occupants of both vehicles received medical treatment for allegedly minor injuries.” It’s important to note that we’re working with only one side of the story here; according to Automotive News, the San Francisco Police Department did not generate its own incident report on the matter, and Cruise’s interpretation of the events could not be independently verified.
There’s still a lot we don’t know, and context is everything. Reading Cruise’s report, it’s easy to assume the Prius driver disregarded the intersection’s traffic patterns. Perhaps the Cruise AV expected the Prius to turn right as it completed its own left turn, but instead, the Prius continued straight and clipped the back right of the robotaxi.
It’s also entirely possible the Prius driver had every intention to turn right but swerved left to avoid the robotaxi because they couldn’t anticipate its movements — a scenario that Carnegie Mellon’s Phil Koopman, quoted in the story, raises:
Although the Cruise vehicle may have been stationary, Phil Koopman, a Carnegie Mellon University professor and autonomous-vehicle safety expert, said much more information would still be needed to assess the behavior of both humans and machine in the crash.
“Many people have a word for a driver who cuts in front of them and then stops in the road, and it’s not a polite or charitable word,” he said. “There are a lot of unknowns here. We don’t know if the Prius driver intended to turn right, but then swerved to try and avoid the crash with the stationary vehicle, for example. There are just a lot of unknowns.”
GM also didn’t list the number of occupants in the Cruise vehicle, nor whether any airbags deployed inside the cabin.
Several weeks after this crash, at least five Cruise taxis blocked traffic on Fulton Street, right off Gough. A Cruise spokesperson termed this a “technical issue” whereupon the vehicles “clustered together,” and reportedly had to be removed by company personnel.
Jalopnik has reached out to Cruise for additional clarification on this story and will update this piece with whatever we learn.
