Crash Record UT1805202611

FMCSA crash record in Utah on Sep 24, 2018.

Tow-Away

What happened

On September 24, 2018, FMCSA recorded a tow-away crash with no reported injuries in Utah. The vehicle was operated by RON OSBORNE TRUCKING INC (USDOT 295311). FMCSA reference UT1805202611.

Fatalities
0
Injuries
0
Vehicles
Carrier
RON OSBORNE TRUCKING INC
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 · 7 units
Days since prior carrier crash
539
Last on Apr 3, 2017
Vs fleet-size peers
above the median
Cohort median 0.0 · 313,835 carriers

Geographic context

How this crash sits in its setting.

Within Utah, 1,492 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 #:
UT1805202611
Date:
Sep 24, 2018
Time:
2109
State:
Utah
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_4807766 Sep 4, 2024 UT Tow-Away 0 0
cr_4396743 Jun 24, 2022 CA Injury 0 1
cr_4370092 May 31, 2022 UT Tow-Away 0 0
cr_3977703 Feb 7, 2020 UT Tow-Away 0 0
cr_4075297 Apr 11, 2019 UT Injury 0 1
cr_3406003 Apr 3, 2017 CA Tow-Away 0 0
cr_2171829 Jul 22, 2008 UT Injury 0 1
cr_1546030 Oct 23, 2005 CA Tow-Away 0 0
cr_1320970 Aug 4, 2004 UT Tow-Away 0 0
cr_1113569 Apr 24, 2001 UT Injury 0 1

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.