Riders in San Diego, Las Vegas, Tampa, and Denver will soon be able to hail a Waymo robotaxi with no human behind the wheel, as the company pushes into four new metro areas backed by a patchwork of state-level approvals. California DMV records confirm that Waymo holds authorization to test and deploy autonomous vehicles without a safety driver in San Diego, while Nevada, Florida, and Colorado each offer distinct regulatory paths that could accelerate or complicate the rollout. The expansion comes as peer-reviewed research based on 56.7 million Waymo rider-only miles offers the first large-scale comparison of driverless crash rates against human benchmarks, setting up a real-time test of whether the company’s safety record can survive contact with unfamiliar roads and rules.
Why four new cities are getting Waymo robotaxis now
The timing of this expansion is tied directly to how each state regulates driverless vehicles. California requires manufacturers to secure explicit geographic permits before operating without a safety driver. Waymo’s approved areas now include San Diego, giving the company a documented legal basis to put rider-only cars on those roads. That process is granular: the state defines where the vehicles can go and under what conditions, and can revise those boundaries as performance data accumulates.
Nevada takes a different approach. The Nevada DMV does not issue a permit or license based on a vehicle’s level of automation. Instead, developers file a testing registry application. That lighter-touch framework means Las Vegas operations face fewer geographic restrictions up front but also fewer state-imposed safety checkpoints before cars start carrying passengers. In practice, oversight shifts from pre-approval toward monitoring, with the burden on operators to self-certify that their systems meet federal and state traffic laws.
Florida’s path is even more permissive. State law, specifically Florida Statutes Section 316.85, declares that a fully autonomous vehicle may operate regardless of whether a human operator is physically present. No city-specific deployment authorization appears in the available regulatory record. Tampa, then, becomes a test case for what happens when a driverless fleet enters a market where the statute itself serves as the green light rather than a permit tied to mapped boundaries. Local officials may still influence curb access, pick-up zones, and fleet staging, but they are working within a statewide rule that treats the automated system as the legal driver.
Colorado rounds out the list, though no primary state regulatory filing or DMV record for Denver operations appears in the available source set. That gap matters because it leaves open the question of what specific conditions, if any, Colorado authorities have placed on Waymo’s planned service area. Without a public filing, residents and city leaders have less visibility into speed limits, weather constraints, or geofenced zones that might apply to early service.
The practical consequence of these regulatory differences is speed. States that rely on general statutes or simple registry filings rather than detailed geographic permits can expect faster rider-only expansion. But that speed comes with a tradeoff: fewer pre-deployment guardrails mean the first measurable differences in crash performance across cities will show up in federal data before state regulators have had a chance to set operating boundaries tailored to local risks.
Crash data at 56.7 million miles and what federal reporting requires
The safety case for this expansion rests heavily on a peer-reviewed study published in Accident Analysis and Prevention. That research compared Waymo rider-only crash rates by crash type to aligned human benchmarks at 56.7 million miles. The study used geographic and road-type alignment methods to make the comparison meaningful rather than simply averaging national crash statistics against a fleet that operates in specific urban corridors, controlling for factors like speed limits, intersection density, and typical traffic volumes.
Those 56.7 million miles were accumulated in Waymo’s existing service areas, where the company has had years to refine its perception stack, prediction models, and defensive driving policies. San Diego, Las Vegas, Tampa, and Denver represent new road environments with different traffic patterns, weather conditions, and driver behaviors. Whether the company’s crash-rate advantage holds in these cities is an open empirical question that the existing study cannot answer. Hills, coastal fog, tourist-heavy corridors, and snow all pose distinct challenges that the prior dataset only partially reflects.
Federal oversight adds another layer. NHTSA’s Standing General Order on crash reporting, designated SGO 2021-01, requires operators of Level 3 through Level 5 automated driving systems to report crashes to the agency. That mandate applies regardless of which state the vehicle operates in. As Waymo’s fleet fans out across four new metros, the volume of reportable incidents will grow, and the data will become publicly available through NHTSA’s reporting program. Residents in these cities and safety researchers alike will be able to track whether driverless performance in new markets matches the record compiled in older ones, and whether any new crash patterns emerge that correlate with local road design or weather.
Gaps in the regulatory record for Denver, Tampa, and Las Vegas
The strongest documentation exists for San Diego. The California DMV list, updated April 3, 2026, names Waymo among manufacturers authorized to test autonomous vehicles without a safety driver and specifies San Diego as an approved area. That is a verifiable, date-stamped regulatory record that ties the company’s operations to a defined geography and set of conditions.
For the other three cities, the evidence is thinner. Nevada’s DMV confirms its registry-based approach but no specific filing from Waymo for Las Vegas operations appears in the available sources. Florida’s statute provides broad legal authorization, yet no Tampa-specific deployment document has surfaced. Denver lacks any primary Colorado regulatory record in the current source set. In each case, the legal authority for operation exists in general law, but the detailed terms under which vehicles will run-such as time-of-day limits or special rules for school zones-are not yet visible to the public.
These gaps do not mean the expansion is unauthorized; they mean the paper trail is harder to follow. In California, residents can look up permits, approved zones, and updates through official channels such as the state portal. In Nevada, Florida, and Colorado, much of that transparency depends on voluntary disclosures from companies and ad hoc briefings from transportation agencies or city councils. For communities weighing the benefits of expanded mobility against concerns about safety and congestion, that difference in documentation can shape how much trust they place in early deployments.
As Waymo moves into San Diego, Las Vegas, Tampa, and Denver, the interplay between state law, federal reporting, and company data will determine not only where robotaxis can operate, but how quickly the public can judge their performance. The 56.7 million miles already logged offer a strong starting point for that conversation. The next phase-on unfamiliar streets under new rules-will show whether those safety gains are durable or narrowly tied to the places where the technology first took root.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
