SigAlert on I-105 westbound in Los Angeles

CHP reported a road closure on I-105 westbound in Los Angeles at 5:29 PM on Tue, Nov 17, 2026.

Road
I-105
Direction
westbound
Location
at Sepulveda Blvd, in Los Angeles, Los Angeles County
State
California
Traffic impact
Lanes blocked 30+ min
First reported
Nov 17, 2026, 5:29 PM PST
Source
California Highway Patrol live incident feed
How long crashes on I-105 usually last. Half of the last 15 crashes CHP listed on this road in California cleared within 38 min, and three in four within 1 hr 6 min. This one has been listed for 26 hr 46 min.

Get an email for the next crash on I-105

What happened, in order

  1. CHP listed it (lanes blocked 30+ min): SigAlert: lanes blocked for 30 minutes or more.
  2. No longer listed by CHP after 3 checks in a row. Last seen at 12:48 AM, so it most likely cleared around then (about 439 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 1:14 AM, so it most likely cleared around then (about 465 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 1:24 AM, so it most likely cleared around then (about 475 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 2:24 AM, so it most likely cleared around then (about 535 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 3:02 AM, so it most likely cleared around then (about 573 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 3:36 AM, so it most likely cleared around then (about 607 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 4:08 AM, so it most likely cleared around then (about 639 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 5:50 AM, so it most likely cleared around then (about 741 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 6:48 AM, so it most likely cleared around then (about 799 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 7:20 AM, so it most likely cleared around then (about 831 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 7:40 AM, so it most likely cleared around then (about 851 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 8:50 AM, so it most likely cleared around then (about 921 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 9:18 AM, so it most likely cleared around then (about 949 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 9:32 AM, so it most likely cleared around then (about 963 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 9:58 AM, so it most likely cleared around then (about 989 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 10:24 AM, so it most likely cleared around then (about 1015 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 10:34 AM, so it most likely cleared around then (about 1025 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 11:04 AM, so it most likely cleared around then (about 1055 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 11:38 AM, so it most likely cleared around then (about 1089 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 12:06 PM, so it most likely cleared around then (about 1117 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 1:06 PM, so it most likely cleared around then (about 1177 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 2:18 PM, so it most likely cleared around then (about 1249 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 3:08 PM, so it most likely cleared around then (about 1299 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 3:18 PM, so it most likely cleared around then (about 1309 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 3:32 PM, so it most likely cleared around then (about 1323 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 4:10 PM, so it most likely cleared around then (about 1361 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 4:38 PM, so it most likely cleared around then (about 1389 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 5:36 PM, so it most likely cleared around then (about 1447 min after it was first reported).
  57. CHP listed it again.
  58. 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 1485 min after it was first reported).
  59. CHP listed it again.
  60. 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 1539 min after it was first reported).
  61. CHP listed it again.
  62. 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 1547 min after it was first reported).
  63. CHP listed it again.

Nearest traffic camera

Current view from the Caltrans camera at I-105 : (301) Sepulveda
Caltrans camera at I-105 : (301) Sepulveda, a few hundred feet away. Image courtesy of Caltrans. It's the current view, refreshed every few minutes, and it may not show the crash itself.

Where

Open a larger map

Other crashes within about 2 miles

  1. Local
    Cleared

    listed 3 hr 37 min
    5000 block of W 140th St, Los Angeles, Los Angeles County
  2. Local
    Cleared

    listed 12 min
    S La Cienega Blvd & W 120th St, Los Angeles, Los Angeles County
  3. I-405
    Cleared

    listed 32 min
    I-405 southbound, at Rosecrans Ave W off-ramp, in Los Angeles, Los Angeles County
  4. I-405
    Cleared

    listed 42 min
    I-405 southbound, at El Segundo Blvd off-ramp, 1 mile from Lennox, Los Angeles County
  5. I-405
    Cleared

    listed 44 min
    I-405 northbound, at La Cienega Blvd off-ramp, in Los Angeles, Los Angeles County
  6. I-405
    Cleared

    listed 40 min
    I-405 northbound, at Manchester Blvd off-ramp, in Los Angeles, Los Angeles County
  7. 1
    Cleared

    listed 2 hr 5 min
    CA 1, at off-ramp / Sepulveda Blvd, in Los Angeles, Los Angeles County
  8. I-405
    Cleared

    listed 56 min
    I-405 southbound, at W Century Blvd, in Los Angeles, Los Angeles County

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. For current conditions, check Caltrans QuickMap.

More on I-105   More in Los Angeles County