Rideshare insurance by app phase can be a key question after a Nevada crash. A driver who is logged in and waiting for a request is in a different status from one who is providing a ride. Nevada law sets different minimum coverage requirements for those periods. The app record, the time of the crash, and what the driver was doing can help determine which provision needs review.
The numbers in a statute do not decide who caused a collision or guarantee that a particular person will receive a payment. They describe required insurance amounts for specified periods of transportation service. A claim still depends on facts such as the driver’s status, the applicable policy, the injury or damage, and the basis for legal responsibility.
Two app periods have different minimums
NRS 690B.470 sets coverage requirements for transportation network company insurance. For a driver who is logged into the company network or app and available to receive ride requests, but is not otherwise providing transportation services, subsection 1 lists three minimum-coverage categories for a single crash. Paragraphs (b) and (c) address bodily injury or death of one person and of two or more people, with the latter subject to the one-person minimum. Paragraph (d) addresses injury to or destruction of other people’s property. The exact current amounts appear in the linked statutory text, so check that section and the applicable policy rather than relying on an older summary.
When a driver is providing transportation services, subsection 1(a) sets a separate, higher single-crash minimum for bodily injury or death of one or more people and injury to or destruction of property of others. The law frames that requirement as a minimum for the service period. It does not say that each injured person automatically receives a particular amount, that the driver is legally responsible, or that a policy will pay without review. Check the linked current section for the exact figure that applies.
These amounts describe different app circumstances, not a simple rule based on whether a passenger was sitting in the car. The statutory language distinguishes the period when a driver is logged in, available for requests, and not otherwise providing services from the period when the driver is providing transportation services. The exact facts and the statutory definitions matter if the crash happened as a request was being accepted, a pickup was underway, or a ride had ended.
Do not guess at that dividing point from memory alone. A rider may remember receiving a trip confirmation, while the driver’s app could have shown a different status or the crash may have occurred during a transition. Preserve the receipt, trip page, pickup location, messages, and timestamps. If you were not the passenger, note what you personally saw and what you learned later from someone else.
The stated amount is not the entire coverage picture
The statute allows the required transportation network company insurance to be provided through one policy or a combination of policies involving the company, driver, or both. It also requires the company to provide its insurance as primary coverage during transportation services if the driver’s coverage lapses or fails to meet the statutory requirements. These provisions address insurance arrangements. They do not resolve disputed facts about whether the driver was working through the app at the time.
A personal auto policy may not automatically fill a gap. Nevada law does not require a standard motor vehicle policy to include transportation network company coverage. The statute also addresses policies that exclude it during periods when a driver is logged in, available for requests, or providing services. That is one reason to identify the app period and the exact policies rather than assume that the driver’s personal insurer or the rideshare insurer must pay every claim.
The law separately requires written disclosures to drivers about transportation network company insurance and warns that the driver’s ordinary auto coverage may not apply to app-based transportation use. A driver may have a company policy, a personal policy with an endorsement, or insurance arranged through more than one policy. A claimant should ask which policies have been identified and what exclusions or limits each insurer says apply.
Transportation network company policies may also include additional coverage, such as medical payments, uninsured or underinsured motorist coverage, comprehensive coverage, or collision coverage. The statute says these additions may be included; it does not guarantee that every company policy contains each one. The policy itself and the company’s coverage disclosure are needed to know what applies to a particular crash.
App records can help fix the timeline
Nevada law has a specific information-sharing rule for investigations of tort liability arising from a motor vehicle’s operation. Under NRS 690B.490, the transportation network company, involved driver, relevant insurers, and other listed participants must cooperate and share information. The statute includes the date and time of the crash, the times the driver logged in and logged out for the twelve hours immediately before and after it, and a clear description of applicable policy coverage, exclusions, and limits.
That does not mean an injured person receives every app record instantly or without following the appropriate request process. It does identify concrete information that may be relevant to an investigation. A request can distinguish the status immediately before the crash from a later screenshot or a general statement that the driver was “on the app.” Keep a note of what was requested, from whom, and when.
NRS 690B.495 also says that a driver must carry proof of transportation network company coverage while logged in, available for requests, or providing services. Upon request, the driver must provide proof and disclose whether the driver was logged in, available, or providing services at the time of the crash to a law enforcement officer and any party involved in the collision. If you were directly involved, write down whether you asked for this information and what response you received.
The date and time should be recorded as precisely as possible. Note the crash time shown on a police exchange form or dispatch record, the time of a ride receipt, and any phone clock or message time. Do not alter an original screenshot to make it easier to read. Save a full-screen copy and a separate working copy if you need to highlight a detail for your own notes.
What a passenger or other driver can preserve
If you were a passenger, save the ride receipt, driver name shown in the app, pickup and destination details, route display, fare record, support messages, and any trip-status notifications. Keep the original email or in-app message when available. Do not rely only on a screen that disappears when the app is closed. If the company offers a way to download trip history, save the record and note when it was retrieved.
If you were in another vehicle, record the rideshare company name, the driver’s identifying details that were exchanged, the vehicle description, license plate, crash location, and approximate time. Preserve any photos or video of the scene in the original format. A witness’s statement that a driver was picking someone up is useful as a lead, but it may not establish exactly what the app showed. Keep observations separate from assumptions.
Ask the investigating officer how the report will identify a transportation network company vehicle and whether the driver’s status was recorded. A police report may contain useful initial information, but it is not a substitute for app and policy records. If a field is missing or appears wrong, write down the specific item and ask how the report can be supplemented. Do not assume that an omitted status means the driver was offline.
When you communicate with an insurer, provide accurate facts and keep a copy of what you send. If an insurer asks for a recorded statement, you can ask what policy and claim it relates to, who it represents, and whether it is asking about your own coverage or another party’s. Avoid guessing about the app stage. If you do not know, say so and point to the available record.
Coverage limits do not establish fault
The minimum amounts in NRS 690B.470 concern insurance for tort liabilities arising from the maintenance or use of a motor vehicle. They do not decide whether the rideshare driver, another driver, a passenger, or anyone else acted carelessly. A crash can involve more than one vehicle or more than one potentially responsible person. The coverage question and the liability question are related, but they are not interchangeable.
A reported app status is not conclusive by itself. The status should be compared with timestamps, the trip history, the crash report, the route, communications, and the insurers’ descriptions of the policies. A coverage dispute may turn on policy language or a disagreement about when transportation services began. Keep the exact wording of any denial or reservation-of-rights letter and the materials the insurer says support its decision.
Likewise, a minimum insurance requirement for a specified period is not a forecast of the value of an injury claim. It does not promise a settlement, a payment date, or a particular recovery. Other conditions, policy terms, available evidence, and the facts of the collision still matter. Any estimate made before those details are known would be speculation.
Steps to take after a rideshare crash
First address safety and medical needs. Call emergency services when necessary and follow medical instructions. Tell the treating professional what happened as accurately as you can. Save discharge papers, imaging records, appointment notes, prescriptions, and bills. Do not delay needed care while trying to identify an insurer or app status.
Next, keep crash records and app records in separate folders. The crash folder can include photographs, the report number, witness contacts, repair documents, and a timeline. The app folder can include receipts, screenshots, messages, account downloads, and any written response from the company. Keep the date received for each insurer letter and note any response deadline shown there.
When an insurer provides a coverage explanation, ask which app period it believes applied, which policy it relies on, and what records support that position. If an insurer says the driver was logged in and available but not yet providing services, compare its position to the statutory waiting-period amounts. If it says transportation services were underway, ask it to identify the policy and limits for that period. Do not treat the first figure mentioned on a phone call as a final coverage determination.
The Bourassa Law Group has additional information about Lyft and Uber accident claims in Las Vegas and what to do after a rideshare injury. The firm’s Nevada car accident practice page describes the broader injury practice. Those pages do not replace review of the app timeline or the actual policy.
If you want to discuss an injury from a rideshare crash, contact The Bourassa Law Group for a free consultation. You can ask how a contingency-fee arrangement would apply to your situation and what costs may involve. A consultation can help identify what records should be reviewed, but no result can be promised before the facts and coverage documents are evaluated.
This article is general information about Nevada law, not legal advice. Reading it does not create an attorney-client relationship.
1-800-870-8910