Skip to main content
TruckCodex
Hubs

Crash Record SC0025515169

FMCSA crash record in NORTH CHARLESTON on Mar 21, 2025.

Tow-Away Federal Recordable

What happened

On March 21, 2025, FMCSA recorded a tow-away crash with no reported injuries in NORTH CHARLESTON, South Carolina. The vehicle was operated by EAN HOLDINGS LLC (USDOT 1499091). Recorded conditions: 1 / 1 / 1 pavement. Reported by EAN HOLDINGS LLC, FMCSA reference SC0025515169.

Carrier pattern note

This is the carrier's 61 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: 178 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
EAN HOLDINGS LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
61
2 fatal · 22 injury
Crashes per 100 power units (24 mo)
0.6
45 crashes · 6,993 units
Days since prior carrier crash
1
Last on Mar 20, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,855 carriers

Geographic context

How this crash sits in its setting.

Within NORTH CHARLESTON, South Carolina, 178 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 #:
SC0025515169
Date:
Mar 21, 2025
Time:
0738
State:
South Carolina
City:
NORTH CHARLESTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
EAN HOLDINGS LLC (1499091)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 3ALACWFC4PDUK2262 XST572 (GA) EAN HOLDINGS LLC 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmtch5ocw000rpmuca4837fu8 Aug 21, 2026 OH Tow-Away 0 0
cms76vgpp000zpehv86j9i0gj Jul 24, 2026 NC Tow-Away 0 0
cmrn1fc89001vpez5tzhzmeo5 Jul 9, 2026 OH Injury 0 1
cmr5veuz30029p8npyyzzjswi Jun 29, 2026 AR Tow-Away 0 0
cmqyq8pog0045p8arcuqi6pyi Jun 24, 2026 NJ Tow-Away 0 0
cmqvwanqy0017p8iu6xt0ixuw Jun 22, 2026 OK Injury 0 1
cmny3yfrc004zk38ve2qfo4jl Apr 6, 2026 MA Tow-Away 0 0
cr_5123491 Mar 20, 2026 KY Tow-Away 0 0
cr_5124563 Mar 11, 2026 PA Injury 0 1
cr_5118474 Mar 4, 2026 PA Tow-Away 0 0

Related records

Vehicle
2023 FREIGHTLINER M2
NHTSA recalls and complaints for this make/model/year.
Recall
23V537000
POWER TRAIN:DRIVELINE:DRIVESHAFT
Recall
23V238000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
EAN HOLDINGS LLC
USDOT 1499091 · 468 crashes · 232 inspections
Vehicle
VIN: 3ALACWFC4PDUK2262
Decode this VIN for make, model, year, and recall data.
State
Crashes in South Carolina
Statewide crash records.
Agency
EAN HOLDINGS LLC
Crashes reported by this law-enforcement agency.
City
Crashes in NORTH CHARLESTON, SC
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.