General Motors’ Cruise autonomous vehicle unit has agreed to cut its fleet of San Francisco robotaxis in half as authorities investigate two recent crashes in the city.
The state Department of Motor Vehicles asked for the reduction after a Cruise vehicle without a human driver collided with a firetruck on Aug. 17.
“The DMV is investigating recent concerning incidents involving Cruise vehicles in San Francisco,” the DMV said Aug. 19 in a statement to The Associated Press. “Cruise has agreed to a 50% reduction and will have no more than 50 driverless vehicles in operation during the day and 150 driverless vehicles in operation at night.”
The development comes just over a week after California regulators allowed Cruise and Google spinoff Waymo to operate autonomous robotaxis throughout San Francisco at all hours, despite safety worries spurred by recurring problems with unexpected stops and other erratic behavior.
The decision Aug. 10 by the Public Utilities Commission made San Francisco the first major U.S. city with two fleets of driverless vehicles competing for passengers.
On Aug. 17 around 10 p.m., the Cruise vehicle had a green light, entered an intersection, and was hit by a firetruck responding to a call, the San Francisco Chronicle reported, based on tweets from Cruise.
The collision occurred while the firetruck was operating in a “Code 3” emergency mode, said the San Francisco Police Department, according to Bloomberg News. That means the fire truck’s lights, including a forward-facing steady red light and siren, were activated.
While we continue our investigation in partnership with city officials and regulators, we wanted to provide an update on our preliminary analysis of the incident. Read more here https://t.co/yPPRIKwJ4W
— cruise (@Cruise) August 19, 2023
The robotaxi was carrying a passenger, who was taken by ambulance to a hospital with injuries that were not severe, Cruise told the newspaper.
Also Aug. 17, a Cruise car without a passenger collided with another vehicle in San Francisco, the newspaper reported.
The robotaxi almost immediately identified the emergency response vehicle as it came into view, Greg Dietrerich, Cruise’s general manager in San Francisco, said in a statement on the company website.
At the intersection, visibility is occluded by buildings, and it’s not possible to see objects around a corner until they are very close to the intersection, Dietrerich’s statement said. The Cruise autonomous vehicle detected the siren as soon it was distinguishable from background noise, he wrote.
“The AV’s ability to successfully chart the emergency vehicle’s path was complicated by the fact that the emergency vehicle was in the oncoming lane of traffic, which it had moved into to bypass the red light,” Dietrerich wrote.
Ryan Manthir of Shell Global Solutions and Michael Grahe of Navistar discuss the future of the internal combusion engine. Tune in above or by going to RoadSigns.ttnews.com.
The Cruise vehicle identified the risk of a crash and braked, reducing its speed, but couldn’t avoid the collision, he wrote.
Cruise vehicles have driven more than 3 million autonomous miles in the city and have interacted with emergency vehicles more than 168,000 times in the first seven months of this year alone, the statement said. “We realize that we’ll always encounter challenging situations, which is why continuous improvement is central to our work.”
The company will work with regulators and city departments to reduce the likelihood of a crash happening again, Dietrerich wrote.
The DMV said the fleet reduction will remain until its investigation ends and Cruise takes corrective action to improve safety. “The DMV reserves the right, following investigation of the facts, to suspend or revoke testing and/or deployment permits if there is determined to be an unreasonable risk to public safety.”
