Monthly Traffic Safety Analysis

975 CRASHES IN
VERMONT, VT
SEPTEMBER 2013

All metrics benchmarked againstSeptember 2012

In September 2013, Vermont recorded 975 total traffic crashes, an 8.9% increase from the 895 crashes reported in September 2012. While the number of fatalities remained unchanged at 8 for both periods, the total number of injuries rose from 188 to 198. The overall rise in collisions represents the most significant trend in this year-over-year comparison.

975

8.9%was 895

Total Crash Events

8

Fatal Crashes

198

5.3%was 188

Injury Crashes

8

Fatal Crash Events

Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 5 crashes with unreported severity are not shown in the severity breakdown.

Source: Vermont Crash Data · Arcgis Open Data · 2013-09-01 to 2013-09-30 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Crash data for September indicates a rising trend year-over-year, with total collisions increasing by 80 incidents, from 895 in September 2012 to 975 in September 2013. While the number of fatalities held steady at 8 in both periods, the number of people injured in crashes saw a 5.3% increase, rising from 188 to 198.

When Crashes Happen

The timing of crashes showed notable shifts between September 2012 and September 2013. The peak day for collisions moved from Friday (167 crashes) in the prior year to Thursday (154 crashes) in the current year. Similarly, the peak hour for crashes shifted two hours earlier, from 5 p.m. in 2012 (81 crashes) to 3 p.m. in 2013 (105 crashes), with the number of incidents during that single hour increasing by 29.6%.

Source: Vermont Crash Data · Arcgis Open Data · 2013-09-01 to 2013-09-30 · Crash date field aggregated by weekday

Source: Vermont Crash Data · Arcgis Open Data · 2013-09-01 to 2013-09-30 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

While the total number of crashes increased year-over-year, the severity distribution remained relatively stable. The number of fatal crashes was unchanged at 8 for both September 2012 and September 2013, leading to a slight decrease in the fatal crash rate from 0.89% to 0.82%. The proportion of crashes resulting in an injury also saw a small decline, from 21.0% in the prior year to 20.3% in the current year, even as the absolute number of injuries rose from 188 to 198.

Outcome by Severity (Crash Events)

Fatal8fatal crashes0.8%
0.0%prior 8
Injury198minor injury crashes20.3%
5.3%prior 188
No Injury764no injury crashes78.4%
9.3%prior 699

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

Severity Distribution (Crash Events)

Source: Vermont Crash Data · Arcgis Open Data · 2013-09-01 to 2013-09-30 · Most severe injury per crash record

Road & Environmental Conditions

Environmental conditions do not appear to be a primary driver of the year-over-year increase in crashes. In September 2013, a greater share of collisions occurred during daylight, rising to 81.8% from 77.8% in the prior year. Crashes on wet roads decreased as a proportion of the total, from 12.1% in September 2012 to 9.4% in September 2013. Similarly, the share of crashes occurring in rainy weather fell from 9.7% to 7.0%.

Weather

Clear621 (74.7%)
5.3%prior 590
Cloudy141 (17.0%)
11.0%prior 127
Rain68 (8.2%)
-21.8%prior 87
Freezing Precipitation1 (0.1%)

Source: Vermont Crash Data · Arcgis Open Data · 2013-09-01 to 2013-09-30 · Weather condition at time of crash

Lighting

Daylight798 (82.8%)
14.7%prior 696
Dark166 (17.2%)
-8.8%prior 182

Source: Vermont Crash Data · Arcgis Open Data · 2013-09-01 to 2013-09-30 · Lighting condition field

Road Surface

Dry756 (87.9%)
8.3%prior 698
Wet92 (10.7%)
-14.8%prior 108
Water (standing / moving)6 (0.7%)
-33.3%prior 9
Sand, mud, dirt, oil, gravel6 (0.7%)
-60.0%prior 15

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

Data Coverage

  • Reporting period: 2013-09-01 through 2013-09-30 (30 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 975

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