Uber and Lyft Accident Lawyer in Phoenix, Arizona

How Rideshare Insurance Actually Works in Arizona

An Uber or Lyft crash is not handled the way an ordinary car accident is handled, and the reason is insurance. Coverage in these cases is not a single policy that either applies or does not. It is a layered program that switches on and off depending on what the driver's app was doing at the exact moment of impact. Arizona recognizes that structure by statute: A.R.S. § 28-9551 and the surrounding provisions of Title 28, Chapter 30 require transportation network companies and their drivers to carry specific minimum coverage during specific phases of app activity.

There are three periods, and almost every disputed rideshare claim in the Phoenix metro comes down to which one applies.

Period 0 — the app is off. The driver is running errands, driving home, or off shift. The rideshare company's commercial policy is not in play at all. The claim proceeds against the driver's personal auto liability policy exactly as it would in any other collision, subject to Arizona's minimum liability limits under A.R.S. § 28-4009. This is the phase where injured people most often discover that the at-fault driver carries state-minimum limits and nothing more.

Period 1 — the app is on and the driver is waiting for a ride request. The personal policy usually excludes this activity outright, because most personal auto policies contain a livery or public-conveyance exclusion. Arizona law fills the gap by requiring contingent liability coverage during this window, and both major rideshare companies publish contingent limits for this phase in the range of $50,000 per person and $100,000 per accident for bodily injury, with property damage coverage as well. The word that matters is contingent: this coverage sits behind the driver's personal insurance and typically responds only after the personal insurer denies or exhausts.

Period 2 — a ride has been accepted and the driver is en route to the passenger. Coverage steps up sharply. Once the driver accepts the trip request, the rideshare company's commercial liability program applies, and both Uber and Lyft publish $1,000,000 in third-party liability coverage for this phase.

Period 3 — the passenger is in the car, until the ride ends. The same $1,000,000 commercial liability limit applies, plus, in Arizona, uninsured and underinsured motorist coverage through the rideshare program and contingent comprehensive and collision coverage for the vehicle itself.

The practical consequence is blunt. The same crash, at the same intersection, with the same injuries, can be worth a state-minimum policy or can access a million-dollar commercial layer — and the only difference is the driver's app status. That is why the first question in one of these cases is never "how bad were you hurt." It is "what was the app doing."

Independent Contractor Status — and Why the Insurance Structure Answers It

Uber and Lyft classify their drivers as independent contractors rather than employees. That classification is deliberate, and it exists in large part to limit the companies' exposure to vicarious liability — the ordinary rule that an employer answers for the negligence of an employee acting within the scope of employment. When an injured person sends a demand to the rideshare company, the first response is often a version of the same sentence: the driver is not our employee, so we are not responsible for the driver's conduct.

That answer sounds like the end of the case. It usually is not, and the reason is the insurance program described above. Arizona's transportation network company statutes do not resolve the employment question, but they do require the coverage to exist regardless of how the driver is classified. The commercial liability policy responds to the driver's negligence during covered periods whether the driver is called a contractor, a partner, or anything else. In other words, the classification argument controls who the named defendant is; it does not, by itself, control whether coverage is available to pay the claim.

There are still situations where the company's own conduct matters independently of vicarious liability. Direct negligence theories — negligent screening, retention of a driver the company knew or should have known was unfit, or defects in how the platform itself functioned — are evaluated on their own facts and are not defeated by the contractor label. Those theories require real evidence rather than assumption, and they are investigated, not assumed.

The more common practical fight is narrower and more useful: whether the coverage period the company assigned to the crash is the correct one. Insurers assign the period from the company's own trip data. When that assignment is wrong — or when it is based on an incomplete record — the difference in available coverage can be enormous. Challenging that assignment is often the single most valuable thing that happens in a rideshare case.

Who Can Bring a Claim: Passengers, Other Drivers, Rideshare Drivers, Pedestrians

Injured passenger. This is the strongest position in a rideshare case. A passenger is almost never at fault for the collision, which means the comparative fault fight that dominates most auto cases largely disappears. During an active trip, the $1,000,000 commercial layer applies. If the rideshare driver caused the crash, the claim goes to that layer. If another motorist caused it, the claim goes first to that motorist's liability insurance, and the rideshare program's uninsured/underinsured motorist coverage sits behind it when the at-fault driver has no insurance or not enough of it. A passenger does not have to choose between those paths at the outset; both are pursued and the recovery is coordinated.

Another driver hit by a rideshare vehicle. Here everything depends on app status, and you have no way to observe it from inside your own car. A driver who has just dropped off a passenger and gone offline is in a completely different coverage world from one who is thirty seconds into a pickup. Because that determination is made from the company's records rather than the police report, this is the scenario in which preserving trip data early matters most.

A rideshare driver injured on the job. Drivers are not covered by Arizona workers' compensation through the platform, because of the contractor classification. What a driver does have is the platform's contingent and commercial coverage depending on period, the driver's own personal policy and any rideshare endorsement purchased for it, the at-fault motorist's liability insurance, and the driver's own uninsured/underinsured motorist coverage. Sorting the order of those layers is the entire case. Drivers should also confirm whether they added a rideshare endorsement to their personal policy — without one, the personal insurer may deny a Period 1 claim outright and may even challenge coverage for personal use if it learns the vehicle was being used commercially.

Pedestrians and cyclists. A person struck by a rideshare vehicle stands in the same position as any other injured non-occupant and accesses whichever coverage period applies to the driver at impact. These cases carry the most severe injuries and the fewest witnesses to app status, which makes the electronic record decisive. If you were on foot or on a bicycle, our pedestrian and bicycle accident page covers the right-of-way rules that usually drive liability.

Proving Driver Status: Trip Records, App Data, and Preservation

The evidence that decides a rideshare case is mostly electronic, mostly held by a company that is not your insurer, and mostly subject to retention schedules that were not written with your claim in mind. The categories that matter:

• Trip records. Request time, acceptance time, pickup and drop-off timestamps, the route driven, and the fare. These establish where the driver was in the trip cycle at the moment of impact.
• Driver status logs. The app's own record of when the driver went online, went offline, accepted, cancelled, and completed. This is the record insurers use to assign the coverage period.
• GPS and telematics. Location traces and, in some cases, speed and hard-braking events captured by the app or by a connected device.
• In-app communications. Messages and calls between driver and passenger before pickup.
• Ratings, complaints, and deactivation history for the driver, where the platform's own knowledge is relevant.
• The ordinary evidence too: the Arizona crash report, scene and vehicle photographs, dash camera footage, nearby business and doorbell video, 911 audio, and the treating medical records that tie the injuries to the collision.

Preservation is time-sensitive and mostly one-directional: once a retention window closes, the data is gone and no amount of later diligence brings it back. Written preservation demands go out to the rideshare company, the driver, the driver's personal insurer, and any third party holding video. Nearby surveillance video is often overwritten within days, and that footage is frequently what corroborates the electronic record.

What you can do in the first hours makes a real difference. Screenshot your trip in the app, including the driver's name, vehicle, license plate, and the trip receipt. Report the crash through the app so it enters the company's own incident record. Photograph the vehicles, the roadway, and any visible injuries. Get the responding officer's name and the report number. And get evaluated medically the same day, because a delay in treatment is the first thing an adjuster uses to argue that the injury came from something else. For more on how insurers handle those early conversations, see should I talk to the insurance adjuster.

UM/UIM Layers Inside the Rideshare Program

Uninsured and underinsured motorist coverage is where rideshare claims are quietly won or lost. Both major platforms provide UM/UIM coverage in Arizona during the periods when a passenger is on board or the driver is en route to a pickup. That coverage exists precisely for the situation the liability layer cannot fix: the at-fault driver is someone else, and that someone else has no insurance or carries limits far below what the injuries are worth.

A passenger in an Uber or Lyft struck by an uninsured driver is therefore not out of options. The rideshare program's UM coverage responds. When the at-fault driver has insurance but not enough — the far more common scenario in Arizona, where minimum limits are low relative to the cost of a hospital stay — the UIM layer can be reached after the liability limits are addressed, provided the sequence is handled correctly.

That sequence has traps. Settling with the at-fault driver's liability insurer before notifying the UIM carrier and obtaining written consent can jeopardize the UIM claim entirely, because the UIM carrier loses its subrogation rights against the at-fault driver. This is one of the most common self-inflicted losses in Arizona injury practice, and it happens most often to people who accepted a quick offer while still in treatment.

Stacking is another question worth asking. An injured passenger may also have UM/UIM coverage under a personal auto policy, and a rideshare driver may have coverage under a personal policy that includes a rideshare endorsement. Whether those policies can be reached, and in what order, depends on the specific policy language and on Arizona's rules governing other-insurance and anti-stacking clauses. Every available policy — the rideshare program, the personal policy, a household relative's policy, an employer's policy if the trip was for work — is identified before anything is settled. Our car accident page covers the same coverage-stacking analysis for non-rideshare collisions.

Comparative Fault, Damages, and What a Claim Can Recover

Arizona applies pure comparative fault under A.R.S. § 12-2505. Each party is assigned a percentage of responsibility, and the injured person's recovery is reduced by that percentage. There is no fifty-percent bar as in many states: a plaintiff found seventy percent at fault still recovers thirty percent of the damages. That rule cuts both ways in rideshare cases, and it is why adjusters press so hard on questions like seatbelt use, distraction, or whether a pedestrian crossed mid-block.

Arizona also abolished joint and several liability in most circumstances, so each defendant generally pays its own share. Defendants may formally designate a non-party at fault within the deadline set by Rule 26(b)(5) of the Arizona Rules of Civil Procedure, which in rideshare cases is frequently used to point at a phantom vehicle, a second motorist, or the platform itself. Each designation has to be met with evidence. More on the mechanics at Arizona comparative fault.

Recoverable damages in an Arizona rideshare injury claim follow ordinary personal injury law: past and future medical treatment, lost income, lost earning capacity, pain and suffering, emotional distress, disability and disfigurement, property damage, and loss of consortium for a spouse or family member. Arizona's constitution prohibits statutory caps on compensatory damages in personal injury and wrongful death cases (Ariz. Const. art. 2, § 31), so the value of a case is set by the evidence rather than by a ceiling written into a statute.

Medical liens and reimbursement claims deserve attention before anything is signed. Health insurers, AHCCCS, Medicare, hospitals asserting liens under A.R.S. § 33-931, and med-pay carriers may all claim part of a recovery, and those claims are negotiated rather than simply paid. See how medical liens work.

If a rideshare crash caused a death, the claim is governed by Arizona's wrongful death statutes rather than by ordinary injury rules, and the categories of recovery and the people entitled to bring the claim are different. That framework is explained on our wrongful death page.

Deadlines and What We Do When We Take a Rideshare Case

Arizona gives most injury claimants two years from the date of the crash to file suit, under A.R.S. § 12-542. Missing that date ends the claim regardless of how clear the liability was. Shorter deadlines can apply. If a government vehicle or a public entity is involved, A.R.S. § 12-821.01 requires a written notice of claim within 180 days of the events, and § 12-821 shortens the filing deadline to one year. Claims involving a minor are generally tolled until the minor turns eighteen, but the evidence still disappears on the ordinary schedule, so waiting is not free.

Contractual deadlines matter too. Insurance policies contain their own notice provisions, and UM/UIM claims in particular carry notice and consent-to-settle requirements that can be breached long before the statute of limitations runs.

What we do:

• Send preservation demands immediately to the rideshare company, the driver, the personal insurer, and any business holding relevant video.
• Establish app status independently rather than accepting the insurer's period assignment, using trip records, GPS data, receipts, and driver status logs.
• Identify every available layer: commercial liability, contingent coverage, the driver's personal policy, the at-fault motorist's policy, UM/UIM under both the rideshare program and any personal policy, and med-pay.
• Handle all insurer communication. No recorded statement, no blanket medical authorization, no early offer accepted while treatment is ongoing.
• Document the injuries properly, including the mechanism of injury in the medical chart and an honest treatment of any pre-existing condition.
• Coordinate the UM/UIM sequence so that a liability settlement never destroys the underinsured claim.
• Negotiate liens and reimbursement claims before distribution so the net recovery reflects reality.
• File suit when the offer does not match the evidence.

We handle rideshare injury cases on a contingency fee. The consultation is free, we come to you anywhere in the Phoenix metro, and you owe nothing unless we recover. Call (602) 217-0000.