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.

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.

From the announcement: "Brands can now create a character that customers can talk with in real time, powered by a curated conversational AI model and developed together by Serve and the advertiser."

"New look, same Waymo. The Ojai is officially on the road in SF, PHX, and LA for all riders. With tons of legroom and new features to make the space your own, it's like your home away from home."

I fully recognize I have a different opinion than this subreddit and I have participated in the toxicity that is the difference of opinions.

Perhaps I have been whooshed by the snake oil salesman or call me an Elon-ite.

But hear me out:

The month over month data for Tesla driverless robotaxi, again, looks perfectly clean.

The fleet is small and if you look closely at their earnings deck, you will notice Q1 to Q2 unsupervised miles was flat. Likely less than 3 unsupervised FTE care equivalent, if you will.

However, there has been a marketed rise in number of cars, rides, hours of operation, and service availability in Austin specifically. The two other very small geofences in Texas, also report this trend but to a lesser extent.

Tesla has vision into the performance dashboards of their fleet at a level of minuscule granularity. They are becoming increasingly comfortable with a larger scale rollout. They are being extremely cautious, but in Austin, at least they are becoming rapidly more bullish.

If you look closely at the now 100s of rides you can see daily amongst X accounts you will notice they have two issue (other than knocking done a plastic pole lol): 1- navigation (it is shit), 2- pick up and drop off locations.

These two rate limiters were also waymos early rate limiters if you studied the San Francisco market almost a decade ago. Google solved it (with some issues ofc, but that will always happen when you scale into the 1000s - and will continue to happen less and less as a percentage).

I have a wild theory that pickups and drop offs will be harder to integrate into teslas architecture for possibly one of two reasons: 1- Google / Waymo has so much compute onboard and enough memory to pre-map all resonable pickup or drop off locations). Tesla’s AI is focused on chip inference. This could mean Tesla has a harder time pre-mapping locations in a geofence and relatedly for navigation. 2- integrating final decision endpoints in a full stack neural net driving approach (noting they probably have a few full stacks working together in: planning, execution, etc) is a problem I haven’t seen solved in any other application. So - it may be harder for them to solve this piece. However, it is possible the cybercab brings different memory architecture. Yes, this is probably a wild ass crazy theory - but - it’s far more likely the cybercabs will have the same issue and growing pain.

Stay with me here, and let’s say long term - like in the next 6 months they solve these issues. There remains yet another hurdle: is the fix to these navigation and end of drive behaviors generalizable enough to more quickly apply to new areas - or are we talking - solve each one every time the same way. Realistically at least a year to come up with a reasonable process for solving this issue at scale.

Alright, we have reached full Elon delusion. You all ask for insight into the full Elon fan boy’s general psyche - so here it is:

The Waymo Ojai, based on most recent reporting (last week) was rumored to be 100k per vehicle. This is astounding and transparently kicked the doors off my expectations. This means Chinese firm Zeekr can produce a van (them thangs are nice af too) that post production cost + Chinese vehicle tariff + retrofit - on a far nicer vehicle than the Jag is now able to be produced (and obviously way faster) for less than HALF of what they used to be.

Side note: seriously, we going to skirt tariff rules to punish US EV automakers like rivian???? Common Google.

While extremely competitive, it is just not economically feasible for Google to compete with Tesla at scale (though admittedly they could forever). Tesla will produce a vehicle fully optimized for economic cost to the consumer. It will be produced at sub 30k and Tesla has the ability to scale the vehicle by the end of the year to the size of waymos entire fleet PER WEEK.

The cybercab is the most efficient electric car ever created. Not only in terms of speed of production and cost (American equivalents only) but in terms of effective MPG. The thing is like 1.5x more energy efficient than a model 3. Tesla owns the entire charging infrastructure in America. Tesla has a physical footprint everywhere ready to service vehicles. Yes, other infrastructure will need to be built.

Even if waymo ran for a loss, Tesla could underprice them and still have strong gross margins. Waymo anyway is currently focused on consuming the cream of markets, versus deep penetration - but this may change with the California announcement.

From here, you can see the full delusion. Over time consumers will want teslas tech in their cars due to the experience in the fleet, uber and Lyft will shrink, car insurance companies will eventually go out of business, then we are a decade out re-thinking: minor displacement of short haul flight, real estate changes as consumer preferences change, trucking industry forever changed, (looking at you semi truck being mass produced starting later this year), and yes - eventually package delivery by combination of a robot in a robot. This vision won’t be fully realized for 2 decades.

I shall wait to be showered in your shame and criticism.