AI Risk Wire

Cases › physical harm › LR-2026-0370

Waymo robotaxi collision with child near elementary school, Santa Monica (January 2026)

Confirmed Why: 2 independent outlets · 2 independent reports

Status: action reported, no fix

Severity moderate
Reported 29 Jan 2026
Developer and model Waymo · 5th Generation Automated Driving System
Industry transportation

No source states: loss or records, agent tool, could do, deployer.

Severity moderate: bounded scope stated (one child, minor injuries per NHTSA records); no broader third-party or system impact is stated

A Waymo robotaxi running its 5th Generation Automated Driving System with no human safety supervisor was involved in a collision in Santa Monica, California, near an elementary school during normal school drop-off hours. The child ran out from behind a double-parked SUV. According to Waymo, the vehicle detected the person as they emerged and braked hard, reducing speed from about 17 mph to under 6 mph before contact. NHTSA records state the child sustained minor injuries. After contact the pedestrian stood up and walked to the sidewalk, Waymo called 911, and the vehicle stopped at the roadside until law enforcement cleared it. NHTSA opened an investigation into whether the vehicle exercised appropriate caution, and the NTSB opened its own investigation in coordination with local police.

What happened

1 · What it reached or didNHTSA records state the child sustained minor injuries.
2 · How it was caughtWaymo itself informed NHTSA of the collision.

What was done

The incident is now being investigated by the U.S. vehicle safety authority.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Stop control

Application

Physical safety interlocks · Human approval for high-impact actions · Live behaviour monitoring · Adversarial testing before deployment

Similar incidents

All cases of this kind ›

Evidence

No source states: what the AI was doing, what went wrong, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.

Show the full account: 6 items from the primary sources

What happened, in order

  1. January 23 Waymo robotaxi struck a child near an elementary school in Santa Monica.

Not dated in the sources:

  • Collision occurred within two blocks of an elementary school during normal school drop-off hours.
  • After contact the pedestrian stood up and walked to the sidewalk, and Waymo called 911.
  • The vehicle remained stopped at the side of the road until law enforcement cleared it to leave.
  • NHTSA opened an investigation into the accident.
  • The NTSB said it opened an investigation in coordination with the Santa Monica Police Department.
Show every field, with its source and grade

The AI system

Model
5th Generation Automated Driving System
C one secondary source states it
Developer
Waymo
C one secondary source states it
How much it acted alone
it acted alone, unwatched
C one secondary source states it

What happened

Earliest source we hold
2026-01-29
D inferred by us from the described behaviour, reason shown
What went wrong
physical harm
C one secondary source states it
AI agent
an AI agent acted
C one secondary source states it
primary risk
RK18
D inferred by us from the described behaviour, reason shown

Impact

Severity
moderate
D inferred by us from the described behaviour, reason shown
Kind of harm
bodily harm
C one secondary source states it
Why this severity
bounded scope stated (one child, minor injuries per NHTSA records); no broader third-party or system impact is stated
D inferred by us from the described behaviour, reason shown

Context

Industry
transportation
C one secondary source states it
Country
United States
C one secondary source states it

Notes on gaps

The child's age and identity are not public. NHTSA and NTSB investigations were still open. The school bus probes and the Los Angeles Zeekr incident are separate incidents and were excluded. No remediation is reported in the sources. Reversibility is not stated.

LR-2026-0370 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON