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 Full Self-Driving v14.2 rolled out late last week to Early Access Program (EAP) members, but its best feature is not what you think.
While Tesla has done a great job of refining the performance of the Full Self-Driving suite with the latest update, there are some other interesting additions, including one that many owners have requested for some time.
Upon the release of v14.2, many owners recognized the Blue Dot next to the Autopilot tab in Vehicle Settings, notifying them of a new feature. What was included as a new feature in the new update was a Full Self-Driving stats feature, which now will show you how many miles you’ve traveled in total, and how many of those miles were driven using FSD:
🚨 The coolest non-driving change of Tesla Full Self-Driving v14.2 pic.twitter.com/HOJcFaV2Ny
— TESLARATI (@Teslarati) November 21, 2025
The feature seems to be more of a bragging rights thing than anything, but it will also give drivers a good idea of how many miles they are using Full Self-Driving for. Those who use telematics-based insurance services will also be able to run experiments of their own, and could determine whether their premiums are impacted by the use of Full Self-Driving, and whether it is more advantageous to use over manual driving.
Tesla rolled out numerous other improvements with Tesla Full Self-Driving v14.2, most notably, the company seems to have resolved previous complaints about brake stabbing and hesitation. This was a major complaint in v14.1, but Tesla has seemed to resolve it with this newest branch of the FSD suite.
There were also improvements in overall operation, and it was notably smoother than past versions. Speed Profiles are seemingly refined as well, as they seem much more fixed on how fast they will travel and how aggressive they will be with things like passing cars on freeways and lane changes.
In future updates, Tesla plans to add Parking Spot selection, along with overall operational improvements. However, CEO Elon Musk recently said that the next branch, Full Self-Driving v14.3, will be where the “final piece of the puzzle is placed.” Tesla believes it is close to solving autonomy, so v14.3 could be a major jump forward, but it remains to be seen.
Tesla has adjusted the functionality of a crucial climate feature as Winter weather has started to arrive throughout some parts of the United States. The new feature was highly requested by owners.
Tesla has a Cabin Overheat Protection feature that helps keep the temperature regulated if it reaches a certain threshold. Inversely, it can be used in cold weather as well, which will automatically warm the cabin if it sinks to a temperature that is too low for the owner’s comfort.
This is a great way to keep the cabin either warmed up just enough or cooled down just enough so that it never gets too hot or too cold. Extreme temperatures could damage certain parts of the vehicle or damage personal belongings that are kept inside the car.
Overheat protection is a great thing to have in hot climates like Arizona or Texas, especially with the Premium trims of the Model 3 and Model Y, which feature a glass roof.
Many owners appreciate the feature, but they argue that using it at home will utilize too much energy, especially during extreme temperatures. For a while, many Tesla fans have requested an option to disable this feature when the car is parked at home, which the company recently added, according to Not a Tesla App.
The feature is part of Software Version 2025.44.3, and the release notes state:
“You can now choose Exclude Home when Cabin Overheat Protection or No A/C is enabled.”
Tesla has been great at listening to what owners want with new features, and this is one that will reserve some charge and prevent unnecessary utilization of available power, especially as the car is parked at home. If owners want to condition the cabin or get the car ready for operation with a comfortable interior, they can utilize the Tesla app to adjust the climate.
Tesla CEO Elon Musk revealed today on the social media platform X that legacy automakers, such as Ford, General Motors, and Stellantis, do not want to license the company’s Full Self-Driving suite, at least not without a long list of their own terms.
“I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy,” Musk said on X. “When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless.”
I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy …
When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless. 🤷♂️
🦕 🦕
— Elon Musk (@elonmusk) November 24, 2025
Musk made the remark in response to a note we wrote about earlier today from Melius Research, in which analyst Rob Wertheimer said, “Our point is not that Tesla is at risk, it’s that everybody else is,” in terms of autonomy and self-driving development.
Wertheimer believes there are hundreds of billions of dollars in value headed toward Tesla’s way because of its prowess with FSD.
A few years ago, Musk first remarked that Tesla was in early talks with one legacy automaker regarding licensing Full Self-Driving for its vehicles. Tesla never confirmed which company it was, but given Musk’s ongoing talks with Ford CEO Jim Farley at the time, it seemed the Detroit-based automaker was the likely suspect.
Tesla’s Elon Musk reiterates FSD licensing offer for other automakers
Ford has been perhaps the most aggressive legacy automaker in terms of its EV efforts, but it recently scaled back its electric offensive due to profitability issues and weak demand. It simply was not making enough vehicles, nor selling the volume needed to turn a profit.
Musk truly believes that many of the companies that turn their backs on FSD now will suffer in the future, especially considering the increased chance it could be a parallel to what has happened with EV efforts for many of these companies.
Unfortunately, they got started too late and are now playing catch-up with Tesla, XPeng, BYD, and the other dominating forces in EVs across the globe.
Tesla Full Self-Driving v14.2’s best new feature is not what you think
Tesla adjusts crucial feature as winter weather arrives
