Monthly Traffic Safety Analysis

868 CRASHES IN
MONTGOMERY, MD
NOVEMBER 2024

All metrics benchmarked againstNovember 2023

In November 2024, Montgomery County recorded 868 total traffic crashes, a 13.9% decrease from the 1,008 crashes in November 2023. While overall crashes and injuries declined, total fatalities doubled from one to two. The most significant year-over-year change was a nearly 90% reduction in reported hit-and-run incidents, which fell from 206 to 22.

868

-13.9%was 1,008

Total Crash Events

2

100.0%was 1

Persons Killed

298

-11.0%was 335

Persons Injured

22

-89.3%was 206

Hit-and-Run Crashes

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

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

Trend Summary

The overall trend in traffic incidents shows a notable decrease year-over-year. Total crashes fell by 13.9% from 1,008 to 868, and the number of people injured decreased by 11.0% from 335 to 298. However, the number of fatalities increased from one in the prior period to two in the current period.

22

Hit-and-Run Crashes — November 2024

-89.3% vs prior (206)

There was a substantial year-over-year decrease in hit-and-run incidents. The number of hit-and-run crashes dropped from 206 in November 2023 to 22 in November 2024. Consequently, the hit-and-run rate fell sharply from 20.4% of all crashes in the prior period to 2.5% in the current period.

Vulnerable Road User Casualties

1

Pedestrians Killed

Prior: 0%

0

Cyclists Killed

Prior: 00.0%

1

Motorists Killed

Prior: 10.0%

0

Other Killed

Prior: 00.0%

41

Pedestrians Injured

Prior: 50-18.0%

9

Cyclists Injured

Prior: 650.0%

244

Motorists Injured

Prior: 277-11.9%

4

Other Injured

Prior: 2100.0%

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

When Crashes Happen

While the peak hour for crashes remained the 5 p.m. hour in both periods, the peak day of the week shifted. In November 2024, Friday was the busiest day with 163 crashes. This contrasts with November 2023, when Wednesday was the peak day with 196 crashes.

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Crash date field aggregated by weekday

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

The severity of crashes shifted year-over-year. The number of fatal crashes doubled from one to two, and the fatal crash rate increased from 0.1% to 0.2% of all crashes. The share of minor injury crashes grew from 9.9% to 16.9% of total incidents, while the proportion of crashes involving serious injuries decreased from 2.1% to 1.4%.

Outcome by Severity (Crash Events)

Fatal2fatal crashes0.2%
100.0%prior 1
Serious Injury12serious injury crashes1.4%
-42.9%prior 21
Minor Injury147minor injury crashes16.9%
47.0%prior 100
Possible Injury87possible injury crashes10%
-47.0%prior 164
No Injury584no injury crashes67.3%
-18.5%prior 717

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · KABCO injury classification scale

Severity Distribution (Crash Events)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Most severe injury per crash record

Top Contributing Factors

A direct comparison of contributing factors is not possible due to a change in how this data was categorized between the two periods. In November 2024, the top cited factor was a driver action, "Failed to Yield Right-of-Way," which was a factor in 79 crashes, or 9.1% of the total. In contrast, the top factor in November 2023 was an environmental condition, "RAIN, SNOW, WET," noted in 56 crashes.

Officer-Reported Primary Contributing Cause

Failed to Yield Right-of-Way79 (9.1%)
Other Improper Action28 (3.2%)
Followed Too Closely27 (3.1%)
Failed to Keep in Proper Lane18 (2.1%)
Too Fast For Conditions17 (2%)
Ran Off Roadway15 (1.7%)
Ran Red Light15 (1.7%)
Operated Motor Vehicle in Inattentive, Careless, Negligent, or Erratic Manner12 (1.4%)
Improper Passing12 (1.4%)
Improper Backing11 (1.3%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Officer-reported primary contributory cause per crash

Road & Environmental Conditions

In November 2024, a larger proportion of crashes occurred under favorable conditions compared to the previous year. Crashes on dry roads accounted for 77.5% of the total, up from 74.4% in the prior period. Similarly, crashes in clear weather made up 82.4% of all incidents, compared to 76.0% in November 2023.

Weather

Clear715 (83.0%)
-6.7%prior 766
Rain76 (8.8%)
-22.4%prior 98
Cloudy66 (7.7%)
13.8%prior 58
Freezing Rain Or Freezing Drizzle2 (0.2%)
Snow1 (0.1%)
Blowing Snow1 (0.1%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Weather condition at time of crash

Lighting

Daylight476 (55.1%)
-9.7%prior 527
Dark - Lighted303 (35.1%)
-11.4%prior 342
Dark - Not Lighted50 (5.8%)
8.7%prior 46
Dusk18 (2.1%)
-40.0%prior 30
Dawn12 (1.4%)
-65.7%prior 35
Dark - Unknown Lighting5 (0.6%)
-58.3%prior 12

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Lighting condition field

Road Surface

Dry673 (87.5%)
-10.3%prior 750
Wet95 (12.4%)
-28.0%prior 132
Other1 (0.1%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · Road surface condition field

Vehicles & Demographics

The top three vehicle makes involved in crashes—Toyota, Honda, and Ford—remained the same across both periods, though their relative ranking shifted. Passenger cars were the most common vehicle type in both years, accounting for 988 of 1,531 vehicles in the current period and 1,224 of 1,765 in the prior period. The total number of vehicles involved in crashes decreased by 13.2% year-over-year.

Top Vehicle Makes (1,531 vehicles)

1
TOYOTA293 (19.1%)
32.6%prior 221
2
HONDA220 (14.4%)
27.9%prior 172
3
FORD146 (9.5%)
-15.6%prior 173
4
NISSAN93 (6.1%)
19.2%prior 78
5
CHEVROLET77 (5%)
156.7%prior 30
6
HYUNDAI68 (4.4%)
44.7%prior 47
7
LEXUS50 (3.3%)
117.4%prior 23
8
MERCEDES-BENZ45 (2.9%)
9
SUBARU37 (2.4%)
23.3%prior 30
10
DODGE35 (2.3%)
0.0%prior 35

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2024-11-01 to 2024-11-30 · 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: 2024-11-01 through 2024-11-30
  • Report generated: September 9, 2026

Data Coverage

  • Reporting period: 2024-11-01 through 2024-11-30 (30 days)
  • Geographic scope: montgomery, MD
  • Total crash records analyzed: 868
  • Total persons involved: 1,589
  • Total vehicles involved: 1,531

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: November 2024." Published September 9, 2026. Reporting period: 2024-11-01 to 2024-11-30. 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/november-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