_Incident · Collision_

# ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11204)

Canonical ID: `63b6f867-df87-47c4-b9c4-a47782d45c75`

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

On June [XXX], 2025 at 5:58 AM MT a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a van at the entrance of a parking lot at [XXX]. 
The Waymo AV was stopped facing south at the entrance of a parking lot at [XXX] while yielding to traffic and preparing to make a left turn at the intersection at [XXX]. As the Waymo AV remained stopped, a van traveling westbound in the rightmost lane on [XXX] traveled onto the north sidewalk of [XXX]. It then entered the parking lot entrance from the sidewalk, traveling perpendicular to the standard direction of travel. The front of the van made contact with the front driver side of the Waymo AV, which was still stationary at intersection, causing the Waymo AV to spin and the front of the Waymo AV to then make contact with a sign pole. 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. 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-11204

## Common questions

### What happened in ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11204)?

On June [XXX], 2025 at 5:58 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a van at the entrance of a parking lot at [XXX]. 
The Waymo AV was stopped facing south at the entrance of a parking lot at [XXX] while yielding to traffic and preparing to make a left turn at the intersection at [XXX]. As the Waymo AV remained stopped, a van traveling westbound in the rightmost lane on [XXX] traveled onto the north sidewalk of [XXX]. It then entered the parking lot entrance from the sidewalk, traveling perpendicular to the standard direction of travel. The front of the van made contact with the front driver side of the Waymo AV, which was still stationary at intersection, causing the Waymo AV to spin and the front of the Waymo AV to then make contact with a sign pole. 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. 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 June 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 Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11204)?

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 Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11204)?

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 Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-11204)?

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


_API: GET /v1/incidents/63b6f867-df87-47c4-b9c4-a47782d45c75 · sources: /v1/incidents/63b6f867-df87-47c4-b9c4-a47782d45c75/sources · responses: /v1/incidents/63b6f867-df87-47c4-b9c4-a47782d45c75/responses · status: /v1/incidents/63b6f867-df87-47c4-b9c4-a47782d45c75/status · canonical URL: /incidents/nhtsa-sgo-30270-11204_