Crash Record GA0009052044

FMCSA crash record in UNINCORPORATED on Jun 23, 2023.

Tow-Away Federal Recordable

What happened

On June 23, 2023, FMCSA recorded a tow-away crash with no reported injuries in UNINCORPORATED, Georgia. The vehicle was operated by KINGS MOUNTAIN NATIONAL CARRIERS INC (USDOT 2361976). Recorded conditions: 2 / 1 pavement. Reported by KINGS MOUNTAIN NATIONAL CARRIERS INC, FMCSA reference GA0009052044.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

KINGS MOUNTAIN NATIONAL CARRIERS INC

USDOT 2361976

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 fatal · 3 injury

Crashes per 100 power units (24 mo)

100.0

1 crashes · 1 units

Days since prior carrier crash

Last on Jun 3, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,569,882 carriers

Geographic context

How this crash sits in its setting.

Within UNINCORPORATED, Georgia, 879 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

MARTA · 23 reports
FEDERAL EXPRESS CORPORATION · 11 reports
DEKALB COUNTY BOARD OF EDUCATION · 9 reports

Contributing factors

What the responding officer recorded.

Light: 2
Weather: —
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 #:: GA0009052044
Date:: Jun 23, 2023
Time:: 0110
State:: Georgia
City:: UNINCORPORATED
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: KINGS MOUNTAIN NATIONAL CARRIERS INC (2361976)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	98	1XKYDP9X4PJ246123	3372943 (IN)	KINGS MOUNTAIN NATIONAL CARRIERS 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	Fatalities	Injuries
cr_4853280	Nov 11, 2024	CT	Tow-Away	0	0
cr_4770410	Jun 29, 2024	MA	Tow-Away	0	0
cr_4837091	May 6, 2024	NM	Fatal	1	0
cr_4763325	May 5, 2024	GA	Tow-Away	0	0
cr_4746551	Apr 26, 2024	MO	Tow-Away	0	0
cr_4710847	Mar 5, 2024	AZ	Tow-Away	0	0
cr_4703025	Feb 25, 2024	TN	Tow-Away	0	0
cr_4708712	Feb 15, 2024	FL	Injury	0	2
cr_4692266	Jan 21, 2024	PA	Tow-Away	0	0
cr_4694831	Jan 14, 2024	MA	Injury	0	1

Carrier booking & risk tools

Check booking and risk signals for USDOT 2361976 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle

2023 KENWORTH T680

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

POWER TRAIN:AUTOMATIC TRANSMISSION:LEVER AND LINKAGE:COLUMN SHIFT

Carrier

KINGS MOUNTAIN NATIONAL CARRIERS INC

USDOT 2361976 · 41 crashes · 0 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XKYDP9X4PJ246123

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

State

Crashes in Georgia

Statewide crash records.

Agency

KINGS MOUNTAIN NATIONAL CARRIERS INC

Crashes reported by this law-enforcement agency.

City

Crashes in UNINCORPORATED, GA

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.