Skip to main content
TruckCodex
Hubs

Crash Record OH0235054706

FMCSA crash record in RICHLAND (TOWNSHIP OF) on Apr 5, 2023.

Tow-Away Federal Recordable

What happened

On April 5, 2023, FMCSA recorded a tow-away crash with no reported injuries in RICHLAND (TOWNSHIP OF), Ohio. The vehicle was operated by JERZY TRUCKING LLC (USDOT 1753719). Recorded conditions: 2 / 1 / 1 pavement. Reported by JERZY, TRUCKING, FMCSA reference OH0235054706.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
1
Carrier
JERZY TRUCKING LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
22
4 injury · 22 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 35 units
Days since prior carrier crash
40
Last on Feb 24, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,547 carriers

Geographic context

How this crash sits in its setting.

Within RICHLAND (TOWNSHIP OF), Ohio, 85 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
2
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 #:
OH0235054706
Date:
Apr 5, 2023
Time:
2330
State:
Ohio
City:
RICHLAND (TOWNSHIP OF)
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
JERZY TRUCKING LLC (1753719)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 3AKJGLDR8HSHF0973 P1159158 (IL) JERZY, TRUCKING 3 No

Crash event

Event sequence description.

1:19:COLLISION WITH WORK ZONE MAINTENANCE EQUIPMENT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4557755 May 7, 2023 IN Tow-Away 0 0
cr_4541870 Apr 12, 2023 VA Tow-Away 0 0
cr_4521902 Feb 24, 2023 PA Tow-Away 0 0
cr_4513136 Feb 14, 2023 WY Tow-Away 0 0
cr_4519921 Jan 31, 2023 PA Tow-Away 0 0
cr_4482021 Dec 21, 2022 KS Injury 0 1
cr_4496160 Dec 12, 2022 OR Tow-Away 0 0
cr_4615027 Oct 8, 2022 NJ Injury 0 1
cr_4400439 Aug 12, 2022 KY Tow-Away 0 0
cr_4409519 Aug 11, 2022 NC Tow-Away 0 0

Related records

Vehicle
2017 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
23V073000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
22V817000
FORWARD COLLISION AVOIDANCE: ADAPTIVE CRUISE CONTROL
Recall
20V567000
EXTERIOR LIGHTING:BRAKE LIGHTS
Carrier
JERZY TRUCKING LLC
USDOT 1753719 · 24 crashes · 0 inspections
Vehicle
VIN: 3AKJGLDR8HSHF0973
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
JERZY, TRUCKING
Crashes reported by this law-enforcement agency.
City
Crashes in RICHLAND (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.