Monthly Traffic Safety Analysis

654 CRASHES IN
MONTGOMERY, MD
MARCH 2020

In March 2020, Montgomery County recorded 654 traffic crashes, resulting in 3 fatalities and 205 injuries. The data indicates that rear-end collisions were the most frequent type of crash, accounting for 162 incidents or nearly a quarter of all collisions during this period.

654

Total Crash Events

3

Persons Killed

205

Persons Injured

18.7%

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. 5 crashes with unreported severity are not shown in the severity breakdown.

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

122

Hit-and-Run Crashes — March 2020

During this period, 122 crashes were classified as hit-and-run incidents, representing 18.7% of all reported collisions. This classification is based on the initial determination made by the responding law enforcement officer at the scene of the crash.

Vulnerable Road User Casualties

Of the 208 total individuals killed or injured, motorists comprised the largest group, with 2 fatalities and 175 injuries. Vulnerable road users were also significantly impacted; one pedestrian was killed and 21 were injured. Additionally, 8 cyclists were injured in collisions, though none fatally.

1

Pedestrians Killed

0

Cyclists Killed

2

Motorists Killed

0

Other Killed

21

Pedestrians Injured

8

Cyclists Injured

175

Motorists Injured

1

Other Injured

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

When Crashes Happen

Crashes occurred most frequently on Mondays and Fridays, with each day recording 110 incidents. The single busiest time for collisions was the 3 p.m. hour, which saw 60 crashes. Overall, collisions were more common during daylight hours, with 432 crashes occurring in daylight compared to 199 at dawn, dusk, or in darkness.

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash date field aggregated by weekday

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash time field aggregated by hour (0-23)

Crash Severity Breakdown

The vast majority of crashes, 72.2% (472 incidents), resulted in no injuries. Injury-involved crashes accounted for 27.8% of the total, distributed among possible (96), minor (68), and serious (10) injury categories. There were 3 fatal crashes, which resulted in 3 total fatalities.

Outcome by Severity (Crash Events)

Fatal3fatal crashes0.5%
Serious Injury10serious injury crashes1.5%
Minor Injury68minor injury crashes10.4%
Possible Injury96possible injury crashes14.7%
No Injury472no injury crashes72.2%

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · KABCO injury classification scale

Severity Distribution (Crash Events)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-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. The top factor was 'N/A, WET' which was noted in 43 incidents (6.6%), followed by 'RAIN, SNOW, WET' in 38 incidents (5.8%). The prevalence of 'N/A' suggests that a specific primary factor was often not determined at the scene.

Officer-Reported Primary Contributing Cause

N/A, WET43 (6.6%)
RAIN, SNOW, WET38 (5.8%)
ANIMAL, N/A4 (0.6%)
N/A, ROAD UNDER CONSTRUCTION/MAINTENANCE4 (0.6%)
N/A, RAIN, SNOW4 (0.6%)
N/A, VISION OBSTRUCTION (INCL. BLINDED BY SUN)3 (0.5%)
BACKUP DUE TO REGULAR CONGESTION, N/A2 (0.3%)
BACKUP DUE TO NON-RECURRING INCIDENT, BACKUP DUE TO REGULAR CONGESTION, N/A1 (0.2%)
N/A, V WIPERS|W OTHER ENVIRONMENTAL1 (0.2%)
ANIMAL, RAIN, SNOW, WET1 (0.2%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Officer-reported primary contributory cause per crash

Road & Environmental Conditions

Most crashes occurred in favorable conditions, with 66.7% (436 incidents) happening in clear weather and 65.6% (429 incidents) on dry road surfaces. Similarly, 66.1% of crashes (432) took place during daylight hours. Adverse conditions were less frequent, with 83 crashes occurring in rain and 121 on wet roads.

Weather

Clear436 (72.2%)
Rain83 (13.7%)
Cloudy81 (13.4%)
Fog, Smog, Smoke4 (0.7%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Weather condition at time of crash

Lighting

Daylight432 (66.8%)
Dark - Lighted152 (23.5%)
Dark - Not Lighted25 (3.9%)
Dusk14 (2.2%)
Dawn13 (2.0%)
Dark - Unknown Lighting9 (1.4%)
Other2 (0.3%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Lighting condition field

Road Surface

Dry429 (77.6%)
Wet121 (21.9%)
Mud, Dirt, Gravel1 (0.2%)
Slush1 (0.2%)
Oil1 (0.2%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Road surface condition field

Vehicles & Demographics

The most common vehicle makes involved in crashes were Honda (136 vehicles) and Toyota (135 vehicles), followed by Ford (116 vehicles). The data includes variations in make names, such as 'TOYT' (52) and 'HOND' (42), which also ranked high in frequency. Data on driver age distribution was not available for this period.

Top Vehicle Makes (1,130 vehicles)

1
HONDA136 (12%)
2
TOYOTA135 (11.9%)
3
FORD116 (10.3%)
4
TOYT52 (4.6%)
5
NISSAN51 (4.5%)
6
HOND42 (3.7%)
7
DODGE37 (3.3%)
8
CHEV27 (2.4%)
9
CHEVROLET22 (1.9%)
10
NISS21 (1.9%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Vehicle unit records

At-Fault Party

In incidents where fault was assigned, a driver was determined to be at fault in 603 cases. A non-motorist was found at fault in 4 instances. This indicates that drivers were considered the at-fault party in over 99% of crashes where this determination was recorded.

Intersection Type

Among crashes that occurred at a specified type of intersection, four-way intersections were the most common location, accounting for 184 incidents. T-intersections were the second most common geometry, with 91 crashes recorded.

Junction Type

Crashes were nearly evenly split between junction and non-junction locations. The data shows 207 crashes occurred at an intersection and 176 occurred on a non-intersection roadway segment. An additional 63 crashes were classified as intersection-related.

Junction Type

"Other" combines 2 smaller categories (3 records): CROSSOVER RELATED (2), OTHER DRIVEWAY (1).

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash-level records

Roadway Division

The most common road design at crash locations was a 'Two-Way, Divided, Positive Median Barrier,' which accounted for 270 incidents. The second most frequent was 'Two-Way, Not Divided,' with 207 crashes. These two road types comprised the locations for the majority of reported collisions.

Roadway Division

1
TWO-WAY, DIVIDED, POSITIVE MEDIAN BARRIER270 (48%)
2
TWO-WAY, NOT DIVIDED207 (36.8%)
3
TWO-WAY, DIVIDED, UNPROTECTED PAINTED MIN 4 FEET53 (9.4%)
4
ONE-WAY TRAFFICWAY23 (4.1%)
5
OTHER8 (1.4%)
6
TWO-WAY, NOT DIVIDED WITH A CONTINUOUS LEFT TURN1 (0.2%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash-level records

Vehicle Damage Extent

Disabling damage was the most frequently reported outcome for vehicles involved in collisions, noted in 400 instances. This was followed by superficial damage (299 instances) and functional damage (277 instances). A total of 59 vehicles were reported as destroyed.

Vehicle Damage Extent

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Vehicle unit records

Driver Action / Circumstance

The data field for driver action primarily captured environmental conditions. The most cited factor was 'N/A, WET,' listed for 75 drivers, followed by 'RAIN, SNOW, WET' for 69 drivers. 'N/A, RAIN, SNOW' was the third most common entry, noted for 7 drivers.

Driver Action / Circumstance

1
N/A, WET75 (38.7%)
2
RAIN, SNOW, WET69 (35.6%)
3
N/A, RAIN, SNOW7 (3.6%)
4
VISION OBSTRUCTION (INCL. BLINDED BY SUN), WET6 (3.1%)
5
N/A, ROAD UNDER CONSTRUCTION/MAINTENANCE6 (3.1%)
6
ANIMAL, N/A5 (2.6%)
7
N/A, VISION OBSTRUCTION (INCL. BLINDED BY SUN)5 (2.6%)
8
BACKUP DUE TO REGULAR CONGESTION, N/A4 (2.1%)
9
ANIMAL, RAIN, SNOW, WET4 (2.1%)

Showing top 9 of 16 reported. 7 additional (13 total) not shown: N/A, PHYSICAL OBSTRUCTION(S), RAIN, SNOW, SLEET, HAIL, FREEZ. RAIN, WET, DEBRIS OR OBSTRUCTION, N/A, BACKUP DUE TO NON-RECURRING INCIDENT, N/A, BACKUP DUE TO NON-RECURRING INCIDENT, BACKUP DUE TO REGULAR CONGESTION, N/A, ANIMAL, WET, N/A, V WIPERS|W OTHER ENVIRONMENTAL.

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Person-level records linked to crash events

Driver Distraction

Among the 239 instances where a specific driver distraction was recorded, 'Looked But Did Not See' was the most common, cited in 157 cases. This was followed by 'Inattentive or Lost in Thought' (38 cases) and 'Other Distraction' (28 cases). Cell phone use was noted in 7 cases, including texting and talking.

Driver Distraction

1
NOT DISTRACTED674 (73.8%)
2
LOOKED BUT DID NOT SEE157 (17.2%)
3
INATTENTIVE OR LOST IN THOUGHT38 (4.2%)
4
OTHER DISTRACTION28 (3.1%)
5
DISTRACTED BY OUTSIDE PERSON OBJECT OR EVENT6 (0.7%)
6
OTHER CELLULAR PHONE RELATED4 (0.4%)
7
OTHER ELECTRONIC DEVICE (NAVIGATIONAL PALM PILOT)2 (0.2%)
8
TALKING OR LISTENING TO CELLULAR PHONE2 (0.2%)
9
TEXTING FROM A CELLULAR PHONE1 (0.1%)

Showing top 9 of 10 reported. 1 additional (1 total) not shown: EATING OR DRINKING.

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-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 moving vehicle, which occurred in 434 of 654 total crashes (66.4%). The next most frequent events were striking a fixed object (103 crashes) and hitting a parked vehicle (54 crashes).

First Harmful Event

1
OTHER VEHICLE434 (66.9%)
2
FIXED OBJECT103 (15.9%)
3
PARKED VEHICLE54 (8.3%)
4
PEDESTRIAN22 (3.4%)
5
OFF ROAD8 (1.2%)
6
BICYCLE7 (1.1%)
7
ANIMAL7 (1.1%)
8
OTHER OBJECT6 (0.9%)
9
OTHER CONVEYANCE3 (0.5%)

Showing top 9 of 13 reported. 4 additional (5 total) not shown: BACKING, OTHER NON COLLISION, OVERTURN, FELL JUMPED FROM MOTOR VEHICLE.

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash-level records

Point of Impact

For the 1,130 vehicles with a recorded point of impact, the front of the vehicle ('Twelve Oclock') was the most common area, accounting for 451 impacts. The rear of the vehicle ('Six Oclock') was the second most frequent point of impact, recorded in 219 instances.

Point of Impact

"Other" combines 7 smaller categories (116 records): SEVEN OCLOCK (23), NINE OCLOCK (23), THREE OCLOCK (23), FOUR OCLOCK (21), EIGHT OCLOCK (20), UNDERSIDE (4), NON-COLLISION (2).

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Vehicle unit records

Pre-Crash Driver Action

Of the 1,130 vehicles with a recorded pre-crash action, the most common was 'Moving Constant Speed,' reported for 492 vehicles (43.5%). The next most frequent actions were 'Slowing or Stopping' (146 vehicles) and being 'Stopped in Traffic Lane' (108 vehicles).

Pre-Crash Driver Action

1
MOVING CONSTANT SPEED492 (44.1%)
2
SLOWING OR STOPPING146 (13.1%)
3
STOPPED IN TRAFFIC LANE108 (9.7%)
4
MAKING LEFT TURN85 (7.6%)
5
ACCELERATING64 (5.7%)
6
BACKING44 (3.9%)
7
MAKING RIGHT TURN37 (3.3%)
8
CHANGING LANES31 (2.8%)
9
STARTING FROM LANE26 (2.3%)

Showing top 9 of 20 reported. 11 additional (83 total) not shown: PARKED, STARTING FROM PARKED, PARKING, MAKING U TURN, PASSING, NEGOTIATING A CURVE, OTHER, ENTERING TRAFFIC LANE, LEAVING TRAFFIC LANE, SKIDDING, DRIVERLESS MOVING VEH..

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Vehicle unit records

Pedestrian/Cyclist Action

For the 24 incidents where a pedestrian's action was recorded, 'No Improper Actions' was the most common finding, noted in 16 cases. Other recorded actions included 'Entering Exiting Parked Standing Vehicle' (3 cases) and 'Dart Dash' (2 cases).

Pedestrian/Cyclist Action

1
NO IMPROPER ACTIONS16 (66.7%)
2
ENTERING EXITING PARKED STANDING VEHICLE3 (12.5%)
3
DART DASH2 (8.3%)
4
IN ROADWAY IMPROPERLY1 (4.2%)
5
FAILURE TO OBEY TRAFFIC SIGNS SIGNALS OR OFFICER1 (4.2%)
6
NOT VISIBLE1 (4.2%)

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Non-motorist records linked to crash events

Manner of Collision

The most prevalent crash type was a same-direction rear-end collision, which accounted for 162 incidents, or 24.8% of all crashes. Single-vehicle crashes were the second most common category, with 135 incidents (20.6%), followed by straight-movement angle collisions with 104 incidents (15.9%).

Manner of Collision

"Other" combines 9 smaller categories (45 records): HEAD ON (16), SAME DIRECTION LEFT TURN (9), OPPOSITE DIRECTION SIDESWIPE (8), ANGLE MEETS RIGHT TURN (3), ANGLE MEETS LEFT TURN (3), ANGLE MEETS LEFT HEAD ON (2), SAME DIR REND RIGHT TURN (2), OPPOSITE DIR BOTH LEFT TURN (1), SAME DIR BOTH LEFT TURN (1).

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash-level records

Traffic Control Device

A significant portion of crashes, 285 incidents (43.6%), occurred at locations with no traffic controls present. Locations with a traffic signal were the site of 182 crashes (27.8%), while 40 crashes (6.1%) occurred at intersections controlled by a stop sign.

Traffic Control Device

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash-level records

Vehicle Type

Passenger cars were the most common vehicle type involved in collisions, accounting for 780 of the 1,130 vehicles recorded (69.0%). Sport Utility Vehicles were the next most frequent, with 84 vehicles involved, followed by pickup trucks (42) and vans (41).

Vehicle Type

"Other" combines 14 smaller categories (76 records): MEDIUM/HEAVY TRUCKS 3 AXLES (OVER 10,000LBS (4,536 (13), POLICE VEHICLE/EMERGENCY (11), CARGO VAN/LIGHT TRUCK 2 AXLES (OVER 10,000LBS (4,5 (10), OTHER LIGHT TRUCKS (10,000LBS (4,536KG) OR LESS) (9), MOTORCYCLE (8), AMBULANCE/EMERGENCY (5), STATION WAGON (5), OTHER (4), OTHER BUS (4), AMBULANCE/NON EMERGENCY (2), FIRE VEHICLE/EMERGENCY (2), TRUCK TRACTOR (1), CROSS COUNTRY BUS (1), MOPED (1).

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Vehicle unit records

Person Injury Severity

Of the 1,164 people involved in crashes, 956 (82.1%) sustained no apparent injury. Among those injured, 117 people had possible injuries, 76 had minor injuries, and 12 had suspected serious injuries. A total of 3 individuals sustained fatal injuries, representing 0.3% of all persons involved.

Person Injury Severity

Source: Montgomery County Crash Reporting (ACRS) · Socrata Open Data · 2020-03-01 to 2020-03-31 · Crash-level records

Vehicles Per Crash

Two-vehicle collisions were the most common scenario, accounting for 381 of the 654 total crashes (58.3%). Single-vehicle crashes were the next most frequent, with 222 incidents (34.0%). Most other crashes involved three vehicles (40 incidents), with one crash involving six vehicles.

Vehicles Per Crash

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

Data Coverage

  • Reporting period: 2020-03-01 through 2020-03-31 (31 days)
  • Geographic scope: montgomery, MD
  • Total crash records analyzed: 654
  • Total persons involved: 1,164
  • Total vehicles involved: 1,130

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: March 2020." Published September 9, 2026. Reporting period: 2020-03-01 to 2020-03-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/march-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