Possible match

Injury collision

Possible injury collision near E Brundage Ln

  • E Brundage Ln
  • Bakersfield

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.

More ways to confirm this location

Recognize anything nearby?

A few recognizable places can help confirm the scene.

Were you involved in this crash?

We can help you get the official CHP report for incident 260813BF0018

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 1:46 AM, a traffic collision was reported near E Brundage Ln in Bakersfield. One vehicle was reported overturned. Dispatch notes indicate the fire department responded. A tow was requested.

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
  • rollover reported
  • fire department responded
  • tow requested

What happened, step by step

  1. 1:47 AMTraffic hazard reportedAs logged1125 IN NB LNS
  2. 1:47 AMVehicle information reportedAs loggedVEH ON ITS SIDE / UNK DESC
  3. 1:48 AMAnother agency contactedAs logged1039 ECC
  4. 1:49 AM1 routine dispatch entry (units, tow rotation, acknowledgements)
  5. 1:49 AMAnother agency contactedAs logged1039 C2 FOR SPLIT
  6. 1:50 AM2 routine dispatch entries (units, tow rotation, acknowledgements)
  7. 1:50 AMAnother agency contactedAs logged1039 DAVES FLEET 661-322-8255
  8. 1:52 AMAnother agency contactedAs logged1039 ECC
  9. 1:53 AMScene clearedAs logged1039 C2 / ADVSD 1022 C3 HANDLE
  10. 1:53 AMAnother agency contactedAs logged1039 C1 // WILL ENTER CALL
  11. 2:04 AMFire department contactedAs logged1039 ECC // FIRE 97 VEH ON ITS SIDE JNO I/S

Every entry in the dispatch record below is represented here.

Dispatch log

12 entries
  1. +0:0001:471125 IN NB LNS
  2. +0:0001:47VEH ON ITS SIDE / UNK DESC
  3. +0:0101:481039 ECC
  4. +0:0201:4991C CPYS EXTENED FROM DELANO -- START 1185 IN THE BLIND
  5. +0:0201:491039 C2 FOR SPLIT
  6. +0:0301:50Tow Request Cancelled: 1483737
  7. +0:0301:50Tow Request Cancelled: 1483738
  8. +0:0301:501039 DAVES FLEET 661-322-8255
  9. +0:0501:521039 ECC
  10. +0:0601:531039 C2 / ADVSD 1022 C3 HANDLE
  11. +0:0601:531039 C1 // WILL ENTER CALL
  12. +0:1702:041039 ECC // FIRE 97 VEH ON ITS SIDE JNO I/S

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