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.
Elon Musk
SpaceX Starship Version 3 booster crumples in early testing
Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.
SpaceX’s new Starship first-stage booster, Booster 18, suffered major damage early Friday during its first round of testing in Starbase, Texas, just one day after rolling out of the factory.
Based on videos of the incident, the lower section of the rocket booster appeared to crumple during a pressurization test. Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.
Booster test failure
SpaceX began structural and propellant-system verification tests on Booster 18 Thursday night at the Massey’s Test Site, only a few miles from Starbase’s production facilities, as noted in an Ars Technica report. At 4:04 a.m. CT on Friday, a livestream from LabPadre Space captured the booster’s lower half experiencing a sudden destructive event around its liquid oxygen tank section. Post-incident images, shared on X by @StarshipGazer, showed notable deformation in the booster’s lower structure.
Neither SpaceX nor Elon Musk had commented as of Friday morning, but the vehicle’s condition suggests it is likely a complete loss. This is quite unfortunate, as Booster 18 is already part of the Starship V3 program, which includes design fixes and upgrades intended to improve reliability. While SpaceX maintains a rather rapid Starship production line in Starbase, Booster 18 was generally expected to validate the improvements implemented in the V3 program.
Tight deadlines
SpaceX needs Starship boosters and upper stages to begin demonstrating rapid reuse, tower catches, and early operational Starlink missions over the next two years. More critically, NASA’s Artemis program depends on an on-orbit refueling test in the second half of 2026, a requirement for the vehicle’s expected crewed lunar landing around 2028.
While SpaceX is known for diagnosing failures quickly and returning to testing at unmatched speed, losing the newest-generation booster at the very start of its campaign highlights the immense challenge involved in scaling Starship into a reliable, high-cadence launch system. SpaceX, however, is known for getting things done quickly, so it would not be a surprise if the company manages to figure out what happened to Booster 18 in the near future.
News
Tesla FSD (Supervised) is about to go on “widespread” release
In a comment last October, Elon Musk stated that FSD V14.2 is “for widespread use.”
Tesla has begun rolling out Full Self-Driving (Supervised) V14.2, and with this, the wide release of the system could very well begin.
The update introduces a new high-resolution vision encoder, expanded emergency-vehicle handling, smarter routing, new parking options, and more refined driving behavior, among other improvements.
FSD V14.2 improvements
FSD (Supervised) V14.2’s release notes highlight a fully upgraded neural-network vision encoder capable of reading higher-resolution features, giving the system improved awareness of emergency vehicles, road obstacles, and even human gestures. Tesla also expanded its emergency-vehicle protocols, adding controlled pull-overs and yielding behavior for police cars, fire trucks, and ambulances, among others.
A deeper integration of navigation and routing into the vision network now allows the system to respond to blocked roads or detours in real time. The update also enhances decision-making in several complex scenarios, including unprotected turns, lane changes, vehicle cut-ins, and interactions with school buses. All in all, these improvements should help FSD (Supervised) V14.2 perform in a very smooth and comfortable manner.
Elon Musk’s predicted wide release
The significance of V14.2 grows when paired with Elon Musk’s comments from October. While responding to FSD tester AI DRIVR, who praised V14.1.2 for fixing “95% of indecisive lane changes and braking” and who noted that it was time for FSD to go on wide release, Musk stated that “14.2 for widespread use.”
FSD V14 has so far received a substantial amount of positive reviews from Tesla owners, many of whom have stated that the system now drives better than some human drivers as it is confident, cautious, and considerate at the same time. With V14.2 now rolling out, it remains to be seen if the update also makes it to the company’s wide FSD fleet, which is still populated by a large number of HW3 vehicles.
News
Tesla FSD V14.2 starts rolling out to initial batch of vehicles
It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.
Tesla has begun pushing Full Self-Driving (Supervised) v14.2 to its initial batch of vehicles. The update was initially observed by Tesla owners and veteran FSD users on social media platform X on Friday.
So far, reports of the update have been shared by Model Y owners in California whose vehicles are equipped with the company’s AI4 hardware, though it would not be surprising if more Tesla owners across the country receive the update as well.
Based on the release notes of the update, key improvements in FSD V14.2 include a revamped neural network for better detection of emergency vehicles, obstacles, and human gestures, as well as options to select arrival spots.
It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.
Following are the release notes of FSD (Supervised) V14.2, as shared on X by longtime FSD tester Whole Mars Catalog.
Release Notes
2025.38.9.5
Currently Installed
FSD (Supervised) v14.2
Full Self-Driving (Supervised) v14.2 includes:
- Upgraded the neural network vision encoder, leveraging higher resolution features to further improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
- Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances.
- Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
- Added additional Speed Profile to further customize driving style preference.
- Improved handling for static and dynamic gates.
- Improved offsetting for road debris (e.g. tires, tree branches, boxes).
- Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
- Improved FSD’s ability to manage system faults and improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
- Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
- Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
- Added additional Speed Profile to further customize driving style preference.
- Improved handling for static and dynamic gates.
- Improved offsetting for road debris (e.g. tires, tree branches, boxes).
- Improve handling of several scenarios, including unprotected turns, lane changes, vehicle cut-ins, and school buses.
- Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
- Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!
Upcoming Improvements:
- Overall smoothness and sentience
- Parking spot selection and parking quality
SpaceX Starship Version 3 booster crumples in early testing
Tesla FSD (Supervised) is about to go on “widespread” release
