Monthly Traffic Safety Analysis

73 CRASHES IN
NORTH ATTLEBOROUGH, MA
FEBRUARY 2026

All metrics benchmarked againstFebruary 2025

In February 2026, NORTH ATTLEBOROUGH, MA experienced 73 total crashes, a substantial increase from the 13 crashes reported in February 2025. This represents a 461.54% year-over-year increase in total crashes. The most notable shift was the dramatic rise in overall crash incidents, accompanied by a 466.67% increase in total injuries, from 3 to 17.

73

461.5%was 13

Total Crash Events

0

Persons Killed

17

466.7%was 3

Persons Injured

3

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

Trend Summary

The overall trend indicates a significant increase in crash activity year-over-year, with total crashes rising from 13 in February 2025 to 73 in February 2026. This constitutes a 461.54% increase in crash incidents. Similarly, the number of injured persons also saw a substantial rise from 3 to 17, marking a 466.67% increase.

3

Hit-and-Run Crashes — February 2026

200.0% vs prior (1)

The number of hit-and-run crashes increased from 1 in February 2025 to 3 in February 2026. Despite this increase in count, the overall hit-and-run crash rate decreased from 7.7% of total crashes in February 2025 to 4.1% in February 2026.

Vulnerable Road User Casualties

0

Motorists Killed

Prior: 00.0%

17

Motorists Injured

Prior: 3466.7%

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 Thursday in February 2025, which saw 5 crashes, to Saturday in February 2026, with 17 crashes. The peak hour also changed, moving from 11a with 3 crashes in the prior period to 2p with 9 crashes in the current period.

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

There were no fatal crashes in either February 2025 or February 2026. However, crashes resulting in any injury (Serious, Minor, or Possible) increased from 2 in February 2025 to 13 in February 2026. This includes the appearance of 1 serious injury crash in February 2026, where none were reported in the prior year.

Outcome by Severity (Crash Events)

Serious Injury1serious injury crashes1.4%
Minor Injury7minor injury crashes9.6%
600.0%prior 1
Possible Injury5possible injury crashes6.8%
400.0%prior 1
No Injury60no injury crashes82.2%
445.5%prior 11

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 contributing factor 'No improper driving' saw a significant increase, rising from 1 crash in February 2025 to 19 crashes in February 2026. 'Driving too fast for conditions' decreased from 6 crashes to 4 crashes year-over-year. Additionally, 'Failed to yield right of way' and 'Followed too closely' emerged as prominent factors in February 2026, accounting for 12 and 9 crashes respectively, categories not among the top reported factors in February 2025.

Officer-Reported Primary Contributing Cause

No improper driving19 (26%)
Failed to yield right of way12 (16.4%)
Followed too closely9 (12.3%)
Other improper action4 (5.5%)
Driving too fast for conditions4 (5.5%)-33.3%prior 6
Failure to keep in proper lane or running off road4 (5.5%)
Visibility obstructed4 (5.5%)
Disregarded traffic signs, signals, road markings3 (4.1%)
Swerving or avoiding due to wind, slippery surface, vehicle, object, vulnerable user in roadway3 (4.1%)
Glare2 (2.7%)

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

Crashes occurring in daylight conditions increased from 5 in February 2025 to 47 in February 2026. Crashes on dry road surfaces increased from 7 to 41, and crashes on snow-covered roads increased from 4 to 14. The proportion of crashes occurring on adverse road surfaces (snow, slush, wet, ice) remained relatively stable, at 46.2% in February 2025 and 42.5% in February 2026.

Weather

Clear33 (45.2%)
Snow11 (15.1%)
Cloudy10 (13.7%)
Clear/Clear7 (9.6%)
40.0%prior 5
Snow/Snow4 (5.5%)
Sleet, hail (freezing rain or drizzle)/Sleet, hail (freezing rain or drizzle)2 (2.7%)
Sleet, hail (freezing rain or drizzle)/Snow1 (1.4%)
Sleet, hail (freezing rain or drizzle)1 (1.4%)
Snow/Cloudy1 (1.4%)
Snow/Rain1 (1.4%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Weather condition at time of crash

Lighting

Daylight47 (64.4%)
840.0%prior 5
Dark - lighted roadway10 (13.7%)
Dark - roadway not lighted7 (9.6%)
0.0%prior 7
Dusk5 (6.8%)
Dawn3 (4.1%)
Dark - unknown roadway lighting1 (1.4%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Lighting condition field

Road Surface

Dry41 (56.9%)
485.7%prior 7
Snow14 (19.4%)
Slush6 (8.3%)
Wet6 (8.3%)
Ice5 (6.9%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Road surface condition field

Vehicles & Demographics

Top Vehicle Makes (139 vehicles)

1
TOYOTA23 (16.5%)
2
NISSAN18 (12.9%)
3
HONDA18 (12.9%)
4
JEEP10 (7.2%)
5
CHEVROLET10 (7.2%)
6
FORD8 (5.8%)
7
HYUNDAI7 (5%)
8
SUBARU5 (3.6%)
9
RAM3 (2.2%)
10
KIA3 (2.2%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-02-01 to 2026-02-28 · Vehicle unit records

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

Sex Distribution (156 persons with recorded sex)

Male87 (55.8%)
480.0%prior 15
Female69 (44.2%)
527.3%prior 11

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

The total number of crashes with a recorded speed limit increased from 11 in February 2025 to 73 in February 2026. Crashes in the 25 mph zone increased from 1 to 7, and those in the 65 mph zone increased from 10 to 16. The 30 mph zone became the most frequent speed zone for crashes in February 2026 with 29 incidents, a category not explicitly detailed in the prior period's data.

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: NORTH ATTLEBOROUGH, MA
  • Total crash records analyzed: 73
  • Total persons involved: 166
  • Total vehicles involved: 139

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). "NORTH ATTLEBOROUGH, 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/north-attleborough/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

North Attleborough, MA Crash Report — February 2026 | ThatCarHitMe.com