_Incident · Collision_

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

Canonical ID: `658cba7a-1736-40cf-bb24-8fb50b9bd717`

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

On August [XXX], 2025 at 12:42 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a section of removed pavement on [XXX] near [XXX]. 
The Waymo AV was traveling southbound through a construction zone on [XXX] in the rightmost lane delineated by a line of temporary orange pylons when it approached a parked construction truck in its lane of travel with a mounted arrow board displaying a flashing left arrow. The Waymo AV changed lanes to continue traveling southbound on [XXX] to the left of the line of pylons. As the Waymo AV continued to follow the path delineated by the pylons, it encountered a section of the pavement that had been removed creating a drop in the lane surface, and the front left wheel proceeded over the section of removed pavement.. 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-11500

## Common questions

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

On August [XXX], 2025 at 12:42 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving a section of removed pavement on [XXX] near [XXX]. 
The Waymo AV was traveling southbound through a construction zone on [XXX] in the rightmost lane delineated by a line of temporary orange pylons when it approached a parked construction truck in its lane of travel with a mounted arrow board displaying a flashing left arrow. The Waymo AV changed lanes to continue traveling southbound on [XXX] to the left of the line of pylons. As the Waymo AV continued to follow the path delineated by the pylons, it encountered a section of the pavement that had been removed creating a drop in the lane surface, and the front left wheel proceeded over the section of removed pavement.. 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 August 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-11500)?

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

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

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


_API: GET /v1/incidents/658cba7a-1736-40cf-bb24-8fb50b9bd717 · sources: /v1/incidents/658cba7a-1736-40cf-bb24-8fb50b9bd717/sources · responses: /v1/incidents/658cba7a-1736-40cf-bb24-8fb50b9bd717/responses · status: /v1/incidents/658cba7a-1736-40cf-bb24-8fb50b9bd717/status · canonical URL: /incidents/nhtsa-sgo-30270-11500_