Injury crash at Road 224 & Avenue 128 near Porterville

CHP reported a crash with injuries in Tulare County at 7:51 PM on Tue, Nov 17, 2026.

Location
Road 224 & Avenue 128, 4 miles from Porterville, Tulare County
State
California
First reported
Nov 17, 2026, 7:51 PM PST
Source
California Highway Patrol live incident feed

Get an email for the next crash in Tulare County

What happened, in order

  1. CHP listed it: Crash, ambulance on the way.
  2. CHP update: Crash with minor injuries.
  3. CHP update: Hit-and-run crash with injuries.
  4. 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 297 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:14 AM, so it most likely cleared around then (about 323 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 1:24 AM, so it most likely cleared around then (about 333 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 2:24 AM, so it most likely cleared around then (about 393 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:02 AM, so it most likely cleared around then (about 431 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 3:36 AM, so it most likely cleared around then (about 465 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 4:08 AM, so it most likely cleared around then (about 497 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 5:50 AM, so it most likely cleared around then (about 599 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 6:48 AM, so it most likely cleared around then (about 657 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:20 AM, so it most likely cleared around then (about 689 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 7:40 AM, so it most likely cleared around then (about 709 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 8:50 AM, so it most likely cleared around then (about 779 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:18 AM, so it most likely cleared around then (about 807 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:32 AM, so it most likely cleared around then (about 821 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 9:58 AM, so it most likely cleared around then (about 847 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:24 AM, so it most likely cleared around then (about 873 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 10:34 AM, so it most likely cleared around then (about 883 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:04 AM, so it most likely cleared around then (about 913 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 11:38 AM, so it most likely cleared around then (about 947 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 12:06 PM, so it most likely cleared around then (about 975 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 1:06 PM, so it most likely cleared around then (about 1035 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 2:18 PM, so it most likely cleared around then (about 1107 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:08 PM, so it most likely cleared around then (about 1157 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:18 PM, so it most likely cleared around then (about 1167 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 3:32 PM, so it most likely cleared around then (about 1181 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:10 PM, so it most likely cleared around then (about 1219 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 4:38 PM, so it most likely cleared around then (about 1247 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 5:36 PM, so it most likely cleared around then (about 1305 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 6:14 PM, so it most likely cleared around then (about 1343 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:08 PM, so it most likely cleared around then (about 1397 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 7:16 PM, so it most likely cleared around then (about 1405 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 8:46 PM, so it most likely cleared around then (about 1495 min after it was first reported).
  67. CHP listed it again.

Where

Open a larger map

Other crashes within about 2 miles

  1. Local
    Cleared

    listed 18 min
    Halsey St & Poplar Ave, Porterville, Tulare 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.