ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · HAVERHILL, MA · FEBRUARY 2026
Purpose: Machine-readable JSON endpoint for AI agents, LLMs, researchers, and programmatic consumers. Returns all underlying crash data and AI-generated commentary without HTML.
Authentication: None required. Public endpoint.
GET: https://thatcarhitme.com/api/crash-data/reports/data/massachusetts/haverhill/february-2026-report
Monthly Traffic Safety Analysis
141 CRASHES IN
HAVERHILL, MA
FEBRUARY 2026
Total crashes in HAVERHILL decreased by 13.5% from 163 in February 2025 to 141 in February 2026. Despite this reduction in total crashes, the number of total injuries rose by 42.3%, from 26 to 37, marking a significant shift in crash outcomes.
141
▼ -13.5%was 163
Total Crash Events
0
Persons Killed
37
▲ 42.3%was 26
Persons Injured
25
▼ -3.8%was 26
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. 15 crashes with unreported severity are not shown in the severity breakdown.
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, HAVERHILL experienced a decrease in total crashes, falling from 163 in February 2025 to 141 in February 2026, a 13.5% reduction. However, total injuries increased by 42.3%, from 26 to 37, while fatalities remained at zero in both periods.
25
Hit-and-Run Crashes — February 2026
▼ -3.8% vs prior (26)
The number of hit-and-run crashes slightly decreased from 26 in February 2025 to 25 in February 2026. However, the hit-and-run rate increased from 16% to 17.7% of all crashes, indicating a higher proportion of crashes involved hit-and-run incidents despite the lower absolute count.
Vulnerable Road User Casualties
0
Motorists Killed
37
Motorists Injured
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
The peak day for crashes shifted from Saturday, which had 35 crashes in February 2025, to Thursday and Friday, both recording 26 crashes in February 2026. The peak crash hour remained 2p in both periods, though the count decreased from 19 crashes in February 2025 to 14 crashes in February 2026.
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Crash date field aggregated by weekday
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
While there were no fatalities in either period, total injuries increased by 42.3%, from 26 in February 2025 to 37 in February 2026. Minor injuries (severity B) saw a count increase from 11 to 15, and possible injuries (severity C) increased from 5 to 9, leading to a higher proportion of injury crashes in the current period.
Outcome by Severity (Crash Events)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Most severe injury per crash record
Top Contributing Factors
The leading contributing factor, 'Inattention,' saw a significant increase of 20 crashes, rising from 33 in February 2025 to 53 in February 2026, and its share of crashes increased from 20.2% to 37.6%. Conversely, 'Failed to yield right of way' decreased by 6 crashes, from 24 to 18, and 'No improper driving' decreased by 3 crashes, from 18 to 15, indicating a shift in the primary causes of crashes.
Officer-Reported Primary Contributing Cause
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
There was a notable shift in crash conditions, with crashes occurring in 'Snow' conditions decreasing from 29 in February 2025 to 9 in February 2026, a reduction of 20 crashes. Crashes on 'Dry' road surfaces increased by 16, from 90 to 106, while crashes during 'Daylight' decreased by 20, from 100 to 80. Overall, the data indicates a decrease in crashes under adverse weather and road conditions.
Weather
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Weather condition at time of crash
Lighting
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Lighting condition field
Road Surface
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Road surface condition field
Vehicles & Demographics
The total number of vehicles involved in crashes decreased from 290 in February 2025 to 258 in February 2026. Among top makes, HONDA, TOYOTA, and FORD all saw decreases in involvement, while SUBARU involvement increased by 11 vehicles, from 8 to 19. The age group 0-15 saw a substantial increase in persons involved, rising from 19 to 51, a change of 32 persons.
Top Vehicle Makes (258 vehicles)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Vehicle unit records
53 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (310 persons with recorded sex)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Person-level records linked to crash events
Speed Limit Zones
Crashes in the 30 mph speed zone increased by 6, from 59 in February 2025 to 65 in February 2026. Conversely, crashes in the 35 mph speed zone decreased by 21, from 41 to 20, marking the largest shift among speed zones. There were no fatal crashes reported in any speed zone during either period.
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · 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: 2026-02-01 through 2026-02-28
- Report generated: June 21, 2026
Data Coverage
- Reporting period: 2026-02-01 through 2026-02-28 (28 days)
- Geographic scope: HAVERHILL, MA
- Total crash records analyzed: 141
- Total persons involved: 356
- Total vehicles involved: 258
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). "HAVERHILL, MA Crash Intelligence Report: February 2026." Published June 21, 2026. Reporting period: 2026-02-01 to 2026-02-28. Data source: Massachusetts Crash Data (MassDOT CDV), Arcgis_yearly Open Data. Available at: https://thatcarhitme.com/crash-data/massachusetts/haverhill/february-2026-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
ThatCarHitMe.com
An Injuria.ai Company
Crash Data Intelligence
Data: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly
Period: 2026-02-01 – 2026-02-28
Generated: June 21, 2026 · All rights reserved