Injury crash at 3700 block of - 4367 Prefumo Canyon Rd near Los Osos

CHP reported a crash with injuries in San Luis Obispo County at 9:47 PM on Tue, Nov 17, 2026.

Road
- 4367 Prefumo Canyon Road
Location
3700 block of - 4367 Prefumo Canyon Rd, 5 miles from Los Osos, San Luis Obispo County
State
California
First reported
Nov 17, 2026, 9:47 PM PST
Weather nearby
Clear, 46°F at 9:20 PM, San Luis Obispo, San Luis Obispo County-Mc Chesney Field (National Weather Service)
Source
California Highway Patrol live incident feed

Get an email for the next crash in San Luis Obispo County

What happened, in order

  1. CHP listed it: Crash, ambulance on the way.
  2. No longer listed by CHP after 3 checks in a row. Last seen at 2:24 AM, so it most likely cleared around then (about 277 min after it was first reported).
  3. CHP listed it again.
  4. No longer listed by CHP after 3 checks in a row. Last seen at 3:02 AM, so it most likely cleared around then (about 315 min after it was first reported).
  5. CHP listed it again.
  6. No longer listed by CHP after 3 checks in a row. Last seen at 3:36 AM, so it most likely cleared around then (about 349 min after it was first reported).
  7. CHP listed it again.
  8. No longer listed by CHP after 3 checks in a row. Last seen at 4:08 AM, so it most likely cleared around then (about 381 min after it was first reported).
  9. CHP listed it again.
  10. No longer listed by CHP after 3 checks in a row. Last seen at 5:50 AM, so it most likely cleared around then (about 483 min after it was first reported).
  11. CHP listed it again.
  12. No longer listed by CHP after 3 checks in a row. Last seen at 6:48 AM, so it most likely cleared around then (about 541 min after it was first reported).
  13. CHP listed it again.
  14. No longer listed by CHP after 3 checks in a row. Last seen at 7:20 AM, so it most likely cleared around then (about 573 min after it was first reported).
  15. CHP listed it again.
  16. No longer listed by CHP after 3 checks in a row. Last seen at 7:40 AM, so it most likely cleared around then (about 593 min after it was first reported).
  17. CHP listed it again.
  18. No longer listed by CHP after 3 checks in a row. Last seen at 8:50 AM, so it most likely cleared around then (about 663 min after it was first reported).
  19. CHP listed it again.
  20. No longer listed by CHP after 3 checks in a row. Last seen at 9:18 AM, so it most likely cleared around then (about 691 min after it was first reported).
  21. CHP listed it again.
  22. No longer listed by CHP after 3 checks in a row. Last seen at 9:32 AM, so it most likely cleared around then (about 705 min after it was first reported).
  23. CHP listed it again.
  24. No longer listed by CHP after 3 checks in a row. Last seen at 9:58 AM, so it most likely cleared around then (about 731 min after it was first reported).
  25. CHP listed it again.
  26. No longer listed by CHP after 3 checks in a row. Last seen at 10:24 AM, so it most likely cleared around then (about 757 min after it was first reported).
  27. CHP listed it again.
  28. No longer listed by CHP after 3 checks in a row. Last seen at 10:34 AM, so it most likely cleared around then (about 767 min after it was first reported).
  29. CHP listed it again.
  30. No longer listed by CHP after 3 checks in a row. Last seen at 11:04 AM, so it most likely cleared around then (about 797 min after it was first reported).
  31. CHP listed it again.
  32. No longer listed by CHP after 3 checks in a row. Last seen at 11:38 AM, so it most likely cleared around then (about 831 min after it was first reported).
  33. CHP listed it again.
  34. No longer listed by CHP after 3 checks in a row. Last seen at 12:06 PM, so it most likely cleared around then (about 859 min after it was first reported).
  35. CHP listed it again.
  36. No longer listed by CHP after 3 checks in a row. Last seen at 1:06 PM, so it most likely cleared around then (about 919 min after it was first reported).
  37. CHP listed it again.
  38. No longer listed by CHP after 3 checks in a row. Last seen at 2:18 PM, so it most likely cleared around then (about 991 min after it was first reported).
  39. CHP listed it again.
  40. No longer listed by CHP after 3 checks in a row. Last seen at 3:08 PM, so it most likely cleared around then (about 1041 min after it was first reported).
  41. CHP listed it again.
  42. No longer listed by CHP after 3 checks in a row. Last seen at 3:18 PM, so it most likely cleared around then (about 1051 min after it was first reported).
  43. CHP listed it again.
  44. No longer listed by CHP after 3 checks in a row. Last seen at 3:32 PM, so it most likely cleared around then (about 1065 min after it was first reported).
  45. CHP listed it again.
  46. No longer listed by CHP after 3 checks in a row. Last seen at 4:10 PM, so it most likely cleared around then (about 1103 min after it was first reported).
  47. CHP listed it again.
  48. No longer listed by CHP after 3 checks in a row. Last seen at 4:38 PM, so it most likely cleared around then (about 1131 min after it was first reported).
  49. CHP listed it again.
  50. No longer listed by CHP after 3 checks in a row. Last seen at 5:36 PM, so it most likely cleared around then (about 1189 min after it was first reported).
  51. CHP listed it again.
  52. No longer listed by CHP after 3 checks in a row. Last seen at 6:14 PM, so it most likely cleared around then (about 1227 min after it was first reported).
  53. CHP listed it again.
  54. No longer listed by CHP after 3 checks in a row. Last seen at 7:08 PM, so it most likely cleared around then (about 1281 min after it was first reported).
  55. CHP listed it again.
  56. No longer listed by CHP after 3 checks in a row. Last seen at 7:16 PM, so it most likely cleared around then (about 1289 min after it was first reported).
  57. CHP listed it again.

Where

Open a larger map

We publish what official sources list and when they stop listing it. We don't publish names, license plates or photos of people involved. Details can change as agencies update their reports. Data sources and terms.