TruckCodex
Hubs

Crash Record IN0904477175

FMCSA crash record in LOGANSPORT on Mar 25, 2024.

Tow-Away Federal Recordable

What happened

On March 25, 2024, FMCSA recorded a tow-away crash with no reported injuries in LOGANSPORT, Indiana. The vehicle was operated by GARDNER TRANSPORT SERVICES INC (USDOT 727828). Recorded conditions: 1 / 8 / 1 pavement. Reported by GARDNER TRANSPORT SERVICES INC, FMCSA reference IN0904477175.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
GARDNER TRANSPORT SERVICES 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
0 injury · 1 tow-away
Crashes per 100 power units (24 mo)
7.7
1 crashes · 13 units
Days since prior carrier crash
826
Last on Dec 20, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,424 carriers

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

Contributing factors

What the responding officer recorded.

Light
1
Weather
8
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 #:
IN0904477175
Date:
Mar 25, 2024
Time:
0825
State:
Indiana
City:
LOGANSPORT
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
GARDNER TRANSPORT SERVICES INC (727828)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1XP5D09X36D896840 404121 (IN) GARDNER TRANSPORT SERVICES INC 3 Yes

Crash event

Event sequence description.

3:17:COLLISION INVOLVING ANIMAL;2:98:OTHER:DITCH;1:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5046234 Sep 26, 2025 IN Tow-Away 0 0
cr_4776539 Jul 2, 2024 IN Tow-Away 0 0
cr_4317861 Dec 20, 2021 IN Tow-Away 0 0
cr_4161346 Apr 1, 2021 IL Injury 0 2
cr_4097920 Jan 14, 2021 IN Injury 0 2
cr_3848009 Sep 12, 2019 IN Tow-Away 0 0
cr_3699127 Nov 20, 2018 IN Tow-Away 0 0
cr_3631875 Jul 27, 2018 IN Tow-Away 0 0
cr_3548813 Feb 9, 2018 IL Tow-Away 0 0
cr_3257785 Jul 21, 2016 IN Tow-Away 0 0

Related records

Vehicle
2006 PETERBILT 379
NHTSA recalls and complaints for this make/model/year.
Recall
15V132000
EQUIPMENT:OTHER:LABELS
Recall
13V593000
EQUIPMENT:OTHER:LABELS
Recall
08V487000
ENGINE AND ENGINE COOLING:ENGINE:DIESEL
Carrier
GARDNER TRANSPORT SERVICES INC
USDOT 727828 · 16 crashes · 12 inspections
Vehicle
VIN: 1XP5D09X36D896840
Decode this VIN for make, model, year, and recall data.
State
Crashes in Indiana
Statewide crash records.
Agency
GARDNER TRANSPORT SERVICES INC
Crashes reported by this law-enforcement agency.
City
Crashes in LOGANSPORT, 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.