Crash Record CA0009700814

FMCSA crash record in SAN BERNARDINO on May 10, 2024.

Injury Federal Recordable Bus

What happened

On May 10, 2024, FMCSA recorded an injury crash with one person hurt in SAN BERNARDINO, California. The vehicle was operated by OMNITRANS (USDOT 2663189). Recorded conditions: 1 / 1 / 1 pavement. Reported by OMNITRANS, FMCSA reference CA0009700814.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

OMNITRANS

Vehicle Type

Bus

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

13 injury · 26 tow-away

Crashes per 100 power units (24 mo)

6.4

20 crashes · 312 units

Days since prior carrier crash

Last on May 8, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 26,858 carriers

Geographic context

How this crash sits in its setting.

Within SAN BERNARDINO, California, 148 other commercial vehicle crashes have been recorded in the past 24 months.

Agencies most active in this area:

OMNITRANS · 12 reports
J B HUNT TRANSPORT INC · 4 reports
FARIAS TOWING INC · 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 #:: CA0009700814
Date:: May 10, 2024
Time:: 1344
State:: California
City:: SAN BERNARDINO
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 3
Carrier (USDOT):: OMNITRANS (2663189)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	4	2	1FDEE4F69KDC40648	1590844 (CA)	OMNITRANS	2	No

Crash event

Event sequence description.

1:13:COLLISION INVOLVING MOTOR VEHICLE IN TRANSPORT

Other crashes by this carrier

10 additional crash record(s) on file.

Record	Date	State	Severity	Injuries
cr_5124204	Feb 22, 2026	CA	Injury	1
cr_5111457	Jan 27, 2026	CA	Injury	1
cr_5095334	Dec 26, 2025	CA	Tow-Away	0
cr_5095840	Dec 6, 2025	CA	Injury	1
cr_5066167	Oct 24, 2025	CA	Tow-Away	0
cr_5085351	Oct 17, 2025	CA	Tow-Away	0
cr_5077611	Oct 7, 2025	CA	Injury	3
cr_5061469	Sep 26, 2025	CA	Tow-Away	0
cr_5060593	Sep 18, 2025	CA	Tow-Away	0
cr_5043990	Sep 14, 2025	CA	Injury	1

Related records

Vehicle

2019 FORD E-450

NHTSA recalls and complaints for this make/model/year.

Carrier

OMNITRANS

USDOT 2663189 · 98 crashes · 136 inspections

Vehicle

VIN: 1FDEE4F69KDC40648

Decode this VIN for make, model, year, and recall data.

State

Crashes in California

Statewide crash records.

Agency

OMNITRANS

Crashes reported by this law-enforcement agency.

City

Crashes in SAN BERNARDINO, 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.