DEPLOYDatabase

Incident · Collision

Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured

A two-vehicle collision at approximately 5:45 AM on July 26, 2026, near Venice Boulevard and Toberman Street in the Pico-Union neighborhood of Los Angeles involved a Waymo robotaxi. Per Waymo, a blue sedan traveling at 47-50 mph in the opposite direction struck a pedestrian with a cart outside a crosswalk at ~42 mph, then swerved into the opposite lane and hit the Waymo vehicle traveling east at ~27 mph.

At least two people were hospitalized (one critically) and several others were treated at the scene. LAPD investigation ongoing; Waymo states its vehicle was not at fault.

Occurred 2026-07-26 · Waymo

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.

Machine-readable surfaces

Sources (3)

  1. Los Angeles Times · https://www.latimes.com/california/story/2026-07-26/multiple-people-injured-pico-union-collision-waymo · 2026-07-26
  2. KTLA · https://ktla.com/news/local-news/waymo-involved-in-los-angeles-collision-that-left-2-hospitalized/ · 2026-07-26
  3. ABC7 Los Angeles · https://abc7.com/amp/post/2-car-crash-involving-waymo-vehicle-pico-union-leaves-1-hospitalized/19580056/ · 2026-07-26

Status history

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

Common questions

What happened in Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured?
A two-vehicle collision at approximately 5:45 AM on July 26, 2026, near Venice Boulevard and Toberman Street in the Pico-Union neighborhood of Los Angeles involved a Waymo robotaxi. Per Waymo, a blue sedan traveling at 47-50 mph in the opposite direction struck a pedestrian with a cart outside a crosswalk at ~42 mph, then swerved into the opposite lane and hit the Waymo vehicle traveling east at ~27 mph. At least two people were hospitalized (one critically) and several others were treated at the scene. LAPD investigation ongoing; Waymo states its vehicle was not at fault.
When did this incident occur?
The incident is recorded as occurring on July 26, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured?
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 Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured?
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 Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 3 sources (no primary) · last reviewed 2026-08-09

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

3
unclassified
Unclassified source

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

Methodology surface for Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured.

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 bf0c7698-331d-49cc-8628-9f9914ca2ef0