ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · ENOSBURG, 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/enosburg/2010-annual-report
Yearly Traffic Safety Analysis
31 CRASHES IN
ENOSBURG, VT
2010
Enosburg experienced 31 crashes in 2010, resulting in 0 fatalities and 11 injuries. A notable finding is that 35.5% of these crashes resulted in injuries, while 64.5% involved no injuries. There were no fatal crashes reported during this period.
31
Total Crash Events
0
Fatal Crashes
11
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 · 2010-01-01 to 2010-12-31 · Aggregate counts from crash, person, and vehicle records
When Crashes Happen
In Enosburg during 2010, Saturday was the peak day for crashes, with 7 incidents reported. The peak hour for crashes was 3 PM, accounting for 6 incidents. The majority of crashes, 23 out of 31, occurred during daylight hours, while 8 crashes happened 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 31 crashes in Enosburg in 2010, 11 crashes (35.5%) resulted in injuries, while 20 crashes (64.5%) involved no injuries. There were no fatal crashes reported, and consequently, 0 fatalities occurred during this 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
The majority of crashes in Enosburg during 2010 occurred under favorable conditions, with 21 crashes (67.7%) happening in clear weather, 19 crashes (61.3%) on dry roads, and 23 crashes (74.2%) during daylight. Conversely, 7 crashes occurred in adverse weather conditions such as cloudy, freezing precipitation, or rain, and 10 crashes happened on non-dry road surfaces like snow, wet, or slush.
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
State Route VT-105 was the corridor with the highest number of crashes, accounting for 14 incidents. VT-108 followed with 3 crashes. Together, these two corridors represent 17 of the 31 total crashes recorded in Enosburg during 2010.
Deadliest Highway Corridors
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Road Class
In Enosburg, the highest number of crashes, 11 incidents, occurred on Town or Local Roads. State highways, including VT-105 and VT-108, accounted for 17 crashes. Additionally, 3 crashes took place on Other Public Roadway / Parking areas.
Road Class
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Junction / Location Type
The most frequent location for crashes in Enosburg was Not at a Junction, with 17 incidents. Intersections, including T-Intersections (7 crashes) and Four-way Intersections (1 crash), collectively accounted for 8 crashes. Additionally, 3 crashes occurred in Parking Lots and 2 in Driveways.
Junction / Location Type
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Manner of Collision
The most prevalent manner of collision in Enosburg during 2010 was Single Vehicle Crashes, which accounted for 12 incidents or 38.7% of all crashes. Rear-end collisions were the second most frequent type, with 7 incidents (22.6%).
Manner of Collision
"Other" combines 1 smaller categories (1 records): Head On (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: Enosburg, VT
- Total crash records analyzed: 31
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). "Enosburg, 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/enosburg/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