Monthly Traffic Safety Analysis

24 CRASHES IN
AMESBURY, MA
DECEMBER 2025

All metrics benchmarked againstDecember 2024

In December 2025, AMESBURY recorded 24 crashes, a 20% decrease compared to the 30 crashes reported in December 2024. Despite the reduction in total crashes, the number of injuries increased significantly from 1 in the prior period to 6 in the current period. This represents a 500% increase in total injuries year-over-year.

24

-20.0%was 30

Total Crash Events

0

Persons Killed

6

500.0%was 1

Persons Injured

1

Hit-and-Run Crashes

Note: "Persons Killed" (0) counts individual fatalities across all crash events. "Fatal" in the severity table below (0) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities.

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall, AMESBURY experienced a decrease in total crashes, falling from 30 in December 2024 to 24 in December 2025, representing a 20% reduction. However, total injuries saw a substantial increase, rising from 1 to 6 during the same period. Fatalities remained at zero for both December 2024 and December 2025.

1

Hit-and-Run Crashes — December 2025

4.2% hit-and-run rate this period vs 0.0% prior. Prior period: 0.

Vulnerable Road User Casualties

0

Motorists Killed

Prior: 00.0%

6

Motorists Injured

Prior: 1500.0%

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)

When Crashes Happen

The temporal distribution of crashes shifted year-over-year, with the peak day moving from Saturday with 6 crashes in December 2024 to Tuesday with 6 crashes in December 2025. The peak hour for crashes also changed, from 4 PM with 6 crashes in the prior period to 1 PM with 4 crashes in the current period. Notably, Sunday crashes decreased from 5 to 1, while crashes around 4 PM saw a significant reduction from 6 to 1.

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Crash date field aggregated by weekday

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

Fatalities remained at 0 in both December 2024 and December 2025. Total injuries increased from 1 to 6 year-over-year. Minor injuries (severity B) rose from 1 crash (3.3% of total crashes) in December 2024 to 5 crashes (20.8% of total crashes) in December 2025, and possible injuries (severity C) appeared with 1 crash (4.2% of total crashes) in the current period, having not been present in the prior period.

Outcome by Severity (Crash Events)

Minor Injury5minor injury crashes20.8%
400.0%prior 1
Possible Injury1possible injury crashes4.2%
No Injury18no injury crashes75%
-37.9%prior 29

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · KABCO injury classification scale

Severity Distribution (Crash Events)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Most severe injury per crash record

Top Contributing Factors

The most frequent contributing factor, 'No improper driving', decreased from 9 instances in December 2024 to 7 in December 2025, a 22.2% decrease in count. 'Distracted' driving emerged as a notable factor, accounting for 3 crashes in December 2025, compared to no reported instances in the prior period. Conversely, 'Failed to yield right of way' crashes decreased from 4 instances in December 2024 to 0 in December 2025.

Officer-Reported Primary Contributing Cause

No improper driving7 (29.2%)-22.2%prior 9
Distracted3 (12.5%)
Swerving or avoiding due to wind, slippery surface, vehicle, object, vulnerable user in roadway2 (8.3%)
Driving too fast for conditions2 (8.3%)
Made an improper turn1 (4.2%)
Operating vehicle in erratic, reckless, careless, negligent or aggressive manner1 (4.2%)
Other improper action1 (4.2%)
Over-correcting/over-steering1 (4.2%)
Failure to keep in proper lane or running off road1 (4.2%)
Disregarded traffic signs, signals, road markings1 (4.2%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Officer-reported primary contributory cause per crash

Road & Environmental Conditions

Crashes occurring on dry road surfaces decreased from 17 in December 2024 to 9 in December 2025, while crashes on wet surfaces increased from 3 to 6, and on ice from 2 to 3. The proportion of crashes under daylight conditions increased from 10 out of 30 crashes (33.3%) in December 2024 to 15 out of 24 crashes (62.5%) in December 2025. Conversely, crashes in dark conditions decreased from 19 to 9.

Weather

Clear9 (37.5%)
-40.0%prior 15
Snow4 (16.7%)
Cloudy3 (12.5%)
Rain2 (8.3%)
Sleet, hail (freezing rain or drizzle)/Rain2 (8.3%)
Snow/Sleet, hail (freezing rain or drizzle)1 (4.2%)
Sleet, hail (freezing rain or drizzle)/Snow1 (4.2%)
Cloudy/Rain1 (4.2%)
Cloudy/Snow1 (4.2%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Weather condition at time of crash

Lighting

Daylight15 (62.5%)
50.0%prior 10
Dark - lighted roadway8 (33.3%)
-42.9%prior 14
Dark - roadway not lighted1 (4.2%)
-80.0%prior 5

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Lighting condition field

Road Surface

Dry9 (37.5%)
-47.1%prior 17
Snow6 (25.0%)
-25.0%prior 8
Wet6 (25.0%)
Ice3 (12.5%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Road surface condition field

Vehicles & Demographics

Top Vehicle Makes (43 vehicles)

1
HONDA6 (14%)
0.0%prior 6
2
TOYOTA6 (14%)
-14.3%prior 7
3
NISSAN5 (11.6%)
4
HYUNDAI3 (7%)
5
FORD3 (7%)
-40.0%prior 5
6
JEEP2 (4.7%)
7
CADI2 (4.7%)
8
LEXUS2 (4.7%)
9
GMC2 (4.7%)
10
CHEVROLET2 (4.7%)
-66.7%prior 6

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Vehicle unit records

8 persons with unknown or unrecorded age excluded from age chart.

Sex Distribution (47 persons with recorded sex)

Male28 (59.6%)
-6.7%prior 30
Female19 (40.4%)
-26.9%prior 26

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Person-level records linked to crash events

Speed Limit Zones

Crashes in the 25 mph speed zone decreased from 16 in December 2024 to 14 in December 2025, a 12.5% decrease in count. In contrast, crashes in the 40 mph zone increased from 2 to 4, a 100% increase in count, and those in the 65 mph zone increased from 4 to 6, a 50% increase in count. There were no fatal crashes reported in any speed zone during either period.

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-12-01 to 2025-12-31 · Posted speed limit at crash location

Data Sources & Methodology

Primary Data Source

All crash data in this report is sourced from Massachusetts Crash Data (MassDOT CDV), accessed programmatically via the Arcgis_yearly 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_yearly 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: 2025-12-01 through 2025-12-31
  • Report generated: June 21, 2026

Data Coverage

  • Reporting period: 2025-12-01 through 2025-12-31 (31 days)
  • Geographic scope: AMESBURY, MA
  • Total crash records analyzed: 24
  • Total persons involved: 54
  • Total vehicles involved: 43

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). "AMESBURY, MA Crash Intelligence Report: December 2025." Published June 21, 2026. Reporting period: 2025-12-01 to 2025-12-31. Data source: Massachusetts Crash Data (MassDOT CDV), Arcgis_yearly Open Data. Available at: https://thatcarhitme.com/crash-data/massachusetts/amesbury/december-2025-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

Amesbury, MA Crash Report — December 2025 | ThatCarHitMe.com