Incident · Collision
ADS crash report in Miami, FL involving a JAGUAR I-PACE (NHTSA SGO 30270-14197)
On March [XXX], 2026 at 2:32 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped facing north in the right lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a van traveling northbound on [XXX], partially in the left lane and partially in the Waymo AV's lane of travel, began to maneuver to the left lane as it approached the Waymo AV from behind and and the front right side of the van made contact with the left side of the stationary Waymo AV. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. 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.
Occurred 2026-03-01 · Waymo
Machine-readable surfaces
- Markdown mirror: /incidents/nhtsa-sgo-30270-14197.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/a62a043c-f0e2-4dfb-bb79-c8801463b257
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Common questions
- What happened in ADS crash report in Miami, FL involving a JAGUAR I-PACE (NHTSA SGO 30270-14197)?
- On March [XXX], 2026 at 2:32 AM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Miami, Florida was in a collision involving a van on [XXX] at [XXX]. The Waymo AV was stopped facing north in the right lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV remained stopped, a van traveling northbound on [XXX], partially in the left lane and partially in the Waymo AV's lane of travel, began to maneuver to the left lane as it approached the Waymo AV from behind and and the front right side of the van made contact with the left side of the stationary Waymo AV. At the time of impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode, and a test driver was present in the driver's seating position. 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 March 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 Miami, FL involving a JAGUAR I-PACE (NHTSA SGO 30270-14197)?
- 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 Miami, FL involving a JAGUAR I-PACE (NHTSA SGO 30270-14197)?
- 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 Miami, FL involving a JAGUAR I-PACE (NHTSA SGO 30270-14197)?
- 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 Miami, FL involving a JAGUAR I-PACE (NHTSA SGO 30270-14197).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 a62a043c-f0e2-4dfb-bb79-c8801463b257