ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · MONTGOMERY, MD · MAY 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/may-2020-report
Monthly Traffic Safety Analysis
459 CRASHES IN
MONTGOMERY, MD
MAY 2020
In May 2020, Montgomery County recorded 459 traffic crashes, resulting in 2 fatalities and 156 injuries. A significant concentration of these incidents occurred on Fridays, which accounted for 110 of the month's total crashes. The data indicates that the afternoon commute period was a high-risk time, with crashes peaking between the hours of 2 PM and 5 PM.
459
Total Crash Events
2
Persons Killed
156
Persons Injured
19.4%
Hit-and-Run Rate
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. 3 crashes with unreported severity are not shown in the severity breakdown.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Aggregate counts from crash, person, and vehicle records
89
Hit-and-Run Crashes — May 2020
Based on the responding officer's initial determination, 89 crashes in May 2020 were classified as hit-and-run incidents. This represents 19.4% of all crashes during the period. These figures reflect the preliminary assessment at the scene of the collision.
Vulnerable Road User Casualties
During this period, 2 motorists were killed and 132 were injured in crashes. No fatalities were recorded among pedestrians or cyclists. However, 13 pedestrians and 7 cyclists sustained injuries in collisions.
0
Pedestrians Killed
0
Cyclists Killed
2
Motorists Killed
0
Other Killed
13
Pedestrians Injured
7
Cyclists Injured
132
Motorists Injured
4
Other Injured
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
Crash frequency in Montgomery County peaked on Fridays, which saw 110 incidents, significantly more than any other day of the week. The single most hazardous time of day was the 5 PM hour with 36 crashes, part of a broader afternoon peak from 2 PM to 5 PM. The majority of crashes, 325 out of 459, occurred during daylight hours.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash date field aggregated by weekday
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The majority of crashes in May 2020 resulted in no injuries, with 321 incidents (69.9%) classified as property-damage-only. Crashes involving some level of injury (possible, minor, or serious) accounted for 133 incidents. There were 2 fatal crashes recorded during this period, which resulted in 2 fatalities.
Outcome by Severity (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Most severe injury per crash record
Top Contributing Factors
The leading contributing factors cited in crash reports were predominantly environmental. Wet road conditions, whether from rain or other sources, were a factor in the top two categories, accounting for a combined 50 incidents. The factor 'RAIN, SNOW, WET' was listed in 26 crashes, while 'N/A, WET' was noted in 24 crashes.
Officer-Reported Primary Contributing Cause
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
The majority of incidents occurred in favorable environments, with over two-thirds of crashes happening in clear weather (314 incidents) and on dry road surfaces (306 incidents). A total of 325 crashes (70.8%) occurred during daylight hours. Adverse conditions were still a factor, with 57 crashes occurring in rain and 71 on wet roads.
Weather
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Weather condition at time of crash
Lighting
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Lighting condition field
Road Surface
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Road surface condition field
Vehicles & Demographics
Analysis of the 756 vehicles involved in crashes shows a prevalence of common passenger vehicle makes. Toyota was the most frequently involved make with 119 vehicles recorded in collisions. This was followed by Ford with 83 vehicles and Honda with 80 vehicles.
Top Vehicle Makes (756 vehicles)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Vehicle unit records
At-Fault Party
In incidents where fault was assigned, drivers were determined to be the at-fault party in 427 cases. Non-motorists were found to be at fault in 7 cases.
Intersection Type
Among crashes occurring at intersections with a defined geometry, four-way intersections were the most common location, accounting for 126 incidents. T-intersections were the site of the next largest group of crashes, with 62 incidents reported.
Junction Type
Crashes were most frequently located at intersections, with 130 incidents occurring directly within a junction and an additional 50 classified as intersection-related. Crashes on non-intersection roadway segments were also common, accounting for 111 incidents.
Junction Type
"Other" combines 2 smaller categories (2 records): CROSSOVER RELATED (1), ALLEY (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash-level records
Roadway Division
The most common road configuration at crash sites was a two-way, divided roadway with a positive median barrier, which was the location for 171 crashes. The second most frequent road type was a two-way, undivided road, accounting for 134 crashes.
Roadway Division
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash-level records
Vehicle Damage Extent
Disabling damage was the most frequently reported level of vehicle damage, noted for 303 vehicles involved in crashes. Functional damage was reported for 176 vehicles, while 191 vehicles sustained only superficial damage. A smaller number of vehicles, 36, were reported as destroyed.
Vehicle Damage Extent
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Vehicle unit records
Driver Distraction
Among drivers for whom a distraction was noted, 'looked but did not see' was the most common issue, cited in 90 instances. General inattentiveness or being 'lost in thought' was reported for 30 drivers. Other specified distractions included cellular phone use, which was cited in 7 instances, and distractions from outside the vehicle, noted in 6 cases.
Driver Distraction
Showing top 9 of 12 reported. 3 additional (3 total) not shown: TALKING OR LISTENING TO CELLULAR PHONE, EATING OR DRINKING, BY OTHER OCCUPANTS.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Person-level records linked to crash events
First Harmful Event
The first harmful event in the majority of crashes was a collision with another moving vehicle, which occurred in 261 incidents (56.9%). The second most common event was striking a fixed object, such as a guardrail or utility pole, which accounted for 83 crashes. Collisions with parked vehicles were the third most frequent initial event, with 57 instances.
First Harmful Event
Showing top 9 of 11 reported. 2 additional (4 total) not shown: OTHER NON COLLISION, SPILLED CARGO.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash-level records
Point of Impact
The most common point of impact on vehicles involved in collisions was the front, designated as 'Twelve Oclock,' which was reported for 321 vehicles. The second most frequent impact point was the rear ('Six Oclock'), accounting for 147 vehicles. These front and rear impacts are often associated with angle and rear-end collisions.
Point of Impact
"Other" combines 7 smaller categories (84 records): FIVE OCLOCK (21), EIGHT OCLOCK (14), NINE OCLOCK (14), SEVEN OCLOCK (14), THREE OCLOCK (12), NON-COLLISION (5), UNDERSIDE (4).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Vehicle unit records
Pre-Crash Driver Action
Prior to the collisions, the most common driver action was 'moving at a constant speed,' reported for 336 vehicles. The next most frequent pre-crash actions were 'slowing or stopping' (87 vehicles) and being 'stopped in a traffic lane' (72 vehicles).
Pre-Crash Driver Action
Showing top 9 of 20 reported. 11 additional (55 total) not shown: CHANGING LANES, PARKING, STARTING FROM PARKED, ENTERING TRAFFIC LANE, SKIDDING, MAKING U TURN, NEGOTIATING A CURVE, OTHER, PASSING, LEAVING TRAFFIC LANE, RIGHT TURN ON RED.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Vehicle unit records
Pedestrian/Cyclist Action
Among incidents involving pedestrians, 'no improper actions' was the most frequent assessment, noted in 11 cases. Other cited pedestrian actions included 'dart dash' (3 cases), 'inattentive' (2 cases), and 'in roadway improperly' (1 case).
Pedestrian/Cyclist Action
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Non-motorist records linked to crash events
Manner of Collision
The most common crash types were single-vehicle incidents, accounting for 110 crashes (24.0%), and rear-end collisions involving vehicles traveling in the same direction, with 102 crashes (22.2%). Angle collisions during straight movements were the third most frequent type, with 71 incidents.
Manner of Collision
"Other" combines 8 smaller categories (41 records): SAME DIRECTION LEFT TURN (13), OPPOSITE DIRECTION SIDESWIPE (9), SAME DIRECTION RIGHT TURN (6), SAME DIR REND RIGHT TURN (5), ANGLE MEETS LEFT TURN (4), SAME DIR REND LEFT TURN (2), SAME DIR BOTH LEFT TURN (1), ANGLE MEETS LEFT HEAD ON (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash-level records
Traffic Control Device
Nearly half of all crashes (224 incidents, 48.8%) occurred at locations with no traffic controls present. Where traffic controls were a factor, traffic signals were the most common, present at the scene of 121 crashes. An additional 30 crashes occurred at intersections controlled by a stop sign.
Traffic Control Device
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash-level records
Vehicle Type
Passenger cars were the predominant vehicle type involved in crashes, accounting for 548 of the 756 vehicles (72.5%). Sport utility vehicles (50) and pickup trucks (34) were the next most common types. Various commercial vehicles, including cargo vans, buses, and heavy trucks, were involved in at least 32 of the incidents.
Vehicle Type
"Other" combines 14 smaller categories (52 records): MOTORCYCLE (11), AMBULANCE/EMERGENCY (6), TRANSIT BUS (6), MEDIUM/HEAVY TRUCKS 3 AXLES (OVER 10,000LBS (4,536 (5), OTHER LIGHT TRUCKS (10,000LBS (4,536KG) OR LESS) (5), OTHER (5), TRUCK TRACTOR (4), FIRE VEHICLE/EMERGENCY (2), AMBULANCE/NON EMERGENCY (2), FIRE VEHICLE/NON EMERGENCY (2), OTHER BUS (1), RECREATIONAL VEHICLE (1), SCHOOL BUS (1), STATION WAGON (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Vehicle unit records
Person Injury Severity
Of the 782 people involved in crashes, the vast majority (624) reported no injuries. A total of 12 individuals, or 1.5% of all persons involved, sustained fatal (2) or suspected serious (10) injuries. An additional 146 people experienced minor or possible injuries.
Person Injury Severity
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-31 · Crash-level records
Vehicles Per Crash
The most common collision involved two vehicles, which occurred in 242 out of 459 crashes. Single-vehicle crashes were also frequent, accounting for 187 incidents (40.7%). Most other incidents involved three or four vehicles, with one crash involving six vehicles.
Vehicles Per Crash
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-05-01 to 2020-05-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-05-01 through 2020-05-31
- Report generated: September 9, 2026
Data Coverage
- Reporting period: 2020-05-01 through 2020-05-31 (31 days)
- Geographic scope: montgomery, MD
- Total crash records analyzed: 459
- Total persons involved: 782
- Total vehicles involved: 756
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: May 2020." Published September 9, 2026. Reporting period: 2020-05-01 to 2020-05-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/may-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-05-01 – 2020-05-31
Generated: September 9, 2026 · All rights reserved