Skip to main content
TruckCodex
Hubs

Crash Record OH0245062426

FMCSA crash record in VANDALIA on Apr 5, 2024.

Injury Federal Recordable

What happened

On April 5, 2024, FMCSA recorded an injury crash with one person hurt in VANDALIA, Ohio. The vehicle was operated by CONTINENTAL EXPRESS INC (USDOT 251206). Recorded conditions: 2 / 1 / 1 pavement. FMCSA reference OH0245062426.

Carrier pattern note

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

Fatalities
0
Injuries
1
Vehicles
2
Carrier
CONTINENTAL EXPRESS INC
USDOT 251206
Vehicle Type
Truck
Severity
Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
32
2 fatal · 8 injury
Crashes per 100 power units (24 mo)
6.4
37 crashes · 580 units
Days since prior carrier crash
6
Last on Mar 30, 2024
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,888 carriers

Geographic context

How this crash sits in its setting.

Within VANDALIA, Ohio, 29 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
2
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 #:
OH0245062426
Date:
Apr 5, 2024
Time:
2111
State:
Ohio
City:
VANDALIA
Fatalities:
0
Injuries:
1
Tow-Away:
No
HazMat:
No
Vehicles:
2
Carrier (USDOT):
CONTINENTAL EXPRESS INC (251206)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
2 9 3 3AKJHHDR5MSMP6993 AAF320 (OH) CONTINENTAL EXPRESS TRACTOR LEASING 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
cmny3ygnr00qgk38vv9qqpay4 Apr 3, 2026 WY Injury 0 1
cmny3yh9g018ek38v52njtlxw Mar 31, 2026 OH Injury 0 1
cr_5118754 Mar 13, 2026 OH Tow-Away 0 0
cr_5126905 Jan 21, 2026 WI Tow-Away 0 0
cr_5080568 Dec 9, 2025 TX Injury 0 2
cr_5070770 Dec 4, 2025 OH Tow-Away 0 0
cr_5069048 Nov 26, 2025 MI Tow-Away 0 0
cr_5062312 Nov 9, 2025 TX Tow-Away 0 0
cr_5037122 Oct 3, 2025 NC Injury 0 1
cr_5044534 Sep 29, 2025 MI Tow-Away 0 0

Carrier booking & risk tools

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

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

Related records

Carrier
CONTINENTAL EXPRESS INC
USDOT 251206 · 485 crashes · 1,167 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: 3AKJHHDR5MSMP6993
Decode this VIN for make, model, year, and recall data.
State
Crashes in Ohio
Statewide crash records.
City
Crashes in VANDALIA, OH
All crashes on file for this city.
Station
IR 75
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.