TruckCodex
Hubs

Crash Record TX6X2DHQE1SX

FMCSA crash record in HOUSTON on May 29, 2024.

Tow-Away Federal Recordable

What happened

On May 29, 2024, FMCSA recorded a tow-away crash with no reported injuries in HOUSTON, Texas. The vehicle was operated by OAP TRANSPORTATION LLC (USDOT 222024). Recorded conditions: 5 / 8 / 1 pavement. FMCSA reference TX6X2DHQE1SX.

Carrier pattern note

This is the carrier's 66 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: 2308 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
0
Vehicles
2
Carrier
OAP TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
66
2 fatal · 27 injury
Crashes per 100 power units (24 mo)
4.4
40 crashes · 919 units
Days since prior carrier crash
5
Last on May 24, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,836 carriers

Geographic context

How this crash sits in its setting.

Within HOUSTON, Texas, 2,308 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
5
Weather
8
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 #:
TX6X2DHQE1SX
Date:
May 29, 2024
Time:
0715
State:
Texas
City:
HOUSTON
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
OAP TRANSPORTATION LLC (222024)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 98 3HSDWTZR8NN313516 N31516 (IN) OAP TRANSPORTATION LLC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5090647 Jan 20, 2026 AL Tow-Away 0 0
cr_5084209 Jan 6, 2026 NC Injury 0 1
cr_5081008 Dec 24, 2025 TN Tow-Away 0 0
cr_5079760 Dec 20, 2025 GA Tow-Away 0 0
cr_5079529 Dec 16, 2025 NC Tow-Away 0 0
cr_5089126 Dec 13, 2025 OH Injury 0 1
cr_5062217 Nov 12, 2025 VA Tow-Away 0 0
cr_5056882 Nov 8, 2025 KY Tow-Away 0 0
cr_5055064 Oct 14, 2025 NM Injury 0 1
cr_5050340 Sep 17, 2025 WA Tow-Away 0 0

Related records

Carrier
OAP TRANSPORTATION LLC
USDOT 222024 · 556 crashes · 1,237 inspections
Vehicle
VIN: 3HSDWTZR8NN313516
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
City
Crashes in HOUSTON, 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.