TruckCodex
Hubs

Crash Record OH0245175898

FMCSA crash record in BEAVERCREEK (TOWNSHIP OF) on Sep 29, 2024.

Injury Federal Recordable

What happened

On September 29, 2024, FMCSA recorded an injury crash with 3 people hurt in BEAVERCREEK (TOWNSHIP OF), Ohio. The vehicle was operated by DTP TRUCKING INC (USDOT 3014141). Recorded conditions: 1 / 2 / 2 pavement. Reported by DTP TRUCKING LLC, FMCSA reference OH0245175898.

Carrier pattern note

This is the carrier's 5 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 power units.

Fatalities
0
Injuries
3
Vehicles
5
Carrier
DTP TRUCKING INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
5
3 injury · 5 tow-away
Crashes per 100 power units (24 mo)
13.3
2 crashes · 15 units
Days since prior carrier crash
96
Last on Jun 25, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 313,835 carriers

Geographic context

How this crash sits in its setting.

Within BEAVERCREEK (TOWNSHIP OF), Ohio, 20 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
2
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 #:
OH0245175898
Date:
Sep 29, 2024
Time:
1519
State:
Ohio
City:
BEAVERCREEK (TOWNSHIP OF)
Fatalities:
0
Injuries:
3
Tow-Away:
Yes
HazMat:
No
Vehicles:
5
Carrier (USDOT):
DTP TRUCKING INC (3014141)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUYSZYB5XLA58827 NS1490 (NC) DTP TRUCKING LLC 3 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4876258 Jan 13, 2025 NC Tow-Away 0 0
cr_4771352 Jun 25, 2024 SC Injury 0 1
cr_4702063 Jan 16, 2024 IL Injury 0 1
cr_4504850 Feb 2, 2023 IL Tow-Away 0 0
cr_4467820 Nov 18, 2022 MI Tow-Away 0 0
cr_4279657 Dec 29, 2021 SC Tow-Away 0 0
cr_4251686 Oct 13, 2021 IL Tow-Away 0 0
cr_4179327 Jun 18, 2021 NC Tow-Away 0 0
cr_4160550 May 26, 2021 NC Injury 0 1
cr_4028408 Jul 13, 2020 IL Tow-Away 0 0

Related records

Vehicle
1999 FREIGHTLINER CC Conventional
NHTSA recalls and complaints for this make/model/year.
Carrier
DTP TRUCKING INC
USDOT 3014141 · 14 crashes · 28 inspections
Vehicle
VIN: 1FUYSZYB5XLA58827
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
DTP TRUCKING LLC
Crashes reported by this law-enforcement agency.
City
Crashes in BEAVERCREEK (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.