Skip to main content
TruckCodex
Hubs

Crash Record OH0215111812

FMCSA crash record in JACKSON (TOWNSHIP OF) on Jun 24, 2021.

Tow-Away Federal Recordable

What happened

On June 24, 2021, FMCSA recorded a tow-away crash with no reported injuries in JACKSON (TOWNSHIP OF), Ohio. The vehicle was operated by PORTABLE CRUSHING LLC (USDOT 2255075). Recorded conditions: 1 / 1 / 1 pavement. Reported by PORTABLE CRUSHING LLC, FMCSA reference OH0215111812.

Carrier pattern note

This is the carrier's 4 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 power units.

Geographic note

This crash is part of an active corridor: 103 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
USDOT 2255075
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 fatal · 0 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 9 units
Days since prior carrier crash
300
Last on Aug 28, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 316,014 carriers

Geographic context

How this crash sits in its setting.

Within JACKSON (TOWNSHIP OF), Ohio, 103 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
OH0215111812
Date:
Jun 24, 2021
Time:
1524
State:
Ohio
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 6 1XP5DB9X4YD537205 PWD4406 (OH) PORTABLE CRUSHING LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4822963 Oct 8, 2024 IN Tow-Away 0 0
cr_4027170 Aug 28, 2020 PA Tow-Away 0 0
cr_3990711 Jun 1, 2020 OH Fatal 1 0
cr_3898330 Dec 2, 2019 OH Tow-Away 0 0
cr_3785077 Apr 24, 2019 KY Tow-Away 0 0
cr_3619294 Jun 26, 2018 OH Tow-Away 0 0
cr_3555509 Feb 25, 2018 OH Injury 0 1
cr_3571118 Jan 4, 2018 OH Injury 0 2
cr_3515740 Dec 28, 2017 OH Injury 0 1
cr_3504720 Dec 1, 2017 OH Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 2255075 — tools open pre-filled.

Related records

Frequently asked questions about FMCSA crash records

What does this crash report tell me about the carrier? ▾
An individual FMCSA crash record tells you that a commercial vehicle operated by this carrier was involved in a reportable crash on the date listed, along with the severity (fatalities / injuries / tow-away) and the responding agency. A single crash record does not tell you whether the carrier was at fault, whether the driver was cited, or how the crash affected the carrier's safety scores. To evaluate the carrier, compare the full multi-year crash history against the carrier's fleet size, miles driven, and cohort peers.
Was this crash the carrier's fault? ▾
FMCSA crash records do not assign fault. Fault attribution requires reviewing the police report, any litigation outcome, and FMCSA's preventability determination if one was requested. If you need a fault determination, request the underlying state police crash report (PAR) — the carrier or its insurer can pull this through standard channels.
How does this crash affect the carrier's safety scores? ▾
Crash records feed FMCSA's Crash Indicator BASIC inside the Safety Measurement System (SMS). Each FMCSA-reportable crash counts for two years from the crash date and is weighted by severity (fatal / injury / tow-only). The Crash Indicator score is normalized against the carrier's power-unit count and exposure, so larger fleets need more crashes to score the same percentile as smaller ones. Non-reportable crashes do not enter the score.
Will this crash show up on the carrier's CSA SMS scores? ▾
If the federal_recordable flag on this record is true, yes — it will appear in the carrier's Crash Indicator BASIC for two years from the crash date. Crashes flagged state-only (state_recordable) are visible on the public crash file but do not enter the federal score.
How do I check the carrier's full crash history? ▾
Click through to the carrier profile (the USDOT link near the top of this page). The carrier's profile lists every crash on file, severity counts, and links into the SMS detail when an MC docket is on record. You can also visit FMCSA's SAFER and SMS portals directly using the carrier's USDOT number.
What if details look wrong — how do I correct an FMCSA crash record? ▾
FMCSA's DataQs system handles corrections to crash records. Either the carrier or an interested third party can file a Request for Data Review (RDR) with supporting documentation (police report, court records, witness statements). Corrections are processed by the originating state agency and propagate to the federal file within roughly 60–120 days when accepted.