ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · HYDE PARK, VT · 2015
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/hyde-park/2015-annual-report
Yearly Traffic Safety Analysis
35 CRASHES IN
HYDE PARK, VT
2015
Total crashes remained stable at 35 in both 2015 and 2014. The most notable year-over-year shift was a 100% increase in DUI crashes, rising from 2 in 2014 to 4 in 2015. Additionally, total injuries increased by 22.2%, from 9 in 2014 to 11 in 2015.
35
Total Crash Events
0
Fatal Crashes
11
▲ 22.2%was 9
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.
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-12-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall crash numbers remained stable year-over-year, with 35 total crashes reported in both 2015 and 2014. However, total injuries increased by 22.2%, rising from 9 in 2014 to 11 in 2015. Fatalities remained at zero for both periods.
When Crashes Happen
The peak day for crashes shifted from Friday in 2014 to Tuesday in 2015, with both days recording 8 crashes. The peak crash hour also changed, moving from 3 PM in 2014 (4 crashes) to 10 PM in 2015 (4 crashes).
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-12-31 · Crash date field aggregated by weekday
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Fatalities and fatal crashes remained at zero in both 2015 and 2014. Injury crashes increased from 9 in 2014 to 11 in 2015, representing a rise from 25.7% to 31.4% of total crashes. Conversely, the proportion of crashes with no injuries decreased from 74.3% in 2014 to 68.6% in 2015.
Outcome by Severity (Crash Events)
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-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 · 2015-01-01 to 2015-12-31 · Most severe injury per crash record
Road & Environmental Conditions
Crashes occurring in clear weather conditions increased by 100%, from 11 in 2014 to 22 in 2015, while crashes in cloudy weather decreased by 66.7%, from 12 to 4. Crashes on dry road surfaces rose by 31.25% from 16 to 21, and crashes on icy roads decreased by 50% from 4 to 2. Crashes in daylight increased from 26 to 28, while those in dark conditions decreased from 9 to 7.
Weather
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-12-31 · Weather condition at time of crash
Lighting
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-12-31 · Lighting condition field
Road Surface
Source: Vermont Crash Data · Arcgis Open Data · 2015-01-01 to 2015-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: 2015-01-01 through 2015-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2015-01-01 through 2015-12-31 (365 days)
- Geographic scope: Hyde Park, VT
- Total crash records analyzed: 35
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). "Hyde Park, VT Crash Intelligence Report: 2015." Published July 5, 2026. Reporting period: 2015-01-01 to 2015-12-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/hyde-park/2015-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: 2015-01-01 – 2015-12-31
Generated: July 5, 2026 · All rights reserved