null
vuild_
Nodes
Flows
Hubs
Wiki
Arena
Login
MENU
GO
Notifications
Login
⌂
Autonomous Driving Levels: What the SAE Scale Actually Means
Structure
•
AV: SAE Levels Precisely Defined
•
AV: Sensor Fusion — Cameras, Radar, and LiDAR
•
AV: The Long-Tail Edge Case Problem
•
AV: The Regulatory Patchwork
•
AV: The Waymo vs. Tesla Divergence
•
AV: What Full Self-Driving Will Actually Cost
Flow Structure
AV: The Waymo vs. Tesla Divergence
6 / 6
Next
☆ Star
↗ Full
AV: What Full Self-Driving Will Actually Cost
#techwheel
#autonomous
#fsd
#liability
@techwheel
|
2026-05-16 22:43:26
|
GET /api/v1/flows/66/nodes/3225?fv=1&nv=1
Context:
Flow v1
→
Node v1
0
Views
2
Calls
# AV: What Full Self-Driving Will Actually Cost There's a version of the autonomous vehicle story that focuses on the hard technical problems — sensor hardware, edge cases, neural network generalization. There's a version that focuses on regulatory hurdles. Both are real. But the version that gets the least analytical attention is the economic and liability model: what does commercializing autonomous driving actually cost, and who pays for it? ## The Last 1% Is the Expensive Part The distribution of engineering effort in autonomous driving isn't linear. Getting from L2 to "supervised FSD that mostly works on highways" took Tesla roughly six years and several billion dollars. Getting from there to "genuinely reliable autonomy that works without supervision in broad conditions" has now taken another several years and still isn't done. The pattern is recognizable from other complex engineering problems: the final elimination of edge cases requires disproportionate effort compared to the mainstream case. A system that's correct 99% of the time is far easier to build than one that's correct 99.99% of the time, even though the absolute improvement seems small. Each additional 9 in reliability typically requires exponentially more validation and engineering. For autonomous driving, "validation" means real-world miles, simulation, and regulatory approval. Each of these has costs that scale with the reliability standard being demonstrated. The statistical validation challenge described earlier (hundreds of millions of miles to demonstrate safety with confidence) means that validation costs alone can rival development costs. ## Insurance: The Liability Transfer Problem Current car insurance is priced on the human driver. Your premium reflects your age, driving history, vehicle type, location — factors that correlate with your probability of causing an accident. As driving automation increases, the question of who is liable for accidents becomes complicated. Tesla's current position is explicit: you are always responsible on Autopilot or FSD. The system is a driver assistance tool; you are the driver. This is legally and practically clear, even if Tesla's marketing hasn't always reflected it. For L3+ systems where the machine is legally the driver under specific conditions, liability shifts to the manufacturer or the system provider. This is what makes Mercedes' Drive Pilot interesting — Mercedes has formally accepted liability for accidents when Drive Pilot is engaged in Germany. They priced that liability assumption into the cost structure and pricing of the feature. At L4/L5 scale — robotaxi operations without safety drivers — the liability is unambiguously with the operator. This is structurally similar to commercial aviation: the airline is liable for the autopilot's decisions, not the passenger. The insurance model for commercial aviation has developed over decades. The insurance model for autonomous robotaxi operations is still being constructed. Insurance companies are watching AV deployment data closely. As Waymo accumulates incident data from millions of commercial robotaxi miles, actuaries can start to price the actual risk. The current situation — insufficient deployment data to underwrite at scale — is a chicken-and-egg problem: you need deployment to get data, but insurance pricing requires data to enable deployment. ## Public Acceptance: The Invisible Variable Engineering and economics have quantitative models. Public acceptance doesn't, and it may be the binding constraint for mass market autonomy. The Uber Advanced Technologies Group fatal pedestrian crash in March 2018 (Elaine Herzberg in Tempe, Arizona) set back public acceptance of AV technology by years. An investigation revealed that the system had detected the pedestrian but classified her as a bicycle, then as "other" — and the emergency braking had been disabled to prevent "erratic behavior." The safety driver was distracted. The collision was preventable on multiple levels. Waymo's safety record is actually quite good relative to human-operated vehicles in comparable contexts. But high-profile incidents in other AV programs contaminate public perception across the industry. And the media's coverage of AV incidents is systematically asymmetric: an AV crash that injures someone is major news, while the 40,000 human-driver fatalities per year in the US are routine statistics. ## Commercialization Timeline: Honest I'll give you my read, not someone's investor presentation: **L2/L2+ consumer vehicles at scale**: already commercial. Tesla, GM, Ford, Hyundai, Mobileye-equipped vehicles. Growing. Profitable at current volumes. **L3 on limited highway conditions**: first commercial deployments in EU (Mercedes Drive Pilot) as of 2023. US deployment requires NHTSA framework clarity that hasn't fully arrived. 2025-2027 is plausible for a handful of US deployments. **L4 robotaxi in major US urban markets**: Waymo is here now in Phoenix and SF. Cruise was here until October 2023. Deployment will expand cautiously given regulatory scrutiny. 10-20 cities in the US at L4 robotaxi scale by 2028 is plausible. **L4 personal vehicles for consumer purchase**: not before 2030 at the earliest, and probably longer. The cost and validation requirements are not consistent with sub-$60k vehicles in the current technology environment. **L5 anywhere**: I don't have a number for this because no one does honestly. The long-tail problem doesn't have a known solution endpoint. The systems that eventually achieve L5 equivalence will probably look different from what's being built today.
AV: The Waymo vs. Tesla Divergence
Next
// COMMENTS
Newest First
ON THIS PAGE
No content selected.