Dangerous Road Conditions Lawyer in Phoenix, Arizona

The 180-Day Notice of Claim Is the Deadline That Ends Most of These Cases

If a public entity may share responsibility for the road where you were hurt, the single most important fact on this page is this: Arizona gives you 180 days — not two years — to serve a written notice of claim. A.R.S. § 12-821.01 requires that any person with a claim against a public entity, a public school district, or a public employee file a notice of claim with the person or persons authorized to accept service within 180 days after the cause of action accrues. A claim that is not filed within that window "is barred and no action may be maintained thereon."

Read that again, because it is unforgiving. It does not matter how catastrophic the injury is. It does not matter that the road condition was obvious, documented, and complained about for years. It does not matter that the ordinary personal injury deadline in Arizona is two years. If the notice is late against a government defendant, the claim against that defendant is over before it starts.

The statute also dictates the contents. The notice must contain facts sufficient to permit the public entity to understand the basis on which liability is claimed, a specific amount for which the claim can be settled, and the facts supporting that amount. Those three requirements are where notices die. A notice that describes the crash but never states a specific settlement amount is defective. A notice that states an amount but offers no facts supporting it is vulnerable. A notice that demands "an amount to be determined" or a range instead of a sum certain invites a motion to dismiss.

Service matters just as much as content. The notice must go to the person authorized to accept service for that entity — for a city, county, school district, or state agency, that is a specific office defined by statute and court rule, not the department that maintains the road and not the risk adjuster who called you. And when a public employee is a defendant, the individual employee must be served as well as the employer.

The practical consequence is that dangerous-road cases have to be identified early. In the first weeks after a crash, most people are focused on treatment and on the other driver's insurance. Nobody is thinking about whether the intersection's signal timing was defective or whether the shoulder drop-off that flipped the vehicle was a maintenance failure. By the time that question gets asked, months of the 180 days may already be gone.

One Year to Sue, Not Two — A.R.S. § 12-821

Serving a compliant notice of claim does not buy you the ordinary two-year statute of limitations. A.R.S. § 12-821 provides that all actions against a public entity or public employee must be brought within one year after the cause of action accrues, and that the cause of action accrues when the damaged party realizes he or she has been damaged and knows or reasonably should know the cause, source, act, event, instrumentality, or condition that caused or contributed to the damage.

So a dangerous-road case against a government defendant runs on two separate clocks that are both shorter than the norm: 180 days to serve the notice, and one year to file suit. Meanwhile, the private defendants in the same crash — the other driver, a trucking company, a construction contractor — are usually governed by the two-year deadline in A.R.S. § 12-542.

That split creates a trap. It is entirely possible to settle or litigate against the private driver on a normal timeline while the public-entity claim quietly expires. It also means the investigation into whether the road contributed cannot wait for the medical picture to stabilize. The engineering question has to be asked in parallel with treatment.

One more timing wrinkle matters: the statute conditions the deadline on when you knew or reasonably should have known the condition that contributed to the harm. That language is sometimes argued in cases where the roadway defect was not apparent at the scene — a signal malfunction, an obscured sign, a design issue discoverable only from plans. It is not a safety net to rely on. It is an argument, and the far better plan is to serve notice early.

Bus and transit claims run on exactly these same rules whenever the operator is a public system or a school district. See our bus accident page for how the deadlines apply there.

When the Road Itself Is Part of the Cause

Most crashes are explained entirely by driver conduct. Some are not. In a subset of cases the roadway environment made a routine mistake catastrophic, or created a hazard that a reasonable driver could not avoid. The conditions that come up repeatedly in Arizona:

• Design defects. Curve radius and superelevation that do not match the posted speed, sight distance too short for the approach speed, on-ramp merge lengths that force late lane changes, medians and turn lanes that put opposing traffic in conflict, and drainage that channels water across travel lanes.
• Missing, damaged, or obscured signage. A stop sign knocked down and not replaced, a curve warning removed during construction, a wrong-way sign that is not visible at night, or regulatory signs hidden behind overgrown vegetation.
• Broken or misprogrammed traffic signals. Dark signals, conflicting greens, signal heads knocked out of alignment, and inadequate yellow or all-red clearance intervals for the approach speed. Signal timing is recorded, and it is discoverable.
• Construction and work zone hazards. Unmarked lane shifts, missing channelizing devices, abrupt pavement edges between milled and unmilled surfaces, unprotected equipment and materials in the clear zone, and flagging operations that do not conform to the traffic control plan.
• Shoulder drop-offs. A vertical edge between the pavement and the shoulder can catch a tire and make recovery nearly impossible at speed. Drop-off cases frequently end as rollovers or as head-on collisions after overcorrection into oncoming traffic.
• Inadequate lighting. Unlit or under-lit intersections, crosswalks, and pedestrian crossings on high-speed arterials, and burned-out fixtures reported and never repaired. These conditions weigh heavily in pedestrian and bicycle cases.
• Vegetation and obstructions blocking sight lines. Untrimmed oleander and palo verde at a corner, temporary signage, and parked equipment that hides an approaching vehicle at a stop-controlled intersection.
• Failed roadside hardware. Guardrail end terminals that do not perform as designed, missing barriers on elevated or embankment sections, and fixed objects inside the clear zone.

The legal question is never simply whether the condition existed. It is whether the entity responsible for that road knew or should have known about it and failed to act within a reasonable time, and whether the condition was a cause of the harm. That is why the historical record at the location matters more than the photographs taken the day of the crash.

Who Is Actually Responsible for the Road

Arizona roadway responsibility is fragmented, and identifying the wrong defendant wastes the 180 days. Jurisdiction generally breaks down like this:

• The State of Arizona, through the Arizona Department of Transportation, for interstates and state routes — I-10, I-17, US 60, the Loop system, and state highways.
• Counties, for county-maintained roads in unincorporated areas.
• Cities and towns, for surface streets, arterials, traffic signals, signage, crosswalks, and street lighting inside municipal limits.
• Special districts and other public entities, including school districts for property and drop-off areas they control, and irrigation or flood control districts for facilities adjacent to a roadway.
• Private contractors — the construction company running the work zone, the traffic control subcontractor, the signal maintenance vendor, the landscaping company responsible for sight-line trimming.

That last category is critical, and it is good news for the injured person. A private contractor is a private defendant. It is not entitled to the § 12-821.01 notice requirement or the § 12-821 one-year deadline simply because its customer was a government agency. Its liability is ordinary negligence on the ordinary two-year clock, and it carries commercial liability insurance.

In practice, many work zone cases are strongest against the contractor, because the contractor accepted a written traffic control plan and either failed to implement it or deviated from it. The contract, the approved plan, the daily inspection reports, and the field diaries are the core evidence, and they exist.

Jurisdictional boundaries are not always where people assume. A street can change from city to county maintenance mid-block. A signal at a state-route intersection may be maintained by the city under an intergovernmental agreement. When responsibility is uncertain, the safe approach is to serve notice on every entity that could plausibly be responsible within the 180 days and sort out jurisdiction afterward.

Governmental Immunity: What It Does and Does Not Block

Arizona abolished blanket sovereign immunity, and public entities can be sued. But the legislature preserved defined categories of immunity, and any honest assessment of a dangerous-road case has to account for them up front.

A.R.S. § 12-820.01 grants absolute immunity for certain functions, including the exercise of a judicial or legislative function and the exercise of an administrative function involving the determination of fundamental governmental policy. The statute describes what counts as fundamental policy — determinations that require weighing competing objectives, the allocation of scarce resources among competing needs, and licensing and regulation choices. In roadway terms, a legislative decision about whether to fund a project is generally protected in a way that failing to repair a known hazard is not.

A.R.S. § 12-820.02 sets out qualified immunities that apply unless the public employee intended to cause injury or was grossly negligent. These cover a specific list of activities, and where one applies, the plaintiff's burden is significantly higher than ordinary negligence.

What this means in practice, stated plainly and without overpromising: how a roadway was designed and whether to build something at all are the areas where immunity arguments are strongest, and design cases often turn on whether the entity followed the standards in effect and whether it had notice that the design was performing badly in the real world. Maintenance, repair, and operational failures — a sign not replaced after a documented knock-down, a signal reported dead and not fixed, a work zone that departed from the approved traffic control plan, vegetation not trimmed on a schedule the entity itself set — are the categories where claims most often proceed.

Damages against public entities also have their own rules. Arizona's constitution prohibits statutory caps on damages for death or personal injury, but A.R.S. § 12-820.04 bars punitive and exemplary damages against a public entity or a public employee acting within the scope of employment. Punitive claims may still be available against private co-defendants such as an impaired driver or a contractor. See our punitive damages explainer.

None of this should be read as a prediction about a specific case. Immunity is applied to specific facts, and the right time to analyze it is at the beginning — during the 180-day window — not after the deadline has passed.

The Evidence That Builds a Roadway Case

Roadway claims are won on records, and most of the useful records belong to the entity you are making a claim against. Public records requests are the primary tool, and they take time — another reason the 180-day clock has to be started immediately.

• Prior complaints. Citizen reports, service requests, and 311-type call records about the same condition at the same location. A complaint log showing the sign was reported down three weeks before the crash converts a maintenance case into a notice case.
• Maintenance and work order history. Inspection schedules, what the entity's own policy required, when the location was last inspected, what was found, and what was done. Failure to follow the entity's own written maintenance standard is powerful.
• Crash history at the location. Reported collisions at the same intersection or segment, ideally in the same pattern. A history of the same type of crash at the same location is how a hazard is shown to be foreseeable rather than freakish. Our post on Phoenix intersections with high crash volume discusses how location history is analyzed.
• Design and construction documents. Plans, as-builts, design exception documentation, the standards in effect at the time of design or reconstruction, and any post-construction safety review.
• Traffic control plans for work zones, the approved plan versus what was actually in the field, daily inspection reports, and the contract between the entity and the contractor.
• Signal records. Timing sheets, controller logs, malfunction management unit data, and maintenance tickets.
• Physical evidence and the scene itself. Roadway conditions change fast — signs get replaced, drop-offs get paved, vegetation gets trimmed. Scene documentation, survey, drone and photogrammetry work, and nighttime photography under the same lighting conditions have to happen before the defendant fixes the thing you are complaining about.
• The vehicles and the reconstruction. Event data recorder downloads, tire and steering evidence, and a reconstruction that separates driver input from what the roadway environment made unavoidable.

Because Arizona applies pure comparative fault under A.R.S. § 12-2505, a road condition claim does not require proving the driver did everything perfectly. Fault can be apportioned between a driver and a public entity in the same case. See our comparative fault explainer.

What We Do When We Take a Dangerous Road Case

• Identify every potentially responsible entity in the first days — state, county, city, district, and every private contractor working the location.
• Calendar the 180-day notice deadline and the one-year suit deadline immediately, and work backward from them rather than toward them.
• Prepare a notice of claim that satisfies § 12-821.01 on its face: the facts supporting liability, a specific sum for settlement, and the facts supporting that sum — served on the officer authorized to accept service for each entity, and on individual employees where they are defendants.
• Send preservation letters for signal data, maintenance records, video, contractor field records, and the vehicles.
• File public records requests for complaint history, work orders, inspection logs, crash history, design plans, and traffic control plans.
• Document the scene before it changes, including nighttime and same-conditions photography, survey, and measurement of any drop-off, sight obstruction, or signage placement.
• Retain the right experts — a traffic engineer or highway design specialist, a reconstructionist, and a human factors expert where perception and reaction under the actual conditions are in dispute.
• Pursue the private defendants in parallel on ordinary deadlines, including the at-fault driver and any contractor, so no recovery source is lost while the public claim is developed.
• Handle all insurer and risk-management communication. No recorded statement, no blanket medical authorization. See talking to the adjuster.
• Resolve medical liens and reimbursement claims before distribution — see how medical liens work.

We handle these cases on a contingency fee. The consultation is free, we advance case costs including expert and records costs, and you owe no fee unless we recover. Call Saguaro Injury Law at (602) 217-0000.