Crash Record CA3300030126

FMCSA crash record in JURUPA VALLEY on May 23, 2025.

Injury Federal Recordable

What happened

On May 23, 2025, FMCSA recorded an injury crash with one person hurt in JURUPA VALLEY, California. The vehicle was operated by MAERSK LOGISTICS & SERVICES USA INC (USDOT 516243). Recorded conditions: 1 / 1 / 1 pavement. Reported by PERFORMANCE TEAM LOGISTICS LLC, FMCSA reference CA3300030126.

Carrier pattern note

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

Fatalities

Injuries

Vehicles

Carrier

MAERSK LOGISTICS & SERVICES USA INC

Vehicle Type

Truck

Severity

Injury

This carrier's crash pattern

Derived from the carrier's full crash history.

Carrier crashes (24 mo)

8 injury · 12 tow-away

Crashes per 100 power units (24 mo)

0.6

8 crashes · 1,239 units

Days since prior carrier crash

204

Last on Oct 31, 2024

Vs fleet-size peers

above the median

Cohort median 0.0 · 3,847 carriers

Geographic context

How this crash sits in its setting.

Within JURUPA VALLEY, California, 125 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 #:: CA3300030126
Date:: May 23, 2025
Time:: 1703
State:: California
City:: JURUPA VALLEY
Fatalities:: 0
Injuries:: 1
Tow-Away:: Yes
HazMat:: No
Vehicles:: 2
Carrier (USDOT):: MAERSK LOGISTICS & SERVICES USA INC (516243)

Vehicles / units involved

1 commercial motor vehicle(s) in this crash.

#	Config	Cargo Type	VIN	Plate	Carrier	GVW	HazMat
1	9	98	3HSDZAPR0MN374632	2994349 (IN)	PERFORMANCE TEAM LOGISTICS LLC	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	Injuries
cr_5125858	Mar 16, 2026	SC	Injury	1
cr_5121021	Mar 13, 2026	OK	Tow-Away	0
cr_5098826	Jan 11, 2026	CA	Injury	2
cr_4991092	Jul 16, 2025	CA	Tow-Away	0
cr_4990814	Jun 20, 2025	CA	Injury	1
cr_4990716	May 23, 2025	CA	Tow-Away	0
cr_4850305	Oct 31, 2024	CA	Tow-Away	0
cr_4817121	Sep 18, 2024	CA	Injury	2
cr_5003039	Jun 27, 2024	NJ	Injury	1
cr_4784223	Jun 18, 2024	CA	Tow-Away	0

Related records

Carrier

MAERSK LOGISTICS & SERVICES USA INC

USDOT 516243 · 125 crashes · 567 inspections

Vehicle

VIN: 3HSDZAPR0MN374632

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

State

Crashes in California

Statewide crash records.

Agency

PERFORMANCE TEAM LOGISTICS LLC

Crashes reported by this law-enforcement agency.

City

Crashes in JURUPA VALLEY, 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.