CrashDNA

Crash data.
Real-world context.

Explore CrashDNA
CrashDNA / California / Los Angeles
Public data. Local reporting. · California

Los Angeles Crash Guide

Where crashes are reported, when they happen, and how Los Angeles is changing.

CHP California Crash Reporting System · Observed records through Nov 7, 2026
Source years 2022–2026 · Updated Nov 8, 2026

Los Angeles, California cityscape
Los Angeles, California · Photo by Andy Feliciotti / Unsplash

Jan 1, 2026 – Nov 7, 2026
Partial year / month; records may be revised.

Reported crashes22,438Jan 1, 2026 – Nov 7, 2026
Records with map coordinates52.8%11,851 with coordinates inside the map extent
Leading known hour4 PM1,354 reported crashes
Leading day of weekThursday3,416 reported crashes
The local picture

4 PM stands out in Los Angeles’s crash records

Los Angeles recorded 22,438 crashes in the selected period. 4 PM recorded 1,354 crashes, 6.0% of the selected total. Thursday had the highest day-of-week count, with 3,416 reported crashes.

I-110 N/B (HARBOR FREEWAY) appears most often as the primary road in these Los Angeles records, with 612 crashes. This groups the reported road name across the city; it does not identify one intersection or establish a crash rate.

Counts describe reports, not individual risk. They do not adjust for traffic volume, distance travelled or time spent on the road. This guide covers records explicitly assigned to the City of Los Angeles, not Los Angeles County or the wider metropolitan area.

Where reports concentrate

Los Angeles crash map

Explore approximate concentrations of reported crashes. Markers combine records in roughly 500 m grid cells; they are not individual crash locations or intersection rankings.

Map year is selected separately from the overview.

Loading the 2026 aggregate map…

Larger markers = more reported crashes

Map coverage varies by year and place. Records with missing or unusable coordinates, or coordinates outside the displayed extent, remain in the guide totals but are not plotted. Areas without markers cannot be interpreted as having no crashes. Map controls and attribution are provided by Leaflet and OpenStreetMap.

When crashes happen · selected period

Time of day

  1. 12 AM663
  2. 1 AM621
  3. 2 AM651
  4. 3 AM427
  5. 4 AM393
  6. 5 AM546
  7. 6 AM687
  8. 7 AM1,094
  9. 8 AM1,124
  10. 9 AM968
  11. 10 AM860
  12. 11 AM974
  13. 12 PM1,051
  14. 1 PM1,038
  15. 2 PM1,219
  16. 3 PM1,335
  17. 4 PM1,354
  18. 5 PM1,279
  19. 6 PM1,175
  20. 7 PM979
  21. 8 PM1,045
  22. 9 PM985
  23. 10 PM1,013
  24. 11 PM803

Reported local clock time. Unknown and invalid times are excluded from hourly rankings; details are in methods.

Day of the week

  1. Sunday3,026
  2. Monday2,977
  3. Tuesday3,172
  4. Wednesday3,200
  5. Thursday3,416
  6. Friday3,415
  7. Saturday3,232

Recorded collision types

  1. rear end7,679
  2. side swipe7,098
  3. hit object2,653
  4. broadside2,165
  5. vehicle/pedestrain1,135
  6. head-on1,100
  7. other405
  8. overturned189

Source descriptions, not party or person classifications. Up to 12 known categories; unknown descriptions remain in the total.

Reported primary roads · selected period

Road names appearing most often

Counts group the exact primary-road description supplied in the crash report. Different spellings may describe the same road. A road name can span many locations.

  1. I-110 N/B (HARBOR FREEWAY)612
  2. I-5 S/B (GOLDEN STATE FREEWAY)537
  3. I-110 S/B (HARBOR FREEWAY)529
  4. I-5 N/B (GOLDEN STATE FREEWAY)511
  5. US-101 S/B (VENTURA FREEWAY)511
  6. US-101 N/B (VENTURA FREEWAY)500
  7. I-405 S/B (SAN DIEGO FWY)385
  8. I-10 E/B (SANTA MONICA FREEWAY)343
  9. I-405 N/B (SAN DIEGO FWY)333
  10. I-405 S/B329
  11. I-10 W/B (SANTA MONICA FREEWAY)322
  12. US-101 S/B (HOLLYWOOD FREEWAY)320

A high count is not a measure of danger, exposure or the likelihood of a crash.

What this first California release supports: crash counts, dates, known hours, collision descriptions and aggregate maps. Party/person breakdowns and serious-injury measures are not included. Their absence is not a zero value.

Download aggregate data (CSV) ↓
Methods, definitions and limitations

Source: California Highway Patrol — California Crash Reporting System (CCRS), annual Crashes files for 2022–2026. Each source is downloaded, archived with a SHA-256 checksum, normalized, independently audited and copied privately before aggregate publication. Crash counts represent eligible crash reports, not people.

Geography: source CityId 535, CityCode 1942, CountyCode 19 and City Name “Los Angeles”, checked together. This is the source’s reported-city assignment, not a geospatial reclassification into county or metro boundaries. Census place GEOID 0644000 is an identity reference only. Official geographic reference: U.S. Census TIGERweb.

Explicitly deleted records are excluded. Identical duplicate identifiers count once; conflicting identifiers are held for review. A source with unknown deletion status or cross-year identifier conflicts cannot be published by this workflow. Invalid or missing casualty fields do not erase an otherwise usable crash event; those fields remain unavailable. No party or person file is required for this crash-only view, and their measures are not inferred.

Dates use the reported local calendar date. Hours require a valid 0000–2359 source time matching the reported timestamp. Codes such as 2500 and inconsistent times are treated as unknown. See the CHP reporting manual, date and time conventions. “Last 12 calendar months” ends at the last calendar-month end represented in the source; this does not certify that reporting is complete.

For the selected period, 154 records have unknown/unusable hour, 0 lack a known primary road and 14 lack a known collision description. Casualty counts are missing in 4,829 records for deaths and 4,829 for injuries; 0 records have invalid casualty values retained as unavailable. These are quality notes, not story findings.

Map cells are coarse approximations, 0.005 degrees on each axis. Coordinate checks use a fixed California/Los Angeles map extent, not a historical municipal boundary. 10,587 records in the selected overview period are not plotted. Count rankings do not account for traffic or pedestrian exposure and do not establish risk or causation. California and Texas use different reporting systems; these counts should not be used for direct state risk comparisons.

Source generation used by this guide
YearSource rowsEligible crashesObserved throughSource revision / checksum
2022405,239405,2392022-12-31ccrs-core-2022-e27b7549d658d172fa70b59b
SHA-256: 0b83a520f42aadac8c12462428633012a813a9734ea8e1cd5ba1e2a73807e15e
Source modified: 2026-11-07T03:18:29.696852
2023409,836409,8362023-12-31ccrs-core-2023-cc7a113533eb21cc97a23cc5
SHA-256: 0e67a9fc04d29d9a87f57fb82824818a1223947f02dad086b22ec8166ef4712c
Source modified: 2026-11-07T03:14:20.974293
2024417,173417,1732024-12-31ccrs-core-2024-37e10137e262fd26dd77dffa
SHA-256: 16a8bf5a533cd129feb36d0356722799f36658d28a7333a90b2e6fa05de9802a
Source modified: 2026-11-07T03:10:08.194695
2025402,447402,4472025-12-31ccrs-core-2025-09dc8344ac724110a36c1b76
SHA-256: 11e1b395905750168b3c51e362f9938cf2752515bb47aa1723111c5146c488fe
Source modified: 2026-11-07T03:06:01.978409
2026312,851312,8512026-11-07ccrs-core-2026-29d9f5fc8fd9d8a4b357a006
SHA-256: 0ff12232181b104ec569f2905bf1f137675bd618f032daad64103a4f946cf875
Source modified: 2026-11-08T03:02:22.270495

Guide revision: 1ffe1c08-5d70-434b-ab0f-38b6c093f773
Source binding: 5628129b2946d2f45539ab983a1259f943e377272a8d513e096bcf520ef3ed1a
Prepared: 2026-11-08T03:13:17.290Z

CrashDNA is not affiliated with CHP or any government agency. Questions and corrections: alerts@crashdna.com.