The 1.8x safety margin offers a compelling empirical win for Tesla, proving that autonomous systems can already mitigate high-stakes human errors. However, the prevalence of low-speed collisions suggests the technology is currently a cautious student rather than a master driver.
深度探索
先修知识
- 暂无数据。
后续步骤
- 暂无数据。
深度探索
Tesla’s Biggest Robotaxi Test Just Happened本站添加:
Tesla's Robo Taxi is now nearly two times safer than humans in Austin. Today I'm going to do a deep dive in what we actually know about Tesla Robo Taxi safety right now. So an analyst named Raines, he ran the numbers and estimates that as of April, Tesla Robo Taxi in Austin is now about 1.8 times safer than human drivers in Austin. Top of that, for the first time, Tesla unredacted the crash reports. So we finally have a clear view of exactly what happened in each one.
17 incidents since launch on June 22nd, 2025.
Seven of those 17 were counted as Tesla at fault.
When you actually read them, two were just curb scrapes. Two happened while a remote teleoperator had control. That leaves three that were the car itself.
I'm going to walk you through what those three were.
So here's the plan. First, the safety number and how Raines built it. Then we're going to talk about those 17 incidents in detail, including the seven where Tesla was at fault.
Then why we still can't cleanly compare Tesla to Waymo. Then one crash report that honestly changed how I think about these cars. And finally, a New York Times piece written by doctors that frames this whole thing in a way I wasn't expecting.
So let me start with the headline because it's the thing that everybody's going to argue about. Raines, who tracks this stuff carefully, he estimates that as of April, Tesla Robo Taxi in Austin was at least about 1.8 times safer than the average human driver.
Now, I don't want you to just take the number. I want you to see how we got there because the method is the whole point. There's three pieces. The first piece is the human baseline. Using NHTSA data and counting both crashes that got reported and the ones that never do, he estimates a human driver has about one accident every 249,000 miles. That's the bar. That's what a Robo Taxi has to be.
Okay, then there's the mileage problem, which has always been the hard part.
Tesla doesn't hand you clean monthly miles driven numbers.
So Raines pulled all the mileage Tesla's reported, plus the 7-day active fleet size from Robo Taxi Tracker, and found the relationship between them is actually pretty stable. Stable enough that he can estimate the monthly Austin robot taxi mileage with under 5% error.
The last piece is how you handle the crashes. Tesla has months with zero crashes in Austin. February was zero.
So, single month rate bounces all over the place. To smooth that, he used a 3-month rolling crash rate.
And when you plot that against the human line, April is the month it crosses. For the first time, the rolling robot taxi crash rate came in safer than humans.
So, here's the claim.
Says that about 1.8 times safer in Austin as of last month. Built on real reported mileage, fleet data, and the actual federal crash reports. Hold on to that because the next thing we do is open up these crash reports and see if the number holds up.
So, this month is different from every month before it, and the reason is the redactions.
For the longest time, the Nitsa reports were redacted. You'd see that a Tesla robot taxi was involved in an incident, and then a black bar where the description should be. Tesla finally unredacted the narratives, retroactively, all the way back to the first one. So, now we can read them all.
And I read them all. Robot taxi tracker also ran an analysis on who was at fault.
Their breakdown came out to about 53% where somebody else was at fault. And about 41% where Tesla was. So, roughly nine versus seven out of 17.
Let me take that somebody else pile first because it's bigger and it's almost comical how consistent it is.
Over and over, it's a Tesla sitting still getting hit.
An SUV creeps forward at a red light and rear-ends the stopped Tesla.
A truck rolls forward at a stop sign and rear-ends a Tesla. A pedicab clips the side mirror as it rides past. A guy in a motor scooter pulls in behind a stopped car, steers into the back of it, and then hops the curb and rides off down the hot sidewalk.
A city bus makes a right turn and the bike rack on the front sideswipes the Tesla's side.
None of those are the car driving badly.
That's the car parked, basically, and the rest of the road being the rest of the road.
And I'm not going to soften this because honesty is the whole reason this video is worth your time.
Two of those seven were under teleoperation, meaning a remote human operator had taken over control, and a human is the one who put it into something.
In one, the safety monitor asked for help because the car wasn't proceeding.
The teleoperator took over, sped it up, turned it left, and drove it up over the curb into a metal fence.
In the other, a teleoperator took control during navigation and ran the car into a temporary construction barricade at about 9 mph, scraping the front fender.
So, those two are remote human errors, not the car's own driving.
Two more were curb scrapes, low-speed stuff. Reversing into a parking space and a rear tire catches the corner of a curb, that kind of thing. Cosmetic.
So, that leaves three that are the real deal. The car driving itself making contact with something it should have cleared.
The first one, the car's making this unprotected left into a parking lot entrance, and it drives into a metal chain strung across the entrance. Low speed, but it didn't see the chain.
The second one, it's turning onto a residential street passing a house with a dump trailer in the driveway. The trailer's gooseneck hitch is sticking out into the road, and the car's side mirror clips it.
And the third, it's going straight down a tight street with a heavy tow truck parked on one side and a car on the other, and the left side mirror catches the side of the tow truck's bed.
So, there's a very clear pattern here.
Chains, hitches, poles, mirrors, tight clearances.
There's even one where it reversed into a wooden electrical pole in a blocked alley.
The car's weak spot right now is low-speed precision around weird stationary objects. The slow, tight, fiddly stuff, not freeway speed or pedestrians in crosswalks.
I want to be fair about one thing across all of these. Every single one had a safety monitor present. These weren't empty cars roaming the city.
There's a person there. So, when you hear robo-taxi crash, picture a 5-mph mirror scrape with a monitor in the seat, because that's what the average one actually is.
EV Wire ran the numbers across all of them, and the average speed was about 5.9 mph with no major injuries.
Now, the question everybody jumps to is, "Okay, how does that stack up against Waymo?" And I have to be honest, right now, cleanly, it doesn't. We can't do an apples-to-apples. Here's why. On raw incident counts, it actually looks lopsided in Tesla's favor. Tobias Göbel pulled the federal numbers by month. In January, Waymo had 100 incidents. Tesla in Austin had five. February, Waymo 73, Tesla zero. March, Waymo 50, Tesla two.
First half of April, Waymo two, Tesla zero. Another tracker, Mayhoff, has Waymo's all-time total over 1,800 incidents with Tesla at 17.
But, you cannot just read those numbers off and declare a winner. Now, I won't let you walk away thinking that. Because Waymo's operating in something like 40 cities, actually 10 They're getting close to 10 cities, right? Atlanta, Austin, LA, Phoenix, San Francisco, and so forth. Tesla's robo-taxi count there is Austin only. Of course, the company in 10 cities has more total incidents.
It's driving vastly more miles in vastly more places.
So, to actually compare them, you need two things for each: in the same place over the same time, miles driven fully unsupervised, and the number of cars actually operating as robo-taxis. And for Tesla, both of those are pretty fuzzy. The exact unsupervised mileage isn't published cleanly. The active fleet size is estimated, not disclosed.
That's literally why Raines had to back into the mileage from fleet size and a stable relationship. It's a smart workaround, but it's an estimate, and he says so.
There's another wrinkle that matters.
The federal data files Tesla's Austin operation as ADS, actual automated driving. But, it files Tesla's Bay Area operation as ADAS, driver assistance.
Waymo's filed as ADAS everywhere. So, even the category labels aren't uniform across the two companies. If you're not careful about which bucket you're pulling from, you'll compare two different things and not even know it.
So, my honest position is this. The incident counts are a real encouraging signal for Tesla. But, anyone telling you that they've got a clean settled Tesla versus Waymo safety ratio is selling you more certainty than the data actually supports.
The right move is to watch the trend in Austin on a per-mile basis.
That trend is the one Waymo needs to show crossing the finish line.
I want to slow down on one specific incident because it flips the whole frame. So, in December, a robo-taxi is driving straight, and its rear right tire rolls over a patch of uneven pavement that punctures the tire.
The car detects the pressure loss.
On its own, it slows down to about 18 mph, pulls over to the side of the road, and puts itself into a safe stopped state. A minimal risk condition in the official language.
On the way to the curb while pulling over, the tire caught the corner of the curb, which is why this one even shows up in the crash list at all.
The thing that put this incident on the crash list is the car's safety like system handling a blown tire by itself.
Without a human touching anything, it sensibly decided it had a problem and parked itself out of traffic. A human driver gets a flat at speed, and half of them panic. They'll brake wrong or drift. This thing just calmly pulled over.
And that's what these cars really are.
They're not just cameras and a driving model. They're rolling computers wired into every system in the vehicle.
They got tire pressure, battery, motors, brakes, the whole car. It can file find a slow leak and act on it before a human would even notice the steering felt off.
These are the most self-aware cars on the road. They can diagnose themselves and respond.
And when you fold that back into the safety story, it's not just does the car avoid crashes, it's what does the car do when something physically goes wrong?
And the answer in the one real world example we have is it handled it better than most people would.
The last thread is one I did not see coming. The New York Times ran a guest essay from a neurosurgeon named Dr. Jonathan Slotkin.
He's not coming at this as a tech guy or a Tesla fan. He's coming at it as a doctor who spends his career putting people back together after car crashes.
So he put together an open letter signed by doctors and nurses asking the government to clear a faster path for self-driving cars.
And his argument is blunt. He calls it a public health imperative to quickly expand the adoption of autonomous vehicles.
The data he leans on is the Waymo record from a peer-reviewed study across more than 56 million driverless miles. 91% fewer serious injury or worse crashes than human drivers on the same roads.
80% fewer crashes causing any injury at all.
And they point to a projection that if just 30% of cars were fully automated, you might prevent 40% of crashes because the automated ones don't cause crashes and they react better when a human nearby screws up.
That's a different conversation than the one we usually have online. We argue about whether the technology is cool or whether the stock goes up. A trauma surgeon is looking at the same technology and seeing fewer people on his operating table. Fewer spinal injuries, fewer funerals.
When the people who deal with the records start writing letters asking for this faster, that tells you the safety case has crossed over from fan argument to medical argument.
Let me give the other side a fair hearing because this is what the audience wants, right? They want signal, not a pepper rally.
The first honest objection is the sample size. 17 incidents in a few months of Austin mileage is not a lot of data. One bad month, one serious crash, and that 1.8 times safer number moves. Rain knows this, which is exactly why he used a 3-month rolling average instead of a cherry-picking a good month.
But it's early. And early numbers are very noisy. Treat it as a real signal, but not a final verdict yet.
Second is safety monitors. Every one of these Austin incidents had a monitor present. So, we're measuring a system that still has a human backstop in the car. The real test, fully empty at scale, is still ahead. The good news is the at-fault incidents we do have are low speed and minor. The honest caveat is that safer than humans today includes that backstop.
Third, the comparison problem I already laid out. We don't have clean, disclosed, unsupervised mileage and fleet counts from Tesla. Until we do, every Tesla versus Waymo ratio has an asterisk on it.
I'd rather tell you that than hand you a fake clean number.
And fourth, the teleoperation piece cuts both ways. Yes, the two of the at-fault incidents were a remote human, not the car. That's good for the driving model.
But, it also means there's still a human in the loop steering these things sometimes. That human can put it into a fence. That's part of the current system, too. And it's fair to count it.
Now, here's the reframe.
Even with all of that, look at where the bar sits. The worst genuine mistakes this car made on its own were scraping a chain, clipping a couple of mirrors, and tapping a pole at walking speed. Nobody got hurt in those.
Meanwhile, the human drivers around it were the ones doing the rear-ending.
That's the actual picture once you read the reports instead of the headlines.
So, what do you actually do with this if you own Tesla or you're thinking about it? The thing that just changed isn't the technology.
The cars were already driving.
What changed is that the evidence got legible. We went from a redacted count that anyone could spin to readable narratives, plus a mileage-based safety estimate, plus a peer-reviewed medical case. The story stopped being trust me and started being here, read it yourself.
For the investment case, robotaxi safety is the gate everything else waits behind. The valuation people put on Tesla's robotaxi future assumes regulators eventually that the scale without a monitor in the seat.
Regulators move on evidence and on political cover. Readable safety data is evidence. Doctors writing letters is the political cover.
Both of those just showed up in the same month.
I'm not telling you to do anything with your money on one analyst estimate. I'm telling you the kind of proof that unlocks the next phase is exactly the kind of proof that just landed.
So, the smart move is to stop watching the hype and start watching the per mile trend and the regulatory response.
That's where the real money gets answered.
So, here's what I'd actually keep an eye on. The first thing is the monthly Nitsa crash data. It updates roughly monthly.
Watch whether Tesla's Austin incidents stay low as the miles climb. Rising miles with flat incidents is a signal that matters.
Then there's the per mile rate, not the raw count.
Anyone waving a total crash number at you without miles behind it is doing it wrong. Ask for the denominator.
Watch for the safety monitor coming out of the seat. The day Tesla runs Austin with no monitor at scale is the day safer than humans gets its final test.
That's the milestone to circle and we're almost there. We're over 50% of all cars in Austin are now unsupervised and it's moving up.
Keep an eye on whether the data stays unredacted and gets more complete.
Disclose unsupervised mileage and disclose fleet size would let us finally do a clean Waymo comparison. Let's push for it.
And then let's read the room on the medical and regulatory side. When more doctors, hospitals, and safety agencies start citing this data, that's the political path to scaling opening up.
So, step back from all of it and here's where I land.
For years, robo-taxi safety was an argument you can only win or lose with conviction because nobody had the receipts.
This month, the receipts showed up.
Readable crash reports. A mileage-based estimate that pulls the car ahead of humans in Austin. A blown tire the car handled by itself.
And a surgeon telling the New York Times this is a public health issue.
It's early. The numbers will move, but the conversation just changed from can it to how fast. And that's a very different place to be standing.
If you want me to keep reading the supports as they update and tell you what's really in them, no spin, please subscribe. Stick around. I'll keep tracking it month by month. Thanks.
相关推荐
Beyond Robotics | European Rover Challenge 2026
beyondrobotics
189 views•2026-06-01
Beatbot Sora70: JetPulse Technology and AI obstacle avoidance and navigation!
DroidModderX
26K views•2026-06-02
Tesla FSD 14.3.3 Hits Phoenix Streets - FIRST LOOK
anthonystesla
114 views•2026-05-29
NVIDIA Just Unveiled a 75 DOF Humanoid Robot
DPCcars
74K views•2026-06-01
Elon Musk Just Revealed Fremont Line for Optimus Gen 3 Mass Production
TheAINexusOfficial
180 views•2026-05-30
人機一体「零式人機 ver.2」 子ども企画【おもしろ発見!モビリティー】 #乗り物 #automobile #robot #shorts
KyodoNews
1K views•2026-05-28
China’s New Luna AI Robot Looks Shockingly Human...
NextGenHumanoids
850 views•2026-05-28
Reachy Mini: the $300 open source robot you can actually hack — Andres Marafioti, Hugging Face
aiDotEngineer
662 views•2026-05-29











