Maryland Accidents

FAQ Glossary Resources About
ESP ENG

Sorting Out Coverage After Maryland Rideshare Crash

“uber was on a ride when they hit us on route 301 and now my insurance says lyft uber and the driver are all pointing at each other in maryland”

— Priya N.

If a rideshare crash happened in Maryland while the app driver was actively on a trip, the fight is usually over which policy is primary, who gets blamed, and whether contributory negligence kills the claim.

If the Uber or Lyft driver was actively on a ride or on the way to pick someone up, this is the part most people miss: you are usually not dealing with just one car insurance policy.

You may be dealing with three.

The driver's own personal auto policy.

The rideshare company's policy.

And possibly your own policy for medical payments, uninsured motorist coverage, or underinsured motorist coverage if the money on the table is not enough.

That sounds simple until everybody starts playing dumb.

The first thing that matters is what "period" the driver was in

Maryland crash cases involving Uber and Lyft get messy fast because coverage changes depending on what the app was doing at the exact second of the wreck.

That's the whole period 1, 2, and 3 problem.

Period 1 means the app is on, but the driver has not accepted a ride yet.

Period 2 means the driver accepted a ride and is on the way to pick up the passenger.

Period 3 means the passenger is in the car and the trip is underway.

If the crash happened in period 2 or period 3, there is usually much stronger rideshare coverage in play. If it happened in period 1, that is where the coverage gap fights start and the shell game gets uglier.

If your adjuster just told you, "we're still determining whether the driver was logged into the app," that is not small talk. That is the entire fight.

If the driver was carrying a passenger, the company usually can't hide behind the personal policy first

When the driver is in period 3, Uber or Lyft generally has a large liability policy available. That does not mean they will gladly hand over money.

It means they will investigate the hell out of the timeline, the trip record, the pickup, the dropoff, the route, and whether their driver can somehow shift blame onto you.

In Maryland, that blame issue is brutal because Maryland is one of the few contributory negligence states. If they can pin even 1% fault on you, they will try to argue you recover nothing.

That is not a scare tactic. That is how the rule works here.

So if you were driving on Route 301 in Brandywine, or on I-95 through Baltimore County, or getting merged into on the Beltway around College Park, the insurance company is not just asking who hit who. They are looking for one bad sentence from you.

"I might have braked late."

"I didn't see him until the last second."

"I was trying to get around traffic."

That is the kind of thing they use to poison a Maryland claim.

The company may act like the driver is independent, but the policy question is still real

This is where people new to Maryland get blindsided.

The app company may keep pushing the idea that the driver is an independent contractor, not an employee, like that ends the conversation. It doesn't.

Employment status and insurance coverage are related, but they are not the same fight.

You are not crazy if it feels like everybody is trying to disappear behind paperwork.

The driver's insurer may say the car was being used for commercial activity and deny or limit coverage.

Uber or Lyft may say they need proof the trip was accepted and active.

Your own insurer may tell you to open a claim under your own coverage while they "sort out liability."

Meanwhile your car is wrecked, your neck is tightening up two days later, and you just moved here for work and don't even know whether you are supposed to be dealing with Maryland insurance rules or whatever state you came from.

If the crash happened in Maryland, Maryland rules are going to matter in a big way.

What actually decides which policy pays first

It usually comes down to documents, not arguments.

The important stuff is boring and ugly:

  • the app trip log and timestamps
  • the police report
  • body shop photos and point-of-impact damage
  • 911 audio if the timeline is disputed
  • witness statements
  • the driver's insurance policy language
  • your own declarations page for UM/UIM and med pay

If the driver had a passenger in the car, or had already accepted a pickup, the rideshare company is going to have electronic records showing that. That data matters more than whatever the driver says at the scene on adrenaline.

And if the crash happened during one of those nasty Maryland weather swings - spring downpour on I-695, fog off the Chesapeake, slick bridge deck before sunrise, leftover black ice in western Maryland - expect the insurer to lean hard on "road conditions" and "shared fault."

That is not neutral fact-gathering. That is them trying to build contributory negligence into the file.

Maryland's minimum insurance is not the same thing as enough insurance

Maryland is an at-fault insurance state, and the minimum required liability limits are 30/60/15.

That can disappear fast in a serious rideshare wreck.

One ambulance ride, an ER workup, missed time from a new job, imaging, and a recommendation for surgery or injections, and suddenly the numbers look tiny.

That is why your own uninsured or underinsured motorist coverage matters more than people realize. If the available liability coverage does not fully cover the damage, your own policy may become part of the case even though you did nothing wrong.

People hear "Uber has a big policy" and assume the money issue is solved.

It isn't.

First they fight about whether the Uber or Lyft policy applies at all.

Then they fight about fault.

Then they fight about your treatment.

Then they fight about whether your injuries were preexisting, delayed, or "not consistent with the crash."

If the adjuster just told you the rideshare company is "not accepting liability yet," that usually means the war is starting, not ending

That phrase is code.

It often means one of these things:

They have not confirmed the app period.

They are waiting to see if they can blame you.

They are hoping you will take the personal policy route only.

Or they are trying to stall while injuries become harder to prove.

In Maryland, a straight rear-end crash can still turn into a stupid argument if somebody claims sudden braking, unsafe lane change, or failure to maintain lights or signals. On roads like Route 301, I-95, or the Beltway, where traffic stacks up fast and people drive like maniacs, insurers love to muddy clean facts.

If the rideshare driver had a passenger or was on the way to one, the central question is not whether Uber or Lyft wants to be involved.

It is whether the evidence locks the crash into period 2 or period 3 strongly enough that they cannot wriggle back into the gap.

by Dwayne Patterson on 2026-02-20

This article is for informational purposes only and is not legal advice. Every case is different. If you or a loved one was injured, talk to an attorney about your situation.

Talk to a lawyer for free →
FAQ
Too late to sue after my Baltimore tow truck roadside crash last winter?
FAQ
Can I file a Hagerstown crash claim if I can't read the paperwork?
Glossary
sight distance
The length of roadway or waterway a person can see ahead. "Length" matters because sight...
Glossary
point of impact
You just got a letter that says the insurer disputes the "point of impact" in your crash. That...
← Back to all articles