ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · SPRINGFIELD, 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/springfield/2010-annual-report
Yearly Traffic Safety Analysis
208 CRASHES IN
SPRINGFIELD, VT
2010
In Springfield, VT, during 2010, a total of 208 crashes were recorded, resulting in 1 fatality and 41 injuries. A significant majority of these incidents occurred under clear weather (64.4%), dry road conditions (70.2%), and during daylight hours (77.4%). This suggests that most crashes did not occur under adverse environmental conditions.
208
Total Crash Events
1
Fatal Crashes
41
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. 4 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
Monday was the peak day for crashes, with 38 incidents recorded, while 4 p.m. was the peak hour, accounting for 20 crashes. The majority of crashes, 164 (78.8%), occurred during daytime hours (6 a.m. to 6 p.m.). Conversely, 44 crashes (21.2%) happened during nighttime hours (6 p.m. to 5 a.m.), indicating a higher incidence of crashes during the day.
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 208 total crashes, 162 (77.9%) resulted in no injuries, while 41 crashes (19.7%) involved injuries. One fatal crash was recorded, which resulted in one fatality. It is important to note that the number of fatalities represents persons killed, and a single fatal crash can involve multiple fatalities.
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 substantial portion of crashes occurred under favorable conditions, with 134 incidents (64.4%) in clear weather and 146 incidents (70.2%) on dry road surfaces. Daylight conditions were present in 161 crashes (77.4%). In contrast, 45 crashes occurred in dark conditions, and 66 crashes involved adverse weather such as cloudy, freezing precipitation, or rain.
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-11 was the corridor with the highest number of crashes, accounting for 52 incidents, which represents 25% of all crashes. I-91 followed with 25 crashes, making up 12% of the total. VT-106 was the third most frequent corridor, with 13 crashes (6.25%).
Deadliest Highway Corridors
Source: Vermont Crash Data · Arcgis Open Data · 2010-01-01 to 2010-12-31 · Crash-level records
Road Class
The most common road class for crashes was 'Town or Local Road,' which accounted for 57 incidents. 'Other Public Roadway / Parking' was the second most frequent category, with 53 crashes. Only 1 crash occurred on 'Private Property / Driveway' within this dataset.
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 road character for crashes was 'Not at a Junction,' with 99 incidents. 'Parking Lot' was the second most common location type, accounting for 49 crashes. Intersections, including T-intersections (20 crashes), four-way intersections (15 crashes), and Y-intersections (4 crashes), collectively accounted for 39 crashes, representing 18.8% of all incidents.
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 Truck' collisions were the most common, with 10 incidents. Motorcycle crashes accounted for 4 incidents. Pedestrian and bicycle crashes combined totaled 4 incidents, representing 22.2% of these specific collision types.
Manner of Collision
'Single Vehicle Crash' was the most common manner of collision, accounting for 64 incidents, or 30.8% of all crashes. 'Rear End' collisions were the second most frequent with 35 incidents, representing 16.8% of the total. 'No Turns, Thru moves only, Broadside' accounted for 26 incidents (12.5%).
Manner of Collision
"Other" combines 8 smaller categories (19 records): Head On (6), Left Turn and Thru, Angle Broadside -->v-- (4), Left Turn and Thru, Broadside v<-- (3), Left Turn and Thru, Same Direction Sideswipe/Angle Crash vv-- (2), Right Turn and Thru, Broadside ^<-- (1), Left Turns, Opposite Directions, Head On/Angle Crash --^v-- (1), Right Turn and Thru, Head On v^-- (1), 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: Springfield, VT
- Total crash records analyzed: 208
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). "Springfield, 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/springfield/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