DEPLOYDatabase

Incident · Collision

ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484)

On March [XXX], 2026 at 5:21 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped facing northeast in the left lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a heavy truck in the adjacent right lane proceeded forward and towards the left as it entered the intersection to initiate a sharp right turn onto [XXX]. The heavy truck stopped and reversed momentarily multiple times before continuing to turn right. While the heavy truck was turning right, the rear left side of the heavy truck trailer made contact with the front right side of the stationary 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-03-01 · Waymo

Track ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484)

Machine-readable surfaces

Sources (1)

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

Common questions

What happened in ADS crash report in Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484)?
On March [XXX], 2026 at 5:21 PM ET a Waymo Autonomous Vehicle ("Waymo AV") operating in Atlanta, Georgia was in a collision involving a heavy truck on [XXX] near [XXX]. The Waymo AV was stopped facing northeast in the left lane on [XXX] for a red light at the intersection with [XXX]. While the Waymo AV was stopped, a heavy truck in the adjacent right lane proceeded forward and towards the left as it entered the intersection to initiate a sharp right turn onto [XXX]. The heavy truck stopped and reversed momentarily multiple times before continuing to turn right. While the heavy truck was turning right, the rear left side of the heavy truck trailer made contact with the front right side of the stationary 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 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 Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484)?
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 Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484)?
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 Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484)?
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 Atlanta, GA involving a JAGUAR I-PACE (NHTSA SGO 30270-14484).

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 2e899ee2-34f8-414a-8be5-d4c11608a18c