Skip to main content
TruckCodex
Hubs

Crash Record NC0106802697

FMCSA crash record in LEXINGTON on Dec 13, 2021.

Injury Federal Recordable

What happened

On December 13, 2021, FMCSA recorded an injury crash with one person hurt in LEXINGTON, North Carolina. The vehicle was operated by KAG DRY BULK LLC (USDOT 3598268). Recorded conditions: 2 / 1 / 1 pavement. Reported by XCEL BULK LOGISTICS LLC, FMCSA reference NC0106802697.

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: 92 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
USDOT 3598268
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
3 injury · 4 tow-away
Crashes per 100 power units (24 mo)
1.9
5 crashes · 261 units
Days since prior carrier crash
6
Last on Dec 7, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,059 carriers

Geographic context

How this crash sits in its setting.

Within LEXINGTON, North Carolina, 92 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
2
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 #:
NC0106802697
Date:
Dec 13, 2021
Time:
2143
City:
LEXINGTON
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
KAG DRY BULK LLC (3598268)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 4 1XPBDP9X3JD484034 NS1956 (NC) XCEL BULK LOGISTICS 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 Fatalities Injuries
cr_5117098 Feb 25, 2026 TX Injury 0 2
cr_5044626 Sep 24, 2025 VA Tow-Away 0 0
cr_5062035 Jun 30, 2025 NC Injury 0 1
cr_4920484 Apr 1, 2025 AR Tow-Away 0 0
cr_4832486 Oct 25, 2024 SC Tow-Away 0 0
cr_4747488 May 1, 2024 NC Tow-Away 0 0
cr_4663265 Nov 6, 2023 MS Tow-Away 0 0
cr_4574486 May 17, 2023 GA Tow-Away 0 0
cr_4471196 Dec 2, 2022 SC Injury 0 1
cr_4434495 Oct 14, 2022 NC Injury 0 1

Carrier booking & risk tools

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

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.