Skip to main content
TruckCodex
Hubs

Crash Record TX79I9HQE1IO

FMCSA crash record in SAN ANTONIO on Sep 29, 2025.

Injury Federal Recordable

What happened

On September 29, 2025, FMCSA recorded an injury crash with one person hurt in SAN ANTONIO, Texas. The vehicle was operated by SPLASH TRANSPORT INC (USDOT 1765150). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference TX79I9HQE1IO.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
3
Carrier
SPLASH TRANSPORT INC
USDOT 1765150
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
106
3 fatal · 42 injury
Crashes per 100 power units (24 mo)
2.4
74 crashes · 3,121 units
Days since prior carrier crash
11
Last on Sep 18, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,877 carriers

Geographic context

How this crash sits in its setting.

Within SAN ANTONIO, Texas, 1,143 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 #:
TX79I9HQE1IO
Date:
Sep 29, 2025
Time:
0855
State:
Texas
City:
SAN ANTONIO
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
3
Carrier (USDOT):
SPLASH TRANSPORT INC (1765150)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
3 9 3 1FUJGEFG9JLJP3560 1M22642 (TX) SPLASH TRANSPORT INC 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmqlxkk08001jp8trwq4r1sid Jun 15, 2026 OK Injury 0 1
cr_5114325 Feb 17, 2026 IN Tow-Away 0 0
cr_5124365 Feb 6, 2026 IL Tow-Away 0 0
cr_5119934 Feb 6, 2026 PA Tow-Away 0 0
cr_5104448 Feb 6, 2026 TN Tow-Away 0 0
cr_5101506 Jan 31, 2026 FL Tow-Away 0 0
cr_5107130 Jan 27, 2026 MI Tow-Away 0 0
cr_5098201 Jan 26, 2026 CA Injury 0 1
cr_5100153 Jan 21, 2026 MI Tow-Away 0 0
cr_5104392 Jan 15, 2026 PA Injury 0 1

Carrier booking & risk tools

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

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

Related records

Carrier
SPLASH TRANSPORT INC
USDOT 1765150 · 905 crashes · 2,517 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUJGEFG9JLJP3560
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
City
Crashes in SAN ANTONIO, 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.