ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · VERMONT, VT · SEPTEMBER 2016
Purpose: Machine-readable JSON endpoint for AI agents, LLMs, researchers, and programmatic consumers. Returns all underlying crash data and AI-generated commentary without HTML.
Authentication: None required. Public endpoint.
GET: https://thatcarhitme.com/api/crash-data/reports/data/vermont/statewide/september-2016-report
Monthly Traffic Safety Analysis
827 CRASHES IN
VERMONT, VT
SEPTEMBER 2016
In September 2016, Vermont recorded 827 total traffic crashes, a 19.6% decrease from the 1,029 crashes reported in September 2015. This downward trend was accompanied by a reduction in total injuries from 203 to 173 and a slight decrease in total fatalities from 7 to 6. A notable aspect of this year-over-year change was the significant drop in crashes involving vulnerable road users, with pedestrian-involved crashes falling from 15 to 8 and bicycle-involved crashes decreasing from 19 to 12.
827
▼ -19.6%was 1,029
Total Crash Events
6
▼ -14.3%was 7
Fatal Crashes
173
▼ -14.8%was 203
Injury Crashes
6
▼ -14.3%was 7
Fatal Crash Events
Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 53 crashes with unreported severity are not shown in the severity breakdown.
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-09-30 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Crash data for September shows a significant year-over-year decrease in traffic incidents across Vermont. Total crashes fell by 19.6%, from 1,029 in September 2015 to 827 in September 2016. This trend included a 14.8% reduction in total injuries (from 203 to 173) and one fewer fatality compared to the same month in the prior year.
When Crashes Happen
The temporal pattern of crashes shifted year-over-year. In September 2016, the peak day for crashes was Friday with 166 incidents, whereas in September 2015, the peak was Tuesday with 184 incidents. Similarly, the peak hour for collisions moved from 3 p.m. in the prior year (97 crashes) to 5 p.m. in the current year (80 crashes), suggesting a change in daily traffic patterns.
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-09-30 · Crash date field aggregated by weekday
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-09-30 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
While the absolute number of fatal crashes decreased from 7 to 6 year-over-year, the fatal crash rate saw a slight increase from 0.68% to 0.73% due to the larger overall drop in total crashes. The proportion of crashes resulting in an injury also increased slightly, moving from 19.7% of all crashes in September 2015 to 20.9% in September 2016. Despite these proportional increases, the total number of people injured and killed saw a net decrease.
Outcome by Severity (Crash Events)
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-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 · 2016-09-01 to 2016-09-30 · Most severe injury per crash record
Road & Environmental Conditions
A larger share of crashes occurred in clear weather and on dry roads in September 2016 compared to the previous year. Crashes on dry roads accounted for 79.3% of the total, up from 69.5% in 2015, while crashes on wet roads decreased from 7.9% to 4.6% of the total. Similarly, the proportion of crashes occurring in rainy weather fell by more than half, from 7.1% in 2015 to 3.1% in 2016. Lighting conditions remained stable, with daylight crashes making up approximately 80% of the total in both periods.
Weather
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-09-30 · Weather condition at time of crash
Lighting
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-09-30 · Lighting condition field
Road Surface
Source: Vermont Crash Data · Arcgis Open Data · 2016-09-01 to 2016-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: 2016-09-01 through 2016-09-30
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2016-09-01 through 2016-09-30 (30 days)
- Geographic scope: vermont, VT
- Total crash records analyzed: 827
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 2016." Published July 5, 2026. Reporting period: 2016-09-01 to 2016-09-30. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/statewide/september-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
ThatCarHitMe.com
An Injuria.ai Company
Crash Data Intelligence
Data: Vermont Crash Data · Arcgis
Period: 2016-09-01 – 2016-09-30
Generated: July 5, 2026 · All rights reserved