ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · MONTGOMERY, MD · JULY 2020
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/maryland/statewide/july-2020-report
Monthly Traffic Safety Analysis
618 CRASHES IN
MONTGOMERY, MD
JULY 2020
In July 2020, Montgomery County reported 618 traffic collisions, resulting in 1 fatality and 235 injuries. The data indicates that crashes were most frequent on Thursdays, with a peak during the 5 p.m. evening commute hour. Rear-end collisions were the most common crash type, accounting for nearly a quarter of all incidents.
618
Total Crash Events
1
Persons Killed
235
Persons Injured
25.9%
Hit-and-Run Rate
Note: "Persons Killed" (1) 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. 1 crash with unreported severity is not shown in the severity breakdown.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Aggregate counts from crash, person, and vehicle records
160
Hit-and-Run Crashes — July 2020
Based on initial officer determinations, 160 crashes in July 2020 were classified as hit-and-run incidents. This represents 25.9% of all reported crashes during this period.
Vulnerable Road User Casualties
During this period, 1 motorist was killed and 190 were injured. Additionally, 25 pedestrians and 16 cyclists sustained injuries in collisions, although no fatalities were reported for these vulnerable road users. In total, 235 individuals were injured across all crash types.
0
Pedestrians Killed
0
Cyclists Killed
1
Motorists Killed
0
Other Killed
25
Pedestrians Injured
16
Cyclists Injured
190
Motorists Injured
4
Other Injured
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
Crash incidents in Montgomery County peaked late in the work week, with Thursday recording the highest number of crashes (112). The most common time for a crash was the 5 p.m. hour, which saw 50 incidents. Overall, crashes were most prevalent during daylight hours, which accounted for 426 of the 618 total collisions.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash date field aggregated by weekday
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The majority of crashes (68.0%) resulted in no injuries, involving only property damage. Injury-involved crashes accounted for 31.7% of the total, distributed among possible (18.1%), minor (10.8%), and serious (2.8%) injury categories. There was 1 fatal crash reported during this period, which resulted in one fatality.
Severity is per crash event (most severe injury). 2 fatal crash events resulted in 1 persons killed.
Outcome by Severity (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Most severe injury per crash record
Top Contributing Factors
The most frequently cited contributing factors were related to environmental conditions rather than specific driver errors. Wet conditions, including rain, were noted in the top two factors, accounting for a combined 7.8% of crashes. The factor 'RAIN, SNOW, WET' was listed in 26 incidents (4.2%), and 'N/A, WET' was listed in 22 incidents (3.6%).
Officer-Reported Primary Contributing Cause
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
The vast majority of collisions occurred in ideal driving conditions. Specifically, 78.8% of crashes happened in clear weather, 76.1% on dry road surfaces, and 68.9% during daylight hours. Crashes in adverse conditions included 41 in rain and 129 in darkness on lighted roadways.
Weather
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Weather condition at time of crash
Lighting
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Lighting condition field
Road Surface
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Road surface condition field
Vehicles & Demographics
Analysis of the 1,045 vehicles involved in crashes shows that passenger cars were the most common vehicle type. Among vehicle makes, Toyota was most frequently involved with 148 vehicles, followed by Honda with 139 vehicles and Ford with 109 vehicles. Data on driver age groups was not available for this period.
Top Vehicle Makes (1,045 vehicles)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Vehicle unit records
At-Fault Party
In crashes where fault was assigned, drivers were determined to be at fault in 566 incidents. This represents the vast majority of cases where a determination was made. Non-motorists were found to be at fault in 10 cases.
Intersection Type
Of the crashes that occurred at a defined intersection type, four-way intersections were the most common location, accounting for 198 incidents. T-intersections were the second most frequent site, with 87 crashes reported. These two types represent the vast majority of intersection-related collisions with a specified geometry.
Junction Type
Crashes were more likely to occur at or near junctions than on open road segments. Collisions at intersections accounted for 204 incidents, with an additional 72 crashes classified as intersection-related. Crashes at non-intersection locations were also significant, with 142 incidents reported.
Junction Type
"Other" combines 2 smaller categories (3 records): RESIDENTIAL DRIVEWAY (2), RAILWAY GRADE CROSSING (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level records
Roadway Division
Crashes occurred with nearly equal frequency on undivided two-way roads (229 crashes) and on divided two-way roads with a positive median barrier (222 crashes). Roads with unprotected painted medians accounted for another 56 crashes. Together, these three two-way road types were the site of the majority of collisions.
Roadway Division
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level records
Vehicle Damage Extent
Disabling damage was the most common outcome for vehicles involved in crashes, reported for 391 vehicles. Functional damage was noted for 268 vehicles, and superficial damage for 234 vehicles. A smaller number of vehicles were reported as destroyed (67) or having no damage (34).
Vehicle Damage Extent
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Vehicle unit records
Driver Action / Circumstance
The most commonly reported driver actions preceding a crash were related to environmental or traffic conditions. The top cited factor was 'RAIN, SNOW, WET,' attributed to 42 drivers. This was followed by 'N/A, WET' for 35 drivers and 'BACKUP DUE TO REGULAR CONGESTION' for 13 drivers.
Driver Action / Circumstance
Showing top 9 of 14 reported. 5 additional (7 total) not shown: SLEET, HAIL, FREEZ. RAIN, WET, N/A, VISION OBSTRUCTION (INCL. BLINDED BY SUN), N/A, V WIPERS|W OTHER ENVIRONMENTAL, N/A, PHYSICAL OBSTRUCTION(S), N/A, SHOULDERS LOW, SOFT, HIGH.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Person-level records linked to crash events
Driver Distraction
Among drivers for whom a distraction was noted, 'Looked but did not see' was the most common factor, reported for 146 drivers. Other specified distractions included 'Other distraction' (19 drivers) and being 'Inattentive or lost in thought' (18 drivers).
Driver Distraction
Showing top 9 of 14 reported. 5 additional (5 total) not shown: SMOKING RELATED, TALKING OR LISTENING TO CELLULAR PHONE, OTHER ELECTRONIC DEVICE (NAVIGATIONAL PALM PILOT), EATING OR DRINKING, USING OTHER DEVICE CONTROLS INTEGRAL TO VEHICLE.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Person-level records linked to crash events
First Harmful Event
The most common first harmful event in a crash was a collision with another motor vehicle, which occurred in 392 incidents, representing 63.4% of all crashes. Collisions with fixed objects (87 incidents) and parked vehicles (67 incidents) were the next most frequent events. Crashes involving pedestrians (25) and bicycles (10) as the first harmful event were also reported.
First Harmful Event
Showing top 9 of 13 reported. 4 additional (4 total) not shown: OTHER PEDALCYCLE, THROWN OR FALLING OBJECT, OTHER, OVERTURN.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level records
Point of Impact
The front of the vehicle was the most common point of impact, recorded as 'Twelve Oclock' for 427 vehicles. This represents approximately 40.8% of vehicles with a specified impact point. The rear of the vehicle ('Six Oclock') was the second most frequent impact point, involved in 180 instances.
Point of Impact
"Other" combines 8 smaller categories (125 records): EIGHT OCLOCK (29), FIVE OCLOCK (26), SEVEN OCLOCK (23), NINE OCLOCK (21), THREE OCLOCK (15), NON-COLLISION (4), UNDERSIDE (4), ROOF TOP (3).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Vehicle unit records
Pre-Crash Driver Action
The most common pre-crash action for drivers was 'Moving at a constant speed,' which was reported for 456 of the 1,045 drivers involved. Other frequent actions included 'Slowing or stopping' (117 drivers), 'Making a left turn' (96 drivers), and being 'Stopped in a traffic lane' (92 drivers).
Pre-Crash Driver Action
Showing top 9 of 20 reported. 11 additional (75 total) not shown: CHANGING LANES, STARTING FROM PARKED, PARKING, ENTERING TRAFFIC LANE, MAKING U TURN, PASSING, SKIDDING, NEGOTIATING A CURVE, RIGHT TURN ON RED, OTHER, LEAVING TRAFFIC LANE.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Vehicle unit records
Pedestrian/Cyclist Action
For the non-motorists involved in crashes, 'No improper actions' was the most frequently documented behavior, noted in 26 cases. However, several improper actions were also recorded, including being 'In roadway improperly' (5 cases), 'Failure to obey traffic signals' (2 cases), and 'Failure to yield right of way' (2 cases).
Pedestrian/Cyclist Action
Showing top 9 of 10 reported. 1 additional (1 total) not shown: DART DASH.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Non-motorist records linked to crash events
Manner of Collision
The most common type of collision was a same-direction rear-end crash, which accounted for 149 incidents or 24.1% of all crashes. Single-vehicle crashes were the second most frequent type, with 112 incidents (18.1%). Angle collisions involving straight movement were also common, representing 16.3% of the total.
Manner of Collision
"Other" combines 6 smaller categories (40 records): OPPOSITE DIRECTION SIDESWIPE (11), SAME DIRECTION LEFT TURN (11), SAME DIRECTION RIGHT TURN (8), ANGLE MEETS LEFT TURN (4), ANGLE MEETS RIGHT TURN (3), SAME DIR BOTH LEFT TURN (3).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level records
Traffic Control Device
A significant portion of crashes, 258 incidents or 41.7% of the total, occurred at locations with no traffic controls. Crashes at intersections with a traffic signal were also frequent, totaling 191 incidents. Locations with stop signs accounted for 41 crashes.
Traffic Control Device
"Other" combines 2 smaller categories (2 records): PERSON (1), WARNING SIGN (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level records
Vehicle Type
Passenger cars were the predominant vehicle type involved in collisions, accounting for 755 of the 1,045 vehicles (72.2%). Sport utility vehicles (90 vehicles) and pickup trucks (44 vehicles) were the next most common types. Commercial vehicles, including various trucks and buses, were involved in at least 39 crashes.
Vehicle Type
"Other" combines 12 smaller categories (53 records): OTHER LIGHT TRUCKS (10,000LBS (4,536KG) OR LESS) (8), CARGO VAN/LIGHT TRUCK 2 AXLES (OVER 10,000LBS (4,5 (7), MOTORCYCLE (7), MEDIUM/HEAVY TRUCKS 3 AXLES (OVER 10,000LBS (4,536 (7), POLICE VEHICLE/EMERGENCY (6), FIRE VEHICLE/EMERGENCY (5), AMBULANCE/EMERGENCY (4), STATION WAGON (3), SCHOOL BUS (2), TRUCK TRACTOR (2), CROSS COUNTRY BUS (1), MOPED (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Vehicle unit records
Person Injury Severity
Of the 1,092 people involved in crashes, the vast majority (856 individuals, or 78.4%) sustained no injuries. There was 1 fatality reported (0.09%), and 19 individuals (1.7%) sustained suspected serious injuries. An additional 78 people had minor injuries and 138 had possible injuries.
Person Injury Severity
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level records
Vehicles Per Crash
Two-vehicle collisions were the most common scenario, accounting for 344 crashes, or 55.7% of the total. Single-vehicle crashes were also frequent, representing 234 incidents (37.9%). Multi-vehicle crashes involving three or more vehicles were less common, with 39 such incidents reported.
Vehicles Per Crash
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-07-01 to 2020-07-31 · Crash-level 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: 2020-07-01 through 2020-07-31
- Report generated: September 9, 2026
Data Coverage
- Reporting period: 2020-07-01 through 2020-07-31 (31 days)
- Geographic scope: montgomery, MD
- Total crash records analyzed: 618
- Total persons involved: 1,092
- Total vehicles involved: 1,045
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 2020." Published September 9, 2026. Reporting period: 2020-07-01 to 2020-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-2020-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: Montgomery County Crash Reporting (ACRS) · Socrata
Period: 2020-07-01 – 2020-07-31
Generated: September 9, 2026 · All rights reserved