Crash Record SC0023219206

FMCSA crash record in SUMMERVILLE on Feb 23, 2023.

Injury Federal Recordable

What happened

On February 23, 2023, FMCSA recorded an injury crash with one person hurt in SUMMERVILLE, South Carolina. The vehicle was operated by LIGHTNING TRANSPORTATION INC (USDOT 326966). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference SC0023219206.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

LIGHTNING TRANSPORTATION INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 13 injury

Crashes per 100 power units (24 mo)

7.0

18 crashes · 256 units

Days since prior carrier crash

Last on Feb 20, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,004 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

PORT CITY CONCRETE INC · 5 reports
UNKNOWN · 4 reports
LANDMARK CONSTRUCTION COMPANY INC · 3 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 #:: SC0023219206
Date:: Feb 23, 2023
Time:: 0955
State:: South Carolina
City:: SUMMERVILLE
Fatalities:: 0
Injuries:: 1
Tow-Away:: No
HazMat:: No
Vehicles:: 4
Carrier (USDOT):: LIGHTNING TRANSPORTATION INC (326966)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	3AKJGLDR6HDHZ1062	P768257 (SC)	LIGHTNING TRANSPORTATION INC	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
cr_5117783	Mar 6, 2026	NC	Injury	1
cr_5121158	Mar 5, 2026	NC	Injury	2
cr_5074571	Dec 11, 2025	GA	Injury	2
cr_5071303	Nov 21, 2025	SC	Tow-Away	0
cr_5056373	Oct 29, 2025	VA	Tow-Away	0
cr_5047691	Oct 9, 2025	GA	Tow-Away	0
cr_5000348	Jul 9, 2025	MD	Tow-Away	0
cr_4999673	Jun 16, 2025	MD	Injury	1
cr_4993108	Jun 12, 2025	GA	Tow-Away	0
cr_4946544	May 21, 2025	SC	Injury	1

Related records

Carrier

LIGHTNING TRANSPORTATION INC

USDOT 326966 · 233 crashes · 593 inspections

Vehicle

VIN: 3AKJGLDR6HDHZ1062

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

State

Crashes in South Carolina

Statewide crash records.

City

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