Skip to main content
TruckCodex
Hubs

Crash Record TX6PSBHQE1BO

FMCSA crash record in HILLSBORO on Oct 23, 2023.

Tow-Away Federal Recordable

What happened

On October 23, 2023, FMCSA recorded a tow-away crash with no reported injuries in HILLSBORO, Texas. The vehicle was operated by EOS INC (USDOT 2413373). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference TX6PSBHQE1BO.

Carrier pattern note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
EOS INC
USDOT 2413373
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
21
4 injury · 20 tow-away
Crashes per 100 power units (24 mo)
5.3
17 crashes · 320 units
Days since prior carrier crash
69
Last on Aug 15, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,365 carriers

Geographic context

How this crash sits in its setting.

Within HILLSBORO, Texas, 25 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 #:
TX6PSBHQE1BO
Date:
Oct 23, 2023
Time:
1047
State:
Texas
City:
HILLSBORO
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
EOS INC (2413373)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHHDR3PSUM4984 K823860 (AR) EOS INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmup2ni6s00anl4z8tp79cils Sep 21, 2026 PA Injury 0 1
cr_5122298 Mar 8, 2026 TX Tow-Away 0 0
cr_5105621 Feb 4, 2026 MS Tow-Away 0 0
cr_5088051 Jan 11, 2026 VA Injury 0 1
cr_5067599 Nov 6, 2025 IL Injury 0 1
cr_5049328 Oct 28, 2025 AR Tow-Away 0 0
cr_5056080 Oct 22, 2025 GA Injury 0 1
cr_5037115 Sep 18, 2025 TX Tow-Away 0 0
cr_5028917 Aug 25, 2025 GA Injury 0 1
cr_5020761 Aug 23, 2025 MI Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 2413373 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Carrier
EOS INC
USDOT 2413373 · 113 crashes · 1,216 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR3PSUM4984
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
City
Crashes in HILLSBORO, 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.