TruckCodex
Hubs

Crash Record LA2025097023

FMCSA crash record in BATON ROUGE on Jul 19, 2025.

Tow-Away Federal Recordable

What happened

On July 19, 2025, FMCSA recorded a tow-away crash with no reported injuries in BATON ROUGE, Louisiana. The vehicle was operated by KENNETH M D'ARENSBOURG (USDOT 661001). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference LA2025097023.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
KENNETH M D'ARENSBOURG
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
100.0
1 crashes · 1 units
Days since prior carrier crash
1,193
Last on Apr 13, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,554,615 carriers

Geographic context

How this crash sits in its setting.

Within BATON ROUGE, Louisiana, 378 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 #:
LA2025097023
Date:
Jul 19, 2025
Time:
1235
State:
Louisiana
City:
BATON ROUGE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
KENNETH M D'ARENSBOURG (661001)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
3 5 12 1FVXJLBB4VL743007 J047061 (LA) KENNETH M D'ARENSBOURG 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

3 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4350809 Apr 13, 2022 LA Injury 0 5
cr_3313706 Nov 10, 2016 LA Tow-Away 0 0
cr_3075176 Jul 15, 2015 LA Tow-Away 0 0

Related records

Vehicle
2027 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Carrier
KENNETH M D'ARENSBOURG
USDOT 661001 · 4 crashes · 0 inspections
Vehicle
VIN: 1FVXJLBB4VL743007
Decode this VIN for make, model, year, and recall data.
State
Crashes in Louisiana
Statewide crash records.
City
Crashes in BATON ROUGE, LA
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.