Skip to main content
TruckCodex
Hubs

Crash Record CO2011000813

FMCSA crash record in Colorado on Jun 14, 2011.

Tow-Away

What happened

On June 14, 2011, FMCSA recorded a tow-away crash with no reported injuries in Colorado. The vehicle was operated by STEVE SCHMIDT TRUCKING INC (USDOT 905584). FMCSA reference CO2011000813.

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

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 7 units
Days since prior carrier crash
2,549
Last on Jun 21, 2004
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,833 carriers

Geographic context

How this crash sits in its setting.

Within Colorado, 2,862 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 #:
CO2011000813
Date:
Jun 14, 2011
Time:
1915
State:
Colorado
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_4844335 Sep 24, 2024 CO Tow-Away 0 0
cr_3323886 Sep 19, 2016 CO Tow-Away 0 0
cr_3301889 May 3, 2016 CO Tow-Away 0 0
cr_3221436 Apr 7, 2016 CO Tow-Away 0 0
cr_3195865 Oct 7, 2015 CO Tow-Away 0 0
cr_3039112 Apr 3, 2015 CO Tow-Away 0 0
cr_2995019 Jan 26, 2015 CO Tow-Away 0 0
cr_2451154 Aug 15, 2011 KS Fatal 1 0
cr_1294623 Jun 21, 2004 CO Injury 0 3
cr_258085 Jun 22, 2001 CO Tow-Away 0 0

Carrier booking & risk tools

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