Crash Record OH0235230642

FMCSA crash record in HUDSON on Dec 11, 2023.

Injury Federal Recordable

What happened

On December 11, 2023, FMCSA recorded an injury crash with 7 people hurt in HUDSON, Ohio. The vehicle was operated by B & T EXPRESS INC (USDOT 285442). Recorded conditions: 2 / 4 / 4 pavement. FMCSA reference OH0235230642.

Carrier pattern note

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

Geographic note

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

Fatalities

Injuries

Vehicles

Carrier

B & T EXPRESS INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

1 fatal · 16 injury

Crashes per 100 power units (24 mo)

6.4

19 crashes · 296 units

Days since prior carrier crash

Last on Nov 22, 2023

Vs fleet-size peers

above the median

Cohort median 0.0 · 27,005 carriers

Geographic context

How this crash sits in its setting.

Within HUDSON, Ohio, 33 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

AFS WORLD LLC · 1 reports
BM TRANSFER · 1 reports
AA SANITATION · 1 reports

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 #:: OH0235230642
Date:: Dec 11, 2023
Time:: 0407
State:: Ohio
City:: HUDSON
Fatalities:: 0
Injuries:: 7
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: B & T EXPRESS INC (285442)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
2	9	3	1XPHD49X0BD121975	PWD6791 (OH)	B & T EXPRESS 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	Injuries
cmqkg784n00cnp8fyqliwhtl5	Jun 11, 2026	AL	Tow-Away	0
cr_5112392	Feb 20, 2026	OH	Injury	1
cr_5126732	Jan 20, 2026	OH	Injury	1
cr_5093968	Jan 5, 2026	OH	Injury	1
cr_5076726	Dec 11, 2025	PA	Tow-Away	0
cr_5069759	Nov 26, 2025	NJ	Tow-Away	0
cr_5059872	Nov 10, 2025	OH	Tow-Away	0
cr_5052705	Nov 4, 2025	TN	Tow-Away	0
cr_5042079	Sep 21, 2025	TX	Tow-Away	0
cr_5022725	Aug 25, 2025	MS	Tow-Away	0

Related records

Carrier

B & T EXPRESS INC

USDOT 285442 · 322 crashes · 847 inspections

Safety

Carrier inspections

Roadside inspection history for this USDOT.

Vehicle

VIN: 1XPHD49X0BD121975

Decode this VIN for make, model, year, and recall data.

State

Crashes in Ohio

Statewide crash records.

City

Crashes in HUDSON, 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.