Possible match
Serious collision near Key St
February 6, 2026 · 4:00 AM
- Nissan
- Bicycle
- Key St
- S RIVERSIDE AV
Possible match
Look around the reported crash area
The record identifies this general area, not an exact collision point.
Did you lose a loved one in this crash?
We help families obtain the official collision report and coroner's records, understand the investigation, and learn what legal options may be available to them. If you would like to speak with someone, submit your information and a senior member of our team will contact you personally.
What the source reported
The California Crash Reporting System (CCRS) record places this collision at S Riverside Av / Key St.
CrashGuide reports only what the named agency published. Missing fields are omitted; no fault or cause is inferred.
See complete source detailsTimeline, dispatch log, and record data
Official report details
California Crash Reporting System (CCRS), California Highway Patrol
CCRS is a filed-report archive that matures over time, not a live dispatch feed. This section appears when a report is filed or revised.
- Report number
- 26-00832
- Report version
- 1
- Last revised
- June 20, 2026, 2:31 PM
- Collision type
- rear-end · See collisions of this type
- Recorded outcomes
- 0 people injured · 1 person killed
- Reported location
- S RIVERSIDE AV / KEY ST
Vehicles listed in the police data
Representative illustrations
How the vehicles were moving
- Vehicle 1: proceeding straight
- Vehicle 2: proceeding straight
- Vehicle 3: proceeding straight
- Vehicle 4: proceeding straight
- Vehicle 5: proceeding straight
- Vehicle 6: proceeding straight
Conditions recorded in the report
- Weather
- clear
- Lighting
- dark without street lights
- Road condition
- no unusual road conditions
- Road surface
- dry
- Traffic control
- traffic controls functioning
Vehicle Code factor recorded
The report records Vehicle Code VC 21202A as the primary collision factor, but does not mark it as cited.
The record of a citation does not establish fault, negligence, or a conviction.
Collision history at this intersection
Filed collision-report history
6 CCRS collision reports were recorded here between January 2019 and January 2026, including 3 collisions with injuries recorded.
View the intersection historyResources for families
Obtaining the collision report as next of kin
California limits collision reports to parties of interest. After a death, that includes the next of kin and the representative of the estate. The investigating CHP office can confirm what proof of relationship it requires.
The coroner / medical examiner process
The county coroner or medical examiner conducts a separate examination and issues its own report. These records are typically available to next of kin, and generally take several weeks — longer than the collision report.
Financial assistance
The California Victim Compensation Board (CalVCB) can help eligible families with funeral and burial expenses. Visit the official CalVCB site
Getting the official crash report
The California Crash Reporting System (CCRS), California Highway Patrol supplied the official-report fields shown here. The report number can help identify the record with the reporting agency.
Source record from California Crash Reporting System (CCRS)
CrashGuide reports only what the named agency published. Missing fields are omitted; no fault or cause is inferred.
Nearby incidents
- CCRS recorded a collision at S RIVERSIDE AV / 6TH ST — August 29, 2026, 1:24 AMHit and run
- CCRS recorded a collision at S RIVERSIDE AV / MIGUEL BUSTAMANTE PKWY — March 21, 2025, 4:15 PMCollision — no injuries reported
- CCRS recorded a collision at S RIVERSIDE AV / W AGUA MANSA RD — March 16, 2025, 1:00 PMInjury collision
- CCRS recorded a collision at S RIVERSIDE AV / MIGUEL BUSTAMANTE PKWY — June 25, 2026, 9:08 AMInjury collision
- CCRS recorded a collision at S RIVERSIDE AV / W AGUA MANSA RD — October 21, 2025, 6:58 PMInjury collision
- Collision with possible injuries reported on I-10 near 9th St in Colton — October 9, 2026Collision — injuries unknown