Home › Resources › Uber/Lyft Accident in Nevada or Utah

Uber/Lyft Accident in Nevada or Utah: Whose Insurance Pays?

By the Apis Felix Law Trial Team — Licensed in Nevada & UtahAttorney-reviewed — July 4, 2026

Uber and Lyft crashes in Las Vegas, Salt Lake City, or anywhere else in Nevada or Utah raise a question that doesn't come up in an ordinary car accident: which insurance policy actually applies? The answer isn't fixed — it shifts depending on exactly what the driver's app was doing in the seconds before the crash. Getting this right early is often the difference between a case with a modest personal auto policy and one with a much larger commercial coverage layer behind it.

Rideshare and delivery driving has grown quickly across both states, and the insurance framework built around it is still less familiar to most people than ordinary auto coverage. Adjusters, on the other hand, deal with these claims constantly and know exactly which questions determine how much coverage is on the table. That imbalance is one of the main reasons these claims benefit from careful handling from the start, rather than assuming a rideshare crash works just like any other fender-bender.

The three coverage periods explained

Rideshare companies structure their insurance programs around the driver's app status, and most programs break down into three periods:

• Period 0 — app off. The driver isn't logged into the rideshare app at all. If a crash happens here, it's treated like any other personal car accident: the driver's own personal auto policy applies, and the rideshare company's coverage generally isn't involved.
• Period 1 — app on, waiting for a ride request. The driver is logged in and available but hasn't been matched with a passenger. Typical program terms in most states — confirm the policy in your case — provide a more limited, contingent layer of liability coverage during this window, which can fill in if the driver's personal policy denies or limits coverage.
• Period 2/3 — en route to pick up or transporting a passenger. Once a driver accepts a ride request, a substantially larger commercial liability layer generally applies — commonly around the $1 million mark, though the details depend on the company and jurisdiction.

Because the difference between these periods can mean the difference between a modest policy and a seven-figure one, figuring out exactly which period applied at the moment of the crash is usually the very first question in any rideshare case. Some crashes happen right at the boundary between periods — for example, seconds after a driver accepts a request but before they start moving — and those borderline moments are exactly where insurers and claimants tend to disagree.

Passenger vs. other-driver vs. pedestrian claims

Who you were at the time of the crash changes how a claim is built:

• If you were a rideshare passenger, you weren't at fault regardless of who caused the crash, and your claim generally runs against whichever driver (rideshare or the other vehicle) was responsible — often reaching the rideshare company's commercial coverage layer, since a ride was underway.
• If you were driving another vehicle that the rideshare driver hit, your claim proceeds much like any other crash claim, but which coverage period the rideshare driver was in still determines how much coverage is potentially available.
• If you were a pedestrian or cyclist struck by a rideshare vehicle, the same period-based analysis applies to determine which policy responds, and your own underinsured motorist coverage (if you have auto insurance) may also come into play.

Passenger claims deserve a closer look because they are the claims most likely to involve the rideshare company's largest coverage layer. A passenger who is injured is, by definition, not at fault for causing the crash, whether the rideshare driver or another driver caused it. That doesn't mean the claim is automatically simple — the insurer for whichever driver is at fault will still investigate the crash, evaluate the injuries, and negotiate (or dispute) the value of the claim the same way it would in any other case. Being a passenger removes the fault question but doesn't remove the rest of the claims process.

Why the app data matters — and how it's obtained

Rideshare companies keep detailed records of exactly when a driver logged into the app, when and whether a ride request was sent and accepted, and when a trip started and ended. That data is often the single most important piece of evidence in the case, because it can definitively establish which coverage period was active at the moment of the crash — rather than leaving it to the driver's memory or the company's initial characterization.

This information generally has to be requested formally, and the request should go out promptly. Rideshare companies are large organizations with their own data retention practices, and a delayed or informal request can result in incomplete records or slower responses. This is one of the technical, time-sensitive steps that benefits from experienced handling early in a case.

It also helps to gather your own supporting details as soon as possible after the crash: a screenshot of the trip receipt or ride history in your app account, the driver's name and vehicle information as shown in the app, and the approximate time the ride was requested and accepted. None of this replaces the company's own formal records, but it can help corroborate the timeline while memories are still fresh.

Stacking layers: personal, rideshare, and UM/UIM coverage

Depending on the facts, more than one policy can potentially contribute to a recovery. A driver's personal auto policy, the rideshare company's contingent or commercial layer, and the injured person's own underinsured/uninsured motorist (UM/UIM) coverage can all interact, particularly if the at-fault party's available coverage doesn't fully cover the damages. Sorting out how these layers stack — and in what order they apply — is a coverage analysis that depends heavily on the specific policies involved.

This is also where your own auto policy can matter even if you weren't driving your own car at the time. Many UM/UIM policies extend coverage to the policyholder as a pedestrian, a passenger in someone else's vehicle, or a passenger in a rideshare vehicle — but the exact terms vary by policy and by state, so this is worth checking rather than assuming either way.

Delivery apps: same logic, different limits

Delivery platforms like DoorDash, Amazon Flex, Instacart, and similar services generally use the same basic framework as rideshare apps — coverage depends on what the driver's app was doing at the time of the crash — but the specific coverage periods, dollar amounts, and company policies are set independently by each platform. A crash involving a food-delivery or package-delivery driver requires the same kind of app-status and app-data analysis, just applied to that company's specific program rather than assumed from the Uber or Lyft model.

Delivery crashes also raise a wrinkle that rideshare cases usually don't: many delivery drivers use their personal vehicles for the job but carry a personal auto policy that excludes commercial or delivery use. That gap between what the personal policy covers and what the delivery company's program covers is exactly the kind of issue that needs to be worked out policy by policy, rather than assumed from general practice.

This article is general information, not legal advice; reading it does not create an attorney-client relationship. Every case is different, and deadlines and rules change — confirm how the law applies to your situation with a licensed lawyer. Apis Felix Law, a trade name of Deseret Lawyers PLLC. Attorney advertising. Kevin Peterson is the attorney responsible for this content and is licensed in Nevada (Bar No. 14598) and Utah (Bar No. 18723).