TruckCodex
Hubs

Crash Record VA0252530255

FMCSA crash record in HANOVER on Sep 4, 2025.

Tow-Away Federal Recordable

What happened

On September 4, 2025, FMCSA recorded a tow-away crash with no reported injuries in HANOVER, Virginia. The vehicle was operated by HINKLE TRUCKING INC (USDOT 85216). Recorded conditions: 1 / 1 / 1 pavement. Reported by HINKLE TRUCKING INC, FMCSA reference VA0252530255.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
HINKLE TRUCKING INC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
12
5 injury · 12 tow-away
Crashes per 100 power units (24 mo)
16.3
14 crashes · 86 units
Days since prior carrier crash
114
Last on May 13, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within HANOVER, Virginia, 71 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 #:
VA0252530255
Date:
Sep 4, 2025
Time:
1043
State:
Virginia
City:
HANOVER
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
HINKLE TRUCKING INC (85216)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 5 1XPXDP9X2HD412497 BA548454 (WV) HINKLE TRUCKING 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 Fatalities Injuries
cr_5124880 Mar 18, 2026 VA Tow-Away 0 0
cr_5112133 Jan 23, 2026 MD Tow-Away 0 0
cr_5077345 Dec 17, 2025 WV Injury 0 1
cr_5077551 Dec 11, 2025 VA Tow-Away 0 0
cr_5078680 Nov 11, 2025 VA Injury 0 2
cr_5026581 Sep 4, 2025 OH Injury 0 1
cr_4947606 May 13, 2025 VA Tow-Away 0 0
cr_4892330 Feb 12, 2025 VA Tow-Away 0 0
cr_4888022 Feb 6, 2025 VA Injury 0 1
cr_4896928 Jan 28, 2025 VA Tow-Away 0 0

Related records

Vehicle
2017 PETERBILT 389
NHTSA recalls and complaints for this make/model/year.
Recall
20V199000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
20V130000
ELECTRICAL SYSTEM:12V/24V/48V BATTERY:CABLES
Recall
18V657000
ENGINE AND ENGINE COOLING:ENGINE:DIESEL
Carrier
HINKLE TRUCKING INC
USDOT 85216 · 129 crashes · 105 inspections
Vehicle
VIN: 1XPXDP9X2HD412497
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
HINKLE TRUCKING INC
Crashes reported by this law-enforcement agency.
City
Crashes in HANOVER, VA
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.