Crash on CA 139 near Tulelake

CHP reported a crash with injuries on CA 139 in Modoc County at 5:05 PM on Tue, Nov 17, 2026.

Road
CA 139
Location
at Cr111 N, 4 miles from Tulelake, Modoc County
State
California
First reported
Nov 17, 2026, 5:05 PM PST
Weather nearby
Mostly clear, 37°F at 4:10 PM, Klamath Falls International Airport (National Weather Service)
Source
California Highway Patrol live incident feed

Get an email for the next crash on CA 139

What happened, in order

  1. CHP listed it: Crash, ambulance on the way.
  2. CHP update: Crash, no injuries.
  3. CHP update: Crash, ambulance on the way.
  4. CHP update: Crash, no injuries.
  5. CHP update: Crash, ambulance on the way.
  6. CHP update: Crash, no injuries.
  7. CHP update: Crash, ambulance on the way.
  8. CHP update: Crash, no injuries.
  9. CHP update: Crash, ambulance on the way.
  10. CHP update: Crash, no injuries.
  11. CHP update: Crash, ambulance on the way.
  12. CHP update: Crash, no injuries.
  13. CHP update: Crash, ambulance on the way.
  14. CHP update: Crash, no injuries.
  15. CHP update: Crash, ambulance on the way.
  16. 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 559 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 3:02 AM, so it most likely cleared around then (about 597 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 3:36 AM, so it most likely cleared around then (about 631 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 4:08 AM, so it most likely cleared around then (about 663 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 5:50 AM, so it most likely cleared around then (about 765 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 6:48 AM, so it most likely cleared around then (about 823 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 7:20 AM, so it most likely cleared around then (about 855 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 7:40 AM, so it most likely cleared around then (about 875 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 8:50 AM, so it most likely cleared around then (about 945 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 9:18 AM, so it most likely cleared around then (about 973 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 9:32 AM, so it most likely cleared around then (about 987 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 9:58 AM, so it most likely cleared around then (about 1013 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 10:24 AM, so it most likely cleared around then (about 1039 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 10:34 AM, so it most likely cleared around then (about 1049 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 11:04 AM, so it most likely cleared around then (about 1079 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 11:38 AM, so it most likely cleared around then (about 1113 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 12:06 PM, so it most likely cleared around then (about 1141 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 1:06 PM, so it most likely cleared around then (about 1201 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 2:18 PM, so it most likely cleared around then (about 1273 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 3:08 PM, so it most likely cleared around then (about 1323 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 3:18 PM, so it most likely cleared around then (about 1333 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 3:32 PM, so it most likely cleared around then (about 1347 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 4:10 PM, so it most likely cleared around then (about 1385 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 4:38 PM, so it most likely cleared around then (about 1413 min after it was first reported).
  63. CHP listed it again.
  64. 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 1471 min after it was first reported).
  65. CHP listed it again.
  66. 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 1509 min after it was first reported).
  67. 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. For current conditions, check Caltrans QuickMap.

More on CA 139   More in Modoc County