Incident · Collision
ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-14890)
On May [XXX], 2026 at 9:51 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when it slowed to a stop in-lane to yield to a second Waymo AV parked facing north near the east curb on [XXX] and partially in-lane with its hazard lights activated ("Parked Waymo AV"). After stopping momentarily, the Waymo AV proceeded forward to pass the Parked Waymo AV on the left and a passenger in the Parked Waymo AV opened the rear left door of the Parked Waymo AV. The front right side of the Waymo AV made contact with the open rear left door of the Parked 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.
Occurred 2026-05-01 · Waymo
Machine-readable surfaces
- Markdown mirror: /incidents/nhtsa-sgo-30270-14890.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/ea50e77f-d4dc-4635-82fa-22516633d083
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Common questions
- What happened in ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-14890)?
- On May [XXX], 2026 at 9:51 PM MT a Waymo Autonomous Vehicle ("Waymo AV") operating in Phoenix, Arizona was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northbound on [XXX] when it slowed to a stop in-lane to yield to a second Waymo AV parked facing north near the east curb on [XXX] and partially in-lane with its hazard lights activated ("Parked Waymo AV"). After stopping momentarily, the Waymo AV proceeded forward to pass the Parked Waymo AV on the left and a passenger in the Parked Waymo AV opened the rear left door of the Parked Waymo AV. The front right side of the Waymo AV made contact with the open rear left door of the Parked 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 May 1, 2026 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-14890)?
- 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-14890)?
- 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-14890)?
- This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 1 source (1 primary) · last reviewed 2026-07-12
Verification posture
Unreviewed
Low confidence
Review state
Stable
Last reviewed 2026-07-12
Sources by quality tier
- 1
- primary-regulatory-filing
- Regulatory filing
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for ADS crash report in Phoenix, AZ involving a JAGUAR I-PACE (NHTSA SGO 30270-14890).Deploy Watch
Track this incident.
We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.
Canonical ID ea50e77f-d4dc-4635-82fa-22516633d083