ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · VERMONT, VT · JULY 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/statewide/july-2010-report
Monthly Traffic Safety Analysis
993 CRASHES IN
VERMONT, VT
JULY 2010
In July 2010, Vermont recorded 993 motor vehicle crashes, resulting in 3 fatalities and 225 injuries. Analysis of crash types reveals that rear-end collisions were the most frequent, accounting for 283 incidents or 28.5% of the total. The majority of crashes, 75.2%, resulted in no injuries.
993
Total Crash Events
3
Fatal Crashes
225
Injury Crashes
3
Fatal Crash Events
Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 18 crashes with unreported severity are not shown in the severity breakdown.
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Aggregate counts from crash, person, and vehicle records
When Crashes Happen
Crash occurrences in July 2010 peaked on Fridays, which saw 202 incidents, while the single busiest hour for crashes was the 4 p.m. hour with 99 events. Crash volumes were highest during the afternoon, and a significant majority of incidents, 783 out of 993, occurred during daylight hours.
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Crash date field aggregated by weekday
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The vast majority of crashes, 747 out of 993 (75.2%), resulted in no injuries. Collisions involving injuries accounted for 22.7% of all incidents, totaling 225 crashes. There were 3 fatal crashes during this period, resulting in 3 total fatalities.
Outcome by Severity (Crash Events)
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-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-07-01 to 2010-07-31 · Most severe injury per crash record
Road & Environmental Conditions
Most crashes in July 2010 occurred in ideal driving conditions, with 83.7% of crashes (831) happening on dry roads and 69.8% (693) in clear weather. A total of 783 crashes, or 78.9% of all incidents, occurred during daylight hours. Crashes in adverse conditions included 68 incidents during rain and 91 on wet road surfaces.
Weather
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Weather condition at time of crash
Lighting
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Lighting condition field
Road Surface
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Road surface condition field
Deadliest Highway Corridors
Analysis of crashes on numbered state highways highlights a concentration on a few key routes. US-7 was the site of the most incidents with 112 crashes, followed by US-2 with 51 and US-5 with 46. Together, these three corridors accounted for 209 crashes, representing a significant portion of all incidents occurring on numbered state routes.
Deadliest Highway Corridors
Showing top 9 of 50 reported. 41 additional (164 total) not shown: US-4, VT-30, VT-11, VT-125, BURLINGTON (ALTERNATE US-7), VT-12, VT-108, VT-36, VT-7A, WEST RUTLAND-RUTLAND (BR US-4), VT-105, VT-2A, VT-116, VT-67A, VT-78, VT-22A, VT-131, I-189, VT-106, VT-114, VT-118, VT-73, VT-25, VT-289, VT-103, VT-117, US-302, VT-62, VT-17, VT-313, VT-346, VT-4A, VT-67, VT-102, FAS 0136 (VT-143 TH), VT-100C, MONTPELIER (BR US-2), VT-142, VT-133, VT-232, VT-242.
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Crash-level records
Road Class
The data indicates a near-even split of crashes between state-numbered highways (492 incidents) and other roadways. Of the crashes on other road types, town or local roads accounted for the largest portion with 324 incidents. An additional 150 crashes occurred on other public roadways or in parking lots.
Road Class
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Crash-level records
Junction / Location Type
The most common crash location was not at a junction, with 474 incidents occurring at mid-block locations. Intersections collectively accounted for 274 crashes, with four-way (125) and T-intersections (121) being the most frequent types. A notable number of incidents, 145, also occurred in parking lots.
Junction / Location Type
Showing top 9 of 14 reported. 5 additional (14 total) not shown: On Ramp, Railway grade crossing, Five-point or more, Shared-use path or trail, Crossover.
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Crash-level records
Vulnerable Users & Heavy Trucks
Among crashes involving specific non-standard road users, those involving heavy trucks were most frequent, with 44 incidents recorded. Collisions involving motorcycles followed with 39 incidents. Vulnerable road users were involved in a total of 22 crashes, comprising 14 bicycle and 8 pedestrian incidents.
Animal-Involved Crashes
Of the 33 crashes involving animals, the vast majority involved deer, which accounted for 24 incidents. Collisions with moose were recorded in 4 instances, with domestic animals also involved in 4 crashes. These animal-related collisions represent 3.3% of total crashes for the month.
Crashes by Town
Crash incidents were geographically concentrated in a few key municipalities, with the top five accounting for 36.9% of all crashes. Burlington recorded the highest number of crashes with 133, followed by South Burlington with 74, and Rutland City with 57. Colchester (53) and Brattleboro (49) also reported high crash volumes.
Crashes by Town
Showing top 9 of 50 reported. 41 additional (316 total) not shown: Middlebury, Springfield, Stowe, Milton, St. Albans City, Shelburne, Swanton, St. Johnsbury, Barre City, Montpelier, Brandon, Derby, Cambridge, Weathersfield, Norwich, Barre Town, Richmond, Woodstock, Rutland Town, Rockingham, Newport City, St. Albans Town, Berlin, Wilmington, Danville, Georgia, Ferrisburgh, Sheldon, Bradford, Windsor, Charlotte, Poultney, Sharon, East Montpelier, Ludlow, Guilford, Lyndon, Addison, New Haven, Chester, Moretown.
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-31 · Crash-level records
Manner of Collision
The most common type of collision was a rear-end crash, which accounted for 283 incidents, or 28.5% of the total. Single-vehicle crashes were the second most frequent type, with 225 incidents (22.7%). Other significant collision types included same-direction sideswipes (99 crashes) and broadside collisions at intersections (84 crashes).
Manner of Collision
"Other" combines 11 smaller categories (113 records): Rear-to-rear (30), Opp Direction Sideswipe (30), Left Turn and Thru, Broadside v<-- (26), Right Turn and Thru, Broadside ^<-- (7), Left Turn and Thru, Head On ^v-- (6), Left Turn and Thru, Same Direction Sideswipe/Angle Crash vv-- (5), Right Turn and Thru, Head On v^-- (3), Right Turn and Thru, Same Direction Sideswipe/Angle Crash ^^-- (2), Left and Right Turns, Simultaneous Turn Crash --vv-- (2), Left Turns, Same Direction, Rear End v--v-- (1), Right Turn and Thru, Angle Broadside -->^-- (1).
Source: Vermont Crash Data · Arcgis Open Data · 2010-07-01 to 2010-07-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-07-01 through 2010-07-31
- Report generated: July 5, 2026
Data Coverage
- Reporting period: 2010-07-01 through 2010-07-31 (31 days)
- Geographic scope: vermont, VT
- Total crash records analyzed: 993
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). "vermont, VT Crash Intelligence Report: July 2010." Published July 5, 2026. Reporting period: 2010-07-01 to 2010-07-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/statewide/july-2010-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-07-01 – 2010-07-31
Generated: July 5, 2026 · All rights reserved