DEPLOYDatabase

Incident · Collision

ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14234)

On March [XXX], 2026 at 8:26 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked facing southwest at the curb on [XXX] with its hazard lights activated for a passenger drop-off. While the Waymo AV remained parked, a passenger car traveling southwestbound along the curb of [XXX] at a high rate of speed began to enter into the adjacent lane, in front of a second passenger car's lane of travel, as it approached the Waymo AV from behind. As the passenger car proceeded to pass the Waymo AV on the left, the front right side of the passenger car made contact with the rear left side of the parked Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

Occurred 2026-03-01 · Waymo

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14234)?
On March [XXX], 2026 at 8:26 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] near [XXX]. The Waymo AV was parked facing southwest at the curb on [XXX] with its hazard lights activated for a passenger drop-off. While the Waymo AV remained parked, a passenger car traveling southwestbound along the curb of [XXX] at a high rate of speed began to enter into the adjacent lane, in front of a second passenger car's lane of travel, as it approached the Waymo AV from behind. As the passenger car proceeded to pass the Waymo AV on the left, the front right side of the passenger car made contact with the rear left side of the parked Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV sustained damage. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because a vehicle involved was towed away. 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 March 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 Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14234)?
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 Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14234)?
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 Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14234)?
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 Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14234).

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 46841130-4bbb-493b-b5a6-9cf980b016a0