Crash Record NC0107146330

FMCSA crash record in ASHEVILLE on Nov 12, 2022.

Tow-Away Federal Recordable

What happened

On November 12, 2022, FMCSA recorded a tow-away crash with no reported injuries in ASHEVILLE, North Carolina. The vehicle was operated by BEACON TRANSPORT LLC (USDOT 874051). Recorded conditions: 1 / 1 / 1 pavement. Reported by BEACON TRANSPORT LLC, FMCSA reference NC0107146330.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

BEACON TRANSPORT LLC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

10 injury · 21 tow-away

Crashes per 100 power units (24 mo)

8.3

11 crashes · 133 units

Days since prior carrier crash

Last on Nov 9, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,858 carriers

Geographic context

How this crash sits in its setting.

Within ASHEVILLE, North Carolina, 222 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

BUNCOMBE COUNTY BOARD OF EDUCATION · 2 reports
CITY OF ASHEVILLE · 2 reports
CONSOLIDATED WASTE SERVICES LLC · 2 reports

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 #:: NC0107146330
Date:: Nov 12, 2022
Time:: 0756
State:: North Carolina
City:: ASHEVILLE
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: BEACON TRANSPORT LLC (874051)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	4V4NC9EG7LN252010	K4070HY (TN)	BEACON TRANSPORT 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	Injuries
cr_5079942	Dec 21, 2025	LA	Injury	2
cr_5079195	Dec 11, 2025	SC	Tow-Away	0
cr_5009892	Jul 24, 2025	TN	Tow-Away	0
cr_5016840	Jun 12, 2025	MO	Tow-Away	0
cr_4952592	May 31, 2025	NC	Injury	1
cr_4932799	Apr 15, 2025	NC	Tow-Away	0
cr_4912069	Feb 16, 2025	IN	Injury	1
cr_4881437	Jan 3, 2025	GA	Tow-Away	0
cr_4860260	Dec 15, 2024	TN	Tow-Away	0
cr_4855360	Nov 20, 2024	GA	Tow-Away	0

Related records

Carrier

BEACON TRANSPORT LLC

USDOT 874051 · 198 crashes · 404 inspections

Vehicle

VIN: 4V4NC9EG7LN252010

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

State

Crashes in North Carolina

Statewide crash records.

Agency

BEACON TRANSPORT LLC

Crashes reported by this law-enforcement agency.

City

Crashes in ASHEVILLE, 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.