Waymo Hit a Child Outside a School and Offered Its Own Data as Proof of Safety
What happened
In January 2026, a fully autonomous Waymo robotaxi struck a child near an elementary school in Santa Monica, California, during the morning drop-off rush. The child had run from behind a double-parked SUV into the street. Other children, a crossing guard, and several vehicles were already in the area. The child sustained minor injuries and walked back to the pavement.
Waymo reported the incident voluntarily, a move that also handed the company its opening defense. Using data from the vehicle, Waymo argued its system outperformed a human driver in the same situation, claiming a human would have struck the child at 14 mph. The National Highway Traffic Safety Administration opened a preliminary investigation regardless, examining whether the robotaxi had "exercised appropriate caution" near the school during drop-off hours and whether the vehicle stayed within the posted speed limit.
The "safer than a human" framing did not go far with the school community or with regulators now asking follow-up questions. The underlying complaint was not whether the vehicle beat some average of all road scenarios. It was whether a vehicle running through a school zone during the predictable high-risk window of morning drop-off should be held to a different standard than that average allows. Proximity to children on a known schedule is a design input, not a mitigating circumstance.
The Santa Monica collision did not arrive without a history. School districts in Austin and Atlanta had previously asked Waymo to pause operations during bell times, citing reports of its vehicles illegally passing stopped school buses. Waymo declined both requests. Federal investigators were now asking the questions those districts had asked and not gotten answered. The incident also coincided with a U.S. Senate Commerce Committee hearing on self-driving safety, bringing the question of school-zone restrictions into legislative view for the first time.
What the incident exposed is a structural gap in how autonomous-vehicle collisions are reported. Waymo held the data and chose how to release it. There is no independent requirement to produce a continuous, verifiable account of what the vehicle detected, how fast it was moving, and what decision the system made in the moments before impact. The public record of any collision comes from the operator. A provable record of what a system did, accessible to regulators and not mediated by the company whose liability depends on the answer, is the accountability layer the current framework does not require.
Reported impact
- Affected parties
- Not publicly disclosed
- Harm type
- Not publicly disclosed
- Scale
- Not publicly disclosed
- Financial impact
- Not publicly disclosed
- Regulatory action
- Not publicly disclosed
Classification
Relevant governance controls
Governance control mapping is not available for this record.
- No controls mapped
Not publicly disclosed
Control mapping is analytical. It does not state that any control would have prevented the incident.
Sources and evidence
This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.