Crash Record MO0000097749

FMCSA crash record in KANSAS CITY on Jul 13, 2022.

Tow-Away Federal Recordable

What happened

On July 13, 2022, FMCSA recorded a tow-away crash with no reported injuries in KANSAS CITY, Missouri. The vehicle was operated by JERZY TRUCKING LLC (USDOT 1753719). Recorded conditions: 1 / 1 pavement. Reported by JERZY TRUCKING LLC, FMCSA reference MO0000097749.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

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)

2 injury · 13 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 35 units

Days since prior carrier crash

Last on Jun 17, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 314,646 carriers

Geographic context

How this crash sits in its setting.

Within KANSAS CITY, Missouri, 709 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

FEDERAL EXPRESS CORPORATION · 6 reports
CITY OF KANSAS CITY · 4 reports
FIRST STUDENT INC · 4 reports

Contributing factors

What the responding officer recorded.

Light: 1
Weather: —
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 #:: MO0000097749
Date:: Jul 13, 2022
Time:: 0905
State:: Missouri
City:: KANSAS CITY
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
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	3HSDZAPR8KN566362	P1141206 (IL)	JERZY TRUCKING LLC	3	No

Crash event

Event sequence description.

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

Other crashes by this carrier

10 additional crash record(s) on file.

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

Related records

Carrier

JERZY TRUCKING LLC

USDOT 1753719 · 24 crashes · 0 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3HSDZAPR8KN566362

Decode this VIN for make, model, year, and recall data.

State

Crashes in Missouri

Statewide crash records.

Agency

JERZY TRUCKING LLC

Crashes reported by this law-enforcement agency.

City

Crashes in KANSAS CITY, MO

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.