Crash Record OR2025430024
FMCSA crash record in 9.72 N LONG CREEK on Feb 5, 2025.
Injury
Federal Recordable
What happened
On February 5, 2025, FMCSA recorded an injury crash with one person hurt in 9.72 N LONG CREEK, Oregon. The vehicle was operated by TIGER TRUCKING LLC (USDOT 3563906). Recorded conditions: 5 / 1 / 6 pavement. Reported by TIGER TRUCKING LLC, FMCSA reference OR2025430024.
Carrier pattern note
This is the carrier's 8 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 power units.
Fatalities
0
Injuries
1
Vehicles
1
Vehicle Type
Truck
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
8
2 injury · 8 tow-away
Crashes per 100 power units (24 mo)
14.3
2 crashes · 14 units
Days since prior carrier crash
93
Last on Nov 4, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,961 carriers
Contributing factors
What the responding officer recorded.
- Light
- 5
- Weather
- 1
- 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 #:
- OR2025430024
- Date:
- Feb 5, 2025
- Time:
- 0840
- State:
- Oregon
- City:
- 9.72 N LONG CREEK
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 1
- Carrier (USDOT):
- TIGER TRUCKING LLC (3563906)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 9 | 3 | 1FUJHHDR7LLLN1827 | A059522 (UT) | TIGER TRUCKING LLC | 3 | No |
Crash event
Event sequence description.
3:18:COLLISION INVOLVING FIXED OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE;1:1:NONCOLLISION:RAN OFF ROAD
Other crashes by this carrier
9 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_4889792 | Nov 4, 2024 | NM | Tow-Away | 0 | 0 |
| cr_4787029 | Jul 24, 2024 | WA | Tow-Away | 0 | 0 |
| cr_4785544 | Jul 16, 2024 | PA | Injury | 0 | 1 |
| cr_4763227 | Jun 4, 2024 | WA | Tow-Away | 0 | 0 |
| cr_4743767 | Apr 5, 2024 | TX | Tow-Away | 0 | 0 |
| cr_4717396 | Mar 13, 2024 | WY | Tow-Away | 0 | 0 |
| cr_4663468 | Nov 24, 2023 | WY | Tow-Away | 0 | 0 |
| cr_4343525 | Apr 12, 2022 | MT | Tow-Away | 0 | 0 |
| cr_4287432 | Jan 5, 2022 | MT | Tow-Away | 0 | 0 |
Carrier booking & risk tools
Check booking and risk signals for USDOT 3563906 — tools open pre-filled.
Related records
Vehicle
2020 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
26V583000
SERVICE BRAKES, AIR:ANTILOCK
Recall
23V299000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V208000
EXTERIOR LIGHTING
Carrier
TIGER TRUCKING LLC
USDOT 3563906 · 10 crashes · 0 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJHHDR7LLLN1827
Decode this VIN for make, model, year, and recall data.
State
Crashes in Oregon
Statewide crash records.
Agency
TIGER TRUCKING LLC
Crashes reported by this law-enforcement agency.
City
Crashes in 9.72 N LONG CREEK, 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.