Skip to main content
TruckCodex
Hubs

Crash Record OH0225014037

FMCSA crash record in OXFORD (TOWNSHIP OF) on Jan 23, 2022.

Injury Federal Recordable

What happened

On January 23, 2022, FMCSA recorded an injury crash with 9 people hurt in OXFORD (TOWNSHIP OF), Ohio. The vehicle was operated by DAALO EXPRESS LLC (USDOT 2485169). Recorded conditions: 1 / 4 / 4 pavement. FMCSA reference OH0225014037.

Geographic note

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

Fatalities
0
Injuries
9
Vehicles
50
Carrier
DAALO EXPRESS LLC
USDOT 2485169
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 injury · 1 tow-away
Crashes per 100 power units (24 mo)
0.0
0 crashes · 3 units
Prior carrier crash
—
No earlier crash on file
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,577,237 carriers

Geographic context

How this crash sits in its setting.

Within OXFORD (TOWNSHIP OF), Ohio, 40 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
1
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 #:
OH0225014037
Date:
Jan 23, 2022
Time:
1330
State:
Ohio
City:
OXFORD (TOWNSHIP OF)
Fatalities:
0
Injuries:
9
Tow-Away:
Yes
HazMat:
No
Vehicles:
50
Carrier (USDOT):
DAALO EXPRESS LLC (2485169)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
37 9 3 4V4NC9EH0CN537396 PWS9796 (OH) DAALO EXPRESS LLC 3 No

Crash event

Event sequence description.

1:21:COLLISION INVOLVING UNKNOWN MOVABLE OBJECT

Other crashes by this carrier

1 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_4642767 Oct 22, 2023 AR Tow-Away 0 0

Carrier booking & risk tools

Check booking and risk signals for USDOT 2485169 — tools open pre-filled.

Book / don't book Insurance check Cancel desk Chameleon check Safety benchmark

Related records

Vehicle
2012 VOLVO TRUCK VNL
NHTSA recalls and complaints for this make/model/year.
Carrier
DAALO EXPRESS LLC
USDOT 2485169 · 2 crashes · 18 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 4V4NC9EH0CN537396
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in OXFORD (TOWNSHIP OF), OH
All crashes on file for this city.
Station
IR 80
Weigh / inspection station matching this crash location.
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.