Skip to main content
TruckCodex
Hubs

Crash Record OH0058339295

FMCSA crash record in Ohio on Dec 12, 2005.

Tow-Away

What happened

On December 12, 2005, FMCSA recorded a tow-away crash with no reported injuries in Ohio. The vehicle was operated by D + S DISTRIBUTION SERVICES INC (USDOT 596904). FMCSA reference OH0058339295.

Fatalities
0
Injuries
0
Vehicles
—
Carrier
USDOT 596904
Vehicle Type
—
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
0 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 18 units
Days since prior carrier crash
512
Last on Jul 18, 2004
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,794 carriers

Geographic context

How this crash sits in its setting.

Within Ohio, 10,690 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 #:
OH0058339295
Date:
Dec 12, 2005
Time:
0730
State:
Ohio
Fatalities:
0
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_4632827 Sep 27, 2023 OH Injury 0 1
cr_4564373 May 3, 2023 OH Injury 0 1
cr_4260342 Nov 3, 2021 PA Tow-Away 0 0
cr_4098111 Jan 20, 2021 OH Tow-Away 0 0
cr_4063682 Nov 2, 2020 OH Tow-Away 0 0
cr_3982456 May 14, 2020 OH Tow-Away 0 0
cr_3935865 Feb 9, 2020 OH Injury 0 1
cr_3667460 Sep 16, 2018 OH Injury 0 1
cr_3361199 Feb 2, 2017 OH Fatal 1 1
cr_3142941 Nov 30, 2015 OH Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 596904 — 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.