Monthly Traffic Safety Analysis

17 CRASHES IN
LUNENBURG, MA
JANUARY 2024

All metrics benchmarked againstJanuary 2023

In January 2024, Lunenburg experienced 17 crashes, a decrease from the 29 crashes recorded in January 2023. This represents a 41.4% reduction in total crashes year-over-year. The most notable shift was the complete absence of injuries in January 2024, compared to 3 injuries in the prior year.

17

-41.4%was 29

Total Crash Events

0

Persons Killed

0

-100.0%was 3

Persons Injured

0

Fatal Crash Events

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

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

Trend Summary

Overall, the trend for crashes in Lunenburg shows a significant decline, with total crashes decreasing from 29 in January 2023 to 17 in January 2024. This marks a 41.4% reduction in crash incidents year-over-year. Fatalities remained at zero in both periods, while injuries decreased from 3 to 0.

When Crashes Happen

The peak day for crashes shifted from Monday in January 2023, which had 13 crashes, to Monday and Tuesday in January 2024, both with 5 crashes. The peak hour remained 3 p.m. in both periods, though the number of crashes at this hour decreased from 5 in January 2023 to 3 in January 2024.

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

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

Top Contributing Factors

The leading contributing factor, 'No improper driving,' decreased significantly from 19 crashes in January 2023 to 6 crashes in January 2024. 'Driving too fast for conditions' saw an increase, going from 1 crash in the prior year to 2 crashes in the current year. 'Failed to yield right of way' and 'Inattention' each accounted for 2 crashes in January 2024, while 'Illness' contributed to 1 crash, none of which were top factors in the prior year's data.

Officer-Reported Primary Contributing Cause

No improper driving6 (35.3%)-68.4%prior 19
Driving too fast for conditions2 (11.8%)
Failed to yield right of way2 (11.8%)
Inattention2 (11.8%)
Illness1 (5.9%)

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

Road & Environmental Conditions

Crashes occurring in clear weather conditions decreased from 11 in January 2023 to 10 in January 2024, while crashes in snowy conditions (including snow/sleet) decreased from 11 to 6. The proportion of crashes occurring in daylight increased from 17 of 29 (58.6%) in January 2023 to 11 of 17 (64.7%) in January 2024. Crashes on dry road surfaces decreased from 11 to 7 year-over-year.

Weather

Clear10 (58.8%)
-9.1%prior 11
Snow5 (29.4%)
-37.5%prior 8
Other/Unknown1 (5.9%)
Snow/Sleet, hail (freezing rain or drizzle)1 (5.9%)

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

Lighting

Daylight11 (68.8%)
-35.3%prior 17
Dark - lighted roadway4 (25.0%)
-33.3%prior 6
Dark - roadway not lighted1 (6.3%)
-80.0%prior 5

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

Road Surface

Dry7 (43.8%)
-36.4%prior 11
Snow5 (31.3%)
-50.0%prior 10
Wet2 (12.5%)
Ice1 (6.3%)
Slush1 (6.3%)

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

Vehicles & Demographics

Top Vehicle Makes (24 vehicles)

1
TOYOTA4 (16.7%)
2
FORD4 (16.7%)
-55.6%prior 9
3
GMC3 (12.5%)
4
MAZDA2 (8.3%)
5
HONDA2 (8.3%)
6
DODGE2 (8.3%)
7
NISSAN2 (8.3%)
8
VOLKSWAGEN1 (4.2%)
9
MACK1 (4.2%)
10
MNNI1 (4.2%)

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

Sex Distribution (23 persons with recorded sex)

Male16 (69.6%)
-27.3%prior 22
Female7 (30.4%)
-50.0%prior 14

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

Speed Limit Zones

The distribution of crashes across speed zones shifted, with crashes in the 30 mph zone decreasing from 9 in January 2023 to 6 in January 2024, and the 35 mph zone decreasing from 7 to 1. Conversely, crashes in the 40 mph zone increased from 4 in January 2023 to 5 in January 2024. No fatalities were recorded in any speed zone during either period.

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

Data Coverage

  • Reporting period: 2024-01-01 through 2024-01-31 (31 days)
  • Geographic scope: LUNENBURG, MA
  • Total crash records analyzed: 17
  • Total persons involved: 24
  • Total vehicles involved: 24

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

Lunenburg, MA Crash Report — January 2024 | ThatCarHitMe.com