Crash Record TX7DJEHQE1D9

FMCSA crash record in HOUSTON on Feb 13, 2026.

Injury Federal Recordable

What happened

On February 13, 2026, FMCSA recorded an injury crash with one person hurt in HOUSTON, Texas. The vehicle was operated by EXCARGO SERVICES INC (USDOT 242877). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference TX7DJEHQE1D9.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

EXCARGO SERVICES INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

3 injury · 5 tow-away

Crashes per 100 power units (24 mo)

6.5

5 crashes · 77 units

Days since prior carrier crash

247

Last on Jun 11, 2025

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,602 carriers

Geographic context

How this crash sits in its setting.

Within HOUSTON, Texas, 2,326 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

METROPOLITAN TRANSIT AUTHORITY (HOUSTON METRO TRANSIT AUTHORITY) · 104 reports
UNKNOWN (USE ONLY FOR ACCIDENTS) · 41 reports
CITY OF HOUSTON · 21 reports

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 #:: TX7DJEHQE1D9
Date:: Feb 13, 2026
Time:: 1329
State:: Texas
City:: HOUSTON
Fatalities:: 0
Injuries:: 1
Tow-Away:: No
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: EXCARGO SERVICES INC (242877)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	11	3HSCUAPR09N119030	1N50346 (TX)	EXCARGO SERVICES INC	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Fatalities	Injuries
cr_5010570	Jun 11, 2025	TX	Injury	0	2
cr_4906409	Mar 4, 2025	TX	Tow-Away	0	0
cr_4897670	Feb 11, 2025	TX	Tow-Away	0	0
cr_4838325	Oct 26, 2024	TX	Tow-Away	0	0
cr_4715829	Mar 5, 2024	TX	Injury	0	1
cr_4647238	Oct 20, 2023	TX	Tow-Away	0	0
cr_4627634	Sep 18, 2023	TX	Fatal	1	1
cr_4538489	Aug 24, 2022	TX	Tow-Away	0	0
cr_4388835	Jul 7, 2022	TX	Injury	0	1
cr_3797168	May 20, 2019	TX	Tow-Away	0	0

Related records

Carrier

EXCARGO SERVICES INC

USDOT 242877 · 68 crashes · 137 inspections

Vehicle

VIN: 3HSCUAPR09N119030

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.