Police Reports in Arizona
Find and request official police reports from any city in Arizona. Our comprehensive database covers all 462 cities and counties throughout the state.
About Arizona Police Reports
Important Information
Arizona offers online report retrieval for many jurisdictions. Uses Form 01-2704 for traffic incidents
Processing Details
Phoenix and Tucson have dedicated traffic units for faster processing
Additional Notes
Online system available for most urban areas
Available Report Types
- Form 01-2704 (Traffic)
- DPS Reports
- Local Agency Reports
REQUEST A ARIZONA POLICE REPORT
Select your city below to start your official police report request
✓ 3-7 business days average processing
✓ Secure online submission
✓ 24/7 customer support
Arizona Traffic Accident Report
Official Report Forms
.png)
Structure and general layout
The first page of the Arizona report opens with administrative information used by ADOT and the investigating agency. Boxes across the top identify the report ID, agency report number, hour, NCIC number and officer ID; the officer marks whether the report is for ADOT use only, a truck/bus supplement or a continuation page. A row of checkboxes allows the officer to indicate whether any of a set of conditions apply: possible road‑rage incident, hazardous materials involved or whether the report is an addendum. Below the header, the form records basic crash demographics: the year, month, day and hour, the total number of units (vehicles, pedestrians and pedalcyclists), total number of persons, number injured and number killed【275392495894876†screenshot】. A section labelled “Collision Occurred On” captures the street, highway or route where the crash took place, along with an intersecting street or mile marker. The officer circles the day of the week and records the precise time. Additional fields collect the city, town or reservation where the crash occurred; the county code; and whether the crash happened on a roadway or within a parking lot.
Party and unit information
The bulk of the report is divided into “unit” or “party” sections. Each unit represents a vehicle, pedestrian or pedalcyclist involved in the crash. The first page allocates space for up to three parties; if more vehicles or pedestrians are involved, supplementary pages are attached. For each party the officer records the driver’s licence number, state, class, expiration date, and driver’s name (last, first, middle)【275392495894876†screenshot】. The driver’s address, city, state and zip code are captured as part of the demographic information. Each party section includes checkboxes to identify sex, hair colour, eye colour, weight and height; the officer records the driver’s date of birth and race. A field for home phone ensures investigators can contact the driver after the collision. A small vehicle silhouette appears on the right side of each party section; the officer shades the area of damage to show where the vehicle was impacted【275392495894876†screenshot】. Under the silhouette, the officer provides the vehicle’s year, make, model and colour, followed by the vehicle identification number (VIN) and licence plate. Space is provided for the owner’s name (if different from the driver) and the insurance company and policy number. Arizona’s form also captures information about commercial vehicles. The officer must indicate whether the vehicle displays a hazardous‑material placard, whether it is a bus or truck as defined by ADOT regulations, and whether a truck/bus supplement is required. If so, a supplemental form is completed that records the carrier’s identification numbers, cargo type, gross vehicle weight rating, vehicle configuration and sequence of events. This supplement mirrors the federal Motor Carrier Management Information System (MCMIS) crash report and is similar to the commercial vehicle supplements used in other states.
Occupants and injury data
The Arizona report devotes a large portion of its first page to occupant information【275392495894876†screenshot】. A grid contains numbered rows where each occupant (drivers, passengers, pedestrians, pedalcyclists) is listed. Columns record the occupant’s seating position, restraint use, air‑bag deployment, injury severity, ejection status, extrication, transport method, hospital, alcohol/drug test results and alcohol or drug involvement suspected. Seat‑position codes correspond to diagrams printed on the form; for example, codes indicate whether a passenger was in the front row left, right or centre seat, rear seat positions, cargo area or on a motorcycle. Injury severity codes follow NHTSA definitions: fatal, incapacitating injury, non‑incapacitating injury, possible injury or no injury. Ejection and extrication codes indicate whether the occupant was fully or partially ejected from the vehicle and whether mechanical means were used to remove them. The transport method lists the agency or service that transported the occupant (e.g., EMS, private vehicle, air ambulance), and the hospital column records the facility’s name. Finally, the officer notes whether an alcohol or drug test was given and records any alcohol or drug involvement. Collecting these details ensures that injury outcomes and impairments are thoroughly documented for all crash participants.
Additional sections and narrative
The Arizona report contains numerous other sections, including: * Collision diagram and narrative: Later pages provide a blank grid for the officer to draw a scaled diagram of the crash, showing roadway configuration, vehicle paths, skid marks and final rest positions. A narrative area allows the officer to describe the sequence of events in prose, including contributing factors and statements from drivers or witnesses. Narrative fields are critical because they capture nuance and context beyond what codes can convey. * Property damage and witness information: The report includes fields to document damage to property other than the vehicles (e.g., fences, buildings, utility poles) and to list witness names, addresses and phone numbers. Witness data helps verify events and supports legal proceedings. * Violations and enforcement: Officers record all traffic citations issued, including the statute number and charge. There is also space to document whether the crash involved a hit and run, whether alcohol or drug impairment was observed, and whether the driver had a valid licence or insurance.
Codes and manuals
Arizona uses numeric codes for many of the report’s data elements, such as road surface condition, light condition, manner of collision and contributing circumstances. Although the code sheet for Form 01‑2704 is not included here, ADOT’s Manual of Instructions explains each code in detail. For example, road surface condition codes distinguish between dry, wet, snow, ice, slush, mud, oil and debris; light condition codes classify daylight, dawn, dusk, dark (lighted) and dark (not lighted). Contributing circumstance codes include exceeding lawful speed, failure to yield, disregard of traffic signal, improper turn, following too closely, driver inattention, improper backing and vehicle defects. The manual also explains occupant‑restraint codes, seat positions, vehicle types and other data elements.
Unique features and use
The Arizona Traffic Accident Report stands out for its comprehensive occupant table, which allows all occupants and pedestrians involved to be listed on the first page【275392495894876†screenshot】. By integrating seat‑position diagrams, restraint codes and injury levels, the form ensures uniform collection of injury data. The small vehicle silhouettes for each party provide a quick visual reference for the area of impact. The emphasis on truck/bus supplements reflects Arizona’s role as a major freight corridor; officers must collect detailed information on commercial vehicles, cargo and carrier identification. The report’s integration of narrative and diagram pages allows investigators to capture the dynamics of the collision beyond the coded data. Arizona’s crash reporting system thus blends structured data fields with narrative description to create a robust record. The form’s adherence to NHTSA standards ensures compatibility with national databases, while its state‑specific supplements address Arizona’s unique roadway conditions and commercial traffic.
Need a Arizona Police Report?
Now that you understand the Arizona police report system, select your city below to begin your request.
Our service simplifies the request process for all Arizona jurisdictions
All 462 Cities Available
Every city page is accessible. Search for your city or browse the list below.
Scottsdale
County: Maricopa
Population: 242.169
ZIP Codes: 85259, 85258, 85251...
San Tan Valley
County: Pinal
Population: 105.231
ZIP Codes: 85143, 85142, 85140...
Prescott Valley
County: Yavapai
Population: 96.190
ZIP Codes: 86327, 86315, 86314...
Showing top 20 cities by population. All 462 cities have dedicated pages.