Uber and Lyft Insurance in Arizona: Which Policy Pays, and When

Who pays after an Uber or Lyft crash in Arizona rarely comes down to one policy. It comes down to a timeline. ARS 28-4038 ties the available insurance to what the driver’s app was doing at the moment of impact.

That single fact decides whether an injured passenger, a struck pedestrian, or another driver recovers from a $25,000 policy or a $1,000,000 one. The gap between those numbers is the whole case.

This guide walks through the statute period by period. It explains which policy attaches when, why a rideshare driver’s personal insurer so often denies the claim, and how a passenger’s route to coverage differs from a third party’s.

The statute at the center of all of it, Arizona’s transportation network company law, runs more precise than most people injured in these crashes ever get told.

ARS 28-4038: The Statute That Governs Uber and Lyft Coverage

Arizona regulates Uber, Lyft, and any similar service as a transportation network company, or TNC. ARS 28-4038 sets the financial responsibility rules every one of them has to meet, and it does something a normal auto policy never does. It splits a single driving trip into stages and assigns different insurance to each one.

The logic is that a rideshare driver moves in and out of commercial activity all day. A driver running personal errands is nothing like a driver carrying a paying passenger, and the statute prices the risk accordingly.

The coverage is lowest when the driver is barely working, and highest when a passenger’s safety is in the driver’s hands.

Three factual questions decide which tier applies. Was the app on at all? Had the driver accepted a ride? Was a passenger actually in the vehicle? Each answer moves the case into a different layer of coverage.

The Three Coverage Periods

The clearest way to read ARS 28-4038 is as a ladder. The driver climbs it as a trip develops, and the coverage rises with each rung.

Period one: the app is on and the driver is waiting

The first regulated period begins the moment a driver logs in and waits for a ride request, before any ride is accepted.

Under ARS 28-4038(A), the driver, the company, or both must carry primary liability coverage of $25,000 for injury or death of one person, $50,000 for two or more people in one accident, and $20,000 for property damage.

That coverage can sit in one of three places. It can come from the driver’s own private passenger policy, but only if that policy expressly covers driving while logged in to the app. It can come from a policy the company maintains. Or it can come from a commercial policy.

The number that matters here is how low the floor is. A serious injury during the waiting period can blow past a $25,000 policy in a single ambulance ride, which is exactly why the next question, whether a ride had been accepted, so often decides the outcome.

Period two: the ride is accepted and the driver is en route

Once the driver accepts a ride, the statute shifts into commercial territory. ARS 28-4038(B) requires a primary commercial liability policy of at least $250,000 per incident while the driver is providing rideshare services, which includes the drive to the pickup.

This is a tenfold jump from the waiting period, and it reflects a simple judgment. A driver heading to collect a paying passenger is fully at work, and the company that dispatched the ride carries the risk.

Alongside the liability coverage, the company must also carry primary commercial uninsured motorist coverage, so an injured person isn’t left empty-handed when the at-fault party has no insurance of their own.

Period three: a passenger is in the vehicle

The top rung attaches the instant a passenger the driver is transporting is in the car. At that point, ARS 28-4038(B)(1) raises the commercial liability minimum to $1,000,000 per incident. The company must maintain that coverage for the entire time the passenger occupies the vehicle.

The commercial uninsured motorist coverage the statute requires during a ride has its own floor. Under ARS 28-4038(B)(2), it must be at least $25,000 per person and $75,000 per incident, or the state minimum liability limits set by ARS 28-4009, whichever is greater.

Why the Driver’s Personal Auto Policy Often Denies the Claim

The most common surprise after a rideshare crash is a denial letter from the driver’s own insurer. That denial usually isn’t a mistake. ARS 28-4038(C) is written to allow it.

The subsection says a rideshare driver’s personal policy, and the vehicle owner’s personal policy, don’t have to cover the vehicle, the driver, the owner, or any third party while the driver is logged in to the app or providing a ride, unless the policy expressly provides that coverage.

Most standard personal auto policies carry a commercial-use exclusion. A driver logged in to Uber or Lyft has stepped into exactly the use that exclusion carves out.

The statute does leave a door open. Under ARS 28-4038(D), an insurer may offer a rideshare endorsement or a policy that specifically covers the logged-in and providing-services periods.

A driver who bought that endorsement has personal coverage that responds. A driver who didn’t, which is the common case, leaves the company’s commercial coverage as the real source of recovery.

For an injured person, the practical lesson is direct. A denial from the driver’s personal insurer isn’t the end of the analysis. It’s often the signal that the claim belongs with the company’s commercial policy instead, and identifying which policy governs is where a rideshare accident claim is won or lost.

Passenger Versus Third Party: Two Routes to the Same Coverage

A rideshare crash usually injures one of two kinds of people, and Arizona law treats their paths to coverage differently even when the money comes from the same policy.

A passenger the driver is transporting is inside the top tier by definition. If the rideshare driver caused the crash, the passenger’s claim runs against the $1,000,000 commercial policy the statute requires during the ride.

If another driver caused it, the passenger can look to that driver’s insurance and, when it falls short, to the commercial uninsured motorist coverage the company carries.

A third party, meaning a pedestrian, a cyclist, or an occupant of another vehicle, reaches coverage through the driver’s app status at the moment of impact. If the rideshare driver was carrying a passenger, the third party can reach the same $1,000,000 tier.

If the driver had accepted a ride but hadn’t picked anyone up, the $250,000 en-route tier applies. If the driver was only logged in and waiting, the third party is left with the $25,000 waiting-period floor.

When the Coverage Still Falls Short

Even the commercial tiers can run out in a catastrophic crash, and the at-fault driver isn’t always the rideshare driver. When another motorist causes the crash and carries little or no insurance, the injured person’s own coverage moves to the front.

That’s where Arizona’s uninsured and underinsured motorist rules matter. Arizona’s UM and UIM statute requires every auto insurer to offer that coverage, and it can stack on top of the commercial coverage a rideshare crash reaches.

For a rideshare passenger struck by an uninsured driver, the layered picture, the company’s commercial uninsured motorist coverage plus the passenger’s own policy, is often what makes a recovery whole.

Thin coverage is a real risk on Arizona roads. The drivers who cause the worst crashes are often the least able to pay for the harm they do, which is the exact situation uninsured motorist coverage exists to answer.

What ARS 28-4038 Requires After a Crash

The statute doesn’t stop at setting coverage. It sets duties the moment a crash happens. Under ARS 28-4038(F), a rideshare driver has to carry proof of insurance at all times while logged in, provide that proof to everyone involved at the scene, and notify the company of the crash.

Subsection G then requires the company and its insurer to cooperate in the claims investigation. They have to exchange information, including the driver’s precise log-on and log-off times in the day before the crash, and give a clear description of the coverage, exclusions, and limits under each policy.

Those disclosures are what let an injured person pin down which tier applies rather than take an insurer’s word for it.

The Deadline That Governs a Rideshare Claim

A rideshare injury claim runs on the same clock as any other car crash claim in Arizona. The personal injury statute of limitations is two years from the date of the crash under ARS 12-542. Miss it, and the claim is generally barred no matter how strong the coverage picture is.

One wrinkle can shorten that window sharply. If a government vehicle or a public entity is involved, ARS 12-821.01 sets a separate 180-day notice-of-claim deadline that runs long before the two-year statute and is a hard bar, not a formality.

A crash that involves a city or transit vehicle alongside the rideshare car can trigger it.

Arizona also follows pure comparative negligence under ARS 12-2505, so a rideshare driver’s or a third party’s share of fault reduces a recovery but doesn’t erase it. Sorting out fault, app status, and the governing coverage tier is work that rewards starting early, while the app records and scene evidence still exist.

When to Engage Counsel

A rideshare crash sits at the intersection of three insurance layers, a company that classifies its drivers as contractors, and a statute that changes the answer based on a fact the injured person usually can’t see: what the app was doing.

That combination is why these claims so often get routed to the wrong policy and settled short.

An Arizona rideshare accident lawyer can pull the driver’s app records, identify the tier that governs, evaluate the commercial and uninsured motorist coverage together, and hold the company’s insurer to the limits ARS 28-4038 actually requires.

For families deciding what to do in the days right after a crash, the guide on what to do after an Uber or Lyft crash lays out the practical steps that protect a claim while the evidence is still fresh.

For a review of a potential Uber or Lyft accident claim, contact the firm directly. Any case the firm accepts is handled on a contingency basis, which means no fee unless there’s a recovery, though a client may owe case costs and expenses.