Robotaxis and Emergency Responders: A Timeline of the 2026 Federal Crackdown

On 8 July 2026, the administrator of the National Highway Traffic Safety Administration sent a letter to autonomous vehicle developers that did something regulators had until then avoided: it treated robotaxis blocking emergency crews not as a series of unlucky edge cases, but as a design failure.

Jonathan Morrison wrote that the inability to detect and respond to emergency scenes “represents a functional insufficiency”, according to TechCrunch, which reported the letter. He gave developers until the end of July to present solutions. That deadline has now passed. Three weeks later, a member of Congress introduced a bill that would write the requirements into federal law.

This is a record of how the confrontation developed, what the federal count captured, and what it missed.

The timeline

What the regulator actually said

The letter did not name a single company. That omission matters: it framed the problem as an industry-wide capability gap rather than one operator's bad month. The behaviours it described were specific — vehicles driving into active emergency scenes, blocking ambulances and fire apparatus, and failing to recognise flashing lights, flares, smoke, fire and traffic cones.

Morrison also drew a comparison that carries more weight than it might first appear. A human driver who impedes law enforcement faces fines and, in some circumstances, jail. He said the agency intends to hold companies accountable in comparable terms. Applied to a driverless fleet, that principle has no settled mechanism behind it yet — which is precisely the gap the new bill is written to fill.

Six incidents, or thirty-one?

The most revealing number in this story is the distance between two counts.

NHTSA documented at least six incidents nationally through March 2026 in which first responders had to intervene with a driverless vehicle. Over a broadly overlapping period, The San Francisco Standard obtained at least 31 internal San Francisco Fire Department reports describing robotaxis obstructing emergency operations — in one city.

The two figures are not measuring quite the same thing, and the federal number is drawn from a narrower definition. But the gap points to something structural: the incidents that reach federal awareness are a fraction of those local crews write up. A regulator acting on six data points is regulating a problem it can only partly see.

One pairing in the San Francisco records illustrates the cost of that lag. Lieutenant Michael F. Digre reported on 8 May 2025 that a Waymo had blocked the positioning of an aerial ladder at a building fire. On 6 April 2026 — eleven months later — the same officer filed an almost identical report. In the interval between those two documents, nothing in the vehicle's behaviour appears to have changed.

The bill now on the table

Rep. Kevin Mullin introduced the AV Emergency Response Coordination Act on 28 July at a San Francisco press conference, joined by Mayor Daniel Lurie, Fire Chief Dean Crispen and Cathy Chase, president of Advocates for Highway and Auto Safety.

The bill would direct federal regulators to set minimum national safety standards for autonomous vehicles, and it contains three provisions aimed squarely at the incidents above: clear emergency protocols for first responders, a hotline staffed around the clock that public officials can reach directly, and the ability for local authorities to request geofencing that keeps robotaxis out of an area during an emergency.

The hotline provision responds to a recurring complaint in the San Francisco reports. In one February incident on Sanchez Street, in Duboce Triangle, a Waymo stuck facing the sidewalk blocked a fire engine answering a medical call; the company representatives reached by crews were described in the report as “very uncooperative”. The geofencing provision responds to the 4 July breakdown, where the vehicles sent to recover stalled robotaxis were blocked by other stalled robotaxis.

Where the companies stand

Waymo declined to comment on the July letter, TechCrunch reported. On the bill, the company said it “has long supported a federal framework” and backs standardising how developers engage with first responders. Responding to the San Francisco reports, it said its goal is “to support first responders, not create additional work for them”.

The company also offers a figure that deserves to be weighed rather than dismissed: it says its vehicles interact with 50,000 emergency vehicles a week in California. If accurate, it places the documented failures against a very large denominator, and it is the strongest argument the industry has that these are rare events rather than a systemic defect.

It is also, on its own, not quite an answer. Emergency response is a domain where the rate matters less than the tail: a fleet that handles 49,999 interactions correctly and parks on a fire hose for the last one has still parked on a fire hose. That is the reasoning behind Morrison's choice of words. “Functional insufficiency” is not a claim about frequency. It is a claim about capability.

What to watch next

Three things will determine whether this becomes binding or fades. First, whether NHTSA discloses what developers submitted against its end-of-July deadline, and whether it treats those submissions as sufficient. Second, whether Mullin's bill attracts co-sponsors outside California, since the incidents driving it are concentrated in cities where robotaxis already operate at scale. Third, whether local fire departments beyond San Francisco publish comparable records — the 31 reports exist as a public number only because a news organisation requested them.

That last point is the one to watch most closely. The regulatory response so far has been shaped less by federal data collection than by a single city's paperwork becoming visible. If other departments release theirs, the six-incident national picture will not survive contact with them.

If you follow autonomous vehicle policy, this timeline is worth keeping to hand — and worth passing to anyone still treating these as isolated glitches.

Sources

Reporting by TechCrunch (8 July 2026, 28 July 2026), The San Francisco Standard (10 July 2026) and Mission Local (July 2026). Fire chief's name as recorded by the City and County of San Francisco.