_Incident · Collision_

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

Canonical ID: `14b062e4-aa13-464d-a43f-462cb3380e77`

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

On November [XXX], 2025 at 4:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX].
The Waymo AV was traveling northeastbound on [XXX], with its right turn signal activated, when it slowed to a stop for a stop sign at the intersection with [XXX]. The Waymo AV proceeded forward slowly as it was yielding to vehicles traveling southeastbound on [XXX] and preparing to turn right onto [XXX]. While the Waymo was proceeding forward, a passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear 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. The passenger in the Waymo AV was not belted at the time of the collision. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries.

Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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-13167

## Common questions

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

On November [XXX], 2025 at 4:52 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Los Angeles, California was in a collision involving a passenger car on [XXX] at [XXX].
The Waymo AV was traveling northeastbound on [XXX], with its right turn signal activated, when it slowed to a stop for a stop sign at the intersection with [XXX]. The Waymo AV proceeded forward slowly as it was yielding to vehicles traveling southeastbound on [XXX] and preparing to turn right onto [XXX]. While the Waymo was proceeding forward, a passenger car traveling northeastbound on [XXX] approached the Waymo AV from behind and the front of the passenger car made contact with the rear 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. The passenger in the Waymo AV was not belted at the time of the collision. The passenger in the Waymo AV was transported to a hospital by an ambulance with unknown injuries.

Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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 November 1, 2025 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-13167)?

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

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

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


_API: GET /v1/incidents/14b062e4-aa13-464d-a43f-462cb3380e77 · sources: /v1/incidents/14b062e4-aa13-464d-a43f-462cb3380e77/sources · responses: /v1/incidents/14b062e4-aa13-464d-a43f-462cb3380e77/responses · status: /v1/incidents/14b062e4-aa13-464d-a43f-462cb3380e77/status · canonical URL: /incidents/nhtsa-sgo-30270-13167_