Skip to main content
TruckCodex
Hubs

Crash Record NC0106813518

FMCSA crash record in ASHEVILLE on Dec 23, 2021.

Tow-Away Federal Recordable

What happened

On December 23, 2021, FMCSA recorded a tow-away crash with no reported injuries in ASHEVILLE, North Carolina. The vehicle was operated by RYDER TRUCK RENTAL INC (USDOT 16130). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference NC0106813518.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
RYDER TRUCK RENTAL INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1,042
20 fatal · 343 injury
Crashes per 100 power units (24 mo)
0.8
476 crashes · 59,883 units
Days since prior carrier crash
1
Last on Dec 22, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,855 carriers

Geographic context

How this crash sits in its setting.

Within ASHEVILLE, North Carolina, 220 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 #:
NC0106813518
Date:
Dec 23, 2021
Time:
1125
State:
North Carolina
City:
ASHEVILLE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
RYDER TRUCK RENTAL INC (16130)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 5 3 3ALACWFB3KDKF7963 2737051 (IN) RYDER 2 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
cmtmftnq8003xpmdxxr9u6oxj Aug 28, 2026 KY Tow-Away 0 0
cmtgtnc070039pmmoquezm36b Aug 25, 2026 KY Tow-Away 0 0
cmtdwm2pe000tpmb992k41xik Aug 24, 2026 ME Tow-Away 0 0
cmsw88seq00fdpev3l5msjozt Aug 7, 2026 LA Tow-Away 0 0
cmsk9cqfz0011pefex7besfm5 Aug 3, 2026 AZ Injury 0 4
cmshdfe97000rpefy2d4n5a59 Jul 31, 2026 MN Tow-Away 0 0
cms76vgq0001hpehvw5mbaqdo Jul 23, 2026 IA Injury 0 1
cms76vgsd003ppehv9vwvd2jt Jul 23, 2026 NC Tow-Away 0 0
cmrfwlwhx000vmlhr78ktz2jb Jul 6, 2026 NC Injury 0 1
cmqkg77ry000tp8fyxlpqfiip Jun 15, 2026 ME Tow-Away 0 0

Related records

Carrier
RYDER TRUCK RENTAL INC
USDOT 16130 · 10,330 crashes · 4,458 inspections
Vehicle
VIN: 3ALACWFB3KDKF7963
Decode this VIN for make, model, year, and recall data.
State
Crashes in North Carolina
Statewide crash records.
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.