<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:wfw="http://wellformedweb.org/CommentAPI/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
     xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
     xmlns:georss="http://www.georss.org/georss"
     xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
     xmlns:media="http://search.yahoo.com/mrss/">
    <channel>
        <title><![CDATA[haddad v lyft florida - Jeffrey P. Gale, P.A.]]></title>
        <atom:link href="https://www.jeffgalelaw.com/blog/tags/haddad-v-lyft-florida/feed/" rel="self" type="application/rss+xml" />
        <link>https://www.jeffgalelaw.com/blog/tags/haddad-v-lyft-florida/</link>
        <description><![CDATA[Jeffrey P. Gale, P.A.'s Website]]></description>
        <lastBuildDate>Mon, 17 Aug 2026 23:35:57 GMT</lastBuildDate>
        
        <language>en-us</language>
        
            <item>
                <title><![CDATA[Jeffrey P. Gale, P.A. // Understanding Haddad v. Lyft Florida, Inc.]]></title>
                <link>https://www.jeffgalelaw.com/blog/jeffrey-p-gale-p-a-understanding-haddad-v-lyft-florida-inc/</link>
                <guid isPermaLink="true">https://www.jeffgalelaw.com/blog/jeffrey-p-gale-p-a-understanding-haddad-v-lyft-florida-inc/</guid>
                <dc:creator><![CDATA[Jeffrey P. Gale, P.A.]]></dc:creator>
                <pubDate>Mon, 17 Aug 2026 21:39:28 GMT</pubDate>
                
                    <category><![CDATA[Car, Truck & Motorcycle Accidents]]></category>
                
                    <category><![CDATA[Civil Litigation]]></category>
                
                    <category><![CDATA[Miscellaneous]]></category>
                
                
                    <category><![CDATA[fourth dca]]></category>
                
                    <category><![CDATA[haddad v lyft florida]]></category>
                
                    <category><![CDATA[inc. 627.748]]></category>
                
                    <category><![CDATA[lyft]]></category>
                
                    <category><![CDATA[ride-share injuries]]></category>
                
                    <category><![CDATA[statute 768.096]]></category>
                
                    <category><![CDATA[transportation network companies]]></category>
                
                    <category><![CDATA[uber]]></category>
                
                
                
                <description><![CDATA[<p>In May 2026, the Fourth District Court of Appeal issued a consequential opinion in Haddad v. Lyft Florida, Inc., fundamentally reshaping the scope of tort claims that may be brought against transportation network companies in Florida. Haddad effectively wiped out the entire suite of common‑law causes of action traditionally asserted against rideshare companies, unless the&hellip;</p>
]]></description>
                <content:encoded><![CDATA[
<p class="has-medium-font-size">In May 2026, the <a href="https://4dca.flcourts.gov/" target="_blank" rel="noreferrer noopener">Fourth District Court of Appeal</a> issued a consequential opinion in <em><a href="https://scholar.google.com/scholar_case?case=6280273538432994566&q=Haddad+v.+Lyft+Florida,+Inc.&hl=en&as_sdt=40006" target="_blank" rel="noreferrer noopener"><em>Haddad v. Lyft Florida, Inc</em>.</a></em>, fundamentally reshaping the scope of tort claims that may be brought against <a href="https://www.urbanismnext.org/technologies/transportation-network-companies" target="_blank" rel="noreferrer noopener">transportation network companies</a> in Florida. <em>Haddad</em> effectively wiped out the entire suite of common‑law causes of action traditionally asserted against rideshare companies, unless the plaintiff can anchor the duty to a specific statutory requirement in <a href="https://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&Search_String=&URL=0600-0699/0627/Sections/0627.748.html" target="_blank" rel="noreferrer noopener">§ 627.748, Florida Statutes</a>.</p>



<p class="has-text-align-center has-large-font-size"><strong>Common‑Law Causes of Action Eliminated by <em>Haddad v. Lyft Florida, Inc.</em></strong> </p>



<p class="has-medium-font-size">(Unless tied to a statutory violation)**</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-1-negligent-hiring"><strong>1. <a href="https://www.aihr.com/hr-glossary/negligent-hiring/" target="_blank" rel="noreferrer noopener">Negligent Hiring</a></strong></h2>



<p>Any claim that Lyft/Uber owed a <em>common‑law duty</em> to hire safe drivers is barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently hired a driver with a history of reckless driving.”</li>
</ul>



<p><strong>Why eliminated:</strong> The statute defines the duty (background check). Common‑law hiring duties are preempted.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-2-negligent-retentio-n"><strong>2. </strong><a href="https://www.vidahr.com/post/what-is-negligent-retention-when-keeping-an-employee-becomes-a-liability" target="_blank" rel="noreferrer noopener"><strong>Negligent Retentio</strong>n</a></h2>



<p>Claims that Lyft should have removed a dangerous driver based on complaints or prior incidents are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently retained a driver despite multiple passenger complaints.”</li>
</ul>



<p><strong>Why eliminated:</strong> Only statutory disqualification duties survive.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-3-negligent-supervision"><strong>3. Negligent Supervision</strong></h2>



<p>General allegations that Lyft failed to supervise or monitor drivers are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently supervised its drivers and failed to ensure safe operation.”</li>
</ul>



<p><strong>Why eliminated:</strong> The statute does not impose a supervision duty; common‑law supervision is preempted.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-4-negligent-training"><strong>4. Negligent Training</strong></h2>



<p>Claims that Lyft should have trained drivers better (safe driving, passenger handling, emergency procedures) are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently failed to train its drivers on passenger safety.”</li>
</ul>



<p><strong>Why eliminated:</strong> The statute imposes no training duty; common‑law training duties are preempted.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-5-negligent-failure-to-protect-passengers"><strong>5. Negligent Failure to Protect Passengers</strong></h2>



<p>Claims that Lyft owed a common‑law duty to protect passengers from foreseeable harm (driver assault, reckless driving, unsafe conditions) are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently failed to protect the passenger from the driver’s violent behavior.”</li>
</ul>



<p><strong>Why eliminated:</strong> Only statutory background‑check and zero‑tolerance duties survive.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-6-negligent-failure-to-warn"><strong>6. Negligent Failure to Warn</strong></h2>



<p>Claims that Lyft should have warned passengers about risks associated with rideshare use are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently failed to warn passengers that drivers may have criminal histories.”</li>
</ul>



<h2 class="wp-block-heading has-medium-font-size" id="h-7-negligent-safety-representations"><strong>7. Negligent Safety Representations</strong></h2>



<p>Claims that Lyft negligently represented its rides as “safe,” “secure,” or “professionally vetted” are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently advertised that its rides were safe.”</li>
</ul>



<p><strong>Why eliminated:</strong> <em>Haddad</em> held that misrepresentation claims arising from the ride fall within statutory immunity.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-8-negligent-operation-of-a-transportation-service"><strong>8. Negligent Operation of a Transportation Service</strong></h2>



<p>Claims that Lyft negligently operated its rideshare platform or transportation network are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently operated its service by allowing unsafe vehicles on the road.”</li>
</ul>



<h2 class="wp-block-heading has-medium-font-size" id="h-9-negligent-infliction-of-emotional-distress-nied"><strong>9. Negligent Infliction of Emotional Distress (NIED)</strong></h2>



<p>NIED claims arising from the ride are barred unless tied to statutory violations.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently caused emotional distress by allowing an unsafe driver to transport the plaintiff.”</li>
</ul>



<h2 class="wp-block-heading has-medium-font-size" id="h-10-negligent-failure-to-implement-additional-safety-measures"><strong>10. Negligent Failure to Implement Additional Safety Measures</strong></h2>



<p>Claims that Lyft should have done “more” than the statute requires — enhanced background checks, in‑car cameras, stricter monitoring — are barred.</p>



<p><strong>Example:</strong></p>



<ul class="wp-block-list">
<li>“Lyft negligently failed to install in‑vehicle cameras to protect passengers.”</li>
</ul>



<p><strong>Why eliminated:</strong> <em>Haddad</em> expressly rejected negligence theories based on duties beyond the statute.</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-11-negligent-misrepresentation-amp-fraudulent-misrepresentation"><strong>11. Negligent Misrepresentation & Fraudulent Misrepresentation</strong></h2>



<p>Claims based on Lyft’s marketing, app statements, or website assurances are barred. </p>



<p><strong>Example:</strong></p>



<p>“Lyft negligently misrepresented that its drivers were thoroughly vetted.”</p>



<h2 class="wp-block-heading has-medium-font-size" id="h-12-vicarious-liability-for-driver-negligence-or-misconduct"><strong>12. Vicarious Liability for Driver Negligence or Misconduct</strong></h2>



<p>Common‑law vicarious liability theories are barred unless the TNC owned or was bailee of the vehicle.</p>



<p><strong>Example:</strong></p>



<p class="has-medium-font-size">“Lyft is vicariously liable for the driver’s negligent operation of the vehicle.”</p>



<p class="has-medium-font-size">The <em>Haddad</em> Court framed the facts of the case as follows:</p>



<p class="has-medium-font-size">“Louise Haddad claims she was assaulted by her Lyft driver. She sued Lyft for negligent and fraudulent misrepresentation, alleging that statements on its website led her to believe that the ride would be safe, thus leading to the personal injuries she suffered at the hands of the driver.”</p>



<p class="has-medium-font-size">Lyft argued that section 627.748(18), Florida Statutes (2022) (“Subsection 18”), provided it with&nbsp;<em>immunity</em>&nbsp;against her claims. The trial court agreed and dismissed the complaint.</p>



<p class="has-medium-font-size">Section 627.748(18), Florida Statutes (2022), provides:</p>



<blockquote class="wp-block-quote has-medium-font-size is-layout-flow wp-block-quote-is-layout-flow">
<p class="has-medium-font-size">Vicarious liability.—</p>
</blockquote>



<blockquote class="wp-block-quote has-medium-font-size is-layout-flow wp-block-quote-is-layout-flow">
<p class="has-medium-font-size">(a) A TNC is not liable under general law by reason of owning, operating, or maintaining the digital network accessed by a TNC driver or rider, or by being the TNC affiliated with a TNC driver, for harm to persons or property which results or arises out of the use, operation, or possession of a motor vehicle operating as a TNC vehicle while the driver is logged on to the digital network if:</p>
</blockquote>



<blockquote class="wp-block-quote has-medium-font-size is-layout-flow wp-block-quote-is-layout-flow">
<p class="has-medium-font-size">1. There is no negligence under this section or criminal wrongdoing under the federal or Florida criminal code on the part of the TNC;</p>
</blockquote>



<blockquote class="wp-block-quote has-medium-font-size is-layout-flow wp-block-quote-is-layout-flow">
<p class="has-medium-font-size">2. The TNC has fulfilled all of its obligations under this section with respect to the TNC driver; and</p>
</blockquote>



<blockquote class="wp-block-quote has-medium-font-size is-layout-flow wp-block-quote-is-layout-flow">
<p class="has-medium-font-size">3. The TNC is not the owner or bailee of the motor vehicle that caused harm to persons or property.</p>



<p class="has-medium-font-size">(b) This subsection does not alter or reduce the coverage or policy limits of the insurance requirements under subsection (7) or the liability of any person other than the vicarious liability of a TNC as described in paragraph (a).</p>
</blockquote>



<p class="has-medium-font-size">Florida Statute § 627.748 governs Transportation Network Companies—such as Uber and Lyft—and establishes the regulatory framework applicable to their operations in Florida.</p>



<p class="has-medium-font-size">Section 627.748(12) delineates the <strong>exclusive statutory duties</strong> imposed on transportation network companies. These are the specific obligations incorporated by reference in Section 627.748(18)(a)2. A rideshare company may be held liable for negligence <strong>only</strong> if it breaches one or more of these enumerated duties <strong>and</strong> that statutory breach proximately causes the claimant’s harm. In other words, liability now arises solely from <strong>statutory‑based negligence</strong>, not from any general‑law tort theory.</p>



<p class="has-medium-font-size">Although Florida law classifies rideshare drivers as <strong><a href="https://en.wikipedia.org/wiki/Independent_contracting_in_the_United_States" target="_blank" rel="noreferrer noopener">independent contractors</a></strong> rather than employees of transportation network companies, § 627.748(12) nevertheless imposes a suite of <strong>mandatory safety, screening, and operational duties</strong> on TNCs that closely resemble the oversight obligations traditionally associated with employers. In effect, the Legislature has required TNCs to conduct background checks, verify driver eligibility, maintain specified insurance, and enforce safety‑related policies even in the absence of an employer‑employee relationship.</p>



<p class="has-medium-font-size">This statutory structure parallels § 768.096, which affords employers a <strong>rebuttable presumption</strong> against negligent hiring when they perform the background investigation prescribed by that statute. Although § 627.748(12) establishes a distinct, TNC‑specific set of screening and safety requirements, both provisions reflect a common legislative judgment: <strong>compliance with defined background‑check and vetting duties serves as a liability shield</strong>, while noncompliance exposes the entity to negligence claims grounded in statutory breach.</p>



<p class="has-medium-font-size">Neither <em>Haddad</em> nor § 627.748(18) disturb the mandatory insurance protections in § 627.748(7), which continue to provide coverage for injuries caused by a rideshare driver’s negligent operation of the vehicle while logged on to the digital network. These insurance obligations remain fully intact, even though tort claims against the TNC itself are largely barred.</p>



<p>*************************************************</p>



<p class="has-medium-font-size"><strong>Contact us today at (305) 758-4900 or by email for a free consultation to learn your legal rights. If we accept your case, we will represent you on a contingency fee basis — meaning you pay no upfront costs. Our fee is collected only if we obtain a favorable recovery on your behalf. If there is no recovery, you owe nothing.</strong></p>



<p class="has-medium-font-size"><a href="https://www.jeffgalelaw.com/">Jeffrey P. Gale, P.A.</a>&nbsp;is a&nbsp;<a href="https://www.google.com/search?q=south+florida&rls=com.microsoft:en-US:IE-Address&rlz=1I7MXGB_enUS635&source=lnms&tbm=isch&sa=X&ved=0ahUKEwj_sKjTobrQAhUBhiYKHea4CPIQ_AUICigD&biw=1097&bih=498" rel="noreferrer noopener" target="_blank">South Florida</a>&nbsp;based law firm committed to the judicial system and to representing and obtaining justice for individuals – the poor, the injured, the forgotten, the voiceless, the defenseless and the damned, and to protecting the rights of such people from corporate and government oppression. We do not represent government, corporations or large business interests.</p>



<p class="has-medium-font-size">While prompt resolution of your legal matter is our goal, our approach is fundamentally different. Our clients are “people” and not “cases” or “files.” We take the time to build a relationship with our clients, realizing that only through meaningful interaction can we best serve their needs. In this manner, we have been able to best help those requiring legal representation.</p>



<p class="has-medium-font-size"><strong>DISCLAIMER</strong>: This information provided by Jeffrey P. Gale, P.A. is for informational purposes only and is intended to be used as a non-legal guide prior to consultation with an attorney familiar with your specific legal situation. It should not be considered legal advice or counseling. No such legal advice or counseling is either expressly or impliedly intended. This information is not a substitute for the advice or counsel of an attorney. If you require legal advice, you should seek the services of an attorney.</p>



<p class="has-medium-font-size"><strong>Our firm is always grateful for the many cases we receive through referrals from fellow attorneys, and we routinely pay referral fees to our referring counsel in accordance with applicable ethical rules.</strong></p>
]]></content:encoded>
            </item>
        
    </channel>
</rss>