Crash Record MO0000112404

FMCSA crash record in ST LOUIS on Nov 15, 2024.

Injury Federal Recordable

What happened

On November 15, 2024, FMCSA recorded an injury crash with one person hurt in ST LOUIS, Missouri. The vehicle was operated by TITAN TOWING LLC (USDOT 3961759). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference MO0000112404.

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

TITAN TOWING LLC

USDOT 3961759

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 0 tow-away

Crashes per 100 power units (24 mo)

28.6

2 crashes · 7 units

Prior carrier crash

—

No earlier crash on file

Vs fleet-size peers

above the median

Cohort median 0.0 · 315,143 carriers

Geographic context

How this crash sits in its setting.

Within ST LOUIS, Missouri, 365 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

METRO TRANSIT · 10 reports
CITY OF ST LOUIS · 6 reports
FIRST STUDENT INC · 4 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 #:: MO0000112404
Date:: Nov 15, 2024
Time:: 0858
State:: Missouri
City:: ST LOUIS
Fatalities:: 0
Injuries:: 1
Tow-Away:: No
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: TITAN TOWING LLC (3961759)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	5	98	3C7WRMDL9GD595947	55J1JB (MO)	TITAN TOWING LLC	2	No

Crash event

Event sequence description.

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

Other crashes by this carrier

1 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_5081372	Dec 23, 2025	MO	Tow-Away	0	0

Carrier booking & risk tools

Check booking and risk signals for USDOT 3961759 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle

2016 RAM 5500

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

Recall

21V398000

WHEELS:LUGS/NUTS/BOLTS/STUDS

Recall

19V018000

AIR BAGS:FRONTAL:PASSENGER SIDE:INFLATOR MODULE

Recall

18V332000

ELECTRICAL SYSTEM:SOFTWARE

Carrier

TITAN TOWING LLC

USDOT 3961759 · 2 crashes · 2 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3C7WRMDL9GD595947

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

State

Crashes in Missouri

Statewide crash records.

City

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