Where do crashes happen most often on I-110?
For reporters and researchers
Need a publication-ready corridor map, reproducible local table, or data-quality review? Contact Meru AI about research and analysis.
I-110 crash-record density
Adjust the window from the profile start date. The map redraws to show only loaded mappable records inside that date range.
Top Incident Locations along I-110
Direction of Travel Split
Severity & Casualties Summary
Locations with the most matching I-110 records
Counts reflect the road labels and city fields recorded in the source data for this reporting window. They do not account for traffic volume, road miles, or time spent traveling.
| Rank | Recorded city | Crashes | Serious or fatal | People killed |
|---|---|---|---|---|
| 1 | Los Angeles | 2,388 | 46 | 8 |
| 2 | Unincorporated | 338 | 8 | 0 |
| 3 | Carson | 14 | 0 | 0 |
| 4 | Lomita | 4 | 0 | 0 |
| 5 | Compton | 3 | 0 | 0 |
| 6 | Long Beach | 3 | 0 | 0 |
| 7 | Torrance | 3 | 1 | 0 |
| 8 | South El Monte | 1 | 0 | 0 |
How this corridor profile is produced
No applied canonical mapping exists for I-110 yet, so this profile temporarily uses the legacy curated alias matcher against the officer-recorded primary-road label. The reporting window is 2025-07-02 through 2026-07-01. Source records come from the California Highway Patrol California Crash Reporting System.
Read the full methodology and privacy notesWhat the numbers cannot establish
- Raw crash counts do not measure individual risk or identify the “most dangerous” segment.
- Traffic volume, vehicle miles traveled, road length, construction, and enforcement exposure are not controlled here.
- Road and city labels can be incomplete, inconsistent, or revised after publication.
Cite or reuse this profile
This is independent analysis of public records. Keep the reporting window, source, and methodology attached when reusing a figure.