Crash Record CA0006296601

FMCSA crash record in California on Dec 3, 2013.

Injury

What happened

On December 3, 2013, FMCSA recorded an injury crash with one person hurt in California. The vehicle was operated by CROMAN CORP (USDOT 74578). FMCSA reference CA0006296601.

Fatalities
0
Injuries
1
Vehicles
Carrier
CROMAN CORP
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 16 units
Days since prior carrier crash
1,253
Last on Jun 29, 2010
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,259 carriers

Geographic context

How this crash sits in its setting.

Within California, 17,594 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 #:
CA0006296601
Date:
Dec 3, 2013
Time:
1635
State:
California
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
CROMAN CORP (74578)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_3835909 Aug 6, 2019 OR Injury 0 1
cr_3641859 Jul 25, 2018 CA Injury 0 1
cr_3495161 Oct 27, 2017 OR Tow-Away 0 0
cr_2967823 Nov 17, 2014 CA Tow-Away 0 0
cr_2956213 Oct 20, 2014 CA Tow-Away 0 0
cr_2838680 Jan 23, 2014 OR Fatal 1 1
cr_2275213 Jun 29, 2010 MT Injury 0 1
cr_1052313 Jun 13, 2002 CA Injury 0 3
cr_313854 Jan 14, 2002 OR Tow-Away 0 0
cr_574235 Jul 19, 1997 ID 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.