Yearly Traffic Safety Analysis

22 CRASHES IN
IRASBURG, VT
2013

All metrics benchmarked against2012

Total crashes in Irasburg increased by 46.67%, rising from 15 in 2012 to 22 in 2013. The most notable year-over-year shift was the tripling of crashes occurring under freezing precipitation conditions, from 2 incidents in 2012 to 6 in 2013.

22

46.7%was 15

Total Crash Events

1

Fatal Crashes

5

-16.7%was 6

Injury Crashes

1

Fatal Crash Events

Note: "Fatal Crashes" and "Injury Crashes" count crash events — this source publishes crash-level counts only, not individual persons. 10 crashes with unreported severity are not shown in the severity breakdown.

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

Trend Summary

The overall trend for crashes in Irasburg shows a significant increase year-over-year, with total crashes rising by 46.67% from 15 in 2012 to 22 in 2013. While total fatalities remained stable at 1 in both periods, total injuries decreased by 16.67%, from 6 in 2012 to 5 in 2013.

When Crashes Happen

The temporal patterns of crashes shifted between the two periods. In 2013, the peak day for crashes was Saturday with 7 incidents, a change from Friday which was the peak day in 2012 with 5 incidents. The peak crash hour also shifted, moving from 3 p.m. in 2012 (4 crashes) to 5 p.m. in 2013 (4 crashes).

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

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

Crash Severity Breakdown

The number of fatal crashes remained constant at 1 in both 2012 and 2013, though the fatal crash rate decreased from 6.7% to 4.5% of reported crashes. Injury crashes saw a decrease in proportion, accounting for 22.7% of crashes in 2013 compared to 40% in 2012, with the count decreasing from 6 to 5. Conversely, crashes with no reported injuries also saw a proportional decrease, from 53.3% in 2012 to 27.3% in 2013.

Outcome by Severity (Crash Events)

Fatal1fatal crashes4.5%
0.0%prior 1
Injury5minor injury crashes22.7%
-16.7%prior 6
No Injury6no injury crashes27.3%
-25.0%prior 8

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

Road & Environmental Conditions

There were notable shifts in crash conditions year-over-year. Crashes occurring in freezing precipitation conditions increased from 2 in 2012 to 6 in 2013, while crashes under clear weather decreased from 9 to 3. Regarding road surface, crashes on dry roads decreased significantly from 10 in 2012 to 2 in 2013, whereas crashes on snow-covered roads increased from 3 to 5, and on wet roads from 1 to 4.

Weather

Freezing Precipitation6 (50.0%)
Clear3 (25.0%)
-66.7%prior 9
Cloudy3 (25.0%)

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

Lighting

Daylight13 (59.1%)
30.0%prior 10
Dark9 (40.9%)
80.0%prior 5

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

Road Surface

Snow5 (38.5%)
Wet4 (30.8%)
Dry2 (15.4%)
-80.0%prior 10
Ice1 (7.7%)
Other - Explain in Narrative1 (7.7%)

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

Data Coverage

  • Reporting period: 2013-01-01 through 2013-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: 2013." Published July 5, 2026. Reporting period: 2013-01-01 to 2013-12-31. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/irasburg/2013-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 — 2013 | ThatCarHitMe.com