TruckCodex
Hubs

Crash Record OH0255014142

FMCSA crash record in MONTGOMERY (TOWNSHIP OF) on Jan 19, 2025.

Tow-Away Federal Recordable

What happened

On January 19, 2025, FMCSA recorded a tow-away crash with no reported injuries in MONTGOMERY (TOWNSHIP OF), Ohio. The vehicle was operated by BARR-NUNN TRANSPORTATION LLC (USDOT 261978). Recorded conditions: 2 / 4 / 4 pavement. FMCSA reference OH0255014142.

Carrier pattern note

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

Geographic note

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

Fatalities
0
Injuries
0
Vehicles
2
Carrier
BARR-NUNN TRANSPORTATION LLC
Vehicle Type
Truck
Severity
Tow-Away

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
56
2 fatal · 16 injury
Crashes per 100 power units (24 mo)
8.4
53 crashes · 629 units
Days since prior carrier crash
2
Last on Jan 17, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,848 carriers

Geographic context

How this crash sits in its setting.

Within MONTGOMERY (TOWNSHIP OF), Ohio, 25 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
4
Road surface
4

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 #:
OH0255014142
Date:
Jan 19, 2025
Time:
2113
State:
Ohio
City:
MONTGOMERY (TOWNSHIP OF)
Fatalities:
0
Injuries:
0
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
BARR-NUNN TRANSPORTATION LLC (261978)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHHDR2NSNA3127 FR0263 (IA) BARR-NUNN TRANSPORTATION LLC 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
cmryiu0wf001fpehreakl32y8 Jul 18, 2026 VA Tow-Away 0 0
cmqkg77x7004lp8fys1oyq1xy Jun 13, 2026 WV Injury 0 1
cmny3yh49013sk38v9jm90bqj Apr 1, 2026 IA Tow-Away 0 0
cr_5108901 Feb 19, 2026 OH Injury 0 1
cr_5106457 Feb 13, 2026 TN Injury 0 1
cr_5104607 Feb 4, 2026 VA Injury 0 1
cr_5096813 Jan 30, 2026 OH Tow-Away 0 0
cr_5116976 Jan 28, 2026 MD Injury 0 1
cr_5093909 Jan 11, 2026 OH Injury 0 1
cr_5085912 Jan 5, 2026 TN Tow-Away 0 0

Related records

Carrier
BARR-NUNN TRANSPORTATION LLC
USDOT 261978 · 925 crashes · 814 inspections
Vehicle
VIN: 3AKJHHDR2NSNA3127
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in MONTGOMERY (TOWNSHIP OF), 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.