Arizona Uber & Lyft Accident Lawyers

One in three rideshare drivers has been involved in a crash while working. That’s from a 2024 Journal of Safety Research study. Uber reported a 40% increase in fatal crashes between the 2019-2020 and 2021-2022 reporting periods, rising from 107 to 153 incidents. Lyft saw a 31% increase in motor vehicle fatalities, with 111 deaths in its most recent safety report.

Rideshare crashes don’t follow the same insurance rules as standard car crashes. The coverage available depends entirely on what the driver was doing at the moment of impact. Arizona law creates three distinct insurance tiers, and the difference between them can be the difference between $25,000 in coverage and $1,000,000.

The Three Insurance Tiers Under ARS 28-4038

Arizona’s Transportation Network Company statute, ARS 28-4038, sets the financial responsibility requirements for Uber, Lyft, and any other TNC operating in the state. The coverage changes based on the driver’s status at the time of the crash.

Under ARS 28-4038, either the TNC driver, the TNC itself, or both must provide the required coverage. In practice, Uber and Lyft carry the $1M policy for Tier 3 situations. During Tier 2, coverage is typically supplemental to the driver’s personal insurance.

Who Is Liable: The Driver, the TNC, or Both?

Uber and Lyft classify their drivers as independent contractors. This classification limits the companies’ direct vicarious liability for a driver’s negligence. You’re generally not suing Uber for what its driver did. You’re filing a claim against the TNC’s insurance policy that covers the driver.

During an active ride (Tier 3), the TNC’s $1M policy is the primary source of recovery when the rideshare driver is at fault. The driver’s personal policy may also apply, but the TNC coverage is the main target.

If a third party hits the rideshare vehicle, that at-fault driver’s insurance applies first. If the at-fault driver is uninsured or underinsured, the TNC’s UM/UIM coverage fills the gap during active rides.

Arizona preempts local TNC regulation under ARS 28-142. Cities and counties can’t impose additional requirements on Uber, Lyft, or their drivers. The state law is the only framework.

Arizona’s Pure Comparative Negligence in Rideshare Cases

ARS 12-2505 applies to rideshare crashes just like any other motor vehicle case. Arizona’s pure comparative negligence system means damages are apportioned by fault percentage. If the Uber driver was 70% at fault and the other driver was 30% at fault, each party’s insurance covers their percentage.

For passengers, comparative negligence rarely reduces the claim. Passengers don’t control the vehicle. Their fault percentage is typically zero. The question becomes which driver was more at fault and which insurance tier applies.

The 2018 Uber Autonomous Vehicle Fatality

On March 18, 2018, an Uber self-driving Volvo XC90 struck and killed Elaine Herzberg as she walked a bicycle across Mill Avenue in Tempe. She was 49 years old. It was the first known pedestrian death involving an autonomous vehicle in the United States.

The NTSB investigation found that Uber’s autonomous system didn’t recognize jaywalking pedestrians. The safety driver, Rafaela Vasquez, was watching Hulu on her phone instead of monitoring the road. Vasquez was charged with negligent homicide and pleaded guilty to endangerment in 2023.

Uber settled with Herzberg’s family for an undisclosed amount and suspended autonomous vehicle testing in Arizona after the crash.

The Herzberg case illustrates the complexity of autonomous vehicle accidents. Liability can involve the testing company, the safety operator, the vehicle manufacturer, and the software developer. Arizona remains a testing ground for autonomous vehicles, and the legal framework for AV crashes continues to develop.

What Makes Rideshare Claims Different

Standard car crash claims involve two drivers and two insurance policies. Rideshare crashes introduce additional parties, additional insurance layers, and coverage disputes that don’t exist in typical cases.

App status disputes are the most common point of friction. The TNC and its insurer may argue the driver wasn’t on an active ride when the crash occurred, shifting the claim from Tier 3 ($1M) to Tier 2 ($25K/$50K/$25K). GPS and ride log data is critical to establishing the driver’s exact status.

Multiple insurance carriers compound the problem. A single rideshare crash can involve the driver’s personal insurer, the TNC’s commercial insurer, the other driver’s insurer, and potentially your own UM/UIM carrier. Each company tries to minimize its share.

Common Rideshare Crash Scenarios

The Two-Year Deadline

Under ARS 12-542, the statute of limitations for rideshare accident claims is two years from the date of the crash. If a government entity is involved, the 180-day notice of claim under ARS 12-821.01 applies.

Two years sounds like plenty of time. It isn’t. Rideshare evidence lives on servers controlled by the TNC. Without a preservation letter or subpoena, that data has limited retention. App status at the time of impact is the single most important piece of evidence in a rideshare case, and it’s the easiest to lose.