Crash Record OR2022030087
FMCSA crash record in 38.53 N WARM SPRINGS on Dec 7, 2022.
Injury
Federal Recordable
What happened
On December 7, 2022, FMCSA recorded an injury crash with one person hurt in 38.53 N WARM SPRINGS, Oregon. The vehicle was operated by LEVI'S EXPEDITION LLC (USDOT 2439546). Recorded conditions: 1 / 4 / 6 pavement. Reported by LEVI'S EXPEDITION LLC, FMCSA reference OR2022030087.
Fatalities
0
Injuries
1
Vehicles
2
Carrier
LEVI'S EXPEDITION LLC
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)
9.1
1 crashes · 11 units
Days since prior carrier crash
805
Last on Sep 23, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,424 carriers
Contributing factors
What the responding officer recorded.
- Light
- 1
- Weather
- 4
- Road surface
- 6
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 #:
- OR2022030087
- Date:
- Dec 7, 2022
- Time:
- 1221
- State:
- Oregon
- City:
- 38.53 N WARM SPRINGS
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- LEVI'S EXPEDITION LLC (2439546)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 9 | 3 | 3AKJGLD59FSGE7667 | 77487RP (WA) | LEVI'S EXPEDITION LLC | 3 | No |
Crash event
Event sequence description.
1:1:NONCOLLISION:RAN OFF ROAD;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT
Other crashes by this carrier
9 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_5071157 | Oct 1, 2025 | OR | Tow-Away | 0 | 0 |
| cr_4776239 | Jun 20, 2024 | OR | Tow-Away | 0 | 0 |
| cr_4675166 | Nov 30, 2023 | CA | Tow-Away | 0 | 0 |
| cr_4696538 | Nov 22, 2023 | OR | Tow-Away | 0 | 0 |
| cr_4529482 | Mar 15, 2023 | WA | Tow-Away | 0 | 0 |
| cr_4497532 | Dec 20, 2022 | OR | Tow-Away | 0 | 0 |
| cr_4038325 | Sep 23, 2020 | WA | Tow-Away | 0 | 0 |
| cr_3565908 | Mar 6, 2018 | WA | Tow-Away | 0 | 0 |
| cr_3130775 | Dec 5, 2015 | OR | Fatal | 1 | 0 |
Related records
Vehicle
2015 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
20V214000
EXTERIOR LIGHTING
Recall
19V370000
SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK
Recall
19V093000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
LEVI'S EXPEDITION LLC
USDOT 2439546 · 10 crashes · 84 inspections
Vehicle
VIN: 3AKJGLD59FSGE7667
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oregon
Statewide crash records.
Agency
LEVI'S EXPEDITION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in 38.53 N WARM SPRINGS, 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.