Call For A Free Consultation(602) 345-1818Free Case Review
-
Cities Served
-
T-Shirt Lawyer
Fighting Suits,
Not Wearing Them.Enter the universeStories, animation and community. Created by Impact Legal.
Call For A Free Consultation(602) 345-1818Free Case Review
Fighting Suits, Stories, animation and community. Created by Impact Legal.
We're Here To Help 24/7
(602) 345-1818A rideshare crash creates a question an ordinary car claim does not: what was happening in the app at the exact time of the collision? An Arizona rideshare accident lawyer can preserve that digital record, identify the driver and platform coverage stage, and test each liability theory against the evidence.
Arizona defines transportation network services in A.R.S. § 28-9551. The statutory definitions distinguish app availability, acceptance of a ride, transport to pick up a passenger, passenger occupancy, and completion. Do not infer status from a platform logo or an after-the-fact statement.
A.R.S. § 28-4038 sets insurance requirements for qualifying periods when a driver is logged in and when the driver is providing transportation network services. Those statutory requirements do not prove the actual policy, limit, exclusions, or insured status in one crash. The app timeline and policy documents must be matched.
For the statutory coverage rule, transportation network services begin when the driver accepts a trip request through the platform and end when the passenger exits or the trip is canceled. When a driver is logged in but not providing those services, the statute requires at least $25,000 per person, $50,000 per accident, and $20,000 for property damage in primary automobile liability coverage. When services have begun but no passenger occupies the vehicle, the required primary coverage rises to $250,000 per incident. With a passenger in the vehicle, it rises to $1 million per incident. The statute also requires uninsured and underinsured motorist coverage of at least $25,000 per person and $75,000 per accident, or the bodily-injury minimum in A.R.S. § 28-4009 if that is higher. These are statutory insurance floors for qualifying periods, not a promise that a particular policy, person, or claim has that amount available.
A screenshot captures one display, not necessarily the whole server record. A preservation request should identify the account, trip, time, location, and requested categories. We compare platform data with phone records, receipts, dispatch timestamps, and witness accounts rather than treating one item as conclusive.
Write down when the driver went online, received the request, accepted it, traveled to pickup, arrived, started the trip, and ended it. Compare those times with the collision, 911 call, receipt, passenger messages, and location history. A gap or conflict identifies the record that needs follow-up.
The timeline also helps separate platform work from another job or personal errand. That distinction can affect parties, coverage, and access to records. It should come from data and testimony, not an assumption based on a sticker or app installed on a phone.
The rideshare driver may be responsible for unsafe driving. Another motorist may have caused the collision. A vehicle owner, employer outside the rideshare relationship, maintenance provider, product maker, or public entity may matter when the facts support a separate duty.
The platform’s role requires a fact and law analysis. App status and a platform policy do not automatically prove an employment relationship or direct negligence. We identify the conduct at issue, the person or entity controlling it, and the evidence supporting that connection.
Under A.R.S. § 12-2505, damages may be reduced according to assigned fault. A.R.S. § 12-2506 generally uses several liability, subject to exceptions. In a rideshare crash, that makes it important to distinguish the driver who caused the event from the policy or company that may pay.
Video, route data, telematics, witness accounts, vehicle damage, and signal information should each be tied to a proposition. Location data may show where a device traveled but may not prove who handled it or why a maneuver occurred.
Potential sources include a driver’s personal policy, a platform policy required for the applicable stage, another driver’s policy, employer or commercial coverage, and applicable uninsured or underinsured motorist coverage. Personal policies may contain exclusions or conditions related to commercial or rideshare use. Platform coverage can depend on trip status.
We obtain the available declarations and policy language, identify the named and additional insureds, match the coverage period to the app record, and track every reservation of rights or denial. An insurer’s initial assignment of a claim number does not establish final coverage.
An injured passenger often has little role in causing the collision, but still needs proof of injury, causation, and coverage. An injured rideshare driver may face competing policy positions based on app status. A pedestrian, cyclist, or occupant of another vehicle may need to prove both the driver’s fault and the applicable rideshare stage.
Before signing a release, confirm that the record identifies every policy and preserves the digital status evidence. A quick settlement with one insurer can create problems if it releases another supported claim.
Save messages about pickup location, route changes, safety reports, cancellation, or a post-crash incident report. They may establish timing, notice, or the identities of people who received information. They do not automatically prove the platform controlled the driving decision at issue.
Keep the original account data and exported files when available. A cropped screenshot may omit timestamps or context. We request the underlying category when it bears on a disputed status or movement.
Keep records that show symptoms, findings, diagnosis, treatment, restrictions, and progress. Document actual effects on driving, work, sleep, mobility, concentration, household tasks, and caregiving. For a driver, app earnings and trip history may help establish income loss, but gross app revenue is not the same as net lost income.
A.R.S. § 12-542 generally provides two years after accrual for an injury action, subject to exceptions. A claim involving a public vehicle or roadway issue can trigger a 180-day notice under A.R.S. § 12-821.01 and the one-year period in A.R.S. § 12-821. Digital retention may be much shorter than any filing deadline.
We build a trip-status timeline, preserve app and vehicle evidence, identify drivers and supported business relationships, and match each policy to the relevant period. We organize medical and income proof, challenge unsupported fault or coverage assumptions, and explain what remains unknown before a release decision.
For broader Arizona injury rules, see our Arizona personal injury page.
No. The statutory floor changes by app stage, and actual coverage still depends on status, policy terms, insured status, and the facts.
Preserve the receipt, trip screen, driver identity, messages, route, and all claim numbers. Liability and coverage still require proof even when passenger fault is unlikely.
Preserve platform, phone, receipt, and witness evidence. A driver’s statement is one piece of the status analysis.
Yes, if the evidence supports that driver’s fault. Each party and policy should be evaluated before any release.
App history, tax records, expenses, and medical restrictions can help measure supported net income loss.
Find help for your city:
Free case review: (602) 345-1818.
A free conversation can help you understand your next step.