Crash Record IN0904274520

FMCSA crash record in INDIANAPOLIS on May 12, 2023.

Tow-Away Federal Recordable

What happened

On May 12, 2023, FMCSA recorded a tow-away crash with no reported injuries in INDIANAPOLIS, Indiana. The vehicle was operated by TRANSPORT N SERVICE INC (USDOT 844628). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference IN0904274520.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

TRANSPORT N SERVICE INC

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 7 tow-away

Crashes per 100 power units (24 mo)

1.2

1 crashes · 85 units

Days since prior carrier crash

Last on Feb 19, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,697 carriers

Geographic context

How this crash sits in its setting.

Within INDIANAPOLIS, Indiana, 1,678 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

UNKNOWN · 101 reports
INDY GO · 63 reports
FEDERAL EXPRESS CORPORATION · 16 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 #:: IN0904274520
Date:: May 12, 2023
Time:: 1346
State:: Indiana
City:: INDIANAPOLIS
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: TRANSPORT N SERVICE INC (844628)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
3	9	3	3AKJHHDR8NSNC9814	PA52786 (ON)	TRANSPORT N SERVICE 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_4818934	Sep 20, 2024	MI	Tow-Away	0
cr_4737113	Apr 5, 2024	UT	Injury	1
cr_4734518	Apr 1, 2024	MI	Tow-Away	0
cr_4513130	Feb 19, 2023	WY	Tow-Away	0
cr_4511273	Feb 16, 2023	KY	Tow-Away	0
cr_4513364	Feb 15, 2023	WV	Tow-Away	0
cr_4482186	Dec 31, 2022	NE	Injury	1
cr_4383339	Jul 5, 2022	SC	Tow-Away	0
cr_4263873	Nov 17, 2021	CA	Tow-Away	0
cr_4165986	Apr 5, 2021	IL	Tow-Away	0

Related records

Vehicle

2022 FREIGHTLINER Cascadia

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

Recall

23V299000

ELECTRONIC STABILITY CONTROL (ESC)

Recall

23V238000

STEERING:LINKAGES:TIE ROD ASSEMBLY

Recall

23V073000

ELECTRONIC STABILITY CONTROL (ESC)

Carrier

TRANSPORT N SERVICE INC

USDOT 844628 · 55 crashes · 0 inspections

Vehicle

VIN: 3AKJHHDR8NSNC9814

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

State

Crashes in Indiana

Statewide crash records.

City

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