Skip to main content
TruckCodex
Hubs

Crash Record AL0003675774

FMCSA crash record in RURAL MARION on Jul 14, 2023.

Tow-Away Federal Recordable

What happened

On July 14, 2023, FMCSA recorded a tow-away crash with no reported injuries in RURAL MARION, Alabama. The vehicle was operated by DM EXPRESS INC (USDOT 2443340). Recorded conditions: 3 / 5 / 1 pavement. Reported by DM EXPRESS INC, FMCSA reference AL0003675774.

Carrier pattern note

This is the carrier's 14 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 1–5 power units.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
DM EXPRESS INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
14
1 fatal · 5 injury
Crashes per 100 power units (24 mo)
0.0
0 crashes · 1 units
Days since prior carrier crash
41
Last on Jun 3, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,566,280 carriers

Geographic context

How this crash sits in its setting.

Within RURAL MARION, Alabama, 36 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
5
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 #:
AL0003675774
Date:
Jul 14, 2023
Time:
0425
State:
Alabama
City:
RURAL MARION
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
DM EXPRESS INC (2443340)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJGLDR9HSJA2443 3037025 (IN) DM EXPRESS INC 3 No

Crash event

Event sequence description.

4:18:COLLISION INVOLVING FIXED OBJECT;2:6:NONCOLLISION:EXPLOSION OR FIRE;3:11:NONCOLLISION:UNKNOWN

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4667095 Nov 30, 2023 PA Tow-Away 0 0
cr_4642167 Oct 18, 2023 TN Tow-Away 0 0
cr_4599621 Aug 3, 2023 TN Tow-Away 0 0
cr_4569811 Jun 3, 2023 NY Injury 0 1
cr_4537951 Apr 3, 2023 NC Injury 0 1
cr_4534555 Mar 21, 2023 IN Tow-Away 0 0
cr_4483184 Dec 30, 2022 TN Tow-Away 0 0
cr_4475234 Nov 18, 2022 IN Tow-Away 0 0
cr_4475236 Nov 18, 2022 IN Tow-Away 0 0
cr_4462572 Nov 9, 2022 MI Tow-Away 0 0

Related records

Vehicle
2017 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V817000
FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL
Recall
20V567000
EXTERIOR LIGHTING:BRAKE LIGHTS
Carrier
DM EXPRESS INC
USDOT 2443340 · 44 crashes · 93 inspections
Vehicle
VIN: 3AKJGLDR9HSJA2443
Decode this VIN for make, model, year, and recall data.
State
Crashes in Alabama
Statewide crash records.
Agency
DM EXPRESS INC
Crashes reported by this law-enforcement agency.
City
Crashes in RURAL MARION, 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.