Yearly Traffic Safety Analysis

110 CRASHES IN
WATERBURY, VT
2014

All metrics benchmarked against2013

In 2014, Waterbury recorded 110 total traffic crashes, a 6.8% increase from the 103 crashes reported in 2013. While total injuries remained stable at 19 compared to 18 the previous year, the temporal patterns of collisions shifted significantly. The most active time for crashes moved from the afternoon commute in 2013, which peaked at 4 p.m., to the morning commute in 2014, with a new peak at 7 a.m.

110

▲ 6.8%was 103

Total Crash Events

0

Fatal Crashes

19

▲ 5.6%was 18

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. 55 crashes with unreported severity are not shown in the severity breakdown.

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

Trend Summary

Overall, traffic collisions in Waterbury saw a slight increase year-over-year. Total crashes rose by 6.8%, from 103 in 2013 to 110 in 2014. Despite the rise in total incidents, the number of resulting injuries remained nearly unchanged, with 19 in 2014 compared to 18 in the prior year, and no fatalities were recorded in either period.

When Crashes Happen

The timing of crashes shifted notably between the two years. In 2014, the peak time for collisions moved to the morning, with 7 a.m. recording the highest number of incidents (11). This contrasts with 2013, when the afternoon commute was the most hazardous period, peaking at 4 p.m. with 13 crashes. While Friday remained the most common day for crashes in both years (29 in 2014 vs. 24 in 2013), Thursday replaced Tuesday as the second-highest day for incidents.

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

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

Crash Severity Breakdown

Crash severity remained relatively consistent year-over-year. No fatal crashes were recorded in either 2014 or 2013. The proportion of crashes resulting in an injury was also stable, accounting for 17.3% of all incidents in 2014 (19 injury crashes) compared to 17.5% in 2013 (18 injury crashes).

Outcome by Severity (Crash Events)

Injury19minor injury crashes17.3%
↑5.6%prior 18
No Injury36no injury crashes32.7%
↓-2.7%prior 37

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

Road & Environmental Conditions

The conditions under which crashes occurred saw a significant shift between periods. In 2014, there was a marked decrease in crashes on dry roads, which fell from 30 incidents in 2013 to 16. Conversely, crashes on adverse road surfaces increased, with incidents on snow rising from 10 to 14, on wet roads from 7 to 12, and on ice tripling from 3 to 9. While the majority of crashes in both years occurred during daylight, the proportion of incidents in the dark increased from 30.1% in 2013 to 35.5% in 2014.

Weather

Clear18 (33.3%)
↓-18.2%prior 22
Freezing Precipitation17 (31.5%)
↑21.4%prior 14
Cloudy15 (27.8%)
↑25.0%prior 12
Rain4 (7.4%)

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

Lighting

Daylight70 (64.2%)
↓-1.4%prior 71
Dark39 (35.8%)
↑25.8%prior 31

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

Road Surface

Dry16 (29.1%)
↓-46.7%prior 30
Snow14 (25.5%)
↑40.0%prior 10
Wet12 (21.8%)
↑71.4%prior 7
Ice9 (16.4%)
Slush2 (3.6%)
Other - Explain in Narrative1 (1.8%)
Water (standing / moving)1 (1.8%)

Source: Vermont Crash Data · Arcgis Open Data · 2014-01-01 to 2014-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: 2014-01-01 through 2014-12-31
  • Report generated: July 5, 2026

Data Coverage

  • Reporting period: 2014-01-01 through 2014-12-31 (365 days)
  • Geographic scope: Waterbury, VT
  • Total crash records analyzed: 110

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

Waterbury, VT Crash Report — 2014 | ThatCarHitMe.com