_Incident · Collision_

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

Canonical ID: `54c89b63-d476-40b0-bcde-b1da58b748d5`

- **Occurred:** 2026-08-01
- **Kind:** `collision`
- **Status (derived):** active
- **Company:** [Waymo](/companies/waymo.md) (id: `2128addc-20c8-4c31-aef5-be5ada97aede`)

On August [XXX], 2026 at 12:38 AM PDT a [Waymo](/companies/waymo.md) Autonomous Vehicle (Waymo AV) operating in [Los Angeles](/locations/los-angeles.md), [California](/locations/california.md) was in a collision involving a passenger car on [XXX] near [XXX].

The Waymo AV was stopped in traffic at a red light facing west on [XXX], in the third lane from the right. While waiting in the traffic queue, a passenger vehicle in front of the Waymo AV began to roll in reverse. As the passenger car reversed, the Waymo AV reversed several feet. As the passenger car continued to reverse, the open door of the passenger vehicle made contact with the right side of a second passenger car stopped in the adjacent left lane as well as with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage.

Waymo is reporting this crash under Request No. 1 of [Standing General Order 2021-01](/regulations/nhtsa-av-framework.md) because a vehicle involved was towed away. Waymo may supplement or correct its reporting with additional information as it may become available.

## Sources (1)

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

## Common questions

### What happened in ADS crash report in Los Angeles, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-16202)?

On August [XXX], 2026 at 12:38 AM PDT a [Waymo Autonomous Vehicle](/models/alphabet-waymo.md) ([Waymo](/companies/waymo.md) AV) operating in [Los Angeles](/locations/los-angeles.md), [California](/locations/california.md) was in a collision involving a passenger car on [XXX] near [XXX].

The Waymo AV was stopped in traffic at a red light facing west on [XXX], in the third lane from the right. While waiting in the traffic queue, a passenger vehicle in front of the Waymo AV began to roll in reverse. As the passenger car reversed, the Waymo AV reversed several feet. As the passenger car continued to reverse, the open door of the passenger vehicle made contact with the right side of a second passenger car stopped in the adjacent left lane as well as with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. All three vehicles sustained damage.

Waymo is reporting this crash under Request No. 1 of [Standing General Order 2021-01](/regulations/nhtsa-av-framework.md) 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 August 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-16202)?

The incident is recorded as involving [Waymo](/companies/waymo.md) 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-16202)?

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-16202)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/54c89b63-d476-40b0-bcde-b1da58b748d5 · sources: /v1/incidents/54c89b63-d476-40b0-bcde-b1da58b748d5/sources · responses: /v1/incidents/54c89b63-d476-40b0-bcde-b1da58b748d5/responses · status: /v1/incidents/54c89b63-d476-40b0-bcde-b1da58b748d5/status · canonical URL: /incidents/nhtsa-sgo-30270-16202_