Skip to main content
TruckCodex
Hubs

Crash Record WV0202602791

FMCSA crash record in WHEELING on Feb 11, 2026.

Injury Federal Recordable Bus

What happened

On February 11, 2026, FMCSA recorded an injury crash with one person hurt in WHEELING, West Virginia. The vehicle was operated by OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY (USDOT 1069870). Recorded conditions: 1 / 1 / 1 pavement. Reported by OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY, FMCSA reference WV0202602791.

Geographic note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY
Vehicle Type
Bus
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
3
2 injury · 3 tow-away
Crashes per 100 power units (24 mo)
23.5
4 crashes · 17 units
Days since prior carrier crash
97
Last on Nov 6, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 314,282 carriers

Geographic context

How this crash sits in its setting.

Within WHEELING, West Virginia, 47 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
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 #:
WV0202602791
Date:
Feb 11, 2026
Time:
1058
State:
West Virginia
City:
WHEELING
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY (1069870)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 3 2 4UZADRFD1NCNT5959 954ZSG (OH) OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY 1 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5117987 Feb 24, 2026 WV Tow-Away 0 0
cr_5054772 Nov 6, 2025 WV Tow-Away 0 0
cr_4836961 Oct 25, 2024 WV Injury 0 1
cr_4669857 Dec 1, 2023 WV Injury 0 1
cr_4567546 May 25, 2023 WV Tow-Away 0 0
cr_4396190 Jul 22, 2022 WV Injury 0 1
cr_3986907 Jun 2, 2020 WV Injury 0 1
cr_3848561 Sep 13, 2019 WV Tow-Away 0 0
cr_3722127 Jan 19, 2019 WV Tow-Away 0 0
cr_3518493 Dec 30, 2017 WV Tow-Away 0 0

Related records

Vehicle
2022 FREIGHTLINER S2C 106 Conventional Cab & Chassis
NHTSA recalls and complaints for this make/model/year.
Carrier
OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY
USDOT 1069870 · 16 crashes · 0 inspections
Vehicle
VIN: 4UZADRFD1NCNT5959
Decode this VIN for make, model, year, and recall data.
State
Crashes in West Virginia
Statewide crash records.
Agency
OHIO VALLEY REGIONAL TRANSPORTATION AUTHORITY
Crashes reported by this law-enforcement agency.
City
Crashes in WHEELING, WV
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.