Crash Record IN0904239533

FMCSA crash record in RENSSELAER on Mar 12, 2023.

Tow-Away Federal Recordable

What happened

On March 12, 2023, FMCSA recorded a tow-away crash with no reported injuries in RENSSELAER, Indiana. The vehicle was operated by FREIGHT ONE ENTERPRISES LLC (USDOT 3520205). Recorded conditions: 2 / 4 / 2 pavement. Reported by FREIGHT ONE ENTERPRISES LLC, FMCSA reference IN0904239533.

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: 44 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

FREIGHT ONE ENTERPRISES LLC

USDOT 3520205

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 4 injury

Crashes per 100 power units (24 mo)

8.9

4 crashes · 45 units

Days since prior carrier crash

164

Last on Sep 29, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 315,143 carriers

Geographic context

How this crash sits in its setting.

Within RENSSELAER, Indiana, 44 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 2 reports
C D K EXPRESS LLC · 1 reports
BH TRANS INC · 1 reports

Contributing factors

What the responding officer recorded.

Light: 2
Weather: 4
Road surface: 2

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 #:: IN0904239533
Date:: Mar 12, 2023
Time:: 0440
State:: Indiana
City:: RENSSELAER
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: FREIGHT ONE ENTERPRISES LLC (3520205)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	3AKJGLD52GSGU6513	P1035350 (IL)	FREIGHT ONE ENTERPRISES LLC	3	No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5103520	Feb 7, 2026	AL	Injury	1
cr_5031614	Sep 19, 2025	TN	Injury	1
cr_4916620	Mar 14, 2025	OH	Tow-Away	0
cr_4886781	Jan 6, 2025	GA	Injury	3
cr_4785351	Jul 30, 2024	NE	Tow-Away	0
cr_4779762	Jun 25, 2024	GA	Tow-Away	0
cr_4768425	Jun 20, 2024	SC	Injury	2
cr_4750966	May 3, 2024	FL	Tow-Away	0
cr_4741259	Mar 27, 2024	IN	Tow-Away	0
cr_4693894	Jan 16, 2024	CT	Tow-Away	0

Carrier booking & risk tools

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

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

Related records

Vehicle

2016 FREIGHTLINER Cascadia

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

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Recall

19V093000

STEERING:LINKAGES:TIE ROD ASSEMBLY

Carrier

FREIGHT ONE ENTERPRISES LLC

USDOT 3520205 · 18 crashes · 279 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKJGLD52GSGU6513

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

State

Crashes in Indiana

Statewide crash records.

Agency

FREIGHT ONE ENTERPRISES LLC

Crashes reported by this law-enforcement agency.

City

Crashes in RENSSELAER, IN

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.