Skip to main content
TruckCodex
Hubs

Crash Record OH-970150090

FMCSA crash record in Ohio on Jan 24, 1997.

Injury

What happened

On January 24, 1997, FMCSA recorded an injury crash with 3 people hurt in Ohio. The vehicle was operated by RAYNOR EXPRESS CORP (USDOT 471976). FMCSA reference OH-970150090.

Fatalities
0
Injuries
3
Vehicles
—
Carrier
RAYNOR EXPRESS CORP
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
3 injury · 2 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 48 units
Days since prior carrier crash
290
Last on Apr 9, 1996
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,812 carriers

Geographic context

How this crash sits in its setting.

Within Ohio, 11,027 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 #:
OH-970150090
Date:
Jan 24, 1997
Time:
1700
State:
Ohio
Fatalities:
0
Injuries:
3
Tow-Away:
No
HazMat:
No
Carrier (USDOT):
RAYNOR EXPRESS CORP (471976)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4092330 Jan 12, 2021 MT Tow-Away 0 0
cr_3936824 Jan 21, 2020 KS Tow-Away 0 0
cr_3837250 Aug 20, 2019 AR Injury 0 1
cr_3536195 Jan 3, 2018 ME Tow-Away 0 0
cr_3514695 Jan 1, 2018 TN Fatal 1 1
cr_3461025 Sep 13, 2017 MS Injury 0 1
cr_3174663 Feb 10, 2016 OH Injury 0 2
cr_3103096 Sep 15, 2015 GA Tow-Away 0 0
cr_2828193 Jan 24, 2014 IL Tow-Away 0 0
cr_2214096 Jan 19, 2010 PA Tow-Away 0 0

Carrier booking & risk tools

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