Hit By A Self-Driving Car In Las Vegas?

Las Vegas is one of the few American cities where you can be hit by a car that nobody was driving. Robotaxis and autonomous shuttles run real routes here, from the resort corridor along Las Vegas Boulevard to downtown and out toward the 215 Beltway, and the technology keeps spreading. That makes a self-driving crash a real and growing claim, not science fiction. If one hurt you, you are not the first person this has happened to, and you will not be the last.

Nevada wrote rules for these vehicles years ago, and the Nevada Department of Motor Vehicles is the state agency that oversees how they operate on public roads. That framework gives the companies behind these cars specific duties to meet. When they fall short and someone gets hurt, those broken duties become the spine of an injury case. We know where that line sits and how to show a jury when a company crossed it.

What trips people up is the instinct to treat this like a fender bender. It is not. The company that owns the car often responds with a polished claims process designed to settle you quietly, fast, and cheap, before you understand how many parties might owe you. Slow down. Talk to a lawyer first. This page walks through who pays, what the car recorded, the injuries we see, and what to do next.

This is where a self-driving crash case is won or lost. A robotaxi is covered in sensors: cameras facing every direction, radar, lidar that maps the world in three dimensions, and a computer logging every decision the software made. The vehicle quietly recorded what it saw, when it saw it, whether it braked, and how hard. In a normal crash you fight over fuzzy memories. Here, the truth is sitting on a server.

The problem is who holds that server. The company does. They can review the logs before you ever see them, and data gets overwritten on a cycle. That is why our first move is a preservation letter, a formal demand that the operator and the maker hold every byte of sensor and autonomy data tied to your crash. Send it late and the most important evidence in your case can be gone for good.

Once the data is locked down, it tells a story. It can show the car had a clear line of sight and a full second to stop and chose not to. It can show the software misread a crosswalk or a cyclist. It can also back you up when the operator claims you caused it. We pair that data with the basics that still matter: the scene photos, the Nevada crash report, the witness names, and your medical records. Build that file early and the company stops treating you like a rounding error.

The companies running these vehicles know they are on new legal ground, so they move fast to control it. Expect a representative to reach out quickly, sound genuinely sorry, and offer to make it easy. The first number they float is built to close your file before you know the full extent of your injuries or how many parties owe you. A signed release the first week is exactly what they want.

Their next play is the data. Because the logs live on their servers, they will frame what happened in the light that favors them, and they will lean on you to settle before any independent eyes review the raw sensor feeds. They may argue the car behaved reasonably and that you, the human, were the unpredictable one. That is why we demand the data and read it ourselves rather than taking their summary on faith.

They will also try to shrink the case by pinning fault on you under Nevada's comparative negligence rule, since every percentage of blame they shift cuts their bill. We push back with the record: the vehicle's own logs, the scene, the witnesses, and your treatment history. If part of the harm traces to a defective component, we keep the manufacturer in the case so no single defendant can hide behind another. For the broader picture on how crash claims work in Nevada, our main car accident page lays out the fundamentals.