u/bobi2393

August NHTSA SGO Automated Driving System crash data was recently published, covering 124 new reports through July 15, 2026, compared to 122 new reports published last month.

Company	August	July	June	May
Waymo	103	102	191	28
Avride	8	7	11	10
Zoox	8	6	6	10
Tesla	2	4	1	2

The table omits companies that had zero or one new crash reports in August. I don't know why many Waymo reports were added in June rather than May. Note that those are NHTSA publication months, covering accidents reported through the 15th of the prior month.

Select accidents:

Waymo

Waymo was involved in 11 collisions that caused injuries. 6 were when the Waymos were stopped at 0 mph, two were 1-2 mph, a 5 mph crash in Washington D.C. occurred when a test driver had taken control, a 6 mph crash occurred when a passenger exited a moving Waymo and was run over by it, and a 33 mph crash occurred when a vehicle changed lanes into the Waymo.

Pavement still a problem: Five incidents involved the undercarriage of Waymos colliding with pavement. Three were turning into parking lots, one was in a parking lot, and one involved "steep pavement" while entering an intersection.

Thin objects still a problem: "The Waymo AV began to reverse into the parking stall and the rear of the Waymo AV made contact with a pole shaft."

Exiting while moving still a problem: "While the Waymo AV was slowing, the passenger seated in the right rear passenger seat exited the vehicle through the open door, placed their feet on the ground, and the rear right tire of the Waymo AV made contact with the Waymo AV passenger, who fell to the ground as the Waymo AV came to a stop."

Dooring still a problem: "...a Waymo AV passenger opened the rear left door and exited the Waymo AV. At the same time, a passenger car traveling westbound through the hotel loading zone proceeded to pass the Waymo AV to the left, and the front right side of the passenger car made contact with the open rear left door of the parked Waymo AV."

Roof clearance still a problem: In two Phoenix incidents, the Waymo roof sensor hit the underside support of a carport. In the past year, there have only been two other roof sensor hits, one hitting a clearance bar, and one under manual control hitting the front edge of a carport roof.

Avride

In an atypical mistake, with no damage, an Avride in autonomous mode was in the middle lane of one way street, with an SUV to its left, when "the AVRIDE AV initiated a left turn onto [XXX] from a non-turning lane" and made "light contact" at 4 mph with SUV.

In a concerningly common problem, an Avride was stopped at 4-way stop, and went straight when it was it had right of way; a vehicle to its left did not stop and hit the Avride. While the other driver is at fault, these types of accidents seem to plague Avride so disproportionately more than Waymo that I suspect many are reasonably avoidable with better software.

Zoox

A Zoox "braked hard" to yield to an approaching emergency vehicle, and was rear-ended while stopped, causing damage and a moderate injury with hospitalization to a passenger. "Zoox vehicle's camera footage shows that the driver of Vehicle 2 was holding a device in their right hand leading up to the collision. The driver of Vehicle 2 was cited for failing to decrease speed." That's the first report I can recall that mentioned another driver's likely cell phone use.

A Zoox slowed to yield to an approaching emergency vehicle, and was rear-ended while driving 1 mph, then the car behind the rear-ending car stopped and was rear-ended by the car behind it. "The police were notified, but did not arrive at the scene."

A Zoox was rear-ended in Miami, which isn't unusual, but again "Law enforcement was notified but did not arrive at the scene."

A Zoox stopped mid-intersection for a fast cyclist going downhill who didn't stop for a stop sign, then the cyclist lost control, went over their handlebars, and hit the Zoox. This sounds like a common idiot cyclist maneuver where they assume a motor vehicle will continue through an intersection without slowing when cyclist runs a stop sign, counting on the timing to not hit the motor vehicle. When cyclists inevitably hit a vehicle that stopped, they're usually pissed at its driver!

Tesla

Both Tesla accidents occurred while Teslas were stopped. The Teslas were driverless, and were blameless in the accidents.

Motional

Their only new accident reported in August mirrors their previously reported accident a couple months earlier. In both crashes, a safety driver took control of the vehicle to perform a lane change, which almost immediately resulted in an accident.

July NHTSA SGO Automated Driving System crash data was just published, covering 122 new reports through June 15, 2026.

• Waymo: 102
• Avride: 7
• Zoox: 6
• Tesla: 4
• May: 2
• Motional: 1

Last month Waymo posted 191 new crashes, Avride 11, Zoox 6, Tesla 1, and May 2.

Waymo selected crash details:

• Injuries: Of Waymo's 102 crashes, 11 involved injuries. Those include 2 moderate w/hospitalization, 1 moderate w/o hosp., 1 minor w/hosp., 4 minor w/o hosp., and 3 unknown injuries transported to hospital.
• Seatbelts: Of Waymo's 102 crashes, 45 accidents reported no passengers, 50 reported all belted, and 7 accidents reported unbelted passengers, 2 excusable due to entering/exiting. One unbelted accidents had 2 unbelted passengers who were both transported to the hospital with moderate injuries, after being T-boned while driving 22 mph through an intersection by a red-light runner. Waymo slowed and turned to try avoiding the vehicle.
• Models: 101 of 102 crash vehicles were Jaguar I-PACEs, 1 was a Zeekr RT. The Zeekr crash reported both in-vehicle and remote driver/operators. The Zeekr was stopped at a red in autonomous mode, when the safety driver took control, tried passing a line of cars to the right, slammed into a pickup, curb, and light pole at 20 mph initial impact, and was taken to a hospital with moderate injuries.
• Door idiocy: 2 crashes were due to door idiocy, one directly and one indirectly. In the direct one, a passenger being dropped off opened a door of their stopped Waymo into a passing vehicle. In the indirect one, a passenger opened the door of a moving Waymo, which caused the Waymo to stop in a traffic lane, and a shuttle bus that had stopped in time then tried squeezing past the Waymo and struck it.
• Animals: 3 crashes involved animals. A Waymo slowed for a domestic animal that entered its lane, but hit it at 28 mph. A Waymo slowed to a stop in-lane for an animal, but the Waymo was struck by another vehicle, while the Waymo passenger was not belted. A Waymo struck a deer that ran into the roadway at 48 mph, while the Waymo's passenger wasn't belted.
• Bicycles: 2 crashes involved bikes. In one, a bike rear-ended a stopped Waymo. In another, as a Waymo slowed to yield in-lane to a pedestrian altercation, a pedestrian carrying a bike emerged from behind an SUV stopped in-lane, and the Waymo struck one of the bike's tires at 12 mph.
• Reversing: In around a dozen crashes, Waymos were reversed into, which is normal. In one case, a safety driver disengaged autonomy as a heavy truck reversed toward it, and was not reported to do anything further as the truck hit the stopped Waymo. In an unusual edge case, an SUV that was stopped in-lane began rolling back, and the Waymo reversed until it was struck, and both vehicles stopped. Then the SUV started rolling again, and the same thing happened. As it rolled for a third time, the driver exited the moving SUV, and the Waymo avoided being hit again, before the SUV crashed into a second Waymo that was stopped to yield to the first Waymo's crashes.
• Pavement: In four crashes, Waymos turned into parking lots at low speeds (8, 9, 9, and 10 mph) when "the undercarriage of the Waymo AV made contact with the pavement" and needed to be towed away.
• PUDOs: Several collisions occurred while Waymos were stopped to pick up or drop off passengers while in a traffic lane or partially in a traffic lane, and in some of those cases were also partially stopped in a bike lane.

Avride's 7 crashes (no injuries, all belted):

• Avride T-boned at 26 mph after entering intersection on green light, by cross traffic running a red.
• Avride T-boned at 11 mph after entering intersection on green light, by cross traffic running a red.
• Avride roof made contact with train crossing arm when driving 10 mph, after stopping until arm raised, then proceeding forward as arm lowered again.
• Avride rear-ended by secondary impact of box truck hitting vehicle behind it, after confusing stop and re-start during attempted left turn.
• Avride was "cut off" by a vehicle changing across two lanes of traffic, which struck Avride while it was traveling 17 mph.
• Avride and another car were both merging into same lane, so Avride stopped, as did 3 cars behind it, including a second Avride, which was rear-ended by another vehicle.
• Avride was struck while driving 21 mph in left lane by a vehicle turning left out of a parking lot.

Zoox's 6 crashes (3 injuries, all belted).

• One occurred just after the safety driver took over turning, in response to another driver waving him through an intersection.
• Zoox rear-ended after hard-braking to 3 mph to avoid debris; passenger "pretty bruised".
• Zoox rear-ended while stopped while yielding to cross-traffic in hit-and-run, honking before impact.
• Zoox rear-ended while stopped at intersection in hit-and-run, honking before impact, and the passenger was injured.
• Zoox rear-ended while stopped at intersection in hit-and-run, and the passenger was injured.
• Zoox reversed into from a roadside parking spot while stopped, honking before impact.

Tesla's 4 crashes (no injuries, all belted):

• Remote operator trying to assist out of dead end road "entered a grassy slope" and hit a "hidden tree stump". (Continuing saga of remote operator mishaps).
• A Tesla hit a thin metal chain blocking a parking lot.
• In two accidents, Teslas were reversed into while stopped. No mention of honking or evasive reversing. (Waymos sometimes do either, Zooxes often honk, Avrides aren't reversed into as proportionally often).

May Mobility's 2 crashes (no injuries, all belted):

• Two Mays collided with a low-hanging utility cable, apparently 17 minutes apart (dates aren't listed, times are), while traveling 32 and 33 miles per hour.

Motional's 1 crash (no injuries, all belted):

• Safety driver disengaged autonomy while stopped at a red light, and immediately hit a car while trying to change lanes.

League ranking minimum set to Dragon 28, anyone can join. Been shorthanded a few months and relaunching recruitment effort. We have a core of 10-12 warring regularly, so have slid in 15v15 CWLs to Crystal League II, but we always participate. Frequent wars, with loose rotation of lowest ranked players if we're a couple over or under a multiple of 5 for war. We always finish clan games, and Clan Capital is fully upgraded (Capital League is Crystal League III).

Overall chill, friendly group, with maybe a reminder-nag toward end of war if someone hasn't used their attack. If you enable Clan Wars preference, and have Played Recently status, and are added to war, it's expected that you attack, though occasional oversights are understandable. Pretty standard practices, 1st attack hit mirror, 2nd attack fill in non-3-star attacks if you think you can 3-star, otherwise use your judgment, maybe waiting until later in war if you can before hitting someone else's mirror.

If you get really angry over someone not 3-starring, or missing their attack, or most anything else, that wouldn't be a good fit. Suggestions or polite criticism are fine, just keep it friendly! 😊

https://www.mlive.com/news/ann-arbor/2026/07/cement-truck-stuck-in-ann-arbor-underpass-closes-roadway.html

https://preview.redd.it/4xv1x3jbh1bh1.png?width=1280&format=png&auto=webp&s=d8d7069d07cd37e77aaa8ba98cec409192292423

June NHTSA SGO Automated Driving System crash data was just published, covering 217 new reports through May 15, 2026.

• Waymo: 191
• Avride: 11
• Zoox: 6
• May: 2
• Aurora, Motional, Nuro, PlusAI, Stack AV, Tesla, WeRide: 1

Of Waymo's 191 new crashes, 1 had moderate injuries with Waymo passengers transported to a hospital, 1 had moderate injuries treated at the scene (motorcyclist rear-ended a Waymo), 7 had minor injuries with hospitalization, and 11 had minor injuries without hospitalization.

I didn't read all the Waymo reports yet, but of the reports with injuries, all seemed pretty clearly to be the fault of others, although in two cases I think Waymo could have improved the outcomes through better engineering:

1. One of the injuries occurred when a Waymo passenger opened their door while the vehicle was stopped at a light in a traffic lane, dooring a cyclist who was passing in a bicycle lane. No active dooring protection is a longstanding Waymo behavior in their Jaguars.
2. One of the injuries occurred mid-ride when not all passengers in the Waymo were belted. The narrative didn't indicate whether they were previously belted, but initiating rides with unbelted passengers was a regular practice with Waymos in the past, and I haven't heard of that changing.

The Aurora semi's crash was due to passing camper trailer's awning coming loose and striking the Aurora; a safety driver took control and pulled the truck over.

May had one accident where it was rear-ended while being manually driven and correctly stopped for a flashing pedestrian crosswalk signal, and another accident where it was proceeding straight through a green when it was T-boned by someone who ran a red (May precrash speed 21 mph). One or more minor injuries requiring hospitalization were reported in the T-bone accident.

In Tesla's one new crash, a Tesla was stopped at a red turn signal, with a pickup stopped behind it, when the pickup started moving and hit rear-ended the Tesla. C'mon, humans!

PlusAI submitted their first crash report, but it was for a near-miss of a crash, and I don't think should have been reported under NHTSA SGO instructions.

WeRide's one crash was a normal rear-ending while the WeRide was stopped at a red.

Of Zoox's six accidents, three were when the Zooxes were stopped and were reversed into, and in two of those three cases the Zooxes honked before impact, but didn't try reversing. In a non-reversing incident, A Zoox stopped to pick up a passenger, when an approaching passenger activated the Zoox's doors, one of which struck the bumper of a vehicle trying to pull around the Waymo.

Avride continues to disproportionately get in accidents that are legally other people's fault, but most of which sound avoidable with better defensive driving, much like the video clip of an Avride being T-boned from a couple days ago. One of Avride's 11 accidents didn't involve contact with the Avride and I don't think should have been reported under NHTSA SGO instructions. Of the other 10, 3 were a normal rear-endings while Avrides were stopped, 2 sound like the Avrides may be at fault, and the remaining 5 sound like others were at fault, but seem like better awareness and planning had a chance to avoid those 5 accidents. (A majority of Waymo crashes, by comparison, are due to rear-endings while Waymos are stopped). Here are some brief summaries of the 7 non-rear-ending crashes:

1. An Avride tried changing from right to left lanes to avoid a stopped work truck, and apparently hit a vehicle in the left lane (Avride precrash speed 11 mph). This sounds like the Avride's fault.
2. An Avride driving slowly through a dropoff circle hit a parked vehicle's open door (Avride precrash speed 6 mph). It sounds like the door was open prior to the Avride trying to pass it, in which case this sounds like the Avride's fault.
3. An Avride proceeded straight through an intersection with a yellow light, when a vehicle on the road to its right entered the intersection in spite of a red light and hit the Avride (Avride precrash speed 29 mph). Minor injuries were reported that did not require hospitalization.
4. An Avride proceeded straight through an intersection where it had no stop sign, and a vehicle stopped at a stop sign on the road to its right entered the intersection and hit the Avride's right side (Avride precrash speed 18 mph).
5. An Avride changed from left to center lane to avoid a parked work truck shortly before a pickup tried changing from right to center lane, striking Avride's front right (Avride precrash speed 23 mph). I'm guessing the Avride was in its blind spot.
6. An Avride stopped behind a vehicle that stopped in front of it, then the vehicle in front reversed into the Avride; the Avride apparently didn't mention trying to reverse or honking its horn, as sometimes happens when Waymos are struck by reversing vehicles. (Around 19% of Waymo accidents at the beginning of the year were due to others reversing into them, and it would presumably be higher if Waymos didn't actively alert/avoid reversing vehicles.)
7. An Avride began a right turn when a cyclist trying to pass on the right ignored a stop sign and hit the turning Avride. Crash geometry is vague, but this seems like an instance where an ADS maybe should have seen the cyclist moving straight a car length or two back, and delayed its right turn until it was more confident the cyclist wouldn't try passing the vehicles and running the stop sign.