California Gov. Gavin Newsom's signing of SB 1246, as reported on October 1, 2026, creates something new in American technology policy: a legally mandated operational-data feed from autonomous vehicle fleets to city governments. The feed is the best part of the law. Some of the staffing mandates around it are blunter than the evidence supports.
What the law requires
Per the bill text on the California Legislature's site, when a system failure affects multiple vehicles, manufacturers must immediately notify local jurisdictions and emergency dispatch of fleet status and location. They must then deploy technicians if remote recovery fails. Remote drivers must be located in the United States and hold a driver's license valid in California. Operators must maintain dedicated phone lines answered within 30 seconds, and must dispatch local incident technicians "immediately" after crashes or obstructions.
The DMV must set reasonable response-time guidelines, weighing urban versus rural settings and incident severity. Civil penalties reach $5,000 for failing to dispatch a technician and up to $10,000 per vehicle when an obstruction lasts more than 30 minutes. City attorneys and county counsel can sue to enforce. The provisions become operative July 1, 2028.
The strongest case for the law
The case for SB 1246 rests on a real failure. According to Sen. Dave Cortese's office, an autonomous vehicle stalled near a grass fire in Redwood City in August 2025, and a CHP officer needed about 30 minutes to move it. During the December 2025 San Francisco blackout, roughly 1,500 Waymos stalled. Responders reportedly faced delays of up to 53 minutes in reaching AV companies. The San Francisco Standard reports that Waymo logged 1,593 vehicle stops of two minutes or more during that outage, yet dispatched staff or tow trucks for only 64 vehicles. It also reports 31 instances of robotaxis blocking first responders in San Francisco since April 2025.
If a city cannot tell where disabled vehicles are, it cannot route ambulances around them. A private fleet that can see every car in real time should not make public safety officials guess. That is a fair argument, and it is the one that carries the notification mandate.
Why the data feed is the proportionate part
A fleet-failure notification is narrow in scope. It triggers only on system-wide events, not routine incidents. It asks for location and status, which operators already hold. It also serves a public function: emergency coordination. This is the kind of targeted transparency that an innovation-friendly framework should accept, because it does not dictate how the technology works. It specifies what the public sector must be told when the technology fails at scale.
The law also leaves the details to a regulator. The DMV's guideline-setting role, with a 2028 runway, allows response times to differ between downtown San Francisco and a rural county road. That is better than a single statutory clock.
Where the law overreaches
The Autonomous Vehicle Industry Association, Waymo and more than 30 industry partners argued in a June 26 letter, as reported by the SF Standard, that the notification requirements would be "onerous and require companies to deploy technicians for minor incidents that don't create a safety hazard." That objection has force against the technician mandate. "Immediately dispatch" a person to every obstruction is a staffing rule, not an outcome rule. It could push operators to hire for worst-case peaks rather than invest in the remote recovery that the December blackout showed was inadequate.
The U.S.-based remote driver requirement is a similar blunt instrument. Training and licensing standards for remote operators are legitimate. Geography is a poor proxy for competence, and it adds cost without a demonstrated safety gain. A rule keyed to qualification and latency would address the same concern.
The 30-minute penalty is the most defensible enforcement hook because it is tied to a measurable harm: blocked emergency access. Even so, penalties of up to $10,000 per vehicle can scale quickly in a blackout affecting hundreds of cars. DMV guidelines should say clearly whether a good-faith, documented recovery effort mitigates liability.
It builds on existing rules
The law lands on top of DMV regulations effective May 1, 2026. As local reporting described them, those rules let police issue citations to AV manufacturers for moving violations and impose a 30-second response requirement for calls from emergency officials. California is therefore layering statute over regulation. Regulators should check how the two interact before adding more, so that operators face a coherent obligation set rather than overlapping clocks.
What to watch
Three things will determine whether SB 1246 is a model or a cautionary tale. First, what the DMV's response-time guidelines say before the July 1, 2028 operative date. Second, whether the data feed uses a standard format, so a city is not integrating separate feeds from each operator. Third, whether the data is handled with clear limits on retention and secondary use, since a location feed of a private fleet is also a mobility dataset. The law is silent on that in the summary we reviewed, and cities should not treat the feed as a general surveillance resource.
The lesson for other states is to copy the data-sharing mandate, which is cheap and targeted, and to be more careful about copying fixed staffing requirements. Public safety needs information first. Headcount rules are only one way to get there.