TruckCodex
Hubs

Crash Record NC0107721758

FMCSA crash record in COLUMBUS on May 17, 2024.

Tow-Away Federal Recordable

What happened

On May 17, 2024, FMCSA recorded a tow-away crash with no reported injuries in COLUMBUS, North Carolina. The vehicle was operated by BENORE LOGISTIC SYSTEMS INC (USDOT 1238256). Recorded conditions: 2 / 1 / 1 pavement. Reported by BENORE LOGISTIC SYSTEMS INC, FMCSA reference NC0107721758.

Carrier pattern note

This is the carrier's 59 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
BENORE LOGISTIC SYSTEMS INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
59
1 fatal · 21 injury
Crashes per 100 power units (24 mo)
4.0
25 crashes · 632 units
Days since prior carrier crash
1
Last on May 16, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,848 carriers

Geographic context

How this crash sits in its setting.

Within COLUMBUS, North Carolina, 29 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 #:
NC0107721758
Date:
May 17, 2024
Time:
0433
State:
North Carolina
City:
COLUMBUS
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BENORE LOGISTIC SYSTEMS INC (1238256)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 3 3HSDZAPR5RN278499 RC35517 (MI) BENORE LOGISTIC SYSTEMS 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_5113539 Feb 28, 2026 SC Tow-Away 0 0
cr_5113493 Feb 24, 2026 SC Injury 0 1
cr_5108891 Feb 12, 2026 SC Tow-Away 0 0
cr_5108196 Feb 12, 2026 VA Injury 0 1
cr_5066872 Nov 17, 2025 GA Tow-Away 0 0
cr_5062846 Nov 3, 2025 GA Injury 0 1
cr_5035895 Sep 11, 2025 SC Injury 0 1
cr_5029751 Sep 9, 2025 GA Tow-Away 0 0
cr_5009029 Aug 16, 2025 SC Tow-Away 0 0
cr_4988344 Aug 12, 2025 AL Tow-Away 0 0

Related records

Carrier
BENORE LOGISTIC SYSTEMS INC
USDOT 1238256 · 338 crashes · 1,009 inspections
Vehicle
VIN: 3HSDZAPR5RN278499
Decode this VIN for make, model, year, and recall data.
State
Crashes in North Carolina
Statewide crash records.
Agency
BENORE LOGISTIC SYSTEMS INC
Crashes reported by this law-enforcement agency.
City
Crashes in COLUMBUS, NC
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.