CrashGuideCall a CG expertEspañol
Menu

Possible match

Injury collision

Possible injury collision in San Leandro

October 8, 2026 · 6:50 AM

  • San Leandro

Visual location check

Reported crash location

Use the road shape and nearby landmarks to check this record.

Street-level and place imagery is for location context and may have been captured before or after this incident.

Were you involved in this crash?

We can help you get the official CHP report for incident 261008GG0381

Were you or a family member injured?

Attorney Advertising Disclosure. CrashGuide is owned and operated by ME Lawyers, APLC. If you submit this form, your information will be shared with ME Lawyers, APLC, a California personal injury law firm, which may contact you about your request and about legal services. Submitting this form does not create an attorney-client relationship and does not obligate you to hire any lawyer. Prior results do not guarantee a similar outcome. You do not need to use this service to obtain a collision report. You may request your report directly from the investigating agency at any time, free of any service beyond the agency's own fees, using the agency information on this page. ME Lawyers, APLC, 11110 Ohio Ave Suite #201, Los Angeles, CA 90025. Responsible attorney: Michael Emrani (CA Bar No. 313449).

No cost. Reports are typically available 7–14 days after a crash.

Call (213) 314-3031 ME Lawyers, APLC · answered 24/7. No cost to ask.

Not mine — find another crash

What the source reported

At approximately 6:50 AM, dispatch information described a collision involving a bicyclist and a pedestrian in San Leandro. A motorcycle was reported involved. A vehicle was reported on an off-ramp. Dispatch notes indicate an ambulance and the fire department responded. A tow was requested. Dispatch notes indicate the collision blocked at least one lane.

CHP corrected this record after the first report. The summary reflects the corrected account.

Written from the CHP dispatch record below. Dispatch notes reflect what was reported at the time and can be incomplete or later corrected.

See complete source detailsTimeline, dispatch log, and record data
  • on an off-ramp
  • motorcycle involved
  • bicyclist involved

What happened, step by step

  1. 6:52 AMVehicle information reportedDispatch notes describe a black motorcycle.
  2. 6:53 AMVehicle position reportedDispatch notes describe a vehicle on an on-ramp.
  3. 6:53 AMVehicle information reportedDispatch notes describe a motorcycle.
  4. 6:54 AMVehicle position reportedDispatch notes describe a vehicle on an on-ramp.
  5. 6:54 AMVehicle information reportedDispatch notes describe a motorcycle.
  6. 6:55 AMMedical responseAs logged1039 1141
  7. 6:55 AMVehicle position reportedDispatch notes describe a vehicle on an on-ramp.
  8. 6:56 AMVehicle position reportedA responding unit reported a vehicle on an on-ramp.
  9. 6:56 AMMedical responseAs logged1039 1141
  10. 6:57 AMDispatch updateAs loggedBC LN 26
  11. 6:57 AMTraffic hazard reportedAs loggedTMC // 1125 IN THE SLOW LANE TWO MCS AND AND SILVER SUV
  12. 6:58 AMCorrection issuedAs logged1039 ACRECC // CPYS ONE IN THE SAME and CORR 1020
  13. 7:01 AMFire department contactedAs loggedALAMEDA FIRE CPYS POSS 1020S
  14. 7:03 AMCorrection issuedAs loggedA25-074 W/ VIS // CORR 1020 : NB 238 TO SB 880 CON #2 LN
  15. 7:04 AMUnits respondingAs loggedA25-020 1097
  16. 7:04 AMLanes affectedAs loggedA25-074 1097 BLKING #2
  17. 7:06 AMFire department contactedDispatch notes indicate a motorcycle.
  18. 7:06 AMMedical responseAs loggedA25-074 2 VEH 1181
  19. 7:12 AMUnits respondingAs loggedA25-073 1097
  20. 7:26 AMTow requestedA responding unit reported a motorcycle.
  21. 7:27 AMTow requestedA responding unit reported a motorcycle and a motorcycle.
  22. 7:27 AM2 routine dispatch entries (units, tow rotation, acknowledgements)
  23. 7:47 AMVehicle position reportedA responding unit reported a vehicle on an off-ramp.
  24. 7:50 AMUnits respondingAs loggedA25-073 A25-073 1097 EM: 850 @ 0750
  25. 7:50 AMUnits respondingAs loggedA25-020 A25-020 1097 EM: 599 @ 0750
  26. 7:50 AM1 routine dispatch entry (units, tow rotation, acknowledgements)
  27. 8:24 AMMedical responseAs loggedA25-074 2 VEH 1181
  28. 8:36 AMScene clearedAs logged[FSP] has closed their incident [261008GGFSP0029]

Every entry in the dispatch record below is represented here.

Dispatch log

59 entries

Combined from more than one CHP dispatch record: 261008GG0381 · 261008GGFSP0029

  1. +0:0006:53PER DUPE , A ST ONR TO SB 880
  2. +0:0006:53MC DRVR SITTING ON RHS
  3. +0:0006:53PER DUPE , A ST ONR TO SB 880
  4. +0:0006:53MC DRVR SITTING ON RHS
  5. +0:0006:53:47BLK MC VS WHI SUV / BLKG ONR / MC SWERVED TO AVOID PED WALKING W/ E BIKE AND TC'D W/ SUV
  6. +0:0006:53:47BLK MC VS WHI SUV / BLKG ONR / MC SWERVED TO AVOID PED WALKING W/ E BIKE AND TC'D W/ SUV
  7. +0:0106:54BC LN 12 // 25-74 CPYS , CHKING A ONR TO SB 1ST
  8. +0:0106:54MC AND VEH BLKG LN 2 ON CON
  9. +0:0106:54BC LN 12 // 25-74 CPYS , CHKING A ONR TO SB 1ST
  10. +0:0106:54MC AND VEH BLKG LN 2 ON CON
  11. +0:0206:551039 1141
  12. +0:0206:551039 1141
  13. +0:0206:55ANI/ALI ON DUPE CALL MAPPING SB 880 X HESP ONR
  14. +0:0206:55ANI/ALI ON DUPE CALL MAPPING SB 880 X HESP ONR
  15. +0:0306:5625-74 CPYS LN 19 // A ST ONR TO SB 880 IS CLR
  16. +0:0306:561039 1141
  17. +0:0306:5625-74 CPYS LN 19 // A ST ONR TO SB 880 IS CLR
  18. +0:0306:561039 1141
  19. +0:0406:57BC LN 26
  20. +0:0406:57TMC // 1125 IN THE SLOW LANE TWO MCS AND AND SILVER SUV
  21. +0:0406:57BC LN 26
  22. +0:0406:57TMC // 1125 IN THE SLOW LANE TWO MCS AND AND SILVER SUV
  23. +0:0506:581039 ACRECC // CPYS ONE IN THE SAME and CORR 1020
  24. +0:0506:581039 ACRECC // CPYS ONE IN THE SAME and CORR 1020
  25. +0:0807:01ALAMEDA FIRE CPYS POSS 1020S
  26. +0:0807:01ALAMEDA FIRE CPYS POSS 1020S
  27. +0:1007:03A25-074 W/ VIS // CORR 1020 : NB 238 TO SB 880 CON #2 LN
  28. +0:1007:03A25-074 W/ VIS // CORR 1020 : NB 238 TO SB 880 CON #2 LN
  29. +0:1107:04A25-020 1097
  30. +0:1107:04A25-074 1097 BLKING #2
  31. +0:1107:04A25-020 1097
  32. +0:1107:04A25-074 1097 BLKING #2
  33. +0:1307:06HAY FIRE LL UTL// NOW ADV FOUND THE MC RIDER// 1182 NOW GOING 98
  34. +0:1307:06A25-074 2 VEH 1181
  35. +0:1307:06HAY FIRE LL UTL// NOW ADV FOUND THE MC RIDER// 1182 NOW GOING 98
  36. +0:1307:06A25-074 2 VEH 1181
  37. +0:1907:12A25-073 1097
  38. +0:1907:12A25-073 1097
  39. +0:3307:26A25-020 1185 FOR MC
  40. +0:3307:26A25-020 1185 FOR MC
  41. +0:3407:27A25-020 MC HAS BO REAR TIRE // FSP MOVING MC OFF TO A JWO 880 // HAVE THE 1185 RESPOND THERE
  42. +0:3407:27A25-020 MC HAS BO REAR TIRE // FSP MOVING MC OFF TO A JWO 880 // HAVE THE 1185 RESPOND THERE
  43. +0:3407:271021 SAN LEANDRO TOW X2 - RINGS BO , YOU CALL CANNOT BE COMPLETED AS DIALED - SKIPPING
  44. +0:3407:271021 SAN LEANDRO TOW X2 - RINGS BO , YOU CALL CANNOT BE COMPLETED AS DIALED - SKIPPING
  45. +0:3507:281039 US TOWING 510-352-8085
  46. +0:3507:281039 US TOWING 510-352-8085
  47. +0:5407:47A25-020 1148X X2 TO A ST OFR BM: 597 @ 0747
  48. +0:5407:47A25-020 1148X X2 TO A ST OFR BM: 597 @ 0747
  49. +0:5407:47A25-073 1148 TO A ST OFR BM: 848 @ 0747
  50. +0:5407:47A25-073 1148 TO A ST OFR BM: 848 @ 0747
  51. +0:5707:50A25-073 A25-073 1097 EM: 850 @ 0750
  52. +0:5707:50A25-020 A25-020 1097 EM: 599 @ 0750
  53. +0:5707:50BC LN 51 / 25-20 CPYS , WILL MAKE CONT W/ THEM
  54. +0:5707:50A25-073 A25-073 1097 EM: 850 @ 0750
  55. +0:5707:50A25-020 A25-020 1097 EM: 599 @ 0750
  56. +0:5707:50BC LN 51 / 25-20 CPYS , WILL MAKE CONT W/ THEM
  57. +1:3108:24A25-074 2 VEH 1181
  58. +1:3108:24A25-074 2 VEH 1181
  59. +1:4308:36has closed their incident [261008GGFSP0029]

About this information.

This page is generated automatically from publicly available California Highway Patrol computer-aided dispatch (CAD) data. Dispatch information is preliminary and unverified. It may contain errors, and it may change as an incident develops. This page is not an official collision report, and no official collision report is available on this website. Dispatch data does not identify any person involved in this incident, and no individuals are identified on this page. To request the official collision report, follow the agency instructions below.

About the accuracy of this page

Nearby incidents

Related guides

All crashes in Alameda · Find your crash.