A California judge has forced General Motors’ (GM) self-driving unit Cruise to increase its settlement offer to the maximum amount, after one of the company’s robotaxis pinned and seriously injured a pedestrian in October.
On October 2, a driverless Cruise vehicle dragged and pinned a pedestrian in San Francisco, and the company’s license to operate self-driving cars was immediately revoked by the California Department of Motor Vehicles (DMV). The DMV later said that Cruise “misrepresented” and “omitted” crucial details about its response to the accident, and the California Public Utilities Commission (CPUC) in December ordered the company to appear before a judge this month.
During the hearing, which was held on Tuesday, California Administrative Law Judge (ALJ) Robert Mason III suggested that Cruise revise its $75,000 settlement offer to the maximum penalty of $112,500, after calling the company’s proposed amount “low,” and even suggesting the company was seeking a “discount.”
While Judge Mason III said he appreciated Cruise attempting to take “corrective action” in its crash response procedures, he added that the company should “take a hint” following his multiple questions about the offer amount, suggesting directly that Cruise change its settlement offer to the full penalty.
“Point taken, your Honor,” responded Craig Glidden, Cruise President and Chief Administrative Officer. “We immediately revise our offer to the amount requested.”
Waymo could face new legal barriers in its expansion to Los Angeles
The hearing discussed findings from an investigation conducted by the law firm Quinn Emanuel, which Cruise hired, including that internet connectivity hampered the company’s sharing of video footage from the accident with regulators in meetings that followed.
In response to the motion for approval to settle at $75,000, the commission can adopt, adopt with revisions, or reject Cruise’s filing. Following the hearing, the next step is for Judge Mason to write a proposed decision on the case for the commissioner’s consideration, with the general timeframe falling within about 60 days, as a CPUC spokesperson clarified to Teslarati.
Cruise said it was eager to resolve the case and move past the incident, adding that it wanted to continue to “advance the mission of bringing driverless cars that are safer to the public and also greater accessibility to the public to the market.”
However, Mason didn’t make it sound like the commission was eager to set the case aside:
“While the commission does fall on the side of getting its cases resolved, I don’t know that this is one of those protracted pieces of litigation that we’re usually most anxious to put aside and then move forward with the regulatory process,” Mason added.
In the original motion, filed on January 30, Cruise outlines the key requirements it would have to follow as part of the settlement:
1. Cruise will adopt voluntarily several new data reporting enhancements that will provide additional data to the Commission concerning California collisions and AVs operating in California under a deployment permit that enter a minimal risk condition (“MRC”) state and result in conditions described in Attachment A;
2. Cruise will provide the Commission with Cruise’s responses to the permit reinstatement questions from the California Department of Motor Vehicles (“DMV”) at the same time Cruise provides those responses to the DMV;
3. Cruise will make a payment of $75,000 to the State General Fund within ten (10) days of the Commission’s approval of the Settlement Agreement without modification; and
4. Upon the Commission’s approval of the Settlement Agreement, the OSC proceeding will be closed.
“We are committed to working in partnership with the CPUC, other regulators and government agencies to improve transportation safety in support of a shared goal –– providing better, safer and more accessible transportation to the public in our communities,” a Cruise spokesperson wrote in an email to Teslarati. “Over the past several months, we have taken important steps to improve our leadership, processes and culture, and we are committed to resolving matters to the Commission’s satisfaction as we work to restore regulatory and public trust.”
Cruise also noted that the accident, which occurred after the pedestrian had already been hit by a human driver, was partially caused by the driverless ride-hailing vehicle falsely identifying the situation as a side-impact collision rather than a frontal collision, causing the Minimal Risk Condition (MRC) response that forces the vehicle to pull over.
In addition, Cruise said it is currently expecting a new Chief Safety Officer in the “not too distant future,” after two co-founders resigned immediately following the accident, and after the company fired nine executives and laid off nearly a quarter of its staff on the same day in December.
GM recently announced plans to cut spending on Cruise in half this year, though it said it also hoped to “refocus and relaunch” the company’s operations. GM CEO Mary Barra highlighted significant changes at Cruise, which the company began implementing following the Quinn Emanuel investigation.
“At Cruise, we are committed to earning back the trust of regulators and the public through our commitments and our actions,” Barra said following GM’s 2023 earnings call.
You can see the full January 30 filing from Cruise below, including the findings from the Quinn Emanuel investigation, which Cruise made public last month.
What are your thoughts? Let me know at zach@teslarati.com, find me on X at @zacharyvisconti, or send your tips to us at tips@teslarati.com.
Tesla Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.
On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:
From 6 to 7
Tesla Full Self-Driving has launched in South Korea; the 7th country to have FSD https://t.co/X6gm1SyoxV
— TESLARATI (@Teslarati) November 23, 2025
This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.
Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.
However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.
Tesla Full Self-Driving appears to be heading to Europe soon
The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”
Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.
For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Tesla Full Self-Driving lands in a new country, its 7th
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
