Skip to main content
TruckCodex
Hubs

Crash Record TX245272800M

FMCSA crash record in Texas on Jan 16, 2003.

Tow-Away

What happened

On January 16, 2003, FMCSA recorded a tow-away crash with no reported injuries in Texas. The vehicle was operated by KINEXO INC (USDOT 255139). FMCSA reference TX245272800M.

Fatalities
0
Injuries
0
Vehicles
—
Carrier
USDOT 255139
Vehicle Type
—
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
4
1 injury · 4 tow-away
Days since prior carrier crash
423
Last on Nov 19, 2001

Geographic context

How this crash sits in its setting.

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

Agencies most active in this area:

Crash details

Key facts from the FMCSA crash record.

Report #:
TX245272800M
Date:
Jan 16, 2003
Time:
1245
State:
Texas
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
KINEXO INC (255139)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_1662886 May 14, 2006 AZ Tow-Away 0 0
cr_1210458 Nov 10, 2003 MO Injury 0 1
cr_313215 Nov 19, 2001 NC Injury 0 1
cr_263042 Mar 8, 2001 NC Tow-Away 0 0
cr_937467 Feb 28, 2001 FL Tow-Away 0 0
cr_869137 Mar 24, 2000 NV Injury 0 2
cr_798817 Sep 11, 1998 NC Injury 0 1
cr_554728 Feb 3, 1998 GA Injury 0 2
cr_827496 Feb 17, 1997 NE Tow-Away 0 0
cr_424191 Dec 4, 1996 AR Tow-Away 0 0

Carrier booking & risk tools

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

Related records

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.