Quick Answer
Nevada has authorized up to 8,000 commercial robotaxis for Clark County, and Zoox and Waymo already carry paying passengers in Las Vegas. When a driverless taxi causes a crash, the claim runs against companies, not a driver: the fleet operator, the manufacturer, or both. Nevada applies its standard negligence, product liability, and comparative fault rules, and the evidence that decides the case is data the company controls. Preservation must begin within days.
Key Takeaways
- In August 2026 the Nevada Transportation Authority cleared Tesla, Waymo, and Uber to operate up to 8,000 commercial robotaxis in Clark County over the following 12 months
- Zoox began charging for driverless rides on the Las Vegas Strip on August 10, 2026, and Waymo also runs a paid driverless service in the city
- Tesla staged the launch event for its production Cybercab, a two-seat robotaxi with no steering wheel or pedals, on September 3, 2026
- With no driver to sue, liability runs to the fleet operator and the manufacturer under Nevada negligence and product liability law
- Nevada was the first state in the nation to regulate autonomous vehicles (NRS Chapter 482A, enacted 2011), and its comparative fault rule (NRS 41.141) applies to robotaxi crashes
- The evidence that decides these cases lives on company servers under retention schedules you do not control. Preservation demands must go out immediately
Las Vegas is becoming the robotaxi capital of the United States. In August 2026 the Nevada Transportation Authority approved permits for Tesla, Waymo, and Uber to run commercial robotaxi fleets in Clark County, authorizing up to 8,000 driverless vehicles over the following twelve months. Tesla drew the largest share, roughly 5,000 permits, and told state regulators it expects about 2,500 vehicles in service within the year. Days before that approval, Amazon’s Zoox became the first company to charge the public for driverless rides on the Strip. And on September 3, Tesla staged the launch event for its production Cybercab, a purpose-built two-seat robotaxi with no steering wheel and no pedals, with Las Vegas infrastructure already in its filings.
Thousands of vehicles with empty driver seats are joining the busiest tourist corridor in America. That raises a question personal injury law has never had to answer at this scale: when a robotaxi hits you, or crashes with you inside it, who pays?
Which Companies Are Operating Robotaxis in Las Vegas Right Now?
Zoox, owned by Amazon, has charged for rides on and around the Strip since August 10, 2026. Its vehicles are purpose-built pods with no manual controls at all, operating under a federal exemption granted in July 2026 from rules that normally require steering wheels and pedals. Waymo, owned by Alphabet, also operates a paid driverless service in Las Vegas and runs robotaxis in more than a dozen American metros. Tesla holds the largest Nevada permit allocation and is bringing its robotaxi network and the new Cybercab to Clark County. Uber received operating authority in the same round of approvals and dispatches partner-built vehicles through its platform. The combined authorization allows up to 8,000 driverless vehicles in the county.
Which Nevada Laws Govern Robotaxis?
Nevada enacted NRS Chapter 482A in 2011, the first autonomous vehicle statute in the country. Under the chapter, an autonomous vehicle is one that drives itself at SAE Level 3, 4, or 5, and a fully autonomous vehicle operates at Level 4 or 5 (NRS 482A.030, 482A.036). Commercial robotaxis fall in the fully autonomous category.
Three points in the chapter matter most after a crash. First, a fully autonomous vehicle may legally operate with nobody inside only if it can reach what the statute calls a minimal risk condition when its driving system fails, meaning it can bring itself to a reasonably safe stop (NRS 482A.070, 482A.080). A vehicle that failed to reach that safe stop in a crash gives the injured person strong support for a negligence claim against the operator. Second, testing an autonomous vehicle on Nevada highways requires proof of five million dollars in insurance or an equivalent bond (NRS 482A.060), and companies carrying paying passengers additionally hold commercial passenger carrier authority from the Nevada Transportation Authority, which issued the 2026 robotaxi permits. Third, crashes during testing that cause injury or more than 750 dollars in damage must be reported to the Nevada DMV within 10 business days (NRS 482A.095), and federal reporting to NHTSA exists on top of that. One distinction matters when reading the chapter: the five million dollar figure and the crash reports above come from the testing rules, while commercial passenger service is governed by the NTA certificate, and insurance for carrying paying passengers is set under that authority rather than the testing bond. Regulators will have records about the crash that hit you. Your lawyer should too.
Who Is Liable When a Robotaxi Causes a Crash?
The Fleet Operator
The company that put the vehicle on the road and collects the fare is the first defendant to examine. Operator liability follows ordinary Nevada negligence principles: deploying vehicles in conditions they were not designed to handle, inadequate remote monitoring, poor maintenance of sensors and hardware, and dispatch decisions that placed a vehicle somewhere it should not have been. There is no individual driver to blame, so the operating company answers for how its fleet behaved.
The Manufacturer and the Software Developer
Nevada product liability law applies to the robotaxi and its systems as it would to any other vehicle. Defects in sensors, braking hardware, or the automated driving system itself can make the manufacturer or developer liable. One detail matters here: Nevada does shield an original manufacturer from liability, but only where an unauthorized third party converted the vehicle or modified its driving system and the defect came from that modification (NRS 482A.090). A company that designs, builds, and operates its own robotaxi cannot hide behind that shield. For Zoox, Waymo, and Tesla robotaxis, the manufacturer and the operator are largely the same corporate family, which concentrates responsibility rather than diluting it. Vehicles dispatched through Uber run on a different model, covered next.
Uber and the Platform Model
Uber holds operating authority from the Nevada Transportation Authority in the 2026 approvals, but Uber does not build vehicles. A robotaxi dispatched through Uber's platform is another company's vehicle carrying Uber's passenger. That splits the roles: the manufacturer of the vehicle and its driving system is one entity, the platform that dispatched it is another, and each has an incentive to point at the other after a crash. Expect Uber to argue that it is a dispatch platform rather than the operator of the vehicle. The right approach in that scenario is to name both companies and let the vehicle's own data sort out where fault sits.
Another Human Driver
Many robotaxi crashes will involve a human-driven vehicle that cut the robotaxi off, rear-ended it, or forced it into an evasive move. Nevada comparative fault applies across everyone involved, so a human driver can carry primary or shared fault alongside the companies. Our guide to self-driving car accident liability breaks down how fault gets divided among manufacturers, operators, and human drivers in more detail.
What If You Were a Passenger in the Robotaxi?
Passenger cases are the cleanest robotaxi claims. A passenger does not steer, brake, or make any driving decision, so fault arguments against passengers rarely exist. Claims can proceed against the robotaxi company and against any other driver involved in the collision. These companies hold passenger carrier authority from the Nevada Transportation Authority and carry commercial insurance sized for that role.
The dynamics resemble rideshare passenger cases, where our office already handles layered commercial coverage questions, with one difference: the company cannot point at an independent contractor driver, because there is none. See our rideshare accident practice page and our guide to Strip rideshare crashes for how passenger claims and commercial coverage interact in Las Vegas.
What Evidence Decides a Robotaxi Case?
A robotaxi records nearly everything: continuous camera and sensor footage, perception logs showing what the system detected, decision logs showing how it responded, remote assistance records, and event data recorder captures. That evidence usually proves exactly what happened. It also sits entirely on company servers, under retention schedules the injured person does not control and cannot see.
Data preservation is urgent. Company systems overwrite routine operational data on rolling schedules. Under current NHTSA reporting guidance, the most severe automated driving system crashes must be reported federally within five days, and regulators receive summaries, but the underlying footage and logs belong to the company. A formal preservation demand should go out within days of any robotaxi crash, before routine retention cycles erase the record. Sending that demand is one of the first things we do in every case involving corporate-controlled evidence.
For a full breakdown of the data categories inside an autonomous vehicle and how each one gets used in litigation, see our companion piece on self-driving car accident evidence.
How Does Comparative Fault Work Against a Machine?
Nevada follows modified comparative negligence under NRS 41.141. If you are 50 percent or less at fault, you recover with a proportional reduction. At 51 percent, you recover nothing. Robotaxi companies know this math, and their first move in a disputed crash is to mine their own sensor data for fault arguments: the pedestrian stepped off the curb, the driver turned across the lane, the cyclist ran the light.
The same data cuts the other way. Perception logs can show the system detected you with time to stop and reacted late, or never classified you correctly at all. The company’s own record is often the strongest proof against it, which is another reason preservation speed decides these cases. Our explainer on Nevada comparative negligence covers how fault percentages change recoveries.
What Should You Do After a Robotaxi Crash in Las Vegas?
- Call 911 and tell the dispatcher a driverless vehicle is involved. Get a police report that records the company and the vehicle unit number.
- Photograph the vehicle from several angles, including the roof and side sensor arrays, its markings, and the full scene.
- If you were a passenger, screenshot the trip screen in the app right away, including the time, route, and vehicle identifier.
- Note any conversation with the company’s remote support through the vehicle, including names and times.
- Seek medical attention the same day, even if you feel fine at the scene.
- Do not give a statement to the company, its insurer, or its representatives before speaking with an attorney.
- Contact an attorney immediately so a preservation demand reaches the company before its systems overwrite the data.
Hit by a Driverless Vehicle, or Hurt Riding in One?
The evidence that proves your case sits on a company server right now. A free consultation takes 15 minutes and puts preservation in motion the same day.
Get Free ConsultationFrequently Asked Questions
Are robotaxis already operating in Las Vegas?
Yes. Zoox began charging for driverless rides on August 10, 2026, and Waymo also operates a paid driverless service in the city. The Nevada Transportation Authority has authorized Tesla, Waymo, and Uber to field up to 8,000 commercial robotaxis in Clark County over the following 12 months.
Who do I sue if a robotaxi hits me and there is no driver?
The claim runs against companies rather than a person: the fleet operator that deployed the vehicle, the manufacturer or developer of the vehicle and its systems under product liability law, and any human driver of another vehicle who contributed. The vehicle’s own data identifies which parties bear responsibility.
Can a passenger in a robotaxi file an injury claim?
Yes, and passenger claims are typically strong because a passenger carries no fault for the driving. Claims can proceed against the robotaxi company, which operates as a regulated passenger carrier with commercial insurance, and against any other involved driver.
Does Nevada comparative fault law apply to robotaxi accidents?
Yes. NRS 41.141 applies. Recovery is reduced by your percentage of fault and barred above 50 percent. Expect the company to argue fault using its own sensor data, and expect a capable attorney to use that same data against it.
How quickly must evidence be preserved after a robotaxi crash?
Within days. Footage and logs live on rolling retention systems. A formal preservation demand sent immediately after the crash is the difference between proving what the vehicle saw and arguing about it.
See also: Who Is Liable When a Self-Driving Car Causes an Accident? for the deeper evidence breakdown, our car accident practice page, and Direct Attorney Access on why the attorney personally handling preservation matters in data-heavy cases.