Transportation network company accident litigation is structurally different from a standard two-car accident because the applicable insurance coverage depends entirely on the driver's app status at the precise moment of the crash. Most plaintiff attorneys know that Uber and Lyft carry substantial liability insurance, but the coverage tier that applies to a specific crash is not always the one that first comes to mind. Getting the coverage analysis right at the outset of the case determines who the insurer is, what the policy limits are, and what discovery is needed to establish that the most favorable coverage period applies.
The Three Coverage Periods
Coverage for rideshare accidents is divided into three periods defined by the driver's app status. Period 1 begins when the driver activates the app and is waiting for a ride request. Period 2 begins when the driver accepts a ride request and is en route to pick up the passenger. Period 3 begins when the passenger enters the vehicle and continues until the passenger exits and the trip is completed. The coverage that applies to an accident involving a rideshare driver changes materially across these three periods.
When the app is off entirely, the driver is operating as a private motorist and the rideshare company provides no coverage. The claim is against the driver's personal auto policy. The driver's personal insurer is the only target, and the limits are whatever the driver's personal policy provides.
In Period 1, when the app is on but no ride has been matched, Uber and Lyft provide contingent liability coverage of $50,000 per person and $100,000 per incident for bodily injury, and $25,000 for property damage, but only if the driver's personal policy does not cover the loss. Many personal auto policies contain a rideshare exclusion that voids coverage when the vehicle is being used in a ride-for-hire context, which triggers the TNC's contingent coverage. California Insurance Code section 11580.9, enacted through TNC insurance legislation, mandates minimum coverage requirements for each period that California TNCs must maintain.
In Periods 2 and 3, when a ride is matched or in progress, the coverage analysis changes dramatically. Both Uber and Lyft maintain commercial liability policies with limits of $1,000,000 per occurrence, which are primary during any period when a ride is in progress. These policies cover injuries to the passenger, to third parties struck by the driver, and to other occupants of other vehicles in multi-vehicle accidents. The million-dollar commercial limits are the target in any case involving a crash during an active ride, and the first investigation step should be confirming through the driver's app records or the TNC's platform data which period was active at the time of the crash.
Documenting the Coverage Period
The driver's app status at the time of the crash is documented in the TNC's platform data, which includes GPS-timestamped ride status records showing when the driver activated the app, when a ride was matched, when the driver arrived at the pickup point, and when the passenger was marked as picked up and dropped off. That data is in the exclusive control of the TNC and is not available through the driver. A preservation demand sent to the TNC's legal department within 24 to 48 hours of the crash should specifically request all platform data related to the driver's account for the date and time of the incident, including app status logs, trip logs, GPS location records, and communications through the app.
Drivers sometimes dispute or misrepresent their app status at the time of a crash, particularly in Period 1 accidents where they are awaiting a match but prefer to characterize the driving as purely personal. The TNC's platform data is the authoritative source for resolving that dispute, and a driver's statement that the app was off is checkable against that data. The TNC is also a required source because the TNC itself is a proper defendant in Period 1 through 3 crashes under agency, joint enterprise, and statutory TNC liability theories depending on the jurisdiction.
Underinsured Motorist Coverage in Rideshare Cases
When the at-fault driver is a rideshare driver in Period 1 and the $50,000 contingent coverage is insufficient for the plaintiff's damages, the plaintiff's own underinsured motorist coverage may apply to bridge the gap. The interaction between the plaintiff's UM/UIM coverage and the TNC's contingent coverage requires analysis of the plaintiff's own policy terms and the jurisdiction's stacking rules. In cases where the plaintiff is a rideshare passenger injured by a third-party driver who is underinsured, the rideshare company's commercial policy should include UM/UIM coverage for Period 3 accidents, though the specific terms of the TNC's commercial policy should be verified through the TNC's insurer or through discovery. For the full insurance coverage and uninsured motorist claim framework, the auto-accidents category covers UM/UIM claim strategy and the phantom vehicle and coverage issues that intersect with rideshare cases. Settlement disbursement and lien considerations in rideshare accident cases follow the same framework as standard auto accident settlements, covered in the liens-and-settlement category. For case-law developments on TNC liability theories and insurer priority disputes in rideshare accident cases, the case-law-settlements archive tracks the relevant decisions.