DEPLOYDatabase

Incident · Collision

ADS crash report in Redwood City, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15195)

On May [XXX], 2026 at 12:27 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Redwood City, California was in a collision involving a passenger car on [XXX] near the northwestbound [XXX] off-ramp. The Waymo AV was traveling southwestbound in the third from the right lane on [XXX] when a passenger car, that was initially stopped in a queue of traffic, partially in the rightmost lane and partially in the second from the right lane, maneuvered to the left and entered the Waymo AV's lane of travel, and the front left side of the passenger car made contact with the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.

Occurred 2026-05-01 · 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 (1)

  1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30270-15195

Common questions

What happened in ADS crash report in Redwood City, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15195)?
On May [XXX], 2026 at 12:27 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Redwood City, California was in a collision involving a passenger car on [XXX] near the northwestbound [XXX] off-ramp. The Waymo AV was traveling southwestbound in the third from the right lane on [XXX] when a passenger car, that was initially stopped in a queue of traffic, partially in the rightmost lane and partially in the second from the right lane, maneuvered to the left and entered the Waymo AV's lane of travel, and the front left side of the passenger car made contact with the right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. Waymo is reporting this crash under Request No. 2 of Standing General Order 2021-01. Waymo may supplement or correct its reporting with additional information as it may become available.
When did this incident occur?
The incident is recorded as occurring on May 1, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in ADS crash report in Redwood City, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15195)?
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 ADS crash report in Redwood City, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15195)?
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 ADS crash report in Redwood City, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15195)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (1 primary) · last reviewed 2026-07-19

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-07-19

Sources by quality tier

1
primary-regulatory-filing
Regulatory filing

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

Methodology surface for ADS crash report in Redwood City, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-15195).

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 e0dea8b8-0deb-46e2-b408-04302784747a