Yearly Traffic Safety Analysis

25 CRASHES IN
ENOSBURG, VT
2018

All metrics benchmarked against2017

In 2018, Enosburg experienced a total of 25 crashes, a decrease of 28.6% compared to the 35 crashes recorded in 2017. This notable reduction in overall crash incidents is the most significant year-over-year shift. The peak day for crashes also shifted from Tuesday in 2017 to Saturday in 2018.

25

-28.6%was 35

Total Crash Events

0

Fatal Crashes

7

-30.0%was 10

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. 2 crashes with unreported severity are not shown in the severity breakdown.

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

Trend Summary

Overall crash trends in Enosburg show a decrease, with total crashes falling from 35 in 2017 to 25 in 2018, representing a 28.6% reduction. Similarly, total injuries decreased from 10 in 2017 to 7 in 2018. Fatalities remained stable at zero for both years.

When Crashes Happen

The temporal patterns of crashes showed shifts year-over-year. In 2017, the peak day for crashes was Tuesday with 10 incidents, while in 2018, Saturday became the peak day with 8 crashes. The peak hour for crashes also shifted from 12 p.m. with 5 crashes in 2017 to 4 p.m. with 3 crashes in 2018.

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

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

Crash Severity Breakdown

The fatal crash rate remained at 0% for both 2017 and 2018, indicating no fatal crashes in either year. The proportion of injury crashes was similar, with 28% (7 crashes) in 2018 and 28.6% (10 crashes) in 2017. However, the proportion of crashes with no injuries increased from 40% (14 crashes) in 2017 to 64% (16 crashes) in 2018.

Outcome by Severity (Crash Events)

Injury7minor injury crashes28%
-30.0%prior 10
No Injury16no injury crashes64%
14.3%prior 14

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

Road & Environmental Conditions

There were notable shifts in crash conditions. Crashes occurring in clear weather decreased from 14 in 2017 to 8 in 2018, while crashes during freezing precipitation increased from 5 to 8 and cloudy conditions rose from 3 to 6. Daylight crashes decreased from 24 in 2017 to 15 in 2018, and dark conditions saw a slight reduction from 11 to 10. For road surface, dry road crashes decreased from 16 to 11, while snow-related crashes increased from 5 to 7.

Weather

Clear8 (36.4%)
-42.9%prior 14
Freezing Precipitation8 (36.4%)
60.0%prior 5
Cloudy6 (27.3%)

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

Lighting

Daylight15 (60.0%)
-37.5%prior 24
Dark10 (40.0%)
-9.1%prior 11

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

Road Surface

Dry11 (50.0%)
-31.3%prior 16
Snow7 (31.8%)
40.0%prior 5
Ice2 (9.1%)
Sand, mud, dirt, oil, gravel1 (4.5%)
Slush1 (4.5%)

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

Data Coverage

  • Reporting period: 2018-01-01 through 2018-12-31 (365 days)
  • Geographic scope: Enosburg, VT
  • Total crash records analyzed: 25

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