An I-17 the Stack accident Phoenix drivers describe almost always starts the same way. A sudden merge. A car braking hard four lanes over. No room to react. The Stack is Arizona’s original stack interchange, opened in 1990 to connect Interstate 17, U.S. Route 60, and Interstate 10 just west of downtown Phoenix. It was the first of its kind in the state. More than three decades later, it still carries some of the heaviest freeway volume in the Valley. That mix of age, volume, and a genuinely complex ramp structure shapes almost everything about how a crash claim at the Stack gets built.
Why an I-17 the Stack Accident Phoenix Claim Looks Different
The interchange stacks four separate levels of roadway on top of each other. I-17/US 60 traffic threads through I-10 traffic without a single at-grade crossing. That design solved a real problem when it opened. It also means drivers merging between the freeways often have less distance to react than they would at a simpler cloverleaf. A 2007 Forbes study ranked the Stack among the twelve most congested interchanges in the country. Average daily volume through it has run well past 200,000 vehicles on the I-10 side alone. High volume, short merge zones, and four decks of traffic moving in different directions add up to a reliable recipe for rear-end collisions and sideswipes, especially during the evening commute.
Fault in an I-17 the Stack Accident Phoenix Case Uses the Same Rules
Nothing about the interchange itself changes how Arizona assigns fault. A.R.S. § 28-730 still requires a following driver to keep a distance reasonable for conditions. A rear-end collision in stop-and-go Stack traffic still tends to fall on the driver who hit the car in front. Arizona’s pure comparative negligence rule (see our guide to comparative negligence in Arizona) still applies if more than one driver contributed to the crash. A jury can divide fault by percentage instead of handing the whole loss to one side. What actually gets harder at the Stack is proving which of several tightly bunched vehicles caused the initial impact. A chain-reaction crash on a curved, multi-level ramp can involve four or five cars before anyone stops moving.
When ADOT Might Share the Blame — and When It Won’t
It’s not that the Arizona Department of Transportation is automatically liable just because the Stack is old and congested. Arizona law gives ADOT real protection for a road built to the engineering standards that existed at the time. A.R.S. § 12-820.03 shields a public entity from liability over a road’s design, as long as the plan conformed to accepted engineering standards when it was prepared. The Arizona Supreme Court confirmed in Glazer v. State (2015) that this immunity survives even when later traffic growth makes an old design look outdated by today’s standards.
What the statute doesn’t excuse is a failure to warn of an unreasonably dangerous condition, or ordinary negligent maintenance. A missing merge sign. A pothole ADOT knew about and never patched. A burned-out lighting section on a blind curve. Those are the real openings a Stack-area claim against the state usually has to work with — not the original 1990 design itself.
The Notice of Claim Clock Runs Faster Than You’d Expect
A claim naming ADOT or another state agency has to clear a hurdle most drivers never see coming. A.R.S. § 12-821.01 requires a formal notice of claim served on the public entity within 180 days of the crash. That’s not the standard two-year deadline under A.R.S. § 12-542 that applies to a claim against another driver — it’s far shorter. Miss that 180-day window, and the state portion of the case is generally gone, no matter how strong the underlying facts are. A claim against a private driver from the same crash can still proceed on the normal two-year clock.
The Bottom Line
Most I-17 Stack crashes never touch ADOT at all. They’re ordinary rear-end and lane-change collisions between drivers navigating a genuinely difficult merge, and they resolve through the same fault and insurance rules that apply to any Phoenix freeway crash. The interchange’s design mainly matters when a claim tries to reach the state itself, and that path is narrower and faster-moving than most people assume. Sorting out which of several vehicles actually triggered a chain-reaction crash — and whether any part of the claim realistically reaches ADOT — is usually where the real work of a Stack-area case sits.
Frequently asked questions
No. A.R.S. § 12-820.03 protects ADOT from design-based liability as long as the Stack’s 1990 design met the engineering standards in place at the time, even though traffic has grown enormously since.
Only 180 days from the crash under A.R.S. § 12-821.01 to serve a notice of claim on the state. That’s far shorter than the two-year deadline that applies to a claim against another driver.
The following driver, under A.R.S. § 28-730’s requirement to keep a reasonable distance. Arizona’s comparative negligence rule can still divide fault by percentage if more than one driver contributed.
A failure to warn of an unreasonably dangerous condition, or ordinary negligent maintenance, such as a missing sign or an unpatched pothole ADOT already knew about.
Ready to meet your legal match?
Right case, right lawyer, zero awkward first dates. Tell us what happened and we’ll introduce you to attorneys who actually fit.
Get MatchedKeep reading: Freeway Accident in Phoenix | Suing the Government in Arizona | Loop 202 South Mountain Freeway Accident Claims (coming soon)
This article is for general information only and is not legal advice. Laws and procedures involving public entities like ADOT change, and deadlines such as the 180-day notice of claim are strictly enforced. If you were hurt in a crash at the I-17 Stack or another Phoenix-area interchange, talk to a licensed Arizona attorney promptly to protect your rights.