Monthly Traffic Safety Analysis

1,053 CRASHES IN
VERMONT, VT
JANUARY 2016

All metrics benchmarked againstJanuary 2015

In January 2016, there were 1,053 total crashes, representing a 38.2% decrease from the 1,705 crashes recorded in January 2015. This substantial reduction in overall collision volume was the most prominent year-over-year change in the data. While the number of fatalities remained unchanged at 3 for both periods, the proportion of crashes involving an injury increased.

1,053

▼ -38.2%was 1,705

Total Crash Events

3

Fatal Crashes

195

▼ -2.5%was 200

Injury Crashes

3

Fatal Crash Events

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

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

Trend Summary

The overall trend from January 2015 to January 2016 shows a significant decline in traffic collisions. Total crashes fell by 38.2%, from 1,705 to 1,053. While fatalities were stable at 3 in both periods, the number of reported injuries saw a slight decrease of 2.5% from 200 to 195.

When Crashes Happen

Temporal crash patterns shifted notably year-over-year. The peak day for collisions moved from Friday, which saw 357 crashes in January 2015, to Tuesday with 191 crashes in January 2016. The peak hour for crashes also shifted slightly later in the afternoon, from the 4 p.m. hour (149 crashes) in the prior year to the 5 p.m. hour (83 crashes) in the current period.

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

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

Crash Severity Breakdown

Although the absolute number of fatal crashes was unchanged at 3, the fatal crash rate per 100 crashes increased from 0.18 to 0.28 year-over-year. A more pronounced change was seen in injury crashes; the proportion of all collisions that resulted in an injury rose from 11.7% in January 2015 to 18.5% in January 2016. This indicates that while total crashes decreased, the remaining crashes were more likely to be severe.

Outcome by Severity (Crash Events)

Fatal3fatal crashes0.3%
→0.0%prior 3
Injury195minor injury crashes18.5%
↓-2.5%prior 200
No Injury805no injury crashes76.4%
↓-20.8%prior 1,017

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

Road & Environmental Conditions

Crash conditions shifted significantly between the two periods, with a larger share of incidents occurring in seemingly favorable conditions. The proportion of crashes on dry roads increased from 22.6% in January 2015 to 40.0% in January 2016. Similarly, crashes in clear weather accounted for 42.9% of the total in the current period, up from 29.3% in the prior year. The distribution of crashes by lighting conditions remained relatively stable.

Weather

Clear452 (49.4%)
↓-9.4%prior 499
Freezing Precipitation237 (25.9%)
↓-26.6%prior 323
Cloudy213 (23.3%)
↓-15.1%prior 251
Rain9 (1.0%)
↓-57.1%prior 21
Wind4 (0.4%)
↓-33.3%prior 6

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

Lighting

Daylight765 (73.4%)
↓-39.8%prior 1,270
Dark277 (26.6%)
↓-34.2%prior 421

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

Road Surface

Dry421 (46.1%)
↑9.1%prior 386
Snow234 (25.6%)
↓-34.3%prior 356
Wet135 (14.8%)
↓-6.3%prior 144
Ice90 (9.9%)
↓-46.7%prior 169
Slush19 (2.1%)
↓-56.8%prior 44
Other - Explain in Narrative9 (1.0%)
↓-10.0%prior 10
Sand, mud, dirt, oil, gravel5 (0.5%)

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

Data Coverage

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

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: January 2016." Published July 5, 2026. Reporting period: 2016-01-01 to 2016-01-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/statewide/january-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 — January 2016 | ThatCarHitMe.com