An Uber or Lyft logo on a vehicle doesn’t automatically mean the same insurance policy applies after a collision. The driver’s app status at the moment of impact and the evidence of who caused the crash usually control where an insurance claim begins. Those two facts can point to very different insurers with very different answers.
For anyone navigating Uber and Lyft insurance coverage after a Maryland crash, Antezana & Antezana, LLC. provides 24/7 support while the details are still fresh. Contact us today!
Why App Status Changes Everything After a Maryland Rideshare Crash
Maryland treats a transportation network company (a company that connects riders with drivers through a digital application) differently from an ordinary personal driving arrangement. Maryland Public Utilities Article §10-405 requires insurance when transportation network services are being provided, and the coverage available shifts with the driver’s status at the time of the crash.
Four stages matter most. A driver may be offline, logged in and waiting for a request, traveling to pick up a rider after accepting a trip, or actively transporting a passenger. The same vehicle, the same road, the same driver. A different insurance policy or coverage level may apply depending on which stage applies.
Fault is the other central question. If another motorist ran a red light or rear-ended the rideshare vehicle, that driver’s liability policy may be the first source of recovery, even when an Uber or Lyft passenger was injured. The driver’s app status still matters, but it doesn’t replace a careful investigation into who caused the collision.
How Coverage Changes Across the Four Driver Statuses
The coverage picture becomes clearer once the app status is identified. Policy language, endorsements, available limits, and the facts of the collision still need review in every case.
App Off
When the driver isn’t logged into the rideshare app, the driver’s personal auto insurance policy is the starting point. The transportation network company’s coverage generally isn’t triggered simply because the vehicle is used for rideshare work at other times.
App On, Waiting for a Request
When a driver is logged in and available but hasn’t accepted a ride, Maryland law requires at least $50,000 in bodily injury liability per person, $100,000 per crash, and $25,000 for property damage. This contingent liability coverage may fill a gap when the driver’s personal policy excludes rideshare activity. Those amounts are statutory minimums, not a promise that every claim will be paid in full. The insurer still evaluates fault, injuries, exclusions, and whether another policy has priority.
Accepted Pickup
Once a driver accepts a trip and is en route to the rider, Maryland’s requirements increase significantly. Under §10-405, the operator or transportation network company must maintain primary automobile liability coverage during this period. This means coverage that responds without waiting for another policy to be exhausted first. The actual limits depend on the company: Uber currently maintains $1 million in this phase, while Lyft has reduced its Maryland coverage to $125,000, the statutory minimum under §10-405.
The accepted trip timestamp can be as important as the crash report itself. A driver may claim they were on the way to a rider, but trip records and app data are more reliable than a roadside account.
Passenger in the Vehicle
The higher coverage requirements continue while a passenger is being transported until the trip ends. Maryland also requires uninsured and underinsured motorist coverage at the required level for transportation network services, which may apply when the at-fault driver carried no insurance or too little to cover the damages. Company policies can contain terms that affect how coverage is administered, so a commonly cited policy limit shouldn’t be treated as an automatic payment or as the only policy in play.
Which Insurer May Pay Your Claim
A rideshare crash can involve more than one insurer, and the first claim should generally follow the evidence of fault. If a separate driver caused the collision, that driver’s liability coverage is typically pursued first. The rideshare driver’s policy, the transportation network company’s coverage, and the injured person’s own policy may all become relevant if the at-fault coverage is unavailable or insufficient.
Maryland Insurance Article §19-517 allows a personal auto insurer to exclude losses that occur while a driver is providing transportation network services, while also permitting coverage for that activity through a rideshare endorsement. In practice, a driver’s personal policy may deny a claim during an active rideshare period while a separate policy responds instead.
Personal injury protection (PIP) is no-fault medical and wage loss coverage available under many Maryland auto policies. Depending on the policy and the person’s status, PIP may provide early benefits without first establishing who caused the crash. Uninsured and underinsured motorist coverage can also matter significantly when the at-fault driver was inadequately insured.
Maryland’s contributory negligence rule adds another layer of risk. Under this rule, a person found to have contributed to causing the collision may be barred from recovering from any other negligent party. Insurers often raise fault arguments early in the process, so statements, photographs, and other evidence can determine outcomes long before a claim is resolved.
How Insurers Confirm the Driver’s App Status
Useful evidence can include:
- Trip Receipts: Passenger receipts can show a booked trip, pickup location, drop-off location, and timing.
- App Screenshots: Screenshots of a driver or passenger app can preserve ride details before they disappear.
- Police Reports: The report may identify occupants, witnesses, vehicle positions, and initial accounts of the collision.
- Witness Information: Independent witnesses may confirm whether a passenger was entering, leaving, or riding in the vehicle.
- Scene Photographs: Images can document vehicle damage, rideshare decals, road conditions, and the crash location.
- Medical & Expense Records: Records connecting treatment, missed work, and out-of-pocket expenses to the collision should be retained from the start.
Maryland law requires transportation network companies and insurers to cooperate in exchanging coverage information and logged-in time records during a claim investigation. Preserving trip data promptly, before digital ride and app records are lost or overwritten, is particularly important when the parties disagree about what the driver was doing at the time of the crash.
What to Do After an Uber or Lyft Crash
Safety and medical care come first. Call 911 when anyone is hurt, vehicles can’t be safely moved, or law enforcement is needed. Even injuries that seem minor at the scene should be evaluated if pain, dizziness, numbness, or other symptoms develop afterward.
- For Rideshare Passengers
Take screenshots of the trip receipt and report the collision through the app. Get the driver’s name, insurance information if available, the police report number, and contact information for any witnesses. Keep all medical records and receipts, including transportation costs to treatment. - For Other Drivers
Exchange information with every involved driver and photograph damage from multiple angles before vehicles are repaired. Don’t assume the rideshare company is responsible just because one vehicle displayed an Uber or Lyft decal. The at-fault driver and each driver’s app status both need to be identified. - For Pedestrians & Bicyclists
Ask responding officers to identify the vehicle, driver, and any passenger. If possible, note whether the driver appeared to be picking someone up, dropping someone off, or waiting for a request. Pedestrians and bicyclists may have access to different insurance benefits than passengers, including coverage under their own auto policy in some circumstances. - For Everyone Involved
Avoid giving a recorded statement or accepting a quick settlement before understanding your injuries and the applicable insurance policies. Acting promptly can help preserve trip data, identify overlapping coverage, and resolve disputes between insurers before critical evidence is gone.
Coverage Depends on More Than a Rideshare Label
The right insurance analysis comes down to three facts: the driver’s app status, the evidence of fault, and the language of every potentially applicable policy. A crash during an active passenger trip may involve coverage that looks nothing like a crash where the app was off, and another driver’s negligence can change the starting point entirely.
For help reviewing a rideshare claim in Gaithersburg, Wheaton, Takoma Park, or anywhere in the surrounding area, Antezana & Antezana, LLC. offers bilingual support, free consultations, and 24/7 availability. We work on a no-fee-unless-we-win basis and can be reached at (301) 640-5735.