Crash Record KS2025E30413

FMCSA crash record in Not Reported on Jul 21, 2025.

Tow-Away Federal Recordable

What happened

On July 21, 2025, FMCSA recorded a tow-away crash with no reported injuries in Not Reported, Kansas. The vehicle was operated by PSI TRANSPORT LLC (USDOT 1978620). Recorded conditions: 2 / 2 / 2 pavement. Reported by PSI TRANSPORT LLC, FMCSA reference KS2025E30413.

Geographic note

This crash is part of an active corridor: 777 crashes occurred in the same city in the past 24 months.

Fatalities

Injuries

Vehicles

Carrier

PSI TRANSPORT LLC

USDOT 1978620

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 injury · 3 tow-away

Crashes per 100 power units (24 mo)

7.4

2 crashes · 27 units

Days since prior carrier crash

470

Last on Apr 7, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 315,733 carriers

Geographic context

How this crash sits in its setting.

Within Not Reported, Kansas, 777 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: 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 #:: KS2025E30413
Date:: Jul 21, 2025
Time:: 1916
State:: Kansas
City:: Not Reported
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 1
Carrier (USDOT):: PSI TRANSPORT LLC (1978620)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	3	1XPCD49X1TD788226	245791 (KS)	PSI TRANSPORT LLC	3	No

Crash event

Event sequence description.

1:98:OTHER;2:17:COLLISION INVOLVING ANIMAL

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4998226	Jul 29, 2025	KS	Injury	1
cr_4735637	Apr 7, 2024	KS	Tow-Away	0
cr_4633976	Sep 28, 2023	KS	Injury	1
cr_4272967	Dec 13, 2021	MO	Tow-Away	0
cr_2935347	Sep 28, 2014	KS	Tow-Away	0
cr_2924246	Sep 23, 2014	KS	Injury	1
cr_2794813	Oct 24, 2013	KS	Tow-Away	0
cr_2704886	May 17, 2013	TX	Tow-Away	0
cr_2677849	Mar 6, 2013	KS	Tow-Away	0
cr_2660530	Feb 5, 2013	NE	Injury	1

Carrier booking & risk tools

Check booking and risk signals for USDOT 1978620 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle

2026 PETERBILT 567

NHTSA recalls and complaints for this make/model/year.

USDOT 1978620 · 13 crashes · 47 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XPCD49X1TD788226

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

State

Crashes in Kansas

Statewide crash records.

Agency

PSI TRANSPORT LLC

Crashes reported by this law-enforcement agency.

City

Crashes in Not Reported, KS

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.