Skip to main content
TruckCodex
Hubs

Crash Record OR2024260057

FMCSA crash record in PORTLAND on Aug 16, 2024.

Injury Federal Recordable

What happened

On August 16, 2024, FMCSA recorded an injury crash with one person hurt in PORTLAND, Oregon. The vehicle was operated by RIVER CITY RUSH DELIVERY INC (USDOT 1208018). Recorded conditions: 1 / 1 / 1 pavement. Reported by RIVER CITY RUSH DELIVERY INC, FMCSA reference OR2024260057.

Geographic note

This crash is part of an active corridor: 234 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
RIVER CITY RUSH DELIVERY INC
USDOT 1208018
Vehicle Type
Truck
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)
6.5
2 crashes · 31 units
Days since prior carrier crash
1,177
Last on May 27, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,686 carriers

Geographic context

How this crash sits in its setting.

Within PORTLAND, Oregon, 234 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
1
Road surface
1

Conditions are mixed. The data does not assign causation; this section reports only what was recorded by the responding officer.

Crash details

Key facts from the FMCSA crash record.

Report #:
OR2024260057
Date:
Aug 16, 2024
Time:
1305
State:
Oregon
City:
PORTLAND
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
RIVER CITY RUSH DELIVERY INC (1208018)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3ALACWFCXKDKB8800 2729627 (IN) RIVER CITY RUSH DELIVERY INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

8 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5059843 Sep 9, 2025 OR Tow-Away 0 0
cr_4934343 Feb 21, 2025 OR Tow-Away 0 0
cr_4166800 May 27, 2021 WA Tow-Away 0 0
cr_4101016 Dec 21, 2020 OR Tow-Away 0 0
cr_3873539 Oct 18, 2019 WA Injury 0 1
cr_3716011 Dec 27, 2018 OR Tow-Away 0 0
cr_3757530 Aug 23, 2018 OR Tow-Away 0 0
cr_3589817 Mar 20, 2018 OR Injury 0 1

Carrier booking & risk tools

Check booking and risk signals for USDOT 1208018 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
RIVER CITY RUSH DELIVERY INC
USDOT 1208018 · 9 crashes · 47 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3ALACWFCXKDKB8800
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oregon
Statewide crash records.
Agency
RIVER CITY RUSH DELIVERY INC
Crashes reported by this law-enforcement agency.
City
Crashes in PORTLAND, OR
All crashes on file for this city.
Index
All Crash Records
Browse FMCSA commercial vehicle crash records.
Database
Roadside Inspections
Inspection history and violation details.
Database
NHTSA Recalls
Active recall campaigns.

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.