Crash Record SC0025248219

FMCSA crash record in SANDY RUN on Jun 9, 2025.

Tow-Away Federal Recordable

What happened

On June 9, 2025, FMCSA recorded a tow-away crash with no reported injuries in SANDY RUN, South Carolina. The vehicle was operated by STAY ALERT SAFETY SERVICES LLC (USDOT 1370638). Recorded conditions: 1 / 1 / 1 pavement. Reported by STAY ALERT SAFETY SERVICES LLC, FMCSA reference SC0025248219.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

STAY ALERT SAFETY SERVICES LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 2 injury

Crashes per 100 power units (24 mo)

3.7

4 crashes · 109 units

Days since prior carrier crash

272

Last on Sep 10, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,004 carriers

Geographic context

How this crash sits in its setting.

Within SANDY RUN, South Carolina, 34 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

SENN BROTHERS INC · 2 reports
COLA TOWING LLC · 1 reports
CARCO RENTALS INC · 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 #:: SC0025248219
Date:: Jun 9, 2025
Time:: 0710
State:: South Carolina
City:: SANDY RUN
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: STAY ALERT SAFETY SERVICES LLC (1370638)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	98	3C63R3AL2PG563173	P906635 (SC)	STAY ALERT SAFETY SERVICES LLC	2	No

Crash event

Event sequence description.

1:11:NONCOLLISION:UNKNOWN

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_5113516	Feb 18, 2026	SC	Injury	0	2
cr_5030030	Aug 28, 2025	SC	Injury	0	1
cr_5008406	Jun 30, 2025	SC	Injury	0	2
cr_4820550	Sep 10, 2024	SC	Injury	0	2
cr_4768386	Jun 18, 2024	SC	Fatal	1	1
cr_4589651	Jul 14, 2023	SC	Tow-Away	0	0
cr_3842626	Aug 13, 2019	NC	Injury	0	2
cr_3674487	Oct 18, 2018	NC	Injury	0	1
cr_3200415	Apr 5, 2016	VA	Tow-Away	0	0
cr_2731393	Feb 22, 2013	SC	Injury	0	1

Related records

Vehicle

2023 RAM 3500

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

AIR BAGS:FRONTAL:DRIVER CLOCKSPRING/SPIRAL CASSETTE

Carrier

STAY ALERT SAFETY SERVICES LLC

USDOT 1370638 · 23 crashes · 0 inspections

Vehicle

VIN: 3C63R3AL2PG563173

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

State

Crashes in South Carolina

Statewide crash records.

Agency

STAY ALERT SAFETY SERVICES LLC

Crashes reported by this law-enforcement agency.

City

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