Call For A Free Consultation(602) 345-1818
Call For A Free Consultation(602) 345-1818
Updated November 2026 | Reviewed November 2026 | 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.
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.
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.
Which tier applies is a factual question decided by app timestamps, not by what the driver tells the responding officer or the adjuster.
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.
What that $1 million can cover:
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.
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:
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.
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:
| Factor | Uber | Lyft |
|---|---|---|
| Governing AZ statute | A.R.S. § 28-9551 et seq. | A.R.S. § 28-9551 et seq. |
| Period 2/3 liability (A.R.S. § 28-9553) | $1M | $1M |
| Period 2/3 UM/UIM (A.R.S. § 28-9553) | $1M | $1M |
| Commercial carrier | Contracted third-party (varies by period, changes over time) | Contracted third-party (different from Uber’s carrier) |
| App-data retrieval | Uber legal / in-app incident flow | Lyft legal / in-app incident flow |
| Trip-log data fields | Uber-specific format and granularity | Lyft-specific format and granularity |
| Driver classification | Independent contractor under TNC chapter | Independent contractor under TNC chapter |
A few practical differences worth calling out:
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.
The contrast matters because it explains why rideshare crashes that look similar can produce very different outcomes:
A passenger who suffers a serious cervical spine injury in a Period 3 Uber ride generally has access to $1 million in coverage. The same passenger walking home from that ride and getting hit by an off-duty Lyft driver in Period 0 is looking at the driver’s personal policy, which by default may be the statutory minimum. Same injury. Same person. Different rules. That’s why pinning down the app status is the first thing we do.
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:
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.
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:
What we send within days of getting hired:
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.
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:
The driver-as-plaintiff scenario runs into a few recurring wrinkles:
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?
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, and the pattern is not random.
“Can we record this call?” The recorded statement locks you into a version of events before you’ve seen the police report, the trip log, or your own medical records. Anything you say gets transcribed and becomes part of the file. “I’m doing okay” can be reframed as “claimant admitted minimal injury” three weeks later when you realize your back is actually a problem.
“Walk me through what happened.” You’re being asked to narrate a traumatic event from memory, on the phone, without the crash report in front of you. Small errors (which lane, which light cycle, which side hit first) become “inconsistencies” later.
“Where were you going and where did you get picked up?” This looks like small talk. It’s actually app-status framing. The adjuster wants to establish whether the trip was in Period 2 or Period 3, and whether the trip endpoints match what the trip log shows.
“Are you hurt? Have you seen a doctor?” If you say no or “not really,” that’s the answer that goes in the file. Many rideshare injuries (whiplash, concussion, disc injury) get worse over days, not hours.
“Would you like to resolve this quickly?” Fast offers are almost always low offers. They’re calculated to close the file before the picture is complete.
You don’t have to be rude to the adjuster. You don’t have to answer these questions on the spot either. Tell them you’ll follow up after you’ve had a chance to review your records and speak with counsel. Get the adjuster’s name, direct line, claim number, and carrier. Then call us.
Arizona law lets injured people recover both economic and non-economic damages in a rideshare case. The categories are the same as any car accident, but the coverage ceilings are usually higher because of the $1M Period 2/3 policy.
Economic damages. Out-of-pocket, receipt-backed losses. Medical bills already paid, medical bills yet to come, lost wages during recovery, reduced future earning capacity if the injury has long-term effects, and property damage. Every dollar has to be documented. Bills, pay stubs, employer letters, treatment plans.
Non-economic damages. Harm that doesn’t come with a receipt. Non-economic damages include pain and suffering, loss of enjoyment of life, emotional distress, disfigurement, and loss of consortium for spouses. Arizona jury instructions let the factfinder consider the severity of the injury, the length of recovery, and how the injury has changed the person’s day-to-day life.
Punitive damages. Rare, but possible in the right facts. Covered in the next section.
Claim value depends on injury severity, treatment history, liability proof, available insurance, and how well the damages are documented. Two passengers in the same crash can end up in very different places if one treated consistently and the other didn’t.
This scenario comes up more than people expect, especially in the downtown and Old Town corridors where late-night rides are a big share of the business.
Arizona allows punitive damages on top of compensatory damages when a defendant acted with an “evil mind.” Arizona case law, including the Arizona Supreme Court’s decision in Linthicum v. Nationwide Life Insurance Co., 150 Ariz. 326, 723 P.2d 675 (1986), sets out that standard. The short version: gross negligence alone isn’t enough. The plaintiff must show the defendant consciously disregarded a substantial risk of significant harm, or acted with a spite or ill will toward others. Whether the facts of a specific case meet that bar is a jury question.
Driving impaired can, depending on the facts, satisfy that bar. So can street-racing, deliberately blowing red lights, or extreme distraction while driving. In a rideshare context, punitive damages could be at issue when:
The TNC chapter itself requires background checks, ongoing driver record checks, and a zero-tolerance intoxication policy for platform drivers. When those requirements aren’t met, or when the platform receives complaints and doesn’t act, there can be a separate corporate-level argument. That’s a heavier lift and depends heavily on the facts.
One thing to keep straight: the platform’s internal deactivation of a driver is not the same as a legal finding of fault. Uber or Lyft can deactivate a driver for any number of reasons. A deactivation is useful evidence, not a substitute for proof. The reverse is also true: a driver who is still active on the platform can still be legally at fault for a crash.
If the crash involved a suspected impaired driver, request the police report and any DUI investigation records early. Toxicology results and the DUI charging decision are important pieces of the punitive-damages analysis.
Under A.R.S. § 12-2505, Arizona reduces damages in proportion to the claimant’s percentage of fault. Even if a jury assigns some fault
We're Here To Help 24/7
(602) 345-1818