Rideshare Accident Lawyer in Washington

Washington's statute of limitations for personal injury claims arising from rideshare accidents is three years from the date of the crash under RCW 4.16.080(2). There is no rideshare-specific limitations period in RCW chapter 46.72B or RCW 49.46.300 — the general personal injury SOL controls. But the practical deadline for building a strong rideshare case is measured in weeks, not years. The TNC's app data — driver status at the moment of impact, ride acceptance time, route taken, speed data, driver rating history — is controlled by the TNC and will be produced only in response to a formal preservation demand or litigation subpoena. The driver's personal dashcam footage, if any, overwrites on a rolling basis. The TNC's insurer assigns a claims adjuster within days and begins building their own version of events before the injured party has even left the hospital. Washington's rideshare insurance framework creates a three-period coverage structure under RCW 46.72B.180, and the TNC will immediately begin arguing over which period applies because the coverage amounts differ by a factor of twenty between Period 1 ($50,000/$100,000/$30,000) and Periods 2-3 ($1,000,000 combined single limit). Getting the app data that proves which period was active is the single most important early step in any Washington rideshare injury case.

Washington's TNC insurance tiers under RCW 46.72B.180 are among the most detailed in the country. During Period 1 — when the driver is logged into the TNC app but has not yet accepted a ride — the TNC must maintain coverage of $50,000 per person for bodily injury, $100,000 per accident for bodily injury, and $30,000 for property damage, plus uninsured/underinsured motorist coverage per RCW 48.22.030 and personal injury protection per RCW 48.22.085 and 48.22.095. During Periods 2 and 3 — from the moment the driver accepts a ride through passenger drop-off — the TNC must maintain a $1,000,000 combined single limit for death, personal injury, and property damage, plus PIP. Period 3 UIM coverage is $100,000 per person and $300,000 per accident. The statute requires this coverage to be maintained 24 hours a day, 7 days a week while the driver is logged in or transporting a passenger. This 24/7 maintenance requirement effectively closes the gap between the driver's personal auto policy — which almost certainly contains a livery exclusion — and the TNC's commercial coverage. Unlike California, Washington's statute does not contain express 'first-dollar' language, but the TNC policy is primary in practice because the personal policy exclusion means there is no other coverage to be primary over. A local Washington rideshare attorney tenders to both carriers and documents the personal-policy denial to establish the TNC policy as the exclusive source of recovery.

Washington is the only state in the country that has created a 'third-category' classification for TNC drivers under RCW 49.46.300, enacted by HB 2076 in 2022. Drivers are classified as independent contractors when the TNC does not prescribe shift dates, times of day, or minimum hours and does not terminate for declining specific rides — but they simultaneously receive a statutory minimum pay floor ($0.59 per passenger platform minute plus $1.38 per passenger platform mile in cities over 600,000 population, or a $5.17 per-trip minimum), paid sick time, paid family and medical leave access, and workers' compensation coverage. This framework rejects both California's Prop 22 approach and the full-employee classification pushed in Massachusetts and New Jersey. For injury cases, the classification matters because the per-trip data records generated by the statutory pay requirements — trip start and end times, distances, route data, pay calculations — are discoverable and create a granular timeline of the driver's activity in the hours leading up to the crash. A driver who had been logged in for twelve consecutive hours, accepting ride after ride to hit a pay target, may have been fatigued — and the trip data proves the pattern. The weekly trip-data notice requirement and 'driver resource center' provisions in RCW 49.46.300 generate records that do not exist in states without comparable TNC labor statutes.

Washington's pure comparative fault rule under RCW 4.22.005 applies to rideshare accidents just as it does to any other personal injury claim. If you were a passenger in a rideshare vehicle that was rear-ended by another driver, fault allocation between the TNC driver and the third-party driver determines which insurance tiers pay and in what proportion. If you were a pedestrian or cyclist hit by a rideshare driver, your own fault may be argued — jaywalking, riding without lights — but it can never bar your recovery entirely. The TNC's insurer will push hard on fault allocation because the difference between Period 1 and Period 2/3 coverage is enormous ($50,000/$100,000/$30,000 versus $1,000,000 CSL). Seattle presents an additional layer: the City of Seattle operates a grandfathered TNC ordinance under SMC 6.310 that overlays the state statute, imposing stricter driver-deactivation review and higher minimum pay within city limits. Rideshare cases arising inside Seattle have two regulatory frameworks generating discoverable records — the state-level RCW 46.72B data and the Seattle-specific SMC 6.310 data. Your attorney should subpoena both. The combination of Washington's pure comparative fault, mandatory $1M Periods 2-3 coverage, $100,000/$300,000 Period-3 UIM, and the richest per-trip data disclosure requirements in the country makes Washington one of the strongest states for rideshare injury claims.