Yearly Traffic Safety Analysis

105 CRASHES IN
WESTMINSTER, VT
2017

All metrics benchmarked against2016

Total crashes in 2017 increased by 45.83% to 105, up from 72 crashes in 2016. This represents a significant year-over-year rise in overall crash incidents. Despite the increase in total crashes, the number of fatalities remained stable at 1 in both periods.

105

45.8%was 72

Total Crash Events

1

Fatal Crashes

11

-8.3%was 12

Injury Crashes

1

Fatal Crash Events

Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 62 crashes with unreported severity are not shown in the severity breakdown.

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall crash incidents in Westminster showed an upward trend, with total crashes increasing by 45.83% from 72 in 2016 to 105 in 2017. While total fatalities remained constant at 1, the number of injuries decreased slightly by 8.33%, from 12 in 2016 to 11 in 2017. This indicates a notable increase in less severe crashes year-over-year.

When Crashes Happen

The peak day for crashes shifted from Saturday in 2016 (23 crashes) to Friday in 2017 (22 crashes). The peak hour for crashes remained 3 PM in both years, with incidents increasing by 44.44% from 9 crashes in 2016 to 13 crashes in 2017. Notably, Monday crashes more than doubled, rising from 10 in 2016 to 22 in 2017.

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Crash date field aggregated by weekday

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

The number of fatal crashes remained consistent at 1 in both 2016 and 2017, though the fatal crash rate decreased from 1.39% to 0.95% due to the overall increase in crashes. Injury crashes saw a slight decrease from 12 in 2016 to 11 in 2017. The proportion of injury crashes also declined from 16.7% of total crashes in 2016 to 10.5% in 2017.

Outcome by Severity (Crash Events)

Fatal1fatal crashes1%
0.0%prior 1
Injury11minor injury crashes10.5%
-8.3%prior 12
No Injury31no injury crashes29.5%
-32.6%prior 46

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Severity derived from reported fatal/injury indicators (no KABCO A/B/C codes)

Severity Distribution (Crash Events)

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Most severe injury per crash record

Road & Environmental Conditions

Under weather conditions, crashes occurring in clear weather decreased from 31 in 2016 to 18 in 2017, while crashes during freezing precipitation increased from 4 to 7. Regarding lighting, crashes occurring in daylight increased from 51 to 60, and crashes in dark conditions more than doubled, rising from 21 in 2016 to 45 in 2017. For road surface, dry road crashes decreased from 35 to 24, while wet road crashes slightly increased from 7 to 8.

Weather

Clear18 (43.9%)
-41.9%prior 31
Cloudy11 (26.8%)
-8.3%prior 12
Freezing Precipitation7 (17.1%)
Rain5 (12.2%)
-37.5%prior 8

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Weather condition at time of crash

Lighting

Daylight60 (57.1%)
17.6%prior 51
Dark45 (42.9%)
114.3%prior 21

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Lighting condition field

Road Surface

Dry24 (57.1%)
-31.4%prior 35
Wet8 (19.0%)
14.3%prior 7
Snow6 (14.3%)
20.0%prior 5
Ice3 (7.1%)
Water (standing / moving)1 (2.4%)

Source: Vermont Crash Data · Arcgis Open Data · 2017-01-01 to 2017-12-31 · Road surface condition field

Data Sources & Methodology

Primary Data Source

All crash data in this report is sourced from Vermont Crash Data, accessed programmatically via the Arcgis Open Data API (SODA). This dataset contains official police-reported motor vehicle traffic crash records maintained by the reporting jurisdiction's law enforcement agency. Records are published to the open data portal by the municipality and are subject to the portal's terms of use.

Data Retrieval

  • Access method: Arcgis Open Data API (SoQL queries)
  • Data format: Structured JSON via REST API
  • Record types queried: Crash events, person records, and vehicle unit records
  • Date filter applied: 2017-01-01 through 2017-12-31
  • Report generated: July 5, 2026

Data Coverage

  • Reporting period: 2017-01-01 through 2017-12-31 (365 days)
  • Geographic scope: Westminster, VT
  • Total crash records analyzed: 105

Analytical Methodology

  • Severity classification: Uses the KABCO injury scale (K=Fatal, A=Incapacitating injury, B=Non-incapacitating injury, C=Possible injury, O=No injury/property damage only), the standard classification in U.S. Model Minimum Uniform Crash Criteria (MMUCC). Severity is assigned per crash event based on the most severe injury in that crash. A single fatal crash (K) may involve multiple fatalities; therefore the "Persons Killed" count in the headline KPIs may differ from the "Fatal" crash count in the severity breakdown.
  • Contributing factors: Reflect the officer-determined primary contributory cause recorded at the time of the crash report. These are preliminary determinations and may not reflect final investigation findings.
  • Hit-and-run classification: Based on the hit-and-run indicator field in the official crash report, as determined by the responding officer at the scene.
  • Temporal analysis: Day-of-week and hour-of-day distributions are computed from the crash date/time timestamp in each record.
  • Demographics: Age and sex distributions are drawn from person-level records linked to each crash event. A single crash may involve multiple persons.
  • Vehicle data: Make information is drawn from vehicle unit records linked to each crash event.
  • AI commentary: Narrative sections are generated by Google Gemini (large language model) based on the structured data. Commentary is descriptive, not predictive, and should not be interpreted as expert opinion.

Limitations & Disclaimers

  • Only crashes reported to and documented by law enforcement are included. Minor incidents, unreported crashes, and near-misses are not captured in this dataset.
  • Data reflects conditions at the time of the initial police report and may be subject to subsequent corrections, reclassifications, or supplements by the reporting agency.
  • Open data portal records may experience a publication lag - recently occurring crashes may not yet appear in the dataset at the time of report generation.
  • AI-generated commentary is produced by a large language model and is intended to highlight patterns in the data. It does not constitute legal, medical, or professional analysis.
  • Percentages are calculated from reported data and are subject to rounding.

Non-Affiliation Disclosure

This report is produced independently by ThatCarHitMe.com (Injuria.ai). It is not affiliated with, endorsed by, or produced in partnership with any law enforcement agency, municipal government, state department of transportation, or the National Highway Traffic Safety Administration (NHTSA). Data is sourced from publicly available government open data portals.

Data License

The underlying crash data is provided under the municipality's Open Data Terms of Use and is made available to the public for unrestricted use. This analysis and report is © 2026 Injuria.ai and may be cited with attribution using the suggested citation below.

Corrections & Feedback

If you believe any data in this report is inaccurate or have questions about our methodology, please contact: data@injuria.ai. We are committed to accuracy and will issue corrections promptly.

Suggested Citation

ThatCarHitMe.com (Injuria.ai). "Westminster, VT Crash Intelligence Report: 2017." Published July 5, 2026. Reporting period: 2017-01-01 to 2017-12-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/westminster/2017-annual-report

About the Publisher

ThatCarHitMe.com is a crash data intelligence platform developed by Injuria.ai, a legal technology company specializing in traffic safety analytics. We aggregate and analyze publicly available government crash data to produce structured intelligence reports for communities, researchers, journalists, and legal professionals. Our reports combine programmatic data retrieval from official open data portals with AI-assisted narrative analysis.

Questions about this report's data or methodology: data@injuria.ai

ThatCarHitMe.com · An Injuria.ai Company

Westminster, VT Crash Report — 2017 | ThatCarHitMe.com