Yearly Traffic Safety Analysis

72 CRASHES IN
WILMINGTON, VT
2012

All metrics benchmarked against2011

Total crashes in Wilmington increased from 64 in 2011 to 72 in 2012, representing a 12.5% increase year-over-year. The most notable shift was the presence of one fatal crash in 2012, compared to zero fatal crashes in 2011.

72

12.5%was 64

Total Crash Events

1

Fatal Crashes

10

-16.7%was 12

Injury Crashes

1

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 · 2012-01-01 to 2012-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall, crash incidents in Wilmington increased by 12.5%, rising from 64 total crashes in 2011 to 72 in 2012. Despite this increase in total crashes, the number of total injuries decreased by 16.7%, from 12 injuries in 2011 to 10 injuries in 2012.

When Crashes Happen

The peak day for crashes shifted from Monday in 2011, with 13 incidents, to Saturday in 2012, which recorded 19 incidents. The peak hour for crashes also changed, moving from 12 PM with 8 crashes in 2011 to 2 PM with 7 crashes in 2012.

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

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

Crash Severity Breakdown

The most significant change in severity was the occurrence of one fatal crash in 2012, resulting in a fatal rate of 1.39%, whereas no fatal crashes were reported in 2011. Injury crashes decreased in proportion, accounting for 13.9% (10 crashes) of all incidents in 2012, down from 18.8% (12 crashes) in 2011.

Outcome by Severity (Crash Events)

Fatal1fatal crashes1.4%
Injury10minor injury crashes13.9%
-16.7%prior 12
No Injury61no injury crashes84.7%
17.3%prior 52

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

Road & Environmental Conditions

The proportion of crashes occurring in adverse weather conditions decreased from 40.6% in 2011 (26 crashes) to 25% in 2012 (18 crashes), driven by a reduction in crashes during rain and freezing precipitation. Similarly, crashes on adverse road surfaces decreased from 56.3% (36 crashes) in 2011 to 45.8% (33 crashes) in 2012, primarily due to fewer crashes on snow and slush. Crashes in daylight increased from 47 in 2011 to 52 in 2012, while crashes in dark conditions also saw a slight increase from 17 to 20 incidents.

Weather

Clear34 (49.3%)
13.3%prior 30
Cloudy17 (24.6%)
142.9%prior 7
Freezing Precipitation12 (17.4%)
-14.3%prior 14
Rain5 (7.2%)
-50.0%prior 10
Wind1 (1.4%)

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

Lighting

Daylight52 (72.2%)
10.6%prior 47
Dark20 (27.8%)
17.6%prior 17

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

Road Surface

Dry36 (52.2%)
38.5%prior 26
Ice10 (14.5%)
25.0%prior 8
Snow10 (14.5%)
-33.3%prior 15
Wet8 (11.6%)
33.3%prior 6
Sand, mud, dirt, oil, gravel3 (4.3%)
Slush2 (2.9%)
-66.7%prior 6

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

Data Coverage

  • Reporting period: 2012-01-01 through 2012-12-31 (366 days)
  • Geographic scope: Wilmington, VT
  • Total crash records analyzed: 72

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

Wilmington, VT Crash Report — 2012 | ThatCarHitMe.com