Arizona Crash Report: How to Get Yours and Read Every Code
An Arizona crash report is ADOT’s three page form 01-2704. The officer must write it within 24 hours of finishing the investigation, and you get it from that officer’s agency: $9 from DPS for a state highway crash, no charge for a digital copy from Phoenix police. Its blocks are filled with numbered codes. Below, all 300 are decoded, and so is Unit 1, which ADOT defines as the unit that caused the crash or was most at fault.
- 1Traffic unit numbers
- 2Injury severity, belts, airbags
- 3Insurance and policy number
- 4Citations, block 10
- 5Violations, block 22
- 6Conditions, distraction, impairment
- 7Diagram and narrative
Code decoder
Look up any code on your Arizona crash report
Find the block the code sits in: on page 2 that is the big printed number from 12 to 27, on page 1 it is the column heading, such as IS for injury severity. Pick it below and type the number the officer checked or wrote. The lists that matter most to an injury claim are one tap away.
Violations or Behavior, page 2, block 22
Type a code from your report to see what it means.
Codes in this list
The decoder reads ADOT’s form revised January 2022 and the officers’ manual of August 2023. A report printed by an agency’s own software may show the words instead of the numbers; the meanings are the same.
Got your Arizona report? Tell us what happened and get a free case review in about a minute.
Step by step
How to get a copy of your Arizona crash report
Arizona has no single statewide shop for crash reports. Each report stays with the agency whose officer investigated, and that agency sends a copy to ADOT’s Traffic Records Section for the state crash database (A.R.S. § 28-667(C)). So the first question is who came: a Department of Public Safety trooper on a freeway or state highway, a city officer inside city limits, or a sheriff’s deputy elsewhere in the county.
| Agency | Where to ask | Cost | Good to know |
|---|---|---|---|
| Arizona Department of Public Safety (state troopers) | Public Services Portal, psp.azdps.gov: Request a Report or Records | $9 by email or the portal | Needs the full incident number: a capital I and 8 digits, no hyphens. Most requests are filled within about 48 hours; reports with supplements or attachments, and fatal crash reports, go to a person and take longer. |
| Phoenix Police Department | Police public records portal, phxpublicsafety.phoenix.gov, record type Traffic Crash | No charge for a digital copy on a personal request; $0.25 per printed page; $10 plus pages for commercial requests | Fees in effect since November 2, 2026. Requests are handled in the order received; the unit answers questions at 602-534-1127. |
| Tucson Police Department | Crashdocs (crashdocs.org), where the department posts its collision reports | Shown at checkout | Records Section, 270 S. Stone Ave., Tucson. |
| Mesa Police Department | LexisNexis online, with the departmental report number (DR) and the crash date | $2.60 when the name on your card is on the report; $5 directly from Mesa police | Other buyers pay an added convenience fee. Fatal crash reports and related reports, such as a DUI report, are not online. |
| Maricopa County Sheriff’s Office | LexisNexis (BuyCrash) online | Paper copy $5 for the first ten pages | Allow seven business days for the upload. Serious injury, fatal and criminal cases are not online; call the Departmental Reports Section, 602-876-1078. |
| Any other city, county or tribal police | The agency’s records unit | Set by the agency | Give the crash date, the location and the agency report number if you have it. |
Fees and steps from each agency’s own records page, checked November 10, 2026.
- Find the agency and the number. If the officer gave you a card or a slip, it carries the agency’s name and its report number. A DPS incident number starts with the letter I.
- Give it time. The officer must write the report within 24 hours of finishing the investigation (§ 28-667(A)), but an investigation can run for weeks. ADOT’s manual notes that a crash with a death or a serious injury, where felony charges may follow, can hold a report open far longer.
- Ask for the unredacted copy. As a person involved, you are entitled to it on request (§ 28-667(C)). The version anyone can buy hides the personal details a claim depends on.
- Count the sheets. ADOT tells officers to print the same report ID on every page and to fill in the Total Number of Sheets box at the top. Pages A, B and C make one report; a Truck/Bus Supplement, a Fatal Supplement or an Occupant Supplement adds sheets. Check that the number you received matches.
Who can get the full report
| Who | What the law gives them |
|---|---|
| A person involved in the crash, the owner of a vehicle in it, or their representative | An unredacted copy on request |
| An insurer of a person or vehicle involved | An unredacted copy on request |
| An attorney or licensed private investigator who represents a person involved | An unredacted copy, with the victim’s personal identifying information removed first if a criminal complaint has been issued (§ 28-667(D)) |
| An insurance support organization | An unredacted copy on request |
| Anyone else | A redacted public record |
An agency can refuse an unredacted copy when releasing it would harm a criminal investigation (§ 28-667(E)). Agencies also may not release reports for a commercial solicitation purpose and may ask for a sworn statement of why you want one (§ 28-667(C)); the statute defines that purpose as a request with no relationship to anyone in the crash, made only to seek business (§ 28-667(H)). If you were the victim of a Part 1 crime, such as an aggravated assault, A.R.S. § 39-127 gives you one copy of the report free, and DPS extends it to the victim’s attorney or family when the victim was killed or incapacitated.
Full or partial
The $2,000 line: full report or partial report
Arizona officers write one of two reports. A full report is required when the crash injured or killed someone, caused property damage over $2,000, or led to a citation (§ 28-667(A)). Below that line, with nobody hurt and no ticket, the officer writes a partial report.
All three pages: the vehicle and person blocks, the violations and conditions on page 2, the diagram and the narrative.
A.R.S. § 28-667(A)At least the date and time, the place, who was involved and any witnesses, a short account, a simple diagram, and the officer’s name, agency and ID number.
A.R.S. § 28-667(B)Page 1 shows which side of the line the officer saw. The total counts every vehicle and any public or private property, and any injury from Possible Injury up marks it Over.
ADOT manual, element 2dADOT’s definition of a reportable crash centers on public roads, but a fatal crash on private property still gets a crash report and a Fatal Supplement.
ADOT manual, General InstructionsIf the damage looked small at the scene and an injury showed up later, the report you get may be the partial kind. It still names the drivers and records where and when the crash happened, which is what your insurer and theirs need first. The medical records carry the injury from there.
No officer at the scene
When police did not come to the crash
Arizona law puts the first steps on the drivers. A driver in a crash that injures or kills someone, or damages a vehicle someone is driving or attending, must give their name, address and vehicle registration number, show their license on request, and give reasonable help to anyone hurt, including arranging a ride to medical care when it is needed or asked for (A.R.S. § 28-663). When anyone is injured or killed, the driver must also notify the police at once by the quickest means: the city police inside a city, otherwise the county sheriff or the nearest highway patrol office (§ 28-666).
When no officer came, ask the agency for the area whether it will take a report after the fact. ADOT’s form has a box for exactly this, Investigated At Scene: the answer No marks what the manual calls a counter report, made by a driver at the agency’s office. Then build your own record the same day:
- Photos of both vehicles, the plates, the damage, the road and any skid marks or debris.
- The other driver’s name, address, license, registration and insurance card.
- Names and phone numbers of witnesses before they leave.
- Your own notes of the time, the place and what each driver said.
Where to look
Seven places on an Arizona report that matter most to an injury claim
The form is three pages. Page 1 identifies the crash and gives one block to each traffic unit; page 2 holds the coded blocks 12 to 27 about the road and what each unit did; page 3 holds the diagram and the narrative. These seven places carry what bears on fault, injury and insurance. The numbers match the drawing at the top of this page.
Traffic Unit No.
Page 1, block 5, the top of each unit block
Each vehicle, pedestrian and cyclist is a numbered traffic unit, and ADOT’s manual tells officers that Unit 1 is the one that caused the collision or was most at fault. Block 2 has a Hit/Run box with the number of any unit that fled. A parked vehicle is a unit with the Driverless box checked.
Injury Severity, safety devices and airbags
Page 1, the IS, SD and AB columns in blocks 5 and 6
Each driver and passenger gets an injury code from 1, No Injury, to 5, Fatal, with the belt or helmet they used and whether an airbag went off at their seat. ADOT’s manual tells officers to base the injury code on the latest information they have when the report is completed.
Decode the IS columnInsurance company and policy
Page 1, block 5, the last line of each unit block
The insurer’s name as printed on the proof of insurance card, not the local agent, with the company’s phone number, the policy number and its expiration date. It appears only on the unredacted copy, and it tells you where to file.
Citation
Page 1, block 10
Each citation is listed by unit number with the A.R.S. section or city code, such as 28-730 for following too closely. By ADOT’s instruction the block names the unit, not the person ticketed. A citation is a charge; a court decides it.
Read the common citationsViolations or Behavior
Page 2, block 22
For every unit the officer checks each violation that applies, from 1, No Improper Action, to 20, Failed to Yield Right of Way, and 49, Aggressive Driving. This is the block that says what the officer believes each driver did wrong.
Decode block 22Conditions, distraction and impairment
Page 2, blocks 19, 20 and 21
Block 19 records road, weather or vehicle conditions that may have contributed, such as sun glare or a work zone. Block 20 records distraction, from talking on a phone to texting. Block 21 records impairment, with boxes for a drug recognition expert’s evaluation and an arrest.
Decode block 20Diagram and narrative
Page 3, blocks 28 to 30
A sketch of the scene with a north arrow, marked either as approximate and not to scale or as drawn to a stated scale, and the officer’s written summary. A vehicle that caused the crash without touching anyone is not a unit in Arizona; look for it here, in the narrative.
Unit 1
Is Unit 1 the driver at fault in Arizona?
On Arizona’s form, Unit 1 is meant to be exactly that. ADOT’s instruction manual tells officers: “Traffic Unit #1 is the vehicle, pedestrian, pedalcycle that caused the collision or was most at fault.” Being listed as Unit 2 is the first sign the officer saw the crash your way.
It is still the officer’s assessment on the day, not a finding a court made, and three details of the form shape how it reads:
- A pedestrian or a cyclist can be Unit 1. The definition covers any traffic unit, so a person who stepped out mid block can be listed first, with the vehicle that hit them as Unit 2.
- A driver who never touched anyone is not a unit. The manual says non contact vehicles are not listed as units but should be named in the narrative. If a car cut you off and fled without contact, it will not appear in the unit blocks at all.
- The speed limit follows Unit 1 at an intersection. For a crash inside an intersection, the posted speed limit entered is the one for the unit most at fault.
Read Unit 1 together with block 22 for each unit and block 10. A Unit 1 with 20, Failed to Yield Right of Way, and a citation under 28-772, against a Unit 2 marked 1, No Improper Action, is a report that points one way.
Fault
Does the police report decide fault in Arizona?
No. Arizona is a pure comparative fault state, and its law leaves the question of a claimant’s own fault to the jury in every case (A.R.S. § 12-2505). The report is evidence, often the first evidence an adjuster reads, but it is the officer’s view, not a verdict.
Pure comparative fault means your damages are reduced by your share of the fault, whatever that share is, and are never cut off entirely by it (§ 12-2505(A)). A driver found 70 percent at fault can still recover 30 percent of their damages from the other driver. That is why every box against you is worth answering with evidence, and every box against the other driver is worth pointing to.
| What the report shows | What it means | Where the rule comes from |
|---|---|---|
| Traffic Unit 1 | The unit the officer saw as causing the crash or most at fault | ADOT manual, element 5a |
| Block 22, code 1, No Improper Action | The officer judged that unit did nothing wrong | ADOT manual, element 22 |
| Other block 22 codes, all that apply | What the officer believes each unit did wrong | ADOT manual, element 22 |
| Block 19 | Road, weather or vehicle conditions that may have contributed | ADOT manual, element 19 |
| Block 10, a citation | A charge under a state law or city code; a court decides it | ADOT manual, element 10 |
| Narrative and diagram | The officer’s own account and sketch | ADOT manual, elements 28 to 30 |
Other evidence counts as much: photos, dashcam or traffic camera video, witnesses, the damaged areas circled in block 7, the vehicles’ event data, and your medical records. ADOT’s own 2024 numbers show how often the report points away from a driver: officers marked No Improper Action for 116,269 of the 236,193 drivers in crashes, almost exactly half.
Block 10
Common citation numbers on an Arizona crash report
Block 10 lists each citation by unit and by the section of Title 28 of the Arizona Revised Statutes, or a city code. These are the sections that appear most often after a crash between vehicles, with what each one requires.
| A.R.S. section | Its title | What it requires |
|---|---|---|
| 28-701(A) | Reasonable and prudent speed | No faster than is safe for the road, the traffic and any hazards, and slow enough to avoid hitting anyone |
| 28-730(A) | Following too closely | A safe gap behind the vehicle ahead, given speed, traffic and the road |
| 28-772 | Vehicle turning left at intersection | A left turning driver yields to oncoming traffic that is in the intersection or close enough to be an immediate hazard |
| 28-645(A)(3) | Traffic control signal legend | Stop for a steady red signal and wait for a signal to go, apart from the turns the law allows |
| 28-855(B) | Stop signs; yield signs | Stop at the stop line or crosswalk, or where the cross traffic can be seen |
| 28-773 | Intersection entrance | After the stop, yield to vehicles in or close to the intersection |
| 28-729(1) | Driving on roadways laned for traffic | Stay within a single lane and leave it only when that can be done safely |
| 28-4135(C) | Motor vehicle financial responsibility requirement | Show proof of insurance to an officer investigating a crash |
| 28-1381 | Driving under the influence | The DUI law; block 21 then usually shows code 4, Alcohol, or a drug code |
Section titles from the Arizona Revised Statutes, Title 28, as published by the Arizona Legislature. A citation for no proof of insurance means proof was not shown when asked, which is not the same as having no policy.
Mistakes
When your Arizona crash report is wrong
Corrections start with the agency that investigated. ADOT keeps the statewide copy for its crash database, but the report is the agency’s, and only its officer or records unit can amend it.
- Get the unredacted copy and mark each error: a wrong name, address or insurer, the wrong unit number on a violation, a wrong direction or lane, an injury code that does not fit.
- Gather proof for each one: your insurance card, photos, the repair estimate, dashcam video, a witness’s name and number, the emergency room record.
- Contact the agency’s records unit with the report number and ask how it handles a request to review or supplement a report. A missed witness or passenger can be added: ADOT’s Occupant Supplement exists to list passengers, citations and witnesses that did not fit on page 1.
- Put it in writing and keep a copy with the date you sent it.
An officer can decline to change an opinion. The unit order, the violations in block 22, the narrative and the diagram are the officer’s judgment. Factual errors are easier to fix than conclusions; if the report stays as it is, your evidence still goes to the insurer with the claim.
The injury code and later information
ADOT’s manual tells officers to base injury severity on the latest information available when the report is completed, and to change the code to 5, Fatal, with a Fatal Supplement, when someone dies within 30 days. A code of 1, No Injury, or 2, Possible Injury, does not set the value of an injury that a doctor finds the next day; the medical records do. See a doctor promptly and keep every record. Our guide to delayed injury symptoms after a car accident lists what to watch for.
2024 data
What Arizona officers marked in 2024
ADOT counted 121,107 crashes in 2024: 1,117 fatal, 37,376 with injuries and 82,614 with property damage only. They killed 1,228 people, down from 1,308 in 2023, and injured 54,426. Block 22 on those reports covered 236,193 drivers. After No Improper Action, the most common marks were Speed Too Fast for Conditions and Failed to Yield Right of Way.
| Violation, with its code in block 22 | Drivers, 2024 | In fatal crashes | In injury crashes | In fatal crashes per 1,000 |
|---|---|---|---|---|
| 1, No Improper Action | 116,269 | 766 | 36,844 | 6.6 |
| 2, Speed Too Fast for Conditions | 32,466 | 152 | 11,275 | 4.7 |
| 20, Failed to Yield Right of Way | 23,078 | 139 | 8,328 | 6.0 |
| 12, Unsafe Lane Change | 10,484 | 27 | 1,681 | 2.6 |
| 13, Failed to Keep in Proper Lane | 7,766 | 133 | 1,952 | 17.1 |
| 4, Followed Too Closely | 7,593 | 13 | 2,115 | 1.7 |
| 6, Disregarded Traffic Signal | 5,891 | 64 | 2,605 | 10.9 |
| 7, Made Improper Turn | 4,250 | 13 | 1,061 | 3.1 |
| 5, Ran Stop Sign | 1,418 | 25 | 592 | 17.6 |
| 8, Drove Left of Center Line | 1,362 | 88 | 561 | 64.6 |
| 3, Exceeded Lawful Speed | 733 | 71 | 322 | 96.9 |
| 49, Aggressive Driving | 333 | 6 | 98 | 18.0 |
| 11, Passed in No Passing Zone | 165 | 5 | 52 | 30.3 |
| 10, Crossed Median | 150 | 15 | 76 | 100.0 |
| 9, Wrong Way Driving | 136 | 13 | 61 | 95.6 |
| 50, Other | 5,380 | 39 | 1,449 | 7.2 |
| 51, Unknown | 18,719 | 247 | 4,550 | 13.2 |
The rare marks are the deadly ones. Drivers marked Exceeded Lawful Speed were in a fatal crash 97 times in every 1,000, Wrong Way Driving 96 times, and Crossed Median 100 times, against under 2 in every 1,000 for Followed Too Closely. Failed to Keep in Proper Lane was far more common than any of those and still ended in a fatal crash 17 times in every 1,000.
Source: ADOT, 2024 Arizona Motor Vehicle Crash Facts, published July 9, 2025, Table 5-11, Driver Violations (a driver can carry more than one mark, so the rows overlap). In fatal crashes per 1,000 calculated by FairSettlement.org.
How vehicles collided
| Manner of impact, block 17 | Crashes | Fatal | With injuries |
|---|---|---|---|
| 4, Rear End | 38,654 | 91 | 12,221 |
| 6, Sideswipe, Same Direction | 19,208 | 34 | 2,534 |
| 2, Angle | 18,182 | 96 | 6,371 |
| 3, Left Turn | 16,866 | 127 | 6,438 |
| 5, Head On | 2,023 | 83 | 919 |
| 7, Sideswipe, Opposite Direction | 1,639 | 10 | 386 |
| 10, U Turn | 983 | 8 | 251 |
| 50, Other | 5,022 | 331 | 2,639 |
| 51, Unknown | 473 | 11 | 109 |
| All crashes between two or more units | 103,050 | 791 | 31,868 |
Rear end crashes were more than a third of all crashes between two or more units, but head on crashes, at 2 percent of them, were 10 percent of the fatal ones. Left turn crashes had more fatal crashes than any other named type, 127.
Source: ADOT, 2024 Arizona Motor Vehicle Crash Facts, Table 3-1, Manner of Collision in Multi-Unit Crashes. Other includes pedestrian and bicycle crashes.
The three biggest police cities
| City | Crashes, 2024 | Killed | Injured |
|---|---|---|---|
| Phoenix | 37,472 | 278 | 15,057 |
| Mesa | 8,022 | 48 | 3,531 |
| Tucson | 5,977 | 96 | 3,644 |
Source: ADOT, 2024 Arizona Motor Vehicle Crash Facts, Table 2-5, Analysis by Jurisdiction.
From report to claim
What the report means for the value of your claim
The report never puts a price on a claim. An Arizona injury claim is valued from the medical bills, the pay you lost, the injury and its effect on your life, reduced by your share of the fault. The report feeds the last part directly through Unit 1, block 22 and block 10, and it is the first written record of the injury through the IS code. Arizona’s constitution bars any law that limits the damages for causing injury or death (art. 2, § 31), so there is no cap on pain and suffering.
Enter the medical bills for a range; lost pay is optional.
Arizona’s minimum liability policy, for policies issued or renewed since July 1, 2020, is $25,000 for one person’s injuries, $50,000 for everyone hurt in one crash and $15,000 for property (A.R.S. § 28-4009). If the other driver carries only that, your own underinsured motorist coverage may pay the difference. The Arizona settlement guide covers the rest of the state’s rules.
Deadlines
Deadlines that run while you wait for the report
The two year limit for an injury lawsuit in Arizona runs from the crash, not from the day the report is ready (A.R.S. § 12-542). A claim against a city, a county or the state moves much faster: a notice of claim must reach the right person within 180 days, stating a specific amount that would settle it and the facts behind that amount (§ 12-821.01(A)), and the lawsuit itself must be filed within one year (§ 12-821). If the public entity does not answer within 60 days, the claim is treated as denied (§ 12-821.01(E)).
Practice
Three sample Arizona crash reports, decoded
These are made up reports, written to show how the blocks read together. Any of the codes can be checked in the decoder at the top of the page.
- Unit 1, block 22
- 4
- Block 17, manner of impact
- 4
- Block 14, relation to junction
- 2
- Block 23, Unit 1 and Unit 2
- 1 and 3
- Unit 2 driver, IS, SD and AB
- 2, 3 and 7
- Block 10
- Unit 1, 28-730(A)
Unit 1 was going straight and hit Unit 2, which was stopped in a line of traffic at the light: an intersection related rear end crash. The officer checked Followed Too Closely for Unit 1 and wrote a citation under the following too closely statute. The Unit 2 driver wore a lap and shoulder belt, no airbag went off, and complained of neck pain with nothing visible, so the injury code is 2, Possible Injury. If an MRI later finds a disc injury, the medical records carry it.
- Unit 1, block 22
- 20
- Unit 2, block 22
- 2
- Block 17, manner of impact
- 3
- Block 23, Unit 1 and Unit 2
- 4 and 1
- Unit 2 driver, IS and AB
- 4 and 1
- Block 10
- Unit 1, 28-772
Unit 1 turned left in front of Unit 2, the officer marked it Failed to Yield Right of Way, and the citation is the left turn statute. But Unit 2 also carries 2, Speed Too Fast for Conditions, because of the rain that night. Under pure comparative fault that does not end Unit 2’s claim: if a jury put 20 percent of the fault on Unit 2, its recovery would drop by 20 percent. A front airbag went off and the injury code is 4, Suspected Serious Injury, pointing to a hard crash.
- Unit 1, the pedestrian, block 22
- 17
- Unit 1, block 23 and block 24
- 17 and 6
- Unit 2, the car, block 22
- 1
- Light condition
- 5
- Unit 1, IS
- 3
- Block 10
- none
Here the pedestrian is Unit 1: crossing the road outside a crosswalk, away from an intersection, on a dark street with no lighting. The driver is marked No Improper Action. Even so, under Arizona law the pedestrian’s claim is reduced by their share of the fault, not barred, and the questions a claim would test are the ones the report leaves open: the car’s speed, its headlights, and whether the driver could have seen the person in time. The pedestrian’s injuries are 3, Suspected Minor, visible at the scene.
The full code list
Every code on an Arizona crash report, block by block
These are all the coded fields on ADOT’s current form, 01-2704 revised January 2022. On page 2 each block has a large printed number, 12 to 27, and the officer checks a numbered box inside it. On page 1 the codes for belts, airbags, injuries and seats are printed once in a key above the vehicle blocks, and the officer writes the number in the SD, AB, IS and Seat Pos columns. Open any list to see each code with a plain note written from ADOT’s instruction manual for officers, 13th edition, August 2023.
Location, light and weather Page 1, block 3
LCLight Condition7 codes
The light at the time of the crash, recorded for every crash.
- 1DaylightFrom sunup to sundown.
- 2DawnThe change from dark to daylight, usually the 30 minutes before sunrise.
- 3DuskThe change from daylight to dark, usually the 30 minutes after sunset.
- 4Dark, LightedNo daylight, but overhead street lighting at the crash site. Light from stores, homes or parking lots does not count.
- 5Dark, Not LightedNo daylight and no overhead street lighting where the crash happened.
- 6Dark, Unknown LightingDark, and the officer could not tell whether street lighting was there.
- 51UnknownUsed when the time of the crash is not known.
WCWeather Conditions9 codes
The main weather at the time of the crash. It is recorded whether or not the weather played any part.
- 1ClearIncludes some cloud, as long as sunlight was not reduced.
- 2CloudyOvercast, or partly cloudy with reduced light.
- 3Sleet, Hail (freezing rain or drizzle)Precipitation falling as ice.
- 4Rain
- 5Snow or Blowing SnowFalling snow, or snow on the ground lifted by wind across the road.
- 7Blowing Sand, Soil, DirtDust or sand lifted by wind that cut visibility: a dust storm.
- 8Fog, Smog, Smoke
- 50OtherAny other condition that cut visibility, or severe weather such as a severe thunderstorm, named on the form or in the narrative.
- 51Unknown
People: belts, airbags, injuries and seats Page 1, the code key above the unit blocks, used in blocks 5 and 6
SDSafety Devices8 codes
The belt, child seat or helmet each person was using, coded in the SD column.
- 0Not ApplicableFor a parked or driverless vehicle, or a pedestrian. Never used for a motorcycle rider or a cyclist.
- 1None UsedNo belt or child seat. For a motorcycle rider or a cyclist, no helmet.
- 2Lap BeltLap belt only, because the vehicle has no shoulder belt or it was not worn.
- 3Shoulder and Lap BeltBoth parts of the belt buckled.
- 4Child Restraint SystemThe child was buckled into a safety seat. The code does not say the seat was used correctly.
- 5Helmet UsedA helmet on a motorcycle, moped, scooter or all terrain vehicle, and also on a cyclist or a skateboarder.
- 50OtherAnother restraint, such as a racing harness, explained in the narrative.
- 51UnknownThe officer could not tell, and should explain why in the narrative.
ABAirbag8 codes
Whether an airbag went off at that person’s seat, and which kind.
- 0Not ApplicableA pedestrian or cyclist, a seat with no airbag, or a vehicle without airbags such as a motorcycle.
- 1Deployed, FrontThe airbag in the steering wheel or the dashboard.
- 2Deployed, Side (door, seatback)An airbag in the outer side of the seat or in the door.
- 3Deployed, Curtain (roof)The head airbag that drops from the roof rail beside the windows, including rollover curtains.
- 4Deployed, Other (knee, airbelt)Another type, such as a knee airbag.
- 5Deployed, CombinationMore than one airbag went off at this seat.
- 6Deployed, Unknown LocationAn airbag went off at this seat, but its location is not known.
- 7Not DeployedNo airbag went off at this seat.
ISInjury Severity6 codes
The most serious injury each person had, on the national KABCO scale. ADOT numbers the levels 1 to 5; the letter in brackets is the national code.
- 1No Injury (O)No reason to believe the person was hurt: no physical sign of injury and no complaint.
- 2Possible Injury (C)An injury claimed or reported with nothing visible, such as a complaint of pain or nausea, limping, or a moment of lost consciousness.
- 3Suspected Minor Injury (B)An injury visible at the scene, such as a bump on the head, scrapes, bruises or small cuts.
- 4Suspected Serious Injury (A)A severe cut, a broken or misshapen arm or leg, a crush injury, a suspected skull, chest or abdominal injury, serious burns, unconsciousness when taken from the scene, or paralysis.
- 5Fatal Injury (K)Death within 30 days of the crash. If a person dies later, the code is changed to 5 and a Fatal Supplement is added.
- 51Unknown or Not ReportedThe form prints 51; ADOT’s manual numbers this code 99. It is meant only for a person who was not there when the officer investigated.
SPSeating Position17 codes
Where each person sat. The first digit is the row, the second the place in it: 11 is the driver’s seat.
- 11Front row, left sideThe driver’s seat. Officers assume the driver sat here unless the narrative says otherwise.
- 12Front row, middle
- 13Front row, right side
- 18Front row, otherSuch as a child on a lap.
- 21Second row, left side
- 22Second row, middle
- 23Second row, right side
- 28Second row, another passengerAn extra passenger in that row.
- 31Third row, left side
- 32Third row, middle
- 33Third row, right side
- 38Third row, another passenger
- 40Enclosed cargo or passenger areaIncluding a fifth row.
- 41Unenclosed cargo areaSuch as the bed of a pickup.
- 42Riding on the outside of the vehicle
- 50Other
- 51Unknown
Drivers and vehicles Page 1, blocks 5, 7 and 8
CLDriver License Class5 codes
The class printed on the driver’s license.
- ACommercial driverClass A commercial license.
- BCommercial driverClass B commercial license.
- CCommercial driverClass C commercial license.
- DOperatorThe standard Arizona license for cars and light trucks.
- GGraduatedThe license for young drivers, with age based limits.
ENLicense Endorsements7 codes
Endorsements on the license.
- HHazardous materials
- MMotorcycle
- NTank vehicle
- PBusPassenger vehicles.
- SSchool bus
- TDouble or triple trailers
- XTank vehicle carrying hazardous materials
7Vehicle Damaged Area12 codes
Where each vehicle was first hit. The officer circles every area that applies on a small drawing of the vehicle seen from above, its front at area 1.
- 0NoneNo visible damage.
- 1Front
- 2Right front corner
- 3Right side
- 4Right rear corner
- 5Rear
- 6Left rear corner
- 7Left sideThe driver’s side.
- 8Left front corner
- 9TopThe roof.
- 10UndercarriageDamage below the body, including hits to the wheels.
- 51Unknown
OCOwner Code8 codes
Who owns damaged property other than the vehicles, such as a sign, a pole or a fence.
- 1PrivateProperty outside the road right of way that no government owns.
- 2Public UtilitySuch as APS, SRP or a rural water district.
- 3Federal GovernmentSuch as the fence of a military base or a veterans hospital.
- 4State of Arizona
- 5County in Arizona
- 6City in Arizona
- 7Tribal Nation
- 51Unknown
The road Page 2, blocks 12 to 16 and 25 to 26
12Road Surface Condition8 codes
The road surface for each unit, recorded whether or not it played a part.
- 1Dry
- 2WetWater from rain or melted snow.
- 3Snow or Slush
- 5Ice or Frost
- 6Water (standing or moving)An unusual amount of water, such as a flooded wash or a pooled lane.
- 8Mud, Dirt, Gravel, SandMaterial lying on the road, not a dirt road by design.
- 50OtherSuch as spilled grain, wet leaves or a spilled liquid.
- 51Unknown
13Road Grade4 codes
The slope of the road in each unit’s direction of travel.
- 1Level
- 2Downhill
- 3Uphill
- 51Unknown
14Relation to Junction8 codes
Where the first event happened compared with an intersection, ramp, crossing or driveway. For an intersection, the officer also marks Four Way, T or Other.
- 0Not Junction Related
- 1Intersection (within)Inside the area where the roads cross.
- 2Intersection RelatedOn the approach to or the exit from an intersection, and caused by traffic moving through it. In Arizona this is normally within 150 feet, or farther when traffic is backed up: a rear end crash in a line stopped at a red light counts.
- 3Entrance or Exit Ramp
- 4Railway Grade Crossing
- 7Driveway or Alley AccessTraffic going into or out of a driveway or alley, including crossing from one driveway to another.
- 50OtherSuch as a frontage road.
- 51Unknown
15Trafficway Description6 codes
Whether the road was one way or two way, and whether a median or barrier separated the directions.
- 1One Way TrafficwayIncluding ramps and one way streets.
- 2Two Way, Not DividedOnly a painted yellow center line, or no markings.
- 3Two Way, Not Divided, Continuous Left Turn LaneA shared center turn lane for both directions.
- 4Two Way, Divided, Unprotected MedianA median wider than 4 feet, raised, grass or flush, with no barrier in it.
- 5Two Way, Divided, Positive Median BarrierA concrete wall, guardrail or cable barrier between the directions. Trees, curbs and rumble strips do not count.
- 51Unknown
16Traffic Control Device12 codes
The sign, signal or person that controlled each unit, recorded whether or not it played a part. With more than one, the officer picks the one that mattered most.
- 0No ControlsNone present. A control that was knocked down, hidden or not working is not coded 0.
- 1SignalA green, yellow and red signal.
- 2Stop Sign
- 3Yield Sign
- 4Warning SignA sign warning of a hazard ahead, such as a curve.
- 5Railroad Crossing Sign
- 6Flashing Traffic SignalFlashing red or yellow, including a signal on its night flash cycle.
- 7PersonA police officer, crossing guard or flagger directing traffic.
- 8Traffic Circle or Roundabout
- 9Pedestrian Hybrid Beacon (HAWK)The overhead crosswalk beacon that stops traffic only when someone presses the button.
- 50Other
- 51Unknown
25Roadway Alignment4 codes
Whether the road was straight or curved before each vehicle’s first harmful event.
- 1Straight
- 2Curve Left
- 3Curve Right
- 51Unknown
26Lane21 codes
The lane each unit was in before the first event. Through lanes are counted from the median or center line outward.
- 0Two way continuous left turn laneThe shared center turn lane.
- 1Through lane 1The lane next to the median or center line.
- 2Through lane 2
- 3Through lane 3
- 4Through lane 4
- 5Through lane 5
- 6Through lane 6
- 7Through lane 7
- 8Through lane 8
- 9Through lane 9
- 10Crosswalk
- L1Left turn lane 1The first left turn only lane after the median or center line; L2 and higher count outward.
- L2Left turn lane 2
- R1Right turn lane 1The first right turn lane after the through lanes; R2 and higher count outward.
- R2Right turn lane 2
- SWSidewalk
- BLDedicated bike lane
- HOVHigh occupancy vehicle laneThe carpool lane.
- 49Non roadway
- 50Other
- 51Unknown
How the crash happened Page 2, blocks 17 to 24 and 27
17Manner of Crash Impact10 codes
How two moving vehicles first came together. When a pedestrian or cyclist was hit, it follows what the vehicle was doing, so a car turning left into a cyclist is coded Left Turn.
- 1Single VehicleNo collision between two moving motor vehicles.
- 2Angle (front to side)The front of one vehicle into the side of another, other than a left turn: the T bone crash.
- 3Left TurnVehicles coming from opposite directions, at least one of them turning left.
- 4Rear End (front to rear)
- 5Head On (front to front)Other than a left turn.
- 6Sideswipe, Same DirectionSide to side contact while traveling the same way, with no real involvement of the front or rear.
- 7Sideswipe, Opposite Direction
- 10U TurnOne vehicle was making a U turn.
- 50OtherSuch as the end of one vehicle swiping another, cargo thrown onto another vehicle, or a rider thrown into another vehicle.
- 51Unknown
18Direction of Unit Travel9 codes
The compass direction each unit was moving before the first event. For a parked or stopped vehicle, the way it faced.
- 1North
- 2South
- 3East
- 4West
- 5Northwest
- 6Northeast
- 7Southwest
- 8Southeast
- 51Unknown
19Contributing Circumstances15 codes
Conditions of the environment, the road or the vehicle that may have contributed, up to two per unit. Driver behavior goes in block 22, not here. A separate box, Possible Road Rage Incident, is checked when the officer believes angry or aggressive behavior was involved.
- 0No Contributing CircumstanceThe officer saw no environment, road or vehicle condition that may have contributed.
- 1AGlare: SunlightThe angle of the sun cut visibility, directly or by reflection.
- 2APhysical Obstruction: Stopped or Parked VehicleA parked or stopped vehicle blocked the view.
- 2BPhysical Obstruction: Moving VehicleAnother moving vehicle blocked the view.
- 2CPhysical Obstruction: Load on VehicleAn object carried on a vehicle blocked the view.
- 2DPhysical Obstruction: Tree, Shrub, BushVegetation blocked the view.
- 3Road Surface ConditionThe surface recorded in block 12 contributed.
- 4DebrisObjects too small to block a lane that could still cause damage or a loss of control, such as tire tread, glass or lost cargo.
- 5Work ZoneThe crash was in or related to a construction, maintenance or utility work zone, with or without workers present. Includes vehicles slowed or stopped by it before the first sign.
- 6Obstruction in RoadwaySomething big enough to block all or part of a lane, such as a fallen tree or a boulder.
- 7Changing Road WidthThe road narrowed for a while because of debris, drifting snow or flooding. Work zone narrowing is code 5.
- 8Non Highway WorkWork near the road that was not road work.
- 12TiresA defective, worn or wrongly sized tire. Damage caused by the crash itself does not count.
- 50OtherAnother environment or vehicle condition, named on the form or in the narrative.
- 51UnknownThe officer believes a condition contributed but could not tell which.
20Distracted Driving Behavior10 codes
What distracted each driver, inside or outside the vehicle.
- 0Not Distracted or Not ApplicableThe officer judged the driver fully attentive. Also used for a parked or driverless vehicle and for pedestrians.
- 1Talking on Hands Free DeviceA headset or the car’s own phone system.
- 2Talking on Hand Held DeviceA phone held in the hand.
- 3PassengerTalking to, looking at or dealing with a passenger, including children.
- 4Other Activity, Electronic DeviceA navigation unit, radio, DVD player or another device.
- 5Manually Operating an Electronic DeviceTexting, typing or dialing.
- 6Other Inside the VehicleEating, drinking, reading, makeup, shaving, an animal.
- 7Outside the VehicleSuch as a crash in another lane, a billboard or a highway sign.
- 50Distracted, Unknown ReasonDistracted, but by what is not known.
- 51Unknown if DistractedThe officer could not tell.
21Condition Influencing Driver, Pedestrian or Cyclist13 codes
The condition of each driver, pedestrian or cyclist that may relate directly to the crash, up to three per unit. Beside it, the DRE boxes record a drug recognition expert’s part.
- 0No Apparent InfluenceThe officer suspected nothing abnormal.
- 1Illness or Physical ImpairmentSuch as a seizure, a diabetic or allergic reaction, a heart attack, fainting, or a disability related to the crash.
- 3Fell Asleep or FatiguedNot because of drugs, alcohol or illness.
- 4AlcoholMarked when the officer had probable cause for a DUI under A.R.S. § 28-1381 and a blood, breath or urine sample was taken.
- 5Illegal DrugsSuspected, such as methamphetamine or cocaine.
- 6MedicationsA prescription or over the counter drug, suspected.
- 7MarijuanaSuspected.
- 8Medical Marijuana Card PresentedThe person showed an Arizona medical marijuana card.
- 50OtherAn emotional condition the officer believes contributed, such as anger or a fight, explained in the narrative.
- 51Unknown Condition
- aDRE respondedA drug recognition expert came to the scene.
- bSuspect evaluatedThe expert evaluated a driver for impairment.
- cSuspect arrestedA driver was arrested for possible or confirmed impairment.
22Violations or Behavior18 codes
What the officer believes each driver, pedestrian or cyclist did wrong. Every box that applies is checked, unit by unit.
- 1No Improper ActionIn the officer’s judgment this unit did nothing wrong.
- 2Speed Too Fast for ConditionsToo fast for the road, weather or traffic, even if under the limit. Not used for distraction, impairment or fatigue, or for running a sign or signal.
- 3Exceeded Lawful SpeedOver the posted limit. An advisory speed on a curve sign is not the limit.
- 4Followed Too CloselyToo close to the vehicle or person ahead to react safely to what they did.
- 5Ran Stop SignDid not come to a complete stop.
- 6Disregarded Traffic SignalWent through a red, including entering on yellow just after it turned red.
- 7Made Improper TurnAn illegal or badly made turn or U turn, such as turning from the wrong lane or against a No Turn sign. Not used for a right of way violation during a proper turn.
- 8Drove Left of Center LineCrossed a painted center line or a center turn lane into the other side. Crossing a raised median or barrier is code 10.
- 9Wrong Way DrivingEstablished on the wrong side, such as driving west in the eastbound lanes of a freeway.
- 10Crossed MedianOn a divided highway, lost control, crossed the median and hit traffic on the other side.
- 11Passed in No Passing ZoneSuch as passing across double yellow lines.
- 12Unsafe Lane ChangeAn improper or erratic lane change, weaving through traffic.
- 13Failed to Keep in Proper LaneDid not stay in the lane.
- 17Did Not Use CrosswalkA pedestrian crossing outside a marked crosswalk or an intersection, or between two signalized intersections.
- 20Failed to Yield Right of WayDid not yield to another vehicle or a person when required.
- 49Aggressive DrivingPrinted on the form; ADOT counted 333 drivers with it in 2024.
- 50OtherAnother violation the officer believes contributed, named on the form and explained in the narrative.
- 51UnknownThe officer could not determine what this unit did.
23Traffic Unit Maneuver or Action24 codes
What each unit was doing just before the crash began. Codes 17 to 22 are for pedestrians and cyclists.
- 1Going Straight Ahead
- 2Slowing in Trafficway
- 3Stopped in TrafficwayStopped in a travel lane: at a sign or signal, waiting to turn, or in stopped traffic.
- 4Making Left TurnIncluding a vehicle waiting to start the turn.
- 5Making Right TurnIncluding a right turn on red. A vehicle waiting to turn is code 3.
- 6Making U Turn
- 7Overtaking or PassingPassing on the left or right. Not used for rear end crashes.
- 8Changing LanesInto a lane going the same direction.
- 9Negotiating a Curve
- 10Backing
- 11Avoiding Vehicle, Object, Pedestrian or CyclistA controlled move to avoid something.
- 12Entering Parking Position
- 13Leaving Parking Position
- 14Properly ParkedStopped entirely outside the roadway.
- 15Improperly ParkedStopped partly or fully in the roadway.
- 16Moving Vehicle, No Driver
- 17Crossing RoadA pedestrian or cyclist crossing, in or outside a crosswalk.
- 18Walking With TrafficWalking or riding in the road in the same direction as the vehicles.
- 19Walking Against Traffic
- 20StandingIn the road.
- 21LyingIn the road.
- 22Getting On or Off Vehicle
- 50Other
- 51Unknown
24Location of Pedestrian or Cyclist18 codes
Where the first pedestrian or cyclist hit was, at the moment of the crash.
- 1At intersection, in marked crosswalk
- 2At intersection, unmarked crosswalk or not known if markedThe crossing implied at a corner, with no painted lines.
- 3At intersection, not in crosswalk
- 4At intersection, location unknown
- 5Not at intersection, in marked crosswalkA painted mid block crosswalk, including where a shared use path crosses.
- 6Not at intersection, on roadway, not in marked crosswalkCrossing mid block outside any crosswalk.
- 7Not at intersection, on roadway, crosswalk availability unknown
- 8School crosswalkA marked school crossing, while school or a school event was in session.
- 9Parking lane or zone
- 10Bicycle lane
- 11Shoulder or roadside
- 12Sidewalk
- 13Median or crossing island
- 14Driveway accessThe end of a driveway, including where a sidewalk crosses it.
- 15Shared use pathA path separated from traffic.
- 16Non trafficway areaSuch as private land not open to traffic.
- 50Other
- 51Unknown location
27Sequence of Events33 codes
Up to four events for each unit, in the order they happened, from the same list used for the First Harmful Event of the crash.
- 1Overturn or RolloverTurned at least 90 degrees onto its side, including motorcycles.
- 2Fire or Explosion
- 5Cargo or Equipment Loss or Shift
- 6Fell or Jumped from Vehicle
- 8Other Non CollisionSuch as driving off a cliff with no rollover or impact, or being run over by one’s own vehicle.
- 9Equipment Failure (tires, brakes)A defect in tires, brakes, steering, suspension, lights, a hitch and similar.
- 10Separation of UnitsA trailer came loose.
- 11Ran Off Road Right
- 12Ran Off Road Left
- 13Cross MedianCrossed the whole median into the other side of a divided highway.
- 14Cross CenterlineCrossed into the other lanes of an undivided road.
- 15Downhill RunawayUsually a heavy truck after a brake failure.
- 16Motor Vehicle in TransportA collision with another motor vehicle in motion or on the road.
- 17Pedestrian
- 18PedalcycleA bicycle or any other pedal powered vehicle.
- 19Train
- 20Light Railway or Railcar VehicleSuch as Phoenix and Tempe light rail or the Tucson streetcar.
- 21AnimalLivestock, game or a pet.
- 25Parked Motor Vehicle
- 27Struck by Falling, Shifting Cargo or Anything Set in Motion by Another VehicleIncluding debris thrown from a nearby collision.
- 28Other Non Fixed ObjectSuch as a tree already lying in the road or an object fallen from another vehicle.
- 29Impact Attenuator, Crash Cushion or Guardrail End
- 33Concrete Curb
- 36Guardrail FaceAny part of a guardrail except its ends.
- 38Median BarrierA concrete wall such as a Jersey barrier.
- 39Cable Barrier
- 41Tree, Bush, Stump (standing)
- 42Traffic Sign SupportIncluding delineator posts.
- 43Traffic Signal Support
- 44Utility Pole or Light Support
- 46FenceCinder block walls count as fences.
- 50Other Fixed ObjectThe form prints 50; ADOT’s manual numbers it 49. Such as a fire hydrant, a transformer box or a cattle guard.
- 51Unknown
Source: ADOT, Arizona Crash Report, forms 01-2704A, 01-2704B and 01-2704C, revised January 2022 (300 codes in 26 lists); ADOT, Traffic Crash Report Forms Instruction Manual, 13th edition, August 2023. Two codes differ between the form and the manual, and the decoder accepts both numbers: Unknown injury severity (51 on the form, 99 in the manual) and Other Fixed Object (50 on the form, 49 in the manual).
Questions people in Arizona ask
Arizona crash report questions
How do I get a copy of my Arizona crash report?
Ask the agency whose officer investigated. For a crash a state trooper worked, request it on the DPS Public Services Portal, psp.azdps.gov, with the incident number: a capital I and 8 digits. Phoenix police reports come through the city’s police records portal, Tucson police reports through Crashdocs, and Mesa police and Maricopa County Sheriff’s Office reports through LexisNexis. As a person involved, you are entitled to the unredacted copy (A.R.S. § 28-667(C)).
How much does an Arizona crash report cost?
It depends on the agency. DPS charges $9 for a report by email or through its portal. Phoenix police charge nothing for a digital copy on a personal request, with $0.25 per printed page. Mesa police reports cost $2.60 online when the card holder is named on the report, or $5 from the department. The Maricopa County Sheriff’s Office charges $5 for the first ten paper pages. A victim of a Part 1 crime gets one copy free under A.R.S. § 39-127.
How long does it take to get a police report after a car accident in Arizona?
The officer must write it within 24 hours of finishing the investigation (A.R.S. § 28-667(A)), but the investigation itself can run longer. DPS fills most automated requests within about 48 hours, and the Maricopa County Sheriff’s Office says to allow seven business days for the online upload. Reports involving a death, a serious injury or a criminal charge can take far longer.
Who can get an unredacted crash report in Arizona?
The people involved and the owners of the vehicles, or their representatives; the insurers of anyone or any vehicle involved; an attorney or licensed private investigator representing someone involved; and insurance support organizations (A.R.S. § 28-667(C)). If a criminal complaint has been issued, the victim’s personal identifying information is removed before an attorney or representative gets the report. Everyone else gets a redacted public record.
What does Unit 1 mean on an Arizona crash report?
ADOT’s instruction manual tells officers that Traffic Unit 1 is the vehicle, pedestrian or pedalcycle that caused the collision or was most at fault. So Unit 1 is the officer’s view of who caused the crash. It is not a court’s finding, and a vehicle that caused the crash without touching anyone is not a unit at all; the officer names it in the narrative.
What does injury severity 2 mean on an Arizona crash report?
2 is Possible Injury, the C on the national scale: an injury that was claimed or reported but not visible, such as a complaint of pain or nausea, limping, or a moment of lost consciousness. 1 is No Injury, 3 Suspected Minor Injury, 4 Suspected Serious Injury and 5 Fatal. The code is the officer’s call from what was known when the report was completed; the medical records show the actual injury.
What does No Improper Action mean on an Arizona crash report?
It is code 1 in block 22, Violations or Behavior. It means that in the officer’s judgment that driver, pedestrian or cyclist did nothing wrong at the time of the crash. ADOT counted it for 116,269 of the 236,193 drivers in Arizona crashes in 2024, about half. A code 1 for you and a violation for the other unit is the strongest way the report can read.
Does the police report decide who is at fault in Arizona?
No. Arizona is a pure comparative fault state: a claimant’s damages are reduced in proportion to their share of the fault, and that question is left to the jury in every case (A.R.S. § 12-2505). The report, the violations in block 22 and any citation are evidence an insurer will weigh, alongside photos, witnesses, video and medical records.
Can I get my Arizona crash report corrected?
Ask the agency that wrote it, not ADOT. Contact its records unit with the report number and proof of each error, such as your insurance card, photos or a witness’s details, and put the request in writing. Missing witnesses or passengers can be added on ADOT’s Occupant Supplement. An officer can correct facts but may decline to change an opinion, such as the violations marked in block 22.
What is a partial crash report in Arizona?
A short report written when the crash caused property damage of $2,000 or less, with no injury, no death and no citation (A.R.S. § 28-667(B)). It must give the date and time, the place, the people involved and any witnesses, a brief narrative, a simple diagram and the officer’s name, agency and ID number. Above that line, or with any injury or citation, the officer writes the full report.
What if the police did not come to my accident in Arizona?
If anyone was hurt or killed, the drivers must notify the police at once (A.R.S. § 28-666), and every driver must exchange names, addresses and registration numbers and show a license on request (§ 28-663). Ask the local agency whether it takes a report after the fact; ADOT’s form marks such counter reports with Investigated At Scene: No. Your photos, the other driver’s details and witness names carry the claim.
Report in hand? Get the whole claim reviewed
Tell us where it happened, how you were hurt and what the report says. A free review checks the deadlines and every policy that might pay, and a licensed attorney contacts you if the case qualifies.
Start my free review