Las Vegas Lyft and Uber Accident Lawyer, Rideshare Claims

Las Vegas Lyft Uber accident lawyer rideshare phone

Las Vegas has one of the highest per-capita rideshare-trip densities in the United States. The Strip-to-airport corridor, the resort-to-resort late-night runs, and the conference-and-convention surge cycles produce a volume of Lyft and Uber activity that translates directly into a steady caseload of rideshare-involved crashes. The cases come in three flavors: the passenger injured during a ride, the third-party driver or pedestrian hit by a rideshare car, and the driver themselves injured by another vehicle. Each flavor has a different insurance framework and a different liability strategy.

This guide explains the Nevada Transportation Network Company framework under NRS 706A, the three-period insurance structure that every rideshare claim turns on, the gaps that can leave injured parties uncovered, and how to determine which insurance layer applies to a specific crash.

Nevada Rideshare Regulation, NRS 706A

Nevada regulates transportation network companies (Uber, Lyft, and any other app-dispatched ride service) under NRS Chapter 706A. The framework establishes minimum insurance, driver background-check standards, vehicle safety inspection requirements, and the conditions under which a TNC driver is considered “operating” for liability purposes.

The Nevada Transportation Authority enforces the regulatory framework, and Lyft and Uber each maintain operating licenses with the state. The TNC must carry the statutorily required coverage on every active driver at all times, and the coverage layering changes based on the driver’s app status.

The Three-Period Insurance Framework

Every rideshare claim in Nevada hinges on which “period” the driver was in at the moment of the crash. The periods are defined by the app status.

Period 0, App Off

The driver is not logged into the app. The driver’s personal auto insurance is the only coverage available. The TNC has no liability. For practical purposes, Period 0 cases are ordinary auto-accident cases with no rideshare angle.

Period 1, App On, No Ride Accepted

The driver is logged into the app but has not accepted a ride request. The TNC provides contingent liability coverage of at least $50,000 per person, $100,000 per accident, and $25,000 property damage under NRS 706A.190. The driver’s personal policy may exclude this period entirely because most personal policies disclaim coverage during livery operation.

Period 1 is the gap zone. Many serious injuries that happen during Period 1 are funded only by the TNC’s contingent layer, which is dramatically lower than the Periods 2-3 coverage.

Period 2, Ride Accepted, En Route to Passenger

The driver has accepted a ride request and is en route to the pickup location. The TNC’s primary liability coverage activates at $1 million per accident under NRS 706A.190. The driver’s personal policy is typically excluded during this period as well, so the TNC million-dollar layer is the available coverage.

Period 3, Passenger On Board

The driver has a passenger in the car. The TNC’s $1 million per-accident primary coverage is active, plus uninsured/underinsured motorist coverage of $1 million under NRS 690B.020. Period 3 cases have the deepest available coverage of any rideshare scenario.

How to Determine the Period

The single most important early step in a Nevada rideshare case is documenting the period the driver was in at the moment of the crash. Lyft and Uber both maintain backend records of driver app status to the second. The records are accessible through a subpoena to the TNC, and the period determination cascades into which insurance carrier is on the claim.

The plaintiff’s counsel typically serves a written preservation request on the TNC within the first week of the engagement, naming the driver’s app-status logs, the trip-acceptance records, the GPS track, the passenger pickup time, and the trip-end time. These records are preserved digitally and do not roll off, but the preservation request creates a written record that becomes important if a discovery dispute develops later.

Common Rideshare Crash Scenarios in Las Vegas

Strip-to-airport runs at McCarran (Harry Reid) International Airport are the highest-volume route for Vegas rideshare activity. The pickup zones at terminal curbsides produce a recurring set of curbside-collision and pickup-zone pedestrian incidents.

Late-night Strip-to-Strip runs (resort to resort, club to club) cluster on Las Vegas Boulevard between Tropicana and Sahara. Driver fatigue, alcohol-impaired passengers, and the dense rush of cross-walk activity produce a recurring crash mix.

Convention surge runs during major events (CES, World of Concrete, Magic) produce a 3x to 5x ride volume increase that some drivers manage with extended shifts, leading to fatigue-related crashes that often qualify for the larger TNC coverage layer.

Driver-passenger assault cases, a separate category from collision cases, are handled by the firm but follow a different framework involving criminal restitution, civil negligent-hiring claims, and the TNC’s evolving safety-record policies. These cases are typically initiated through the same intake but require specialized representation.

The Personal Policy Exclusion Problem

Standard Nevada personal auto policies exclude livery and commercial use. When a rideshare driver is in Period 1, 2, or 3, the driver’s personal policy will typically deny coverage on the rideshare-related portion of any claim. Some specialty carriers offer rideshare endorsements that fill the gap, but coverage is by no means universal.

The gap matters most in Period 1, where the TNC’s contingent coverage is significantly lower than the personal policy limits would be. A serious Period 1 injury can quickly exceed the $50,000-per-person contingent limit, leaving the injured party to look at the driver’s personal assets if the personal carrier denies coverage.

Damages Available

Nevada plaintiffs recover the standard categories of compensatory damages: past and future medical, lost wages and earning capacity, pain and suffering, and mental anguish. Punitive damages under NRS 42.005 apply where the at-fault driver acted with conscious disregard, including DUI cases, hit-and-run cases, and cases involving documented driver misconduct.

For fatal rideshare crashes, NRS 41.085 governs the wrongful death framework. Heirs recover grief, loss of consortium, and pecuniary loss. The estate recovers pre-death pain and suffering plus funeral expenses.

Statute of Limitations

NRS 11.190(4)(e) imposes a two-year limit on personal injury claims from the date of the accident. The wrongful death limit is also two years from the date of death.

What the Rideshare Carriers Will Argue and How Each Argument Is Answered

A Lyft or Uber crash generally puts two or three adjusters on the file at once, and each of them has a financial reason to push the loss toward someone else. The positions below come up in most Nevada rideshare claims, along with how a trial firm meets each one.

The first argument is almost always about the period. The commercial carrier will read the app data in the way that places the driver in the lowest coverage layer it can support, and will sometimes lean on the driver’s recollection rather than the timestamped record. The answer is the record itself. The trip-acceptance time, the GPS track, and the pickup and drop-off times are pulled through the preservation request and, where needed, a subpoena, and the period is fixed from the data rather than from memory. A driver who says the ride ended a block before the collision is answered by the trip-end timestamp, not by debate.

The second argument is that the driver is an independent contractor, so the company bears no responsibility for what happened behind the wheel. The label matters less than the carriers suggest. The insurance obligations under NRS 706A follow the driver’s app status, not whether the driver is on the company’s payroll. The company’s policy is on the risk whenever the app placed the driver in an active period, and where the facts support it, a separate claim for negligent screening or retention of a driver with a documented history can be brought regardless of classification.

The third argument shifts fault to the injured person. Nevada applies a modified comparative negligence rule, and an injured person whose share of fault exceeds the combined fault of everyone else recovers nothing, while a smaller share reduces the recovery in proportion. Carriers use this to argue that a passenger distracted the driver or was intoxicated, or that a pedestrian at a Strip pickup zone stepped out against the signal. In most Nevada cases a passenger’s conduct has no causal link to a collision between two vehicles, and the argument is answered by keeping the focus on what actually caused the crash. Nevada law also generally bars the use of a passenger’s seatbelt non-use as evidence of negligence in a civil case, so the belt argument is usually a dead end for the carrier.

The fourth argument is the handoff. When another motorist caused the crash, the rideshare carrier will point the passenger toward that driver’s policy and step back. The answer depends on the period. In a Period 3 case the rideshare policy carries its own uninsured and underinsured motorist layer, so if the at-fault driver has minimum coverage or none at all, the passenger’s claim does not end at that driver’s limits. The passenger’s own auto policy may also respond through its uninsured motorist coverage, and it is put on notice at the same time as the commercial carriers rather than discovered late.

The last argument is delay. Adjusters on rideshare files often wait for the injured person to finish treating, then question every gap in the record. The answer is a treatment history documented from the first visit and a claim file built while the records are fresh, not assembled after the fact.

How the Firm Approaches Rideshare Cases

The Bourassa Law Group approach starts with period determination on day one. A written preservation request goes to the TNC immediately, locking the driver’s app-status records. The driver’s personal policy is identified, and the carrier put on notice. The TNC’s coverage layer is identified, and the carrier put on notice. An accident reconstruction is commissioned where the crash dynamics are contested. Treating physician relationships are documented from the start. Representation is contingency-based.

For broader Nevada catastrophic injury context, see our Las Vegas catastrophic injury lawyer page. For the federal motor carrier framework, see FMCSA federal regulations.

The Three Insurance Periods That Decide a Rideshare Claim

What makes a Lyft or Uber crash different from an ordinary car wreck is that the available insurance changes depending on what the driver was doing at the exact moment of the collision. Coverage falls into three periods, and which one applies can swing a claim by a wide margin. When the app is switched off and the driver is using the car for personal reasons, only their own auto policy is in play. When the app is on and the driver is waiting for a ride request, the rideshare company provides a more limited layer of coverage that fills gaps in the driver’s personal policy. Once the driver has accepted a trip and is on the way to the rider, or has a passenger in the car, a much larger commercial policy applies, with up to one million dollars in liability coverage standing behind the trip. Because the company has every reason to argue the driver was in a lower-coverage period, pinning down the trip status through app records and ride data is often the most important early step in a rideshare case. Getting that timeline right is what determines whether an injured person is reaching for a small personal policy or the full commercial coverage meant to protect riders and the public.

Related Reading

• Las Vegas Bus Accident Lawsuits

• Las Vegas Spinal Cord Injury Lawyer

Related Posts

Free Case Evaluation

The evaluation is FREE! You do not have to pay anything to have an attorney evaluate your case.