Skip to main content
TruckCodex
Hubs

Crash Record CA3702303286

FMCSA crash record in RICHMOND on Oct 22, 2023.

Fatal Federal Recordable

What happened

On October 22, 2023, FMCSA recorded a fatal crash that resulted in one death in RICHMOND, California. The vehicle was operated by JEOMEL TRANSPORTATION LLC (USDOT 2856395). Recorded conditions: 2 / 2 / 2 pavement. Reported by JEOMEL TRANSPORTATION LLC, FMCSA reference CA3702303286.

Geographic note

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

Fatalities
1
Injuries
2
Vehicles
6
Carrier
JEOMEL TRANSPORTATION LLC
USDOT 2856395
Vehicle Type
Truck
Severity
Fatal

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)
1
1 fatal · 1 injury
Crashes per 100 power units (24 mo)
37.5
3 crashes · 8 units
Days since prior carrier crash
1,530
Last on Aug 14, 2019
Vs fleet-size peers
above the median
Cohort median 0.0 · 315,833 carriers

Geographic context

How this crash sits in its setting.

Within RICHMOND, California, 26 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
2
Road surface
2

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 #:
CA3702303286
Date:
Oct 22, 2023
Time:
0554
State:
California
City:
RICHMOND
Fatalities:
1
Injuries:
2
Tow-Away:
Yes
HazMat:
No
Vehicles:
6
Carrier (USDOT):
JEOMEL TRANSPORTATION LLC (2856395)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

# Config Cargo Type VIN Plate Carrier GVW HazMat
1 5 3 JL6CRK1A5FK000392 76857S1 (CA) JEOMEL TRANSPORTATION LLC 2 No

Crash event

Event sequence description.

1:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;4:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;3:20:COLLISION INVOLVING OTHER MOVABLE OBJECT;2:20:COLLISION INVOLVING OTHER MOVABLE OBJECT

Other crashes by this carrier

5 additional crash record(s) on file.

Record Date State Severity Fatalities Injuries
cr_5025272 Aug 8, 2025 CA Tow-Away 0 0
cr_4922573 Feb 26, 2025 CA Tow-Away 0 0
cr_4870761 Nov 13, 2024 CA Injury 0 2
cr_4771978 May 28, 2024 CA Tow-Away 0 0
cr_3839437 Aug 14, 2019 CA Injury 0 1

Carrier booking & risk tools

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

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

Related records

Vehicle
2015 MITSUBISHI FUSO FEC92S
NHTSA recalls and complaints for this make/model/year.
Carrier
JEOMEL TRANSPORTATION LLC
USDOT 2856395 · 6 crashes · 62 inspections
Safety
Carrier inspections
Roadside inspection history for this USDOT.
Vehicle
VIN: JL6CRK1A5FK000392
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
JEOMEL TRANSPORTATION LLC
Crashes reported by this law-enforcement agency.
City
Crashes in RICHMOND, CA
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.