ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · SHELBURNE, 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/shelburne/2010-annual-report
Yearly Traffic Safety Analysis
113 CRASHES IN
SHELBURNE, VT
2010
In Shelburne, Vermont, during 2010, there were 113 total crashes, resulting in 1 fatality and 19 injuries. The most frequent collision type was rear-end crashes, accounting for 47.8% of all incidents. This data provides a snapshot of traffic safety trends within the city for the specified period.
113
Total Crash Events
1
Fatal Crashes
19
Injury Crashes
1
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 · 2010-01-01 to 2010-12-31 · Aggregate counts from crash, person, and vehicle records
When Crashes Happen
Crash incidents in Shelburne, Vermont, peaked on Wednesdays with 22 crashes and during the 3 PM hour with 14 crashes. Analysis of lighting conditions indicates that 91 crashes occurred during daylight, while 19 crashes occurred in dark conditions. This highlights a predominant occurrence of crashes during daytime hours and specific weekday and afternoon peaks.
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
Out of 113 crashes, 82.3% (93 crashes) resulted in no injuries, while 16.8% (19 crashes) involved injuries. There was 1 fatal crash, accounting for 0.9% of all incidents. The total number of fatalities was 1, which aligns with the single fatal crash event.
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
The majority of crashes occurred under clear weather conditions (60 crashes), on dry road surfaces (83 crashes), and during daylight hours (91 crashes). However, adverse conditions also contributed to incidents, with 12 crashes occurring in rain, 7 in freezing precipitation, and 17 on wet road surfaces. These figures indicate that while most crashes happen in optimal conditions, a notable portion occurs when conditions are less favorable.
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
The primary corridors for crashes in Shelburne were US-7, with 80 crashes, and VT-116, with 4 crashes. These two state highways collectively accounted for 84 crashes, representing 74.3% of all crashes recorded. This concentration suggests that US-7 is a significant focus area for traffic safety interventions.
Deadliest Highway Corridors
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Road Class
The majority of crashes, totaling 84, occurred on state highways (US-7 and VT-116). Town or Local Roads accounted for 16 crashes, and Other Public Roadway / Parking areas for 13 crashes. State highways represent the most frequent location type for crashes in the area.
Road Class
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Junction / Location Type
Crashes most frequently occurred at locations not at a junction, accounting for 54 incidents. Intersections, specifically four-way and T-intersections, collectively contributed to 39 crashes. This indicates that both mid-block segments and intersections are significant sites for crash occurrences.
Junction / Location Type
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Vulnerable Users & Heavy Trucks
Among crashes involving non-standard road users, heavy trucks were most frequently involved with 8 incidents. Motorcycles were involved in 2 crashes, and bicycles in 1 crash. The combined share of pedestrian and bicycle crashes was 1, representing a small portion of total incidents.
Manner of Collision
Rear-end collisions were the most common manner of collision, accounting for 54 crashes, or 47.8% of all incidents. Other significant collision types included broadside crashes at intersections with 18 incidents, and single vehicle crashes with 12 incidents. This pattern highlights the prevalence of rear-end incidents in the crash profile.
Manner of Collision
"Other" combines 2 smaller categories (3 records): Left Turn and Thru, Angle Broadside -->v-- (2), Right Turn and Thru, Same Direction Sideswipe/Angle Crash ^^-- (1).
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: Shelburne, VT
- Total crash records analyzed: 113
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). "Shelburne, 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/shelburne/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