Skip to main content
TruckCodex
Hubs

Crash Record OH0245217221

FMCSA crash record in TOWNSEND (TOWNSHIP OF) on Nov 19, 2024.

Tow-Away Federal Recordable

What happened

On November 19, 2024, FMCSA recorded a tow-away crash with no reported injuries in TOWNSEND (TOWNSHIP OF), Ohio. The vehicle was operated by A PARENT COMPANY LLC (USDOT 3365498). Recorded conditions: 5 / 1 / 2 pavement. Reported by A PARENT COMPANY LLC, FMCSA reference OH0245217221.

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
A PARENT COMPANY LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
0 injury · 3 tow-away
Crashes per 100 power units (24 mo)
12.5
3 crashes · 24 units
Days since prior carrier crash
151
Last on Jun 21, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,812 carriers

Geographic context

How this crash sits in its setting.

Within TOWNSEND (TOWNSHIP OF), Ohio, 26 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
5
Weather
1
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 #:
OH0245217221
Date:
Nov 19, 2024
Time:
1708
State:
Ohio
City:
TOWNSEND (TOWNSHIP OF)
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
A PARENT COMPANY LLC (3365498)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 8 1NPSLP9X6KD600003 PWR6937 (OH) A PARENT COMPANY LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

4 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5082584 Dec 9, 2025 MI Tow-Away 0 0
cr_5013972 Aug 5, 2025 TX Tow-Away 0 0
cr_4828171 Jun 21, 2024 MI Tow-Away 0 0
cr_4633342 Sep 18, 2023 OH Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2019 PETERBILT 365
NHTSA recalls and complaints for this make/model/year.
Recall
22V277000
STEERING:CRITICAL FASTENERS
Recall
21V391000
FUEL SYSTEM, DIESEL:FUEL INJECTION SYSTEM:FUEL RAIL
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Carrier
A PARENT COMPANY LLC
USDOT 3365498 · 5 crashes · 39 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1NPSLP9X6KD600003
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
A PARENT COMPANY LLC
Crashes reported by this law-enforcement agency.
City
Crashes in TOWNSEND (TOWNSHIP OF), OH
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.