Monthly Traffic Safety Analysis

1,011 CRASHES IN
VERMONT, VT
OCTOBER 2016

All metrics benchmarked againstOctober 2015

In October 2016, Vermont recorded 1,011 vehicle crashes, a 5.6% decrease from the 1,071 crashes reported in October 2015. While overall collisions declined, one of the most significant year-over-year changes was a 56.3% reduction in crashes involving pedestrians, which fell from 16 to 7 incidents. Fatalities also decreased from 5 to 3.

1,011

▼ -5.6%was 1,071

Total Crash Events

3

▼ -40.0%was 5

Fatal Crashes

197

▲ 3.7%was 190

Injury Crashes

3

▼ -40.0%was 5

Fatal Crash Events

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

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

Trend Summary

Crash data for October shows a downward trend compared to the previous year. Total crashes decreased from 1,071 in October 2015 to 1,011 in October 2016, a drop of 60 incidents. Fatalities also declined from 5 to 3, though total injuries saw a slight increase from 190 to 197.

When Crashes Happen

The temporal patterns of crashes showed some shifts between October 2015 and October 2016. Friday remained the peak day for crashes in both periods, with 205 incidents in 2016 and 202 in 2015. However, the peak hour for collisions moved from 4 p.m. in 2015 (97 crashes) to a tie between 3 p.m. and 5 p.m. in 2016, with each hour recording 100 crashes. Notably, Saturday crashes decreased from 180 to 137 year-over-year.

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

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

Crash Severity Breakdown

The severity of crashes shifted between the two periods. In October 2016, there were 3 fatal crashes, accounting for 0.3% of all incidents, a decrease from 5 fatal crashes (0.5% of total) in October 2015. Conversely, the proportion of crashes resulting in an injury increased from 17.7% (190 crashes) in the prior year to 19.5% (197 crashes) in the current year. Crashes with no injuries decreased in absolute terms from 681 to 663.

Outcome by Severity (Crash Events)

Fatal3fatal crashes0.3%
↓-40.0%prior 5
Injury197minor injury crashes19.5%
↑3.7%prior 190
No Injury663no injury crashes65.6%
↓-2.6%prior 681

Source: Vermont Crash Data · Arcgis Open Data · 2016-10-01 to 2016-10-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 · 2016-10-01 to 2016-10-31 · Most severe injury per crash record

Road & Environmental Conditions

Adverse weather conditions were a more significant factor in crashes in October 2016 compared to the previous year. Collisions occurring in rain more than doubled, increasing from 64 to 136 incidents. Correspondingly, crashes on wet road surfaces also more than doubled, rising from 90 to 187. While crashes in daylight remained the majority, their share of the total decreased from 70.5% to 66.9%, with a corresponding increase in the proportion of crashes occurring in darkness.

Weather

Clear460 (58.0%)
↓-16.5%prior 551
Cloudy161 (20.3%)
↓-9.0%prior 177
Rain136 (17.2%)
↑112.5%prior 64
Freezing Precipitation36 (4.5%)

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

Lighting

Daylight676 (67.7%)
↓-10.5%prior 755
Dark322 (32.3%)
↑6.3%prior 303

Source: Vermont Crash Data · Arcgis Open Data · 2016-10-01 to 2016-10-31 · Lighting condition field

Road Surface

Dry561 (71.3%)
↓-18.1%prior 685
Wet187 (23.8%)
↑107.8%prior 90
Snow22 (2.8%)
Sand, mud, dirt, oil, gravel7 (0.9%)
→0.0%prior 7
Water (standing / moving)5 (0.6%)
Other - Explain in Narrative3 (0.4%)
Ice1 (0.1%)
↓-88.9%prior 9
Slush1 (0.1%)

Source: Vermont Crash Data · Arcgis Open Data · 2016-10-01 to 2016-10-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: 2016-10-01 through 2016-10-31
  • Report generated: July 5, 2026

Data Coverage

  • Reporting period: 2016-10-01 through 2016-10-31 (31 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 1,011

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). "vermont, VT Crash Intelligence Report: October 2016." Published July 5, 2026. Reporting period: 2016-10-01 to 2016-10-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/statewide/october-2016-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

Vermont (Statewide) Crash Report — October 2016 | ThatCarHitMe.com