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 AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
