Crash Record TX6E4DHQE1W6

FMCSA crash record in IRVING on Aug 29, 2022.

Tow-Away Federal Recordable

What happened

On August 29, 2022, FMCSA recorded a tow-away crash with no reported injuries in IRVING, Texas. The vehicle was operated by RUNSS CORP (USDOT 1962700). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference TX6E4DHQE1W6.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

RUNSS CORP

USDOT 1962700

Vehicle Type

Truck

Severity

Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

2 injury · 3 tow-away

Crashes per 100 power units (24 mo)

0.0

0 crashes · 55 units

Days since prior carrier crash

204

Last on Feb 6, 2022

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,042 carriers

Geographic context

How this crash sits in its setting.

Within IRVING, Texas, 201 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

DALLAS AREA RAPID TRANSIT (D A R T) · 2 reports
FEDERAL EXPRESS CORPORATION · 2 reports
LONE STAR MILK TRANSPORT INC · 2 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 #:: TX6E4DHQE1W6
Date:: Aug 29, 2022
Time:: 0814
State:: Texas
City:: IRVING
Fatalities:: 0
Injuries:: 0
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: RUNSS CORP (1962700)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	3AKJHHDR0NSWE9796	P1157381 (IL)	RUNSS CORP	3	No

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_4817174	Sep 19, 2024	MA	Tow-Away	0
cr_4597064	Jul 16, 2023	GA	Tow-Away	0
cr_4524070	Mar 1, 2023	OH	Injury	1
cr_4507539	Feb 4, 2023	TX	Tow-Away	0
cr_4504512	Feb 1, 2023	AR	Tow-Away	0
cr_4489916	Dec 21, 2022	MD	Injury	1
cr_4461765	Nov 16, 2022	MT	Tow-Away	0
cr_4301719	Feb 6, 2022	TN	Injury	1
cr_4215024	Aug 29, 2021	TX	Tow-Away	0
cr_4178587	Jun 15, 2021	NC	Injury	1

Carrier booking & risk tools

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

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

Related records

Carrier

RUNSS CORP

USDOT 1962700 · 13 crashes · 0 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 3AKJHHDR0NSWE9796

Decode this VIN for make, model, year, and recall data.

State

Crashes in Texas

Statewide crash records.

City

Crashes in IRVING, 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.