The SGO file, in a form you can search
NHTSA publishes the crash reports as three CSV files of 116 columns each, with several versions of the same report mixed in. This is the same data as one table: driverless systems (ADS) and Level 2 driver assistance side by side, 2021 to today including NHTSA's archive, one row per report at its latest version, every row traceable to its NHTSA report number. Free, CC BY 4.0, refreshed from NHTSA on every pipeline run.
- Reports
- 8612
- Fatal
- 87
- Of them Level 2
- 79
- Reporting entities
- 64
- Incidents
- 2019-08 to 2026-09
48 reports, showing 1 to 48.
| Report ID | Case | Program | Entity | Incident | Place | Vehicle | Engaged | Crash with | Severity | Speed, mph | Roadway | Narrative |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 30413-16664 | ADS | May Mobility | 2026-08 14:17 | Arlington, TX | 2024 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 0 | Intersection | On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn i…On August [XXX], 2026, at 2:17 p.m. CT, a May Mobility autonomous vehicle (AV) operating northbound in autonomous mode stopped at a stop sign on [XXX] in Arlington, Texas. The May Mobility AV began to make a right turn into the curb lane of eastbound [XXX], but stopped mid-turn to yield to a crossing vehicle. A passenger vehicle trailing the May Mobility AV advanced into the crosswalk at three mph, making contact with the May Mobility AV's rear left corner, causing moderate damage to the May Mobility AVâs rear left-side bumper and quarter panel, and damaging the passenger vehicleâs front right tire. No injuries were reported, no towing was needed, and no airbags were deployed. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-16665 | ADS | May Mobility | 2026-08 15:05 | Atlanta, GA | 2023 TOYOTA Sienna | Verified Engaged | Passenger Car | Minor W/O Hospitalization | 0 | Intersection | On August [XXX], 2026, at 3:05 p.m. ET, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling south on[XXX] in Midtown Atlanta, Georgia, approaching the intersection of [XXX]. A box truck …On August [XXX], 2026, at 3:05 p.m. ET, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling south on[XXX] in Midtown Atlanta, Georgia, approaching the intersection of [XXX]. A box truck was stopped in the adjacent right lane, positioned to turn right at a green traffic signal. The May Mobility AV slowed and came to a stop short of the crosswalk. The front end of a passenger vehicle, following the May Mobility AV, made contact with the rear left section of the May Mobility AV. Impact caused moderate damage to the May Mobility AV's left rear bumper, lift gate, side panel, and tail light; the passenger vehicle experienced moderate damage to its front-right bumper, quarter panel, and headlight. The May Mobility AV operator reported a minor injury. No medical services were called. No vehicles were towed and no airbags were deployed. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-16218 | ADS | May Mobility | 2026-07 14:33 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Van | No Injured Reported | 0 | Street | On July [XXX], 2026, at 2:33 p.m. ET, the May Mobility autonomous vehicle (AV) was facing west on [XXX] at a red light, preparing for a right turn onto northbound [XXX] in Atlanta, GA. The Autonomous Vehicle Operator (AV…On July [XXX], 2026, at 2:33 p.m. ET, the May Mobility autonomous vehicle (AV) was facing west on [XXX] at a red light, preparing for a right turn onto northbound [XXX] in Atlanta, GA. The Autonomous Vehicle Operator (AVO) disengaged autonomy during the right turn and assumed manual operation of the AV. Twenty-eight seconds after the disengagement, the manually operated AV, which had queued behind a van at a red light, rolled forward at 0.45 mph. The front of the May Mobility AV made contact with the rear of the van. No damage was evident to the AV or the van. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-16238 | ADS | May Mobility | 2026-07 13:04 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 0 | Street | On July [XXX], 2026, at 1:04 p.m. CT, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling west on [XXX] in Arlington, Texas, when it came to a complete stop for a moving mail delivery va…On July [XXX], 2026, at 1:04 p.m. CT, the May Mobility autonomous vehicle (AV), operating in autonomous mode, was traveling west on [XXX] in Arlington, Texas, when it came to a complete stop for a moving mail delivery van attempting to pull away from the curb. The AV remained stationary, in the lane, and in autonomous operation, as an SUV approached traveling east on [XXX]. As the SUV passed on the passenger side, the right side of the SUV made contact with the stationary AV's right-side mirror and right-side sensor pod, causing minor damage to the sensor pod and minor scuff marks to the mirror. The SUV continued traveling east without stopping. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-15463 | ADS | May Mobility | 2026-05 16:11 | Arlington, TX | 2024 TOYOTA Sienna | Verified Engaged | Other, see Narrative | No Injured Reported | 33 | Street | On May [XXX], 2026 at 4:11 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX] The May Mobility AV was traveling Eastbound on [XXX…On May [XXX], 2026 at 4:11 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX] The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel made contact with the front right A-pillar near the windshield of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 33 MPH. The impact left scuffs on the May Mobility AV that were buffed out, not requiring repair. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-15464 | ADS | May Mobility | 2026-05 16:38 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | Other, see Narrative | No Injured Reported | 32 | Street | On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XX…On May [XXX], 2026 at 4:38 pm CT, a low-hanging utility cable made contact with a May Mobility Autonomous Vehicle (AV) operating in Arlington, Texas on [XXX] near [XXX]. The May Mobility AV was traveling Eastbound on [XXX]. As the May Mobility AV passes [XXX] a loop of an unsecured, low-hanging utility cable that was dangling above the right lane of travel struck the windshield and roof of the May Mobility AV. At the time of impact, the May Mobility AV was in autonomous mode, traveling at 32 MPH. The May Mobility AV sustained damage on the top, front, and right side of the vehicle that is estimated to be more than $1,000. Damage to the utility cable beyond the original state of disrepair is unknown. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-14938 | ADS | May Mobility | 2026-04 13:59 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Other, see Narrative | Minor W/ Hospitalization | 21 | Intersection | On April [XXX], 2026, at 1:59 pm EST, a third-party vehicle, John Deere UTV Crossover Gator Utility Vehicle, collided with a May Mobility Autonomous Vehicle (AV) in Atlanta, Georgia, at the intersection of [XXX] and [XXX…On April [XXX], 2026, at 1:59 pm EST, a third-party vehicle, John Deere UTV Crossover Gator Utility Vehicle, collided with a May Mobility Autonomous Vehicle (AV) in Atlanta, Georgia, at the intersection of [XXX] and [XXX]. The May Mobility AV was traveling south on [XXX] in Atlanta, Georgia approaching the intersection of [XXX] on a green traffic light, with its automated driving system engaged in autonomous mode. The third- party vehicle was traveling west on [XXX] approaching a red light at [XXX] when it ran the red light and proceeded into the intersection without slowing, making contact with the May Mobility AV. The May Mobility AV began to apply the brakes as the third- party vehicle started to run the red light. During the May Mobility AVâs braking, the telematics confirm that the Autonomous Vehicle Operator also started to intervene, moving the steering wheel to the right and braking more forcefully. The collision was unavoidable with the third-party vehicle making contact with the front left bumper and the driver side rear passenger door of the May Mobility AV. The May Mobility AV was towed from the scene. May Mobility is reporting this crash under Request No. 1 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it becomes available. | |
| 30413-15019 | ADS | May Mobility | 2026-04 18:28 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 0 | Street | On April [XXX], 2026, at 6:28 PM ET, a passenger car collided with a May Mobility Autonomous Vehicle (AV) operating in Atlanta, Georgia on [XXX] near [XXX]. The May Mobility AV was traveling east on [XXX] in the left lan…On April [XXX], 2026, at 6:28 PM ET, a passenger car collided with a May Mobility Autonomous Vehicle (AV) operating in Atlanta, Georgia on [XXX] near [XXX]. The May Mobility AV was traveling east on [XXX] in the left lane. A passenger car traveling east on [XXX] in the right lane proceeded to change lanes from the right lane to the left lane. The May Mobility AV Operator began braking before a pedestrian crosswalk, which had an activated Rectangular Rapid Flashing Beacon and the presence of a pedestrian waiting to cross. After changing lanes, the passenger car failed to brake and the front of the passenger car made contact with the rear of the May Mobility AV. At the time of impact, the May Mobility AV was in manual mode. The May Mobility AV sustained a significant puncture in the rear, lower bumper with scratches, the passenger car sustained scratches on the front bumper. May Mobility is reporting this crash under Request No. 2 of Standing General Order 2021-01. May Mobility may supplement or correct its reporting with additional information as it may become available. | |
| 30413-14624 | ADS | May Mobility | 2026-03 10:18 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 6 | Intersection | On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making…On March [XXX], 2026, at 10:18 am, a third-party vehicle collided with a May Mobility Autonomous Vehicle (Ego) in Arlington, Texas, at the intersection of [XXX] and [XXX]. The May Ego was traveling north on [XXX], making a right turn at a yield sign onto eastbound [XXX]. with its automated driving system engaged in autonomy mode. The May Ego stopped at the yield sign then held its position in order to confirm its prediction that an oncoming vehicle was not making a left turn across the ego's path. The third-party vehicle, traveling north on [XXX] behind the Ego, failed to stop at the yield sign and rear-ended the Ego. Vehicle telematics confirm the Autonomous Vehicle Operator intervened using the accelerator to avoid the collision; however, the collision was unavoidable. | |
| 30413-13853 | ADS | May Mobility | 2026-01 07:48 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Other Fixed Object | Minor W/ Hospitalization | 29 | Street | On January [XXX], 2026 at 7:48 AM, a May Mobility Autonomous Vehicle (AV) was in a collision with a fire hydrant in Atlanta, Georgia on [XXX]near[XXX]. The May Mobility AV was traveling westbound on [XXX]in Atlanta, Geor…On January [XXX], 2026 at 7:48 AM, a May Mobility Autonomous Vehicle (AV) was in a collision with a fire hydrant in Atlanta, Georgia on [XXX]near[XXX]. The May Mobility AV was traveling westbound on [XXX]in Atlanta, Georgia with its automated driving system engaged in autonomy mode when the Autonomous Vehicle Operator (AVO) fell asleep while his right hand rested on the right side of the steering wheel. In-cabin video and telematics confirms that the AVO's hand restricted the motion of the steering wheel, preventing the autonomous system from keeping the vehicle in its lane. Though the AV braked after perceiving the exit from its travel lane, collision with the fire hydrant could not be avoided. The air bags deployed during the collision and the AV was towed from the scene. The AVO was transported by ambulance to the hospital with minor injuries. | |
| 30413-13468 | ADS | May Mobility | 2025-12 11:29 | Arlington, TX | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 2 | Intersection | The May Mobility vehicle (Ego) is stopped at a red light, then the Ego begins to accelerate and turn right when the traffic light changes to green. As the Ego accelerates, a pedestrian begins moving and enters the crossw…The May Mobility vehicle (Ego) is stopped at a red light, then the Ego begins to accelerate and turn right when the traffic light changes to green. As the Ego accelerates, a pedestrian begins moving and enters the crosswalk from the other side of the intersection. This activates the rule-based crosswalk logic. Ego determines that it is able to stop before the crosswalk without exceeding our max deceleration threshold, which triggers an in-policy stopping reaction for the crosswalk. The Ego brakes to yield for the pedestrian. The vehicle trailing the Ego accelerates, making contact with the rear-end of the Ego. In the 2.5 seconds between the start of the Ego braking and the collision, the rear vehicle accelerated from 0.2 to 6.1 m/s (0.4 to 13.6 mph) without slowing until after the collision occurred. In response to this incident, immediate mitigations were made, in that the vehicle operators (AVOs) operate all intersections in manual mode. This remained in place until January 12, when we received a solution which instituted a reduction of the 3.5 m/s2 parameter, in order to prevent the Ego from yielding to pedestrians in crosswalks that are still far from the Egoâs lane if such yielding would induce braking. | |
| 30413-13469 | ADS | May Mobility | 2025-12 19:37 | Arlington, TX | 2023 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 4 | Intersection | The May Mobility vehicle (Ego) approaches a turn with a trailing vehicle following closely behind. The May planner initially selects a trajectory it believes will safely complete the turn. However, as the Ego begins the …The May Mobility vehicle (Ego) approaches a turn with a trailing vehicle following closely behind. The May planner initially selects a trajectory it believes will safely complete the turn. However, as the Ego begins the turn, it re-evaluates the situation and detects a significant risk of striking the curb. At that point, the planner shifts focus from avoiding the curb entirely to minimizing the severity of a potential curb strike. To reduce speed before the expected contact, the Ego brakes at €"3.5 m/s²). Because the trailing vehicle is following so closely, this deceleration makes a rear-end collision likely. The Ego predicts a potential rear-end collision and elects to reduce brake force to lessen the impact severity. Moments later, the trailing vehicle strikes the rear driver-side bumper of the Ego and then drives away. Future improvements are underway to give the planner a policy option to steer away from curbs. This new capability will help the vehicle avoid situations where braking becomes the only remaining way to manage close curb proximity. | |
| 30413-13470 | ADS | May Mobility | 2025-12 11:01 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | SUV | No Injured Reported | 5 | Street | The May Mobility vehicle (Ego) was operating in autonomy while waiting in slow traffic in the leftmost of two parallel lanes. Ahead, both lanes were obstructed by stopped vehicles, prompting traffic to move to the center…The May Mobility vehicle (Ego) was operating in autonomy while waiting in slow traffic in the leftmost of two parallel lanes. Ahead, both lanes were obstructed by stopped vehicles, prompting traffic to move to the center turn lane to proceed. The Autonomous Vehicle Operator (AVO) intervened to move closer to the lead vehicle as another vehicle in the right lane attempted to merge left, preventing it. After the merging car stopped, the AVO pulled closer to the lead vehicle, removing any space to merge. As the lead vehicle began to move, both the AVO and the vehicle to the right immediately accelerated, while the merging vehicle moved left into the side of the May AV. Had the Ego remained in Autonomous mode, it would have maintained a safe distance allowing the merging vehicle to proceed safely. No software defects led to this event. This behavior goes against the training of May AVOs. Upon review of this AVOâs actions it was decided to remove this person from their role as an AVO. | |
| 30413-13083 | ADS | May Mobility | 2025-11 11:40 | Grand Rapids, MN | 2023 TOYOTA Sienna | Verified Engaged | Other Fixed Object | No Injured Reported | 25 | Street | A May autonomous shuttle (Ego) is approaching a passenger stop location in autonomy. The vehicle operator (AVO) presses on the accelerator, taking control of the Ego, then accelerates into the curb at the stop. The Ego m…A May autonomous shuttle (Ego) is approaching a passenger stop location in autonomy. The vehicle operator (AVO) presses on the accelerator, taking control of the Ego, then accelerates into the curb at the stop. The Ego made contact with the curb 3 seconds after switching into manual, causing severe damage to the front-right tire. Resimulation of this event shows that there were no autonomy errors that led to this event, and had the Ego stayed in autonomy, this event would not have happened. This AVO had just completed our training course with only a few hours of service time before this incident. Upon further review of the AVO performance, on their own, it was decided to remove her from the AVO role. | |
| 30413-13248 | ADS | May Mobility | 2025-11 15:06 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 1 | Intersection | The May autonomous shuttle (Ego) stopped in Autonomous mode safely behind a lead vehicle at a traffic light, which then, the lead vehicle, reversed into the stationary Ego. The Autonomous vehicle operator took over contr…The May autonomous shuttle (Ego) stopped in Autonomous mode safely behind a lead vehicle at a traffic light, which then, the lead vehicle, reversed into the stationary Ego. The Autonomous vehicle operator took over control of the vehicle and attempted to reverse, but was unable to get out of the way of the reversing vehicle. The planner did roll out the agent with a reversing policy and predicted the collision, but the system currently is not able to honk or reverse or do anything else that could have avoided this. The primary factor was fault by the lead vehicle. There was no fault in our software that led to this event. | |
| 30413-13249 | ADS | May Mobility | 2025-11 11:38 | Atlanta, GA | 2023 TOYOTA Sienna | Verified Engaged | Other Fixed Object | No Injured Reported | 5 | Parking Lot | 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 experim…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. | |
| 30413-11593 v2 | ADS | May Mobility | 2025-08 11:35 | Peachtree Corners, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | Minor W/O Hospitalization | 13 | Intersection | The May vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May…The May vehicle was travelling in an autonomous vehicle (AV) only lane approaching an intersection. A vehicle travelling to the left of the May shuttle (ego) in the non-AV lane performed a right hand turn across the May vehicle's path. Given the full stopping power and the limited space with which the ego had to stop, the ego was physically unable to stop in time before impact. The primary factor that led to this collision was human error on the part of the other vehicle that was required to yield to through traffic in the AV lane but did not. Right turns across a straight lane are uncommon, and drivers are typically not used to them, however there are several signs that instruct other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Update: There was no indication of injury or request for medical attention at the scene. The police report states "Driver 1 complained of neck pain." For this reason, we are updating the highest severity injury alleged field to reflect the "minor w/o hospitalization" injury level. The remaining content of this report is unchanged from the initial report submitted on September [XXX], 2025, Report ID #[XXX]. | |
| 30413-11669 | ADS | May Mobility | 2025-08 18:08 | Eden Prairie, MN | 2023 TOYOTA Sienna | Verified Engaged | Pickup Truck | No Injured Reported | 13 | Intersection | A May autonomous shuttle (Ego) is passing through an intersection. A vehicle sensor detects a false positive as a pedestrian moving toward the May vehicles path in a region closely behind another vehicle. This causes…A May autonomous shuttle (Ego) is passing through an intersection. A vehicle sensor detects a false positive as a pedestrian moving toward the May vehicles path in a region closely behind another vehicle. This causes the May vehicle to stop to allow it to safely pass. A following agent (still accelerating at the time of the impact) collides with the May vehicle one second after we come to a stop. Re-simulation on newer software shows that routine software improvements resolved this issue and the commercial May software has been updated to this release. | |
| 30413-11487 | ADS | May Mobility | 2025-07 14:30 | Peachtree Corners, GA | 2024 TOYOTA Sienna | Verified Engaged | Passenger Car | No Injured Reported | 20 | Intersection | The May autonomous vehicle was travelling in an autonomous vehicle (AV) only lane, on [XXX], approaching the intersection at [XXX] A vehicle travelling to the left of the May shuttle in the non-AV lane attempted to perf…The May autonomous vehicle was travelling in an autonomous vehicle (AV) only lane, on [XXX], approaching the intersection at [XXX] A vehicle travelling to the left of the May shuttle in the non-AV lane attempted to perform a right hand turn across the May vehicles path and collided with the May AV. The primary factor that led to this collision was human error on the part of the other vehicle that was required to yield to through traffic in the AV lane but did not. Right turns across a straight lane are uncommon, and drivers are typically not used to them, however there is a metal street sign that instructs other traffic to yield to the vehicles in the AV lane. There were no autonomy faults or errors which led to this incident. Additionally, there is a second traffic light at this intersection that warns public drivers to yield to the AV shuttle. This light was not operating as it should during this incident. We are working with our partner to maintain the operation of this light and have implemented a mitigation policy of daily inspections of this light and implementing an AVO in service if this light is not functioning. | |
| 30413-11489 | ADS | May Mobility | 2025-07 09:02 | Atlanta, GA | 2024 TOYOTA Sienna | Verified Engaged | Other Fixed Object | No Injured Reported | 18 | Street | While traveling north on [XXX], the Autonomous Vehicle Operator (AVO) engages autonomy 3.0 m before the planned right turn and 7.7 m before the break in the curb while traveling at 8.0 m/s. The May Autonomous Vehicle (e…While traveling north on [XXX], the Autonomous Vehicle Operator (AVO) engages autonomy 3.0 m before the planned right turn and 7.7 m before the break in the curb while traveling at 8.0 m/s. The May Autonomous Vehicle (ego) was planning to make a tight right turn into a parking lot, which the AVO was unaware of when engaging autonomy. The ego jerked to the right upon entering autonomy, hitting a curb and damaging both passenger-side front and rear tires and the right rear tire rim. The AV attempted the right turn despite not having time to slow sufficiently and mounted the curb. The AVO intervened by accelerating and steering back to the left upon striking the curb, manually maneuvering back to the street while striking a second curb on the opposite side of the parking lot driveway. Resimulations without the manual intervention show the ego slowing appropriately and making the right turn into the parking lot. The AVO should have been attentive to the planned route before engaging autonomy. As a result of this incident, planned improvements to the AVOs instructive dash and audio alerts for upcoming turns have begun to be implemented. | |
| 30413-10762 | ADS | May Mobility | 2025-04 11:28 | Detroit, MI | 2023 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 1 | Intersection | A large semi-trailer truck is making a left turn from a street on the right into the oncoming lane in Detroit, MI. As the May autonomous shuttle (Ego) is slowing, the Autonomous Vehicle Operator (AVO) intervenes to stop…A large semi-trailer truck is making a left turn from a street on the right into the oncoming lane in Detroit, MI. As the May autonomous shuttle (Ego) is slowing, the Autonomous Vehicle Operator (AVO) intervenes to stop earlier. The manually controlled Ego remains stationary for five seconds. The AVO then manually reverses two meters to create more space for the trailer intruding into the Egos lane, making contact with a rear vehicle at 0.6 m/s. Our team looked at the incident and determined that this event was caused by human error - no autonomy software defects led to this incident. | |
| 30413-10763 | ADS | May Mobility | 2025-04 8:55 | Atlanta, GA | 2024 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 13 | Street | Manual control was initiated by a May autonomous shuttle operator for a right turn onto [XXX] in Atlanta, GA. Autonomous mode was then engaged. The autonomous system executed a stop due to a narrow passage obstructed b…Manual control was initiated by a May autonomous shuttle operator for a right turn onto [XXX] in Atlanta, GA. Autonomous mode was then engaged. The autonomous system executed a stop due to a narrow passage obstructed by parked vehicles on both sides of the roadway and an approaching vehicle. Following the departure of the first vehicle and the next oncoming vehicle 80m away, the Autonomous Vehicle Operator (AVO) disengages and proceeds in manual. The AVO overcorrects to the right slightly and a minor contact with the parked car's mirror occurs. Our team looked at the incident and determined that this event was caused by human error - no autonomy software defects led to this incident. | |
| 30413-10764 | ADS | May Mobility | 2025-04 8:33 | Ann Arbor, MI | 2024 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Intersection | A May autonomous shuttle (ego) was stopped at a traffic light in autonomous mode. A vehicle approaching from behind coasted into the ego vehicle. Our system responded with a software Health Drop, which immediately took t…A May autonomous shuttle (ego) was stopped at a traffic light in autonomous mode. A vehicle approaching from behind coasted into the ego vehicle. Our system responded with a software Health Drop, which immediately took the ego out of autonomous mode (for safety). Minor damage was reported to our rear sensor and bumper. | |
| 30413-9723 v2 | ADS | May Mobility | 2025-01 17:04 | Martinez, CA | 2023 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 20 | Street | While traveling northbound on[XXX] in Martinez, a car pulled out of a driveway on the right side without right of way and collided with the right side of May's vehicle (t-bone.) May's vehicle was traveling at approximate…While traveling northbound on[XXX] in Martinez, a car pulled out of a driveway on the right side without right of way and collided with the right side of May's vehicle (t-bone.) May's vehicle was traveling at approximately 20 MPH in a residential neighborhood, and was approximately 1m left of lane center when a black vehicle exited a driveway on the right from behind a fence, facing the road and May's vehicle. This vehicle did not slow down or stop until entering into the roadway and collided with the May vehicle's right side. AVO attempts to swerve to the left but is unable to avoid a collision. The primary factor that led to the collision was the other vehicles action proceeding without the right-of-way into the side of the May vehicle. Upon further inspection, it was determined that we did not predict this collision until it was too late to avoid it even by veering. The velocity of the other vehicle was underestimated and was largely given only yield policies as having the most significant likelihood. There is some room for improvement in our response, which we plan to implement in future software releases, namely, an emergency veer policy must exist that is capable of moving quickly and far enough to possibly avoid the collision, more accurate reporting of velocity for slow-moving agents, estimate acceleration when assessing risk, improvements to predictions of the probability of an agent yielding, and adjusting our risk assessment so that it is heading dependent and more risk would be associated with passing close in front of another vehicle. | |
| 30413-9949 | ADS | May Mobility | 2025-01 12:34 | Ann Arbor, MI | 2024 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Street | The May vehicle was involved in a rear-end collision shortly after completing a right-hand turn. As the vehicle proceeded through its turn, it encountered exhaust fumes from vehicles waiting at a stoplight in the adjacen…The May vehicle was involved in a rear-end collision shortly after completing a right-hand turn. As the vehicle proceeded through its turn, it encountered exhaust fumes from vehicles waiting at a stoplight in the adjacent lane. Due to environmental conditions and sensor limitations, the vehicle's lidar system interpreted the exhaust plume as a solid object in its path. In response, the autonomous vehicle first tried to adjust its position. When this maneuver proved insufficient, the system initiated a hard stop response. The vehicle behind, which was following at approximately 7-8 meters, was unable to stop in time and collided with the rear of the autonomous vehicle. The collision occurred at relatively low speeds (the autonomous vehicle had decelerated from approximately 7.6 m/s to 0 m/s), though exact impact speeds of the following vehicle were not recorded. The primary factor that led to this incident is that Lidar does not pierce through exhaust so the exhaust cloud appears to be a large, solid object. Some corrective actions that will be implemented: consider weather implication in future platform sensor selection and continue working on the software to improve a neural network to classify lidar points, which will use temporal information, radar, and camera features to make a decision on whether a lidar point is truly an object. | |
| 30413-9958 | ADS | May Mobility | 2025-01 09:28 | Peachtree Corners, GA | 2024 Toyota Sienna | ADS | Other Fixed Object | No Injuries Reported | 7 | Parking Lot | A May shuttle began a test shift on experimental software in a parking sub-lot. The vehicle exited the sub-lot and rolled over a curb. The vehicle stopped at a stop sign at the exit of the main lot. As it proceeded to tu…A May shuttle began a test shift on experimental software in a parking sub-lot. The vehicle exited the sub-lot and rolled over a curb. The vehicle stopped at a stop sign at the exit of the main lot. As it proceeded to turn onto the main road, it rolled over another curb. Almost immediately after rolling the curb, the vehicle began to drift right in lane, rubbing the vehicle sidewall on a curb. The test driver intervened immediately, but not before the sidewall of the rear right tire was weakened. Later during the drive while under manual control, the sidewall fails, eventually leading to a low pressure indicator illuminating in the dash. It was discovered that the deployment of map files, which must remain compatible, was incomplete, leaving a mismatch in the system. This resulted in the vehicle having an incorrect estimate of where lanes are in the coordinates of our localization map, and as a result, the vehicle had an incorrect estimate of proximity to lane boundaries, resulting in curb strikes. | |
| 30413-9109 | ADS | May Mobility | 2024-10 13:07 | Arlington, TX | 2022 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Street | The May Mobility vehicle was at a designated pick up location waiting for a passenger to get on board. Because of an unprotected turn required to get to the stop, the autonomous vehicle operator took over manually. As th…The May Mobility vehicle was at a designated pick up location waiting for a passenger to get on board. Because of an unprotected turn required to get to the stop, the autonomous vehicle operator took over manually. As the vehicle waited parked at the stop, a car in a parking space in front of the stop backed up into the May vehicle at 2mph. This impact occurs 25 seconds after last being in autonomous mode. | |
| 30413-8861 | ADS | May Mobility | 2024-09 09:06 | Peachtree Corners, GA | 2022 Toyota Sienna | ADS | Other Fixed Object | No Injuries Reported | 30 | Street | A May autonomous vehicle was traveling in the right lane of a two-lane road, maintaining a steady speed of 30 mph, in compliance with the posted speed limit. The road was characterized by light traffic, with a slight cur…A May autonomous vehicle was traveling in the right lane of a two-lane road, maintaining a steady speed of 30 mph, in compliance with the posted speed limit. The road was characterized by light traffic, with a slight curvature that transitioned from a gentle rightward sway to a leftward sway. As the vehicle navigated this transition of curvature, the May vehicle made contact with the curb, causing a flat tire. At the time of the incident, no other vehicles or pedestrians were present in the immediate vicinity, and there were no external factors such as obstructions or adverse weather conditions influencing the vehicles path. Speed was reduced from 30mph to 25mph after this event and tested (and worked to mitigate the problem in that area) and now will be reduced to 22 which is the sweet spot for most areas on the route. The May vehicle chose to maneuver at the curb due to perceived risk from a car in an adjacent lane, so May is increasing the allowed distance to the curb to mitigate how close the vehicles are allowed to get. | |
| 30413-8218 | ADS | May Mobility | 2024-07 13:57 | Miami, FL | 2022 Toyota Sienna | ADS | Non-Motorist: Cyclist | No Injuries Reported | 0 | Street | May vehicle was parked in autonomous mode at a rider stop when a VRU on a bicycle approached from the north, coming towards the vehicle. Bicycle was on the wrong side of the road and appeared to be weaving. There were no…May vehicle was parked in autonomous mode at a rider stop when a VRU on a bicycle approached from the north, coming towards the vehicle. Bicycle was on the wrong side of the road and appeared to be weaving. There were no other vehicles nearby and the bicycle had significant room to avoid the May vehicle. However, the bicyclist came into contact with the driver side of the May vehicle, resulting in some minor damage to the May vehicle. After contact, the bicyclist appeared uninjured, got up and left the scene on the bicycle. | |
| 30413-8305 | ADS | May Mobility | 2024-07 08:40 | Miami, FL | 2022 Toyota Siennaa | ADS | Van | No Injuries Reported | 0 | Street | May vehicle was waiting at the red light of [XXX] and [XXX]. The May vehicle was stopped and was 2nd behind the stop line. The van behind the May vehicle was also stopped. Van driver removed their foot from the brake ped…May vehicle was waiting at the red light of [XXX] and [XXX]. The May vehicle was stopped and was 2nd behind the stop line. The van behind the May vehicle was also stopped. Van driver removed their foot from the brake pedal, idling into the May vehicle at a low rate of speed. | |
| 30413-8306 | ADS | May Mobility | 2024-07 12:57 | Miami, FL | 2022 Toyota Sienna | ADS | SUV | No Injuries Reported | 15 | Street | The May vehicle is approaching a lane change. It signals the lane change appropriately early and begins to gradually decelerate for the change. The trailing SUV continues to accelerate while the May vehicle is simultaneo…The May vehicle is approaching a lane change. It signals the lane change appropriately early and begins to gradually decelerate for the change. The trailing SUV continues to accelerate while the May vehicle is simultaneously decelerating, and eventually changes lanes directly into the May vehicle. Trailing SUV drives away without slowing meaningfully, disappearing around an upcoming turn. May vehicle deceleration never exceeds -1.3m/s2, so there is no plausible reason a responsible driver would not have had adequate time to adjust their speed or path to avoid a collision. | |
| 30413-7880 | ADS | May Mobility | 2024-05 17:05 | Miami, FL | 2022 Toyota Sienna | ADS | Motorcycle | No Injuries Reported | 0 | Street | While in traffic and stopped at 0mph in autonomy, a motorized scooter riding between the 2 lanes of traffic clipped the May Mobility vehicle's mirror with their own mirror. The scooter proceeded along its way, seemingly …While in traffic and stopped at 0mph in autonomy, a motorized scooter riding between the 2 lanes of traffic clipped the May Mobility vehicle's mirror with their own mirror. The scooter proceeded along its way, seemingly unaware of the mirror clip. | |
| 30413-7704 | ADS | May Mobility | 2024-04 11:35 | Miami, FL | 2022 Toyota Sienna | ADS | Van | No Injuries Reported | 5 | Intersection | The May vehicle was traveling through an intersection with a van in the oncoming left turn lane. As the May vehicle enters the intersection, the van creeps towards its turn. Predicting that the two will get too close, t…The May vehicle was traveling through an intersection with a van in the oncoming left turn lane. As the May vehicle enters the intersection, the van creeps towards its turn. Predicting that the two will get too close, the May vehicle elects to stop hard. As vehicle is coming to a stop in the stop-hard policy, the turning van fails to respond in time and collides with the rear left corner of the vehicle. In the new software, deploying within the next month, agent-proximity has been replaced with agent-clearance. Performing resimulations of the incident with the latest branch verifies that this issue does not persist. | |
| 30413-7307 | ADS | May Mobility | 2024-02 11:40 | Ann Arbor, MI | 2022 Toyota Sienna | ADS | SUV | No Injuries Reported | 29 | Street | The May vehicle was in autonomous mode on experimental test software (not deployed to the Commercial fleet), in light snow conditions. A vehicle behind the AV was traveling approximately the same speed as the May shuttl…The May vehicle was in autonomous mode on experimental test software (not deployed to the Commercial fleet), in light snow conditions. A vehicle behind the AV was traveling approximately the same speed as the May shuttle. The May AV began to slow for an object ahead. Due to weather conditions, the AV misclassified a speed limit sign as a pedestrian, which intersected with the predicted trajectory of the AV. This caused the May AV to apply additional braking to avoid the projected collision with the misclassified object. The following vehicle did not react promptly when the May AV started to slow down, resulting in the following vehicle braking too late to avoid collision and impacting the May AV from behind. The following vehicle then pulled around the May vehicle and drove away. Resimulation of this event with an upcoming software version shows that the May AV would not misidentify the non-exist object so would not have decelerated unnecessarily. This improved software is set to be deployed to the full commercial fleet soon. In addition, per May policy, the commercial fleet would not operate in weather conditions like those present in this incident. | |
| 30413-6684 | ADS | May Mobility | 2023-10 10:03 | Grand Rapids, MN | 2021 Toyota Sienna | ADS | Other Fixed Object | No Injuries Reported | 27 | Street | The May vehicle was traveling eastbound on [XXX] in autonomy. The vehicles internal facing cameras show that the operator started to fall asleep while applying physical input to the steering wheel. The road started to be…The May vehicle was traveling eastbound on [XXX] in autonomy. The vehicles internal facing cameras show that the operator started to fall asleep while applying physical input to the steering wheel. The road started to bend to the left. The physical input from the operator was enough to deviate the vehicle from its intended path but not enough to trigger an intervention and take the vehicle out of autonomy. The vehicle, going straight as the road curved, then struck the curb, resulting in minor vehicle damage. Due to the vehicle being off path, the vehicle begins to stop. This occurs as the operator wakes up. The operator was not injured and no third parties were impacted or otherwise affected by the incident. The local May Mobility site staff did not notice any signs of fatigue from this operator prior to going out in the vehicle. The operator had responded to audio check-ins from site staff at a regular interval. We are exploring additional risk mitigation options for in-cabin health monitoring, in addition to the existing cameras and radio check-ins. | |
| 30413-6257 | ADS | May Mobility | 2023-08 10:10 | Arlington, TX | 2021 Toyota Sienna | Unknown, see Narrative | Passenger Car | No Injuries Reported | 18 | Street | The vehicle operator took the vehicle out of autonomy while driving NB on [XXX]. In manual the operator clipped the May vehicle's right sensor with the trunk of a diagonally parked car. The operator did not report the in…The vehicle operator took the vehicle out of autonomy while driving NB on [XXX]. In manual the operator clipped the May vehicle's right sensor with the trunk of a diagonally parked car. The operator did not report the incident, however based on video footage they were aware of physical damage to the May vehicle. Local staff noticed a vehicle health error regarding that sensor and called the operator back to base, where they saw the damage. The operator was sent home immediately and terminated upon video review due to not following proper procedure. | |
| 30413-6032 | ADS | May Mobility | 2023-07 17:25 | Grand Rapids, MN | 2021 Toyota Sienna | ADS | Pickup Truck | No Injuries Reported | 0 | Street | The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and…The May vehicle came to a gentle stop at the railroad crossing (about -0.8 m/s2 deceleration) as designed, but the agent behind did not come to a stop and made contact with the AV. The May shuttle behaved as expected and slowed down to a stop in a safe manner. The collision was unavoidable from the shuttle side. | |
| 30413-5633 | ADS | May Mobility | 2023-05 16:40 | Grand Rapids, MN | 2021 Toyota Sienna | ADS | Non-Motorist: Other | No Injuries Reported | 0 | Intersection | On Tuesday May [XXX] at 16:40 local time, the May shuttle was driving Northbound from [XXX] to [XXX] in Grand Rapids, MN, in autonomous mode and was followed by 2 people riding on scooters. As the May shuttle made the tu…On Tuesday May [XXX] at 16:40 local time, the May shuttle was driving Northbound from [XXX] to [XXX] in Grand Rapids, MN, in autonomous mode and was followed by 2 people riding on scooters. As the May shuttle made the turn, the VRUs were traveling in the same direction as the May shuttle on opposite sides of the lane. As the May shuttle completed the turn at 10 MPH, the brakes were applied and the vehicle came to a complete stop because one of the riders attempted to cross over in the lane which caused VRU safety buffer to intersect with vehicle path, which led the vehicle to slow to a stop. The scooter rider contacted the rear left rear bumper of the shuttle. Scooters were traveling at an estimated speed of 12 mph and accelerating. | |
| 30413-5396 | ADS | May Mobility | 2023-04 16:16 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | Passenger Car | No Injuries Reported | 18 | Street | On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice a…On Friday April [XXX] at 16:16 local time, the May shuttle was driving Westbound on [XXX] in Ann Arbor, MI in autonomous mode and was followed by another vehicle. The following vehicle was traveling approximately twice as fast as the May shuttle and catching up to the May shuttle from behind. The May shuttle began to slow for traffic ahead, which was stopping for a red light, but the following vehicle did not decelerate. While slowing, the May shuttle identified a bollard on the side of the road as a likely pedestrian and added a safety buffer which intersected with the predicted trajectory of the shuttle. This caused the shuttle to increase deceleration to avoid the projected collision with the buffer. The following vehicle started braking late and impacted the May shuttle from behind with a relative velocity of 6.2 m/s. Re-simulation of this event with a future software version shows that the May shuttle would have decelerated less abruptly. | |
| 30413-4352 | ADS | May Mobility | 2022-12 18:38 | Ann Arbor, MI | 2020 Lexus RX450h | ADS | SUV | No Injuries Reported | 0 | Street | Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle…Operator turned onto [XXX] headed westbound approaching the stop sign at the intersection with [XXX]. In autonomy, the subject vehicle came to a stop. An SUV behind the subject vehicle then rear-ended the subject vehicle. No injuries were reported by the operator or the driver of the other vehicle and there was no damage to the SUV and a small crack in the bumper for the subject vehicle. | |
| 30413-4378 | ADS | May Mobility | 2022-12 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Motorcycle | No Injuries Reported | 0 | Street | Subject vehicle left the [XXX] headed southwest on [XXX]. Following the [XXX] intersection a motorcycle started following us closely. The subject vehicle came to a stop and the motorcyclist attempted to brake in time, bu…Subject vehicle left the [XXX] headed southwest on [XXX]. Following the [XXX] intersection a motorcycle started following us closely. The subject vehicle came to a stop and the motorcyclist attempted to brake in time, but hit the motorcycle's left mirror/handlebar against the rear passenger-side of the subject vehicle's bumper. | |
| 30413-4170 | ADS | May Mobility | 2022-11 15:43 | Ann Arbor, MI | 2020 Lexus RX450H | Unknown, see Narrative | Non-Motorist: Cyclist | No Injuries Reported | 4 | Intersection | Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have …Operator was approaching stop sign at the intersection of [XXX] westbound and [XXX] northbound, which is a planned disengagement (this unprotected turn is outside of our ODD). If left in autonomy, the vehicle would have come to a full stop before the stop line and remained stopped until the operator took over. 6 seconds prior to incident, operator took the vehicle over manually before it could have stopped in autonomy. Operator moved the vehicle manually passed the stop line, colliding with a bicyclist's back tire. No injuries reported from the bicyclist or the operator and no damage to the vehicle or bicycle. | |
| 30413-3943 | ADS | May Mobility | 2022-09 09:02 | Sun City, AZ | 2021 Toyota Sienna | ADS | Passenger Car | No Injuries Reported | 0 | Parking Lot | The May Mobility vehicle was traveling in autonomy through a parking lot and comes to a stop due to a vehicle backing up. Vehicle begins to reverse further so the operator in the May Mobility vehicle takes over and manua…The May Mobility vehicle was traveling in autonomy through a parking lot and comes to a stop due to a vehicle backing up. Vehicle begins to reverse further so the operator in the May Mobility vehicle takes over and manually reverses. The other vehicle continues backing up and does not stop, contacting the front of the May Mobility vehicle. Other vehicle then proceeds to drive away. | |
| 30413-3764 | ADS | May Mobility | 2022-08 16:15 | Arlington, TX | 2020 LExus RX450H | ADS | Pickup Truck | No Injuries Reported | 10 | Intersection | May Mobility vehicle is traveling westbound in autonomous mode on [XXX], stopped at a red light. When the traffic light turns green, the subject vehicle accelerates up to approximately 10mph. Approximately halfway throug…May Mobility vehicle is traveling westbound in autonomous mode on [XXX], stopped at a red light. When the traffic light turns green, the subject vehicle accelerates up to approximately 10mph. Approximately halfway through the intersection of [XXX], the subject vehicle begins to slow down due to construction fencing that is intruding into the lane, eventually coming to a complete stop. The safety operator takes over manual operation via the accelerator pedal, but is struck from the rear by a Toyota pickup that was following. The Toyota was first struck by the Chevy vehicle traveling behind it, pushing the Toyota into the subject vehicle. | |
| 30413-3138 | ADS | May Mobility | 2022-05 16:11 | Arlington, TX | 2020 Lexus RX450H | ADS | Pickup Truck | No Injuries Reported | 11 | Street | The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passe…The May vehicle was traveling on an unpainted (no center line) residential road with vehicles parked along the right side of the road. The May vehicle passed too close to a parked vehicle, causing the May vehicle's passenger-side mirror to contact the parked vehicle's driver-side mirror. The May vehicle's ground mapping module had fallen significantly behind in its processing of lidar data. As a result, actual objects were being filtered out of the lidar data during object detection. This filtering caused the truck to oscillate between being detected, detecting only the cab, detecting the cab and mirror, and not being detected at all. After assessing the issue, it has been determined that ground map latency alone will not cause safety issues. There is no risk to VRUs, or anything at ground level. The issue was with something in the air (mirror), above the ground. A permanent fix to address the ground map latency issue is in process and will be implemented in the entire fleet within the next 30 days. The second factor in the collision is that we were artificially constraining the vehicle to the right side of the road due to ambiguous and unpainted roadway. If we change that constraint to an advisory line (and allow the vehicle to cross the line to the left), we would have been far enough to the left to avoid collision (simulation success). Solution Implementation: AVO training for extra caution related to protruding items like mirrors (short term), software changes coming in the next update and hotfix (within 30 days), and further improvement in the following update (within 60 days). Until the tested software changes are implemented, we have advised the AVOs to take extra caution in these scenarios and to continue to disengage autonomy when desired. As always, we sacrifice autonomy for safety, as needed. | |
| 30413-1206 | ADS | May Mobility | 2021-08 11:16 | Indianapolis, IN | 2020 Lexus RX450H | ADS | Other, see Narrative | No Injuries Reported | 6 | Street | Vehicle made a right turn and struck the curb, causing a blown tire. Vehicle elected a controller path mid corner, which caused the curb strike. We have assessed the localities where this could occur and are taking those…Vehicle made a right turn and struck the curb, causing a blown tire. Vehicle elected a controller path mid corner, which caused the curb strike. We have assessed the localities where this could occur and are taking those turns in manual operation. We are currently testing a fix that will make our controller more aware of the curb to prevent future occurrences. | |
| 30413-1207 | ADS | May Mobility | 2021-08 11:30 | Ann Arbor, MI | 2020 Lexus RX450H | ADS | Other, see Narrative | No Injuries Reported | 22 | Street | Vehicle was moving forward and veered slightly to the left, making contact with the curb, resulting in a blown tire. Curb strike occurred during testing. There was human error involved in defining the desired vehicle pos…Vehicle was moving forward and veered slightly to the left, making contact with the curb, resulting in a blown tire. Curb strike occurred during testing. There was human error involved in defining the desired vehicle pose in the lane, which led to a curb strike. We have since resolved this by fixing the desired pose. | |
| 30413-1130 | ADS | May Mobility | 2021-07 16:15 | Indianapolis, IN | 2020 Lexus RX450H | ADS | SUV | No Injuries Reported | 18 | Street | Summary of incidentLeading up to the event, the autonomy system functioned as expected, following the route through the intersection, slowing appropriately for other road users and the red light. Vehicle autonomous beha…Summary of incidentLeading up to the event, the autonomy system functioned as expected, following the route through the intersection, slowing appropriately for other road users and the red light. Vehicle autonomous behavior was performing as expected and did not require a takeover.Description of event:16:17:30 May vehicle, traveling East on [XXX], in full working order with no errors, autonomously navigates the [XXX] and [XXX] intersection.16:17:35 May vehicle autonomously begins to slow to match the speed of a vehicle several car lengths ahead merging into our lane from the right.16:17:37 By means of an accelerator pedal push the vehicle is moved into manual mode by the safety operator - from this point forward, the vehicle remains under control of the safety operator.16:17:43 Manual acceleration command via the pedal increases.16:17:44 Safety operator manually continues straight which, due to the slight change in angle of the road, brings the May vehicle into contact with the first vehicle to the right.16:17:44 Safety operator manually applies brake.16:17:45 With the manual brake command now at maximum the May vehicle makes contact with the second vehicle.Vehicle indicators for manual or autonomy mode:The visual indicator for autonomy was functioning properly and as expected in the time leading up to and during the event.The audio communication device in the vehicle was functioning properly and was used to call for assistance and to report the incident.The audio beep to indicate a state change was functioning properly.The safety operator had some audio indication that he had exited autonomy and entered manual operation, and he had full visual indication on his dashboard. |
What this table is and is not. Rows are the operators' own filings, not verified cases, and a filing does not establish fault. NHTSA redacts most Level 2 narratives as confidential business information, so the text column is empty for most Tesla rows; the structured columns are not redacted. When one crash is filed by several entities, an operator and the fleet owner for example, NHTSA gives the filings one same_incident_id; the "one row per incident" view collapses them into a single row at the highest severity any filer alleged, with the count of filings and every report number beside it, so a count of incidents or deaths is not inflated by duplicate filings. The table joins NHTSA's current files (incidents from June 2025, after the third amended order) with its 2021-2025 archive, which used an older layout: severity labels, roadway and weather fields differ between the two sets, and the source_set column in the CSV says which one a row came from. Level 2 reports are shown here because the file contains them, but they are not cases in the register, which counts a vehicle as a robot only when nobody inside is responsible for driving. Source: NHTSA SGO 2021-01. On 7 November 2026 we filed a public comment built on this table in the California Public Utilities Commission's Rulemaking R.12-12-011, asking for machine-readable mileage files and a crosswalk between the Commission's incident categories and the SGO definitions. The themed reading of the driverless narratives is on the reports page.