Skip to main content
TruckCodex
Hubs

Crash Record MI0003312704

FMCSA crash record in DETROIT on Oct 9, 2024.

Tow-Away Federal Recordable

What happened

On October 9, 2024, FMCSA recorded a tow-away crash with no reported injuries in DETROIT, Michigan. The vehicle was operated by WARNER BROTHERS SERVICES INC (USDOT 1655717). Recorded conditions: 1 / 1 / 1 pavement. Reported by WARNER BROTHERS SERVICES INC, FMCSA reference MI0003312704.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
WARNER BROTHERS SERVICES INC
USDOT 1655717
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 injury · 4 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 13 units
Days since prior carrier crash
162
Last on Apr 30, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,866 carriers

Geographic context

How this crash sits in its setting.

Within DETROIT, Michigan, 918 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
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 #:
MI0003312704
Date:
Oct 9, 2024
Time:
1130
State:
Michigan
City:
DETROIT
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
WARNER BROTHERS SERVICES INC (1655717)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 6 1NPXL40X1LD722240 BC49808 (MI) WARNER BROTHERS SERVICES INC 3 No

Crash event

Event sequence description.

1:11:NONCOLLISION:UNKNOWN

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4834495 Oct 22, 2024 MI Tow-Away 0 0
cr_4750369 Apr 30, 2024 MI Tow-Away 0 0
cr_4584198 Jun 28, 2023 MI Injury 0 2
cr_4539846 Mar 14, 2023 MI Tow-Away 0 0
cr_4409638 Aug 4, 2022 MI Tow-Away 0 0
cr_4395380 Jul 18, 2022 MI Injury 0 1
cr_4246081 Oct 4, 2021 MI Tow-Away 0 0
cr_3855648 Sep 19, 2019 MI Tow-Away 0 0
cr_3811496 Jun 8, 2019 MI Tow-Away 0 0
cr_3752110 Feb 16, 2019 MI Injury 0 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2020 PETERBILT 389
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V906000
ELECTRICAL SYSTEM:SOFTWARE
Recall
20V506000
POWER TRAIN:AXLE ASSEMBLY
Carrier
WARNER BROTHERS SERVICES INC
USDOT 1655717 · 12 crashes · 13 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1NPXL40X1LD722240
Decode this VIN for make, model, year, and recall data.
State
Crashes in Michigan
Statewide crash records.
Agency
WARNER BROTHERS SERVICES INC
Crashes reported by this law-enforcement agency.
City
Crashes in DETROIT, MI
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.