Monthly Traffic Safety Analysis

955 CRASHES IN
VERMONT, VT
FEBRUARY 2012

All metrics benchmarked againstFebruary 2011

In February 2012, Vermont recorded 955 traffic crashes, a 26.4% decrease from the 1,297 crashes reported in February 2011. Despite this overall reduction in collisions, the total number of fatalities increased from 4 to 6. The most significant contributing change was in road surface conditions, with crashes on 'Dry' roads becoming the most frequent type in 2012, whereas 'Snow' was the leading condition in 2011.

955

▼ -26.4%was 1,297

Total Crash Events

6

▲ 50.0%was 4

Fatal Crashes

161

▼ -14.4%was 188

Injury Crashes

6

▲ 50.0%was 4

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

Trend Summary

Year-over-year data for February shows a significant downward trend in the total number of crashes, with a 26.4% decrease from 1,297 in 2011 to 955 in 2012. The number of injuries also fell by 14.4%, from 188 to 161. In contrast to these trends, total fatalities increased from 4 in February 2011 to 6 in February 2012.

When Crashes Happen

The temporal patterns of crashes shifted between the two periods. In February 2012, the peak day for crashes was Friday with 201 incidents, whereas in February 2011, the peak was Tuesday with 242 incidents. The peak hour for crashes also changed, moving from the 4 p.m. hour (118 crashes) in the prior year to the 3 p.m. hour (91 crashes) in the current year.

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

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

Crash Severity Breakdown

While total crashes decreased, the severity of crashes increased in February 2012 compared to the previous year. The fatal crash rate more than doubled, rising from 0.31% to 0.63% of all crashes. Similarly, the proportion of crashes resulting in an injury increased from 14.5% to 16.9%, while the share of crashes with no injuries decreased from 85.0% to 82.3%.

Outcome by Severity (Crash Events)

Fatal6fatal crashes0.6%
↑50.0%prior 4
Injury161minor injury crashes16.9%
↓-14.4%prior 188
No Injury786no injury crashes82.3%
↓-28.7%prior 1,103

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

Road & Environmental Conditions

A significant change in crash conditions was observed between the two periods, particularly concerning road surfaces. In February 2012, crashes on 'Dry' roads accounted for 52.3% of all incidents, a substantial increase from 27.2% in the prior year. Conversely, the proportion of crashes on 'Snow' covered roads dropped from 35.0% in February 2011 to 19.1% in February 2012. The share of crashes occurring in 'Daylight' also decreased from 77.0% to 69.4% year-over-year.

Weather

Clear437 (49.3%)
↓-12.8%prior 501
Freezing Precipitation211 (23.8%)
↓-36.6%prior 333
Cloudy204 (23.0%)
↓-35.2%prior 315
Rain31 (3.5%)
↑287.5%prior 8
Wind4 (0.5%)
↓-69.2%prior 13

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

Lighting

Daylight663 (69.8%)
↓-33.6%prior 998
Dark287 (30.2%)
↑3.2%prior 278

Source: Vermont Crash Data · Arcgis Open Data · 2012-02-01 to 2012-02-29 · Lighting condition field

Road Surface

Dry499 (55.7%)
↑41.4%prior 353
Snow182 (20.3%)
↓-59.9%prior 454
Wet98 (10.9%)
↓-55.7%prior 221
Ice83 (9.3%)
↓-1.2%prior 84
Slush18 (2.0%)
↓-73.1%prior 67
Sand, mud, dirt, oil, gravel10 (1.1%)
Other - Explain in Narrative6 (0.7%)
↓-14.3%prior 7

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

Data Coverage

  • Reporting period: 2012-02-01 through 2012-02-29 (29 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 955

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