Skip to main content
TruckCodex
Hubs

Crash Record LA2023060128

FMCSA crash record in LAKE CHARLES on May 24, 2023.

Tow-Away Federal Recordable

What happened

On May 24, 2023, FMCSA recorded a tow-away crash with no reported injuries in LAKE CHARLES, Louisiana. The vehicle was operated by SAIA MOTOR FREIGHT LINE LLC (USDOT 29124). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference LA2023060128.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
USDOT 29124
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
369
10 fatal · 110 injury
Crashes per 100 power units (24 mo)
3.7
278 crashes · 7,428 units
Days since prior carrier crash
1
Last on May 23, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,901 carriers

Geographic context

How this crash sits in its setting.

Within LAKE CHARLES, Louisiana, 90 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 #:
LA2023060128
Date:
May 24, 2023
Time:
0822
State:
Louisiana
City:
LAKE CHARLES
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 8 12 1FUBHSDV5LLLE2022 P254705 (LA) SAIA MOTOR FREIGHT LINE LLC 3 No

Crash event

Event sequence description.

2:98:OTHER;1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;4:98:OTHER;3:98:OTHER

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmvettr0900uzogssbco3dt9m Oct 7, 2026 TX Tow-Away 0 0
cmuz83joi001hogz66bujhfk8 Oct 2, 2026 OH Tow-Away 0 0
cmsw88sfb00gnpev3c7sg253a Aug 7, 2026 NJ Injury 0 1
cmsmuqxy60011pexo5d77blqu Aug 5, 2026 NC Tow-Away 0 0
cmroiq0z90007pemcmix3svep Jul 13, 2026 MN Injury 0 1
cmrir6e95001vpeyzrasz2j0n Jul 6, 2026 NC Tow-Away 0 0
cmqkg77zo006vp8fyef8zaf0m Jun 11, 2026 NC Injury 0 5
cmq0fazbn0017pmw8m4x8v5iu May 28, 2026 MI Injury 0 1
cmpw5noje0007mot333wqe1vo May 28, 2026 NC Tow-Away 0 0
cmpezcvdp008vpj798emlwx7w May 13, 2026 OH Tow-Away 0 0

Carrier booking & risk tools

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

Related records

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.