Monthly Traffic Safety Analysis

1,297 CRASHES IN
VERMONT, VT
FEBRUARY 2011

All metrics benchmarked againstFebruary 2010

In February 2011, Vermont recorded 1,297 traffic crashes, a 58.6% increase from the 818 crashes reported in February 2010. This year-over-year comparison shows a significant rise in total collisions, accompanied by an increase in both injuries and fatalities. The most substantial shift was the overall volume of crashes, which grew by 479 incidents compared to the previous year.

1,297

58.6%was 818

Total Crash Events

4

300.0%was 1

Fatal Crashes

188

12.6%was 167

Injury Crashes

4

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

Source: Vermont Crash Data · Arcgis Open Data · 2011-02-01 to 2011-02-28 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Traffic crashes in Vermont showed a significant upward trend when comparing February 2011 to the same month in 2010. Total collisions increased by 58.6%, rising from 818 to 1,297. Concurrently, the number of people injured rose by 12.6% from 167 to 188, and fatalities increased from 1 to 4.

When Crashes Happen

The temporal patterns of crashes shifted slightly year-over-year. In February 2011, the peak day for crashes was Tuesday with 242 incidents, a change from Wednesday (154 crashes) in the prior year. The busiest time of day also shifted, with the peak hour moving from 3 p.m. (75 crashes) in 2010 to 4 p.m. (118 crashes) in 2011. Both periods show a concentration of crashes during afternoon commute hours.

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

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

Crash Severity Breakdown

While the absolute number of fatal and injury crashes increased, the overall severity distribution shifted. In February 2011, there were 4 fatal crashes compared to 1 in the prior year, and the fatal crash rate rose from 0.12 to 0.31 per 100 crashes. However, the proportion of crashes resulting in any injury decreased, accounting for 14.5% of all collisions in 2011, down from 20.4% in 2010. Consequently, the share of non-injury crashes increased from 78.5% to 85.0% year-over-year.

Outcome by Severity (Crash Events)

Fatal4fatal crashes0.3%
300.0%prior 1
Injury188minor injury crashes14.5%
12.6%prior 167
No Injury1,103no injury crashes85%
71.8%prior 642

Source: Vermont Crash Data · Arcgis Open Data · 2011-02-01 to 2011-02-28 · Severity derived from reported fatal/injury indicators (no KABCO A/B/C codes)

Severity Distribution (Crash Events)

Source: Vermont Crash Data · Arcgis Open Data · 2011-02-01 to 2011-02-28 · Most severe injury per crash record

Road & Environmental Conditions

The environmental conditions associated with crashes showed a notable shift, particularly regarding road surfaces. In February 2011, crashes on snowy roads were the most common type, accounting for 35.0% of all incidents (454 crashes), an increase from a 29.6% share (242 crashes) in the prior year. Correspondingly, the proportion of crashes on dry roads decreased from 41.8% to 27.2%. The number of crashes on snowy roads increased by 87.6% year-over-year, while collisions on icy roads more than doubled, rising from 34 to 84.

Weather

Clear501 (42.8%)
76.4%prior 284
Freezing Precipitation333 (28.5%)
26.1%prior 264
Cloudy315 (26.9%)
57.5%prior 200
Wind13 (1.1%)
Rain8 (0.7%)
-57.9%prior 19

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

Lighting

Daylight998 (78.2%)
64.4%prior 607
Dark278 (21.8%)
36.3%prior 204

Source: Vermont Crash Data · Arcgis Open Data · 2011-02-01 to 2011-02-28 · Lighting condition field

Road Surface

Snow454 (38.2%)
87.6%prior 242
Dry353 (29.7%)
3.2%prior 342
Wet221 (18.6%)
79.7%prior 123
Ice84 (7.1%)
147.1%prior 34
Slush67 (5.6%)
131.0%prior 29
Other - Explain in Narrative7 (0.6%)
Water (standing / moving)1 (0.1%)
Sand, mud, dirt, oil, gravel1 (0.1%)

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

Data Coverage

  • Reporting period: 2011-02-01 through 2011-02-28 (28 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 1,297

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