Skip to main content
TruckCodex
Hubs

Crash Record OH0233106707

FMCSA crash record in COLUMBUS on May 16, 2023.

Injury Federal Recordable

What happened

On May 16, 2023, FMCSA recorded an injury crash with one person hurt in COLUMBUS, Ohio. The vehicle was operated by FEDERAL EXPRESS CORPORATION (USDOT 86876). Recorded conditions: 1 / 1 / 1 pavement. FMCSA reference OH0233106707.

Carrier pattern note

This is the carrier's 379 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: 762 crashes occurred in the same city in the past 24 months.

Fatalities
0
Injuries
1
Vehicles
2
Carrier
FEDERAL EXPRESS CORPORATION
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
379
8 fatal · 138 injury
Crashes per 100 power units (24 mo)
1.7
2,413 crashes · 138,481 units
Days since prior carrier crash
1
Last on May 15, 2023
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,858 carriers

Geographic context

How this crash sits in its setting.

Within COLUMBUS, Ohio, 762 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
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 #:
OH0233106707
Date:
May 16, 2023
Time:
1731
State:
Ohio
City:
COLUMBUS
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
FEDERAL EXPRESS CORPORATION (86876)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 12 1FUBGDDV9ELFN7198 F451HX (TN) FEDEX EXPRESS CORPORATION 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
cmup2ni6p00afl4z8zcsv3e54 Sep 21, 2026 OH Injury 0 2
cmup2ni6q00ajl4z8v44okx7q Sep 21, 2026 ME Tow-Away 0 0
cmu507cav000hpmtod4z1831t Sep 13, 2026 ME Tow-Away 0 0
cmu507ces005rpmtow13xvjpw Sep 9, 2026 NJ Tow-Away 0 0
cmtzbpprh000zpmsr5qlx21nw Sep 8, 2026 VA Injury 0 1
cmtqq5agv001zpmkttbo81660 Sep 2, 2026 NJ Injury 0 2
cmtmftnpq002vpmdxdrb4lbq3 Aug 28, 2026 KY Tow-Away 0 0
cmtl0dt2a002zpm66q8qu1cl3 Aug 27, 2026 NC Tow-Away 0 0
cmtfchmfj0009pmjnybpu3leu Aug 26, 2026 OK Tow-Away 0 0
cmtdwm2p5000ppmb9mlqlgnkh Aug 24, 2026 NJ Tow-Away 0 0

Related records

Carrier
FEDERAL EXPRESS CORPORATION
USDOT 86876 · 9,257 crashes · 26,832 inspections
Vehicle
VIN: 1FUBGDDV9ELFN7198
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in COLUMBUS, 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.