TruckCodex
Hubs

Crash Record OH0253057285

FMCSA crash record in SPRING VALLEY (TOWNSHIP O on Mar 30, 2025.

Injury Federal Recordable

What happened

On March 30, 2025, FMCSA recorded an injury crash with one person hurt in SPRING VALLEY (TOWNSHIP O, Ohio. The vehicle was operated by GFS TRANSPORT LLC (USDOT 175852). Recorded conditions: 2 / 2 pavement. Reported by GFS TRANSPORT LLC, FMCSA reference OH0253057285.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
1
Carrier
GFS TRANSPORT LLC
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
109
2 fatal · 27 injury
Crashes per 100 power units (24 mo)
3.8
77 crashes · 2,011 units
Days since prior carrier crash
4
Last on Mar 26, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,847 carriers

Geographic context

How this crash sits in its setting.

Within SPRING VALLEY (TOWNSHIP O, Ohio, 6 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
2
Weather
—
Road surface
2

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 #:
OH0253057285
Date:
Mar 30, 2025
Time:
2315
State:
Ohio
City:
SPRING VALLEY (TOWNSHIP O
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
1
Carrier (USDOT):
GFS TRANSPORT LLC (175852)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 12 3AKJHTDV6NDNB3843 3137601 (OH) GFS TRANSPORT LLC 3 No

Crash event

Event sequence description.

1:6:NONCOLLISION:EXPLOSION OR FIRE;2:18:COLLISION INVOLVING FIXED OBJECT

Other crashes by this carrier

10 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cmtazy7kl002npmln1he3tzip Aug 20, 2026 MA Tow-Away 0 0
cmrx2ea5f002dpequmqf3xspo Jul 16, 2026 OH Injury 0 1
cmrn1fcbc006hpez59z2few1a Jul 8, 2026 KY Tow-Away 0 0
cr_5125147 Mar 25, 2026 KY Injury 0 2
cr_5125713 Mar 17, 2026 GA Injury 0 1
cr_5125519 Mar 12, 2026 NC Injury 0 1
cr_5124912 Mar 6, 2026 TX Injury 0 1
cr_5118697 Mar 2, 2026 OH Injury 0 1
cr_5121529 Feb 19, 2026 IN Tow-Away 0 0
cr_5107232 Feb 10, 2026 MI Tow-Away 0 0

Related records

Vehicle
2022 FREIGHTLINER Cascadia
NHTSA recalls and complaints for this make/model/year.
Recall
26V583000
SERVICE BRAKES, AIR:ANTILOCK
Recall
23V299000
ELECTRONIC STABILITY CONTROL (ESC)
Recall
23V238000
STEERING:LINKAGES:TIE ROD ASSEMBLY
Carrier
GFS TRANSPORT LLC
USDOT 175852 · 853 crashes · 1,200 inspections
Vehicle
VIN: 3AKJHTDV6NDNB3843
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
GFS TRANSPORT LLC
Crashes reported by this law-enforcement agency.
City
Crashes in SPRING VALLEY (TOWNSHIP O, OH
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.