180 incidents on record · 2026 Headlights Incident reports by Ellie Harris · Melbourne
10 new this week Library last updated 30 August 2026
← The incident library
HD-INC-124
Autonomous vehicles and ride-hailing · United States · 2025 · Safety-critical driving rule not enforced

US regulators opened an investigation after Waymo's driverless taxis were recorded passing stopped school buses with their lights flashing and stop arms out, and Waymo recalled the software on more than 3,000 vehicles

By Ellie Harris · Filed Incidents during 2025; NHTSA investigation opened October 2025

Alleged: Waymo (Alphabet) developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

US regulators opened an investigation after Waymo's driverless taxis were recorded passing stopped school buses with their lights flashing and stop arms out, and Waymo recalled the software on more than 3,000 vehicles

What happened

It was reported that during 2025 Waymo’s driverless taxis, which carry passengers with no safety driver at the wheel, were recorded more than once driving past school buses that had stopped to let children on or off, with their red lights flashing and their stop arms extended. In September a television station in Atlanta aired video of a Waymo doing this. A school district in Austin, Texas, said it had documented 19 cases of Waymo vehicles illegally passing stopped school buses over the school year, including one in which a car went by moments after a child had crossed in front of it.

It was reported that in October 2025 the United States road safety regulator, the National Highway Traffic Safety Administration, opened an investigation into how Waymo’s cars behave around stopped school buses, and that it later widened the inquiry. The regulator noted that the cases already recorded were likely to be only part of the picture. Waymo said it had identified a problem in its software and, in December 2025, filed a voluntary recall covering more than 3,000 vehicles, with its chief safety officer saying the company had decided to file the recall so its cars would slow and stop properly in these situations. The school district in Austin said some of the passes it recorded had happened after Waymo told it the software had been updated. No injuries were reported.

What an auditable version would have shown

A stopped school bus with its lights flashing and its stop arm out is one of the clearest rules on the road: the traffic around it must stop. The question an audit answers is why a car that could see the bus did not stop, and how often it happened across the fleet. A signed record of each encounter, what the car detected, what rule applied, and what it did, turns a set of filmed near misses into a count the operator and the regulator can read: how many times a Waymo met a stopped school bus, and how many times it failed to stop. What the school district had to gather by watching was, in a system that keeps such a record, already a number.

Where the gap was

The car could see the stopped school bus and drove past it anyway. What brought that to light was people filming it and a school district keeping count, not the car ever registering that it had done anything wrong. A ConstraintGate encodes a hard rule, such as remaining stopped for a school bus showing its stop signal, as a check the car must satisfy before it moves, so the rule holds every time rather than most of the time. A ConductRecord keeps each encounter and what the car did, so a pattern of failures is visible from the record. A MetricRecord keeps the count across the fleet, so the rate at which the rule is broken is a figure the operator watches rather than one an outside body assembles after the fact. The recall changed the software. The record is what shows whether the change holds.

What governance should have looked like

A driverless car carrying passengers on public roads has to treat the most important traffic rules as limits it cannot cross, not as behaviour it usually gets right. Best practice would be for the operator to encode a rule like stopping for a school bus as a check the car must pass before it proceeds, to keep a record of every such encounter and what the car did, and to track across the whole fleet how often the rule is met and how often it is broken, so a problem shows up as a rising number rather than as a video. Waymo found the problem and recalled the software. Whether the fix holds, on every car and every time, is something a record of these encounters can show.

Failure Pattern: a driverless vehicle that could detect a stopped school bus failed to stop for it, and the failures were found by people filming and counting rather than caught by the system and measured across the fleet.

Governance Principle: a safety-critical rule for an autonomous system must be enforced as a hard check before the action, every encounter must be recorded, and the rate at which the rule holds must be measured across the fleet.

The reference implementation of ConstraintGate, ConductRecord and MetricRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

No tracking. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and Waymo (Alphabet) could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →