Skip to main content
TruckCodex
Hubs

Crash Record OR2017260057

FMCSA crash record in Oregon on Mar 27, 2017.

Tow-Away

What happened

On March 27, 2017, FMCSA recorded a tow-away crash with no reported injuries in Oregon. The vehicle was operated by RM BEVERAGE LLC (USDOT 745149). FMCSA reference OR2017260057.

Carrier pattern note

This is the carrier's 4 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 51–500 power units.

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

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 fatal · 0 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 111 units
Days since prior carrier crash
199
Last on Sep 9, 2016
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,367 carriers

Geographic context

How this crash sits in its setting.

Within Oregon, 2,796 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 #:
OR2017260057
Date:
Mar 27, 2017
Time:
1345
State:
Oregon
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
RM BEVERAGE LLC (745149)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4611926 Jul 21, 2023 OR Fatal 1 0
cr_4536194 Mar 30, 2023 WA Tow-Away 0 0
cr_4425775 Aug 10, 2022 OR Tow-Away 0 0
cr_4348605 Mar 17, 2022 OR Injury 0 1
cr_4169600 May 12, 2021 OR Tow-Away 0 0
cr_4143385 Mar 15, 2021 OR Tow-Away 0 0
cr_4023470 Aug 24, 2020 OR Tow-Away 0 0
cr_3762729 Mar 1, 2019 OR Injury 0 1
cr_3748877 Feb 5, 2019 OR Tow-Away 0 0
cr_3670390 Sep 11, 2018 OR Tow-Away 0 0

Carrier booking & risk tools

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