Yearly Traffic Safety Analysis

2 CRASHES IN
ISLE LAMOTTE, VT
2014

All metrics benchmarked against2013

Total crashes in Isle Lamotte remained stable at 2 for both 2014 and the prior year, 2013, representing a 0% change. Fatalities and injuries also saw no change, remaining at 0 and 1 respectively. The most notable shift was a 100% decrease in motorcycle crashes, falling from 1 in 2013 to 0 in 2014.

2

Total Crash Events

0

Fatal Crashes

1

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

Trend Summary

Overall crash trends in Isle Lamotte remained stable year-over-year, with total crashes holding at 2 for both 2014 and 2013. This represents no change in the total number of incidents. Similarly, the number of fatalities and injuries remained unchanged across both periods.

When Crashes Happen

Temporal patterns showed some shifts, although total crash counts remained consistent. While the peak day for crashes remained Saturday with 1 incident in both years, the peak hour shifted from 10 p.m. in 2013 to 9 p.m. in 2014. Additionally, crashes in 2014 were distributed between April (1) and May (1), whereas all 2 crashes in 2013 occurred in May.

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

Crash Severity Breakdown

Crash severity distributions remained identical between 2014 and 2013. Both periods reported 0 fatalities and 1 injury, with injury crashes accounting for 50% of the total crashes in each year. There was no change in the proportion of fatal or injury-involved incidents.

Outcome by Severity (Crash Events)

Injury1minor injury crashes50%
→0.0%prior 1
No Injury1no injury crashes50%
→0.0%prior 1

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

Lighting conditions remained consistent across both years, with one crash occurring in dark conditions and one in daylight conditions in each period. Road surface data was only available for 2014, showing one crash on a dry surface and one on a wet surface, preventing a year-over-year comparison. Weather conditions data was not available for either period.

Lighting

Dark1 (50.0%)
Daylight1 (50.0%)

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

Road Surface

Dry1 (50.0%)
Wet1 (50.0%)

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: Isle Lamotte, VT
  • Total crash records analyzed: 2

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). "Isle Lamotte, 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/isle-lamotte/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

Isle Lamotte, VT Crash Report — 2014 | ThatCarHitMe.com