Crash Record TX33IFHQE1GZ

FMCSA crash record in Texas on Jan 26, 2010.

Injury

What happened

On January 26, 2010, FMCSA recorded an injury crash with 2 people hurt in Texas. The vehicle was operated by RAD TRUCKING LTD (USDOT 1152201). FMCSA reference TX33IFHQE1GZ.

Carrier pattern note

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

Fatalities
0
Injuries
2
Vehicles
Carrier
RAD TRUCKING LTD
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
1 fatal · 5 injury
Crashes per 100 power units (24 mo)
30.0
3 crashes · 10 units
Days since prior carrier crash
2
Last on Jan 24, 2010
Vs fleet-size peers
above the median
Cohort median 0.0 · 312,512 carriers

Geographic context

How this crash sits in its setting.

Within Texas, 31,090 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 #:
TX33IFHQE1GZ
Date:
Jan 26, 2010
Time:
0851
State:
Texas
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
RAD TRUCKING LTD (1152201)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5029913 Sep 16, 2025 LA Injury 0 1
cr_4888889 Jan 31, 2025 TX Injury 0 1
cr_4809396 Sep 7, 2024 TX Injury 0 1
cr_4782563 Jun 28, 2024 TX Injury 0 1
cr_4770325 Jun 8, 2024 TX Injury 0 2
cr_4744652 Apr 26, 2024 TX Tow-Away 0 0
cr_4587832 Jun 30, 2023 TX Tow-Away 0 0
cr_4323172 Mar 16, 2022 TX Tow-Away 0 0
cr_4532218 Sep 1, 2021 TX Injury 0 2
cr_4160019 May 20, 2021 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.