Crash Record CA0009823865
FMCSA crash record in ROSEVILLE on Aug 15, 2025.
Injury
Federal Recordable
What happened
On August 15, 2025, FMCSA recorded an injury crash with one person hurt in ROSEVILLE, California. The vehicle was operated by FEDERAL EXPRESS CORPORATION (USDOT 86876). Recorded conditions: 1 / 1 / 1 pavement. Reported by FEDERAL EXPRESS CORPORATION, FMCSA reference CA0009823865.
Carrier pattern note
This is the carrier's 2101 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: 44 crashes occurred in the same city in the past 24 months.
Fatalities
0
Injuries
1
Vehicles
5
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)
2,101
51 fatal · 733 injury
Crashes per 100 power units (24 mo)
1.8
2,455 crashes · 138,481 units
Days since prior carrier crash
1
Last on Aug 14, 2025
Vs fleet-size peers
above the median
Cohort median 0.0 · 3,845 carriers
Geographic context
How this crash sits in its setting.
Within ROSEVILLE, California, 44 other commercial vehicle crashes have been recorded in the past 24 months.
Agencies most active in this area:
- CITY OF ROSEVILLE · 3 reports
- ROSEVILLE JOINT UNION HIGH SCHOOL DISTRICT · 2 reports
- A & S TRANSPORT INC · 1 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 #:
- CA0009823865
- Date:
- Aug 15, 2025
- Time:
- 1334
- State:
- California
- City:
- ROSEVILLE
- Fatalities:
- 0
- Injuries:
- 1
- Tow-Away:
- Yes
- HazMat:
- No
- Vehicles:
- 5
- 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 |
|---|---|---|---|---|---|---|---|
| 1 | 5 | — | 4V4N39EH9DN141386 | 2619322 (IN) | FEDERAL EXPRESS CORPORATION | 3 | No |
Other crashes by this carrier
10 additional crash record(s) on file.
| Record | Date | State | Severity | Fatalities | Injuries |
|---|---|---|---|---|---|
| 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 |
| cmtazy7j7001bpmln8osd34ic | Aug 20, 2026 | OH | Injury | 0 | 1 |
| cmt5ony23005fpmdm8265vd2x | Aug 17, 2026 | NJ | Tow-Away | 0 | 0 |
Related records
Carrier
FEDERAL EXPRESS CORPORATION
USDOT 86876 · 9,255 crashes · 26,389 inspections
Vehicle
VIN: 4V4N39EH9DN141386
Decode this VIN for make, model, year, and recall data.
State
Crashes in California
Statewide crash records.
Agency
FEDERAL EXPRESS CORPORATION
Crashes reported by this law-enforcement agency.
City
Crashes in ROSEVILLE, 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.