Monthly Traffic Safety Analysis

857 CRASHES IN
MONTGOMERY, MD
JULY 2025

All metrics benchmarked againstJuly 2024

In July 2025, Montgomery County recorded 857 total crashes, a slight increase of 0.5% from the 853 crashes reported in July 2024. While the total number of fatalities remained stable at five, the most notable year-over-year shift was in the type of person killed, with pedestrian fatalities increasing from one to four and motorist fatalities decreasing from four to one.

857

0.5%was 853

Total Crash Events

5

Persons Killed

296

-0.7%was 298

Persons Injured

25

-16.7%was 30

Hit-and-Run Crashes

Note: "Persons Killed" (5) counts individual fatalities across all crash events. "Fatal" in the severity table below (5) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities. 48 crashes with unreported severity are not shown in the severity breakdown.

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Aggregate counts from crash, person, and vehicle records

Trend Summary

Overall crash trends in Montgomery County remained relatively stable year-over-year. Total crashes increased by a marginal 0.5%, from 853 in July 2024 to 857 in July 2025. The total number of injuries saw a slight decrease of 0.7% from 298 to 296, and fatalities were unchanged at five for both periods.

25

Hit-and-Run Crashes — July 2025

-16.7% vs prior (30)

Hit-and-run incidents decreased in both absolute numbers and as a percentage of total crashes. The count of hit-and-run crashes fell from 30 in July 2024 to 25 in July 2025. This corresponds to a drop in the hit-and-run rate from 3.5% of all crashes in the prior period to 2.9% in the current period.

Vulnerable Road User Casualties

4

Pedestrians Killed

Prior: 1300.0%

0

Cyclists Killed

Prior: 00.0%

1

Motorists Killed

Prior: 4-75.0%

0

Other Killed

Prior: 00.0%

31

Pedestrians Injured

Prior: 303.3%

14

Cyclists Injured

Prior: 15-6.7%

247

Motorists Injured

Prior: 2470.0%

4

Other Injured

Prior: 6-33.3%

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)

When Crashes Happen

The temporal patterns of crashes showed a slight shift between the two periods. In July 2025, the peak day for crashes was Tuesday with 163 incidents, moving from Monday (144 crashes) in the prior year. The peak hour for collisions also shifted an hour later, from the 4 PM hour in July 2024 (69 crashes) to the 5 PM hour in July 2025 (76 crashes).

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Crash date field aggregated by weekday

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

The number of fatal crashes remained unchanged at five in both July 2025 and July 2024. However, there was a notable decrease in the number of crashes resulting in serious injuries, which fell from 19 (2.2% of total crashes) in the prior year to 12 (1.4% of total) in the current period. The proportions of minor, possible, and no-injury crashes remained largely consistent year-over-year.

Outcome by Severity (Crash Events)

Fatal5fatal crashes0.6%
0.0%prior 5
Serious Injury12serious injury crashes1.4%
-36.8%prior 19
Minor Injury141minor injury crashes16.5%
-1.4%prior 143
Possible Injury97possible injury crashes11.3%
4.3%prior 93
No Injury554no injury crashes64.6%
1.3%prior 547

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · KABCO injury classification scale

Severity Distribution (Crash Events)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Most severe injury per crash record

Top Contributing Factors

Failing to yield right-of-way was the leading contributing factor in both periods, though its count decreased by 22.9% from 70 crashes in July 2024 to 54 in July 2025. The second most cited factor, 'Other Improper Action,' saw its count increase from 36 to 40 incidents. Crashes attributed to 'Followed Too Closely' declined from 35 to 30.

Officer-Reported Primary Contributing Cause

Failed to Yield Right-of-Way54 (6.3%)-22.9%prior 70
Other Improper Action40 (4.7%)11.1%prior 36
Followed Too Closely30 (3.5%)-14.3%prior 35
Improper Backing20 (2.3%)33.3%prior 15
Failed to Keep in Proper Lane18 (2.1%)-21.7%prior 23
Operated Motor Vehicle in Inattentive, Careless, Negligent, or Erratic Manner14 (1.6%)-22.2%prior 18
Too Fast For Conditions14 (1.6%)-26.3%prior 19
Ran Red Light12 (1.4%)71.4%prior 7
Improper Turn9 (1.1%)-25.0%prior 12
Ran Off Roadway7 (0.8%)-12.5%prior 8

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Officer-reported primary contributory cause per crash

Road & Environmental Conditions

While most crashes in both periods occurred in clear weather on dry roads, there was an increase in crashes under adverse conditions. The number of crashes reported during rain increased from 59 in July 2024 to 80 in July 2025, and incidents on wet road surfaces rose from 80 to 96. The proportion of crashes occurring in daylight increased from 75.0% to 79.5% of all crashes.

Weather

Clear708 (83.9%)
0.4%prior 705
Rain80 (9.5%)
35.6%prior 59
Cloudy56 (6.6%)
-25.3%prior 75

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Weather condition at time of crash

Lighting

Daylight681 (80.1%)
6.4%prior 640
Dark - Lighted137 (16.1%)
-7.4%prior 148
Dark - Not Lighted17 (2.0%)
-50.0%prior 34
Dusk9 (1.1%)
50.0%prior 6
Dawn3 (0.4%)
-66.7%prior 9
Other2 (0.2%)
Dark - Unknown Lighting1 (0.1%)
-80.0%prior 5

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Lighting condition field

Road Surface

Dry620 (86.6%)
-6.2%prior 661
Wet96 (13.4%)
20.0%prior 80

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Road surface condition field

Vehicles & Demographics

Toyota, Honda, and Ford remained the top three vehicle makes involved in crashes across both periods. The number of Toyotas involved in collisions saw a notable increase from 269 in July 2024 to 320 in July 2025. Regarding vehicle types, the count of passenger cars involved increased from 912 to 988, while the involvement of sport utility vehicles decreased from 255 to 211.

Top Vehicle Makes (1,473 vehicles)

1
TOYOTA320 (21.7%)
19.0%prior 269
2
HONDA214 (14.5%)
-4.0%prior 223
3
FORD129 (8.8%)
-7.2%prior 139
4
CHEVROLET82 (5.6%)
12.3%prior 73
5
NISSAN80 (5.4%)
-15.8%prior 95
6
HYUNDAI67 (4.5%)
1.5%prior 66
7
SUBARU38 (2.6%)
-19.1%prior 47
8
KIA36 (2.4%)
33.3%prior 27
9
LEXUS36 (2.4%)
28.6%prior 28
10
MERCEDES-BENZ32 (2.2%)
33.3%prior 24

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2025-07-01 to 2025-07-31 · Vehicle unit records

Data Sources & Methodology

Primary Data Source

All crash data in this report is sourced from Montgomery County Crash Reporting (ACRS) (https://data.montgomerycountymd.gov/d/bhju-22kf), accessed programmatically via the Socrata 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: Socrata Open Data API (SoQL queries)
  • Dataset URL: https://data.montgomerycountymd.gov/d/bhju-22kf
  • Data format: Structured JSON via REST API
  • Record types queried: Crash events, person records, and vehicle unit records
  • Date filter applied: 2025-07-01 through 2025-07-31
  • Report generated: September 9, 2026

Data Coverage

  • Reporting period: 2025-07-01 through 2025-07-31 (31 days)
  • Geographic scope: montgomery, MD
  • Total crash records analyzed: 857
  • Total persons involved: 1,532
  • Total vehicles involved: 1,473

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). "montgomery, MD Crash Intelligence Report: July 2025." Published September 9, 2026. Reporting period: 2025-07-01 to 2025-07-31. Data source: Montgomery County Crash Reporting (ACRS), Socrata Open Data. Dataset: https://data.montgomerycountymd.gov/d/bhju-22kf. Available at: https://thatcarhitme.com/crash-data/maryland/statewide/july-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