CHP Traffic Incidents

← Back to history
Closed

1179-Trfc Collision-1141 Enrt

📍 Buttonwillow · I5 N / Millux Rd

Sep 20, 10:39 PM · 2d ago

StatusClosed
Duration33m
First seenSep 20, 10:44 PM
Last updateSep 20, 11:08 PM
Location desc.NB I5 JSO MILLUX

✉ Sign up for email alerts

Open in Google Maps ↗

Dispatch log

  1. Sep 20 2026 11:07PM[36] B117-502B RECONT RP ADV NEG ON O/T VEH SPIN OUT ONLY UTL [Shared]
  2. Sep 20 2026 11:00PM[35] [Notification] [CHP]-PER ECC -- FIRE DID NOT RESPOND DUE TO VEH FLEEING AREA [Shared]
  3. Sep 20 2026 10:59PM[34] 117-502B CHECK IF FIRE ON SCENE [Shared]
  4. Sep 20 2026 10:46PM[31] [Notification] [CHP]-ECC ADV PER ADL RP -- VEH NOW LEAVING SCENE ON DIRT RD -- UNK DOT [Shared]
  5. Sep 20 2026 10:45PM[22] [Rotation Request Comment] 1039 GOLDEN EMPIRE TOWING 661-834-8697 [Shared]
  6. Sep 20 2026 10:45PM[28] [Appended, 22:46:13] [5] TC'D INTO C/D LANDED OFF RDWY APPROX 20-30FT
  7. Sep 20 2026 10:44PM[27] [Appended, 22:46:13] [4] UNK VEH DESCR
  8. Sep 20 2026 10:44PM[26] [Appended, 22:46:13] [3] CORR -- SOLO VEH TC
  9. Sep 20 2026 10:44PM[21] 117-506C CPZ START AN 1185 AND HAVE THEM TAKE 50FT OF CABLE [Shared]
  10. Sep 20 2026 10:42PM[18] [Notification] [CHP]-Problem changed from 1183-Trfc Collision-Unkn Inj to 1011-FCC Identifier by CHP [Shared]
  11. Sep 20 2026 10:41PM[14] [Appended, 22:42:17] [10] SUBJS STILL INSIDE VEH
  12. Sep 20 2026 10:41PM[25] [Appended, 22:46:13] [2] 2 VEH TC
  13. Sep 20 2026 10:40PM[8] [Appended, 22:42:17] [4] NEG 1125
  14. Sep 20 2026 10:40PM[3] NEG 1125 // WENT THROUGH FENCE
  15. Sep 20 2026 10:40PM[2] VEH WAS SWERVING // LOST CONTROL
  16. Sep 20 2026 10:39PM[6] [Appended, 22:42:17] [2] VEH OVERTURN INTO A DITCH
  17. Sep 20 2026 10:39PM[5] [Appended, 22:42:17] [1] VEH TC

Units

  1. Sep 20 2026 10:51PMUnit Enroute
  2. Sep 20 2026 10:51PMUnit Assigned
  3. Sep 20 2026 11:07PMUnit Cleared
  4. Sep 20 2026 10:47PMUnit Enroute
  5. Sep 20 2026 10:47PMUnit Assigned
  6. Sep 20 2026 10:47PMUnit Enroute
  7. Sep 20 2026 10:46PMUnit Assigned

CHP incident #260920BF0398 · What do these codes mean?