ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · VERMONT, VT · OCTOBER 2017
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/october-2017-report
Monthly Traffic Safety Analysis
910 CRASHES IN
VERMONT, VT
OCTOBER 2017
In October 2017, there were 910 total traffic crashes, a 10.0% decrease from the 1,011 crashes recorded in October 2016. Despite this overall reduction in collisions, the most significant year-over-year change was the doubling of fatalities, which increased from 3 to 6.
910
▼ -10.0%was 1,011
Total Crash Events
6
▲ 100.0%was 3
Fatal Crashes
147
▼ -25.4%was 197
Injury Crashes
6
▲ 100.0%was 3
Fatal Crash Events
Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 119 crashes with unreported severity are not shown in the severity breakdown.
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Year-over-year data indicates a downward trend in overall crash volume, with total collisions falling by 10.0% from 1,011 to 910. The number of injuries also saw a significant decline of 25.4%, from 197 to 147. However, this trend did not extend to the most severe outcomes, as fatalities doubled from 3 to 6 over the same period.
When Crashes Happen
The temporal patterns of crashes shifted between the two periods. The peak day for collisions moved from Friday in October 2016, which saw 205 crashes, to Tuesday in October 2017 with 161 crashes. Similarly, the peak hour for crashes shifted from 5 PM in the prior year (100 crashes) to 3 PM in the current year (74 crashes).
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-31 · Crash date field aggregated by weekday
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
While overall crashes decreased, the severity of outcomes worsened in certain respects. The number of fatal crashes doubled from 3 to 6, causing the fatality rate per crash to increase from 0.3% in October 2016 to 0.66% in October 2017. Conversely, the proportion of crashes resulting in non-fatal injuries decreased from 19.5% to 16.2%, while the share of collisions with no injuries rose from 65.6% to 70.1%.
Outcome by Severity (Crash Events)
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-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 · 2017-10-01 to 2017-10-31 · Most severe injury per crash record
Road & Environmental Conditions
Crashes were more concentrated in favorable conditions in October 2017 compared to the prior year. The proportion of collisions occurring in daylight increased from 66.9% to 73.6%, while crashes in the dark decreased from 322 to 231. Similarly, crashes on wet roads declined from 187 to 124, and collisions during rainy weather fell from 136 to 88.
Weather
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-31 · Weather condition at time of crash
Lighting
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-31 · Lighting condition field
Road Surface
Source: Vermont Crash Data · Arcgis Open Data · 2017-10-01 to 2017-10-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: 2017-10-01 through 2017-10-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2017-10-01 through 2017-10-31 (31 days)
- Geographic scope: vermont, VT
- Total crash records analyzed: 910
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: October 2017." Published July 5, 2026. Reporting period: 2017-10-01 to 2017-10-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/statewide/october-2017-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: 2017-10-01 – 2017-10-31
Generated: July 5, 2026 · All rights reserved