Yearly Traffic Safety Analysis

5 CRASHES IN
WELLS, VT
2018

All metrics benchmarked against2017

In 2018, there were 5 crashes in Wells, an increase from 4 crashes reported in 2017, representing a 25% rise year-over-year. A significant shift was observed in DUI-related crashes, which decreased from 2 in 2017 to 0 in 2018.

5

25.0%was 4

Total Crash Events

0

Fatal Crashes

2

100.0%was 1

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.

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, crashes in Wells increased by 25% year-over-year, rising from 4 crashes in 2017 to 5 crashes in 2018. Concurrently, the number of injured persons doubled, increasing from 1 in 2017 to 2 in 2018. Fatalities remained stable at 0 for both periods.

When Crashes Happen

The temporal distribution of crashes showed shifts year-over-year. The peak day for crashes moved from Wednesday in 2017 (2 crashes) to Tuesday in 2018 (2 crashes). While 6p remained a peak hour, the number of crashes at this time increased from 1 in 2017 to 2 in 2018. Notably, crashes on Wednesday decreased from 2 in 2017 to 0 in 2018, while crashes on Tuesday increased from 0 to 2.

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

There were no fatal crashes or fatalities reported in either 2017 or 2018. However, the total number of injured persons increased by 100%, from 1 in 2017 to 2 in 2018. Consequently, the proportion of crashes resulting in injury rose from 25% (1 of 4 crashes) in 2017 to 40% (2 of 5 crashes) in 2018.

Outcome by Severity (Crash Events)

Injury2minor injury crashes40%
100.0%prior 1
No Injury3no injury crashes60%
0.0%prior 3

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

Weather conditions during crashes saw a shift, with crashes in freezing precipitation increasing from 0 in 2017 to 2 in 2018, while crashes in cloudy conditions decreased from 1 to 0. Crashes occurring in dark lighting conditions increased from 2 in 2017 to 3 in 2018. Data for road surface conditions in 2017 was not available for comparison.

Weather

Clear3 (60.0%)
Freezing Precipitation2 (40.0%)

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

Lighting

Dark3 (60.0%)
Daylight2 (40.0%)

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

Road Surface

Dry2 (40.0%)
Ice1 (20.0%)
Snow1 (20.0%)
Wet1 (20.0%)

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

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). "Wells, 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/wells/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

Wells, VT Crash Report — 2018 | ThatCarHitMe.com