Police Reports in Virginia

Find and request official police reports from any city in Virginia. Our comprehensive database covers all 680 cities and counties throughout the state.

680

Cities Covered

3-5

Business Days Average

100%

Secure & Confidential

Primary Agency

Virginia State Police

Processing Time

5-10 business days

Fee Range

$12-$15 for most reports

Report Forms

FR300 Series, State Police Reports, Local Reports

Online Availability

Online requests available

Secure Process

Protected & confidential

About Virginia Police Reports

Important Information

FR300 series forms in use with multiple overlay versions

Processing Details

Northern Virginia has separate procedures

Additional Notes

FR300P and FR300T overlays available

Available Report Types

FR300 Series
State Police Reports
Local Reports

REQUEST A VIRGINIA POLICE REPORT

Select your city below to start your official police report request

✓ 5-10 business days average processing

✓ Secure online submission

✓ 24/7 customer support

Virginia Police Crash Report Form

Virginia's road network ranges from quiet rural lanes to busy interstates carrying commuters into Richmond, Norfolk and the nation's capital. When collisions happen, the investigating officer's police reports become the official record of the crash. These accident reports, known formally as the Virginia Police Crash Report (FR‑300P), document key facts such as where the crash occurred, who was involved and how the vehicles collided. Without a standardized form, information would be inconsistent from one jurisdiction to the next, making it nearly impossible to compare data or identify dangerous trends. Consistent crash reports enable law enforcement to reconstruct collisions, allow insurance companies to assign liability fairly and help transportation planners prioritize safety improvements. Virginia began using the FR‑300 series of forms decades ago and continues to revise them as laws and vehicle technology evolve.

Official Report Forms

Virginia Police Crash Report Form FR-300P (Rev. 7/2007)

Virginia Crash Facts and Statistics

Form overview

The Commonwealth's official crash form is titled the Virginia Police Crash Report (FR‑300P). The version examined in this article is the revision dated July 2007. This revision date is visible on the form's footer and in the manual provided to officers. The Virginia Department of Motor Vehicles (DMV) issues the form through its Traffic Records Electronic Data System (TREDS) and requires that all crashes involving injury, death or at least $1,500 in property damage be reported. The report is supported by a companion manual (FR‑300M) and code sheet that explain the numeric fields and coding instructions. Officers complete the report either electronically or on paper; the completed report is uploaded into TREDS, where it becomes part of the statewide crash database. The FR‑300P consists of six primary pages and additional supplements. The first three pages collect core information about the crash, drivers and vehicles. The fourth page contains a diagram and narrative. Pages five and six are used when commercial vehicles, pedestrians or extra occupants are involved. Supplementary pages allow officers to document more vehicles or people as needed. Using a single, standardized form across all Virginia jurisdictions ensures that crash data can be compared across years and regions.

Section breakdown

Page 1 – Basic crash information and participants

The top of the first page provides a general overview of the crash. Officers record the date, time and location of the collision, including the road name, direction of travel, intersection or block number and whether the crash occurred on a highway, rural road or at an intersection. There is also a space to note the number of vehicles involved and the estimated dollar amount of damage. If the crash is classified as a hit and run or involves a fatality, the officer checks the appropriate box. Because insurance claims often hinge on the estimated damage, drivers should review this field carefully and request corrections if necessary. Below the crash overview, the page is divided into two mirrored sections—one for each of the first two vehicles involved. Each section lists the driver's name, address, date of birth, license number and status, along with contact information and whether the driver was injured. There are check boxes to indicate seat belt use, airbag deployment, ejection and whether extrication was needed. The officer also enters the driver's insurance company and policy number. Beneath the driver information, the vehicle section records the year, make, model, color, Vehicle Identification Number (VIN), license plate number and state. Officers note whether the vehicle was towed, its travel speed and the direction of travel prior to impact. If more than two vehicles are involved, additional vehicle pages are attached. At the bottom of page 1, the report lists passengers and their seating positions. Only passengers who were injured or killed are named; uninjured passengers are counted but unnamed. For each passenger, the officer records seat location, seat belt or restraint use, airbag deployment and the severity of injury, coded as fatal, incapacitating, non‑incapacitating, possible injury or no injury. This level of detail helps researchers evaluate the effectiveness of seat belts and airbag systems.

Page 2 – Driver actions and vehicle characteristics

Page 2 of the FR‑300P delves into factors that may have contributed to the crash. Along the left side, the officer selects codes corresponding to driver actions and conditions. These include speeding, failure to yield, disregarding signals, following too closely, improper lane change and distracted driving. Other codes indicate whether the driver was impaired by alcohol or drugs, fatigued or experiencing a medical condition. The form also records whether a breath or blood test was conducted, the test results and whether citations were issued. This information is critical for law enforcement and prosecutors when determining whether criminal charges such as driving under the influence are warranted. The right side of page 2 focuses on the vehicle body type, maneuver and condition. Officers choose codes from the manual to describe the vehicle (for example, passenger car, pickup truck, SUV, motorcycle or large truck). They note the vehicle's maneuver at the time of the crash—going straight, slowing, stopping, turning left or right, passing or backing. Another set of codes indicates the vehicle condition, such as defective brakes, worn tires or broken headlights. Defective equipment can be a significant crash factor, and identifying these issues helps insurers and safety agencies determine whether mechanical failure played a role.

Page 3 – Environment and road conditions

The third page captures details about the crash environment. The left side of the page uses codes to indicate light conditions (daylight, dawn/dusk, dark lighted or dark unlighted), weather conditions (clear, rainy, snowy, foggy, etc.) and roadway surface (dry, wet, icy, sanded). Officers also record whether the crash occurred in a work zone, school zone or railroad crossing, and the posted speed limit. A section called "type of crash" identifies the manner of collision—such as rear‑end, head‑on, sideswipe, angle or single‑vehicle run‑off. These classifications help analysts identify common crash types and design targeted countermeasures. Below the environmental codes, the officer checks boxes for traffic control devices present at the scene (stop sign, yield sign, traffic signal, flashing signal, officer or none). There are also spaces to record whether the crash occurred at a junction, and if so, whether it was an intersection, interchange, driveway or other. The page provides fields for road alignment (straight, curve) and surface type (asphalt, concrete, gravel). By standardizing these details, Virginia's crash database can reveal patterns like high crash rates on wet curves or intersections with inadequate signage.

Page 4 – Diagram and narrative

Page 4 is devoted to the officer's crash diagram and narrative. The diagram is a bird's‑eye sketch of the roadway, showing lanes, intersections, traffic control devices and the paths of the vehicles before, during and after the collision. The officer uses arrows to indicate the direction of travel and marks the point of impact with an "X." A well‑drawn diagram helps insurers and engineers visualize the crash without visiting the scene. Next to the diagram, a large narrative section allows the officer to describe the crash in plain language. The narrative explains how the events unfolded, referencing the numbered "sequence of events" codes printed beneath it. Officers list the first harmful event (e.g., collision with another vehicle or object) and subsequent events, then identify the most harmful event. This information is essential for determining primary causation and calculating crash severity. If non‑vehicle property was damaged, the officer documents what was hit, such as guardrails, signs or fences. The narrative may also include statements from drivers and witnesses that could be significant in legal proceedings.

Page 5 – Commercial vehicle supplement

When a crash involves a commercial motor vehicle, the officer must complete page 5. This supplemental page records the vehicle's configuration (single unit truck, tractor‑semi‑trailer, double trailer), cargo body type (van, flatbed, tanker) and whether hazardous materials were involved. It also lists the commercial carrier's name, address, U.S. DOT number and phone number. The driver's commercial driver's license class and endorsement are recorded, along with hours of service and whether the driver was transporting passengers. Because commercial vehicle crashes often result in severe injuries and significant property damage, federal regulations require detailed documentation. Page 5 ensures that Virginia meets these requirements and can share data with the Federal Motor Carrier Safety Administration.

Page 6 – Pedestrian and additional occupant supplement

Crashes involving pedestrians, cyclists or more passengers than fit on page 1 require the officer to complete page 6. The top of the page records each pedestrian's or non‑motorist's name, contact information and injuries. Officers note the person's activity (crossing at crosswalk, walking along roadway, standing, etc.), their action prior to impact and any contributing circumstances such as alcohol impairment or failure to obey signals. The page also includes fields for additional passengers not listed on page 1, capturing their seat position, restraints, airbag deployment and injuries. By capturing this data, the report ensures that non‑motorists and extra occupants are not overlooked in the crash record.

Code sheets and supplements

Throughout the FR‑300P, officers rely on a code sheet to convert detailed descriptions into numeric codes. The accompanying FR‑300M manual explains every code and provides instructions for filling out the form. Codes exist for weather conditions, vehicle type, driver contributing factors, road surface, alignment and more. By using codes instead of free text, the state can efficiently input thousands of crash reports into TREDS and analyze them with computer algorithms. When the crash involves more than two vehicles or additional people, officers attach supplemental pages that mirror the main report structure.

Use cases

Law enforcement and crash investigation

For police agencies, the FR‑300P is an essential tool for crash investigation. Officers use the structured fields to gather evidence, while supervisors review reports to ensure completeness and accuracy. The driver action and vehicle defect codes on page 2 help investigators identify primary causes such as distracted driving, speeding or brake failure. The narrative and diagram on page 4 allow reconstruction specialists to visualize the sequence of events and verify whether the physical evidence matches witness statements. When crashes involve fatalities, these police reports can support criminal charges for reckless driving, impaired driving or vehicular manslaughter.

Insurance and legal claims

Insurers depend on accident reports to determine liability and process claims. The FR‑300P lists each party's insurance information and documents contributing factors, helping adjusters assign fault. The injury severity and medical transport fields allow insurers to evaluate medical claims quickly. Attorneys representing crash victims use the narrative, diagram and codes to argue negligence. For example, if the report shows that a driver failed to yield and was traveling above the speed limit, a lawyer can use that evidence in settlement negotiations or at trial. Conversely, defense attorneys examine the report for inconsistencies or missing information that might mitigate their client's liability.

Transportation planning and research

The Virginia Department of Transportation (VDOT) and regional planners use crash data from the FR‑300P to identify dangerous roads and intersections. By analyzing patterns in the environmental and road condition codes on page 3, engineers can determine whether poor lighting, inadequate signage or slippery surfaces contribute to crashes. Crash diagrams and narratives provide context for designing countermeasures such as rumble strips, better signage or redesigned intersections. The data also feed into statewide Highway Safety Improvement Program applications, helping Virginia secure federal funding for safety projects.

Public health and education

Public health agencies study crash reports to understand injury trends and evaluate safety programs. The passenger injury data on page 1 and the pedestrian information on page 6 help researchers assess the effectiveness of seat belt campaigns, child restraint use and pedestrian safety initiatives. If data show a rise in crashes involving young drivers distracted by mobile devices, educational programs can be targeted accordingly. Likewise, an increase in crashes in work zones may prompt outreach to motorists and contractors on work zone safety.

Accountability and transparency

Finally, the FR‑300P promotes accountability. Each report lists the investigating officer's name, badge number and agency, providing a point of contact for follow‑up questions. Supervisors review the report for accuracy, and the standardized format makes it harder to omit critical information. By documenting the who, what, when, where and how of each crash, the report helps ensure that victims' rights are protected and that negligent drivers are held accountable.

Conclusion

The Virginia Police Crash Report (FR‑300P) is more than a bureaucratic requirement; it is a comprehensive tool that supports safety, justice and data‑driven decision‑making. By capturing detailed information about the crash scene, driver actions, vehicle conditions and environmental factors, the form allows stakeholders to reconstruct events and identify patterns. The accompanying code sheet ensures that data are consistent and easy to analyze. Whether used by law enforcement, insurers, transportation planners, public health researchers or attorneys, these police reports and crash reports provide the foundation for improving road safety across the Commonwealth. In a state where traffic ranges from rural byways to some of the busiest highways on the East Coast, such standardization is essential for protecting lives and ensuring accountability.

Need a Virginia Police Report?

Now that you understand the Virginia police report system, select your city below to begin your request.

Our service simplifies the request process for all Virginia jurisdictions

All 680 Cities Available

Every city page is accessible. Search for your city or browse the list below.

Virginia Beach

County: Virginia Beach

Population: 1.431.821

ZIP Codes: 23459, 23451, 23453...