Phoenix Uber & Lyft Accident Lawyer

Updated January 2026 | Reviewed January 2026 for statutory accuracy | By Jared J. Pehrson | Impact Legal Car Accident Attorneys

Short answer: Up to $1 million in rideshare coverage may apply to your injuries under Arizona’s Transportation Network Company statute, but only if the driver had accepted a ride or had a passenger in the car at the moment of impact. If the app was on with no ride accepted, smaller contingent limits apply. Our team handles both Uber and Lyft cases out of our north Phoenix office, and the coverage analysis runs through the same TNC framework either way.

That single question, app status at the second of impact, decides whether your case sits on a state-minimum policy or has access to seven-figure coverage. Arizona’s TNC chapter is codified at A.R.S. § 28-9551 et seq., with the rideshare insurance minimums set out at A.R.S. § 28-9553. Proving which tier applies requires the trip log, GPS data, and ping timestamps, and that evidence ages out fast.

If you were a passenger, another driver hit by a rideshare vehicle, a pedestrian or cyclist struck by one, or the rideshare driver yourself, call before talking to any rideshare insurer: (602) 345-1818. Free case review.

For related guidance, see our Valley Metro and city bus crashes.

Handled by Jared J. Pehrson personally. Your Uber or Lyft case doesn’t get passed to a case manager or a rotating associate. Jared reviews the trip data, drafts the preservation letters, and negotiates directly with the rideshare carrier. That’s the whole point of hiring a boutique firm instead of a billboard shop.

For related guidance, see our Glendale rideshare crashes near State Farm Stadium page. Rideshare demand spikes on weekends, and we regularly handle Uber and Lyft crashes near ASU and Mill Avenue where late-night pickups and drop-offs concentrate.

On this page

1. Who pays when you’re hurt in an Uber or Lyft accident in Phoenix?
2. Uber’s $1 million liability policy: when it applies
3. Lyft accident claims in Phoenix
4. Uber vs. Lyft: are the claims different?
5. Rideshare passenger vs. rideshare driver: how the claim differs
6. UM/UIM coverage for rideshare passengers
7. Evidence to preserve in the first 72 hours
8. Rideshare driver as the injured party
9. What the rideshare adjuster asks first (and why)
10. What damages can rideshare passengers recover?
11. What if the rideshare driver was impaired or reckless?
12. When multiple parties share fault (comparative negligence)
13. Statute of limitations for rideshare accidents in Arizona
14. Phoenix rideshare crash hotspots
15. FAQ

Who pays when you’re hurt in an Uber or Lyft accident in Phoenix?

Rideshare insurance isn’t a single policy. It’s three tiers, and which tier applies turns entirely on the driver’s app status at the moment of the crash. Both Uber and Lyft operate under the same statute (A.R.S. § 28-9551 et seq.), with the insurance requirements at A.R.S. § 28-9553.

Period 0: App off (driver not working). The driver’s personal auto policy is the only thing in play. Under A.R.S. § 28-4009, Arizona’s minimum personal auto limits are $25,000 per person, $50,000 per accident, and $15,000 property damage (25/50/15). Neither Uber’s nor Lyft’s policies apply in Period 0.

Period 1: App on, no ride accepted. When the driver is logged in waiting for a request, A.R.S. § 28-9553 requires contingent liability coverage of $50,000 per person for bodily injury, $100,000 per accident, and $25,000 for property damage. “Contingent” means this coverage typically responds only if the driver’s personal insurance denies the claim, which most personal auto policies do for app-on driving unless the driver carries a rideshare endorsement.

Periods 2 and 3: Ride accepted (Period 2) or passenger in the car (Period 3). From the moment the driver taps “accept” until the trip ends in the app, A.R.S. § 28-9553 requires $1 million in third-party liability coverage, plus $1 million in uninsured/underinsured motorist (UM/UIM) coverage during the same periods. That UM/UIM piece matters: if you’re a passenger and a third-party driver causes the crash but carries no insurance or only the Arizona minimum, the $1M rideshare UM/UIM coverage may still apply to your injuries.

Here’s what most people don’t realize: the same crash can trigger different coverage depending on a 30-second difference in timing. If the driver accepted your ping at 9:14:32 and the crash happened at 9:14:50, you’re in Period 2 and the $1M policy applies. If the crash happened at 9:14:15, you’re in Period 1 and the cap is $50K per person. We pull the trip log to prove which one.

The three tiers, at a glance

• Period 0 (app off): Driver’s personal policy only. Arizona minimum under A.R.S. § 28-4009 is $25K/$50K/$15K.
• Period 1 (app on, waiting for a ping): $50K per person / $100K per accident / $25K property, contingent (A.R.S. § 28-9553).
• Periods 2 and 3 (accepted ride or passenger onboard): $1M third-party liability plus $1M UM/UIM (A.R.S. § 28-9553).

Which tier applies is a factual question decided by app timestamps, not by what the driver tells the responding officer or the adjuster.

Uber’s $1 million liability policy: when it applies

The $1 million figure isn’t a marketing claim from Uber. It’s the third-party liability minimum required by A.R.S. § 28-9553 for any transportation network company operating in Arizona during Periods 2 and 3. It applies the second the driver taps to accept a trip and stays in force until the passenger is dropped off and the trip ends in the app.

Uber doesn’t write this policy directly. The coverage is administered through commercial insurers Uber contracts with, and the specific carrier changes over time and by coverage period. The adjuster who calls you will identify as being from that commercial carrier, not from “Uber” itself. Either way, the adjuster’s role is to evaluate and resolve the claim within the carrier’s parameters. That’s not the same role as yours, which is to make sure the claim reflects what actually happened to you.

The $1M sits on top of, not in place of, other coverage that may apply. If a third-party driver caused the crash and carries usable liability limits, that policy may pay first with the rideshare policy in a secondary position. The order of payment matters when injuries are catastrophic and the value pushes past a single policy’s ceiling.

Lyft accident claims in Phoenix

Lyft operates under the same Arizona TNC chapter as Uber. A.R.S. § 28-9551 et seq. does not distinguish between the two companies, and A.R.S. § 28-9553 sets identical tiered minimums for every TNC licensed to operate in the state. We cover platform-specific detail on our Lyft-specific accident page as well.

That means the analysis for a Lyft crash mirrors an Uber crash:

• Period 0: Lyft’s coverage does not apply. Driver’s personal policy only.
• Period 1: $50K/$100K/$25K contingent liability under A.R.S. § 28-9553.
• Periods 2 and 3: $1M third-party liability plus $1M UM/UIM.

The differences are operational, not statutory. Lyft routes its claims through a different commercial carrier than Uber does, and the intake process starts inside the Lyft app rather than the Uber app. Trip logs, GPS pings, and app-status data are still the decisive evidence, but the preservation letter has to be addressed to Lyft’s legal department and the data-field requests have to match Lyft’s format.

If you’re not sure which platform you were riding, the trip receipt in your email or the ride history inside the app will confirm it. Both companies retain trip records for a limited window, so screenshot everything as soon as you can.

Uber vs. Lyft: are the claims different?

Both companies operate under the same statute, so the headline coverage structure is identical. If you ride both apps, the legal framework is the same.

What differs is how the claim moves once you’re in it:

A few practical differences worth calling out:

• Insurer of record. Uber and Lyft route claims through different commercial carriers, and the specific carrier can vary by coverage period.
• Claims portal and intake. Uber has its own incident-reporting flow inside the driver and rider apps. Lyft’s intake routes differently. Where the claim first lands affects how fast it reaches the adjuster.
• App data formats. Trip logs, GPS granularity, and the telematics each company captures are not identical. The litigation hold and preservation request have to be tailored to the platform.
• Driver onboarding records. Background-check documentation, deactivation policies, and prior-incident records are handled through different platform processes. That matters in the rare cases where corporate fault is on the table.
• Settlement posture. Every claim turns on its own facts, documentation, and the specific adjuster and carrier assigned. Two Uber cases and two Lyft cases can each look nothing alike.

Bottom line: the statute is the same, the coverage limits are the same, but the workflow to get from crash to resolution runs on different tracks depending on the platform.

Rideshare passenger vs. rideshare driver: how the claim differs

Most rideshare articles pretend the injured person is always a passenger. Two audiences actually walk into our office: passengers, and drivers who were on-app when they got hit. The framework for each looks similar on the surface but diverges in a few key places.

If you’re the passenger:

• Your claim runs primarily against whoever caused the crash. If the rideshare driver caused it, the $1M Period 2/3 policy is on the hook. If a third party caused it, you first look at their policy, then the rideshare $1M UM/UIM if the third party’s limits are too small.
• You are not a party to the driver’s independent-contractor agreement with Uber or Lyft, so arbitration clauses tucked into driver agreements don’t bind you.
• Your own auto policy’s UM/UIM may also stack on top depending on policy terms.

If you’re the rideshare driver:

• Your app status at impact still decides which tier of coverage applies to you.
• The $1M UM/UIM at Periods 2 and 3 is the coverage that most often responds to your own injuries when a third party caused the crash and is uninsured or underinsured.
• Rider agreement arbitration terms don’t apply to you, but you may have signed a driver agreement with the platform. That’s a separate document with its own dispute-resolution language.
• Workers’ comp is generally unavailable because rideshare drivers are classified as independent contractors under A.R.S. § 28-9551 et seq. The TNC insurance framework is the substitute.

Both audiences should ask the same first question: what was the app status at the second of impact?

How rideshare insurance compares to Arizona’s minimum coverage

Same passenger, same injury, different app status. That’s the scenario that shows why this matters.

Imagine you and a friend take an Uber home from a downtown Phoenix concert. Both trips end with a T-bone at the same intersection. Same speed. Same injury: a herniated disc that will need surgery and years of follow-up care.

• Trip A: You’re in the back seat, mid-ride, Period 3. The rideshare $1M third-party liability policy is available. If the third party who hit the Uber has minimum coverage, the $1M UM/UIM is also available. Your case sits on up to $1M in usable insurance from the rideshare side alone, plus whatever the third party carries.
• Trip B: The Uber driver had just dropped off the previous passenger and was app-on waiting for the next ping. Period 1. The rideshare policy is capped at $50K per person, and only contingent, meaning it may not respond at all if the driver’s personal policy takes the claim. If a third party hit the car and carries only Arizona’s $25K minimum, you’re looking at $25K plus whatever your own UM/UIM adds.
• Trip C: The Uber driver was off-app driving home. Period 0. Zero rideshare coverage. You’re looking at the driver’s personal 25/50/15 policy plus any UM/UIM you carry personally.

Same injury. Same intersection. Three completely different coverage pictures. That’s why proving app status is the first move in every rideshare case.

UM/UIM coverage for rideshare passengers

Uninsured and underinsured motorist coverage is the part of rideshare law many injured passengers hear about last, and it’s often the difference-maker.

A.R.S. § 28-9553 requires $1 million in UM/UIM coverage during Periods 2 and 3. Arizona’s general UM/UIM framework at A.R.S. § 20-259.01 governs how those coverages are offered and structured. Insurers must offer UM/UIM coverage, and a consumer can reject it only in writing. What that means in practice:

• You’re a passenger in an Uber or Lyft. A third-party driver runs a red light and T-bones the rideshare vehicle. The third-party driver carries no insurance, or only the Arizona minimum.
• Without UM/UIM, you’d be chasing an empty pocket. This is the same trap that catches so many injured people in ordinary uninsured driver scenarios.
• With the $1M rideshare UM/UIM coverage in place during Periods 2 and 3, you may be able to pursue a UM/UIM claim against the rideshare policy for your damages up to the policy limit, even though the rideshare driver wasn’t at fault.

Many injured rideshare passengers don’t hear about this coverage from the at-fault driver’s insurer, and it isn’t always front-of-mind for adjusters on the other side of the claim. It should be part of the analysis from day one.

What if the Uber or Lyft driver was uninsured on their personal policy?

This comes up mostly in Period 0 and Period 1 crashes. Most standard Arizona personal auto policies exclude losses arising from “livery” or “for-hire” use. A rideshare driver who never bought a TNC endorsement can find their personal insurer denying the claim the moment the log-in status hits the file.

For injured third parties or passengers, the practical answer depends on the period:

• Period 0: No rideshare coverage applies at all. The driver’s personal policy is the only source. If it’s been canceled, lapsed, or excludes the loss, the claim falls back on any UM coverage you carry personally.
• Period 1: The contingent $50K/$100K/$25K TNC coverage under A.R.S. § 28-9553 is designed for exactly this gap. If the personal policy denies, the contingent layer should respond up to those limits.
• Periods 2 and 3: The $1M third-party liability sits on the Uber or Lyft policy directly and is not contingent on the driver’s personal policy responding. Personal-policy exclusions don’t cut off your coverage.

Evidence that ages out: what to preserve in the first 72 hours

Rideshare cases live and die on data that either exists or doesn’t by the time the case is worked up. Some of it exists for weeks. Some exists for days. Some, for hours. The 72-hour window after a crash is where most evidence loss happens.

What to preserve immediately:

1. Screenshot the ride in the app. Open the Uber or Lyft app, go to your trip history, and screenshot the ride: origin, destination, driver name, timestamps, and receipt. Do it before the ride ages out of your visible history.
2. Save the email receipt. Both platforms email a trip receipt within minutes of a completed ride. Move it to a separate folder so it isn’t lost in inbox cleanup.
3. Photograph the scene, both vehicles, and any visible injuries. Wide shots and close shots. License plates. The rideshare decal on the windshield or bumper.
4. Get the police report number. 911 CAD (computer-aided dispatch) records include the exact time the call was placed, which anchors the app-status timeline down to the second. Phoenix PD releases the report typically 5 to 10 business days later. Request it early.
5. Identify nearby cameras. Businesses, garages, and residential doorbell cameras. Most private-business systems overwrite in 7 to 30 days. Some, in 72 hours. A quick canvass in the first day or two is often the difference between having video and having nothing.
6. Note witness names and phone numbers. Passengers, pedestrians, other drivers. People scatter fast.
7. Preserve your phone. Do not factory-reset or “clean up” your device. Location history, health-app step data, and text messages from the day can all become evidence.

What we send within days of getting hired:

• Preservation letters to Uber or Lyft demanding retention of trip data, driver logs, GPS pings, in-app messages, and background-check records
• Preservation requests to any identified surveillance sources
• Records requests for 911 CAD data and the responding officer’s body cam if applicable
• If a DUI is suspected, a request for the toxicology chain-of-custody records

The single biggest mistake we see is passengers assuming the rideshare company will “have the data whenever the lawyer wants it.” The data exists, but retention windows are not infinite, and the specific fields captured are only produced in response to a properly formatted request.

Rideshare driver as the injured party

Most rideshare content is written for passengers. It skips the scenario where the person hurt is the driver. That’s a real gap, because a rideshare driver in Period 2 or 3 who gets hit by an uninsured third party sits in a specific coverage situation with its own answer.

If you’re a rideshare driver hurt while working:

• Period 0 (app off, personal errand): Your personal auto policy. Nothing from Uber or Lyft.
• Period 1 (app on, no ping): Your personal auto policy first. If it denies (many policies exclude app-on driving without a rideshare endorsement), the contingent TNC policy at $50K/$100K/$25K under A.R.S. § 28-9553 may respond.
• Period 2 or 3 (accepted ride or passenger onboard): The $1M UM/UIM coverage under A.R.S. § 28-9553 is the key. If a third-party driver is at fault and either uninsured or underinsured, you as the rideshare driver may recover under that $1M UM/UIM policy for your own bodily injuries, up to the policy limit.

The driver-as-plaintiff scenario runs into a few recurring wrinkles:

• Personal policy exclusions. Most standard Arizona personal auto policies exclude losses arising from “livery” or “for-hire” use. Rideshare endorsements (sometimes called TNC endorsements) are sold by some carriers to fill Period 1 gaps. If you drive rideshare, review your declarations page for that endorsement.
• 1099 lost-income proof. Rideshare drivers are independent contractors under the TNC chapter, so lost wages have to be proved through 1099s, in-app earnings history, and tax returns rather than a W-2 or employer letter. Preserve those records.
• Workers’ comp is generally not available. Because platform drivers are classified as independent contractors, standard Arizona workers’ compensation typically doesn’t apply. The TNC insurance framework is the substitute.

If you were driving for Uber or Lyft when you were hit, the analysis of your own claim starts with the same question we ask passengers: what was your app status at the moment of impact?

What the rideshare adjuster asks first (and why)

The adjuster from the rideshare carrier will usually call within 24 to 72 hours. The voice is friendly. The tone is helpful. The questions follow a pattern