Crash Record TX5IGDHQE1IS

FMCSA crash record in Texas on Jul 16, 2019.

Injury

What happened

On July 16, 2019, FMCSA recorded an injury crash with one person hurt in Texas. The vehicle was operated by MUSTANG CAT (USDOT 428958). FMCSA reference TX5IGDHQE1IS.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
Carrier
MUSTANG CAT
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
4 injury · 4 tow-away
Crashes per 100 power units (24 mo)
2.5
2 crashes · 81 units
Days since prior carrier crash
43
Last on Jun 3, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within Texas, 31,183 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
TX5IGDHQE1IS
Date:
Jul 16, 2019
Time:
0755
State:
Texas
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
MUSTANG CAT (428958)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5033375 Sep 18, 2025 TX Tow-Away 0 0
cr_4838345 Oct 25, 2024 TX Tow-Away 0 0
cr_4806929 Aug 23, 2024 TX Injury 0 1
cr_3854379 Sep 17, 2019 TX Injury 0 1
cr_3835500 Jul 29, 2019 TX Injury 0 1
cr_3805288 Jun 3, 2019 TX Injury 0 1
cr_3625003 Jul 2, 2018 TX Injury 0 1
cr_3610864 May 29, 2018 TX Tow-Away 0 0
cr_3582094 Apr 10, 2018 TX Injury 0 3
cr_3437066 Jul 27, 2017 TX Tow-Away 0 0

Related records

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.