TruckCodex
Hubs

Crash Record TX6398HQE1UB

FMCSA crash record in NOT LISTED on Jul 28, 2021.

Injury Federal Recordable

What happened

On July 28, 2021, FMCSA recorded an injury crash with one person hurt in NOT LISTED, Texas. The vehicle was operated by BEEMAC INC (USDOT 388467). Recorded conditions: 1 / 1 / 1 pavement. Reported by BEEMAC INC, FMCSA reference TX6398HQE1UB.

Carrier pattern note

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

Geographic note

This crash is part of an active corridor: 11935 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
BEEMAC INC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
47
1 fatal · 18 injury
Crashes per 100 power units (24 mo)
7.2
38 crashes · 525 units
Days since prior carrier crash
13
Last on Jul 15, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,836 carriers

Geographic context

How this crash sits in its setting.

Within NOT LISTED, Texas, 11,935 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 #:
TX6398HQE1UB
Date:
Jul 28, 2021
Time:
1247
State:
Texas
City:
NOT LISTED
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BEEMAC INC (388467)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 3 1FUPCSZB8XLA19762 R426314 (TX) BEEMAC INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5124108 Mar 19, 2026 AL Tow-Away 0 0
cr_5119630 Mar 4, 2026 PA Tow-Away 0 0
cr_5115997 Mar 3, 2026 MO Injury 0 1
cr_5118292 Mar 1, 2026 MO Tow-Away 0 0
cr_5116376 Feb 24, 2026 TX Injury 0 1
cr_5106288 Feb 16, 2026 KY Injury 0 1
cr_5106697 Feb 8, 2026 MO Tow-Away 0 0
cr_5120782 Feb 6, 2026 PA Tow-Away 0 0
cr_5098390 Jan 20, 2026 MI Injury 0 1
cr_5109020 Jan 17, 2026 PA Tow-Away 0 0

Related records

Carrier
BEEMAC INC
USDOT 388467 · 255 crashes · 1,372 inspections
Vehicle
VIN: 1FUPCSZB8XLA19762
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
Agency
BEEMAC INC
Crashes reported by this law-enforcement agency.
City
Crashes in NOT LISTED, 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.