Monthly Traffic Safety Analysis

853 CRASHES IN
VERMONT, VT
MARCH 2016

All metrics benchmarked againstMarch 2015

In March 2016, Vermont recorded 853 total traffic crashes, a 22.6% decrease from the 1,102 crashes documented in March 2015. Despite the overall reduction in collisions, the most significant year-over-year change was the increase in fatalities, which rose from zero in the prior period to six in the current period.

853

-22.6%was 1,102

Total Crash Events

6

Fatal Crashes

166

15.3%was 144

Injury Crashes

6

Fatal Crash Events

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

Source: Vermont Crash Data · Arcgis Open Data · 2016-03-01 to 2016-03-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall crash incidents in Vermont showed a downward trend, decreasing by 249 from 1,102 in March 2015 to 853 in March 2016. However, the number of people injured increased by 15.3%, rising from 144 to 166, despite the lower total crash volume.

When Crashes Happen

The temporal patterns of crashes shifted between the two periods. In March 2016, the peak day for crashes was Wednesday with 165 incidents, a change from the prior year's peak on Sunday, which saw 186 crashes. The peak hour also moved from 3 p.m. in 2015 (99 crashes) to 12 p.m. in 2016 (75 crashes).

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

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

Crash Severity Breakdown

Crash severity increased in March 2016 compared to the previous year. The number of fatal crashes rose from zero to six, accounting for 0.7% of all incidents. The proportion of crashes resulting in an injury also grew, increasing from 13.1% (144 of 1,102 crashes) in March 2015 to 19.5% (166 of 853 crashes) in March 2016.

Outcome by Severity (Crash Events)

Fatal6fatal crashes0.7%
Injury166minor injury crashes19.5%
15.3%prior 144
No Injury567no injury crashes66.5%
-17.7%prior 689

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

Road & Environmental Conditions

Compared to the prior year, a larger proportion of crashes in March 2016 occurred during favorable conditions. The share of crashes happening in daylight increased from 66.6% to 76.3% of the total. Similarly, incidents on dry roads rose from 39.9% to 54.6% of the total, while crashes in clear weather increased from 36.6% to 47.5% of all events.

Weather

Clear405 (61.0%)
0.5%prior 403
Cloudy132 (19.9%)
-22.8%prior 171
Freezing Precipitation75 (11.3%)
-34.2%prior 114
Rain51 (7.7%)
131.8%prior 22
Wind1 (0.2%)
-87.5%prior 8

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

Lighting

Daylight651 (77.0%)
-11.3%prior 734
Dark194 (23.0%)
-44.9%prior 352

Source: Vermont Crash Data · Arcgis Open Data · 2016-03-01 to 2016-03-31 · Lighting condition field

Road Surface

Dry466 (69.6%)
5.9%prior 440
Wet91 (13.6%)
-12.5%prior 104
Ice48 (7.2%)
-20.0%prior 60
Snow36 (5.4%)
-63.6%prior 99
Slush15 (2.2%)
200.0%prior 5
Sand, mud, dirt, oil, gravel10 (1.5%)
100.0%prior 5
Other - Explain in Narrative3 (0.4%)
-40.0%prior 5
Water (standing / moving)1 (0.1%)

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

Data Coverage

  • Reporting period: 2016-03-01 through 2016-03-31 (31 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 853

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