Crash Record OH0236047955
FMCSA crash record in LIBERTY (TOWNSHIP OF) on Mar 27, 2023.
What happened
On March 27, 2023, FMCSA recorded an injury crash with one person hurt in LIBERTY (TOWNSHIP OF), Ohio. The vehicle was operated by VELVET ICE CREAM COMPANY (USDOT 349027). Recorded conditions: 1 / 1 / 1 pavement. Reported by VELVET ICE CREAM COMPANY, FMCSA reference OH0236047955.
Carrier pattern note
This is the carrier's 9 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: 199 crashes occurred in the same city in the past 24 months.
This carrier's crash pattern
Derived from the carrier's full crash history.
Geographic context
How this crash sits in its setting.
Within LIBERTY (TOWNSHIP OF), Ohio, 199 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- UNKNOWN · 5 reports
- SCHNEIDER NATIONAL CARRIERS INC · 2 reports
- OLENTANGY LOCAL SCHOOLS · 2 reports
Contributing factors
What the responding officer recorded.
- Light
- 1
- 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 #:
- OH0236047955
- Date:
- Mar 27, 2023
- Time:
- 1055
- State:
- Ohio
- City:
- LIBERTY (TOWNSHIP OF)
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 1
- Carrier (USDOT):
- VELVET ICE CREAM COMPANY (349027)
Vehicles / units involved
1 commercial motor vehicle(s) in this crash.
| # | Config | Cargo Type | VIN | Plate | Carrier | GVW | HazMat |
|---|---|---|---|---|---|---|---|
| 1 | 7 | — | 3ALACWFC8KDKP9227 | PFX4495 (OH) | VELVET ICE CREAM COMPANY | 2 | No |
Crash event
Event sequence description.
2:1:NONCOLLISION:RAN OFF ROAD;1:6:NONCOLLISION:EXPLOSION OR FIRE;3:6:NONCOLLISION:EXPLOSION OR FIRE;4:18:COLLISION INVOLVING FIXED OBJECT
Other crashes by this carrier
10 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| cr_5074785 | Nov 17, 2025 | IN | Tow-Away | 0 | 0 |
| cr_4945406 | May 19, 2025 | KY | Injury | 0 | 2 |
| cr_4955419 | May 2, 2025 | IN | Tow-Away | 0 | 0 |
| cr_4723351 | Mar 15, 2024 | IN | Tow-Away | 0 | 0 |
| cr_4724911 | Mar 13, 2024 | OH | Tow-Away | 0 | 0 |
| cr_4902798 | Feb 24, 2024 | KY | Tow-Away | 0 | 0 |
| cr_4648536 | Oct 30, 2023 | OH | Tow-Away | 0 | 0 |
| cr_4595796 | Jul 19, 2023 | IN | Tow-Away | 0 | 0 |
| cr_4573590 | Jun 13, 2023 | KY | Tow-Away | 0 | 0 |
| cr_4564334 | Apr 21, 2023 | OH | Tow-Away | 0 | 0 |
Related records
How to evaluate a carrier's crash record
- Look at frequency, not any single crash. A single crash record rarely tells you anything decisive about a carrier. Pull the carrier's full multi-year crash list and look at the rate over time — clusters and trends matter more than any one event.
- Calculate crashes per power unit when data is available. Divide the 24-month crash count by the carrier's reported power units. A rate of one crash per power unit per year is high; a rate of one crash per ten power units per year is closer to industry baseline. Skip this step when power_units is missing or zero — the rate is meaningless without it.
- Filter for fault-attributed crashes. FMCSA crash records do not flag fault. To distinguish preventable from non-preventable, check whether the carrier requested a Preventability Determination through DataQs and what FMCSA ruled. Only the preventable crashes are a clean signal of carrier or driver behavior.
- Compare against fleet-size peers. Crash counts cannot be compared directly between fleets of different sizes. Use the SMS Crash Indicator percentile, or compare the carrier's crashes-per-power-unit rate against the median for its fleet-size cohort. A 50-truck carrier with 4 crashes in 24 months looks very different from a 5-truck carrier with the same count.
- Cross-reference with the SMS BASIC Crash Indicator. FMCSA's Safety Measurement System publishes a Crash Indicator percentile when the carrier has enough crashes and exposure to score. A score in the 65th percentile or higher triggers federal intervention thresholds. Always sanity-check raw crash counts against the percentile before drawing conclusions.
Frequently asked questions about FMCSA crash records
What does this crash report tell me about the carrier? ▾
Was this crash the carrier's fault? ▾
How does this crash affect the carrier's safety scores? ▾
Will this crash show up on the carrier's CSA SMS scores? ▾
How do I check the carrier's full crash history? ▾
What if details look wrong — how do I correct an FMCSA crash record? ▾
Data sources & freshness
TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.
Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.