Skip to main content
TruckCodex
Hubs

Crash Record TX70P8HQE1II

FMCSA crash record in NOT LISTED on Nov 12, 2024.

Injury Federal Recordable

What happened

On November 12, 2024, FMCSA recorded an injury crash with 2 people hurt in NOT LISTED, Texas. The vehicle was operated by STERLING LOGISTICS COMPANY (USDOT 2095642). Recorded conditions: 2 / 5 / 1 pavement. FMCSA reference TX70P8HQE1II.

Carrier pattern note

This is the carrier's 7 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 6–50 power units.

Geographic note

This crash is part of an active corridor: 10481 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
2
Vehicles
2
Carrier
STERLING LOGISTICS COMPANY
USDOT 2095642
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
7
1 injury · 7 tow-away
Crashes per 100 power units (24 mo)
6.5
2 crashes · 31 units
Days since prior carrier crash
305
Last on Jan 12, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 316,078 carriers

Geographic context

How this crash sits in its setting.

Within NOT LISTED, Texas, 10,481 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
2
Weather
5
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 #:
TX70P8HQE1II
Date:
Nov 12, 2024
Time:
0050
State:
Texas
City:
NOT LISTED
Fatalities:
0
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
STERLING LOGISTICS COMPANY (2095642)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
3 9 3 4V4NC9EJ6PN613292 RC27557 (MI) STERLING LOGISTICS CO 3 No

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5056393 Oct 31, 2025 TX Tow-Away 0 0
cr_4680969 Jan 12, 2024 AR Tow-Away 0 0
cr_4609602 Aug 22, 2023 TN Tow-Away 0 0
cr_4548904 Apr 21, 2023 IN Tow-Away 0 0
cr_4533808 Mar 17, 2023 TX Tow-Away 0 0
cr_4523980 Mar 4, 2023 MI Tow-Away 0 0
cr_4468324 Dec 3, 2022 AR Tow-Away 0 0
cr_4361489 May 18, 2022 AR Injury 0 1
cr_4341838 Apr 8, 2022 TX Injury 0 1
cr_4013204 Aug 2, 2020 MI Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
STERLING LOGISTICS COMPANY
USDOT 2095642 · 25 crashes · 48 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 4V4NC9EJ6PN613292
Decode this VIN for make, model, year, and recall data.
State
Crashes in Texas
Statewide crash records.
City
Crashes in NOT LISTED, 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.