Crash Record SC0022268281

FMCSA crash record in SIMPSONVILLE on Aug 26, 2022.

Tow-Away Federal Recordable

What happened

On August 26, 2022, FMCSA recorded a tow-away crash with no reported injuries in SIMPSONVILLE, South Carolina. The vehicle was operated by PODS ENTERPRISES LLC (USDOT 1397252). Recorded conditions: 1 / 1 / 1 pavement. Reported by PODS ENTERPRISES LLC, FMCSA reference SC0022268281.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

PODS ENTERPRISES LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 fatal · 18 injury

Crashes per 100 power units (24 mo)

2.6

34 crashes · 1,324 units

Days since prior carrier crash

Last on Aug 9, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within SIMPSONVILLE, South Carolina, 38 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

DAVENPORT TRANSPORTATION INC · 2 reports
APPLE MOVING · 1 reports
ANCORA EDUCATION MILLER-MOTTE DRIVING INSTITUTE · 1 reports

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 #:: SC0022268281
Date:: Aug 26, 2022
Time:: 1225
State:: South Carolina
City:: SIMPSONVILLE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: PODS ENTERPRISES LLC (1397252)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	5	3HAEUMMN4LL702865	2985336 (IN)	PODS ENTERPRISES LLC	3	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	Injuries
cmrx2ea5v003bpequyo701b1t	Jul 15, 2026	NJ	Tow-Away	0
cmq1vv02f002lpbjq5uycdapt	Jun 1, 2026	NC	Tow-Away	0
cr_5122514	Feb 2, 2026	CT	Tow-Away	0
cr_5092334	Jan 20, 2026	NV	Tow-Away	0
cr_5074912	Nov 20, 2025	IL	Injury	1
cr_5063412	Nov 11, 2025	NC	Tow-Away	0
cr_5070121	Nov 11, 2025	NM	Tow-Away	0
cr_5059618	Oct 28, 2025	CO	Tow-Away	0
cr_5051180	Oct 11, 2025	GA	Injury	1
cr_5038350	Sep 23, 2025	IL	Tow-Away	0

Related records

Vehicle

2020 INTERNATIONAL MV607

NHTSA recalls and complaints for this make/model/year.

Carrier

PODS ENTERPRISES LLC

USDOT 1397252 · 231 crashes · 1,416 inspections

Vehicle

VIN: 3HAEUMMN4LL702865

Decode this VIN for make, model, year, and recall data.

State

Crashes in South Carolina

Statewide crash records.

Agency

PODS ENTERPRISES LLC

Crashes reported by this law-enforcement agency.

City

Crashes in SIMPSONVILLE, 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.