Rideshare passenger cases have always lived in an awkward gap between three insurance policies: the driver's personal coverage, the rideshare platform's contingent policy, and the platform's primary policy when a ride is "in progress." Until recently, Pennsylvania carriers used that ambiguity to delay and underpay.
A 2026 ruling from Pennsylvania's Superior Court has started closing that gap. The decision, addressing a multi-vehicle crash on I-95 near Philadelphia, held that platform-issued primary coverage attaches the moment a passenger accepts the ride — not at pickup, and not when the GPS confirms the route has started. That distinction matters: in earlier cases, carriers argued the passenger was technically not "in" the vehicle yet and tried to push liability back onto the driver's personal policy, which is often inadequate for serious injuries.
What this means for your case
If you were injured as a rideshare passenger in PA — or in DE or NJ where similar arguments are still being litigated — three things matter:
- The exact moment you accepted the ride, often recoverable from your app history
- The driver's status in the platform at the time (offline, logged-in, on a ride)
- The platform's policy effective dates, which we obtain via formal discovery
We've handled a half-dozen rideshare passenger matters since this ruling came down. The pattern: insurers reach earlier, fairer numbers when we can document policy attachment with the platform's own logs.
— DiLeonardo & Shaw · Personal Injury