ADS crash report in Dallas, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16196)
[COLLISION]Date Unspecified · Physical AI Entity
Failure Mode
COLLISION
Event Date
Date Unspecified
Primary Entity
Physical AI Entity
Robotic Platform
Cross-Fleet / Unspecified
Jurisdiction / Location
Federal / Global
Audit Standard
Physical State Verified
Incident Abstract & Audit Findings
On August [XXX], 2026 at 11:31 PM CDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Dallas, Texas was in a collision involving a pedestrian and an SUV on [XXX] near [XXX].
System & Fleet Architecture
Operating Manufacturer
Hardware Platform
Operational Sectors
Primary Sources & Evidentiary Filings
- Inspect Filing
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30270-16196
https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30270-16196
Related Incidents & Failure Precedents
6 records on file- Amazon Prime Air MK30 drone crashes into residential garden in Darlington, UK, prompting AAIB investigation[COLLISION]
Jul 29, 2026 · Amazon · Amazon Astro · Seattle
Details - Waymo robotaxi struck by blue sedan that had just hit a pedestrian in Pico-Union, Los Angeles; two hospitalized, one critically injured[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle collision in Los Angeles, multiple people hospitalized[COLLISION]
Jul 26, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Waymo robotaxi involved in two-vehicle crash in LA's Pico-Union, one person critically injured[COLLISION]
Jul 25, 2026 · Waymo · Waymo Driver (6th gen) · Sacramento, California, USA
Details - Tesla remote operator crashed a Robotaxi into a tree stump in Houston, NHTSA data shows[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details - Tesla robotaxi remote operator crashed vehicle into metal fence in Houston[COLLISION]
Jul 20, 2026 · Tesla · Tesla Robotaxi (Model Y ADS) · Orlando, Florida, USA
Details
Incident Context & FAQ
What happened in ADS crash report in Dallas, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16196)?
On August [XXX], 2026 at 11:31 PM CDT a Waymo Autonomous Vehicle ("Waymo AV") operating in Dallas, Texas was in a collision involving a pedestrian and an SUV on [XXX] near [XXX]. The Waymo AV was traveling northwestbound in the second lane from the right curb on [XXX] when it began slowing to yield to a pedestrian walking in the roadway ahead, within the southeastbound lanes of traffic. As the Waymo AV was slowing, an SUV traveling southeastbound in the second lane from the right curb struck the pedestrian, sending the pedestrian towards the Waymo AV. After contacting the ground, the pedestrian made contact with the rear left of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The pedestrian involved in the collision sustained a fatal injury. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because of a fatality. 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, 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 Dallas, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16196)?
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 Dallas, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16196)?
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 Dallas, TX involving a JAGUAR I-PACE (NHTSA SGO 30270-16196)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.