Hit by an Uber or Lyft Driver: Third-Party Injury Claims

If an Uber or Lyft driver hit you — while you were walking, cycling, or driving your own car — you are not a party to any rideshare agreement, and yet your entire claim turns on the same technical detail that governs the driver’s own passengers: what the driver’s app was doing when the crash happened.

That single fact determines whether you are dealing with a driver’s thin personal auto policy, a modest “contingent” commercial policy, or a $1 million commercial liability policy — and insurers on both sides have a financial incentive to place the crash in whichever period is cheapest for them.

Quick answer: If the driver had accepted a ride or had a passenger, up to $1,000,000 in third-party liability coverage typically applies — regardless of whether you were a pedestrian, cyclist or another driver. If the app was on but no ride was matched, contingent coverage of roughly $50,000/$100,000/$25,000 applies instead. If the app was off, only the driver’s personal policy applies, and it may exclude commercial use entirely.

The Same Three Periods, From the Other Side

Every rideshare trip runs through the same coverage periods discussed in claims by the driver or their passengers — the difference is that as a third party, you were never inside the vehicle and never had any relationship with the app at all:

With the app off entirely, there is no rideshare coverage at all — only the driver’s own personal auto policy, which may itself exclude commercial or livery use once it’s established the driver was working. The bottom row of the table above is the one that matters most in practice: it applies not just to the rideshare passenger, but to anyone the driver hits while working a matched trip — a pedestrian in a crosswalk, a cyclist in a bike lane, or the occupants of another vehicle.

Why the App-Status Fight Is the Whole Case

Unlike a claim against an ordinary at-fault driver, where liability and damages are usually the main fights, a third-party rideshare claim frequently turns almost entirely on a single factual question that has nothing to do with how the crash happened: was the driver logged in, and to which status, at the moment of impact?

Two competing incentives collide here:

• The rideshare company’s insurer has an incentive to argue the app was off, or that no ride had been matched, shifting responsibility to the driver’s thin personal policy.
• The driver’s personal insurer has an incentive to argue the opposite — that the driver was actively working — because personal auto policies routinely exclude commercial or livery use entirely, giving the personal insurer grounds to deny the claim outright if commercial use is established.

You, the injured third party, are caught between two insurers each trying to point at the other. The trip and app-status data that resolves this dispute is held by the rideshare company, not by you, and getting it released typically requires formal discovery — sometimes only achievable after a lawsuit is filed.

Building the Claim

• Get the driver’s identifying information and rideshare company at the scene — vehicle decal or app-visible trip screen, license plate, and driver name — before it becomes a discovery fight later.
• Preserve your own evidence immediately: photos of the scene, your injuries, and the vehicle; contact information for any witnesses; and, where available, footage from nearby businesses or traffic cameras.
• File a report with police documenting both drivers’ accounts and any citation issued.
• Notify your own insurer if you were driving, even if you believe the rideshare driver was entirely at fault — this preserves your own UM/UIM option if the rideshare coverage picture turns out to be disputed or insufficient.
• Expect the trip-data request to take time. Rideshare companies do not typically hand over driver app logs voluntarily and quickly; plan around this rather than being surprised by it.

If You Were a Pedestrian or Cyclist

Comparative fault applies to third-party claimants the same way it applies to any other pedestrian or cyclist claim — where you were crossing, whether a signal was in your favor, and your own visibility and conduct can all be raised by the insurer regardless of which rideshare period applied. See our guides on pedestrian accident settlements and bicycle accident settlements for how that analysis works, and our comparative negligence by state guide for what your state’s fault rule does to a partially disputed claim.

Sources & Further Reading

• NCOIL Model Act to Regulate Insurance Requirements for Transportation Network Companies and Transportation Network Drivers (adopted 19 July 2015) — the origin of the tiered structure, following a March 2015 agreement among PCI, AIA, NAMIC, Uber and Lyft
• State TNC statutes codifying those third-party minimums by app-status period — e.g. Fla. Stat. § 627.748, N.C. Gen. Stat. ch. 20 art. 10A, Okla. Stat. tit. 47 § 1025. More than 40 states have enacted TNC insurance legislation.
• NAIC, Transportation Network Company Insurance Principles for Legislators and Regulators
• Uber, Insurance for Rideshare and Delivery Drivers, and Lyft, Insurance coverage while driving with Lyft — though the operative document in a claim is the state-specific certificate of insurance for the date of the crash
• See our Uber & Lyft accident settlements guide for the same coverage structure from a passenger’s perspective, and our rideshare driver coverage gaps guide for the driver’s own exposure.
• For the doctrines behind the independent contractor classification described above — and the routes that get around it, including apparent agency and negligent selection — see our guide to vicarious liability and negligent entrustment.
• The same classification problem shapes assault claims against the platforms, where the theories are negligent screening and negligent retention rather than vicarious liability — see our guide to rideshare sexual assault claims.