Monthly Traffic Safety Analysis

1,089 CRASHES IN
VERMONT, VT
JULY 2011

All metrics benchmarked againstJuly 2010

In July 2011, there were 1,089 total crashes, an increase of 9.7% from the 993 crashes recorded in July 2010. The number of fatalities rose from 3 to 4, and injuries increased from 225 to 256. One of the most significant changes was the number of bicycle-involved crashes, which increased by 71.4% from 14 in the prior year to 24 in the current period.

1,089

9.7%was 993

Total Crash Events

4

33.3%was 3

Fatal Crashes

256

13.8%was 225

Injury Crashes

4

33.3%was 3

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

Trend Summary

Comparing July 2011 to July 2010, the overall trend shows an increase in traffic collisions. Total crashes rose by 9.7%, from 993 to 1,089. This upward trend is also reflected in the number of persons injured, which increased by 13.8% from 225 to 256, and total fatalities, which increased from 3 to 4.

When Crashes Happen

The temporal patterns of crashes remained broadly consistent between July 2010 and July 2011, with Friday being the peak day for collisions in both periods (202 and 220 crashes, respectively). However, the peak hour for crashes shifted slightly from the 4 p.m. hour in 2010 (99 crashes) to the 5 p.m. hour in 2011 (111 crashes). Overall, late afternoon and evening commute times on weekdays continued to be the most frequent periods for collisions.

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

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

Crash Severity Breakdown

The severity of crashes saw a slight increase in July 2011 compared to the previous year. The number of fatal crashes rose from 3 to 4, with the corresponding proportion of total crashes increasing from 0.3% to 0.4%. Crashes resulting in an injury also increased in both count (from 225 to 256) and proportion (from 22.7% to 23.5%). The majority of collisions in both periods resulted in no injuries, accounting for 75.2% of crashes in July 2010 and 76.1% in July 2011.

Outcome by Severity (Crash Events)

Fatal4fatal crashes0.4%
33.3%prior 3
Injury256minor injury crashes23.5%
13.8%prior 225
No Injury829no injury crashes76.1%
11.0%prior 747

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

Road & Environmental Conditions

In both July 2010 and July 2011, the vast majority of crashes occurred in clear, dry, and daylight conditions. In July 2011, crashes during daylight hours accounted for 80.3% of the total (874 crashes), a slight increase from 78.9% (783 crashes) the previous year. The proportion of crashes on dry roads also increased from 83.7% to 85.6%. Correspondingly, the share of crashes occurring in adverse conditions like rain (down from 6.8% to 4.3%) and on wet roads (down from 9.2% to 7.4%) decreased year-over-year.

Weather

Clear812 (80.7%)
17.2%prior 693
Cloudy145 (14.4%)
-5.2%prior 153
Rain47 (4.7%)
-30.9%prior 68
Wind1 (0.1%)
Freezing Precipitation1 (0.1%)

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

Lighting

Daylight874 (80.9%)
11.6%prior 783
Dark206 (19.1%)
-0.5%prior 207

Source: Vermont Crash Data · Arcgis Open Data · 2011-07-01 to 2011-07-31 · Lighting condition field

Road Surface

Dry932 (90.9%)
12.2%prior 831
Wet81 (7.9%)
-11.0%prior 91
Sand, mud, dirt, oil, gravel10 (1.0%)
42.9%prior 7
Water (standing / moving)2 (0.2%)

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

Data Coverage

  • Reporting period: 2011-07-01 through 2011-07-31 (31 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 1,089

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