Skip to main content

Crash Record OR2004360008

FMCSA crash record in Oregon on Jul 13, 2004.

Injury

What happened

On July 13, 2004, FMCSA recorded an injury crash with one person hurt in Oregon. The vehicle was operated by THE SAUNDERS COMPANY INC (USDOT 904522). FMCSA reference OR2004360008.

Fatalities
0
Injuries
1
Vehicles
—
Carrier
THE SAUNDERS COMPANY INC
Vehicle Type
—
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
1 injury · 3 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 2 units
Days since prior carrier crash
309
Last on Sep 8, 2003
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,566,811 carriers

Geographic context

How this crash sits in its setting.

Within Oregon, 2,988 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 #:
OR2004360008
Date:
Jul 13, 2004
Time:
1530
State:
Oregon
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No

Other crashes by this carrier

6 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4798100 Aug 12, 2024 OR Tow-Away 0 0
cr_1880387 Nov 1, 2007 OR Tow-Away 0 0
cr_1438159 Mar 18, 2005 OR Tow-Away 0 0
cr_1168478 Sep 8, 2003 OR Tow-Away 0 0
cr_1285929 Jul 17, 2003 OR Tow-Away 0 0
cr_285277 Oct 2, 2001 OR 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.