TruckCodex
Hubs

Crash Record NC0107240854

FMCSA crash record in ASHEVILLE on Feb 7, 2023.

Tow-Away Federal Recordable

What happened

On February 7, 2023, FMCSA recorded a tow-away crash with no reported injuries in ASHEVILLE, North Carolina. The vehicle was operated by SOUTHEAST AMALGAMATED INC (USDOT 1550128). Recorded conditions: 1 / 1 / 1 pavement. Reported by SOUTHEAST AMALGAMATED INC, FMCSA reference NC0107240854.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
SOUTHEAST AMALGAMATED INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
2 injury · 6 tow-away
Crashes per 100 power units (24 mo)
3.6
1 crashes · 28 units
Days since prior carrier crash
47
Last on Dec 22, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,259 carriers

Geographic context

How this crash sits in its setting.

Within ASHEVILLE, North Carolina, 226 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 #:
NC0107240854
Date:
Feb 7, 2023
Time:
1648
State:
North Carolina
City:
ASHEVILLE
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SOUTHEAST AMALGAMATED INC (1550128)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 4 1XP5DB9X86N888562 NE8401 (NC) SOUTHEAST AMALGAMATED INC 3 Yes

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_5008390 Jul 9, 2025 SC Tow-Away 0 0
cr_4612980 Aug 29, 2023 NC Injury 0 3
cr_4595715 Jul 13, 2023 NC Injury 0 1
cr_4579573 Jun 21, 2023 NC Injury 0 1
cr_4479065 Dec 22, 2022 SC Injury 0 1
cr_4331879 Mar 25, 2022 SC Tow-Away 0 0
cr_4282200 Jan 5, 2022 NC Tow-Away 0 0
cr_4278247 Jan 2, 2022 NC Injury 0 1
cr_4205473 Aug 20, 2021 NC Tow-Away 0 0
cr_4049409 Oct 21, 2020 NC Injury 0 1

Related records

Carrier
SOUTHEAST AMALGAMATED INC
USDOT 1550128 · 21 crashes · 48 inspections
Vehicle
VIN: 1XP5DB9X86N888562
Decode this VIN for make, model, year, and recall data.
State
Crashes in North Carolina
Statewide crash records.
Agency
SOUTHEAST AMALGAMATED INC
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.