TruckCodex
Hubs

Crash Record TX6RKEHQE1HZ

FMCSA crash record in LAREDO on Dec 19, 2023.

Injury Federal Recordable

What happened

On December 19, 2023, FMCSA recorded an injury crash with one person hurt in LAREDO, Texas. The vehicle was operated by ERIVES ENTERPRISES INC (USDOT 1807687). Recorded conditions: 3 / 1 / 1 pavement. Reported by ERIVES ENTERPRISES INC, FMCSA reference TX6RKEHQE1HZ.

Carrier pattern note

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

Geographic note

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

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

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
25
4 injury · 24 tow-away
Crashes per 100 power units (24 mo)
3.8
16 crashes · 420 units
Days since prior carrier crash
33
Last on Nov 16, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,863 carriers

Geographic context

How this crash sits in its setting.

Within LAREDO, Texas, 251 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
3
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 #:
TX6RKEHQE1HZ
Date:
Dec 19, 2023
Time:
1735
State:
Texas
City:
LAREDO
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
ERIVES ENTERPRISES INC (1807687)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 8 98 3AKJHHDR7LSLJ0232 R445450 (TX) ERIVES ENTERPRISES INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmny3yh1r011fk38vg8fsen6g Apr 1, 2026 AR Injury 0 1
cr_5115561 Mar 4, 2026 NC Tow-Away 0 0
cr_5117423 Feb 18, 2026 GA Tow-Away 0 0
cr_5084337 Dec 18, 2025 TX Tow-Away 0 0
cr_5065469 Dec 1, 2025 AL Tow-Away 0 0
cr_5021534 Sep 1, 2025 TN Tow-Away 0 0
cr_5011232 Jun 17, 2025 TX Tow-Away 0 0
cr_4943103 May 12, 2025 TX Fatal 1 0
cr_4944235 May 12, 2025 VA Injury 0 1
cr_4912549 Mar 11, 2025 TX Tow-Away 0 0

Related records

Carrier
ERIVES ENTERPRISES INC
USDOT 1807687 · 116 crashes · 1,530 inspections
Vehicle
VIN: 3AKJHHDR7LSLJ0232
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
Agency
ERIVES ENTERPRISES INC
Crashes reported by this law-enforcement agency.
City
Crashes in LAREDO, 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.