_Incident · Collision_

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

Canonical ID: `13e83ee1-f282-4d80-8cf6-505ff6c3fac8`

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

On July [XXX], 2025 at 1:35 AM MT a [Waymo](/companies/waymo.md) Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near the [XXX] entrance.
The Waymo AV was traveling northeastbound on [XXX] in the right lane. A passenger car was traveling southwestbound on the wrong side of median-divided [XXX], directly in the Waymo AV's lane of travel.  The Waymo AV braked and initially maneuvered left to avoid the oncoming passenger car. However, the passenger car continued to proceed, maneuvering towards the Waymo AV. The Waymo AV then continued to brake and maneuvered back to the right, to again attempt to avoid the passenger car, but the passenger car once more maneuvered towards the Waymo AV. As the Waymo AV continued to brake and the passenger car continued off the southeast side of [XXX], the front passenger side of the passenger car made contact with the front passenger side 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.
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-11417

## Common questions

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

On July [XXX], 2025 at 1:35 AM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a passenger car on [XXX] near the [XXX] entrance.
The Waymo AV was traveling northeastbound on [XXX] in the right lane. A passenger car was traveling southwestbound on the wrong side of median-divided [XXX], directly in the Waymo AV's lane of travel.  The Waymo AV braked and initially maneuvered left to avoid the oncoming passenger car. However, the passenger car continued to proceed, maneuvering towards the Waymo AV. The Waymo AV then continued to brake and maneuvered back to the right, to again attempt to avoid the passenger car, but the passenger car once more maneuvered towards the Waymo AV. As the Waymo AV continued to brake and the passenger car continued off the southeast side of [XXX], the front passenger side of the passenger car made contact with the front passenger side 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.
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 July 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-11417)?

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

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

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


_API: GET /v1/incidents/13e83ee1-f282-4d80-8cf6-505ff6c3fac8 · sources: /v1/incidents/13e83ee1-f282-4d80-8cf6-505ff6c3fac8/sources · responses: /v1/incidents/13e83ee1-f282-4d80-8cf6-505ff6c3fac8/responses · status: /v1/incidents/13e83ee1-f282-4d80-8cf6-505ff6c3fac8/status · canonical URL: /incidents/nhtsa-sgo-30270-11417_