Crash on US 101 northbound in Los Angeles
Still listed
First reported at 11:35 PM, 19 hr 47 min ago. Still on the official list at our last check, 6 min ago.
CHP reported a crash with injuries on US 101 northbound in Los Angeles at 11:35 PM on Tue, Nov 17, 2026.
- Road
- US 101
- Direction
- northbound
- Location
- in Los Angeles, Los Angeles County
- State
- California
- First reported
- Nov 17, 2026, 11:35 PM PST
- Weather nearby
- Clear, 52°F at 11:05 PM, Burbank - Bob Hope Airport (National Weather Service)
- Source
- California Highway Patrol live incident feed
How long crashes on US 101 usually last. Half of the last 167 crashes CHP listed on this road in California cleared within 44 min, and three in four within 1 hr 21 min. This one has been listed for 19 hr 47 min.
Get an email for the next crash on US 101
What happened, in order
- CHP listed it: Crash, ambulance on the way.
- 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 375 min after it was first reported).
- CHP listed it again.
- 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 433 min after it was first reported).
- CHP listed it again.
- 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 465 min after it was first reported).
- CHP listed it again.
- 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 485 min after it was first reported).
- CHP listed it again.
- 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 555 min after it was first reported).
- CHP listed it again.
- 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 583 min after it was first reported).
- CHP listed it again.
- 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 597 min after it was first reported).
- CHP listed it again.
- 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 623 min after it was first reported).
- CHP listed it again.
- 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 649 min after it was first reported).
- CHP listed it again.
- 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 659 min after it was first reported).
- CHP listed it again.
- 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 689 min after it was first reported).
- CHP listed it again.
- 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 723 min after it was first reported).
- CHP listed it again.
- 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 751 min after it was first reported).
- CHP listed it again.
- 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 811 min after it was first reported).
- CHP listed it again.
- 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 883 min after it was first reported).
- CHP listed it again.
- 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 933 min after it was first reported).
- CHP listed it again.
- 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 943 min after it was first reported).
- CHP listed it again.
- 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 957 min after it was first reported).
- CHP listed it again.
- 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 995 min after it was first reported).
- CHP listed it again.
- 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 1023 min after it was first reported).
- CHP listed it again.
- 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 1081 min after it was first reported).
- CHP listed it again.
- 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 1119 min after it was first reported).
- CHP listed it again.
- 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 1173 min after it was first reported).
- CHP listed it again.
Nearest traffic camera
Where
Other crashes within about 2 miles
-
101
45 min agoUS 101 westbound, at Laurel Canyon Blvd, in Los Angeles, Los Angeles County -
101
1 hr agoUS 101 eastbound, at Laurel Canyon Blvd, in Los Angeles, Los Angeles County -
134
listed 50 minCA 134 eastbound, at Cahuenga Blvd, in Los Angeles, Los Angeles County -
134
listed 48 minCA 134 westbound, at CA 170 northbound connector / Vineland Ave, in Los Angeles, Los Angeles County -
101
listed 5 minUS 101 northbound, at Lankershim Blvd, in Los Angeles, Los Angeles County -
101
listed 58 minUS 101 southbound, at N Cahuenga Blvd, in Los Angeles, Los Angeles County -
170
listed 54 minCA 170 northbound, at CA 134 westbound CA 170 northbound connector, 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.