Police Reports in Arkansas
Find and request official police reports from any city in Arkansas. Our comprehensive database covers all 621 cities and counties throughout the state.
About Arkansas Police Reports
Important Information
Arkansas maintains a centralized crash database for statistical analysis. Uses Form 5-2000 with separate code sheets
Processing Details
Electronic filing has reduced processing times significantly
Additional Notes
Separate code sheet available for detailed information
Available Report Types
- Form 5-2000 (Traffic)
- State Police Reports
- County Reports
REQUEST A ARKANSAS POLICE REPORT
Select your city below to start your official police report request
✓ 3-5 business days average processing
✓ Secure online submission
✓ 24/7 customer support
Arkansas Motor Vehicle Collision Report and Code Sheet
Official Report Forms
Page 1 – crash summary and vehicle/driver information
The first page of the Arkansas report opens with general crash identification fields. At the top are spaces for the report number, page number and unit assigned. The officer must record the date and time of collision, day of week, time notified and time arrived. There are checkboxes to indicate whether the crash occurred at AM or PM, whether it was a hit and run, and whether the location is within a city or not【863468665513393†screenshot】. A geo code and district line help link the report to geographical databases, and a small block allows the officer to indicate the direction of travel for the vehicles using cardinal directions (north, south, east or west). Below these general fields are lines for the county, city, road/street/highway and the intersection or reference point. Officers specify whether the collision occurred at an intersection, on a city street, or on a rural roadway, and whether the speed limit is posted【863468665513393†screenshot】. This structured location information allows crash investigators to reconstruct the scene and later analyze crashes by jurisdiction or roadway type. The remainder of page 1 is divided into two vertical halves, each labelled “Vehicle #____ (Pedestrian #____).” These sections collect detailed driver, vehicle and injury information for up to two vehicles or pedestrians involved. When the collision involves more vehicles, the officer completes additional pages for the remaining vehicles. Each vehicle section begins with a checkbox asking whether a Commercial Vehicle Supplement is required, linking to the Arkansas Commercial Motor Vehicle Collision Report Supplement described later. Officers record the driver’s name, address, city, state and zip code. A line labelled additional information allows the officer to note items such as the driver’s employer or contact numbers. The report collects demographic data about the driver: date of birth, race, sex and driver’s licence state and class【863468665513393†screenshot】. There is a checkbox to indicate whether a blood, breath or urine test was requested for alcohol or drug screening, and a line for the test results if known. This ensures that impaired‑driving incidents are documented. A space for the vehicle owner’s name distinguishes between the driver and owner. Next, the form captures the vehicle description. Officers fill in the year, make, model, body style and colour of the vehicle. The vehicle identification number (VIN) and licence plate fields uniquely identify the vehicle, while the estimated damage field requires officers to estimate the dollar amount of damage. There are checkboxes to indicate whether the vehicle has a trailer attached (with space to record number of units and licence information), whether there was prior vehicle damage, and whether the vehicle was disabled as a result of the collision【863468665513393†screenshot】. If the vehicle was towed, the form captures the name of the tow service and the location to which the vehicle was removed. Under the heading additional information are lines for insurance company and policy number, as well as EMS arrival and transport information; officers note if injured persons were transported and to which hospital【863468665513393†screenshot】. These details make the Arkansas report particularly useful for insurance investigations and public‑safety records.
Page 2 – point‑of‑contact diagrams, property damage, witnesses and narrative
The second page expands on the crash details. At the top are two schematic diagrams labelled “Point of Initial Contact”—one for each vehicle【338392651410652†screenshot】. Each diagram shows a rectangle representing the vehicle, subdivided into the front, rear, left and right sides. Officers mark the portion of the vehicle where the initial impact occurred, or check “Undercarriage” for underride or undercarriage damage. This simple graphic allows data‑entry staff to quickly classify the point of impact without sketching a new diagram. Below the impact diagrams, the report gathers information about property damage other than the vehicles. Officers indicate whether there was property damage and describe the object struck (such as a fence, utility pole or building). There is a line for the owner’s name, address and damage estimate; another checkbox records whether the owner was notified【338392651410652†screenshot】. A large section is devoted to witnesses; officers list the full name and address of any witness, supporting later testimony or civil claims. The next table records any citation(s) issued—each row lists the person charged, the charge and statute number, and the citation number【338392651410652†screenshot】. This ties law‑enforcement actions directly to the crash report. The lower half of page 2 provides a generous Narrative area with lined rows. Here the investigating officer describes the crash in narrative prose, including the sequence of events, contributing factors and any important observations that are not captured by code fields. Because the structured codes cannot capture every nuance (for example, a driver swerving to avoid an animal or the specific cause of a brake failure), the narrative is essential for clarifying ambiguous situations. Beneath the narrative, the officer must sign their name, provide their badge number and department, and list the reviewing officer and date filed. A small checkbox at the bottom records whether photos were taken【338392651410652†screenshot】, reminding officers to supplement the narrative with photographic evidence when available.
Page 3 – blank diagram sheet
Page 3 of the Arkansas form is reserved entirely for a scaled crash diagram【447939236859535†screenshot】. The sheet contains a large blank area labelled “Diagram” and a small circle at the bottom right instructing the officer to indicate north by arrow. Officers use this page to draw the roadway layout, vehicle paths, skid marks, debris fields, traffic signs and any other physical evidence. A free‑form diagram is critical for reconstructing collisions because it shows relative distances and geometry that cannot be captured through codes alone. The separate page ensures that the diagram does not clutter the information fields on the other pages, and its simplicity encourages legible and scaled drawings.
Page 4 – Commercial Motor Vehicle Collision Report Supplement
When a collision involves a heavy or passenger‑carrying vehicle, Arkansas requires completion of the Commercial Motor Vehicle Collision Report Supplement【937660437747050†screenshot】. The supplement’s introduction states that it must be used if the collision involves a motor vehicle (or combination) with a gross vehicle rating over 10,000 pounds, a motor vehicle displaying a hazardous‑material placard, or a bus designed to transport seven or more people, and if the crash results in injury requiring transport to a medical facility, a fatality, or if any vehicle is towed. These criteria align with federal commercial‑vehicle reporting requirements. The supplement opens with a section to mark the gross vehicle weight rating: 10,001 to 26,000 pounds or more than 26,000 pounds【937660437747050†screenshot】. It then collects the carrier’s identification numbers, including the U.S. DOT number and ICC Motor Carrier number, linking the vehicle to its registered carrier. A table for the carrier’s information records the carrier’s name, address, city, state, zip code and whether the carrier operates interstate【937660437747050†screenshot】. This data ensures that investigators can contact the responsible carrier and determine whether the vehicle is subject to interstate or intrastate regulations. Next, the supplement lists a sequence of events enumerated from 1 to 23【937660437747050†screenshot】. Many of these events describe common collision types—ran off roadway, jackknife, overturn (rollover), cargo loss/shift, explosion/fire, collision involving pedestrians, collision with another vehicle in transport, collision with a train, collision with a fixed object, and various non‑collision events such as equipment failure or unknown events. Investigators mark the sequence in which these events occurred, capturing complex crashes where multiple events happen in succession (e.g., a truck jackknifes, collides with another vehicle, then overturns). Beside the sequence of events list is a column with numerals and small boxes where officers enter the order of events (first, second, third). This sequential approach provides granular data about how the crash unfolded. The supplement then catalogues cargo body type and vehicle configuration. Cargo body types include bus (designated to transport 7–15 people), bus (designated to transport 16 or more people), van/enclosed box, cargo tank, flatbed, dump truck, concrete mixer, auto transporter, garbage/refuse truck, grain/chips/gravel trailer, pole trailer and not applicable【937660437747050†screenshot】. Vehicle configurations range from bus (seats 7+) and bus (16+) to various truck and tractor combinations: single truck with two axles and six tires, single truck with three or more axles, truck/trailer, truck tractor (bobtail), tractor with semi‑trailer, tractor with double trailers, tractor with triple trailers, passenger car carrying hazardous materials, light truck carrying hazardous materials, and unknown heavy truck. Recording these categories allows analysts to distinguish collisions involving large commercial vehicles from those involving private passenger cars. Finally, the supplement asks about hazardous materials. Officers mark whether the vehicle had a hazardous‑material placard and whether there was any leakage of hazardous materials【937660437747050†screenshot】. If the vehicle has a placard, officers must record the four‑digit placard number from the diamond and a one‑digit hazard classification number from the bottom of the diamond. This information is critical for emergency responders and environmental agencies because it identifies the substance and hazard class. By including this data on the collision report, Arkansas ensures that hazardous‑material incidents are traced to specific events and carriers.
Code sheet – standardising the data
Arkansas’s collision report uses numeric codes in many fields. To interpret these codes, investigators rely on a code sheet (overlay) printed separately from the form【223724111436008†screenshot】. The overlay is densely arranged in boxes and columns, each containing a list of codes and descriptions. For example: * Atmospheric conditions: codes 1 through 9 describe weather at the time of the crash, including clear, rain, sleet, snow, fog/smog/smoke, severe winds and dust. Codes 98 and 99 capture “other” and “unknown” conditions【223724111436008†screenshot】. * Light conditions: the report distinguishes daylight, dawn, dusk, dark (lighted) and dark (not lighted), with additional codes for dark but lights lighted and unknown lighting conditions【223724111436008†screenshot】. Combined with the time of day, these codes help analysts study the effect of lighting on crash frequency. * Accident location and road system: codes identify whether the collision occurred on an interstate, U.S. highway, state highway, county road, city street, frontage road or private property【223724111436008†screenshot】. Additional codes specify whether the crash happened at an intersection, not at an intersection but related to one, or on a roadway curve, grade or hillcrest. * Roadway surface conditions: codes for dry, wet, ice, snow, slush, mud, sand, oil and debris allow officials to study how surface conditions contribute to collisions【223724111436008†screenshot】. * Traffic flow and number of lanes: the overlay includes codes for two‑way undivided, divided by median, divided by concrete barrier, four‑lane expressway and other lane configurations, as well as the number of lanes in each direction【223724111436008†screenshot】. These codes help in understanding capacity and traffic flow. * Roadway defects: codes identify hazards such as holes or deep ruts, loose materials on surface, defective shoulders, obstructed view, faded lane markings, no shoulders and debri【223724111436008†screenshot】. By coding roadway defects, Arkansas can allocate maintenance resources to areas where defects contribute to crashes. * Occupancy and occupant position: codes classify each occupant as driver, front passenger, rear passenger, occupant of bus or van, motorcycle driver, bicyclist or pedestrian【223724111436008†screenshot】. Another table records position in or on vehicle and whether the occupant was using safety equipment (seatbelt type, shoulder harness, deployed airbag, helmet)【223724111436008†screenshot】. The code sheet also defines injury codes ranging from fatal injury to not injured. * Ejection from vehicle: codes differentiate between not ejected, partially ejected and totally ejected【223724111436008†screenshot】. This data is important for evaluating occupant protection systems. * Relation to junction and traffic control device: the overlay lists codes for crashes occurring at intersections, driveway accesses, alleys, interchange ramps, railroad crossings and roundabouts【223724111436008†screenshot】. Associated codes identify whether the junction had a stop sign, yield sign, traffic signal, railroad crossing gates or no control devices. * Type of collision and contributing factors: codes classify collisions as head‑on, rear end, sideswipe, angle, left‑turn, backing, parking, overturn, hit‑and‑run or non‑collision【223724111436008†screenshot】. Contributing factors codes cover failure to yield, disregard for traffic control, driving too fast for conditions, improper turn, following too closely, driver inattention, wrong side of road, driving under the influence, vehicle defective equipment and more【223724111436008†screenshot】. These codes help identify common causal factors statewide. * Collision with fixed objects: the code sheet lists numerous fixed objects with which vehicles may collide—bridge rails, guardrails, utility poles, signs, barrels, trees, houses and fences【223724111436008†screenshot】. By coding the object type, analysts can identify infrastructure that poses higher risk. * Vehicle action and first harmful event: codes describe what each vehicle was doing just before impact (e.g., going straight, slowing/stopping, changing lanes, making a U‑turn, overtaking/passing) and record the first harmful event such as collision with another vehicle, pedestrian, train, animal or fixed object【223724111436008†screenshot】. Additional codes identify where the first harmful event occurred—shoulder, median, ditch, on roadway, off roadway or outside right‑of‑way. * Driver vision obscured and vehicle defects: codes specify whether vision was obscured by rain, fog on windshield, objects on windshield, sun glare, dirty windshield or other obstructions【223724111436008†screenshot】. Vehicle defect codes record mechanical issues such as defective steering, brakes, tire failure, lighting failure, suspension failure and trailer hitch issues, enabling defect‑related crash analysis【223724111436008†screenshot】. * Pedestrian and bicyclist actions: the overlay defines codes for pedestrians and bicyclists, including crossing at an intersection with or without crosswalk, walking or standing in roadway, playing in roadway, working on vehicle and walking in bicycle lanes【223724111436008†screenshot】. These codes are essential for analysing vulnerable‑road‑user crashes. * Condition of drivers and pedestrians: codes differentiate between apparently normal, illness, fatigued, physical disability, emotional disturbance, alcohol impairment, drug impairment and unknown【223724111436008†screenshot】. This field allows officers to note whether impairment or health contributed to the crash. By using numeric codes for so many variables, Arkansas ensures that data can be quickly entered into statewide databases for statistical analysis. Researchers can query, for example, all crashes where the roadway surface was wet and the primary contributing factor was failure to yield, or all collisions involving trucks carrying hazardous materials. The code sheet also reduces ambiguity: officers choose from predetermined options rather than writing subjective descriptions. However, the narrative and diagrams remain necessary to provide context that codes cannot capture.
Unique aspects of Arkansas’s reporting system
The Arkansas Motor Vehicle Collision Report stands out because of its combination of structured coding, diagrammatic representation and narrative description. The first page collects comprehensive driver and vehicle data for up to two vehicles, including driver demographics, vehicle specifications, ownership, insurance and injury/EMS details【863468665513393†screenshot】. The second page uses standard vehicle diagrams to pinpoint impact locations and includes fields for property damage, witnesses and citations【338392651410652†screenshot】. The third page provides a clean slate for scaled diagrams【447939236859535†screenshot】, ensuring clear visual representation without crowding the form. Finally, the commercial‑vehicle supplement brings Arkansas into compliance with federal regulations by collecting weight ratings, carrier numbers, sequence of events and hazardous‑material information【937660437747050†screenshot】. The code sheet itself is exceptionally detailed【223724111436008†screenshot】. It enumerates an extensive list of atmospheric conditions, road configurations, traffic controls, collision types, contributing factors, occupant positions, injury codes, vision obstructions, vehicle defects and pedestrian actions. This level of granularity allows Arkansas to analyse crash data from numerous angles: environment, infrastructure, driver behaviour, vehicle mechanical issues and occupant outcomes. The presence of codes for construction zones, roadway defects and hazardous materials highlights the state’s focus on understanding how infrastructure and commercial operations influence safety. At the same time, the inclusion of narrative space and diagrams acknowledges that not all nuances can be captured through codes alone. In summary, Arkansas’s collision reporting system provides a multi‑layered approach to documenting crashes. It collects detailed driver and vehicle information, describes the physical and environmental context through coded fields, captures the dynamics of the collision via diagrams and the sequence of events, and records open‑ended narratives for context. This comprehensive dataset serves not only law‑enforcement and insurance investigations but also transportation agencies, public‑health researchers and policymakers seeking to improve roadway safety.
Need a Arkansas Police Report?
Now that you understand the Arkansas police report system, select your city below to begin your request.
Our service simplifies the request process for all Arkansas jurisdictions
All 621 Cities Available
Every city page is accessible. Search for your city or browse the list below.
Little Rock
County: Pulaski
Population: 467.846
ZIP Codes: 72211, 72210, 72212...
Fayetteville
County: Washington
Population: 405.556
ZIP Codes: 72704, 72703, 72701...
Fort Smith
County: Sebastian
Population: 128.384
ZIP Codes: 72908, 72901, 72904...
Springdale
County: Washington
Population: 87.388
ZIP Codes: 72764, 72762, 72765...
Jonesboro
County: Craighead
Population: 79.187
ZIP Codes: 72467, 72401, 72404...
Rogers
County: Benton
Population: 71.411
ZIP Codes: 72758, 72756, 72716...
North Little Rock
County: Pulaski
Population: 64.504
ZIP Codes: 72113, 72116, 72114...
Bentonville
County: Benton
Population: 56.326
ZIP Codes: 72713, 72712
Pine Bluff
County: Jefferson
Population: 40.436
ZIP Codes: 71602, 71601, 71603...
Hot Springs
County: Garland
Population: 38.023
ZIP Codes: 71901, 71913, 71902...
Benton
County: Saline
Population: 35.954
ZIP Codes: 72015, 72019, 72018...
Sherwood
County: Pulaski
Population: 32.915
ZIP Codes: 72120, 72076, 72117...
Bella Vista
County: Benton
Population: 30.935
ZIP Codes: 72714, 72715
Jacksonville
County: Pulaski
Population: 29.285
ZIP Codes: 72099, 72076, 72078
Russellville
County: Pope
Population: 29.057
ZIP Codes: 72802, 72801, 72811
West Memphis
County: Crittenden
Population: 24.147
ZIP Codes: 72301, 72364, 72303
Hot Springs Village
County: Garland
Population: 16.509
ZIP Codes: 71909, 71910
Blytheville
County: Mississippi
Population: 13.026
ZIP Codes: 72315, 72316
Mountain Home
County: Baxter
Population: 13.021
ZIP Codes: 72653, 72654
Forrest City
County: St. Francis
Population: 12.826
ZIP Codes: 72335, 72336
Arkadelphia
County: Clark
Population: 10.316
ZIP Codes: 71923, 71999, 71998
Helena-West Helena
County: Phillips
Population: 9.218
ZIP Codes: 72390, 72342
Monticello
County: Drew
Population: 8.320
ZIP Codes: 71655, 71656, 71657
Prairie Grove
County: Washington
Population: 7.445
ZIP Codes: 72753, 72730
Heber Springs
County: Cleburne
Population: 7.101
ZIP Codes: 72543, 72545
East End
County: Saline
Population: 6.344
ZIP Codes: 72065, 72206, 72103
Cave Springs
County: Benton
Population: 5.778
ZIP Codes: 72713, 72718
Cherokee Village
County: Sharp
Population: 5.078
ZIP Codes: 72529
Shannon Hills
County: Saline
Population: 4.557
ZIP Codes: 72002, 72103
Johnson
County: Washington
Population: 3.628
ZIP Codes: 72704, 72762, 72741
Elm Springs
County: Washington
Population: 3.000
ZIP Codes: 72762, 72728
Goshen
County: Washington
Population: 2.488
ZIP Codes: 72703, 72727, 72735
Wrightsville
County: Pulaski
Population: 1.409
ZIP Codes: 72206, 72183
Oak Grove Heights
County: Greene
Population: 1.271
ZIP Codes: 72450
Mineral Springs
County: Howard
Population: 1.169
ZIP Codes: 71851
Sulphur Springs
County: Jefferson
Population: 1.035
ZIP Codes: 71603
Tumbling Shoals
County: Cleburne
Population: 752
ZIP Codes: 72581
Clarkedale
County: Crittenden
Population: 536
ZIP Codes: 72325, 72384, 72364
Crawfordsville
County: Crittenden
Population: 476
ZIP Codes: 72327
Caldwell
County: St. Francis
Population: 449
ZIP Codes: 72326, 72322, 72335
Horseshoe Lake
County: Crittenden
Population: 396
ZIP Codes: 72348
Campbell Station
County: Jackson
Population: 333
ZIP Codes: 72112, 72473
Yarborough Landing
County: Little River
Population: 332
ZIP Codes: 71822
College Station
County: Pulaski
Population: 326
ZIP Codes: 72053, 72206
Lost Bridge Village
County: Benton
Population: 295
ZIP Codes: 72732
Pleasant Plains
County: Independence
Population: 263
ZIP Codes: 72568
Pleasant Grove
County: Stone
Population: 255
ZIP Codes: 72567, 72555
Ravenden Springs
County: Randolph
Population: 178
ZIP Codes: 72460
Blue Mountain
County: Logan
Population: 150
ZIP Codes: 72826, 72943
Fountain Hill
County: Ashley
Population: 100
ZIP Codes: 71646, 71642
Hagarville
County: Johnson
Population: 82
ZIP Codes: 72839, 72830, 72846
Witts Springs
County: Searcy
Population: 50
ZIP Codes: 72650, 72686
Whelen Springs
County: Clark
Population: 47
ZIP Codes: 71772, 71743
Wiederkehr Village
County: Franklin
Population: 14
ZIP Codes: 72821, 72949
Showing top 20 cities by population. All 621 cities have dedicated pages.