Cruise is complying with a California DMV request to cut its fleet by 50% as the regulator probes “recent concerning incidents” involving Cruise robotaxis
Cruise, the self-driving car subsidiary of GM, has been asked to reduce its robotaxi fleet by 50% in San Francisco following a crash Thursday night with a fire truck.
TechCrunchKirsten Korosec
Context & Ripple Effects
Cruise had recently extended its San Francisco driverless service to round-the-clock operation, after operating what it called a small fleet. The city had already urged state regulators to halt or slow the expansion of Cruise and Waymo over vehicles stopping or idling in traffic.
The fleet reduction turns those earlier concerns into an operating constraint imposed by the state regulator. It also sits in a longer record of Cruise tempering deployment ambitions over safety and performance, including its missed 2019 commercial-service target.
First-order effects
Cruise must immediately operate fewer robotaxis in San Francisco, reducing the service capacity available while the DMV examines the incidents.
The DMV has made continued deployment contingent on addressing safety concerns, shifting Cruise’s near-term focus from expanding availability to satisfying regulatory scrutiny.
Second-order effects
A reduced fleet limits the operational data and rider-service scale Cruise can generate in its principal deployment market, following its move to 24/7 driverless operations.
The action reinforces San Francisco’s earlier request that regulators slow autonomous-vehicle expansion, raising the compliance burden for robotaxi operators seeking larger local fleets.
Third-order effects
If regulators increasingly respond to incidents with immediate fleet restrictions, permits will function less like a one-time launch approval and more like a continuously revisable operating license.
The later suspension of Cruise’s California permits shows how quickly a constrained deployment can escalate into a full halt, making regulatory resilience a core determinant of robotaxi commercialization.
The trend: Robotaxi deployment is moving toward continuous, incident-driven regulatory oversight rather than expansion determined solely by a company’s technical readiness.
DMV orders Cruise to reduce robotaxi fleet in SF by 50% after collision yesterday with fire truck, injuring passenger. Of course, just a handful of days ago the CPUC said Waymo and Cruise could vasty expand their fleets in SF. At least the DMV has some sense about this half-bak…
A little after 10PM last night one of our cars was in a collision at Polk and Turk St and we wanted to provide an update on what we know at this time. (1/5)
Last night a driverless vehicle collided with a fire truck in my district, sending a passenger to the hospital. This situation has gotten out of control. It's irresponsible & reckless to allow this experiment to play out on our streets without limitation
Saying “a driverless vehicle collided with a fire truck” is at best misleading and at worst a straight up intentional lie. The fire truck hit the Cruise car. I expect more honesty from a 5th grader. I know you won't respond btw, b/c you are also a coward.
to be fair who the fuck would get into one of those? they're playing crash dummies for their silicon valley overlords
Quote
·
Last night a driverless vehicle collided with a fire truck in my district, sending a passenger to the hospital. This situation has gotten out of control. …
Easy to posture when you can't do anything about it
Quote
·
Last night a driverless vehicle collided with a fire truck in my district, sending a passenger to the hospital. This situation has gotten out of control. It's irresponsible & reckless to allow this experiment to play out…
SF Chronicle publishes factually untrue headline The driverless Cruise car, which had a green light, was hit by an emergency vehicle. Yet the SF Chronicle headline claims the opposite. This is what you get when “objectivity” is abandoned by legacy media