When Is a Rideshare Company Liable in Florida? What Haddad v. Lyft Changes
A rideshare injury case can look simple at first: identify the driver, identify the app, and determine who caused the harm. Florida law makes the company-liability question much more exacting. The answer can depend not only on what happened in the vehicle, but also on whether the driver was logged into the platform, whether the transportation network company complied with its statutory duties, who owned the vehicle, and how the complaint is pleaded.
That distinction became sharper in Haddad v. Lyft Florida, Inc., a May 13, 2026 decision from Florida’s Fourth District Court of Appeal. The court read Florida’s rideshare immunity provision broadly—even where the plaintiff characterized her claims as Lyft’s own negligent and fraudulent misrepresentations rather than merely an attempt to hold Lyft responsible for its driver. For injured riders and motorists, the decision is a reminder that a rideshare claim must be investigated party by party, coverage period by coverage period, and statute by statute.
What the court actually decided in Haddad
The plaintiff alleged that a Lyft driver assaulted her during an April 2022 ride and caused severe, permanent injuries. She sued the driver and asserted negligent and fraudulent misrepresentation claims against Lyft. According to the complaint, statements about driver screening and safety measures on Lyft’s website led her to believe the ride would be safe.
The merits of those allegations were not decided. The issue on appeal was whether section 627.748(18), Florida Statutes, barred the claims against Lyft. In its published opinion, the Fourth DCA affirmed the dismissal with prejudice.
The result is important because the plaintiff did not rely solely on traditional vicarious liability—the doctrine that can make one party answer for another person’s conduct. She alleged that Lyft’s own representations caused her to use the service and encounter the driver. The court nevertheless held that the statutory text reached those claims.
Why the heading “vicarious liability” did not narrow the statute
Subsection 18 is titled “Vicarious Liability,” but the court focused on the operative words rather than the heading. The provision says a transportation network company is not liable under general law, by reason of operating or maintaining the digital network or being affiliated with the driver, for harm arising out of the use, operation, or possession of a vehicle operating as a TNC vehicle while the driver is logged on—if the statute’s stated conditions are met.
The Fourth DCA treated that language as broader than conventional vicarious liability. It reasoned that “under general law,” “by reason of,” and “arises out of” collectively sweep beyond a claim based only on an employment relationship. On the allegations before it, Lyft’s network and affiliation with the driver were part of the causal chain the plaintiff herself described.
That means labels are unlikely to decide the issue. Calling a count “direct negligence,” “negligent misrepresentation,” or something similar does not necessarily take it outside subsection 18. Courts will examine the facts alleged, the connection between the platform and the harm, and the statutory conditions.
The three conditions that control the immunity analysis
Florida’s statute does not say that every rideshare company is immune from every claim. Subsection 18 applies when three conditions are satisfied: there is no negligence under section 627.748 or federal or Florida criminal wrongdoing by the company; the company fulfilled all obligations under the section concerning the driver; and the company was not the owner or bailee of the vehicle that caused the harm.
Haddad gives special meaning to the first condition. The court held that “negligence under this section” means negligent failure to meet a requirement imposed by section 627.748. It does not mean any ordinary negligence that happens to relate to operation of a rideshare network. That makes the company’s compliance with the statute—not merely the theory named in the complaint—a central factual and legal question.
The statute addresses driver background checks, driving-history reviews, insurance, zero-tolerance procedures for drug and alcohol complaints, record retention, vehicle requirements, and other duties. A suspected violation must still be tied to provable facts and the elements of a viable claim. The absence of an immunity condition does not automatically establish negligence or damages; it means the analysis cannot end with the statutory shield.
What Haddad did not take away
The decision does not erase the potential liability of the rideshare driver, another at-fault motorist, a vehicle owner, or any other responsible person. Subsection 18(b) expressly says that the provision does not reduce the statutory insurance requirements or alter the liability of persons other than the TNC liability described in the immunity paragraph.
Nor does the decision mean the rideshare company’s compliance should simply be assumed. The opinion explains that the default rule can be addressed at the motion-to-dismiss stage when the complaint does not allege facts supporting an exception. The trial court had given the plaintiff an opportunity to amend, and the Fourth DCA concluded that the amended pleading still did not allege a negligent statutory violation, company criminal wrongdoing, failure to fulfill obligations regarding the driver, or company ownership or bailment of the vehicle.
For a claimant, the practical lesson is not to overstate company liability before the evidence is known. It is to investigate the statutory predicates early and plead facts rather than conclusions. For background on the immediate health and evidence decisions after a collision, Tucker Law’s guide on what to do after an Uber accident addresses the first steps. The company-immunity analysis begins after those fundamentals are protected.
App status still determines the insurance layer
Company immunity and insurance coverage are related questions, but they are not the same question. Section 627.748(7) requires different coverage depending on the driver’s status in the digital network.
When the driver is logged on but has not accepted a prearranged ride, the statute requires at least $50,000 in bodily-injury liability coverage per person, $100,000 per incident, and $25,000 for property damage, along with the required personal injury protection and uninsured or underinsured motorist coverage. Once the driver is engaged in a prearranged ride, the statute requires at least $1 million in primary automobile liability coverage for death, bodily injury, and property damage, plus the required PIP and UM/UIM coverage. If the app was off, the TNC coverage framework does not apply in the same way, and the language of the driver’s personal policy becomes critical.
Those categories are why a rideshare case cannot be evaluated from the crash report alone. A report may identify the vehicles and record statements, yet say nothing definitive about when a request was accepted or whether the trip had ended.
The timestamps are evidence, not a technical detail
Florida law anticipates the app-status dispute. During a coverage investigation, subsection 8 requires a TNC, upon an authorized request, to provide the precise times when the driver logged on and off during the 12 hours before and the 12 hours after the accident. Subsection 15 also requires individual ride records to be kept for at least one year and driver records for at least one year after the driver’s relationship with the company ends.
That makes preservation especially important. The trip receipt, pickup and destination data, in-app messages, screenshots, driver identity, license-plate information, phone records, dash-camera footage, nearby surveillance, vehicle downloads, witness contacts, and medical documentation can collectively establish far more than any single item. They may show whether the ride was active, which insurance period applied, who controlled the vehicle, and whether facts exist to examine the company’s statutory compliance.
People injured in a rideshare collision can also review Tucker Law’s Florida car accident practice and Personal Injury Information Center for broader information about claims, treatment, and evidence. The important point is to avoid treating “Uber’s insurance” or “Lyft’s liability” as a single answer. They are separate questions that change with the facts.
A better way to frame a Florida rideshare claim
After Haddad, the useful first question is not simply, “Can I sue the rideshare company?” The better inquiry is: who caused the harm, what was the driver’s exact platform status, which policies applied, did the company satisfy each relevant statutory duty, and does the evidence support a recognized claim against each potential defendant?
That approach also prevents two opposite mistakes. One is assuming the platform must pay merely because its name appeared on the app. The other is accepting a broad immunity argument without testing the statutory conditions, ownership facts, available insurance, and responsibility of other parties.
Rideshare cases move quickly, and important electronic evidence may not remain readily accessible. If you were injured as a passenger, driver, pedestrian, cyclist, or occupant of another vehicle, Tucker Law can examine the platform timeline, the applicable insurance periods, and the responsible parties before those issues harden into an insurer’s version of events. Contact Tucker Law through its Fort Lauderdale personal injury office for a free case review.
This article provides general information about Florida law and is not legal advice. Every claim depends on its facts, the available evidence, and the law in effect when the event occurred.
