Skip to main content
TruckCodex
Hubs

Crash Record WV202208927A

FMCSA crash record in BIG OTTER on Mar 31, 2022.

Injury Federal Recordable

What happened

On March 31, 2022, FMCSA recorded an injury crash with one person hurt in BIG OTTER, West Virginia. The vehicle was operated by MENKE LLC (USDOT 1648850). Recorded conditions: 1 / 1 / 1 pavement. Reported by MENKE LLC, FMCSA reference WV202208927A.

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
1
Carrier
USDOT 1648850
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
8
1 injury · 8 tow-away
Crashes per 100 power units (24 mo)
10.0
7 crashes · 70 units
Days since prior carrier crash
129
Last on Nov 22, 2021
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,419 carriers

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 #:
WV202208927A
Date:
Mar 31, 2022
Time:
1700
State:
West Virginia
City:
BIG OTTER
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
1
Carrier (USDOT):
MENKE LLC (1648850)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 7 12 1XKYDP9X5LJ342577 2421387 (IN) MENKE LLC 2 No

Crash event

Event sequence description.

1:98:OTHER:GUARDRAIL FACE

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmodru174005hnvfdi9f42gqt Apr 19, 2026 KY Tow-Away 0 0
cmoax1cjz002vnvsyuwj4t0b4 Apr 17, 2026 TN Tow-Away 0 0
cr_5062267 Nov 16, 2025 TN Tow-Away 0 0
cr_4998017 Jul 1, 2025 KY Injury 0 1
cr_5016036 Jul 1, 2025 WV Tow-Away 0 0
cr_4943818 May 13, 2025 OH Injury 0 1
cr_4899550 Jan 29, 2025 GA Tow-Away 0 0
cr_4735228 Apr 14, 2024 FL Tow-Away 0 0
cr_4729169 Apr 7, 2024 NC Tow-Away 0 0
cr_4706490 Feb 12, 2024 PA Injury 0 1

Carrier booking & risk tools

Check booking and risk signals for USDOT 1648850 — 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.