CHP Traffic Incidents

← Back to history
Closed

FIRE-Report of Fire

📍 San Luis Obispo · US101 / Laetitia Vineyard Dr

Sep 16, 9:43 AM · 4d ago

StatusClosed
Duration1h 9m
First seenSep 16, 9:48 AM
Last updateSep 16, 10:48 AM
Location desc.NB 101 JNO

✉ Sign up for email alerts

Open in Google Maps ↗

Dispatch log

  1. Sep 16 2026 10:29AM[42] A28-404 #2 LANE NOW OPEN [Shared]
  2. Sep 16 2026 10:27AM[41] A28-505 FIVE CITIES FIRE 97 WITH THE 1126 PARTIES [Shared]
  3. Sep 16 2026 10:14AM[38] A28-505 1126 POSS RELATED TO THE FIRE / UNINTENTIONAL / 404 WILL ATTEMPT TO CONTACT FIRE TO RELAY AND SEE IF THEY WANT TO CONTACT PARTIES [Shared]
  4. Sep 16 2026 10:00AM[32] A28-404 FIRE IS OUT / BATTALION CHIEF ADV'ING ADD'L TRUCK ENRT TO MAKE SURE ITS OUT COMPLETELY / WILL HAVE THE #2 CLOSED FOR APPROX 1 HR [Shared]
  5. Sep 16 2026 9:54AM[31] A28-404 FIRE 97 BLOCKING THE #2 / TRAFFIC FLOWING SLOWLY THRU THE #1 [Shared]
  6. Sep 16 2026 9:51AM[29] 1039 CAL FIRE [Shared]
  7. Sep 16 2026 9:50AM[28] A28-505 CAL FIRE IS GIVING 1020 BTWN TRAFFIC WAY AND GRAND [Shared]
  8. Sep 16 2026 9:49AM[25] A28-505 BREAK IN PLACE NB JNO WILLOW [Shared]
  9. Sep 16 2026 9:48AM[20] [Notification] [CHP]-RP ADVSD PASSSERBY ATTEMPTING TO PUT FIRE OUT [Shared]
  10. Sep 16 2026 9:47AM[17] A28-404 97 AT THE FIRST TURN THRU JSO EC / REQ 505 START A BREAK [Shared]
  11. Sep 16 2026 9:46AM[12] A28-404 UTL EC TO TRAFFIC WAY / SB JNO WINERY NOW [Shared]
  12. Sep 16 2026 9:46AM[13] [Appended, 09:47:02] [1] BRUSH ON FIRE // RHS
  13. Sep 16 2026 9:46AM[9] [Notification] [CHP]-ADDTL CALLER PLACING FIRE CLOSER TO THE WINERY // ADVD 3 SEPARATE SPOT FIRES [Shared]
  14. Sep 16 2026 9:44AM[1] BRUSH FIRE STARTING ON RHS
  15. Sep 16 2026 9:43AM[2] [Appended, 09:44:05] [1] FIRE STARTING ON RHS

Units

  1. Sep 16 2026 9:54AMUnit At Scene
  2. Sep 16 2026 9:46AMUnit Enroute
  3. Sep 16 2026 9:46AMUnit Assigned
  4. Sep 16 2026 10:35AMUnit Cleared
  5. Sep 16 2026 9:54AMUnit At Scene
  6. Sep 16 2026 9:54AMUnit Enroute
  7. Sep 16 2026 9:44AMUnit Assigned

CHP incident #260916SL0075 · What do these codes mean?