DEPLOYDatabase

Incident · Regulatory action

NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders

In July 2026, NHTSA Administrator Jonathan Morrison issued a directive to autonomous vehicle developers requiring them to ensure their vehicles get out of the way of first responders. The letter cited a clear pattern of driverless AVs interfering with law enforcement and other first responders, including incidents where AVs drove into active emergency scenes, blocked the paths of ambulances or firefighters, or failed to recognize or respond to flashing lights, flares, smoke, fire, and traffic cones. The directive preceded Zoox's smoke-detection recall and follows multiple Waymo recalls for construction-zone and flooded-roadway entry failures.

Occurred 2026-07-09 · Waymo · Investigated by NHTSA

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders

Machine-readable surfaces

Sources (2)

  1. NHTSA · https://www.nhtsa.gov/document/ads-developer-letter-july-2026 · 2026-07-09
  2. CNBC · https://www.cnbc.com/2026/07/17/amazon-zoox-recalls-robotaxi-smoke.html · 2026-07-17

Status history

  • Active · 2026-07-25 · agent:recon

Common questions

What happened in NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders?
In July 2026, NHTSA Administrator Jonathan Morrison issued a directive to autonomous vehicle developers requiring them to ensure their vehicles get out of the way of first responders. The letter cited a clear pattern of driverless AVs interfering with law enforcement and other first responders, including incidents where AVs drove into active emergency scenes, blocked the paths of ambulances or firefighters, or failed to recognize or respond to flashing lights, flares, smoke, fire, and traffic cones. The directive preceded Zoox's smoke-detection recall and follows multiple Waymo recalls for construction-zone and flooded-roadway entry failures.
When did this incident occur?
The incident is recorded as occurring on July 9, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders?
The incident is recorded as involving Waymo on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (1 primary) · last reviewed 2026-08-09

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

1
primary-regulatory-filing
Regulatory filing
1
secondary-established-publication
Established publication

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for NHTSA issues directive to AV developers citing clear pattern of driverless AVs interfering with first responders.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID 03df96de-b7ce-4c2d-b502-68e78372cda2