DEPLOYDatabase

Incident · Collision

ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-13377)

A Zoox retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continue west on [XXX]. The Zoox vehicle inched forward and then stopped again for cross-traffic. The Zoox vehicle operator then disengaged from autonomous mode and proceeded to begin to cross [XXX]. While crossing, a motorcyclist traveling northbound on [XXX] at a high rate of speed collided with the driver's side front fender and door of the Zoox vehicle. The motorcycle and its operator fell to the ground. After the collision, the Zoox vehicle operator cleared the intersection and pulled over. Both the Zoox vehicle and the motorcycle sustained damage. Police and EMT personnel arrived at the scene, but the motorcycle operator was not transported from the scene.

Occurred 2025-11-01 · Zoox

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.
Track ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-13377)

Machine-readable surfaces

Sources (1)

  1. https://www.nhtsa.gov/laws-regulations/standing-general-order-crash-reporting#report-30610-13377

Common questions

What happened in ADS crash report in Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-13377)?
A Zoox retrofitted test vehicle (Vehicle 1) in autonomous mode was stopped, yielding to cross-traffic, on westbound [XXX] at [XXX] in Miami while waiting for an opportunity to proceed through the intersection and continue west on [XXX]. The Zoox vehicle inched forward and then stopped again for cross-traffic. The Zoox vehicle operator then disengaged from autonomous mode and proceeded to begin to cross [XXX]. While crossing, a motorcyclist traveling northbound on [XXX] at a high rate of speed collided with the driver's side front fender and door of the Zoox vehicle. The motorcycle and its operator fell to the ground. After the collision, the Zoox vehicle operator cleared the intersection and pulled over. Both the Zoox vehicle and the motorcycle sustained damage. Police and EMT personnel arrived at the scene, but the motorcycle operator was not transported from the scene.
When did this incident occur?
The incident is recorded as occurring on November 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 Miami, FL involving a TOYOTA Highlander (NHTSA SGO 30610-13377)?
The incident is recorded as involving Zoox 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 TOYOTA Highlander (NHTSA SGO 30610-13377)?
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 TOYOTA Highlander (NHTSA SGO 30610-13377)?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 1 source (1 primary) · last reviewed 2026-07-14

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-07-14

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 TOYOTA Highlander (NHTSA SGO 30610-13377).

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 d53aa07d-f6fc-4d08-b6fd-b2da77b53e30