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.
News
Why SpaceX is finishing another space-internet system that isn’t Starlink
SpaceX launched three final O3b mPower satellites Sunday, finishing a lesser known SES satellite network.
SpaceX had an 87 minute window opening at 2:49 p.m. Eastern on Sunday to fly a Falcon 9 out of Cape Canaveral carrying the final three satellites for SES’s O3b mPower constellation, a project that has taken more than a decade to finish since Boeing and SES first signed SpaceX on for the work.
Unlike the thousands of Starlink satellites SpaceX has stacked into orbit over the years, O3b mPower flies in a different neighborhood entirely. The three new satellites, tagged F11, F12 and F13, are headed for medium Earth orbit at roughly 5,000 miles up, more than ten times higher than Starlink’s shell around 340 miles but still a small fraction of the 22,000 miles where old school geostationary satellites sit. That middle position is the whole point, because a satellite that far out needs far fewer siblings to blanket the globe than a low orbit constellation does. Essentially, SES only needed 13 satellites total to build a network offering quick, steady service that used to require thousands of spacecraft.
With most people having heard plenty about Starlink and almost nothing about O3b mPower, SES and SpaceX already blend the two networks for some customers. Both SpaceX and SES sell satellite broadband, but they’re aimed at different buyers. Starlink is built for volume, direct to consumers, RVs, homes, small businesses, plus a growing aviation and maritime business. O3b mPower skips consumers entirely and sells enterprise grade connectivity to airlines, cruise lines, offshore energy operators, telecoms needing backhaul, and governments, priced and provisioned more like a dedicated circuit.
A 2023 partnership lets cruise ships combine Starlink’s speed with O3b mPower’s steady capacity depending on what a ship needs at a given moment. Sunday’s completed 13 satellite constellation effectively finishes the medium orbit half of that pairing, years after.
Sunday’s mission was already a something on SpaceX’s manifest well before O3b mPower entered the picture. This flight marked its 29th trip to orbit, a history that includes two crewed Axiom missions, the European Space Agency’s Euclid telescope and 22 separate Starlink batches. SpaceX has landed boosters on the droneship A Shortfall of Gravitas so often that Sunday’s touchdown attempt, if it went as planned, was set to be the 661st successful Falcon booster landing to date.
For a company that pushed the Starlink constellation past 11,000 satellites back in August, almost entirely through bulk launches from California, Sunday’s flight was a reminder that SpaceX’s schedule still has room for someone else’s satellites too. SES gets a finished network built for a narrower set of customers, and Falcon 9 gets one more line on an already long resume.
Elon Musk
Tesla gives the Roadster an official “Go for launch” demonstration date
Tesla teased an October 1 Roadster reveal, reviving years of delayed SpaceX thruster hover promises.
Tesla teased an October 1 event date for its next generation Roadster, posting an image on X Saturday that shows the car lit up like it is sitting on a launch pad, with the date “10.01” stamped across the bottom and the caption “Go for launch.” A countdown clock on Tesla’s Roadster order page now points to the same date, which falls on a Thursday. The company has not said where the event will happen or whether it will be streamed at the moment. Stay with us @Teslarati for live updates.
Go for launch pic.twitter.com/Khu03eiZ04
— Tesla (@Tesla) September 12, 2026
Tesla has since sent formal invitations to reservation holders confirming the event will take place in Waco, Texas, about 90 minutes north of its Austin headquarters, based on a digital ticket shared on X by Sawyer Merritt. Tesla did not name the exact venue, though Waco sits close to SpaceX’s McGregor, Texas, rocket test site, previously reported as the planned location for a Roadster thruster demonstration. The invite sets the reveal for 8:30 p.m. Eastern on October 1, requires RSVPs by midnight on September 16, and limits entry to guests 21 and older. Invitations are non-transferable.
The tease follows nine years of a project defined by unimaginable specs along with slipped dates. Musk first showed the second generation Roadster in November 2017 as a surprise reveal at the end of the Tesla Semi event, promising a 0 to 60 mph time under two seconds, a top speed above 250 mph, 620 miles of range from a 200 kWh battery, and production starting in 2020. At last November’s shareholder meeting, Musk set an April 1 demo date and joked the choice gave him “deniability” if it slipped again, which it did, moving first to late April, then to “a month or so,” then to August.
Tesla Roadster SpaceX Package’s 1.1-second 0-60 mph launch visualized in concept video
Whatever Tesla shows on October 1 is expected to center on the SpaceX developed thruster package Musk has described since 2018. Internally code named A71, a nod to the Lockheed SR-71 Blackbird, the system reportedly uses cold gas thrusters fed by a composite overwrapped pressure vessel, the same tank design SpaceX uses on Falcon 9. Musk has said a thruster equipped Roadster could hit 60 mph in about 1.1 seconds under roughly 2.75 g of launch force, well past the 1.9 second figure quoted for the standard car. That version reportedly will not be street legal and has reportedly been discussed as a limited run sold through a track only program.
The standard Roadster is still expected to carry the original $200,000 base price and $250,000 Founders Series tier, both set when Tesla opened $50,000 and $250,000 reservations in 2017. Tesla VP of Vehicle Engineering Lars Moravy has confirmed production will happen at Gigafactory Texas, with Musk targeting 2027 or 2028, 12 to 18 months after whatever the company demonstrates next month.
News
Tesla plans big safety improvements for Full Self-Driving v15
Tesla is planning to roll out some pretty significant safety and accident avoidance features with Full Self-Driving version 15, which will be the next major FSD deployment from the company.
Tesla AI lead Ashok Elluswamy used a near-miss this week to preview what the company says is the next leap in Full Self-Driving.
In response to a driver whose car had swerved away from another vehicle pulling out of a parking lot, Elluswamy wrote that he was glad the owner was safe and that “even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance” would arrive with FSD v15.
Glad you are safe. Even earlier prediction of hazards, even faster reaction time and overall significantly better safety and collision avoidance coming as part of the next big upgrade (v15).
— Ashok Elluswamy (@aelluswamy) September 11, 2026
The comment landed as Tesla continues to treat software as the primary safety upgrade path. v15 is described internally as a larger architectural step, with a much bigger neural network and tighter coupling between prediction and control.
The company has already begun using early v15 software in some robotaxi operations while rolling out safety features such as Automatic Collision Evasion into current customer cars, allowing the driving stack to intervene even when the driver is in manual control.
Tesla is rolling out a new FSD version with a massive safety addition
Tesla’s published telemetry is the backbone of its safety argument. In recent North American Vehicle Safety Report data, vehicles with FSD (Supervised) engaged traveled roughly 5.1 million to 5.7 million miles between major collisions, defined as airbag-deployment events.
Tesla’s estimate of the U.S. average over the same period is about 699,000 miles per comparable crash. That is the comparison Tesla often frames as roughly seven times fewer major collisions.
A tighter comparison uses the same Tesla fleet. Cars driven manually with active safety features such as automatic emergency braking still recorded a major collision about every 2.1 million miles. Against that baseline, FSD’s advantage shrinks to roughly 2.4 to 2.7 times fewer severe crashes, which independent researchers argue is the more apples-to-apples figure.
European data released in 2026 pointed in the same direction: Tesla reported FSD as 3.5 times safer than manual driving in the Netherlands and 4.1 times fewer collisions than manually driven Teslas with active safety across more than 100 million kilometers in five approved countries.
Those numbers do not settle every debate. NHTSA’s Standing General Order still shows Tesla accounting for the large majority of U.S. Level 2 driver-assist crash reports, in part because the fleet logs far more assisted miles than rivals. Critics also note that Tesla’s “U.S. average” mixes crash definitions and driving mix.
Even so, Tesla’s own same-car comparisons, plus lower rates of automatic emergency braking and harsh maneuvers when FSD is engaged, are the evidence Elluswamy is pointing to when he says v15 will push prediction and collision avoidance further. The claim is not that software already eliminates risk. It is that each major version is meant to widen the gap between the system and an unaided human driver.