Yearly Traffic Safety Analysis

77 CRASHES IN
MIDDLESEX, VT
2017

All metrics benchmarked against2016

Total crashes remained stable year-over-year in Middlesex, VT, with 77 crashes reported in both 2016 and 2017. A significant decrease was observed in total injuries, falling from 17 in 2016 to 6 in 2017, representing a 64.7% reduction. Conversely, DUI-related crashes increased by 33.3%, rising from 3 in 2016 to 4 in 2017.

77

Total Crash Events

0

Fatal Crashes

6

-64.7%was 17

Injury Crashes

0

Fatal Crash Events

Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 57 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 numbers remained stable year-over-year in Middlesex, VT, with 77 crashes reported in both 2016 and 2017. Despite stable total crash counts, total injuries decreased by 64.7%, from 17 in 2016 to 6 in 2017. DUI crashes, however, saw an increase of 33.3%, rising from 3 in 2016 to 4 in 2017.

When Crashes Happen

Temporal patterns of crashes shifted between 2016 and 2017. The peak day for crashes moved from Tuesday, with 20 crashes in 2016, to Friday, with 21 crashes in 2017. The peak hour also changed, from 7 AM with 8 crashes in 2016 to 2 PM with 8 crashes 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

No fatal crashes or fatalities were recorded in Middlesex, VT, during either 2016 or 2017. Total injuries decreased substantially, from 17 in 2016 to 6 in 2017, marking a 64.7% reduction. Consequently, the proportion of crashes resulting in injury fell from 22.1% in 2016 to 7.8% in 2017.

Outcome by Severity (Crash Events)

Injury6minor injury crashes7.8%
-64.7%prior 17
No Injury14no injury crashes18.2%
7.7%prior 13

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

Notable shifts occurred in crash conditions between 2016 and 2017. Crashes occurring in the dark increased from 16 in 2016 to 24 in 2017, while daylight crashes decreased from 61 to 52. Crashes on dry road surfaces decreased from 13 in 2016 to 7 in 2017, and crashes on wet surfaces decreased from 11 to 3, but crashes on icy roads increased from 1 to 4.

Weather

Clear7 (36.8%)
-41.7%prior 12
Freezing Precipitation6 (31.6%)
20.0%prior 5
Rain4 (21.1%)
-50.0%prior 8
Cloudy2 (10.5%)

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

Lighting

Daylight52 (68.4%)
-14.8%prior 61
Dark24 (31.6%)
50.0%prior 16

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

Road Surface

Dry7 (41.2%)
-46.2%prior 13
Ice4 (23.5%)
Snow3 (17.6%)
Wet3 (17.6%)
-72.7%prior 11

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: Middlesex, VT
  • Total crash records analyzed: 77

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). "Middlesex, 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/middlesex/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

Middlesex, VT Crash Report — 2017 | ThatCarHitMe.com