_Incident · Collision_

# ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13249)

Canonical ID: `fd274a52-c3a2-42f7-a99d-8b78abfdd92a`

- **Occurred:** 2025-11-01
- **Kind:** `collision`
- **Status (derived):** active
- **Company:** [May Mobility](/companies/may-mobility.md) (id: `8f52c3ed-fb8c-4f25-8c75-c7c9f912776d`)

During normal autonomous operation, the May autonomous shuttle (Ego) was traveling through a narrow section of roadway in a parking lot bordered by parked vehicles on the left and a retaining wall on the right on experimental software version v29.0.20. As the Ego proceeded, the system initially recognized the static retaining wall as a large, non-rectangular object. As the Ego approaches the wall, the resulting density of lidar returns on the object (wall) exceeds the detectors maximum limitation. The newer lidar points, toward the forward edge of the elongated object, exceeding the limit were filtered out, causing the track to disappear when the ego approached 5m from the track (i.e. the wall). The situation was exacerbated by the fact that the road edge was incorrectly marked in that section.  The road edge was drawn through the retaining wall and thus the vehicle did not have any prior knowledge about the edge of the road. As a result, the Ego drove too close to the wall, scraping it at a speed of 2 meters per second while driving straight (i.e. in lane-nominal policy) with no nudge or veer corrections. There was no damage to the wall. The limitation leading to the lost track affects Software versions v26.0 (when the Open World Tracklet v2 feature was introduced) through v31.0. This is the only known instance of this failure mode, and in v32.0 an optimization was made to remove the LIDAR threshold entirely and mitigate the vulnerability.  Furthermore, the incorrect road edge annotation was corrected shortly after this incident and the map updated for the deployed vehicles.

## Sources (1)

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

## Common questions

### What happened in ADS crash report in Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13249)?

During normal autonomous operation, the May autonomous shuttle (Ego) was traveling through a narrow section of roadway in a parking lot bordered by parked vehicles on the left and a retaining wall on the right on experimental software version v29.0.20. As the Ego proceeded, the system initially recognized the static retaining wall as a large, non-rectangular object. As the Ego approaches the wall, the resulting density of lidar returns on the object (wall) exceeds the detectors maximum limitation. The newer lidar points, toward the forward edge of the elongated object, exceeding the limit were filtered out, causing the track to disappear when the ego approached 5m from the track (i.e. the wall). The situation was exacerbated by the fact that the road edge was incorrectly marked in that section.  The road edge was drawn through the retaining wall and thus the vehicle did not have any prior knowledge about the edge of the road. As a result, the Ego drove too close to the wall, scraping it at a speed of 2 meters per second while driving straight (i.e. in lane-nominal policy) with no nudge or veer corrections. There was no damage to the wall. The limitation leading to the lost track affects Software versions v26.0 (when the Open World Tracklet v2 feature was introduced) through v31.0. This is the only known instance of this failure mode, and in v32.0 an optimization was made to remove the LIDAR threshold entirely and mitigate the vulnerability.  Furthermore, the incorrect road edge annotation was corrected shortly after this incident and the map updated for the deployed vehicles.

### When did this incident occur?

The incident is recorded as occurring on November 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 Atlanta, GA involving a TOYOTA Sienna (NHTSA SGO 30413-13249)?

The incident is recorded as involving May Mobility 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 TOYOTA Sienna (NHTSA SGO 30413-13249)?

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 TOYOTA Sienna (NHTSA SGO 30413-13249)?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/fd274a52-c3a2-42f7-a99d-8b78abfdd92a · sources: /v1/incidents/fd274a52-c3a2-42f7-a99d-8b78abfdd92a/sources · responses: /v1/incidents/fd274a52-c3a2-42f7-a99d-8b78abfdd92a/responses · status: /v1/incidents/fd274a52-c3a2-42f7-a99d-8b78abfdd92a/status · canonical URL: /incidents/nhtsa-sgo-30413-13249_