Skip to main content
TruckCodex
Hubs

Crash Record TX4CB7HQE1BE

FMCSA crash record in Texas on May 15, 2015.

Fatal

What happened

On May 15, 2015, FMCSA recorded a fatal crash that resulted in one death in Texas. The vehicle was operated by REVEILLE TRUCKING INC (USDOT 592668). FMCSA reference TX4CB7HQE1BE.

Carrier pattern note

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

Fatalities
1
Injuries
0
Vehicles
—
Carrier
REVEILLE TRUCKING INC
Vehicle Type
—
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
9
2 fatal · 4 injury
Crashes per 100 power units (24 mo)
3.7
5 crashes · 134 units
Days since prior carrier crash
73
Last on Mar 3, 2015
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,929 carriers

Geographic context

How this crash sits in its setting.

Within Texas, 29,286 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 #:
TX4CB7HQE1BE
Date:
May 15, 2015
Time:
2148
State:
Texas
Fatalities:
1
Injuries:
0
Tow-Away:
No
HazMat:
No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5091183 Jan 13, 2026 AZ Injury 0 2
cr_5031886 Sep 13, 2025 AZ Tow-Away 0 0
cr_5023032 Sep 5, 2025 WV Tow-Away 0 0
cr_4988585 Jun 25, 2025 AR Injury 0 1
cr_4924712 Mar 13, 2025 TX Tow-Away 0 0
cr_4725802 Feb 19, 2024 CA Injury 0 1
cr_4686321 Jan 13, 2024 TX Tow-Away 0 0
cr_4681976 Dec 20, 2023 TX Tow-Away 0 0
cr_4627775 Sep 27, 2023 AR Injury 0 2
cr_4604027 Jul 23, 2023 TX Fatal 1 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.