Crash Record OH0194295001

FMCSA crash record in Ohio on Nov 25, 2019.

Injury

What happened

On November 25, 2019, FMCSA recorded an injury crash with one person hurt in Ohio. The vehicle was operated by TRX EXPRESS INC (USDOT 2330774). FMCSA reference OH0194295001.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
Carrier
TRX EXPRESS INC
Vehicle Type
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
8
2 injury · 7 tow-away
Crashes per 100 power units (24 mo)
9.3
9 crashes · 97 units
Days since prior carrier crash
25
Last on Oct 31, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 26,680 carriers

Geographic context

How this crash sits in its setting.

Within Ohio, 11,628 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 #:
OH0194295001
Date:
Nov 25, 2019
Time:
1355
State:
Ohio
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Carrier (USDOT):
TRX EXPRESS INC (2330774)

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5097788 Jan 31, 2026 NC Injury 0 1
cr_5060373 Nov 7, 2025 RI Tow-Away 0 0
cr_4998653 Aug 1, 2025 KY Tow-Away 0 0
cr_5009836 Jul 28, 2025 TN Tow-Away 0 0
cr_4996769 Jun 11, 2025 IN Tow-Away 0 0
cr_4946625 Apr 3, 2025 IN Injury 0 2
cr_4876857 Jan 10, 2025 NC Tow-Away 0 0
cr_4825386 Oct 14, 2024 WI Tow-Away 0 0
cr_4816329 Sep 27, 2024 VA Injury 0 1
cr_5003161 Jul 8, 2024 NJ Injury 0 1

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.