Jack’s Got Your Back
Las Vegas Uber / Lyft Accident Lawyers
The same collision can be covered by a $1 million commercial policy, by a $50,000 per person rideshare policy, or only by the driver’s personal insurance, depending on whether the Uber or Lyft driver was offline, logged in and waiting, or carrying a passenger. That single variable, not the severity of the crash, often decides what your claim is worth and who fights to avoid paying it.
If you were injured in a Las Vegas Uber or Lyft crash, the most useful thing this page does is tell you which of those situations is yours and what actually moves your claim. Start with the route that matches you.
What You Need to Know
- The driver’s app status decides which policy pays. Nevada law (NRS 690B.470) sets the required insurance by whether the driver is providing transportation services or is only logged into the network and available for requests (the app-status windows the industry calls Periods 0, 1, 2, and 3). It sets no rideshare requirement at all for a driver who is offline. The period is where the coverage analysis starts, not where it ends: the required insurance may be provided through one policy or a combination of them (NRS 690B.470(3)), and a driver or company may carry more than the minimum.
- The “app on, no ride yet” gap is where claims get denied from both sides. In this window, the driver’s personal insurer often denies for “commercial use” while the rideshare company calls its own coverage contingent, leaving you with two denial letters pointing at each other, though the insurer providing the rideshare coverage may not require the personal policy to deny a claim first (NRS 690B.470(7)).
- The active-period coverage floor is now $1 million, down from $1.5 million. Nevada’s AB 523 (2025) lowered it, and the bill says the change does not apply to a cause of action that arose before October 1, 2025. A page or adjuster still quoting a flat $1.5 million is using the wrong figure for a cause of action arising on or after that date.
- Uber and Lyft have a vicarious-liability shield, and it is not the whole story. AB 523 says the company is not vicariously liable for an act or omission of a driver or passenger that harms a person or property, and that shield is not conditioned on the insurance it carries (NRS 706A.155(1)). The same section says it does not alter or preclude any other theory of liability against the company, or any duty of care the company itself owes, to the extent available and proven under law (NRS 706A.155(2)).
- Three different people read this page with the same question. A passenger, a third party hit by a rideshare driver, and the rideshare driver each get a different “whose insurance pays” answer, keyed to the same period grid.
- The proof is digital, and it disappears. App logs and trip data establish which period applied. Preserve them fast; Nevada’s deadline to file most injury claims is two years (NRS 11.190(4)(e)).
Find out what your case is worth
Free, confidential evaluation in as little as 5 minutes. Contact us today to speak to Jack personally.
- You pay nothing until we win
- Get an immediate call back. 24/7
- We do not sell or share your information
Over $500 Million in Verdicts & Settlements
Jack Bernstein stays personally involved in the cases his firm handles. We will investigate your claim and pursue any compensation that may be available under the facts and the law.
*Jack Bernstein has worked on the above cases during his career at this firm or another firm. Past results do not guarantee, warrant, or predict future cases.
See Case ResultsWhy hire Jack Bernstein Injury Lawyers?
Jack G. Bernstein, Esq. has been protecting the rights of injured victims and their families for over 40 years.
Speak to Jack about your caseJack and our case manager Traci always answered any questions we had about our case promptly and with great concern of our well being. Jack’s team starting with Dan, we felt like we had chosen the best attorney to settle our case and in the end we did.
We look forward to and confident of Jack’s representation of our next case.
Thank you so much
Sincerely Mark and Cecilia
$500 million+ recovered
More than 40 years of verdicts and settlements for injured people and their families. Past results do not guarantee your outcome.
Jack is personally involved
You are not a case number. Jack stays involved in your case, and you will always know who is handling it.
We know how insurance companies work
Uber and Lyft accidents can involve several insurance policies. We find every policy that applies to you.
Experts who strengthen your case
Trip records, app data and the driver’s history, secured early, plus doctors who document your injuries.
No fee unless we win
No upfront cost. We advance the expenses of your case, and you pay no attorney fee unless we win.
Free consultation, day or night
Call any time, 24 hours a day. Tell us what happened and you will get an honest answer about your case.
The coverage periods: the decision tool the app status controls
Nevada’s rideshare insurance rules live in NRS 690B.470. The statute itself does not use the words “Period 0, 1, 2, 3” (that is industry shorthand), but it does draw the exact lines the shorthand describes, based on whether the driver is “providing transportation services” or merely “logged into the digital network … and available to receive requests … but is not otherwise providing transportation services.”
Here is the grid, read as a timeline of who pays.
| Period | Driver’s app status | Coverage that applies (Nevada) | The catch |
|---|---|---|---|
| Period 0 | App off (driver is a private motorist) | The driver’s personal auto policy only; no rideshare coverage | The rideshare company will disclaim entirely. This is an ordinary car-accident claim. |
| Period 1 | App on, no ride accepted (“available”) | Contingent rideshare coverage: $50,000 per person / $100,000 per accident / $25,000 property (NRS 690B.470(1)(b), (d)) | The gap. Personal carrier may deny for commercial use; rideshare carrier calls its coverage contingent. This is where both sides point at each other. |
| Period 2 | Ride accepted, en route to pick up | $1,000,000 active-period policy (NRS 690B.470(1)(a)) | The high-limit policy is live, but the company will dispute exactly when “en route” began. |
| Period 3 | Passenger in the car | $1,000,000 active-period policy (NRS 690B.470(1)(a)) | The strongest coverage position. Passengers are almost always here. |
Bottom line: Start with the period; it is what sets the coverage Nevada requires. The single most consequential fact in a Las Vegas rideshare claim is not how badly you were hurt. It is what the driver’s app was doing when the cars met.
A note on the dollar figures, because they recently changed. The active-period floor (Periods 2 and 3) used to be $1.5 million. Nevada’s Assembly Bill 523 (2025) lowered it to $1 million. The enrolled bill text makes the change explicit, amending NRS 690B.470(1)(a) to read “not less than [$1,500,000] $1,000,000,” and section 4 of the bill provides that its amendatory provisions do not apply to a cause of action that arises before October 1, 2025. So the floor that governs depends on when your claim arose: $1.5 million for a cause of action arising before October 1, 2025; $1 million on or after. Any source quoting a flat $1.5 million today is citing a number that no longer governs a cause of action arising on or after that date.
What this means for you: if your cause of action arose before October 1, 2025, the higher floor still applies to it, because the bill’s amendatory provisions do not reach a cause of action that arose before that date. If yours arose on or after it, plan around the $1 million figure and, for a serious injury, look hard for the additional layers below, because $1 million can be exhausted fast in a catastrophic or multi-victim crash.
The period 1 gap: where both insurers deny
The “app on, no ride accepted” window is the single most contested situation in Nevada rideshare claims, and it is worth understanding before it happens to you.
Here is the mechanism. The driver is logged in and waiting. A crash occurs. The driver’s personal auto insurer learns the car was being used for Uber or Lyft and denies the claim, invoking a commercial-use or “livery” exclusion. The rideshare company’s insurer responds that its Period-1 coverage is only contingent: it applies, the carrier argues, only after the personal policy pays, or only if the driver was properly logged in within the coverage window. The first of those arguments runs against NRS 690B.470(7), which bars an insurer providing transportation network company insurance from requiring the driver’s personal policy to deny a claim before the rideshare coverage responds. The result is two denial letters that each point at the other carrier.
That outcome is in tension with what NRS 690B.470 can be argued to require. The statute says the rideshare company’s policy must step in as primary when the driver’s coverage “lapses” or “fails to meet the requirements” (NRS 690B.470(4)). Two open questions sit inside that leverage, and both are arguments a plaintiff has to press, sometimes in litigation: first, subsection (4) is written to apply “during any period in which the driver … is providing transportation services,” so a Period-1 claimant must argue the primary-coverage mandate reaches the “logged in but waiting” window at all; and second, that a personal-policy denial for commercial use is the kind of “failure to meet the requirements” the statute means. Neither is settled law, but together they are the statutory hook for forcing the contingent coverage to respond.
Experienced rideshare attorneys treat the Period-1 denial not as the end of a claim but as a predictable opening move: the carriers are leveraging public confusion about app status and coverage triggers, and the response is to nail down the digital app log, then invoke the statute’s primary-coverage mandate directly. What this means for you: a denial letter in this window is not a verdict on your claim. It is the start of a coverage fight, and the contingent limits ($50,000 / $100,000 / $25,000) are low enough that finding every other available layer matters even more than usual. The deeper mechanics of the dual-denial (the exact exclusion language, the timing disputes, the denial-letter patterns) are covered in detail in Uber’s Period 1 gap and why coverage gets denied when the app is on.
Not sure which rules apply to your ride?
You do not need to know whether your crash counts as rideshare, a taxi, or a shuttle before you call. Tell us which vehicle was involved and Jack will tell you honestly which rules apply and whether it is a case worth bringing.
Free consultation · No fee unless we win · Available 24/7
The independent-contractor shield, and the hole AB 523 left in it
Uber and Lyft have long maintained that their drivers are independent contractors, not employees. That position matters because it is the foundation of a liability shield: if the driver is not an employee, the companies argue, they are not responsible for the driver’s negligence under ordinary respondeat superior (an employer’s liability for an employee’s on-the-job conduct).
AB 523 went further and wrote a shield into statute. It added NRS 706A.155, which states that a transportation network company “is not vicariously liable for any act or omission of a driver or passenger that harms a person or property under any theory of liability or duty of care.” The statute puts no insurance condition on that shield, and it reaches causes of action arising on or after October 1, 2025. In plain terms: you generally cannot hold Uber or Lyft responsible merely because their driver caused the crash.
But the same section does not close every door. It expressly provides that the shield “does not alter or preclude any other theory of liability against a transportation network company … to the extent available and proven under law.” That is a savings clause rather than a list: it names no claim and creates none, and it leaves another theory standing only so far as that theory is available and can be proven. What it does mean is that the vicarious-liability bar is not the end of the analysis. Whether anything about the company’s own conduct supports a claim on your facts is a question for your attorney.
Bottom line: AB 523 closed the front door: you cannot hold Uber or Lyft liable merely because its driver was at fault. By its own terms it did not alter or preclude any other theory of liability against the company, to the extent one is available and proven under law. So the question after AB 523 is what, if anything, the company itself did.
The doctrinal playbook for piercing a contractor shield (the right-to-control analysis, the negligent-hiring and ostensible-agency theories) is laid out for a parallel context in piercing the independent-contractor shield in delivery-van cases. The structure of the argument transfers; the rideshare-specific wrinkle is that AB 523 bars the vicarious route outright (NRS 706A.155(1)), while its savings clause leaves any other available theory unaltered (NRS 706A.155(2)).
UM/UIM: the recovery layer most people never check
There is a coverage layer that frequently goes unexamined in rideshare claims: uninsured and underinsured motorist coverage (UM/UIM). It pays your damages when the at-fault driver has no insurance or not enough, which matters because Nevada has a large uninsured-driver population, and a $1 million active-period policy can be exhausted by a single catastrophic injury.
NRS 690B.470(6) expressly allows a rideshare insurance policy to include UM/UIM coverage, but it does not require it, and whether a given rideshare company’s policy carries UM/UIM in Nevada has become a moving target. So this is a layer to investigate, not assume. There are usually two places to look: whether the rideshare company’s policy in force at the time included UM/UIM, and whether your own personal auto policy’s UM/UIM applies to you as a passenger or pedestrian. Under NRS 687B.145(2), UM/UIM coverage lets you recover from your own insurer, up to your own limits, the damages that exceed the bodily-injury limits carried by the at-fault owner or operator. Whether limits from more than one policy can be combined is set by the policy language: NRS 687B.145(1) lets a policy cap the total recovery at the highest single applicable limit and prorate between the coverages, but only if that limitation is in clear language and prominently displayed, and the limitation is void if the insured bought separate coverage on the same risk and paid a premium calculated for full reimbursement.
What this means for you: if the at-fault driver was uninsured or underinsured, do not assume the rideshare company’s liability policy is the only money on the table. Your own UM/UIM coverage may apply even though you were a passenger in someone else’s car, and whether limits from more than one policy can be combined turns on the policy language (NRS 687B.145(1)), a recovery path competitors routinely skip and adjusters have no incentive to mention.
If you were a passenger in the Uber or Lyft
As a passenger, you are in the strongest coverage position, because you were almost certainly in Period 3: passenger in the car, with the $1 million active-period policy live (for crashes on or after October 1, 2025). A passenger is also rarely the one blamed for the crash, which usually keeps the comparative-fault fight out of your claim, though a carrier can still argue your own conduct played a part. Any share of fault assigned to you reduces what you recover as long as your negligence was not greater than the negligence of the defendant, or the combined negligence of the defendants you are suing; if your share is found greater than theirs, you recover nothing.
Two complications are common. First, the rideshare driver may not be the one at fault (another vehicle may have caused the crash). When that happens your recovery may run against the other driver’s insurance first, with the rideshare policy and any UM/UIM behind it, so all the layers above are in play. Second, you may be a tourist. If you were visiting Las Vegas, you can pursue the claim under Nevada law even after you fly home, and a Nevada crash is generally governed by Nevada law, because the state where the injury happened ordinarily has the most significant relationship to the case (General Motors Corp. v. Eighth Judicial Dist. Ct., 122 Nev. 466, 134 P.3d 111 (2006)). That is a presumption, not an absolute rule, but for a typical visitor hurt by a Nevada driver or business it points to Nevada law and Nevada’s two-year deadline. The out-of-state-plaintiff issues (coordinating evidence and treatment from another state, which state’s law governs a specific issue) are handled at depth on the Las Vegas tourist injury page.
The catch: your strong coverage position is real, but it does not collect itself. The rideshare company’s claims process is built to settle quickly and for less, and the period and at-fault analysis still have to be proven before anyone discusses value.
The first 72 hours: preserve the proof before it disappears
The evidence that proves which period applied is almost entirely digital, and the rideshare company controls most of it. App logs, trip timestamps, GPS data, and driver-status records are what establish whether the driver was offline, available, or carrying a passenger, and that data does not sit around indefinitely.
If the crash just happened:
- Screenshot everything in the app now: If you were the passenger, your trip receipt, the driver’s name and vehicle, and the pickup/drop-off times are in your own account; capture them before anything changes.
- Photograph the driver’s screen if it is safe: A visible app status (or a dark, logged-off screen) at the scene is direct evidence of the period.
- Get names and numbers of witnesses, and note any nearby business or traffic cameras on the Strip or the surrounding streets.
- Preserve, don’t volunteer: Decline to give a recorded statement to any insurer until you understand which period and which policy are in play; an adjuster’s early “just checking on you” call is an evidence-gathering event.
The reason speed matters is structural: a formal preservation demand to the rideshare company is what freezes the app and trip data before routine retention cycles put it out of easy reach. What this means for you: the difference between a provable period and an unprovable one is often made in the first days, and Nevada’s two-year deadline to file most injury claims (NRS 11.190(4)(e)) is the outer limit, not a reason to wait.
How fault affects what you recover
Nevada follows modified comparative negligence under NRS 41.141. You can still recover as long as your share of fault is not greater than the combined negligence of everyone you are seeking recovery from; cross that line and recovery is barred. (The statute does not contain a literal “51%”; that figure is the common shorthand for the “not greater than the combined” rule, and Nevada weighs your fault against all defendants combined, not one at a time.) Your recovery is then reduced in proportion to your share of fault.
This matters in rideshare cases because comparative fault is a lever the carriers pull. Inflating a passenger’s or third party’s supposed fault is one way to reduce or defeat a claim. What this means for you: an adjuster’s suggestion that you were partly to blame is not the last word; how fault is actually apportioned among multiple drivers and carriers is a contested question, and on a serious claim it is worth contesting.
Frequently asked questions
Have questions about your case?
Every Uber or Lyft accident case is different. These answers cover the general rules; what applies to you depends on the facts.
Call us any time, 24 hours a day, and we will go through the specifics with you. It is free, and there is no obligation.
(702) 633-3333 Free consultation · Available 24/7 Or send us the details onlineDoes Uber or Lyft Always Have a $1 Million Policy?
No. The $1 million active-period policy applies only when the driver has accepted a ride or has a passenger in the car (Periods 2 and 3). When the driver is logged in but waiting (Period 1), the required rideshare coverage is far lower: $50,000 per person, $100,000 per accident, $25,000 property. When the app is off (Period 0), there is no rideshare coverage at all. And for a cause of action that arose before October 1, 2025, the active-period floor was $1.5 million, not $1 million.
What Is the Period 1 Gap?
Period 1 is the window when the driver’s app is on but no ride has been accepted. In a crash during this window, the driver’s personal insurer often denies the claim for commercial use, while the rideshare company calls its coverage contingent, so an injured person can receive denials from both carriers. Nevada law does not let the rideshare company’s insurer wait behind that denial: an insurer providing transportation network company insurance may not require the driver’s personal policy to deny a claim before the rideshare coverage responds (NRS 690B.470(7)). Getting both carriers to honor that often still takes a coverage fight.
Can I Still Sue Uber or Lyft After AB 523?
Not for the driver’s negligence alone. AB 523 added NRS 706A.155(1), which bars vicarious liability against a transportation network company for an act or omission of a driver or passenger that harms a person or property, for causes of action arising on or after October 1, 2025. The same section says it does not alter or preclude any other theory of liability against the company, or any duty of care the company itself owes, to the extent available and proven under law. It does not name those theories, so whether one fits your facts is a question for a lawyer.
I Was Visiting Las Vegas. Can I Still File After I Go Home?
Yes. A crash that happened in Nevada is generally governed by Nevada law and can be pursued here even after you return home. Nevada’s deadline to file most injury claims is two years from the injury (NRS 11.190(4)(e)), so it is worth preserving evidence and getting advice before you leave the state.
How Do I Prove Which Period the Driver Was In?
Through the digital record: app logs, trip timestamps, GPS data, and driver-status records, plus your own trip receipt if you were the passenger and a photo of the driver’s screen if you could safely take one. Because the rideshare company controls most of that data and it is subject to routine retention cycles, a prompt preservation demand is what keeps it available.
Related reading
We will contact you immediately.
The consultation is free, confidential, and available now. Tell us what happened. We will tell you where you stand.
Call Now 24/7/365(702) 633-3333Find out what your case is worth
Free, confidential evaluation in as little as 5 minutes. Contact us today to speak to Jack personally.
- You pay nothing until we win
- Get an immediate call back. 24/7
- We do not sell or share your information







