Crash Record MO0000109665

FMCSA crash record in SPRINGFIELD on Sep 6, 2024.

Tow-Away Federal Recordable

What happened

On September 6, 2024, FMCSA recorded a tow-away crash with no reported injuries in SPRINGFIELD, Missouri. The vehicle was operated by HC TRANSPORT INC (USDOT 726855). Recorded conditions: 1 / 1 / 1 pavement. Reported by HC TRANSPORT INC, FMCSA reference MO0000109665.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

HC 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)

2 fatal · 13 injury

Crashes per 100 power units (24 mo)

2.3

30 crashes · 1,297 units

Days since prior carrier crash

Last on Sep 3, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,838 carriers

Geographic context

How this crash sits in its setting.

Within SPRINGFIELD, Missouri, 197 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

CITY UTILITIES OF SPRINGFIELD · 4 reports
RPM RECOVERY LLC · 3 reports
PRIME INC · 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 #:: MO0000109665
Date:: Sep 6, 2024
Time:: 1608
State:: Missouri
City:: SPRINGFIELD
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: HC TRANSPORT INC (726855)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	5	3	1HTMMMML1GH458789	PWB8809 (OH)	HC TRANSPORT INC	2	No

Crash event

Event sequence description.

1:98:OTHER:OTHER;2:98:OTHER:OTHER;3:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5126225	Mar 25, 2026	AR	Tow-Away	0
cr_5120628	Feb 6, 2026	WV	Tow-Away	0
cr_5074788	Nov 14, 2025	IN	Tow-Away	0
cr_5067002	Nov 11, 2025	GA	Tow-Away	0
cr_5064325	Nov 4, 2025	MO	Tow-Away	0
cr_5049177	Oct 24, 2025	OH	Injury	1
cr_5049552	Oct 24, 2025	MO	Tow-Away	0
cr_5057819	Oct 12, 2025	IN	Tow-Away	0
cr_5047728	Oct 7, 2025	IL	Tow-Away	0
cr_5034254	Sep 25, 2025	TN	Tow-Away	0

Related records

Vehicle

2016 INTERNATIONAL MA025

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

Carrier

HC TRANSPORT INC

USDOT 726855 · 576 crashes · 931 inspections

Vehicle

VIN: 1HTMMMML1GH458789

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

State

Crashes in Missouri

Statewide crash records.

Agency

HC TRANSPORT INC

Crashes reported by this law-enforcement agency.

City

Crashes in SPRINGFIELD, MO

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.