Skip to main content
TruckCodex
Hubs

Crash Record MS9055230005

FMCSA crash record in PEARL RIVER on Jun 5, 2023.

Injury Federal Recordable

What happened

On June 5, 2023, FMCSA recorded an injury crash with one person hurt in PEARL RIVER, Mississippi. The vehicle was operated by DENMAN TRUCKING L L C (USDOT 659942). Recorded conditions: 1 / 2 / 2 pavement. Reported by DENMAN TRUCKING L L C, FMCSA reference MS9055230005.

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
DENMAN TRUCKING L L C
USDOT 659942
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)
0.0
0 crashes · 8 units
Days since prior carrier crash
1,136
Last on Apr 25, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,733 carriers

Geographic context

How this crash sits in its setting.

Within PEARL RIVER, Mississippi, 28 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
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 #:
MS9055230005
Date:
Jun 5, 2023
Time:
1617
State:
Mississippi
City:
PEARL RIVER
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
DENMAN TRUCKING L L C (659942)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 6 1XKWD49X4CJ330961 A490983 (MS) DENMAN TRUCKING L L C 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4739167 Apr 26, 2024 LA Tow-Away 0 0
cr_3965675 Apr 25, 2020 LA Tow-Away 0 0
cr_1954580 Mar 7, 2008 LA Tow-Away 0 0
cr_1739166 Jul 26, 2006 LA Fatal 1 0
cr_1422416 Jan 18, 2005 AL Injury 0 1
cr_1216390 Nov 24, 2003 FL Tow-Away 0 0
cr_1116277 Jan 20, 2003 LA Tow-Away 0 0
cr_433950 Jul 11, 2002 AL Tow-Away 0 0
cr_306984 Dec 5, 2001 GA Fatal 1 0
cr_313998 Oct 10, 2001 MS Injury 0 2

Carrier booking & risk tools

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

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

Related records

Carrier
DENMAN TRUCKING L L C
USDOT 659942 · 11 crashes · 20 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1XKWD49X4CJ330961
Decode this VIN for make, model, year, and recall data.
State
Crashes in Mississippi
Statewide crash records.
Agency
DENMAN TRUCKING L L C
Crashes reported by this law-enforcement agency.
City
Crashes in PEARL RIVER, MS
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.