DC Injury Lawyer Blog
You climbed into an Uber or Lyft expecting an ordinary ride across the District, and instead the trip ended in a collision. Now you are hurt, you are not sure whether the rideshare driver or another motorist caused it, and you have no idea whose insurance is supposed to cover your medical bills. That uncertainty is normal, and in a rideshare case it often matters more than people realize.
In Washington, D.C., the money available to pay your claim can swing from a modest policy to a million-dollar one depending on a single fact: what the driver’s app was doing at the moment of the crash. Knowing how that works, and what can put the larger coverage out of reach, helps you protect your claim from the first day.
Which Coverage Applies Depends on the Driver’s App Status
District law ties the rideshare company’s insurance to the stage of the trip, so the driver’s screen at the time of impact shapes your recovery. Under D.C. Code § 50-301.29c, a rideshare driver who is logged in and waiting for a request, with no trip accepted yet, carries lower primary coverage of at least $50,000 per person, $100,000 for everyone hurt in the crash, and $25,000 for property damage. The picture changes once the driver accepts a request. From the moment a ride is accepted through the end of your trip, the company must provide one million dollars in liability coverage. When the app is off entirely, the driver’s personal auto policy is the only coverage in play, and many personal policies exclude driving for hire. The same driver, the same car, and the same intersection can produce very different coverage depending on which of those stages applied.
Why the Rideshare Company’s Million-Dollar Policy Is Not Automatic
Reaching the larger policy depends on proving the trip stage, and that is exactly where insurers push back. A rideshare company and its insurer have a financial reason to argue that the driver had not yet accepted your ride, or was offline, when the crash happened. The answer lives in the app data, which records when the driver logged on, when a request was accepted, and when the trip began and ended. D.C. Code § 50-301.29c(g) requires the company to cooperate in a claims investigation and to share the dates and times that fix the driver’s status. That cooperation helps only if someone requests the records before they are lost or buried. Locking down the trip data early is often what decides whether the million-dollar policy is even on the table.
How D.C.’s Fault Rule Affects Passengers and Other Drivers
The District’s approach to fault is unusually harsh, though it lands differently depending on where you were sitting. Washington, D.C. still follows contributory negligence for collisions between motor vehicles, which means a person who shares any fault for a crash can be barred from recovering at all. The comparative fault protection in D.C. Code § 50-2204.52 reaches pedestrians, cyclists, and scooter riders, not people riding inside a car. As a passenger, you almost never share blame for how the vehicles collided, so that bar rarely threatens your claim. The rule carries more weight if you were the rideshare driver or the driver of another vehicle, where an insurer may try to assign you part of the fault. More than one driver can be responsible for the same crash, and you may have a claim against each of them. Sorting out who was at fault, and keeping any blame off your shoulders, is central to protecting what you can recover.
Evidence That Decides a D.C. Rideshare Claim
The proof in a rideshare case is part digital and part traditional, and both kinds fade quickly. Your trip receipt, the in-app ride history, the police report, and the driver’s recorded status all help establish who was responsible and which policy applies. Photographs, witness statements, and your medical records fill in the rest. Deadlines apply to all of it. You generally have three years from the date of the crash to file an injury lawsuit in the District under D.C. Code § 12-301(a)(8), and a far shorter clock can apply when a government vehicle or agency is involved, since a claim against the District calls for written notice to the Mayor within six months under D.C. Code § 12-309. An attorney can request the app data and preserve the rest while it still exists. The sooner that evidence is gathered, the harder it becomes for an insurer to dispute what happened.
Get The Schupak Law Firm Involved Early After a D.C. Rideshare Crash
If you were hurt in a rideshare crash in Washington, D.C., Maryland, or Virginia, you do not have to figure out the insurance layers alone. The Schupak Law Firm can review what happened, identify which coverage applies to your claim, and explain your next steps before key records disappear. To schedule a consultation, contact The Schupak Law Firm at 240-833-3914.