Headlines about self-driving car crashes dominate news cycles, but context is often missing. Are robotaxis genuinely more dangerous than human drivers, or does every minor fender-bender get amplified because the vehicle has no one behind the wheel? For consumers evaluating whether to step into a driverless pod, the answer requires hard data — not marketing claims or viral dashcam clips.

This analysis breaks down the current state of Level 4 robotaxi operations in the United States: where they run, what their safety records actually show, which technology stacks power them, and where regulators stand as of 2026. We'll also draw a firm line between true driverless robotaxis and consumer driver-assist systems like Tesla FSD Supervised, because conflating the two distorts the crash data entirely.

What "Self-Driving" Actually Means: SAE Levels Explained

Before examining crash data, you need to know which vehicles we're talking about. The SAE International J3016 standard defines six levels of driving automation, and most public confusion stems from lumping Level 2 and Level 4 into the same bucket.

SAE Automation Levels — What Each Level Requires
LevelNameWho DrivesExamples
Level 0No AutomationHuman does everythingBasic cruise control
Level 1Driver AssistanceHuman drives; system assists steering OR speedAdaptive cruise, lane-keeping
Level 2Partial AutomationHuman drives; system assists steering AND speed simultaneouslyTesla Autopilot/FSD Supervised, GM Super Cruise, Ford BlueCruise
Level 3Conditional AutomationSystem drives in limited conditions; human must take over when requestedMercedes Drive Pilot (limited markets)
Level 4High AutomationSystem drives entirely within its operational design domain; no human driver neededWaymo One, Zoox, Cruise (pre-suspension)
Level 5Full AutomationSystem drives everywhere, all conditionsDoes not exist commercially
Key Distinction: When media reports a "self-driving car crash" involving a Tesla on Autopilot, that is a Level 2 incident where a human driver was legally responsible for supervision. When a Waymo vehicle is involved in a collision in Phoenix, that is a Level 4 incident with no human driver present. These are fundamentally different scenarios with different liability frameworks and different implications for autonomous vehicle safety. This article focuses on Level 4 robotaxi operations.

Where Robotaxis Actually Operate in 2026

Despite years of expansion announcements, Level 4 driverless robotaxi service remains geographically constrained. Here's where you can hail a ride with no one in the driver's seat right now:

Live Level 4 Robotaxi Service Areas (2026)
OperatorCityService AreaHoursVehicle
Waymo OnePhoenix, AZ~225 sq mi (metro Phoenix including Chandler, Tempe, Mesa, Scottsdale)24/7Jaguar I-PACE (Gen 5/6 sensor suite)
Waymo OneSan Francisco, CA~50 sq mi (most of SF proper)24/7Jaguar I-PACE (Gen 5/6 sensor suite)
Waymo OneLos Angeles, CA~80 sq mi (Santa Monica, Hollywood, Downtown, Westside)24/7Jaguar I-PACE (Gen 5/6 sensor suite)
Waymo OneAustin, TXLimited geofenced zones (expanding)Limited hoursJaguar I-PACE
ZooxFoster City, CALimited pilot areaLimited hours, invite-only/employeeZoox purpose-built vehicle
ZooxLas Vegas, NVLimited corridor testingLimitedZoox purpose-built vehicle

Notable absence: Cruise, which once operated in San Francisco, Phoenix, and Austin, suspended all driverless operations in late 2023 after a serious incident in San Francisco where a pedestrian was dragged. As of 2026, Cruise has been gradually returning to testing with human safety drivers but has not resumed fully driverless commercial service. GM has signaled a cautious, phased re-entry.

If you live outside these specific geofenced zones, you cannot use a Level 4 robotaxi — no matter how many expansion announcements you've read. Service areas are defined by high-definition mapping, validated edge-case coverage, and regulatory approval boundaries.

Self-Driving Car Crashes: What the Data Actually Shows

This is where nuance matters most. Robotaxi operators in California are required to report collisions to the California DMV and disengagement events to the state's Public Utilities Commission. The National Highway Traffic Safety Administration (NHTSA) also maintains a Standing General Order requiring crash reporting for vehicles equipped with Level 2 and above automation.

Safety Data Snapshot — Waymo (through mid-2025 reporting):
  • Total driverless miles driven: Over 10 million fully autonomous miles across Phoenix, SF, and LA combined
  • Reported collisions: Several hundred DMV-reported incidents across all operations
  • Injury severity: Vast majority are low-speed, property-damage-only contacts (under 15 mph). Waymo's own published safety study (peer-reviewed, 2023) claimed a 85% reduction in injury-causing crash rates compared to human benchmarks in Phoenix
  • Common collision types: Rear-ended at stoplights, side-swiped in low-speed traffic, contact with stationary objects during complex maneuvers
  • At-fault determination: In the majority of reported incidents, the other human-driven vehicle was determined to be the at-fault party

Note: Waymo's internal safety studies compare their crash rates to human baseline data from the same geographies. Independent third-party validation at scale remains limited.

The Cruise San Francisco Incident: A Case Study

The October 2023 Cruise incident in San Francisco remains the most consequential robotaxi safety event to date. A Cruise vehicle struck a pedestrian who had been thrown into its path by a human-driven vehicle. The robotaxi braked but then pulled over to the curb, dragging the pedestrian approximately 20 feet while she was underneath the vehicle. The incident led to:

  • California DMV suspending Cruise's driverless permit
  • Cruise voluntarily pausing all nationwide driverless operations
  • NHTSA opening an investigation
  • Significant leadership changes at Cruise
  • A fundamental reset of public and regulatory trust in robotaxi deployment timelines

This single event demonstrated that while robotaxi collision rates per mile may be competitive with or better than human drivers in routine scenarios, edge-case handling — particularly post-collision behavior — remains a critical vulnerability. The vehicle detected the initial impact but failed to appropriately manage the aftermath.

Human Driver Baseline: The Comparison Context

For perspective, the U.S. sees approximately 6 million police-reported crashes annually, with roughly 1.35 fatalities per 100 million vehicle miles traveled (NHTSA, 2022 data). Human drivers are impaired, distracted, fatigued, or speeding in a significant percentage of serious crashes. Robotaxis don't drink, text, or fall asleep — but they do encounter scenarios their training data hasn't fully covered.

Technology Stack: How Robotaxis See the World

Level 4 robotaxis rely on sensor fusion — combining multiple perception systems to build a real-time 3D model of the environment. Here's how the major operators differ:

Waymo — Multi-Sensor Lidar-Heavy Stack

  • Lidar: Custom-designed rooftop and perimeter lidar units (Gen 5: ~5 units; Gen 6: reduced count with improved range). Provides precise 3D point clouds up to 500+ meters.
  • Cameras: 29+ high-resolution cameras for traffic light state detection, sign reading, lane markings, and object classification.
  • Radar: Multiple radar units for velocity detection and adverse-weather penetration.
  • Audio: External microphones to detect sirens from emergency vehicles.
  • Compute: Custom AI inference hardware processing terabytes of sensor data per hour.

Zoox — Purpose-Built, Symmetric Sensor Coverage

  • Vehicle: Custom bidirectional vehicle with no steering wheel — designed from scratch for autonomous operation.
  • Sensors: Lidar, cameras, and radar distributed symmetrically on all four corners for 360-degree redundancy.
  • Design philosophy: Every sensor has a redundant pair for fault tolerance.

Tesla FSD Supervised — Camera-Only (Level 2, Not Robotaxi)

  • Cameras: 8 surround cameras, no lidar, no radar (removed in recent model years).
  • Approach: Vision-only neural network inference.
  • Status: Level 2 driver-assist — human driver is legally responsible at all times. Not approved or deployed as a driverless robotaxi service anywhere.

The lidar-vs-camera debate is largely settled for Level 4 commercial deployment: every operational robotaxi service in the U.S. uses lidar as a core sensor. Camera-only approaches (Tesla) remain at Level 2, where the human driver serves as the redundancy layer.

Robotaxi Pricing vs. Uber and Lyft

Robotaxi fares vary by city, time of day, and demand, but here's how Waymo One generally compares to traditional rideshare:

Typical Robotaxi vs. Rideshare Pricing (2026 Estimates)
ScenarioWaymo OneUberX / LyftNotes
5-mile trip (off-peak)$12–$18$10–$16Roughly comparable; Waymo sometimes cheaper with promotions
5-mile trip (peak hours)$16–$25$15–$30Waymo pricing tends to surge less aggressively than Uber/Lyft
10-mile airport trip$25–$40$22–$45Depends heavily on airport surcharges and route
Subscription/discountsWaymo offers promo credits for new users; no formal subscriptionUber One ($9.99/mo) for discountsWaymo has historically subsidized rides to build adoption

Important context: Waymo's current pricing likely does not reflect the full long-term cost of operations. The company is backed by Alphabet and has been operating at a loss to build market share and gather data. Whether robotaxi rides remain price-competitive without subsidies once the industry matures is an open question.

How to ride: Download the Waymo One app (iOS/Android), create an account, set your pickup and dropoff within the service area, and request a ride. The vehicle arrives, you unlock it via the app, and it drives you to your destination with no one in the driver's seat. In-app features let you control music, temperature, and make stops.

Current Limitations: Where Robotaxis Cannot Go or Operate

Operational Limitations — What Robotaxis Cannot Do:
  • Geofence boundaries: If your destination falls outside the mapped service area, the ride cannot be requested. Waymo's Phoenix coverage is ~225 sq mi; SF is ~50 sq mi. Crossing a geofence boundary is not possible.
  • Heavy weather: Dense fog, heavy rain, and snow degrade lidar and camera performance. Waymo has reduced or paused service during severe weather events. Phoenix's dry climate is a reason it was the first market.
  • Construction zones: Temporary lane closures, moved barriers, and flaggers create scenarios that may not match the vehicle's HD map. Robotaxis may reroute, pull over, or request remote human assistance.
  • Unusual road configurations: Unmapped driveways, private roads, parking garages (most), and rural roads are outside the operational design domain.
  • Emergency vehicle interactions: While robotaxis are programmed to yield to sirens, complex multi-emergency-vehicle scenarios remain challenging.
  • Pets and unusual cargo: Service animals are generally accommodated; policies on pets vary. There is no driver to assist with loading luggage or mobility devices.
  • Passenger emergencies: If a passenger has a medical emergency mid-ride, there is no driver to pull over and assist. In-app support can connect to remote operators and emergency services.

Regulatory Oversight: Who Approves Robotaxi Operations

Robotaxi deployment in the U.S. involves overlapping jurisdiction between state and federal authorities, and the regulatory framework remains a patchwork:

  • California Public Utilities Commission (CPUC): Regulates robotaxi operations as passenger carriers. Operators need CPUC permits to charge fares for driverless rides. The CPUC can impose restrictions or revoke permits (as seen with Cruise).
  • California DMV: Issues testing and deployment permits, collects collision reports, and can suspend permits for safety concerns.
  • NHTSA (Federal): Oversees vehicle safety standards and investigates safety defects. NHTSA's Standing General Order requires automated vehicle crash reporting. However, NHTSA does not "approve" robotaxi services — it regulates the vehicles, not the service operations.
  • State legislatures: Arizona has taken a permissive approach (no special permit required for testing, which is why Phoenix was Waymo's first market). Texas passed legislation enabling autonomous vehicle operations. Other states require specific legislation or have not addressed Level 4 deployment.
  • No comprehensive federal framework: Unlike aviation (FAA), there is no single federal agency with comprehensive authority to certify and oversee autonomous vehicle operations nationwide. This creates state-by-state variability in what's permitted.

This regulatory fragmentation means a robotaxi that's legal and operational in Phoenix may face years of permitting battles before operating in a city like New York or Chicago.

Putting Self-Driving Car Crashes in Perspective

The data available through mid-2025 suggests that Level 4 robotaxis operating within their validated domains achieve collision rates that are competitive with or better than human drivers for routine driving scenarios. Waymo's published research indicates meaningful reductions in injury-causing crashes in their Phoenix operating area.

However, several caveats are essential:

  1. Sample size: Even at 10+ million miles, robotaxi operations represent a tiny fraction of total U.S. vehicle miles. Rare but severe edge cases may not yet be reflected in the data.
  2. Operational design domain: Robotaxis operate in mapped, geofenced areas with favorable conditions. Their safety record cannot be extrapolated to all driving environments.
  3. Post-collision behavior: The Cruise incident demonstrated that how a robotaxi behaves after an initial collision matters as much as avoiding the collision itself. This remains an active area of development and regulatory scrutiny.
  4. Reporting bias: Every robotaxi collision is reported to regulators and often makes the news. The 6 million annual human-driver crashes receive no comparable attention. This creates a perception gap.
  5. Independent verification: Much of the safety data comes from the operators themselves. Robust, independent third-party safety auditing at scale is still developing.

Frequently Asked Questions

Where can I use a robotaxi service right now?

As of 2026, Waymo One offers fully driverless commercial rides in Phoenix, San Francisco, Los Angeles, and limited areas of Austin, TX. Zoox has limited pilot operations in Foster City, CA, and Las Vegas. Cruise has not resumed driverless commercial service since its late-2023 suspension. If you're outside these specific geofenced areas, no Level 4 robotaxi service is available to you.

How much does a robotaxi cost vs. Uber or Lyft?

Waymo One pricing is broadly comparable to UberX and Lyft — typically $12–$25 for a 5-mile trip depending on time of day and demand. Waymo has historically offered promotional pricing and tends to surge less aggressively. However, current pricing may reflect subsidies that won't persist indefinitely.

How safe are robotaxis — is there real data?

Yes, but with caveats. Waymo reports over 10 million driverless miles with a collision rate that their published research suggests is lower than human drivers for injury-causing crashes. The vast majority of reported incidents are low-speed, property-damage contacts, often where the other party is at fault. However, the Cruise 2023 San Francisco incident demonstrated that edge-case handling remains a vulnerability. Independent third-party safety validation at scale is still limited.

What are the current limitations of robotaxis?

Robotaxis cannot operate outside their geofenced service areas, may reduce or pause service in heavy rain, fog, or snow, can struggle with unmapped construction zones, cannot enter most parking garages, and have no driver to assist with passenger emergencies or unusual cargo. They are designed for specific, mapped urban environments — not all driving scenarios.

Is Tesla FSD a self-driving robotaxi?

No. Tesla Full Self-Driving (Supervised) is an SAE Level 2 driver-assist system. The human driver is legally responsible for supervising the vehicle at all times and must remain engaged. Tesla FSD is not approved as a driverless service anywhere, and Tesla vehicles are not operating as commercial robotaxis. Conflating Level 2 driver-assist incidents with Level 4 robotaxi incidents distorts the safety data for both categories.

What happens if a robotaxi gets into a crash?

The vehicle is programmed to stop, contact remote support, and the operator reports the incident to regulators as required. Passengers can communicate with remote operators via in-app support. Emergency services are contacted if needed. The operator's insurance covers the incident. Fault determination follows standard insurance and legal processes, with the robotaxi operator liable for at-fault incidents.