_Incident · Collision_

# ADS crash report in Brisbane, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13507)

Canonical ID: `5c68c9ab-9e2b-46df-a856-42564a3a637f`

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

On December [XXX], 2025 at 5:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Brisbane, California was in a collision involving a heavy truck on [XXX] at a parking lot entrance at [XXX].
The Waymo AV was traveling eastbound in the right lane on [XXX] when it began to slow for a heavy truck traveling eastbound in the right lane on [XXX] in front of the Waymo AV. The heavy truck changed lanes to the left and the Waymo AV proceeded forward in the right lane, adjacent to the heavy truck. The heavy truck then proceeded to turn right from the left lane into the parking lot at [XXX], entering the Waymo AV's lane of travel. The Waymo AV slowed to a stop as the heavy truck continued to turn, and the right of the heavy truck trailer made contact with the front 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. 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.

## Sources (1)

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

## Common questions

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

On December [XXX], 2025 at 5:54 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in Brisbane, California was in a collision involving a heavy truck on [XXX] at a parking lot entrance at [XXX].
The Waymo AV was traveling eastbound in the right lane on [XXX] when it began to slow for a heavy truck traveling eastbound in the right lane on [XXX] in front of the Waymo AV. The heavy truck changed lanes to the left and the Waymo AV proceeded forward in the right lane, adjacent to the heavy truck. The heavy truck then proceeded to turn right from the left lane into the parking lot at [XXX], entering the Waymo AV's lane of travel. The Waymo AV slowed to a stop as the heavy truck continued to turn, and the right of the heavy truck trailer made contact with the front 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. 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 December 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 Brisbane, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13507)?

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 Brisbane, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13507)?

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 Brisbane, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-13507)?

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


_API: GET /v1/incidents/5c68c9ab-9e2b-46df-a856-42564a3a637f · sources: /v1/incidents/5c68c9ab-9e2b-46df-a856-42564a3a637f/sources · responses: /v1/incidents/5c68c9ab-9e2b-46df-a856-42564a3a637f/responses · status: /v1/incidents/5c68c9ab-9e2b-46df-a856-42564a3a637f/status · canonical URL: /incidents/nhtsa-sgo-30270-13507_