16 CRASHES IN
CHARLESTON, VT
2013

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: Charleston, VT
• Total crash records analyzed: 16

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). "Charleston, 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/charleston/2013-annual-report