Crash Record OH0146077336

FMCSA crash record in Ohio on Jul 16, 2014.

Fatal

What happened

On July 16, 2014, FMCSA recorded a fatal crash that resulted in one death in Ohio. The vehicle was operated by ROCKIN S TRUCKIN INC (USDOT 1881356). FMCSA reference OH0146077336.

Fatalities
1
Injuries
0
Vehicles
Carrier
ROCKIN S TRUCKIN INC
Vehicle Type
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 fatal · 0 injury
Crashes per 100 power units (24 mo)
7.5
11 crashes · 146 units
Prior carrier crash
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,695 carriers

Geographic context

How this crash sits in its setting.

Within Ohio, 11,577 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
OH0146077336
Date:
Jul 16, 2014
Time:
2240
State:
Ohio
Fatalities:
1
Injuries:
0
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5124128 Mar 18, 2026 AR Injury 0 1
cr_5116692 Feb 18, 2026 TX Tow-Away 0 0
cr_5080500 Dec 4, 2025 TX Injury 0 1
cr_5076836 Dec 3, 2025 OK Tow-Away 0 0
cr_5072691 Nov 28, 2025 TX Tow-Away 0 0
cr_5034045 Sep 22, 2025 LA Injury 0 1
cr_5030323 Sep 9, 2025 TX Tow-Away 0 0
cr_4943979 May 3, 2025 TX Tow-Away 0 0
cr_4931902 Apr 19, 2025 OK Injury 0 1
cr_4916180 Mar 17, 2025 TX Tow-Away 0 0

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.