ThatCarHitMe.com
An Injuria.ai Company
YEAR-OVER-YEAR CRASH REPORT · WELLESLEY, MA · AUGUST 2025
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/wellesley/august-2025-report
Monthly Traffic Safety Analysis
55 CRASHES IN
WELLESLEY, MA
AUGUST 2025
In August 2025, Wellesley experienced 55 crashes, marking a 22.2% increase from the 45 crashes recorded in August 2024. The most significant change observed was the presence of 1 fatality in the current period, compared to 0 fatalities in the prior year.
55
▲ 22.2%was 45
Total Crash Events
1
Persons Killed
5
▼ -58.3%was 12
Persons Injured
3
▲ 200.0%was 1
Hit-and-Run Crashes
Note: "Persons Killed" (1) counts individual fatalities across all crash events. "Fatal" in the severity table below (1) 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-08-01 to 2025-08-31 · Aggregate counts from crash, person, and vehicle records
Trend Summary
Overall, total crashes in Wellesley showed an upward trend, increasing by 22.2% from 45 crashes in August 2024 to 55 crashes in August 2025. While total fatalities increased from 0 to 1, total injuries decreased by 58.3%, from 12 to 5, indicating a shift in crash outcomes.
3
Hit-and-Run Crashes — August 2025
▲ 200.0% vs prior (1)
Hit-and-run incidents increased year-over-year, with 3 crashes reported in August 2025 compared to 1 crash in August 2024. This resulted in the hit-and-run rate rising from 2.2% of all crashes in the prior period to 5.5% in the current period, indicating an upward trend.
Vulnerable Road User Casualties
1
Motorists Killed
5
Motorists Injured
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-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. In August 2025, the peak day for crashes was Friday with 11 incidents, while in August 2024, Thursday saw the most crashes with 10 incidents. The peak crash hour also changed from 12 PM with 9 crashes in the prior period to 5 PM with 10 crashes in the current period.
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Crash date field aggregated by weekday
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The severity distribution of crashes changed significantly, with August 2025 recording 1 fatal crash (1.8% of total crashes) compared to 0 fatal crashes in August 2024. The proportion of crashes resulting in injuries (Serious, Minor, or Possible) decreased from 20% (9 crashes) in the prior period to 7.2% (4 crashes) in the current period, despite an increase in total crashes.
Outcome by Severity (Crash Events)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Most severe injury per crash record
Top Contributing Factors
Analysis of contributing factors shows shifts in prevalence. 'Inattention' increased from 9 crashes in August 2024 to 15 crashes in August 2025, a 66.7% increase in count, becoming the top factor. Conversely, 'Followed too closely' decreased from 12 crashes to 10 crashes, a 16.7% decrease in count, moving from the top factor to second. 'Failed to yield right of way' more than doubled, rising from 4 crashes to 9 crashes year-over-year.
Officer-Reported Primary Contributing Cause
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
Crash conditions remained largely consistent year-over-year. The majority of crashes in both periods occurred under 'Clear' weather conditions, accounting for 45 crashes in August 2025 and 35 crashes in August 2024. Similarly, 'Daylight' was the predominant lighting condition for 53 crashes in the current period and 43 crashes in the prior period, and 'Dry' road surfaces were present in 52 crashes and 42 crashes respectively.
Weather
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Weather condition at time of crash
Lighting
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Lighting condition field
Road Surface
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Road surface condition field
Vehicles & Demographics
Toyota remained the most frequently involved vehicle make, increasing from 16 vehicles in August 2024 to 22 vehicles in August 2025. Honda also saw a notable increase in involvement, from 5 vehicles to 12 vehicles. Regarding persons involved, the 65+ age group saw an increase from 19 persons in the prior period to 22 persons in the current period, while the 26-34 age group decreased from 20 persons to 11 persons.
Top Vehicle Makes (107 vehicles)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Vehicle unit records
11 persons with unknown or unrecorded age excluded from age chart.
Sex Distribution (101 persons with recorded sex)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-31 · Person-level records linked to crash events
Speed Limit Zones
A significant shift was observed in crashes occurring in 30 mph zones, which doubled from 15 crashes in August 2024 to 30 crashes in August 2025, and included the single fatal crash in the current period. Conversely, crashes in 50 mph zones decreased by 50%, from 18 crashes to 9 crashes. Crashes in 55 mph zones saw a slight increase from 5 to 6.
Fatal crashes by zone: 30 mph: 1 of 30 (3.333%)
Source: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly Open Data · 2025-08-01 to 2025-08-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-08-01 through 2025-08-31
- Report generated: June 21, 2026
Data Coverage
- Reporting period: 2025-08-01 through 2025-08-31 (31 days)
- Geographic scope: WELLESLEY, MA
- Total crash records analyzed: 55
- Total persons involved: 113
- Total vehicles involved: 107
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). "WELLESLEY, MA Crash Intelligence Report: August 2025." Published June 21, 2026. Reporting period: 2025-08-01 to 2025-08-31. Data source: Massachusetts Crash Data (MassDOT CDV), Arcgis_yearly Open Data. Available at: https://thatcarhitme.com/crash-data/massachusetts/wellesley/august-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
ThatCarHitMe.com
An Injuria.ai Company
Crash Data Intelligence
Data: Massachusetts Crash Data (MassDOT CDV) · Arcgis_yearly
Period: 2025-08-01 – 2025-08-31
Generated: June 21, 2026 · All rights reserved