DEPLOYDatabase

Incident · Collision

ADS crash report in San Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655)

On the morning of March [XXX], 2026, at approximately 11:46 a.m., a WeRide autonomous vehicle (Vehicle 1) was traveling along [XXX] in San Jose, California, proceeding straight in the second lane from the left as it approached the intersection with [XXX]. Operating in autonomous mode, the vehicle came to a complete stop at a red traffic signal. While stopped, Vehicle 1 was struck from behind by a white 2012 Chevrolet Colorado pickup truck (Vehicle 2), whose driver failed to stop in time. Immediately following the collision, the In-vehicle safety operator of Vehicle 1 disengaged autonomous mode and assessed the situation. Both drivers then relocated their vehicles to a safe area nearby, where they exchanged information and performed a visual inspection of the damage. The damage to both vehicles was minor in nature. Vehicle 1 sustained a small scratch to its rear bumper, while Vehicle 2 sustained a corresponding minor scratch to its front bumper. No injuries were reported by either party, and emergency services were not requested.

Occurred 2026-03-01 · WeRide

Track ADS crash report in San Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in San Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655)?
On the morning of March [XXX], 2026, at approximately 11:46 a.m., a WeRide autonomous vehicle (Vehicle 1) was traveling along [XXX] in San Jose, California, proceeding straight in the second lane from the left as it approached the intersection with [XXX]. Operating in autonomous mode, the vehicle came to a complete stop at a red traffic signal. While stopped, Vehicle 1 was struck from behind by a white 2012 Chevrolet Colorado pickup truck (Vehicle 2), whose driver failed to stop in time. Immediately following the collision, the In-vehicle safety operator of Vehicle 1 disengaged autonomous mode and assessed the situation. Both drivers then relocated their vehicles to a safe area nearby, where they exchanged information and performed a visual inspection of the damage. The damage to both vehicles was minor in nature. Vehicle 1 sustained a small scratch to its rear bumper, while Vehicle 2 sustained a corresponding minor scratch to its front bumper. No injuries were reported by either party, and emergency services were not requested.
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 San Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655)?
The incident is recorded as involving WeRide 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 Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655)?
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 Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655)?
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 San Jose, CA involving a NISSAN Ariya Hatchback (NHTSA SGO 30792-14655).

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 c45e8a88-a62b-42e0-8fb2-6d6a38e68499