GM’s Cruise slashed fleet of robotaxis by 50% in San Francisco after collisions

CNN —
California authorities have asked General Motors to “immediately” take some of its Cruse robotaxis off the road after autonomous vehicles were involved in two collisions – including one with an active fire truck – last week in San Francisco.
California’s Department of Motor Vehicles confirmed to CNN that it is investigating “recent concerning incidents involving Cruise vehicles in San Francisco.”
“The DMV is in contact with Cruise and law enforcement officials to determine the facts and requested Cruise to immediately reduce its active fleet of operating vehicles by 50% until the investigation is complete and Cruise takes appropriate corrective actions to improve road safety,” the department said in a statement.
That means Cruise, which is the self-driving subsidiary of General Motors, can have no more than 50 driverless cars in operation during the day, and 150 in operation at night, according to the department.
The California DMV said that Cruise has agreed to the request, and a spokesperson from Cruise told CNN that the company is investigating the firetruck crash as well.
Accidents come just after Cruise’s big win in San Francisco
The accidents come less than two weeks after California regulators officially gave the green light for Cruise and competitor Waymo to charge money for robotaxi trips around San Francisco at any time of day. Prior to the approval, Cruise was only authorized to offer fared passenger service from driverless cars overnight from 10 pm to 6 am, when there are fewer pedestrians or traffic that could confuse the autonomous vehicle’s software.
The collisions, which both occurred on Thursday, reveal potential risks of driverless technology.
In a blog post, Cruise’s general manager for San Francisco said the firetruck crash occurred when an emergency vehicle that appeared to be en route to an emergency scene moved into an oncoming lane of traffic to bypass a red light. Cruise’s driverless car identified the risk, the blog post said, but it “was ultimately unable to avoid the collision.”
That crash resulted in one passenger being taken to the hospital via ambulance for seemingly minor injuries, according to the company.
Cruise told CNN the other crash on Thursday took place when another car ran a red light “at a high rate of speed.”
“The AV detected the vehicle and braked but the other vehicle made contact with our AV. There were no passengers in our AV and the driver of the other vehicle was treated and released at the scene,” Hannah Lindow, a Cruise spokesperson, told CNN.
It is unclear whether the two accidents would have been avoided had there been a human driver rather than an autonomous vehicle (AV) involved – but the crashes were not the only two incidents involving Cruise’s driverless cars in San Francisco last week.
On Tuesday, Cruise confirmed on X, formerly known as Twitter, that one of its driverless taxis drove into a construction area and stopped in wet concrete.
“This vehicle has already been recovered and we’re in communication with the city about this,” the company said.
Roadblocks for autonomous vehicles
The recent events underscore the challenges of creating safe, fully driverless passenger vehicles.
General Motors acquired Cruise Automation in 2016 for $1 billion, solidifying its place in the autonomous vehicles race, but many companies have since scaled back, or abandoned their driverless car ambitions. The endeavor has proven costly, and mastering all situations that humans might face behind the wheel is difficult and time-consuming.
Ridesharing giants Uber and Lyft have both sold autonomous vehicle units in recent years. Even Tesla CEO Elon Musk, who has been optimistic about autonomous vehicle technology, has yet to fully deliver on his promise.
Tesla vehicles now come with the option to add a “full self-driving” feature in beta-testing for $15,000, but drivers must agree to “stay alert, keep your hands on the steering wheel at all times and maintain control of your car.”