Incident · Collision
ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14856)
On April [XXX], 2026 at 6:13 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] when it initiated a left turn onto southbound [XXX]. As the Waymo AV was exiting the intersection, it came to a stop facing south to yield to a heavy truck traveling north on [XXX] with vehicles parked at the curb in both directions. While the Waymo AV was stopped, the heavy truck proceeded to pass the Waymo AV and began to initiate a left turn onto westbound [XXX], and the left side of the heavy truck made contact with the rear 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.
Occurred 2026-04-01 · Waymo
Machine-readable surfaces
- Markdown mirror: /incidents/nhtsa-sgo-30270-14856.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/805de5d8-cfbf-4c34-8317-a50edfa0e501
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Common questions
- What happened in ADS crash report in Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14856)?
- On April [XXX], 2026 at 6:13 PM CT a Waymo Autonomous Vehicle ("Waymo AV") operating in Austin, Texas was in a collision involving a heavy truck on [XXX] at [XXX]. The Waymo AV was traveling west on [XXX] when it initiated a left turn onto southbound [XXX]. As the Waymo AV was exiting the intersection, it came to a stop facing south to yield to a heavy truck traveling north on [XXX] with vehicles parked at the curb in both directions. While the Waymo AV was stopped, the heavy truck proceeded to pass the Waymo AV and began to initiate a left turn onto westbound [XXX], and the left side of the heavy truck made contact with the rear 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 April 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 Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14856)?
- 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 Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14856)?
- 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 Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14856)?
- 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 Austin, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-14856).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 805de5d8-cfbf-4c34-8317-a50edfa0e501