Rideshare Crash Claims in DC, 2023 Edition: The Insurance Layers, Eight Years On
Eight years ago, we wrote about Uber and Lyft crashes as a new legal frontier — an "insurance gap" era when nobody was quite sure whose policy covered a rideshare collision. In 2023, rideshare is simply how the region moves, and the legal framework has matured. The gaps have narrowed. But the layered insurance system that replaced them still confuses injured passengers, drivers, and pedestrians alike — and the difference between the layers can be the difference between a $25,000 policy and a $1,000,000 one.
The layers: coverage follows the app
Since the District's vehicle-for-hire legislation took effect in 2015, transportation network company (TNC) insurance in DC has followed the driver's app status. The structure in 2023:
| App status | Whose insurance, and how much |
|---|---|
| App off | Driver's personal auto policy only |
| App on, waiting for a ride request ("Period 1") | TNC-required coverage of at least $50,000 per person / $100,000 per accident bodily injury and $25,000 property damage |
| Ride accepted, en route to pick up ("Period 2") | $1,000,000 in liability coverage |
| Passenger in the vehicle ("Period 3") | $1,000,000 in liability coverage |
Two structural points. First, the driver's personal auto policy almost certainly excludes commercial activity — personal carriers routinely deny claims once the app was on. Second, the $1 million layer is real and collectible, but it applies only when the crash fits the right period. Establishing exactly what the app showed at the moment of impact is therefore not a detail; it is the case.
What changed since 2015 — and what didn't
- The framework hardened. What was a patchwork of company promises in 2015 is now statutory obligation, with insurers (not just the TNCs' goodwill) on the risk.
- Vulnerable road users got real protection. If a rideshare driver hits a pedestrian, cyclist, or scooter rider, the District's comparative-fault reforms — the Motor Vehicle Collision Recovery Act of 2016 and the vulnerable-user expansion effective in 2021 — mean the injured person's own minor negligence is no longer an automatic bar. Passengers in the rideshare vehicle rarely face a fault argument at all, which makes passenger claims among the cleanest liability cases we see.
- Contributory negligence still rules driver-vs-driver claims. A rideshare driver hurt in a crash, or another motorist in a collision with one, still faces the District's traditional 1% contributory negligence bar.
- The gig-delivery asterisk. The TNC insurance framework covers ridesharing. Food and package delivery apps run on different (often thinner) coverage structures — a distinction we covered in 2020 and that still catches injured people by surprise.
The practical traps
1. Period disputes. Insurers litigate the app status. Screenshots, trip receipts, and the TNC's own data logs resolve it — if they are preserved. A prompt preservation demand to the TNC is standard practice in our office. 2. Layer ping-pong. The personal carrier points to the TNC insurer; the TNC insurer points to the period. Injured people who negotiate alone often get settled out of the wrong (smaller) layer. 3. Underinsured drivers in Period 1. The waiting-period limits are modest. Your own uninsured/underinsured motorist coverage may be the most important policy in the case — check it before assuming the rideshare layer is all there is. 4. The "independent contractor" deflection. TNCs classify drivers as contractors and resist direct liability. The insurance layers exist precisely so that fight usually doesn't matter to compensation — but it is one more reason these claims benefit from counsel who has run the route before. 5. Multi-apping. Many drivers run two or three platforms at once. When the crash happens with one app on a trip and another merely open and waiting, the companies' insurers will each argue the other's period controls. The data logs from every platform the driver used that day belong in the preservation demand.
What this means for injured people in the District of Columbia
If you are hurt in any crash involving a rideshare vehicle — as a passenger, another driver, or a pedestrian — treat the app data like the crash-scene photographs: capture it immediately. Screenshot the trip screen, the receipt, the driver and vehicle details. Report the crash in the app so the TNC's records reflect it. Call the police and make sure a report is written. And before accepting any insurer's characterization of which coverage applies, get advice — the layers exist, but they do not sort themselves out in your favor on their own.
Eight years on, the rideshare insurance story in DC is no longer about gaps. It is about knowing which of several real policies is on the hook — and holding the right one to it.
If you or a loved one has been hurt, call Posey Lebowitz at (202) 524-0123 or send us a message for a free consultation.
Part of our DMV case law archive, compiled in 2026 to reflect the archive of some of the most important decisions in injury law.