Crash Record TX4YZBHQE126
FMCSA crash record in Texas on Aug 10, 2017.
Tow-Away
What happened
On August 10, 2017, FMCSA recorded a tow-away crash with no reported injuries in Texas. The vehicle was operated by BIH LLC (USDOT 2463093). FMCSA reference TX4YZBHQE126.
Fatalities
0
Injuries
0
Vehicles
—
Carrier
BIH LLC
Vehicle Type
—
Severity
Tow-Away
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
2
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
20.0
1 crashes · 5 units
Days since prior carrier crash
291
Last on Oct 23, 2016
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,564,214 carriers
Geographic context
How this crash sits in its setting.
Within Texas, 29,445 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- UNKNOWN (USE ONLY FOR ACCIDENTS) · 276 reports
- METROPOLITAN TRANSIT AUTHORITY (HOUSTON METRO TRANSIT AUTHORITY) · 106 reports
- FEDERAL EXPRESS CORPORATION · 95 reports
Crash details
Key facts from the FMCSA crash record.
- Report #:
- TX4YZBHQE126
- Date:
- Aug 10, 2017
- Time:
- 1316
- State:
- Texas
- Fatalities:
- 0
- Injuries:
- 0
- Tow-Away:
- Yes
- HazMat:
- No
- Carrier (USDOT):
- BIH LLC (2463093)
Other crashes by this carrier
6 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_4890736 | Jan 21, 2025 | MI | Tow-Away | 0 | 0 |
| cr_4763154 | May 30, 2024 | MI | Tow-Away | 0 | 0 |
| cr_4495899 | Dec 9, 2022 | MI | Tow-Away | 0 | 0 |
| cr_4173620 | Jun 19, 2021 | MI | Injury | 0 | 1 |
| cr_3779805 | Apr 12, 2019 | MI | Tow-Away | 0 | 0 |
| cr_3294822 | Oct 23, 2016 | AL | Injury | 0 | 2 |
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.