Skip to main content
TruckCodex
Hubs

Crash Record AL0002617543

FMCSA crash record in RURAL ST. CLAIR on Feb 17, 2022.

Injury Federal Recordable

What happened

On February 17, 2022, FMCSA recorded an injury crash with one person hurt in RURAL ST. CLAIR, Alabama. The vehicle was operated by ORPHAN CREEK CATTLE LLC (USDOT 2898609). Recorded conditions: 3 / 2 / 2 pavement. Reported by ORPHAN CREEK CATTLE LLC, FMCSA reference AL0002617543.

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
3
Carrier
ORPHAN CREEK CATTLE LLC
USDOT 2898609
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 · 0 tow-away
Crashes per 100 power units (24 mo)
20.0
1 crashes · 5 units
Days since prior carrier crash
1,620
Last on Sep 11, 2017
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,574,305 carriers

Geographic context

How this crash sits in its setting.

Within RURAL ST. CLAIR, Alabama, 63 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
2
Road surface
2

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 #:
AL0002617543
Date:
Feb 17, 2022
Time:
1930
State:
Alabama
City:
RURAL ST. CLAIR
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
3
Carrier (USDOT):
ORPHAN CREEK CATTLE LLC (2898609)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XP5DB9X63N588479 A305416 (MS) ORPHAN CREEK CATTLE LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

3 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5012414 Jul 9, 2025 TX Tow-Away 0 0
cr_3459953 Sep 11, 2017 MS Tow-Away 0 0
cr_3390233 Apr 13, 2017 LA Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2003 PETERBILT 379
NHTSA recalls and complaints for this make/model/year.
Recall
07V044000
SERVICE BRAKES, AIR
Recall
03V410000
STEERING:LINKAGES:KNUCKLE:SPINDLE:ARM
Recall
03V343000
SERVICE BRAKES, AIR:SLACK ADJUSTERS
Carrier
ORPHAN CREEK CATTLE LLC
USDOT 2898609 · 4 crashes · 5 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XP5DB9X63N588479
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
Agency
ORPHAN CREEK CATTLE LLC
Crashes reported by this law-enforcement agency.
City
Crashes in RURAL ST. CLAIR, AL
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.