Reading a police accident report means working through five parts in order: the identifying information at the top, the scene diagram, the officer’s written narrative, the coded fields that record factors and injuries, and the officer’s fault assessment. Each part uses a different visual language, and knowing how to read a police accident report comes down to knowing what each section is trying to tell you and where the codes are defined.
Reports look similar from state to state because the National Highway Traffic Safety Administration publishes voluntary guidelines, the Model Minimum Uniform Crash Criteria (currently in its 6th edition), that encourage states to collect the same core data. State forms differ in layout and in the specific code numbers they use, but the categories are consistent.
The Identifying Information at the Top
The header records the date, time, county, and precise location of the crash, often with GPS coordinates or a description such as “200 feet south of the intersection of Main and Elm.” It also assigns a unique crash identification number. Note that number. Insurers, attorneys, and the agency itself will use it to reference your crash.
Below the header, every person involved is listed. Drivers appear with name, address, date of birth, driver’s license number, and license-issuing state. Passengers and pedestrians get similar entries without the license fields. You may also see fields for person type, seating position, and whether restraints or helmets were in use.
Vehicle information follows: make, model, year, color, license plate, and Vehicle Identification Number for each vehicle, plus the insurance company and policy number for each driver. Check these fields first. A transposed digit in a VIN or policy number can hold up a claim for weeks.
How to Read the Crash Diagram
Nearly every report includes a diagram of the scene, either hand-drawn or generated by software. Read it as a bird’s-eye view. The officer sketches the roadway, lane markings, traffic signals, and features like medians, shoulders, and parking areas. Each vehicle is drawn as a simple rectangle. Arrows show the direction each vehicle was traveling before the collision. The point of impact is usually marked, along with where each vehicle came to rest. A north arrow is typically included.
Skid marks, debris fields, and gouge marks on the pavement may also appear on the diagram. They are there because they help reconstruct speed and the direction of force at impact. Compare the diagram to your memory of the crash. If something is off, make a note of it. The diagram carries real weight with insurance adjusters because it tells a spatial story that the narrative cannot.
How to Read the Officer’s Narrative
The narrative is the officer’s written account, usually a few paragraphs covering the sequence of events, what drivers and witnesses reported, and what the officer personally observed. It is the most readable part of the report and the best window into the officer’s overall interpretation.
Officers write in shorthand to keep it compact. Common abbreviations:
- V1, V2: Vehicle 1, Vehicle 2
- VEH: vehicle
- PED: pedestrian
- MVA: motor vehicle accident
- NB, SB, EB, WB: northbound, southbound, eastbound, westbound
- INJ: injury
- BAC: blood alcohol concentration
If an abbreviation isn’t obvious, the issuing agency can clarify it.
As you read, separate what the officer saw firsthand from what someone told the officer. A sentence like “Driver 1 stated she had a green light” is secondhand. The officer is recording a claim, not confirming it. That distinction matters if you later dispute the other driver’s account or if the case moves toward litigation.
Decoding the Numbered Fields
Much of the report is filled with numbered or lettered codes rather than plain English. The codes exist because crash data feeds into statewide databases for statistical analysis, and standardized codes make that possible. The MMUCC framework sets recommended data elements covering atmospheric conditions, light levels, driver distractions, and contributing circumstances, though each state assigns its own specific code numbers.
Contributing Factors and Road Conditions
Contributing factor codes indicate what the officer believes played a role: speeding, distracted driving, failure to yield, running a red light, following too closely, improper lane changes. A single crash can carry multiple codes, generally listed in order of significance. Road condition codes describe the surface (dry, wet, icy, snow-covered) and atmospheric conditions (clear, rain, fog, sleet) at the time of the crash.
Injury Severity on the KABCO Scale
Most states classify injuries using the five-level KABCO scale recommended by the MMUCC guidelines. Each person involved receives one rating:
- K, Fatal: the person died as a result of the crash.
- A, Suspected Serious Injury: injuries that are immediately apparent and severe, such as broken bones, deep lacerations, or loss of consciousness.
- B, Suspected Minor Injury: visible but less severe injuries, like bruises or small cuts.
- C, Possible Injury: the person complained of pain or showed signs of injury, but nothing was visibly obvious at the scene.
- O, No Injury: no apparent injury.
The officer assigns the rating based on what they observe at the scene, not on a medical diagnosis. A C rating does not mean your injuries are minor. It means they were not visually obvious to the officer. Soft tissue injuries, concussions, and internal injuries frequently receive a C at the scene and turn out to be far more serious once a doctor examines you. Don’t treat KABCO as a medical conclusion.
Vehicle Damage and Direction of Force
Reports note where each vehicle was struck and how badly it was damaged. Many agencies use a clock-position system for direction of force. Twelve o’clock is a head-on impact, six o’clock is being struck from behind, and three or nine o’clock indicates a side impact. Damage severity is often given on a numerical scale, with higher numbers indicating more destruction. Letter codes may describe the type and location of damage on the vehicle (front, rear, left side, right side, roof, undercarriage).
Alcohol and Drug Testing
If the officer suspected impairment, the report has fields for whether a test was administered and what kind: blood, breath, or urine. The result, typically a BAC number, appears in a separate field. Because MMUCC includes data elements for both “Law Enforcement Suspects Alcohol Involvement” and “Alcohol Test,” the officer may note suspected impairment based on observations like slurred speech, odor of alcohol, or open containers in the vehicle even when no test was given.
Where to Find the Code Legend
Most report forms print a legend or code key on the back of the form or on an attached reference sheet. If your copy doesn’t include one, check the law enforcement agency’s website or your state’s department of transportation. Many states publish their code sheets online as downloadable PDFs. The specific numbers won’t match across state lines, but the categories they cover are broadly similar because of the MMUCC framework.
The Fault Assessment
Not every report assigns fault explicitly. Many indicate which driver received a citation or list contributing factors against each driver. When the report shows “Driver 1: Failed to Yield” and “Driver 2: No Contributing Factor,” the officer is effectively naming Driver 1 as the cause. Some reports also have a dedicated field for the officer’s opinion on the primary cause.
The assessment carries real weight with insurance adjusters, but it is not the final word. The officer arrived after the crash and reconstructed events from evidence and statements. Officers sometimes get it wrong, particularly in multi-vehicle crashes or when weather and visibility make the evidence ambiguous. Admissibility at trial is also more limited than most people expect: firsthand observations are more likely to come in than the officer’s conclusions or secondhand witness statements, and rules vary by state.
What to Do About Errors
Reports contain two types of errors, and the fix is different for each.
Factual errors are the straightforward kind: a misspelled name, wrong address, incorrect license plate, or inaccurate vehicle description. Contact the law enforcement agency and ask to speak with the officer who wrote the report. Bring documentation that shows the correct information, such as your driver’s license, vehicle registration, or insurance card. Most agencies will amend the report once you provide proof.
Disputed findings are harder. If you believe the narrative or fault determination is wrong, the agency is unlikely to rewrite the report based on disagreement alone. Officers generally won’t change their conclusions without compelling new evidence they didn’t have at the scene, such as surveillance footage or a witness who comes forward after the fact. What you can do is write a detailed supplemental statement giving your account and request that it be attached to the official report. That puts your version on record even if the officer’s narrative reads differently.
Review the report as soon as you get it. The sooner you catch errors, the easier they are to correct and the less damage they can do to your insurance claim. If the fault determination is wrong and the claim is significant, that is the point at which consulting an attorney is worth the cost.