Crash Record NC0108010138

FMCSA crash record in DURHAM on Jan 29, 2025.

Tow-Away Federal Recordable

What happened

On January 29, 2025, FMCSA recorded a tow-away crash with no reported injuries in DURHAM, North Carolina. The vehicle was operated by SWING TRANSPORT INC (USDOT 142116). Recorded conditions: 1 / 1 / 1 pavement. Reported by SWING TRANSPORT INC, FMCSA reference NC0108010138.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

SWING TRANSPORT 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 injury · 13 tow-away

Crashes per 100 power units (24 mo)

7.5

12 crashes · 160 units

Days since prior carrier crash

Last on Jan 17, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,833 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

CITY OF DURHAM · 25 reports
DURHAM PUBLIC SCHOOL SYSTEM · 6 reports
RESEARCH TRIANGLE REGIONAL PUBLI · 5 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 #:: NC0108010138
Date:: Jan 29, 2025
Time:: 0728
State:: North Carolina
City:: DURHAM
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: SWING TRANSPORT INC (142116)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	7	3	1M1AN4GY6NM029107	MX4998 (NC)	SWING TRANSPORT 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	Injuries
cr_5090140	Jan 16, 2026	SC	Injury	1
cr_5081140	Dec 17, 2025	TN	Tow-Away	0
cr_5055734	Nov 5, 2025	NC	Tow-Away	0
cr_5091944	Aug 12, 2025	NC	Tow-Away	0
cr_5091495	Jul 24, 2025	NC	Injury	2
cr_5008857	Jun 20, 2025	SC	Tow-Away	0
cr_4950057	May 27, 2025	SC	Tow-Away	0
cr_4887010	Feb 3, 2025	TN	Tow-Away	0
cr_4889727	Jan 17, 2025	GA	Tow-Away	0
cr_4872602	Dec 12, 2024	GA	Tow-Away	0

Related records

Vehicle

2022 MACK Anthem

NHTSA recalls and complaints for this make/model/year.

Carrier

SWING TRANSPORT INC

USDOT 142116 · 223 crashes · 609 inspections

Vehicle

VIN: 1M1AN4GY6NM029107

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

State

Crashes in North Carolina

Statewide crash records.

Agency

SWING TRANSPORT INC

Crashes reported by this law-enforcement agency.

City

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