Quick Answer
Nevada has authorized up to 7,000 commercial robotaxis for Clark County under three new permits, 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
- On August 20, 2026, the Nevada Transportation Authority approved Autonomous Vehicle Network Company permits for Tesla, Waymo, and Uber's subsidiary Aviari Services, authorizing up to 7,000 robotaxis in Clark County during the first 12 months: up to 5,000 for Tesla and up to 1,000 each for Waymo and Aviari
- Zoox began charging for driverless rides on the Las Vegas Strip on August 10, 2026, and Waymo opened paid rides to the public on September 14, 2026
- 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
- Nevada requires robotaxi companies to carry at least $1.5 million in liability coverage under NRS 706B.300, but does not require them to carry uninsured or underinsured motorist coverage for passengers
- Robotaxi app terms commonly contain arbitration clauses. Who booked the ride, which terms were accepted, and whether the rider opted out can decide whether a case is heard in court
Las Vegas is becoming the robotaxi capital of the United States. On August 20, 2026, the Nevada Transportation Authority unanimously approved Autonomous Vehicle Network Company permits for Tesla Robotaxi, LLC, Waymo LLC, and Aviari Services, LLC, an Uber subsidiary, authorizing up to 7,000 driverless vehicles in Clark County during the first twelve months. Tesla drew the largest share, up to 5,000 vehicles, though a Tesla engineer told Nevada regulators the company would be happy to reach roughly 2,500 within a year, as TechCrunch reported. 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.
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?
Update, September 19, 2026: Zoox began full commercial robotaxi service at Harry Reid International Airport on September 3. Tesla started charging for Cybercab rides in Austin on September 4, with Las Vegas among its next markets. Waymo opened paid rides to the public on September 14 and holds authority for up to 1,000 vehicles in Clark County. Uber's permit is held by its subsidiary Aviari Services, LLC.
Update, September 19, 2026: Corrected the combined permit total to 7,000 vehicles per the Nevada Transportation Authority's announcement and clarified that Uber's permit is held by its subsidiary Aviari Services, LLC. Added sections on Nevada's $1.5 million robotaxi insurance requirement under NRS 706B.300, the uninsured motorist coverage gap for passengers, arbitration clauses in robotaxi app terms, records retention under NRS 706B.220, and crashworthiness claims.
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, and on September 3 added full commercial service at Harry Reid International Airport. Zoox holds its own Autonomous Vehicle Network Company permit from the Nevada Transportation Authority. 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, opened paid driverless service to the public in Las Vegas on September 14, 2026, initially by invitation, with authority for up to 1,000 vehicles, 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. Paid Cybercab rides began in Austin on September 4, 2026, and Las Vegas is among the next markets. Uber received operating authority in the same round of approvals through its subsidiary Aviari Services, LLC, and dispatches partner-built vehicles from companies such as Motional through its platform. The three new permits together allow up to 7,000 driverless vehicles in the county, in addition to Zoox's existing permit. The permits do not by themselves authorize airport service. Each company needs separate authorization from the Clark County Department of Aviation to serve Harry Reid International Airport.
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 an Autonomous Vehicle Network Company permit issued by the Nevada Transportation Authority under NRS Chapter 706B. 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 DMV crash reports come from the testing rules in Chapter 482A, while paid passenger service is governed by the company's Autonomous Vehicle Network Company permit under Chapter 706B, which carries its own insurance requirement. Regulators will have records about the crash that hit you. Your lawyer should too.
That second chapter matters as much as the first. NRS Chapter 706B governs autonomous vehicle network companies, meaning businesses that connect paying passengers to fully autonomous vehicles. Under NRS 706B.300, a company must maintain at least $1,500,000 in coverage for bodily injury, death, and property damage in any one crash that occurs while providing transportation services, through a licensed insurer, a surplus lines placement, or an approved self-insurance program. Two details matter to injured people. First, the requirement is liability coverage. It pays when the robotaxi company is at fault. Second, the statute says nothing about uninsured or underinsured motorist coverage for passengers, a gap explained below.
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 through its subsidiary Aviari Services, LLC, 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. The evidence and liability principles for human against machine crashes are covered throughout this guide.
What If the Vehicle Had a Human Safety Driver?
Some autonomous vehicle deployments, especially test operations, keep a human safety driver in the vehicle whose job is to take over when the system encounters something it cannot handle. If that person failed to intervene when they should have, or intervened badly and caused the crash, the safety driver and their employer can share liability alongside the manufacturer and the operator. Courts are also still developing standards for a newer kind of product claim these cases raise: not a defective brake or airbag, but a defective decision, meaning an AI driving system that was poorly designed, inadequately tested, or deployed in conditions it was not built for.
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 operate under Autonomous Vehicle Network Company permits from the Nevada Transportation Authority and must carry at least $1.5 million in liability coverage.
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 If Another Driver Caused the Crash and Has Little or No Insurance?
This is the gap most riders do not know about. If a human driver hits your robotaxi and that driver is uninsured or carries Nevada's minimum limits, the robotaxi company's liability coverage does not automatically pay you, because the company did not cause the crash. Nevada law does not require robotaxi companies to carry uninsured or underinsured motorist (UM/UIM) coverage for passengers, and a company may self-insure. Whether any such coverage exists has to be confirmed in writing in every case. Your own auto policy is often the answer: UM/UIM coverage follows you as a person, including when you are a passenger in someone else's vehicle, and in Nevada it generally pays on top of the at-fault driver's limits. If you ride in robotaxis, check your own UM/UIM and medical payments limits now, before you need them.
Why Even a Small Share of Robotaxi Fault Matters
Nevada normally makes each defendant pay only its own percentage of fault under NRS 41.141. But the Nevada Supreme Court held in Buck v. Greyhound Lines, Inc., 105 Nev. 756, 783 P.2d 437 (1989), that the statute applies only where the injured person's own negligence is a genuine issue. A passenger who did nothing wrong falls outside it, and defendants can be held jointly and severally liable, meaning any one of them can be responsible for the full judgment. Claims based on a defective product are also excluded from the several-liability rule. In practice, if a robotaxi's own data shows it detected a hazard and failed to brake or evade the way a careful driver would have, even a minority share of fault can open the company's coverage to a passenger whose damages exceed the other driver's policy.
Did the Vehicle Protect You in the Crash?
A separate claim exists even when the robotaxi did nothing to cause the collision. Under product liability law, a vehicle must be reasonably crashworthy. Purpose-built robotaxis use new interior layouts, including facing seats, no steering column, and redesigned restraint and airbag systems, with limited real-world crash history. If a design defect made your injuries worse than they should have been, the manufacturer can be liable for those enhanced injuries regardless of who caused the crash. The vehicle itself is evidence and should be inspected before it is repaired or returned to service.
Did You Agree to Arbitration When You Downloaded the App?
Probably, if you used the app. Robotaxi and rideshare apps require users to accept terms of service, and those terms commonly require private arbitration instead of court and waive class actions. Here is where the four Las Vegas operators stood as of September 2026:
Tesla. Tesla's Robotaxi Terms of Service state that they apply to every rider, whether you requested the ride or rode as a guest. They send disputes to a single arbitrator under the American Arbitration Association's Consumer Arbitration Rules, bar class claims, and allow small claims court as an alternative. A rider may opt out within 30 days after accepting the terms, but only by mailing a letter to Tesla stating the rider's name, address, telephone number, email address, and intent to opt out.
Uber. Uber's U.S. Terms of Use contain an arbitration agreement and class action waiver, along with a section addressing autonomous vehicles provided by third parties. When a robotaxi ride is booked through Uber, a threshold question is whose terms govern a claim against the company that built and operates the vehicle.
Waymo. Waymo's rider terms, presented in its app in September 2026, send disputes to a single arbitrator under the JAMS Streamlined Arbitration Rules and bar class claims. A rider who starts arbitration pays JAMS filing fees capped at $250. A rider may opt out of arbitration within 30 days of first accepting the terms by emailing waymo-arbitration-optout@waymo.com with the rider's full name and a clear statement of intent to opt out. One provision deserves special attention: the terms state that any demand for arbitration must be made within one year of discovery of the claim or it is permanently barred. Nevada gives injury victims two years to sue, so a Waymo rider who waits could face an argument that the contract cut that time in half.
Zoox. Zoox's rider terms, presented in its app in September 2026, require binding individual arbitration before a single arbitrator under the JAMS Streamlined Arbitration Rules and waive class actions and jury trials. Before arbitration can begin, the terms require a written Notice of Dispute sent by certified mail to Zoox's legal department in Foster City, California, followed by a 45 day informal resolution period, with the statute of limitations tolled while that period runs. The terms also state that the arbitrator may not award punitive damages except where a statute permits them. Small claims court remains available, but the dispute resolution section presented at signup contains no opt-out provision.
An arbitration clause does not end the analysis. Key questions include who actually booked the ride; whether a guest who never opened the app can be bound by terms they never saw, which is a contested legal question; which version of the terms was in effect on the date of the ride; whether the terms allowed an opt-out period and whether you used it; and whether the clause reaches bodily injury claims at all. Do not delete the app or your account after a crash. The terms you accepted, and when you accepted them, are evidence. An attorney should review them before any claim is filed.
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.
Nevada law helps in one respect. Under NRS 706B.220, an autonomous vehicle network company must keep trip records, vehicle inspection records, complaint records, and records of each reported crash for at least three years. The statute does not list raw sensor footage or driving-system logs, which is why a specific preservation demand still has to go out immediately.
The data categories break down like this. The event data recorder captures speed, braking, and impact data, and in an autonomous vehicle it also records automation status, meaning whether the system or a human was driving in the seconds before impact. Perception logs show what the cameras, lidar, and radar detected, when they detected it, and whether the perception was accurate. Decision logs record what the driving system chose to do about what it saw, including a hazard it identified but failed to respond to. Remote monitoring records show whether a human operator watching the fleet had visibility of the situation and failed to act. And operational design domain records show the conditions the vehicle was engineered for, which matters when a crash happens outside them. Each category gets used differently in litigation, and each sits on a different retention clock.
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.
- Do not delete the robotaxi app or your account. Screenshot the terms of service and your ride history. Whether you are bound by an arbitration clause can depend on those records.
- Pull your own auto insurance declarations page. Your uninsured and underinsured motorist coverage and medical payments coverage may apply even though you were riding in a robotaxi.
- 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 opened paid rides to the public on September 14, 2026. The Nevada Transportation Authority has also authorized Tesla, Waymo, and Uber's subsidiary Aviari Services to field up to 7,000 commercial robotaxis in Clark County during the first 12 months of their permits.
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 under a Nevada Autonomous Vehicle Network Company permit and must carry at least $1.5 million in liability coverage, 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.
Who is liable if a Waymo, Tesla, or Zoox robotaxi hits me in Las Vegas?
For those three brands, the operator and the manufacturer are largely the same corporate family: Alphabet stands behind Waymo, Tesla runs its own robotaxi network, and Amazon owns Zoox. A ride dispatched through Uber can involve a separate vehicle owner, so both companies get named. In every case the claim proceeds against businesses with commercial insurance, not an individual driver.
Does insurance cover a robotaxi accident in Las Vegas?
It depends on who caused the crash. Nevada requires autonomous vehicle network companies to maintain at least $1.5 million in liability coverage under NRS 706B.300, which applies when the robotaxi company is at fault. If another driver caused the crash, that driver's insurance is primary, and Nevada does not require robotaxi companies to carry uninsured or underinsured motorist coverage for passengers. Your own auto policy's UM/UIM and medical payments coverage may apply even though you were a passenger. An attorney identifies every policy in play.
Can I still sue if I accepted the robotaxi app's terms of service?
Maybe. Robotaxi app terms commonly include an arbitration clause, which can move a claim out of court and into private arbitration. Tesla's published Robotaxi terms, for example, require arbitration, state that they apply to guests as well as the person who booked, and allow an opt-out only by mailed letter within 30 days of acceptance. Whether a clause binds you depends on who booked the ride, which version of the terms you accepted, whether you opted out, and whether the clause reaches injury claims. Keep the app and your account intact and have an attorney review the terms.
What if the driver who hit my robotaxi has no insurance?
The robotaxi company's required coverage is liability coverage, which pays when the company is at fault. Nevada does not require robotaxi companies to carry uninsured motorist coverage for passengers. Your own UM/UIM coverage follows you into a robotaxi and is often the main source of recovery in that situation, along with any claim that the robotaxi shared fault or failed to protect you in the crash.
The robotaxi did not cause the crash. Do I have any claim against the company?
Sometimes. If the vehicle's data shows it could have avoided or reduced the collision and did not, the company may share fault, and a fault-free passenger in Nevada may be able to recover the full judgment from any responsible defendant under Buck v. Greyhound Lines. Separately, if a design defect in the vehicle's seats, restraints, or airbags made the injuries worse, a product liability claim can exist regardless of who caused the crash.
See also: our Las Vegas Uber and Lyft accident page and our car accident page.