Monthly Traffic Safety Analysis

11 CRASHES IN
BOXBOROUGH, MA
JUNE 2024

All metrics benchmarked againstJune 2023

In June 2024, BOXBOROUGH, MA recorded 11 total crashes, a decrease of 26.7% compared to the 15 crashes reported in June 2023. Both periods reported zero fatalities and zero injuries. A notable shift was observed in 'Rear-end' collisions, which decreased from 5 crashes in June 2023 to 1 crash in June 2024.

11

-26.7%was 15

Total Crash Events

0

Persons Killed

0

Persons Injured

0

-100.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. 11 crashes with unreported severity are not shown in the severity breakdown.

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

Trend Summary

Overall, crash incidents in BOXBOROUGH, MA showed a downward trend year-over-year. Total crashes decreased from 15 in June 2023 to 11 in June 2024, representing a 26.7% reduction. This indicates a decrease in crash frequency for the specified period.

When Crashes Happen

The temporal distribution of crashes shifted year-over-year. While Thursday remained the peak day for crashes, increasing from 3 in June 2023 to 4 in June 2024, the peak hour changed from 4 PM with 3 crashes in June 2023 to 8 AM with 2 crashes in June 2024. Notably, Sunday and Tuesday saw no crashes in June 2024, compared to 3 and 2 crashes respectively in June 2023.

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

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

Top Contributing Factors

The landscape of contributing factors saw shifts year-over-year. 'Followed too closely' crashes significantly decreased from 4 in June 2023 to 1 in June 2024, a 75% reduction in count. Crashes attributed to 'No improper driving' decreased slightly from 6 to 5. 'Inattention', which accounted for 2 crashes in June 2023, was not reported as a factor in June 2024, while new factors like 'Glare', 'Exceeded authorized speed limit', 'Over-correcting/over-steering', and 'Visibility obstructed' each contributed to 1 crash in June 2024.

Officer-Reported Primary Contributing Cause

No improper driving5 (45.5%)-16.7%prior 6
Followed too closely1 (9.1%)
Glare1 (9.1%)
Exceeded authorized speed limit1 (9.1%)
Over-correcting/over-steering1 (9.1%)
Visibility obstructed1 (9.1%)
Illness1 (9.1%)

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

Road & Environmental Conditions

Crash conditions saw changes across the periods. Crashes occurring in 'Daylight' decreased from 11 in June 2023 to 6 in June 2024. 'Wet' road surface conditions were a factor in 1 crash in June 2024, down from 4 crashes in June 2023. Crashes under 'Clear' weather conditions also decreased from 9 to 8.

Weather

Clear8 (72.7%)
-11.1%prior 9
Cloudy1 (9.1%)
Cloudy/Clear1 (9.1%)
Rain1 (9.1%)

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

Lighting

Daylight6 (54.5%)
-45.5%prior 11
Dark - lighted roadway2 (18.2%)
Dark - roadway not lighted2 (18.2%)
Dawn1 (9.1%)

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

Road Surface

Dry10 (90.9%)
-9.1%prior 11
Wet1 (9.1%)

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

Vehicles & Demographics

Top Vehicle Makes (15 vehicles)

1
TOYOTA5 (33.3%)
-16.7%prior 6
2
HONDA3 (20%)
3
LEXUS2 (13.3%)
4
FORD2 (13.3%)
5
MERCEDES-BENZ1 (6.7%)
6
RAM1 (6.7%)
7
JEEP1 (6.7%)

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

Sex Distribution (15 persons with recorded sex)

Male10 (66.7%)
-16.7%prior 12
Female5 (33.3%)
-37.5%prior 8

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

Speed Limit Zones

Crashes in the 65 mph speed zone saw a substantial decrease, falling from 12 in June 2023 to 5 in June 2024. Conversely, crashes in the 40 mph zone slightly increased from 2 to 3. Additionally, June 2024 reported crashes in 25 mph, 30 mph, and 45 mph zones, which were not present in the June 2023 data, while the 35 mph zone reported 1 crash in June 2023 but none in June 2024. No fatalities were reported in any speed zone during either period.

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

Data Coverage

  • Reporting period: 2024-06-01 through 2024-06-30 (30 days)
  • Geographic scope: BOXBOROUGH, MA
  • Total crash records analyzed: 11
  • Total persons involved: 16
  • Total vehicles involved: 15

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

Boxborough, MA Crash Report — June 2024 | ThatCarHitMe.com