Monthly Traffic Safety Analysis

825 CRASHES IN
VERMONT, VT
FEBRUARY 2018

All metrics benchmarked againstFebruary 2017

In February 2018, there were 825 total crashes, a 35.4% decrease from the 1,278 crashes recorded in February 2017. This year-over-year decline was also reflected in fatalities, which fell from 7 to 3, and total injuries, which decreased from 132 to 118. The most significant change was the overall reduction in crash volume across the state.

825

-35.4%was 1,278

Total Crash Events

3

-57.1%was 7

Fatal Crashes

118

-10.6%was 132

Injury Crashes

3

-57.1%was 7

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 · 2018-02-01 to 2018-02-28 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Crash data for February 2018 indicates a significant year-over-year decrease across key metrics compared to February 2017. Total crashes fell by 453 incidents, from 1,278 to 825. Similarly, the number of fatalities decreased from 7 to 3, and the total number of injuries declined from 132 to 118.

When Crashes Happen

Temporal patterns shifted between February 2017 and February 2018. The peak day for crashes moved from Wednesday (239 crashes) in the prior year to Friday (151 crashes) in the current year. The peak hour also shifted slightly later, from the 3 p.m. hour (99 crashes) in 2017 to the 4 p.m. hour (73 crashes) in 2018. Overall, the daily distribution of crashes was less concentrated in 2018 compared to the prior year, which saw significant peaks on Wednesday and Thursday.

Source: Vermont Crash Data · Arcgis Open Data · 2018-02-01 to 2018-02-28 · Crash date field aggregated by weekday

Source: Vermont Crash Data · Arcgis Open Data · 2018-02-01 to 2018-02-28 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

While the total number of fatal and injury-related incidents decreased year-over-year, the proportion of crashes resulting in an injury increased. In February 2018, 14.3% of crashes resulted in an injury, up from 10.3% in February 2017. Conversely, the fatal crash rate saw a decline, with fatal incidents accounting for 0.4% of all crashes in the current period, down from 0.5% in the prior year.

Outcome by Severity (Crash Events)

Fatal3fatal crashes0.4%
-57.1%prior 7
Injury118minor injury crashes14.3%
-10.6%prior 132
No Injury704no injury crashes85.3%
-13.5%prior 814

Source: Vermont Crash Data · Arcgis Open Data · 2018-02-01 to 2018-02-28 · Severity derived from reported fatal/injury indicators (no KABCO A/B/C codes)

Severity Distribution (Crash Events)

Source: Vermont Crash Data · Arcgis Open Data · 2018-02-01 to 2018-02-28 · Most severe injury per crash record

Road & Environmental Conditions

The distribution of crashes across different environmental conditions remained broadly consistent between February 2017 and February 2018, despite a large drop in overall crash volume. In the current period, 73.6% of crashes occurred in daylight, compared to 75.0% in the prior year. Crashes on non-dry road surfaces, such as snow, ice, or wet pavement, accounted for a slightly lower share of incidents, decreasing from 64.7% in 2017 to 62.2% in 2018.

Weather

Clear277 (42.7%)
-19.9%prior 346
Freezing Precipitation177 (27.3%)
-40.0%prior 295
Cloudy172 (26.5%)
-14.9%prior 202
Rain21 (3.2%)
162.5%prior 8
Wind2 (0.3%)

Source: Vermont Crash Data · Arcgis Open Data · 2018-02-01 to 2018-02-28 · Weather condition at time of crash

Lighting

Daylight607 (73.9%)
-36.7%prior 959
Dark214 (26.1%)
-30.3%prior 307

Source: Vermont Crash Data · Arcgis Open Data · 2018-02-01 to 2018-02-28 · Lighting condition field

Road Surface

Dry249 (37.8%)
-17.8%prior 303
Snow186 (28.3%)
-41.9%prior 320
Wet116 (17.6%)
-20.0%prior 145
Ice63 (9.6%)
46.5%prior 43
Slush32 (4.9%)
-11.1%prior 36
Other - Explain in Narrative8 (1.2%)
60.0%prior 5
Sand, mud, dirt, oil, gravel3 (0.5%)
-50.0%prior 6
Water (standing / moving)1 (0.2%)

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

Data Coverage

  • Reporting period: 2018-02-01 through 2018-02-28 (28 days)
  • Geographic scope: vermont, VT
  • Total crash records analyzed: 825

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). "vermont, VT Crash Intelligence Report: February 2018." Published July 5, 2026. Reporting period: 2018-02-01 to 2018-02-28. Data source: Vermont Crash Data, Arcgis Open Data. Available at: https://thatcarhitme.com/crash-data/vermont/statewide/february-2018-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

Vermont (Statewide) Crash Report — February 2018 | ThatCarHitMe.com