Monthly Traffic Safety Analysis

36 CRASHES IN
READING, MA
APRIL 2026

All metrics benchmarked againstApril 2025

In April 2026, Reading, MA recorded 36 crashes, marking a 44% increase from the 25 crashes reported in April 2025. Total injuries also saw a 20% rise, from 5 to 6. The most notable year-over-year shift was in crashes attributed to 'Followed too closely,' which surged by 200% from 5 incidents in the prior period to 15 in the current period.

36

44.0%was 25

Total Crash Events

0

Persons Killed

6

20.0%was 5

Persons Injured

2

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-04-01 to 2026-04-30 · Aggregate counts from crash, person, and vehicle records

Trend Summary

The overall trend indicates an increase in crash incidents, with total crashes rising by 44% from 25 in April 2025 to 36 in April 2026. Concurrently, total injuries increased by 20%, from 5 to 6. Fatalities remained at 0 in both periods, indicating a stable, non-fatal outcome trend despite the rise in incidents.

2

Hit-and-Run Crashes — April 2026

0.0% vs prior (2)

The number of hit-and-run crashes remained stable at 2 incidents in both April 2025 and April 2026. However, due to an overall increase in total crashes, the hit-and-run rate decreased from 8% in April 2025 to 5.6% in April 2026.

Vulnerable Road User Casualties

0

Motorists Killed

Prior: 00.0%

6

Motorists Injured

Prior: 520.0%

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · 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 Friday with 5 crashes in April 2025 to Wednesday with 9 crashes in April 2026. The peak hour also changed significantly, moving from 7 AM with 4 crashes in April 2025 to 3 PM with 8 crashes in April 2026. This suggests a shift in the timing of peak crash activity within the month.

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · Crash date field aggregated by weekday

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

There were no fatal crashes in either April 2025 or April 2026. Minor injury crashes increased from 2 (8% of total) in the prior period to 3 (8.3% of total) in the current period, while possible injury crashes decreased from 3 (12% of total) to 1 (2.8% of total). Crashes with no injuries rose from 19 (76% of total) to 32 (88.9% of total), indicating a higher proportion of non-injury incidents despite the overall increase in crash count.

Outcome by Severity (Crash Events)

Minor Injury3minor injury crashes8.3%
50.0%prior 2
Possible Injury1possible injury crashes2.8%
-66.7%prior 3
No Injury32no injury crashes88.9%
68.4%prior 19

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · KABCO injury classification scale

Severity Distribution (Crash Events)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · Most severe injury per crash record

Top Contributing Factors

The leading contributing factor, 'Followed too closely,' increased from 5 crashes in April 2025 to 15 crashes in April 2026, representing a 200% rise in count and growing from a 20% to a 41.7% share of all crashes. 'Failed to yield right of way' also saw a substantial increase, from 1 crash in the prior period to 5 crashes in the current period, a 400% change in count. Conversely, 'No improper driving' decreased by 33.3% in count, from 3 to 2 crashes.

Officer-Reported Primary Contributing Cause

Followed too closely15 (41.7%)200.0%prior 5
Failed to yield right of way5 (13.9%)
Inattention4 (11.1%)
No improper driving2 (5.6%)
Distracted1 (2.8%)
Disregarded traffic signs, signals, road markings1 (2.8%)
Fatigued/asleep1 (2.8%)
Other improper action1 (2.8%)
Failure to keep in proper lane or running off road1 (2.8%)
Made an improper turn1 (2.8%)

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · Officer-reported primary contributory cause per crash

Road & Environmental Conditions

Crashes occurring in 'Clear/Clear' weather conditions increased by 100%, from 11 in April 2025 to 22 in April 2026. Similarly, crashes under 'Cloudy/Cloudy' conditions also doubled from 3 to 6. Regarding road surface, crashes on 'Dry' roads increased by 76.5% from 17 to 30, while those on 'Wet' roads decreased by 25% from 8 to 6. Information on lighting conditions was not available for the prior period, preventing a comparative analysis.

Weather

Clear/Clear22 (61.1%)
100.0%prior 11
Cloudy/Cloudy6 (16.7%)
Clear2 (5.6%)
Cloudy/Clear1 (2.8%)
Cloudy/Rain1 (2.8%)
Rain/Cloudy1 (2.8%)
Rain/Rain1 (2.8%)
Clear/Cloudy1 (2.8%)
Cloudy1 (2.8%)

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

Lighting

Daylight30 (83.3%)
Dark - lighted roadway4 (11.1%)
Dark - roadway not lighted1 (2.8%)
Dusk1 (2.8%)

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

Road Surface

Dry30 (83.3%)
76.5%prior 17
Wet6 (16.7%)
-25.0%prior 8

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

Vehicles & Demographics

The total number of vehicles involved in crashes increased by 48%, from 52 in April 2025 to 77 in April 2026. Honda and Toyota remained the top two vehicle makes involved in crashes, with Honda increasing from 7 to 12 vehicles and Toyota from 7 to 11 vehicles. There was a notable increase in persons aged 16-20 involved in crashes, rising from 1 in the prior period to 14 in the current period, and for ages 45-54, increasing from 8 to 17.

Top Vehicle Makes (77 vehicles)

1
HONDA12 (15.6%)
71.4%prior 7
2
TOYOTA11 (14.3%)
57.1%prior 7
3
SUBARU8 (10.4%)
4
FORD8 (10.4%)
33.3%prior 6
5
JEEP5 (6.5%)
6
MAZDA4 (5.2%)
7
NISSAN4 (5.2%)
8
CHEVROLET3 (3.9%)
9
ACURA3 (3.9%)
10
KIA2 (2.6%)

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

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

Sex Distribution (92 persons with recorded sex)

Male52 (56.5%)
57.6%prior 33
Female40 (43.5%)
90.5%prior 21

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · Person-level records linked to crash events

Speed Limit Zones

Crashes in 30 mph zones increased by 88.9%, from 9 in April 2025 to 17 in April 2026, becoming the most frequent speed zone for crashes. Crashes in 40 mph zones rose by 50%, from 4 to 6, and 35 mph zones also saw a 50% increase, from 2 to 3. Conversely, crashes in 65 mph zones decreased by 50%, from 4 to 2. No fatal crashes were reported in any speed zone for either period.

Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2026-04-01 to 2026-04-30 · 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-04-01 through 2026-04-30
  • Report generated: June 21, 2026

Data Coverage

  • Reporting period: 2026-04-01 through 2026-04-30 (30 days)
  • Geographic scope: READING, MA
  • Total crash records analyzed: 36
  • Total persons involved: 100
  • Total vehicles involved: 77

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). "READING, MA Crash Intelligence Report: April 2026." Published June 21, 2026. Reporting period: 2026-04-01 to 2026-04-30. Data source: Massachusetts Crash Data (MassDOT CDV), Arcgis_yearly Open Data. Available at: https://thatcarhitme.com/crash-data/massachusetts/reading/april-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

Reading, MA Crash Report — April 2026 | ThatCarHitMe.com