Skip to main content
TruckCodex
Hubs

Crash Record OR2024030036

FMCSA crash record in ROSEBURG on Jun 11, 2024.

Tow-Away Federal Recordable

What happened

On June 11, 2024, FMCSA recorded a tow-away crash with no reported injuries in ROSEBURG, Oregon. The vehicle was operated by SYSCO PORTLAND INC (USDOT 9997). Recorded conditions: 3 / 1 / 1 pavement. Reported by SYSCO PORTLAND INC, FMCSA reference OR2024030036.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
SYSCO PORTLAND INC
USDOT 9997
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
0 injury · 5 tow-away
Crashes per 100 power units (24 mo)
2.5
3 crashes · 118 units
Days since prior carrier crash
95
Last on Mar 8, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within ROSEBURG, Oregon, 9 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
3
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 #:
OR2024030036
Date:
Jun 11, 2024
Time:
0430
State:
Oregon
City:
ROSEBURG
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SYSCO PORTLAND INC (9997)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1M1AN4GY0LM019332 2962371 (IN) SYSCO PORTLAND INC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmoz9e28w0009nufy3t4ugw5n May 6, 2026 OR Tow-Away 0 0
cr_5005948 Aug 1, 2025 OR Tow-Away 0 0
cr_4870125 Dec 23, 2024 OR Tow-Away 0 0
cr_4835814 Oct 7, 2024 OR Injury 0 2
cr_4729417 Mar 8, 2024 OR Tow-Away 0 0
cr_4685024 Jan 3, 2024 OR Tow-Away 0 0
cr_4614350 Aug 17, 2023 OR Tow-Away 0 0
cr_4609233 Aug 9, 2023 WA Tow-Away 0 0
cr_4386285 Apr 25, 2022 OR Tow-Away 0 0
cr_4330066 Feb 21, 2022 WA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2020 MACK Anthem
NHTSA recalls and complaints for this make/model/year.
Carrier
SYSCO PORTLAND INC
USDOT 9997 · 65 crashes · 40 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1M1AN4GY0LM019332
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oregon
Statewide crash records.
Agency
SYSCO PORTLAND INC
Crashes reported by this law-enforcement agency.
City
Crashes in ROSEBURG, 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.