Yearly Traffic Safety Analysis

30 CRASHES IN
ENOSBURG, VT
2016

All metrics benchmarked against2015

In 2016, there were 30 crashes, representing a slight decrease of 3.23% compared to 31 crashes in 2015. The most significant year-over-year shift was the complete absence of fatalities in 2016, down from one fatality recorded in 2015.

30

-3.2%was 31

Total Crash Events

0

-100.0%was 1

Fatal Crashes

11

83.3%was 6

Injury Crashes

0

-100.0%was 1

Fatal Crash Events

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

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

Trend Summary

Overall, crash frequency showed a slight downward trend, with total crashes decreasing by 3.23% from 31 in 2015 to 30 in 2016. Fatalities were eliminated, dropping from 1 in 2015 to 0 in 2016, while total injuries increased by 83.33%, from 6 in 2015 to 11 in 2016.

When Crashes Happen

The peak day for crashes remained Friday in both years, though the number of crashes on Fridays decreased from 8 in 2015 to 5 in 2016. The peak hour shifted from 3 p.m. in 2015, which saw 6 crashes, to 4 p.m. in 2016, which recorded 5 crashes.

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

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

Crash Severity Breakdown

Fatal crashes decreased significantly, from 1 in 2015 (3.2% of total crashes) to 0 in 2016. Conversely, injury crashes increased from 6 (19.4% of total crashes) in 2015 to 11 (36.7% of total crashes) in 2016. Crashes resulting in no injury also increased, from 5 (16.1% of total crashes) in 2015 to 11 (36.7% of total crashes) in 2016.

Outcome by Severity (Crash Events)

Injury11minor injury crashes36.7%
83.3%prior 6
No Injury11no injury crashes36.7%
120.0%prior 5

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

Road & Environmental Conditions

Regarding weather conditions, crashes occurring in Freezing Precipitation increased from 2 in 2015 to 5 in 2016, and crashes in Cloudy conditions doubled from 2 to 4. For lighting conditions, crashes occurring in daylight decreased from 28 to 23, while those in dark conditions more than doubled from 3 to 7. On road surfaces, crashes on snow increased from 1 in 2015 to 4 in 2016, and new categories for wet (4 crashes) and slush (3 crashes) appeared in 2016.

Weather

Clear10 (47.6%)
25.0%prior 8
Freezing Precipitation5 (23.8%)
Cloudy4 (19.0%)
Rain2 (9.5%)

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

Lighting

Daylight23 (76.7%)
-17.9%prior 28
Dark7 (23.3%)

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

Road Surface

Dry10 (45.5%)
0.0%prior 10
Snow4 (18.2%)
Wet4 (18.2%)
Slush3 (13.6%)
Ice1 (4.5%)

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

Data Coverage

  • Reporting period: 2016-01-01 through 2016-12-31 (366 days)
  • Geographic scope: Enosburg, VT
  • Total crash records analyzed: 30

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

Enosburg, VT Crash Report — 2016 | ThatCarHitMe.com