An overview of Virginia's computerized crash records systems.
archive: archived pipeline: cataloged verified
Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)
Summary
This report provides a comprehensive overview of Virginia’s computerized crash records systems, addressing the lack of formal documentation regarding how various state and local agencies capture, store, and process traffic crash data. Motivated by a request from the Virginia Department of Motor Vehicles (DMV) to prepare background information for an independent traffic records audit and to support the development of a statewide Safety Management System, the study aims to inventory existing systems, identify data flow issues, and recommend improvements for data utility, accessibility, and accuracy. The research was conducted between June 1994 and July 1995 by the Virginia Transportation Research Council. The methodology involved categorizing agencies into "primary users" (those affecting data flow) and "secondary users" (those using data without affecting integrity). Primary users, including local law enforcement agencies (e.g., Fairfax County, Charlottesville, Powhatan County), statewide agencies (DMV, VDOT, State Police, VASAP, OEMS, DOE, DOC), and the Transportation Safety Training Center, were interviewed via site visits or telephone. These interviews were supplemented by the examination of computer printouts, data dictionaries, and agency-generated literature. Descriptions of each agency’s system were created and iteratively verified with the respective agencies to ensure accuracy. Secondary users were assessed primarily through telephone conversations. The findings reveal a fragmented landscape of crash data management. Local law enforcement agencies utilize diverse systems, such as the Micro Traffic Records System (MTRS) or mainframe databases, but none capture all data elements from the standard FR-300P crash report. For instance, Fairfax County enters approximately two-thirds of data elements, while MTRS users enter only about one-third, omitting details like driver condition or vehicle repair costs. Data from local systems are subsequently re-entered by the DMV into the statewide Centralized Accident Processing (CAP) system. The study identified significant discrepancies in data handling, such as differing definitions of property damage costs between DMV, VDOT, and local records. Furthermore, the report highlights issues regarding data integrity, duplication of effort, and limited coordination among agencies. It also notes that many crashes remain unrecorded if they are not deemed "reportable," and that current forms inadequately capture restraint usage for uninjured occupants. The significance of this report lies in its detailed mapping of Virginia’s crash data infrastructure, which serves as a foundational document for future audits and the implementation of a Safety Management System. By documenting the specific capabilities, limitations, and data flows of each agency, the report provides evidence-based recommendations to improve the linkage of crash data with other datasets, such as emergency medical services and roadway information. It underscores the need for standardized data entry, better documentation of database capabilities, and enhanced cooperation among providers and users to ensure that crash data are accurate, accessible, and useful for safety research and policy-making.
Key finding
Virginia's crash data systems suffer from fragmentation, duplication of effort, and inconsistent data entry practices across state and local agencies, necessitating improved coordination and documentation to enhance data utility and accuracy.
Methodology
survey
Provenance
The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | rosap | — | — | 2 | 2026-05-23 |
| archive | success | — | — | — | 1 | 2026-05-23 |
| extract | success | cached | — | — | 2 | 2026-06-10 |
| clean | success | — | — | — | 1 | 2026-06-01 |
| chunk | success | — | — | — | 1 | 2026-06-01 |
| embed | success | — | — | — | 1 | 2026-06-02 |
| enrich | success | — | — | — | 1 | 2026-05-23 |
| promote | success | — | — | — | 1 | 2026-05-23 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 3 | 2026-06-10 |
| tag | success | vector_similarity | — | — | 19 | 2026-06-11 |
| verify | partial | — | — | — | 2 | 2026-06-10 |
Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified_with_issues.
Topics
Ranked by relevance to this paper. Hover a topic for its definition.
- incidence prevalence
- naturalistic crash near crash
- in depth crash investigation
- causation analyses
- crash typology
Information type
What kind of knowledge this paper contributes, grouped by family — independent of topic (what it is about) and method (how it was studied).
- Empirical Findings: crash risk outcomes
- Methodological Resource: dataset resource