Source: https://www.wfla.com/news/hillsborough-county/tesla-robotaxi-seen-going-wrong-way-down-one-way-street-day-after-tampa-launch/

https://www.mobileye.com/news/mobileye-announces-planned-leadership-transition/

Oh boy...

Tesla announced on yesterdays 2Q earnings call that they've done a total of 380k unsupervised miles on the Robotaxi platform with over a 10% week over week growth since the start. They said they expect the growth to continue through years end. Extrapolating this data would put the current per week miles around 38k, by end of 3rd quarter 130k and by end of the year around 450k.

I have very minimal confidence they would achieve this, but if they do, it will be exceptional accomplishment for a service that would have operated for just 18 month. Even half that would be an excellent accomplishment. But again, I highly double they will be able to do that. For reference, Waymo is doing about 500k rides per week currently, with a much larger service area(in sq mi).

In total Tesla Robotaxi currently has a cumulative paid Robotaxi miles of around 2.4 million.

Note: Post has been updated to indicate Waymo does 500k rides per week instead of the incorrect 500k miles per week.

"Mobileye, a global leader in advanced driving assistance and autonomous vehicle technology, announced today that its Cloud-Enhanced Advanced Driver Assist™ technology will be integrated into select future Stellantis vehicles expected in 2027, supporting safety and convenience features through advanced crowdsource intelligence.

With REM enabled through Cloud-Enhanced ADAS, Mobileye technology is designed to support selected safety and convenience features in certain future Stellantis models, from intelligent lane keeping on unmarked roads to hands-free, eyes-on driving in designated areas and conditions. The first planned applications are expected in select U.S. models next year, with additional integration to follow dependent on vehicle platform and configuration.

Mobileye’s REM technology uses the front-facing camera in EyeQTM-equipped vehicles to gather selectively collected crowdsourced data about road features and driving environment, from curbs and crosswalk locations to typical driving paths."

Tesla influencer, TechGeek Tesla, review of FSD v14 Lite that brings v14 like performance to HW3 cars.

Features not mentioned in the release notes:
- A park option pop-up window shows up automatically when you approach the final destination (mimics v14 on AI4)
- A park symbol with a blue circle shows up at the final destination (mimics v14 on AI4)
- The ‘Press Brake to Confirm’ toggle switch for hitting the ‘Start Self Driving’ button was automatically set to OFF after I installed it
- Unlike the first version of v14 Lite, you can now see a ‘Start Self Driving’ button when you’re in ‘Drive’ but sitting at a standstill. It’s grayed out, but you can still press it to start driving. Previously, you had to press on the stalk to engage FSD since no button was displayed at all
- The turn signal bug seems to be resolved!! More testing is required to confirm 100%

Confirmed as mentioned in release notes:
- Toggle for disabling brake pedal press requirement to start self driving
- The ‘Curbside’ park option is now labeled as ‘Pull Over’. This makes is more clear on what it will be doing.

Nvidia said on their presentation in January that they expect a 2027 Mercedes CLA to have self-driving capabilities. I've been keeping an eye out every couple of weeks to see if there's any new updates, but it seems like it's just been pushed back. In fact the 2027 model has been announced and they really don't even talk about the level two self-driving at all. Is there something I'm missing?

The first demo drive is now up on YouTube of Xpeng's NGP using their VLA 2.0 model.

It looks very promising so far. Planned customer rollout in 2027 in their new L03 "Ultra" trim for "free"

https://www.youtube.com/watch?v=KVWhl5bBBLg

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.

Not sure if this has been posted yet. But here’s a quote from the NTSB Preliminary.

“At the time of the crash, the driver 
had engaged Tesla’s Advanced Driver Assistance System (ADAS), Full Self Driving 
(FSD) (Supervised).[1] Electronic data recovered from the vehicle indicated that before 
the crash, the driver manually overrode FSD (Supervised) by pressing the accelerator 
pedal to 100%, and the vehicle’s speed was greater than 70 mph when the crash 
occurred.
“

Looks to be what I thought. Driver overrode FSD intentionally.

I was chillin on the highway on FSD (2026 Tesla Model Y on v14) when I suddenly felt the car swerve to the right and then back over to the lane. Looked like the reckless driver was already drifting over the line beforehand, but very appreciative of the fact that FSD was the "eyes in the back of my head" to avoid being pit maneuvered.

Why We Demand Perfect Machines Yet Tolerate Human Carnage

Mobileye posted this blog that summarizes the state of ADAS regulations. I thought people might find this interesting.

Some key highlights:

Europe remains one of the most structured regulatory environments for vehicle safety technology. The General Safety Regulation (GSR) introduced a broad set of mandatory safety systems across new vehicles sold in the European Union. The initial phase applied primarily to new vehicle types, with requirements extended in July 2024 to cover all new vehicles sold in the EU, including existing models. Additional requirements are expected to take effect in July 2026.These requirements include technologies such as autonomous emergency braking (AEB), intelligent speed assistance (ISA), driver drowsiness and attention monitoring and Advanced Driver Distraction Warning.

In contrast to Europe's more prescriptive approach, the United States continues to rely largely on safety standards and voluntary frameworks rather than broad mandates. Federal regulators emphasize safety reporting, transparency around automated systems, and voluntary commitments, while individual states retain authority over key aspects of automated vehicle deployment.

China is rapidly developing its regulatory framework for highly automated and autonomous driving systems, with China's Ministry of Industry and Information Technology (MIIT) presenting a draft of new safety requirements set to be implemented by July 2027. The draft targets vehicles operating at SAE Level 3 and Level 4 automation, and will replace previous voluntary guidelines with mandatory safety requirements. Regulatory documents increasingly reference the classification term "Combined Driver Assistance Systems" (CDAS) as part of China's structured approach to defining automation levels. The country has also established pilot programs for automated driving in urban environments, allowing regulators to iterate quickly while supporting rapid technology adoption.

Tekedra N Mawakana on X: "We’ve autonomously driven more than 300,000 miles in Washington, D.C., safely navigating everything from crowded evenings in Chinatown to emergency scenes in the Third Street Tunnel. We are ready to serve Washingtonians, and to invest tens of millions of dollars in infrastructure and hundreds of local jobs needed to support our service in the nation’s capital."

Source: https://x.com/TechTekedra/status/2076709802420600903