Skip to main content
TruckCodex
Hubs

Crash Record NC0108247877

FMCSA crash record in SHELBY on Aug 4, 2025.

Injury Federal Recordable

What happened

On August 4, 2025, FMCSA recorded an injury crash with one person hurt in SHELBY, North Carolina. The vehicle was operated by GILLTRANSPORT INC (USDOT 2906833). Recorded conditions: 1 / 1 / 1 pavement. Reported by GILLTRANSPORT INC, FMCSA reference NC0108247877.

Carrier pattern note

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

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

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
4 injury · 5 tow-away
Crashes per 100 power units (24 mo)
6.4
5 crashes · 78 units
Days since prior carrier crash
20
Last on Jul 15, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,354 carriers

Geographic context

How this crash sits in its setting.

Within SHELBY, North Carolina, 51 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
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 #:
NC0108247877
Date:
Aug 4, 2025
Time:
1011
City:
SHELBY
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
GILLTRANSPORT INC (2906833)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 3 3AKJHHDR6SSVS2487 — GILLTRANSPORT 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
cmpqehzbs00a1qiysves9o7rg May 20, 2026 PA Injury 0 1
cr_5087129 Dec 18, 2025 IN Tow-Away 0 0
cr_5000268 Jul 15, 2025 MD Tow-Away 0 0
cr_4955939 Jun 11, 2025 KY Injury 0 1
cr_4722852 Mar 23, 2024 NY Injury 0 1
cr_4932281 Jan 27, 2024 MD Tow-Away 0 0
cr_4682510 Dec 27, 2023 IN Injury 0 1
cr_4552540 May 2, 2023 NC Injury 0 1
cr_4452431 Nov 5, 2022 TN Tow-Away 0 0
cr_4411464 Aug 16, 2022 PA Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 2906833 — 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.