Yearly Traffic Safety Analysis

144 CRASHES IN
MORRISTOWN, VT
2014

All metrics benchmarked against2013

Total crashes in Morristown decreased from 165 in 2013 to 144 in 2014, representing a reduction of 12.73%. Despite the overall decrease in crashes, total injuries increased by 52.38%, rising from 21 in 2013 to 32 in 2014.

144

-12.7%was 165

Total Crash Events

0

Fatal Crashes

32

52.4%was 21

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, total crashes in Morristown decreased year-over-year, falling from 165 crashes in 2013 to 144 crashes in 2014. This represents a reduction of 21 crashes, or a 12.73% decrease, in the total number of incidents.

When Crashes Happen

The peak day for crashes shifted from Friday, which had 30 incidents in 2013, to Wednesday, with 28 incidents in 2014. Similarly, the peak crash hour moved from 3 PM with 18 incidents in 2013 to 12 PM with 17 incidents in 2014.

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

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

Crash Severity Breakdown

Total fatalities remained at zero for both 2013 and 2014. However, total injuries increased by 52.38%, rising from 21 injured persons in 2013 to 32 injured persons in 2014. The proportion of crashes resulting in injury also increased, from 12.7% in 2013 to 22.2% in 2014.

Outcome by Severity (Crash Events)

Injury32minor injury crashes22.2%
52.4%prior 21
No Injury112no injury crashes77.8%
-22.2%prior 144

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

Crashes occurring in cloudy weather decreased from 58 in 2013 to 38 in 2014, while crashes in clear weather increased from 62 to 73. Crashes during dark lighting conditions decreased from 32 in 2013 to 24 in 2014. Crashes on wet road surfaces saw a significant reduction, dropping from 30 incidents in 2013 to 10 incidents in 2014.

Weather

Clear73 (53.3%)
17.7%prior 62
Cloudy38 (27.7%)
-34.5%prior 58
Freezing Precipitation23 (16.8%)
-20.7%prior 29
Rain3 (2.2%)
-62.5%prior 8

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

Lighting

Daylight120 (83.3%)
-9.8%prior 133
Dark24 (16.7%)
-25.0%prior 32

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

Road Surface

Dry95 (67.9%)
2.2%prior 93
Snow26 (18.6%)
4.0%prior 25
Wet10 (7.1%)
-66.7%prior 30
Ice7 (5.0%)
-22.2%prior 9
Slush2 (1.4%)

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

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). "Morristown, 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/morristown/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

Morristown, VT Crash Report — 2014 | ThatCarHitMe.com