ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · STOWE, VT · 2010
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/stowe/2010-annual-report
Yearly Traffic Safety Analysis
192 CRASHES IN
STOWE, VT
2010
In Stowe, Vermont, during 2010, a total of 192 crashes were reported. Notably, there were no fatalities recorded for the period, and only 16 injuries occurred. The data indicates that 90.1% of crashes resulted in no injuries.
192
Total Crash Events
0
Fatal Crashes
16
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. 3 crashes with unreported severity are not shown in the severity breakdown.
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Aggregate counts from crash, person, and vehicle records
When Crashes Happen
Crashes most frequently occurred on Mondays, with 38 incidents reported, and the peak hour for crashes was 12 AM, with 21 incidents. A greater number of crashes happened during daylight hours, accounting for 119 incidents, compared to 55 incidents in the dark.
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash date field aggregated by weekday
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
Of the 192 reported crashes, 16 (8.3%) resulted in injuries, while 173 crashes (90.1%) involved no injuries. There were no fatal crashes recorded, and consequently, zero fatalities were reported for the period.
Outcome by Severity (Crash Events)
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-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 · 2010-01-01 to 2010-12-31 · Most severe injury per crash record
Road & Environmental Conditions
A majority of crashes occurred under clear weather conditions (78 incidents), on dry road surfaces (93 incidents), and during daylight hours (119 incidents). However, adverse conditions were also a factor, with 32 crashes occurring on snow, 22 on wet roads, and 55 crashes happening in the dark.
Weather
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Weather condition at time of crash
Lighting
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Lighting condition field
Road Surface
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Road surface condition field
Deadliest Highway Corridors
VT-100 was the most common corridor for crashes, with 46 incidents, accounting for 23.96% of all crashes. VT-108 followed with 30 crashes, representing 15.63% of the total.
Deadliest Highway Corridors
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Road Class
The most frequent road class for crashes was "Other Public Roadway / Parking," which accounted for 68 incidents. Town or Local Roads were associated with 46 crashes during the period.
Road Class
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Junction / Location Type
Crashes predominantly occurred "Not at a Junction" (73 incidents) or within a "Parking Lot" (65 incidents). Intersections, including T-intersections (19), Y-intersections (4), and four-way intersections (1), collectively accounted for 24 crashes, representing 12.5% of the total.
Junction / Location Type
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Animal-Involved Crashes
Deer were involved in 12 crashes, making them the dominant animal type in animal-strike incidents, while moose were involved in 2 crashes. Animal-strike crashes, particularly involving deer and moose, are a known hazard in rural Vermont, often peaking in autumn.
Manner of Collision
"Rear End" collisions were the most frequent manner of collision, accounting for 48 incidents or 25% of all crashes. "Single Vehicle Crash" was the second most common type, with 46 incidents, representing 24% of the total.
Manner of Collision
"Other" combines 4 smaller categories (10 records): Left Turn and Thru, Angle Broadside -->v-- (3), No Turns, Thru moves only, Broadside ^< (3), Left Turn and Thru, Broadside v<-- (2), Right Turn and Thru, Angle Broadside -->^-- (2).
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
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: 2010-01-01 through 2010-12-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2010-01-01 through 2010-12-31 (365 days)
- Geographic scope: Stowe, VT
- Total crash records analyzed: 192
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). "Stowe, VT Crash Intelligence Report: 2010." Published July 5, 2026. Reporting period: 2010-01-01 to 2010-12-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/stowe/2010-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: 2010-01-01 – 2010-12-31
Generated: July 5, 2026 · All rights reserved