ThatCarHitMe.com
An Injuria.ai Company
CRASH INTELLIGENCE REPORT · MONTGOMERY, MD · APRIL 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/april-2020-report
Monthly Traffic Safety Analysis
374 CRASHES IN
MONTGOMERY, MD
APRIL 2020
In April 2020, Montgomery County recorded 374 traffic crashes, which resulted in 1 fatality and 90 injuries. A notable finding from this period is that 22.2% of all crashes, totaling 83 incidents, were classified as hit-and-runs based on the responding officer's initial report.
374
Total Crash Events
1
Persons Killed
90
Persons Injured
22.2%
Hit-and-Run Rate
Note: "Persons Killed" (1) counts individual fatalities across all crash events. "Fatal" in the severity table below (1) 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-04-01 to 2020-04-30 · Aggregate counts from crash, person, and vehicle records
83
Hit-and-Run Crashes — April 2020
During this period, 83 crashes were identified as hit-and-runs, accounting for 22.2% of all reported incidents. This classification is based on the initial determination made by the responding officer at the scene of the crash.
Vulnerable Road User Casualties
During this period, 1 motorist was killed and 71 were injured in traffic crashes. Among vulnerable road users, no fatalities were recorded, but 12 pedestrians and 6 cyclists sustained injuries. These stemmed from 13 pedestrian-involved crashes and 6 bicycle-involved crashes in total.
0
Pedestrians Killed
0
Cyclists Killed
1
Motorists Killed
0
Other Killed
12
Pedestrians Injured
6
Cyclists Injured
71
Motorists Injured
1
Other Injured
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Mode classified from person records (driver/passenger → motorist; pedestrian; bicyclist → cyclist; in-line skater / unspecified → other)
When Crashes Happen
Crashes occurred most frequently on Thursdays, with 71 incidents reported on that day of the week. The single busiest hour for crashes was 12 p.m., which saw 36 incidents. A clear daytime pattern emerged, with 258 crashes (69% of the total) occurring during daylight hours, and a sustained peak in incidents from 12 p.m. through 6 p.m.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash date field aggregated by weekday
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash time field aggregated by hour (0-23)
Crash Severity Breakdown
The majority of crashes, 293 out of 374 (78.3%), resulted in no injuries. Injury-involved crashes, encompassing serious, minor, and possible injuries, accounted for 81 incidents (21.7% of the total). There was 1 fatal crash during this period, which resulted in 1 fatality.
Outcome by Severity (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · KABCO injury classification scale
Severity Distribution (Crash Events)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Most severe injury per crash record
Top Contributing Factors
The most frequently cited contributing factor was "RAIN, SNOW, WET," which was noted in 43 crashes, or 11.5% of the total. The second most common factor was "N/A, WET" with 16 occurrences (4.3%), also indicating the influence of wet conditions. Other noted factors included animal involvement in 7 crashes.
Officer-Reported Primary Contributing Cause
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Officer-reported primary contributory cause per crash
Road & Environmental Conditions
The majority of crashes occurred in favorable conditions, with 58.6% (219 crashes) happening in clear weather and 61% (228 crashes) on dry road surfaces. Daylight conditions were present for 258 crashes, representing 69% of all incidents. Adverse conditions were also a factor, with rain reported in 68 crashes and wet road surfaces in 72 crashes.
Weather
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Weather condition at time of crash
Lighting
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Lighting condition field
Road Surface
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Road surface condition field
Vehicles & Demographics
The data on vehicle makes involved in crashes shows Toyota as the most frequent, with 89 vehicles recorded. Ford was the second most common with 78 vehicles, followed by Honda with 58 vehicles. Other frequently listed makes include Nissan (32 vehicles) and Dodge (23 vehicles); data for driver age distribution was not available in this report.
Top Vehicle Makes (584 vehicles)
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Vehicle unit records
At-Fault Party
Based on the available data where fault was assigned, drivers were determined to be the at-fault party in 336 instances. This represents 97.9% of cases with an at-fault determination. Non-motorists were found to be at fault in the remaining 7 cases.
Intersection Type
Four-way intersections were the most common location for crashes occurring at an intersection, accounting for 112 incidents. This represents 66.3% of all crashes where the intersection geometry was specified. T-intersections were the next most frequent type, with 38 crashes reported at these locations.
Junction Type
Crashes occurred more frequently at junctions than on open roadway segments. Incidents at intersections accounted for 126 crashes, or 48.1% of cases where a junction type was specified. Non-intersection locations were the site of 91 crashes, representing 34.7% of the reported total.
Junction Type
"Other" combines 1 smaller categories (2 records): CROSSOVER RELATED (2).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash-level records
Roadway Division
Crashes were most prevalent on roadways with a "TWO-WAY, DIVIDED, POSITIVE MEDIAN BARRIER," accounting for 130 incidents. This was closely followed by crashes on "TWO-WAY, NOT DIVIDED" roads, which saw 125 incidents. Together, these two road types represented 83.3% of crashes where the road division was documented.
Roadway Division
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash-level records
Vehicle Damage Extent
The most commonly reported level of vehicle damage was "Disabling," which was noted for 239 vehicles involved in crashes. This category, representing vehicles that were not drivable after the crash, accounted for 42% of all vehicles with damage extent reported. "Functional" damage was the next most frequent category with 141 vehicles.
Vehicle Damage Extent
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Vehicle unit records
Driver Action / Circumstance
The most frequently cited driver-related factor was "RAIN, SNOW, WET," associated with 66 drivers. The second most common entry was "N/A, WET," reported for 27 drivers. These top factors primarily describe environmental conditions present at the time of the crash rather than specific driver maneuvers.
Driver Action / Circumstance
Showing top 9 of 16 reported. 7 additional (8 total) not shown: ANIMAL, WET, V WIPERS|W OTHER ENVIRONMENTAL, WET, N/A, RAIN, SNOW, N/A, ROAD UNDER CONSTRUCTION/MAINTENANCE, N/A, SMOG, SMOKE, N/A, TRAFFIC CONTROL DEVICE INOPERATIVE, N/A, V EXHAUST SYSTEM|R OTHER ROAD, WET.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · 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, reported for 78 drivers. "Inattentive or lost in thought" was the second most frequent distraction, with 26 occurrences. Other specified distractions included "Other distraction" (11 drivers) and distractions by an outside person, object, or event (4 drivers).
Driver Distraction
Showing top 9 of 12 reported. 3 additional (3 total) not shown: ADJUSTING AUDIO AND OR CLIMATE CONTROLS, OTHER CELLULAR PHONE RELATED, OTHER ELECTRONIC DEVICE (NAVIGATIONAL PALM PILOT).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-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 216 incidents (57.8% of the total). The second most frequent event was striking a fixed object, such as a guardrail or utility pole, which happened in 70 crashes. Collisions with parked vehicles (40 crashes) and pedestrians (15 crashes) were the next most common initial events.
First Harmful Event
Showing top 9 of 13 reported. 4 additional (4 total) not shown: OTHER PEDALCYCLE, OVERTURN, OTHER CONVEYANCE, OTHER.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash-level records
Point of Impact
The front of the vehicle ("Twelve Oclock") was the most common point of impact, recorded in 242 instances, representing 41.4% of all vehicles for which an impact point was documented. The rear of the vehicle ("Six Oclock") was the second most frequent impact point, with 90 occurrences (15.4%).
Point of Impact
"Other" combines 8 smaller categories (64 records): EIGHT OCLOCK (15), SEVEN OCLOCK (14), NINE OCLOCK (13), FOUR OCLOCK (11), THREE OCLOCK (7), UNDERSIDE (2), NON-COLLISION (1), ROOF TOP (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Vehicle unit records
Pre-Crash Driver Action
The most common pre-crash action for drivers was "Moving constant speed," reported for 274 vehicles (46.9% of the total). "Slowing or stopping" was the next most frequent action with 55 occurrences, followed closely by "Making left turn" with 52 occurrences. Other notable actions included accelerating (39 drivers) and being stopped in a traffic lane (34 drivers).
Pre-Crash Driver Action
Showing top 9 of 20 reported. 11 additional (42 total) not shown: PARKING, STARTING FROM PARKED, PARKED, MAKING U TURN, OTHER, ENTERING TRAFFIC LANE, NEGOTIATING A CURVE, SKIDDING, RIGHT TURN ON RED, LEAVING TRAFFIC LANE, PASSING.
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Vehicle unit records
Pedestrian/Cyclist Action
In 13 instances involving a pedestrian, their action was deemed proper and recorded as "No improper actions." Improper actions were noted in several cases, including 2 instances of "Failure to obey traffic signs," 2 instances of "Failure to yield right of way," and 2 instances of being "In roadway improperly." There was also one reported case of a pedestrian performing a "Dart dash" action.
Pedestrian/Cyclist Action
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Non-motorist records linked to crash events
Manner of Collision
Single-vehicle crashes were the most common type of incident, accounting for 87 crashes or 23.3% of the total. The next most frequent collision manners were "Straight movement angle" crashes (68 incidents, 18.2%) and "Same direction rear end" collisions (67 incidents, 17.9%). These top three categories collectively represent nearly 60% of all crashes during the period.
Manner of Collision
"Other" combines 8 smaller categories (34 records): HEAD ON (11), OPPOSITE DIRECTION SIDESWIPE (6), SAME DIRECTION RIGHT TURN (5), ANGLE MEETS LEFT HEAD ON (3), OPPOSITE DIR BOTH LEFT TURN (3), SAME DIR REND RIGHT TURN (3), ANGLE MEETS RIGHT TURN (2), ANGLE MEETS LEFT TURN (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash-level records
Traffic Control Device
A significant portion of crashes, 170 incidents or 45.5%, occurred at locations with "No controls." Where traffic controls were present, traffic signals were the most common, with 97 crashes occurring at signalized locations. Stop signs were present at the location of 21 crashes.
Traffic Control Device
"Other" combines 1 smaller categories (1 records): WARNING SIGN (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash-level records
Vehicle Type
Passenger cars were the most common type of vehicle involved in crashes, accounting for 401 of the 584 vehicles (68.7%). Sport Utility Vehicles were the next most frequent with 38 vehicles, followed by vans and pickup trucks, each with 23 vehicles. Commercial vehicles, including various trucks and buses, were involved in at least 40 instances.
Vehicle Type
"Other" combines 11 smaller categories (38 records): AMBULANCE/EMERGENCY (8), POLICE VEHICLE/EMERGENCY (6), MEDIUM/HEAVY TRUCKS 3 AXLES (OVER 10,000LBS (4,536 (6), CARGO VAN/LIGHT TRUCK 2 AXLES (OVER 10,000LBS (4,5 (5), OTHER (3), MOTORCYCLE (3), FIRE VEHICLE/NON EMERGENCY (2), SCHOOL BUS (2), STATION WAGON (1), AMBULANCE/NON EMERGENCY (1), FIRE VEHICLE/EMERGENCY (1).
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Vehicle unit records
Person Injury Severity
Of the 607 people involved in crashes, 516 (85%) were reported to have no injuries. There was 1 fatality and 8 individuals who sustained suspected serious injuries. Combined, fatal and serious injuries accounted for 1.5% of all persons involved, while an additional 82 people had minor or possible injuries.
Person Injury Severity
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-30 · Crash-level records
Vehicles Per Crash
Two-vehicle collisions were the most common scenario, comprising 182 of the 374 total crashes (48.7%). Single-vehicle crashes were also very frequent, accounting for 172 incidents, or 46% of the total. Crashes involving three or more vehicles were less common, with 16 three-vehicle crashes reported.
Vehicles Per Crash
Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-04-01 to 2020-04-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-04-01 through 2020-04-30
- Report generated: September 9, 2026
Data Coverage
- Reporting period: 2020-04-01 through 2020-04-30 (30 days)
- Geographic scope: montgomery, MD
- Total crash records analyzed: 374
- Total persons involved: 607
- Total vehicles involved: 584
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: April 2020." Published September 9, 2026. Reporting period: 2020-04-01 to 2020-04-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/april-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-04-01 – 2020-04-30
Generated: September 9, 2026 · All rights reserved