Possible match

Injury collision

Possible injury collision near Rudgear Rd on-ramp

  • Rudgear Rd on-ramp
  • I-680
  • Walnut Creek

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 260812GG2274

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:21 PM, a traffic collision was reported on I-680 northbound near Rudgear Rd Onr in Walnut Creek. Dispatch notes indicate an ambulance responded. Dispatch notes indicate the collision blocked at least one lane.

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

What happened, step by step

  1. 6:07 PMCollision reportedAs logged[2] OCC OO VEH
  2. 6:07 PMDispatch updateAs logged[1] DARK 4D SD CD
  3. 6:23 PMLanes affectedAs loggedBLKG SLOW LNS
  4. 6:23 PMDispatch updateAs logged[3] RP IS UNSURE WHAT HAPPENED / SOUNDED LIKE A POSS TC
  5. 6:26 PMMedical responseAs logged1039 1141
  6. 6:26 PMVehicle information reportedAs logged[5] XRAY IN VEH
  7. 6:26 PMLanes affectedAs logged[3] BLKING SLO LN
  8. 6:28 PMScene clearedAs loggedhas closed their incident [260812GG2220]
  9. 6:29 PMScene clearedAs logged[FSP] has closed their incident [260812GGFSP0153]
  10. 6:34 PMScene clearedAs logged1039 1141 TO 1022
  11. 6:34 PMScene clearedAs logged[FSP] has closed their incident [260812GGFSP0157]

Every entry in the dispatch record below is represented here.

Dispatch log

20 entries

Combined from more than one CHP dispatch record: 260812GG2274 · 260812GGFSP0157

  1. +0:0018:23[3] BLKG SLOW LNS
  2. +0:0018:23BLKG SLOW LNS
  3. +0:0318:261039 1141
  4. +0:0318:261039 1141
  5. +0:0418:27:18XRAY IN VEH
  6. +0:0418:27:18BLKING SLO LN
  7. +0:0418:27:18XRAY IN VEH
  8. +0:0418:27:18BLKING SLO LN
  9. +0:0418:27:40OCC OO VEH
  10. +0:0418:27:40DARK 4D SD CD
  11. +0:0418:27:40OCC OO VEH
  12. +0:0418:27:40DARK 4D SD CD
  13. +0:0518:28has closed their incident [260812GG2220]
  14. +0:0518:28has closed their incident [260812GG2220]
  15. +0:0518:28:01RP IS UNSURE WHAT HAPPENED / SOUNDED LIKE A POSS TC
  16. +0:0518:28:01RP IS UNSURE WHAT HAPPENED / SOUNDED LIKE A POSS TC
  17. +0:0618:29has closed their incident [260812GGFSP0153]
  18. +0:0618:29has closed their incident [260812GGFSP0153]
  19. +0:1118:341039 1141 TO 1022
  20. +0:1118:34has closed their incident [260812GGFSP0157]

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