News
Cruise to reduce self-driving fleet by 50% in SF following robotaxi crash
The California Department of Motor Vehicles (DMV) has asked General Motors’ self-driving unit, Cruise, to temporarily reduce its robotaxi fleet by 50% in San Francisco. The request came after one of the company’s driverless vehicles was involved in a crash with a fire truck last week.
The California DMV noted that its is investigating “recent concerning incidents” involving autonomous robotaxis in the city. With this in mind, the DMV has advised that Cruise must reduce its San Francisco fleet by half until the investigation is completed and the self-driving company takes appropriate actions to improve road safety.
Following is the CA DMV’s statement about Cruise’s recent robotaxi incidents.
“Safety of the traveling public is the California DMV’s top priority. The primary focus of the DMV’s regulations is the safe operation of autonomous vehicles and safety of the public who share the road with these vehicles.
“The DMV 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. 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 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.”
With Cruise agreeing to reduce its fleet by 50%, the company also released a blog post explaining the circumstances that led up to the accident. As per Cruise, the robotaxi identified the emergency vehicle almost immediately as it came into video. The robotaxi operator also noted that the vehicle initiated a braking maneuver and reduced its speed, but it was ultimately unable to avoid the collision.
All in all, the damage is super light. Good learning experience. A deaf, colorblind, human driver would have probably also gotten clipped.
In this situation, if you don't hear the truck and you don't notice the approaching scattered red light, reflecting on the buildings/street… pic.twitter.com/mTAGEQkAEk
— oFFMetaSweat (@oFFMetaSweat) August 18, 2023
Following is Cruise’s post about the incident.
“While our investigation is ongoing and we remain in contact with city officials and regulators, we wanted to provide an update on our preliminary analysis on the incident involving an emergency vehicle colliding with a Cruise AV.
“First and foremost, our primary concern remains with our passenger and their well-being. We have been in contact to offer support and will remain in touch.
“In terms of what occurred around the scene of the collision there are many aspects that looked typical from the AV’s perspective and several factors that added complexity to this specific incident.
“The AV positively identified the emergency vehicle almost immediately as it came into view, which is consistent with our underlying safety design and expectation. It is worth noting, however, that the confines of this specific intersection make visual identification more challenging – for humans and AVs alike – as it is significantly occluded by buildings, meaning that it is not possible to see objects around the corner until they are physically very close to the intersection.
“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.
“Cruise AVs have the ability to detect emergency sirens, which increase their ability to operate safely around emergency vehicles and accompanying scenes. In this instance, the AV identified the siren as soon as it was distinguishable from the background noise.
“The Cruise AV did identify the risk of a collision and initiated a braking maneuver, reducing its speed, but was ultimately unable to avoid the collision.
“During the course of more than 3 million miles of fully autonomous driving in San Francisco we’ve seen an enormous number of emergency vehicles – more than 168,000 interactions just in the first 7 months of this year alone. Our first responders are trying to balance keeping all of us safe while quickly responding to emergency scenes and we’re grateful for their work and dedication.
“We realize that we’ll always encounter challenging situations, which is why continuous improvement is central to our work. We will continue to work in partnership with regulators and city departments on EMV interactions to reduce the likelihood of incidents like these happening again.”
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads-up.
Tesla Robotaxi ride-hailing without a Safety Monitor is proving to be a difficult task, according to some riders who made the journey to Austin to attempt to ride in one of its vehicles that has zero supervision.
Last week, Tesla officially removed Safety Monitors from some — not all — of its Robotaxi vehicles in Austin, Texas, answering skeptics who said the vehicles still needed supervision to operate safely and efficiently.
BREAKING: Tesla launches public Robotaxi rides in Austin with no Safety Monitor
Tesla aimed to remove Safety Monitors before the end of 2025, and it did, but only to company employees. It made the move last week to open the rides to the public, just a couple of weeks late to its original goal, but the accomplishment was impressive, nonetheless.
However, the small number of Robotaxis that are operating without Safety Monitors has proven difficult to hail for a ride. David Moss, who has gained notoriety recently as the person who has traveled over 10,000 miles in his Tesla on Full Self-Driving v14 without any interventions, made it to Austin last week.
He has tried to get a ride in a Safety Monitor-less Robotaxi for the better part of four days, and after 38 attempts, he still has yet to grab one:
Wow just wow!
It’s 8:30PM, 29° out ice storm hailing & Tesla Robotaxi service has turned back on!
Waymo is offline & vast majority of humans are home in the storm
Ride 38 was still supervised but by far most impressive yet pic.twitter.com/1aUnJkcYm8
— David Moss (@DavidMoss) January 25, 2026
Tesla said last week that it was rolling out a controlled test of the Safety Monitor-less Robotaxis. Ashok Elluswamy, who heads the AI program at Tesla, confirmed that the company was “starting with a few unsupervised vehicles mixed in with the broader Robotaxi fleet with Safety Monitors,” and that “the ratio will increase over time.”
This is a good strategy that prioritizes safety and keeps the company’s controlled rollout at the forefront of the Robotaxi rollout.
However, it will be interesting to see how quickly the company can scale these completely monitor-less rides. It has proven to be extremely difficult to get one, but that is understandable considering only a handful of the cars in the entire Austin fleet are operating with no supervision within the vehicle.
Tesla has given its biggest hint that Full Self-Driving in Europe is imminent, as a new feature seems to show that the company is preparing for frequent border crossings.
Tesla owner and influencer BLKMDL3, also known as Zack, recently took his Tesla to the border of California and Mexico at Tijuana, and at the international crossing, Full Self-Driving showed an interesting message: “Upcoming country border — FSD (Supervised) will become unavailable.”
FSD now shows a new message when approaching an international border crossing.
Stayed engaged the whole way as we crossed the border and worked great in Mexico! pic.twitter.com/bDzyLnyq0g
— Zack (@BLKMDL3) January 26, 2026
Due to regulatory approvals, once a Tesla operating on Full Self-Driving enters a new country, it is required to comply with the laws and regulations that are applicable to that territory. Even if legal, it seems Tesla will shut off FSD temporarily, confirming it is in a location where operation is approved.
This is something that will be extremely important in Europe, as crossing borders there is like crossing states in the U.S.; it’s pretty frequent compared to life in America, Canada, and Mexico.
Tesla has been working to get FSD approved in Europe for several years, and it has been getting close to being able to offer it to owners on the continent. However, it is still working through a lot of the red tape that is necessary for European regulators to approve use of the system on their continent.
This feature seems to be one that would be extremely useful in Europe, considering the fact that crossing borders into other countries is much more frequent than here in the U.S., and would cater to an area where approvals would differ.
Tesla has been testing FSD in Spain, France, England, and other European countries, and plans to continue expanding this effort. European owners have been fighting for a very long time to utilize the functionality, but the red tape has been the biggest bottleneck in the process.
Tesla Europe builds momentum with expanding FSD demos and regional launches
Tesla operates Full Self-Driving in the United States, China, Canada, Mexico, Puerto Rico, Australia, New Zealand, and South Korea.
Elon Musk
SpaceX Starship V3 gets launch date update from Elon Musk
The first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.
Elon Musk has announced that SpaceX’s next Starship launch, Flight 12, is expected in about six weeks. This suggests that the first flight of Starship Version 3 and its new Raptor V3 engines could happen as early as March.
In a post on X, Elon Musk stated that the next Starship launch is in six weeks. He accompanied his announcement with a photo that seemed to have been taken when Starship’s upper stage was just about to separate from the Super Heavy Booster. Musk did not state whether SpaceX will attempt to catch the Super Heavy Booster during the upcoming flight.
The upcoming flight will mark the debut of Starship V3. The upgraded design includes the new Raptor V3 engine, which is expected to have nearly twice the thrust of the original Raptor 1, at a fraction of the cost and with significantly reduced weight. The Starship V3 platform is also expected to be optimized for manufacturability.
The Starship V3 Flight 12 launch timeline comes as SpaceX pursues an aggressive development cadence for the fully reusable launch system. Previous iterations of Starship have racked up a mixed but notable string of test flights, including multiple integrated flight tests in 2025.
Interestingly enough, SpaceX has teased an aggressive timeframe for Starship V3’s first flight. Way back in late November, SpaceX noted on X that it will be aiming to launch Starship V3’s maiden flight in the first quarter of 2026. This was despite setbacks like a structural anomaly on the first V3 booster during ground testing.
“Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X.
Tesla Robotaxi ride-hailing without a Safety Monitor proves to be difficult
Tesla gives its biggest hint that Full Self-Driving in Europe is imminent
