Can Speeding Be Second Degree Murder in Arizona? ARS 13-1104

When Does Speeding Become Second Degree Murder?

When the State can convince a jury that the circumstances manifested extreme indifference to human life. That is the whole difference. Manslaughter under A.R.S. § 13-1103(A)(1) is recklessly causing a death. Second degree murder under A.R.S. § 13-1104(A)(3) is also reckless conduct — but conduct creating a grave risk of death, under circumstances showing that indifference. The act can be identical. The felony class is not.

In Arizona courts prosecutors do not build that finding from the speed alone. They build it from accumulation: sustained extreme speed rather than a momentary lapse, racing another car, weaving through heavy traffic, a near miss the driver kept going after, or warnings from a passenger. For the offenses themselves, see our pages on vehicular manslaughter and second degree murder.

What Each Charge Actually Carries

Three homicide charges reach the same fatal crash. The conduct that separates them is a state of mind defined in A.R.S. § 13-105.

Below the homicide line, the charges are lesser but not minor. A fatal moving violation alone is a class 1 misdemeanor under A.R.S. § 28-672. Reckless driving under A.R.S. § 28-693 is a class 2 misdemeanor, and racing under A.R.S. § 28-708 becomes a class 6 felony with a mandatory ten days on a second conviction within twenty-four months. Ordinary criminal speeding sits below all of it.

How the State Builds the Case Against You

These files are assembled in a predictable order, and knowing it matters, because the evidence that decides your charge is gathered in the first days and then degrades.

A fatal collision is worked by a dedicated investigator, not the first patrol unit. The scene is documented with a total station, laser scanner or drone photogrammetry, fixing the debris field, tire marks, gouge marks and final rest positions. Every speed number that appears later is built on that map, so an error in it travels all the way through. Both vehicles are then impounded and inspected — brakes, steering, and tire size against the factory specification, which matters more than it sounds.

Next comes the module download, warrants for phones, carrier records and manufacturer telematics, and blood where impairment is suspected. Statements are taken early: at the roadside, in the ambulance, at the hospital. Defense attorneys commonly see those statements become the most damaging evidence in the file, because a driver in shock will estimate his own speed, describe what he saw, and apologize.

Only at the end does the State assemble the narrative that turns physics into a felony class — how long the conduct lasted, whether there were near misses, what the driving record shows, what was posted online. That narrative is what separates manslaughter from murder, and it is argument rather than measurement.

What the “Black Box” Actually Records

Juries hear black box and picture a flight recorder. It is neither. The event data recorder is a function of the restraint control module — the computer that decides whether to fire the airbags — and what it must capture is set by federal regulation at 49 CFR Part 563. It records no video, no audio, no GPS position, and on most vehicles no steering input. It does not know the speed limit and it does not know who was driving.

What it does record is powerful, and the State leads with it because it appears to speak for itself. It does, within limits the regulation itself sets out:

• It samples twice per second. For vehicles built before September 2031 — effectively everything on the road — Table I requires pre-crash data from -5.0 to 0 seconds at two samples per second. That is ten data points, not a continuous trace. What happened between samples was never recorded.
• The timestamps carry slack. Footnote 1 to that table states pre-crash and crash data are asynchronous, with a sample time accuracy requirement of -0.1 to 1.0 seconds. The regulation gives its own example: a point labeled T = -1 need only have occurred somewhere between -1.1 and 0 seconds.
• It is indicated speed, not measured ground speed. Section 563.5 defines it as speed indicated by a manufacturer-designated subsystem — derived, typically from wheel rotation. Under braking, wheel lock or lost traction, that diverges from true ground speed, and non-standard tires shift it systematically.
• Non-deployment records are fragile. Section 563.9(a) requires deployment-event memory to be locked against overwriting. Subsection (b) treats non-deployment events differently. Where no airbag fired, what happened to the car before it was imaged becomes a real question.
• The ignition counters expose the handling history. Table I requires both ignition cycle at crash and at download. The gap between those two numbers is how many times the vehicle was powered up in between — every one an opportunity for overwriting.
• The file may be incomplete. Table I carries a complete-file flag precisely because crash power loss can truncate a record, and multi-event counters exist because identifying which impact the data describes is frequently contested.

Where the Reconstruction Is Contestable

A reconstruction report reads like physics and its arithmetic is usually sound. What is contestable are the inputs the analyst chose before the arithmetic started. Skid-based speed calculations need a coefficient of friction for that surface on that day, and a published range is commonly substituted — move that assumed value slightly and the calculated speed moves with it, often across the line the State needs.

Crush-based estimates depend on stiffness coefficients for that model, and the uncertainty widens quickly for oblique or offset impacts or vehicles thinly represented in the data. Momentum analysis is highly sensitive to assumed impact and departure angles, which come from the scene map. Avoidability opinions rest on an assumed perception-reaction figure that is a range in reality, not a constant. And causation may not run through the driver at all — grade, signal timing, sight obstruction, another driver, a mechanical failure or a medical event can each explain a collision without any conscious disregard of risk.

How Tamou Law Group Defends These Cases

Pre-charge advocacy comes first. In Arizona courts the charging decision in a fatal crash is often still open for weeks while the reconstruction is written. That window is the point of greatest leverage, and it is when a defense reconstruction and an independent module examination can change which statute gets charged rather than argue about it afterward.

Then disclosure. We request the full reconstruction file, not the summary — the scene data, the assumed inputs, the raw module download and the imaging documentation, including the ignition-cycle counters. A single-number speed opinion should be tested for the range behind it.

Then the collateral analysis. The difference between these charges is not only sentencing exposure. Class of felony drives release eligibility, plea posture and the long-term consequences that follow a conviction, so any resolution has to be evaluated against the charge it resolves, not just the number of years attached to it.