Yearly Traffic Safety Analysis

45 CRASHES IN
KILLINGTON, VT
2025

All metrics benchmarked against2024

In 2025, Killington experienced 45 crashes, a decrease from the 47 crashes recorded in 2024, representing a 4.26% reduction. The most significant year-over-year change was a substantial 62.5% decrease in total injuries, falling from 16 in 2024 to 6 in 2025.

45

-4.3%was 47

Total Crash Events

0

Fatal Crashes

6

-62.5%was 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.

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall, crash data for Killington indicates a downward trend in total crashes, decreasing by 4.26% from 47 in 2024 to 45 in 2025. This period also saw a notable reduction in total injuries, dropping by 62.5% from 16 to 6.

When Crashes Happen

The peak day for crashes shifted from Thursday in 2024, which had 11 crashes, to Tuesday in 2025, with 9 crashes. The peak crash hour also moved, occurring at 4 PM with 7 crashes in 2024 and at 5 PM with 7 crashes in 2025.

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-12-31 · Crash date field aggregated by weekday

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-12-31 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

While both years reported no fatalities, there was a significant change in injury severity. The number of crashes resulting in injuries decreased from 16 in 2024 to 6 in 2025. This led to a substantial reduction in the proportion of injury crashes, which fell from 34% of all crashes in 2024 to 13.3% in 2025.

Outcome by Severity (Crash Events)

Injury6minor injury crashes13.3%
-62.5%prior 16
No Injury39no injury crashes86.7%
25.8%prior 31

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-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 · 2025-01-01 to 2025-12-31 · Most severe injury per crash record

Road & Environmental Conditions

Crash incidents under clear weather conditions decreased from 24 in 2024 to 20 in 2025, while crashes during rainy conditions increased from 1 to 4. Regarding road surface, dry road crashes remained stable at 21 for both years, and crashes on wet surfaces decreased from 7 in 2024 to 5 in 2025.

Weather

Clear20 (46.5%)
-16.7%prior 24
Freezing Precipitation14 (32.6%)
-6.7%prior 15
Cloudy5 (11.6%)
Rain4 (9.3%)

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-12-31 · Weather condition at time of crash

Lighting

Daylight37 (84.1%)
-5.1%prior 39
Dark7 (15.9%)
-12.5%prior 8

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-12-31 · Lighting condition field

Road Surface

Dry21 (51.2%)
0.0%prior 21
Snow12 (29.3%)
-7.7%prior 13
Wet5 (12.2%)
-28.6%prior 7
Slush2 (4.9%)
Ice1 (2.4%)

Source: Vermont Crash Data · Arcgis Open Data · 2025-01-01 to 2025-12-31 · Road surface condition field

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: 2025-01-01 through 2025-12-31
  • Report generated: July 5, 2026

Data Coverage

  • Reporting period: 2025-01-01 through 2025-12-31 (365 days)
  • Geographic scope: Killington, VT
  • Total crash records analyzed: 45

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). "Killington, VT Crash Intelligence Report: 2025." Published July 5, 2026. Reporting period: 2025-01-01 to 2025-12-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/killington/2025-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

Killington, VT Crash Report — 2025 | ThatCarHitMe.com