Crash Record WV202512014A
FMCSA crash record in GLENWOOD on Jun 3, 2025.
Injury
Federal Recordable
What happened
On June 3, 2025, FMCSA recorded an injury crash with 2 people hurt in GLENWOOD, West Virginia. The vehicle was operated by SPLASH TRANSPORT INC (USDOT 1765150). Recorded conditions: 1 / 1 / 1 pavement. Reported by SPLASH TRANSPORT INC, FMCSA reference WV202512014A.
Carrier pattern note
This is the carrier's 116 crashes in the past 24 months — above the typical pattern (median 0) for fleets of 500+ power units.
Fatalities
0
Injuries
2
Vehicles
2
Vehicle Type
Truck
Severity
Injury
This carrier's crash pattern
Derived from the carrier's full crash history.
Carrier crashes (24 mo)
116
2 fatal · 42 injury
Crashes per 100 power units (24 mo)
2.4
74 crashes · 3,121 units
Days since prior carrier crash
1
Last on Jun 2, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,875 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 #:
- WV202512014A
- Date:
- Jun 3, 2025
- Time:
- 1550
- State:
- West Virginia
- City:
- GLENWOOD
- Fatalities:
- 0
- Injuries:
- 2
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 2
- Carrier (USDOT):
- SPLASH TRANSPORT INC (1765150)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 9 | 3 | 1FUBCXCY6EHFR7136 | 2195997 (IN) | SPLASH TRANSPORT INC | 3 | 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 |
|---|---|---|---|---|---|
| cmqlxkk08001jp8trwq4r1sid | Jun 15, 2026 | OK | Injury | 0 | 1 |
| cr_5114325 | Feb 17, 2026 | IN | Tow-Away | 0 | 0 |
| cr_5104448 | Feb 6, 2026 | TN | Tow-Away | 0 | 0 |
| cr_5124365 | Feb 6, 2026 | IL | Tow-Away | 0 | 0 |
| cr_5119934 | Feb 6, 2026 | PA | Tow-Away | 0 | 0 |
| cr_5101506 | Jan 31, 2026 | FL | Tow-Away | 0 | 0 |
| cr_5107130 | Jan 27, 2026 | MI | Tow-Away | 0 | 0 |
| cr_5098201 | Jan 26, 2026 | CA | Injury | 0 | 1 |
| cr_5100153 | Jan 21, 2026 | MI | Tow-Away | 0 | 0 |
| cr_5104392 | Jan 15, 2026 | PA | Injury | 0 | 1 |
Carrier booking & risk tools
Check booking and risk signals for USDOT 1765150 — tools open pre-filled.
Related records
Carrier
SPLASH TRANSPORT INC
USDOT 1765150 · 905 crashes · 2,517 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 1FUBCXCY6EHFR7136
Decode this VIN for make, model, year, and recall data.
State
Crashes in West Virginia
Statewide crash records.
Agency
SPLASH TRANSPORT INC
Crashes reported by this law-enforcement agency.
City
Crashes in GLENWOOD, 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.