DEPLOYDatabase

Incident · Collision

ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14832)

On April [XXX], 2026 at 1:45 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southeastbound in the rightmost lane on [XXX] when it slowed to a stop at a green light at the intersection with [XXX] to yield to a passenger car traveling westbound in the rightmost lane of [XXX] at a high rate of speed. While the Waymo AV was stopped, the passenger car entered the intersection and initiated a wide right turn onto southeastbound [XXX], against the proper direction of traffic. As the passenger car exited the intersection into the southeastbound lanes of [XXX], the left side of the passenger car made contact with the left side of the stationary 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-04-01 · Waymo

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14832)?
On April [XXX], 2026 at 1:45 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a passenger car on [XXX] at [XXX]. The Waymo AV was traveling southeastbound in the rightmost lane on [XXX] when it slowed to a stop at a green light at the intersection with [XXX] to yield to a passenger car traveling westbound in the rightmost lane of [XXX] at a high rate of speed. While the Waymo AV was stopped, the passenger car entered the intersection and initiated a wide right turn onto southeastbound [XXX], against the proper direction of traffic. As the passenger car exited the intersection into the southeastbound lanes of [XXX], the left side of the passenger car made contact with the left side of the stationary 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 April 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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14832)?
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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14832)?
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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14832)?
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-12

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-07-12

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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14832).

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 fa4a456b-d3c4-4bf2-8c1f-9d58cba01c78