San Francisco rideshare accident statistics reveal patterns in when, where, and how Uber and Lyft crashes happen across the city, but finding reliable local data requires piecing together state-level reports, citywide collision records, and transportation studies that don't always separate rideshare vehicles from the broader traffic picture.
The Zinn Law Firm represents individuals injured in serious rideshare crashes throughout San Francisco and Mill Valley. We utilize crash data, traffic patterns, and local collision trends to build stronger claims against rideshare drivers and insurance companies.
Call for a free consultation with a San Francisco rideshare accident attorney. We work on contingency, so there are no attorneys' fees unless you win.
Where to Find Reliable San Francisco Rideshare Crash Data
San Francisco rideshare accident statistics come from multiple sources, and none of them provide a perfect, real-time count of every Uber and Lyft crash in the city. Here's what each source can and cannot tell you.
California Public Utilities Commission (CPUC) TNC Annual Reports
The CPUC regulates Transportation Network Companies (TNCs) like Uber and Lyft in California and publishes annual reports on rideshare collisions statewide. These reports include total crashes, injury collisions, and fatal collisions reported by Uber and Lyft, but the data is aggregated at the state level. The CPUC does not break down crashes by city or county, so you cannot extract San Francisco-specific numbers directly from these reports.
The CPUC reports show collision trends over time and provide context for how rideshare crash rates compare to vehicle miles traveled, but they rely on self-reporting by the companies and don't capture crashes where rideshare involvement wasn't documented or where the driver's app status was unclear.
SFMTA Traffic Collision Data and DataSF
The San Francisco Municipal Transportation Agency (SFMTA) tracks traffic collisions on city streets through its Vision Zero program and publishes crash data through DataSF, the city's open data portal. This data includes collision locations, injury severity, vehicle types, and contributing factors like speeding, failure to yield, or distracted driving.
The challenge with SFMTA data is that collision reports don't always identify whether a vehicle was operating as a rideshare at the time of the crash. A Lyft driver with the app off looks like any other private vehicle in the data, and even on-duty rideshare crashes may not be flagged as such unless the driver or passengers disclosed it at the scene.
SWITRS and UC Berkeley TIMS
The Statewide Integrated Traffic Records System (SWITRS), maintained by the California Highway Patrol, collects data on all traffic collisions reported to law enforcement in California. UC Berkeley's Transportation Injury Mapping System (TIMS) provides a searchable interface for SWITRS data, including maps and filters for location, collision type, and severity.
SWITRS data covers San Francisco crashes but, like SFMTA records, doesn't reliably identify rideshare involvement unless officers noted it in the collision report. You can map collision hotspots and analyze trends by time of day, day of week, and road type, but isolating rideshare-specific crashes requires additional context or cross-referencing with trip volume data.
San Francisco Rideshare Crash Trends: What the Data Shows
San Francisco has 500 times more TNC trips per square mile than the rest of California, concentrating rideshare collision risk in a geographically small area with dense traffic, high pedestrian volume, and complex street networks.
Statewide Context: CPUC TNC Reports
CPUC annual reports show thousands of self-reported TNC collisions statewide yearly, though isolating injuries/fatalities requires deeper analysis. These numbers reflect crashes during all app phases (drivers waiting for requests, en route to pickups, and carrying passengers).
The collision rate per million vehicle miles traveled has fluctuated over time, with increases during periods of high trip volume and decreases during the COVID-19 pandemic when rideshare use dropped sharply.
San Francisco accounts for a significant portion of California rideshare trips, but without city-specific breakdowns in CPUC reports, local crash totals remain estimates based on trip volume and traffic patterns.
San Francisco Trip Volume and Collision Risk
SFCTA studies show that rideshare services generate millions of trips in San Francisco each year, with the highest concentrations in downtown, SoMa, the Mission, the Financial District, North Beach, and the Castro. High trip volume correlates with collision risk because more rideshare vehicles on the road means more opportunities for distracted driving, unsafe pickups and drop-offs, and interactions with cyclists, pedestrians, and other drivers.
Rideshare trips peak during evening and nighttime hours, particularly on weekends when bar and restaurant activity increases. Crashes involving rideshare vehicles are more common during these high-volume periods, and nighttime collisions carry higher injury severity because of reduced visibility and higher speeds.
High-Collision Corridors and Neighborhoods
San Francisco collision data from SFMTA and SWITRS consistently identifies high-crash corridors where rideshare activity overlaps with congestion, pedestrian traffic, and cycling volume. Market Street, Geary Boulevard, Van Ness Avenue, and 19th Avenue see frequent collisions involving all vehicle types, including rideshare vehicles. Downtown intersections near Powell Street, Union Square, the Transbay Terminal, and the Civic Center experience high activity from rideshare pickups and drop-offs, contributing to increased crash risk.
Neighborhoods with dense rideshare trip volumes, like the Mission, SoMa, Hayes Valley, the Castro, North Beach, and Pacific Heights, see more rideshare-related collisions than lower-traffic residential areas. Crashes in these neighborhoods involve pedestrians struck in crosswalks, cyclists hit by drivers opening doors or merging into bike lanes, and rear-end collisions caused by sudden stops to pick up passengers.
Time-of-Day and Day-of-Week Patterns
Rideshare collisions follow predictable time-of-day patterns tied to when people use rideshare services most. Evening rush hour (5 PM to 8 PM) and late-night hours (10 PM to 2 AM) see higher crash rates because trip volume increases, drivers work longer shifts and experience fatigue, and traffic mixes with pedestrians and cyclists in entertainment districts.
Weekend crashes, particularly Friday and Saturday nights, involve higher injury severity because of increased nightlife activity, alcohol-related crashes, and aggressive driving as drivers compete for high-demand rides.
Rideshare vs. Personal Vehicle Crash Rates
Comparing rideshare crash rates to personal vehicle crash rates is difficult because the datasets don't align perfectly. CPUC reports show rideshare collision rates per million vehicle miles traveled, while broader traffic safety data includes all vehicles without distinguishing rideshare use.
Studies suggest rideshare vehicles may have higher per-mile crash rates than personal vehicles because drivers spend more time on the road, operate in congested urban areas, and experience distraction from app notifications and GPS navigation.
Uber vs. Lyft Safety Statistics
CPUC reports show significant differences in reported incident rates between Uber and Lyft, though these differences may reflect inconsistent reporting practices rather than actual safety performance.
According to SFCTA's analysis of 2020 CPUC Annual Reports, Lyft reported total public safety incident rates more than 3 times higher than Uber per 100,000 trips. Lyft's collision rates were twice Uber's per 100,000 trips. In total numbers, Uber reported approximately 14,800 collisions, and Lyft reported 11,200 collisions statewide, but Lyft completed fewer total trips, resulting in a higher collision rate per trip.
However, these figures come with major caveats. Lyft's 2020 public reports were incomplete, with only 36% of required data was reported as measured by required public fields and records, while Uber reported 99.99% of required data.
The companies also report incidents differently, making direct comparisons unreliable. For example, Lyft reported assault and harassment rates more than 30 times higher than Uber, which likely reflects different internal classification and reporting standards rather than actual safety differences.
Both companies' data contains internal inconsistencies that undermine reliability. Lyft's reports showed two different trip totals that differed by 49.7 million trips (81%), while Uber's totals differed by 9.3 million trips (6%). These data quality issues suggest the need for stronger regulatory oversight and standardized reporting requirements before meaningful safety comparisons between the companies can be made.
Why San Francisco Rideshare Crash Data Is Incomplete
No single data source provides a complete, real-time picture of how many rideshare crashes happen in San Francisco each year. The gaps result from reporting inconsistencies, ambiguous vehicle classifications, delayed data publication, and structural limitations in the collection and disclosure of collision information.
App Status Ambiguity
Rideshare crashes only get classified as such if someone, the police, the driver, a passenger, or another party discloses that the vehicle was operating as a rideshare at the time of the crash. Drivers sometimes claim they were offline to avoid insurance complications, and crashes involving Period 1 drivers (app on, waiting for a request) may not be reported to Uber or Lyft if the driver doesn't file a claim.
Lack of Real-Time Reporting
Collision data from SFMTA, SWITRS, and CPUC reports arrives months or years after crashes occur. CPUC annual reports typically cover data from one to two years prior, and local crash records take time to compile, verify, and publish. Real-time rideshare crash statistics don't exist in a publicly accessible form.
Self-Reporting by Rideshare Companies
CPUC TNC reports rely on data provided by Uber and Lyft, and critics argue that self-reported crash numbers may undercount incidents or exclude crashes where rideshare involvement is unclear. Independent verification of these numbers is difficult without access to internal company records.
Pedestrian and Cyclist Crashes Underreported
Not all pedestrian and cyclist crashes involving rideshare vehicles result in police reports, particularly if injuries seem minor at the scene. Delayed-symptom injuries, like concussions and soft tissue damage, may not appear in official statistics if the injured person didn't report the crash immediately.
What Rideshare Crash Statistics Mean for Your Claim
At Zinn Law Firm, our car accident lawyers use San Francisco rideshare crash data to build stronger liability arguments, identify patterns of negligent driving, and counter insurance company narratives that treat your crash as an isolated incident. Local collision statistics, trip volume data, and high-crash corridor analysis provide context that transforms a single accident into evidence of systemic risk that rideshare drivers and companies should have anticipated.
Patterns Support Liability Arguments
When your Uber or Lyft crash fits a documented pattern, crash statistics support the argument that the driver's behavior created foreseeable risk. Our Uber accident attorneys use local collision data to show that the crash wasn't a freak accident but a predictable result of negligent driving in a high-risk environment.
High-Volume Areas Increase Exposure
If your crash happened in a neighborhood or corridor with high rideshare trip volume, the data might support the claim that rideshare activity contributed to congestion, distraction, and collision risk. This context strengthens claims against rideshare drivers and, in some cases, against Uber or Lyft if inadequate safety policies contributed to the crash.
Time-of-Day Factors Affect Fault Analysis
Crashes during peak rideshare hours, particularly late-night and weekend collisions, may involve driver fatigue, distraction from competing for high-demand rides, or impaired judgment. Your Lyft accident lawyer can use these factors to support claims that the driver failed to exercise reasonable care under the circumstances.
FAQ for San Francisco Rideshare Accident Statistics
Are San Francisco Rideshare Crashes Increasing or Decreasing?
Statewide CPUC data shows fluctuations in rideshare crash totals and rates over time, with increases during high trip volume periods and decreases during the pandemic. San Francisco-specific trends are harder to isolate, but local collision data suggests rideshare-related crashes remain common in high-traffic neighborhoods and corridors.
How Many Uber and Lyft Crashes Happen in San Francisco Each Year?
There is no publicly available count of Uber and Lyft crashes specific to San Francisco. Statewide CPUC reports show thousands of rideshare injury collisions annually in California, and San Francisco's share depends on its proportion of statewide rideshare trips. However, inconsistent reporting makes it difficult to pinpoint an exact number.
Why Don't Collision Reports Always Identify Rideshare Vehicles?
Police reports don't always capture whether a vehicle was operating as a rideshare at the time of the crash, particularly if the driver was offline or waiting for a request. Crash data relies on voluntary disclosure and accurate documentation at the scene.
Can I Use Rideshare Crash Statistics in My Injury Claim?
Crash statistics provide context for liability arguments but don't replace evidence specific to your crash, such as photos, witness statements, police reports, medical records, and app data. An attorney uses local crash trends to support claims that the driver's behavior created foreseeable risk.
Do I Need a Lawyer for a San Francisco Rideshare Accident?
You're not legally required to hire an attorney, but rideshare crashes involve layered insurance coverage, app status disputes, and competing liability claims that insurance companies use to minimize payouts. Our attorneys handle evidence gathering, app status verification, and negotiation with multiple insurers while you focus on recovery, and cases involving serious injuries or disputed coverage particularly benefit from representation.
Using Crash Data to Strengthen Your Claim
San Francisco rideshare accident statistics show that Uber and Lyft crashes concentrate in predictable locations, during high-volume hours, and involve patterns of negligent driving that affect thousands of people each year. If you were injured in a rideshare crash, local collision data could support the argument that your experience fits a broader pattern of risk that rideshare drivers and companies should have anticipated and prevented.
To discuss a potential rideshare accident case in San Francisco or Mill Valley, call The Zinn Law Firm at (415) 292-4100. Our San Francisco personal injury attorney is here to answer your questions and is ready to fight for fair compensation.