Uber driver accused of kidnapping a drunk passenger and taking her to a motel, but wasn't on the Uber system at the time
Uber Driver Allegedly Kidnapped L.A. Club-Goer, Took Her to Motel — A 26-year-old female clubgoer was allegedly kidnapped by an Uber driver and taken to a motel in Panorama City, police said today.
Context & Ripple Effects
The story moved fast and wide: within a day of the LAPD account, the Los Angeles Times, CBS Los Angeles, ABC7, NBC Southern California, KTLA and KTTV had all carried it, and Uber published its own blog response the same day — unusual speed for the company, whose key talking point was that the accused driver was not active on the Uber system when the alleged abduction happened. That off-app detail is doing heavy lifting: it lets Uber frame the case as driver misconduct rather than a failure of its service.
The timing sharpens the stakes. Uber is reported (though unconfirmed) to be weighing a round at valuations above $10 billion and possibly near $17 billion, and weeks earlier a New York Taxi commission official had confirmed plans to join the company as head of policy development. A kidnapping accusation attached to an 'Uber driver' label — even an off-shift one — lands squarely on the two fronts, investor confidence and regulator relations, where Uber is most exposed in mid-2014. It also feeds the ongoing argument over the company's model, in which drivers shift from employee status to sole proprietors, blurring who answers when one of them harms a rider.
First-order effects
- LAPD is pursuing the accused driver, while Uber's same-day blog statement works to wall the case off from its platform by pointing out he was not logged into the Uber system at the time.
Second-order effects
- Taxi interests and city regulators gain a concrete exhibit for their case that 'Uber driver' branding carries public expectations the company disclaims contractually, complicating the policy-hiring and lobbying push underway.
- Rival services and Uber alike face renewed questions about driver screening and off-shift conduct — whether a driver's badge and car read as 'on duty' to passengers regardless of app status.
Third-order effects
- If the pattern holds, the practical resolution points toward continuous driver vetting and explicit platform-liability boundaries — a structural test of the independent-contractor model in which harm by an off-app driver sits in a legal gray zone between company and sole proprietor.
The trend: As ride-hailing scales, every high-profile driver misconduct case forces platforms to define where corporate responsibility begins and ends when the app is switched off.