Yearly Traffic Safety Analysis

22 CRASHES IN
IRASBURG, VT
2011

All metrics benchmarked against2010

In 2011, there were 22 total crashes, marking a 120% increase from the 10 crashes reported in 2010. This period also saw a significant rise in total injuries, increasing from 1 in 2010 to 12 in 2011. The number of fatal crashes also doubled from 1 to 2 year-over-year.

22

120.0%was 10

Total Crash Events

2

100.0%was 1

Fatal Crashes

12

1100.0%was 1

Injury Crashes

2

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

Trend Summary

Overall, crash metrics showed an upward trend year-over-year. Total crashes increased by 120%, from 10 in 2010 to 22 in 2011, while total fatalities rose by 100% from 1 to 2. Total injuries experienced an even more substantial increase, from 1 in 2010 to 12 in 2011.

When Crashes Happen

The peak day for crashes shifted from Tuesday in 2010, with 3 crashes, to Saturday in 2011, with 6 crashes. However, the peak hour remained 10a in both years, each recording 3 crashes. Crashes in 2011 were distributed across 10 months, compared to 7 months in 2010.

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

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

Crash Severity Breakdown

Fatal crashes increased from 1 in 2010 to 2 in 2011, though the fatal crash rate slightly decreased from 10% to 9.09%. Injury crashes saw a substantial increase from 1 in 2010 to 12 in 2011, leading to a rise in their proportion from 10% to 54.5% of all crashes. Conversely, crashes with no injuries, while remaining at 8 incidents, decreased proportionally from 80% to 36.4%.

Outcome by Severity (Crash Events)

Fatal2fatal crashes9.1%
100.0%prior 1
Injury12minor injury crashes54.5%
1100.0%prior 1
No Injury8no injury crashes36.4%
0.0%prior 8

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

Road & Environmental Conditions

Crashes occurring in 'Clear' weather increased from 5 to 8, but their proportion of total crashes decreased from 50% to 36.4%. Conversely, crashes in 'Cloudy' and 'Freezing Precipitation' conditions increased in both count and proportion. While crashes in 'Daylight' and 'Dark' conditions both rose in number, their proportional shares remained relatively stable, with Daylight at 68.2% and Dark at 31.8% in 2011. Crashes on 'Dry' road surfaces increased from 6 to 14, with their proportion slightly rising from 60% to 63.6%.

Weather

Clear8 (36.4%)
60.0%prior 5
Cloudy7 (31.8%)
Freezing Precipitation5 (22.7%)
Wind2 (9.1%)

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

Lighting

Daylight15 (68.2%)
114.3%prior 7
Dark7 (31.8%)

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

Road Surface

Dry14 (63.6%)
133.3%prior 6
Snow3 (13.6%)
Wet3 (13.6%)
Ice1 (4.5%)
Other - Explain in Narrative1 (4.5%)

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

Data Coverage

  • Reporting period: 2011-01-01 through 2011-12-31 (365 days)
  • Geographic scope: Irasburg, VT
  • Total crash records analyzed: 22

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

Irasburg, VT Crash Report — 2011 | ThatCarHitMe.com