ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · MIDDLETOWN SPRINGS, VT · 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/middletown-springs/2016-annual-report
Yearly Traffic Safety Analysis
5 CRASHES IN
MIDDLETOWN SPRINGS, VT
2016
Total crashes in Middletown Springs decreased significantly from 14 in 2015 to 5 in 2016, representing a 64.28% reduction year-over-year. The most notable shift was the substantial decrease in overall crash incidents. Despite the overall reduction, the number of crashes involving injuries remained stable at 2 in both years.
5
▼ -64.3%was 14
Total Crash Events
0
Fatal Crashes
2
Injury Crashes
0
Fatal Crash Events
Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 2 crashes with unreported severity are not shown in the severity breakdown.
Source: Vermont Crash Data · Arcgis Open Data · 2016-01-01 to 2016-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall crash incidents in Middletown Springs showed a significant downward trend year-over-year, decreasing from 14 crashes in 2015 to 5 crashes in 2016. This represents a 64.28% reduction in total crashes. The data indicates a substantial improvement in crash frequency during the period.
When Crashes Happen
The peak day for crashes remained Monday in both 2015 and 2016, with 4 crashes reported on this day in each year. However, the peak crash hour shifted from 4a in 2015 (with 2 crashes) to 10a in 2016 (also with 2 crashes). This indicates a change in the specific time of day when crashes were most frequent, moving from early morning to late morning.
Source: Vermont Crash Data · Arcgis Open Data · 2016-01-01 to 2016-12-31 · Crash date field aggregated by weekday
Source: Vermont Crash Data · Arcgis Open Data · 2016-01-01 to 2016-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Total fatalities remained at 0 in both 2015 and 2016. The number of injury crashes also remained constant at 2 in both periods. However, due to a decrease in overall crashes, the proportion of injury crashes increased from 14.3% of total crashes in 2015 to 40% in 2016.
Outcome by Severity (Crash Events)
Source: Vermont Crash Data · Arcgis Open Data · 2016-01-01 to 2016-12-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-01-01 to 2016-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Crashes occurring in 'Clear' weather conditions decreased from 4 in 2015 to 2 in 2016, while crashes in 'Freezing Precipitation' remained at 1 for both years. On road surfaces, crashes on 'Dry' roads decreased from 6 in 2015 to 2 in 2016, and crashes on 'Snow' roads decreased from 2 to 1. Data for lighting conditions was only available for 2015, showing 8 crashes in 'Daylight' and 6 in 'Dark' conditions, preventing a year-over-year comparison for this factor.
Weather
Source: Vermont Crash Data · Arcgis Open Data · 2016-01-01 to 2016-12-31 · Weather condition at time of crash
Road Surface
Source: Vermont Crash Data · Arcgis Open Data · 2016-01-01 to 2016-12-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-01-01 through 2016-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2016-01-01 through 2016-12-31 (366 days)
- Geographic scope: Middletown Springs, VT
- Total crash records analyzed: 5
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). "Middletown Springs, VT Crash Intelligence Report: 2016." Published July 5, 2026. Reporting period: 2016-01-01 to 2016-12-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/middletown-springs/2016-annual-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-01-01 – 2016-12-31
Generated: July 5, 2026 · All rights reserved