Incident · Collision
ADS crash report in San Francisco, CA involving a JAGUAR I-PACE (NHTSA SGO 30270-14627)
On April [XXX], 2026 at 8:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northeastbound on [XXX] when an SUV traveling southwestbound on [XXX] crossed the solid double yellow lane lines and entered the Waymo AV's lane of travel. The Waymo AV braked and maneuvered to the right to yield to the SUV as the SUV continued forward, and the front of the SUV made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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-14627.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/a0100559-1ad3-4b7d-bc7c-25f81894af7d
- 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-14627)?
- On April [XXX], 2026 at 8:58 AM PT a Waymo Autonomous Vehicle ("Waymo AV") operating in San Francisco, California was in a collision involving an SUV on [XXX] near [XXX]. The Waymo AV was traveling northeastbound on [XXX] when an SUV traveling southwestbound on [XXX] crossed the solid double yellow lane lines and entered the Waymo AV's lane of travel. The Waymo AV braked and maneuvered to the right to yield to the SUV as the SUV continued forward, and the front of the SUV made contact with the front of the Waymo AV. At the time of the impact, the Waymo AV's Level 4 ADS was engaged in autonomous mode. Both vehicles sustained damage. The driver of the SUV was transported to a hospital by an ambulance with unknown injuries. Waymo is reporting this crash under Request No. 1 of Standing General Order 2021-01 because an individual involved was transported from the scene to a hospital for medical treatment. 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-14627)?
- 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-14627)?
- 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-14627)?
- 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-14627).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 a0100559-1ad3-4b7d-bc7c-25f81894af7d