Skip to main content
TruckCodex
Hubs

Crash Record OH0215047756

FMCSA crash record in BERLIN (TOWNSHIP OF) on Mar 19, 2021.

Injury Federal Recordable

What happened

On March 19, 2021, FMCSA recorded an injury crash with one person hurt in BERLIN (TOWNSHIP OF), Ohio. The vehicle was operated by SYSCO CLEVELAND INC (USDOT 330684). Recorded conditions: 5 / 1 / 1 pavement. Reported by SYSCO CLEVELAND INC, FMCSA reference OH0215047756.

Carrier pattern note

This is the carrier's 6 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
0
Injuries
1
Vehicles
2
Carrier
SYSCO CLEVELAND INC
USDOT 330684
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
6
2 injury · 6 tow-away
Crashes per 100 power units (24 mo)
3.1
4 crashes · 131 units
Days since prior carrier crash
88
Last on Dec 21, 2020
Vs fleet-size peers
above the median
Cohort median 0.0 · 27,189 carriers

Geographic context

How this crash sits in its setting.

Within BERLIN (TOWNSHIP OF), Ohio, 33 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
5
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 #:
OH0215047756
Date:
Mar 19, 2021
Time:
0747
State:
Ohio
City:
BERLIN (TOWNSHIP OF)
Fatalities:
0
Injuries:
1
Tow-Away:
Yes
HazMat:
No
Vehicles:
2
Carrier (USDOT):
SYSCO CLEVELAND INC (330684)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 9 12 4V4M39DF9JN890308 2561110 (IN) SYSCO CLEVELAND 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
cr_5080017 Dec 20, 2025 OH Tow-Away 0 0
cr_5070379 Nov 10, 2025 OH Injury 0 1
cr_5028246 Aug 27, 2025 OH Tow-Away 0 0
cr_4885802 Jan 27, 2025 OH Tow-Away 0 0
cr_4828749 Oct 14, 2024 OH Tow-Away 0 0
cr_4856486 Oct 9, 2024 OH Injury 0 1
cr_4648576 Oct 26, 2023 OH Injury 0 1
cr_4633395 Sep 27, 2023 OH Tow-Away 0 0
cr_4651694 Jul 1, 2023 OH Tow-Away 0 0
cr_4539265 Apr 5, 2023 OH Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Vehicle
2018 VOLVO TRUCK VNM
NHTSA recalls and complaints for this make/model/year.
Carrier
SYSCO CLEVELAND INC
USDOT 330684 · 65 crashes · 48 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 4V4M39DF9JN890308
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
Agency
SYSCO CLEVELAND INC
Crashes reported by this law-enforcement agency.
City
Crashes in BERLIN (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.