DEPLOYDatabase

Incident · Collision

ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)

A Zoox vehicle (Vehicle 1) in autonomous mode was traveling in the left lane on southwest-bound [XXX] toward [XXX] in San Francisco when a ball, immediately followed by a dog, entered the roadway from between parked cars on the left side of [XXX] directly into the path of the Zoox vehicle. The Zoox vehicle braked in response, but its underbody made contact with the dog. The Zoox vehicle operator then disengaged autonomous mode and brought the vehicle to a stop. The Zoox vehicle operator then reversed the vehicle to free the dog. The dog owner did not indicate injuries to the dog at the scene. The dog and its owner then returned to the sidewalk and the Zoox vehicle operator drove the vehicle from the scene. The police were not called. Zoox subsequently received an email alleging injuries to the dog, "abrasions behind its left front leg and a possible cracked rib."

Occurred 2025-07-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.

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)?
A Zoox vehicle (Vehicle 1) in autonomous mode was traveling in the left lane on southwest-bound [XXX] toward [XXX] in San Francisco when a ball, immediately followed by a dog, entered the roadway from between parked cars on the left side of [XXX] directly into the path of the Zoox vehicle. The Zoox vehicle braked in response, but its underbody made contact with the dog. The Zoox vehicle operator then disengaged autonomous mode and brought the vehicle to a stop. The Zoox vehicle operator then reversed the vehicle to free the dog. The dog owner did not indicate injuries to the dog at the scene. The dog and its owner then returned to the sidewalk and the Zoox vehicle operator drove the vehicle from the scene. The police were not called. Zoox subsequently received an email alleging injuries to the dog, "abrasions behind its left front leg and a possible cracked rib."
When did this incident occur?
The incident is recorded as occurring on July 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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)?
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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)?
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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514)?
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 San Francisco, CA involving a TOYOTA Highlander (NHTSA SGO 30610-11514).

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 aef60cd7-b52f-4c39-a233-96c1e6b88c5a