Incident · Collision
ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14847)
On April [XXX], 2026 at 3:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing west on Silver Avenue for a stop sign at the intersection with [XXX]. After traffic had cleared in the intersection, the Waymo AV proceeded straight on [XXX]. As the Waymo AV was approaching the exit of the intersection, a pickup truck traveling southbound on [XXX] and turning right onto [XXX] entered the intersection without stopping at the stop sign on [XXX], and the front of the pickup truck made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV 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-04-01 · Waymo
Machine-readable surfaces
- Markdown mirror: /incidents/nhtsa-sgo-30270-14847.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/8a952148-615e-437f-bf86-4f2143254d4b
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Common questions
- What happened in ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14847)?
- On April [XXX], 2026 at 3:09 PM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving a pickup truck on [XXX] at [XXX]. The Waymo AV was stopped facing west on Silver Avenue for a stop sign at the intersection with [XXX]. After traffic had cleared in the intersection, the Waymo AV proceeded straight on [XXX]. As the Waymo AV was approaching the exit of the intersection, a pickup truck traveling southbound on [XXX] and turning right onto [XXX] entered the intersection without stopping at the stop sign on [XXX], and the front of the pickup truck made contact with the rear right side of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. The Waymo AV 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 April 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 Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14847)?
- 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 San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14847)?
- 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 JAGUAR I-PACE (NHTSA SGO 30270-14847)?
- 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 Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14847).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 8a952148-615e-437f-bf86-4f2143254d4b