Crash Record SD0202305824

FMCSA crash record in Rural on Mar 17, 2023.

Tow-Away Federal Recordable

What happened

On March 17, 2023, FMCSA recorded a tow-away crash with no reported injuries in Rural, South Dakota. The vehicle was operated by LION CARGO INC (USDOT 3478882). Recorded conditions: 1 / 6 / 6 pavement. FMCSA reference SD0202305824.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
3
Carrier
LION CARGO INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
2
0 injury · 2 tow-away
Crashes per 100 power units (24 mo)
5.0
3 crashes · 60 units
Days since prior carrier crash
69
Last on Jan 7, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within Rural, South Dakota, 625 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
6
Road surface
6

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 #:
SD0202305824
Date:
Mar 17, 2023
Time:
1630
State:
South Dakota
City:
Rural
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
LION CARGO INC (3478882)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 5KJJBHDR8NLNC1719 PWN9035 (OH) LION CARGO INC 3 No

Other crashes by this carrier

5 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5118785 Mar 3, 2026 OH Tow-Away 0 0
cr_5099883 Jan 25, 2026 OK Tow-Away 0 0
cr_5105299 Jan 24, 2026 MO Tow-Away 0 0
cr_4688426 Jan 17, 2024 PA Injury 0 1
cr_4491712 Jan 7, 2023 NE Tow-Away 0 0

Related records

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.