Crash Record TX6CDAHQE1RT

FMCSA crash record in MIDLAND on Jun 17, 2022.

Tow-Away Federal Recordable

What happened

On June 17, 2022, FMCSA recorded a tow-away crash with no reported injuries in MIDLAND, Texas. The vehicle was operated by FEVID TRANSPORT LLC (USDOT 2404947). Recorded conditions: 1 / 1 / 1 pavement. Reported by FEVID TRANSPORT LLC, FMCSA reference TX6CDAHQE1RT.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

FEVID TRANSPORT 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 fatal · 8 injury

Crashes per 100 power units (24 mo)

6.3

13 crashes · 205 units

Days since prior carrier crash

Last on May 23, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,672 carriers

Geographic context

How this crash sits in its setting.

Within MIDLAND, Texas, 181 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 #:: TX6CDAHQE1RT
Date:: Jun 17, 2022
Time:: 1415
State:: Texas
City:: MIDLAND
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: FEVID TRANSPORT LLC (2404947)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	13	3AKJGHDVXFSGR0481	R504019 (TX)	FEVID TRANSPORT LLC	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5111010	Feb 3, 2026	TX	Injury	1
cr_5053975	Oct 12, 2025	TX	Injury	1
cr_5012064	Jul 8, 2025	TX	Tow-Away	0
cr_5012068	Jul 3, 2025	TX	Tow-Away	0
cr_5012114	Jul 2, 2025	TX	Tow-Away	0
cr_5011868	Jun 24, 2025	TX	Tow-Away	0
cr_5010475	Jun 13, 2025	TX	Tow-Away	0
cr_4911931	Mar 12, 2025	TX	Tow-Away	0
cr_4903668	Feb 28, 2025	TX	Injury	2
cr_4911982	Feb 19, 2025	TX	Tow-Away	0

Related records

Vehicle

2015 FREIGHTLINER Cascadia

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

SERVICE BRAKES, AIR:SUPPLY:RESERVOIR/TANK

Recall

19V093000

STEERING:LINKAGES:TIE ROD ASSEMBLY

Carrier

FEVID TRANSPORT LLC

USDOT 2404947 · 73 crashes · 237 inspections

Vehicle

VIN: 3AKJGHDVXFSGR0481

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

State

Crashes in Texas

Statewide crash records.

Agency

FEVID TRANSPORT LLC

Crashes reported by this law-enforcement agency.

City

Crashes in MIDLAND, TX

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.