ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · MONTGOMERY, MD · JUNE 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/june-2020-report
Monthly Traffic Safety Analysis
576 CRASHES IN
MONTGOMERY, MD
JUNE 2020
In June 2020, Montgomery County recorded 576 traffic crashes, resulting in 3 fatalities and 228 injuries. These incidents involved 1,017 people and 975 vehicles. The most frequent type of collision was a same-direction rear-end crash, accounting for 139 incidents or 24.1% of all crashes during this period.
576
Total Crash Events
3
Persons Killed
228
Persons Injured
21.4%
Hit-and-Run Rate
Note: "Persons Killed" (3) counts individual fatalities across all crash events. "Fatal" in the severity table below (3) counts crash events where at least one fatality occurred. A single crash can result in multiple fatalities. 4 crashes with unreported severity are not shown in the severity breakdown.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Aggregate counts from crash, person, and vehicle records
123
Hit-and-Run Crashes — June 2020
During this period, 123 crashes were classified as hit-and-runs, representing 21.4% of all reported incidents. This determination is based on the initial assessment by the responding law enforcement officer at the scene. These crashes involved a driver leaving the scene of the collision without providing required information.
Vulnerable Road User Casualties
Motorists represented the largest group of individuals killed or injured, with 2 fatalities and 190 injuries. Among vulnerable road users, there were no pedestrian or cyclist fatalities reported. However, 19 pedestrians and 16 cyclists sustained injuries in crashes during this period.
0
Pedestrians Killed
0
Cyclists Killed
2
Motorists Killed
1
Other Killed
19
Pedestrians Injured
16
Cyclists Injured
190
Motorists Injured
3
Other Injured
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
Crash analysis reveals that Friday was the most frequent day for incidents, with 101 crashes recorded. The single busiest hour was the 5 p.m. evening commute slot, which saw 59 crashes. Overall, a majority of collisions, 429 out of 576, occurred during daylight hours.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash date field aggregated by weekday
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The majority of crashes, 378 incidents or 65.6%, resulted in no injuries. Injury-involved crashes accounted for 33.2% of the total, comprising 16 serious injury, 83 minor injury, and 92 possible injury crashes. There were 3 fatal crashes recorded, which resulted in 3 fatalities.
Outcome by Severity (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Most severe injury per crash record
Top Contributing Factors
Analysis of contributing factors indicates that environmental conditions were frequently cited. The most common factor noted was 'RAIN, SNOW, WET,' listed in 33 crashes (5.7%), followed by wet road conditions ('N/A, WET') in 22 crashes (3.8%). Other cited factors included road construction (6 crashes) and animals in the roadway (5 crashes).
Officer-Reported Primary Contributing Cause
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
The data shows that most crashes occurred in favorable conditions. A total of 432 crashes happened in clear weather, and 412 took place on dry road surfaces. Crashes during daylight hours were most common, with 429 incidents. Adverse conditions were also present in a subset of crashes, with 48 occurring in rain and 64 on wet roads.
Weather
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Weather condition at time of crash
Lighting
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Lighting condition field
Road Surface
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Road surface condition field
Vehicles & Demographics
Among the 975 vehicles involved in crashes, passenger cars were the most common type, accounting for 698 vehicles. The most frequently involved vehicle makes were Toyota with 131 vehicles, Honda with 114 vehicles, and Ford with 90 vehicles. Data on driver age demographics was not available in this report.
Top Vehicle Makes (975 vehicles)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Vehicle unit records
At-Fault Party
In crashes where fault was assigned, drivers were determined to be the at-fault party in 528 incidents. This represents the vast majority of cases with a determined fault. Non-motorists were found at fault in 13 cases.
Intersection Type
Of the crashes that occurred at a defined intersection geometry, four-way intersections were the most common location, accounting for 184 incidents. T-intersections were the second most frequent site, with 91 crashes reported. Other intersection types like roundabouts and Y-intersections saw far fewer crashes.
Junction Type
Analysis of crash locations shows that incidents occurred more frequently at junctions than on open road segments. A total of 204 crashes were reported at intersections, with an additional 58 classified as intersection-related. In contrast, 128 crashes occurred at non-intersection locations.
Junction Type
"Other" combines 1 smaller categories (1 records): CROSSOVER RELATED (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash-level records
Roadway Division
The most common roadway design at crash locations was a two-way divided road with a positive median barrier, accounting for 230 incidents. The second most frequent road type was a two-way, undivided roadway, where 181 crashes occurred. Roads with a painted median accounted for another 60 crashes.
Roadway Division
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash-level records
Vehicle Damage Extent
Disabling damage was the most frequently reported level of vehicle damage, noted for 374 vehicles involved in collisions. Functional damage was reported for 246 vehicles, while 217 vehicles sustained only superficial damage. A total of 55 vehicles were reported as destroyed.
Vehicle Damage Extent
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Vehicle unit records
Driver Action / Circumstance
The data provided under driver actions primarily lists environmental factors. The most cited factor was 'RAIN, SNOW, WET,' associated with 50 drivers. The second most common entry was 'N/A, WET,' noted for 43 drivers, followed by 'N/A, ROAD UNDER CONSTRUCTION/MAINTENANCE' for 21 drivers.
Driver Action / Circumstance
Showing top 9 of 13 reported. 4 additional (4 total) not shown: N/A, PHYSICAL OBSTRUCTION(S), N/A, ROAD UNDER CONSTRUCTION/MAINTENANCE, RUTS, HOLES, BUMPS, N/A, RUTS, HOLES, BUMPS, SMOG, SMOKE, WET.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Person-level records linked to crash events
Driver Distraction
Excluding drivers who were not distracted, the most common form of distraction reported was 'looked but did not see,' which was cited for 148 drivers. Other specified distractions included 'other distraction' (32 drivers) and being 'inattentive or lost in thought' (25 drivers). Distractions related to cellular phone use were noted for a total of 7 drivers, including talking, texting, or other phone-related activities.
Driver Distraction
Showing top 9 of 15 reported. 6 additional (8 total) not shown: OTHER CELLULAR PHONE RELATED, TEXTING FROM A CELLULAR PHONE, USING DEVICE OBJECT BROUGHT INTO VEHICLE, EATING OR DRINKING, OTHER ELECTRONIC DEVICE (NAVIGATIONAL PALM PILOT), ADJUSTING AUDIO AND OR CLIMATE CONTROLS.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · 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 359 incidents. The second most frequent event was striking a fixed object, such as a guardrail or utility pole, which happened in 82 crashes. Collisions with parked vehicles were the third most common event, with 66 instances.
First Harmful Event
Showing top 9 of 14 reported. 5 additional (6 total) not shown: OTHER NON COLLISION, OVERTURN, OTHER PEDALCYCLE, BACKING, U-TURN.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash-level records
Point of Impact
The front of the vehicle, designated as 'twelve o'clock,' was the most common point of impact, reported in 387 instances. The rear of the vehicle ('six o'clock') was the second most frequent impact point, with 181 cases. Side impacts were less common, with the one o'clock and eleven o'clock positions being the most frequent among them.
Point of Impact
"Other" combines 7 smaller categories (119 records): EIGHT OCLOCK (27), SEVEN OCLOCK (26), THREE OCLOCK (24), NINE OCLOCK (17), FOUR OCLOCK (13), NON-COLLISION (6), UNDERSIDE (6).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Vehicle unit records
Pre-Crash Driver Action
The most common action drivers were taking immediately before a crash was 'moving at a constant speed,' reported for 401 drivers. The next most frequent pre-crash actions were 'slowing or stopping' (122 drivers) and being 'stopped in a traffic lane' (94 drivers). These three actions account for a significant portion of driver activities prior to collision.
Pre-Crash Driver Action
Showing top 9 of 20 reported. 11 additional (64 total) not shown: STARTING FROM PARKED, PARKING, MAKING U TURN, PARKED, ENTERING TRAFFIC LANE, SKIDDING, PASSING, OTHER, NEGOTIATING A CURVE, LEAVING TRAFFIC LANE, RIGHT TURN ON RED.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Vehicle unit records
Pedestrian/Cyclist Action
Among the 37 pedestrians and cyclists involved in crashes, no improper actions were noted for the majority, with 21 cases falling into this category. For those where an action was cited, being 'inattentive' was the most common, with 4 instances. Other actions included 'dart dash' and being 'in roadway improperly,' each noted in 3 cases.
Pedestrian/Cyclist Action
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Non-motorist records linked to crash events
Manner of Collision
The most prevalent crash pattern was the 'same direction rear end' collision, which accounted for 139 crashes, or 24.1% of the total. Single-vehicle crashes were the second most common type, with 108 incidents (18.8%). Angle collisions during straight movement were the third most frequent, with 92 crashes (16.0%).
Manner of Collision
"Other" combines 9 smaller categories (48 records): OPPOSITE DIRECTION SIDESWIPE (11), HEAD ON (11), SAME DIRECTION LEFT TURN (11), ANGLE MEETS LEFT TURN (4), ANGLE MEETS RIGHT TURN (4), SAME DIR REND RIGHT TURN (3), ANGLE MEETS LEFT HEAD ON (2), SAME DIR REND LEFT TURN (1), SAME DIR BOTH LEFT TURN (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash-level records
Traffic Control Device
A significant number of crashes occurred at locations with no traffic controls, accounting for 255 incidents. Intersections controlled by a traffic signal were the site of 178 crashes. Crashes at locations with stop signs were less frequent, with 31 incidents reported.
Traffic Control Device
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash-level records
Vehicle Type
Passenger cars were the predominant vehicle type involved in crashes, accounting for 698 of the 975 vehicles. Sport utility vehicles were the second most common type with 71 vehicles. Commercial vehicles, including various types of trucks and buses, were involved in 120 instances.
Vehicle Type
"Other" combines 12 smaller categories (67 records): MEDIUM/HEAVY TRUCKS 3 AXLES (OVER 10,000LBS (4,536 (12), CARGO VAN/LIGHT TRUCK 2 AXLES (OVER 10,000LBS (4,5 (11), TRANSIT BUS (9), OTHER (9), MOTORCYCLE (6), TRUCK TRACTOR (5), STATION WAGON (5), FIRE VEHICLE/NON EMERGENCY (3), AMBULANCE/NON EMERGENCY (2), FIRE VEHICLE/EMERGENCY (2), AMBULANCE/EMERGENCY (2), SCHOOL BUS (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Vehicle unit records
Person Injury Severity
Of the 1,017 people involved in crashes, 3 sustained fatal injuries and 17 sustained serious injuries. A larger number of individuals had minor injuries (96) or possible injuries (115). The majority of people involved, 786 individuals, were not injured.
Person Injury Severity
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · Crash-level records
Vehicles Per Crash
Two-vehicle collisions were the most common scenario, accounting for 309 of the 576 total crashes. Single-vehicle crashes were the second most frequent type, with 221 incidents, representing 38.4% of the total. While most crashes involved one or two vehicles, the data also includes a few larger incidents, such as one 10-vehicle crash and two 6-vehicle crashes.
Vehicles Per Crash
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-06-01 to 2020-06-30 · 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-06-01 through 2020-06-30
- Report generated: September 9, 2026
Data Coverage
- Reporting period: 2020-06-01 through 2020-06-30 (30 days)
- Geographic scope: montgomery, MD
- Total crash records analyzed: 576
- Total persons involved: 1,017
- Total vehicles involved: 975
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: June 2020." Published September 9, 2026. Reporting period: 2020-06-01 to 2020-06-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/june-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-06-01 – 2020-06-30
Generated: September 9, 2026 · All rights reserved