Yearly Traffic Safety Analysis

25 CRASHES IN
FERRISBURGH, VT
2012

All metrics benchmarked against2011

In Ferrisburgh, total crashes decreased by 36% from 39 crashes in 2011 to 25 crashes in 2012. The most notable year-over-year shift was the complete elimination of traffic fatalities, dropping from 1 fatality in 2011 to 0 in 2012.

25

-35.9%was 39

Total Crash Events

0

-100.0%was 1

Fatal Crashes

10

-23.1%was 13

Injury Crashes

0

-100.0%was 1

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 · 2012-01-01 to 2012-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall, crash trends in Ferrisburgh showed a significant decline from 2011 to 2012. Total crashes decreased by 14 incidents, representing a 36% reduction. This decline was accompanied by a 100% reduction in fatalities, from 1 in 2011 to 0 in 2012, and a 23% decrease in total injuries, from 13 to 10.

When Crashes Happen

The peak day for crashes remained Friday, though the number of crashes on Fridays decreased from 9 in 2011 to 7 in 2012. The peak crash hour shifted from 4 PM in 2011 (4 crashes) to 5 PM in 2012 (5 crashes). Notably, crashes on Mondays decreased from 8 in 2011 to 1 in 2012, while crashes on Thursdays increased from 1 in 2011 to 3 in 2012.

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

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

Crash Severity Breakdown

Crash severity saw a significant positive shift, with fatal crashes decreasing from 1 in 2011 to 0 in 2012, eliminating the 2.6% fatal crash rate. The proportion of injury crashes increased from 33.3% (13 crashes) in 2011 to 40% (10 crashes) in 2012, despite a decrease in the absolute number of injury crashes. Conversely, the proportion of no-injury crashes decreased from 64.1% (25 crashes) in 2011 to 60% (15 crashes) in 2012.

Outcome by Severity (Crash Events)

Injury10minor injury crashes40%
-23.1%prior 13
No Injury15no injury crashes60%
-40.0%prior 25

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

Road & Environmental Conditions

The number of crashes under clear weather conditions decreased from 19 in 2011 to 16 in 2012, while crashes during cloudy conditions decreased from 10 to 4. Crashes occurring in daylight decreased from 25 in 2011 to 13 in 2012, shifting the proportion of daylight crashes from 64.1% to 52%. Crashes on dry road surfaces decreased from 27 to 21, and crashes on snowy roads decreased from 7 to 2.

Weather

Clear16 (66.7%)
-15.8%prior 19
Cloudy4 (16.7%)
-60.0%prior 10
Freezing Precipitation3 (12.5%)
-40.0%prior 5
Rain1 (4.2%)

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

Lighting

Daylight13 (52.0%)
-48.0%prior 25
Dark12 (48.0%)
-14.3%prior 14

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

Road Surface

Dry21 (84.0%)
-22.2%prior 27
Snow2 (8.0%)
-71.4%prior 7
Ice1 (4.0%)
Wet1 (4.0%)
-80.0%prior 5

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

Data Coverage

  • Reporting period: 2012-01-01 through 2012-12-31 (366 days)
  • Geographic scope: Ferrisburgh, VT
  • Total crash records analyzed: 25

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

Ferrisburgh, VT Crash Report — 2012 | ThatCarHitMe.com