Call For A Free Consultation(602) 345-1818
Call For A Free Consultation(602) 345-1818
Someone on their phone hit you. You knew it the moment you got out of the car. Maybe you saw the phone in their hand. Maybe they admitted it. Maybe they didn’t admit anything, but they never hit the brakes. This page explains exactly how a Phoenix distracted driving accidents lawyer builds these cases under Arizona law, why the evidence window closes fast, and what you should do in the first 48 hours to protect your claim.
Arizona’s handheld ban lives in A.R.S. § 28-914. In plain English: you cannot hold or physically support a cell phone or stand-alone electronic device while driving. Voice commands, hands-free Bluetooth, and a single tap to start or end a call are allowed. Holding the phone to text, scroll, film, swipe through music, or read a map is not.
The law has been in effect statewide as a primary offense since January 1, 2021. Primary enforcement matters. An officer can pull a driver over for the phone alone. They don’t need another violation.
This statute does two useful things in a civil claim. It defines the standard of care. And when the at-fault driver was ticketed under § 28-914, that citation becomes a piece of evidence about negligence. It is not automatic liability, but it is a strong starting point.
Most rear-end claims are about who was following too closely. The fault discussion is short. The fight is over injury value.
A distracted driving case is different in two ways.
First, the conduct is worse. A driver who was looking at their phone for the six seconds before impact is not just careless. They chose to stop watching the road. Adjusters know juries respond to that. The settlement posture changes.
Second, the evidence is fragile. Phone records, app activity logs, and carrier billing data are obtainable through subpoena under Rule 45 of the Arizona Rules of Civil Procedure. But carriers routinely overwrite or purge detailed cell-site and data-session records within 30 to 90 days. If nobody sends a preservation letter, that evidence is gone before the demand even goes out. Most rear-end claims do not require that kind of fast move. These cases do.
Nationally, distracted driving accounts for roughly 28% of rear-end crashes, according to NHTSA data. So most distracted-driving collisions look like ordinary rear-end accident claims in Phoenix on the police report. The difference is what’s underneath.
You almost never have one piece of evidence that wins a distracted-driving case. You have a stack of evidence, and the stack tells the story. The usual sources:
Phone records. Subpoenaed from the carrier. They show call and text timestamps and, often, data-session activity. A text sent thirty seconds before impact is powerful.
App activity logs. Subpoenaed from the platform (Snapchat, Instagram, TikTok, Waze, Google Maps, Spotify, WhatsApp). These show in-app actions with timestamps. Waze use is not illegal, but app interaction at the moment of impact still proves attention was elsewhere.
Dashcam footage. Yours, the other driver’s if they have one, or a nearby vehicle’s. Many newer vehicles also record short event-data clips when airbags deploy.
Vehicle event data recorder (EDR). The “black box.” Records pre-impact speed, throttle, and braking inputs. A driver who never touched the brake before a rear-end impact at 35 mph was not watching the road.
Witnesses. People in the other car. People in the cars around you. The driver themselves, who often admits the phone use at the scene before they have a lawyer.
Officer observations. What the responding officer wrote in the narrative section of the crash report. If you don’t have your report yet, here’s how to get your Phoenix crash report.
Social media. A driver who posted to Instagram thirty seconds before the crash created a timestamp the platform cannot quietly erase.
A spoliation letter (also called a litigation hold or preservation letter) is a formal demand sent to the at-fault driver, their insurer, their employer if it was a work vehicle, and sometimes the carrier directly. It tells them to preserve specific categories of evidence: phone, vehicle EDR, dashcam, employer-provided device logs, and so on.
If they destroy evidence after receiving a proper preservation letter, an Arizona court can instruct the jury to assume the destroyed evidence was unfavorable to them. That is a meaningful lever.
The problem is timing. Cell carriers do not retain detailed records forever. The retention windows vary by carrier and record type, but practically: detailed text content, cell-site data, and data-session logs often start dropping out of the system inside 30 to 90 days. Vehicle event data can be overwritten by the next ignition cycle if the airbag did not deploy. Dashcam loops overwrite themselves in days.
This is the single highest-leverage early move in a distracted-driving claim, and it has to happen in days, not weeks. Most claimants don’t know this. Most general-practice attorneys don’t move fast enough either.
Arizona uses pure comparative negligence, codified at A.R.S. § 12-2505. Under Arizona’s comparative negligence rule, your damages are reduced by your percentage of fault. The math: recovery = total damages × (100% − your fault %). If a jury finds you 20% at fault on a $100,000 case, you recover $80,000. If you are 90% at fault, you still recover 10%. There is no bar at 50% the way some other states have.
This matters in distracted-driving cases because adjusters reach for comparative fault constantly. The two most common arguments:
The fault presumption in a rear-end collision still cuts the right direction. The following driver is generally presumed at fault because they had the duty to maintain a safe following distance. Distracted-driving evidence reinforces that presumption. But you neutralize the adjuster’s comparative-fault arguments with concrete evidence: your phone records showing no activity, dashcam showing your brake lights came on with normal warning, EDR data showing reasonable speed.
The takeaway: do not assume your own phone records help only the other side. If you weren’t using your phone, those records actively prove you weren’t.
Distracted-driving rear-end crashes routinely produce:
A note on speed: IIHS crash testing data shows about 90% of rear-end crashes happen at impact speeds under 30 mph. People assume that means the injuries should be minor. They aren’t. Injuries occur even at impact speeds around 10 mph, because the struck driver isn’t braced. The body is loose, the head whips forward and back, and the cervical spine absorbs the force. Low property damage to your bumper does not mean low injury to your spine, and adjusters who argue “minor impact, minor injury” are using a sales script, not medical evidence.
ADOT crash data show predictable hotspots in the metro:
Surface streets aren’t immune. Camelback at high-traffic intersections, Bell Road across the north Valley, and downtown corridors near Roosevelt Row see the same pattern at lower speeds. Lower speed does not mean lower injuries.
The first two days set up the next two years.
They will call fast, usually inside 48 hours, sometimes inside 24. They will sound friendly. They will ask for a recorded statement.
You generally are not required to give a recorded statement to the other driver’s insurer. Your obligation is to your own insurer, and even that obligation depends on the cooperation language in your specific policy. Do not assume “cooperation” means “say whatever the other side’s adjuster wants you to say on tape.”
What you can do without a recorded statement: confirm the basic facts of the crash (date, location, vehicles involved), give your contact information, and tell the adjuster you’ll respond on substantive questions after you’ve gotten legal guidance. That is not stonewalling. That is normal.
What adjusters do with early statements: they use anything ambiguous against you. “I felt okay at the scene” becomes “claimant denied injury at the time of loss.” “I’m not sure exactly how fast he was going” becomes “claimant could not identify any speed violation.”
Arizona’s minimum liability limits, for policies issued or renewed beginning July 1, 2020, are 25/50/15: $25,000 bodily injury per person, $50,000 per accident, $15,000 property damage. A lot of Phoenix drivers carry exactly that. A distracted-driving crash with a serious injury can blow through $25,000 in medical bills alone.
Under A.R.S. § 20-259.01, Arizona insurers must offer uninsured (UM) and underinsured (UIM) motorist coverage. You can reject it in writing, but if you didn’t reject it, you have it.
If the at-fault driver has only minimum insurance or no insurance at all, UM/UIM on your own policy may be the only meaningful source of recovery. Pull your declarations page early. Know what you have. UM/UIM claims are first-party, meaning you’re now negotiating with your own insurer, who is supposed to be on your side and often isn’t.
Arizona’s punitive damages standard is strict. The Linthicum line of cases requires an “evil mind,” meaning conscious and deliberate disregard for the substantial risk that conduct will cause significant harm.
Garden-variety distracted driving usually does not meet that bar. But egregious phone use can. Documented examples that have supported punitive claims or strong settlement leverage: texting through an active school zone, livestreaming or filming while driving, prior phone-related citations on the same driver, or a commercial driver violating an employer’s explicit handheld policy.
Punitive damages are uncapped under Arizona law and are separate from compensatory damages. They are not insured against in most policies, which changes who is paying and how hard they negotiate. For more on the legal standard, see punitive damages in Arizona.
Distracted driving is not as instantly punitive-eligible as a DUI. DUI cases are the cleanest punitive-damages fact pattern in Arizona, which is why most drunk driving claims include them. Distracted-driving punitives require specific aggravating facts. We look for them.
You have 2 years from the date of the crash to file a personal injury lawsuit in Arizona under A.R.S. § 12-542. For background, see the Arizona statute of limitations rules.
But the 2-year deadline is not the real timeline. The real timeline is evidence preservation. Phone records start dropping inside 30 to 90 days. Vehicle EDR data can be overwritten in hours. Witness memory degrades in weeks. Surveillance footage from nearby businesses overwrites in 14 to 30 days.
A claimant who calls a lawyer at month 22 still has time to file. They no longer have most of the evidence that would have proven the other driver was on their phone. The case becomes a he-said-she-said about a citation on the police report, instead of a documented record of exactly what app was open at impact.
The framework is the same in every case, even if the facts aren’t.
Week one. Preservation letters out to the at-fault driver, their carrier, any employer if commercial, and the cell carrier. EDR preservation requested on the at-fault vehicle. Independent investigator dispatched if there’s any chance of dashcam or surveillance footage at the scene. Treatment plan locked in with the client.
Weeks two through four. Police report obtained and reviewed. Witness statements taken. Photo evidence catalogued. Medical record collection started. Adjuster contact managed through us, not the client.
Months two through six. Treatment progresses. Medical specials build. We do not demand on an open file. The demand goes out when treatment plateaus and the actual damages are known.
Demand and negotiation. Comprehensive demand letter with liability narrative, phone-evidence summary if developed, full medical specials, lost wage documentation, and non-economic damages analysis. Negotiation back and forth. Most cases resolve here.
Litigation if needed. If the offer doesn’t reflect the case, we file. Subpoenas for the phone records go out in formal discovery. Depositions. Mediation. Trial if necessary.
This is car accident cases in Phoenix the way they should be handled: by an attorney who knows the case, not by a paralegal at a volume shop.
Through a combination of sources: subpoenaed phone records, app activity logs, vehicle EDR data, dashcam footage, witness statements, the officer’s observations, and sometimes the driver’s own admission at the scene. No single piece usually does it. The stack does.
That happens. Officers don’t always document phone use, especially if the driver denies it and there’s no obvious phone visible at the scene. The police report is a starting point, not the final answer. Phone records can prove what the report doesn’t.
Yes, under Arizona’s pure comparative negligence rule. Your recovery is reduced by your percentage of fault, but you can still recover even if you were partly at fault. The question becomes how to limit your fault percentage, which is a fact-by-fact analysis.
Your UM/UIM coverage on your own policy may be the next source of recovery, if you carry it. We pull your declarations page early to know what’s available. If UM/UIM is in place, the claim shifts to your own insurer once the other driver’s limits are tendered.
No. Arizona’s punitive standard requires “evil mind” conduct, which is a high bar. Texting alone usually doesn’t meet it. Aggravating facts (school zone, prior citations, livestreaming, commercial driver violating policy) can change that analysis.
Two years from the date of the crash for personal injury in Arizona under A.R.S. § 12-542. But evidence preservation needs to start in days, not months. Waiting until month 22 to call a lawyer means most of the phone-record evidence is already gone.
If you were rear-ended in Phoenix by a driver who was on their phone, the most important thing happening right now is the clock on the evidence. Phone records, app logs, dashcam footage, and EDR data are on retention timers measured in days and weeks, not months.
Free case review: (602) 345-1818. We answer 24/7. No attorney’s fees unless we recover (case costs and fee terms are explained in the written agreement).
By Jared J. Pehrson | Impact Legal Car Accident Attorneys
We're Here To Help 24/7
(602) 345-1818