Skip to main content
TruckCodex
Hubs

Crash Record VA0222075234

FMCSA crash record in Virginia on Jul 19, 2022.

Injury Federal Recordable

What happened

On July 19, 2022, FMCSA recorded an injury crash with one person hurt in Virginia. The vehicle was operated by J R THARPE TRUCKING COMPANY INC (USDOT 270972). Recorded conditions: 1 / 1 / 1 pavement. Reported by J R THARPE TRUCKING COMPANY INC, FMCSA reference VA0222075234.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
J R THARPE TRUCKING COMPANY INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
11
1 fatal · 6 injury
Crashes per 100 power units (24 mo)
6.7
10 crashes · 150 units
Days since prior carrier crash
180
Last on Jan 20, 2022
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,000 carriers

Geographic context

How this crash sits in its setting.

Within Virginia, 7,546 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 #:
VA0222075234
Date:
Jul 19, 2022
Time:
1128
State:
Virginia
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
J R THARPE TRUCKING COMPANY INC (270972)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 6 6 4V5KG9EJ7LN247968 75519P (VA) J R THARPE TRUCKING COMPANY INC 3 No

Crash event

Event sequence description.

3:17:COLLISION INVOLVING ANIMAL;1:8:NONCOLLISION:CROSS MEDIAN/CENTERLINE;2:6:NONCOLLISION:EXPLOSION OR FIRE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5125432 Mar 9, 2026 VA Tow-Away 0 0
cr_5109180 Feb 6, 2026 VA Tow-Away 0 0
cr_5098526 Jan 30, 2026 VA Tow-Away 0 0
cr_5090596 Jan 16, 2026 VA Tow-Away 0 0
cr_5057481 Nov 6, 2025 VA Tow-Away 0 0
cr_5058313 Jul 9, 2025 VA Tow-Away 0 0
cr_4898736 Feb 19, 2025 VA Tow-Away 0 0
cr_4885444 Jan 28, 2025 VA Tow-Away 0 0
cr_4844974 Nov 1, 2024 VA Injury 0 1
cr_4826226 Oct 10, 2024 VA Tow-Away 0 0

Related records

Vehicle
2020 VOLVO TRUCK VHD
NHTSA recalls and complaints for this make/model/year.
Carrier
J R THARPE TRUCKING COMPANY INC
USDOT 270972 · 78 crashes · 221 inspections
Vehicle
VIN: 4V5KG9EJ7LN247968
Decode this VIN for make, model, year, and recall data.
State
Crashes in Virginia
Statewide crash records.
Agency
J R THARPE TRUCKING COMPANY INC
Crashes reported by this law-enforcement agency.
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.