Life Saver Pool Fence Systems Incorporated v. Howard

CourtDistrict Court, D. Arizona
DecidedFebruary 8, 2023
Docket2:22-cv-01556
StatusUnknown

This text of Life Saver Pool Fence Systems Incorporated v. Howard (Life Saver Pool Fence Systems Incorporated v. Howard) is published on Counsel Stack Legal Research, covering District Court, D. Arizona primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Life Saver Pool Fence Systems Incorporated v. Howard, (D. Ariz. 2023).

Opinion

1 WO 2 3 4 5 6 IN THE UNITED STATES DISTRICT COURT 7 FOR THE DISTRICT OF ARIZONA 8

Life Sav er Pool Fence Systems ) No. CV-22-01556-PHX-SPL ) 9 Incorporated, ) 10 ) O R D E R Plaintiff, ) ) 11 vs. ) ) 12 Jason Howard, et al., ) 13 ) ) 14 Defendants. )

15 Before the Court is Defendants’ Motion to Dismiss for Failure to State a Claim 16 (Doc. 15), in which they seek dismissal of Count IV of Plaintiff’s Complaint. For the 17 following reasons, the Motion will be denied.1 18 I. BACKGROUND 19 On September 13, 2022, Plaintiff Life Saver Pool Fence Systems, Inc. initiated 20 this action against Defendants Jason and Tonja Howard, doing business in Arizona as A 21 Safe Pool and The Pool Fence Warehouse. (Doc. 1). Plaintiff is a pool fence 22 manufacturer. (Doc. 1 at 2). In 2008, Defendants became authorized dealers of Plaintiff’s 23 Life Saver pool fences pursuant to a dealership agreement. (Doc. 1 at 4). Plaintiff later 24 terminated the agreement when Defendants allegedly breached the agreement by 25 purchasing pool fences from Plaintiff’s competitors and selling them to customers. (Doc. 26

27 1 Because it would not assist in resolution of the instant issues, the Court finds the pending motion is suitable for decision without oral argument. See LRCiv 7.2(f); Fed. R. 28 Civ. P. 78(b); Partridge v. Reich, 141 F.3d 920, 926 (9th Cir. 1998). 1 1 at 4). Plaintiff alleges that in April 2022, it learned that Defendants were continuing to 2 use the Life Saver name to market and sell competing pool fences. (Doc. 1 at 5). The 3 Complaint includes several alleged text message exchanges between Defendants and 4 customers in which Defendants purported to be selling Life Saver fences when in fact 5 they were selling non-Life Saver fences. (Doc. 1 at 6–7). 6 The Complaint alleges four counts against Defendants: (1) trademark 7 infringement; (2) false designation of origin and unfair competition; (3) unfair 8 competition and palming off; and (4) tortious interference with business expectancy. 9 (Doc. 1). On November 18, 2022, Defendants filed the pending Motion to Dismiss, which 10 requests dismissal only of the tortious interference claim. (Doc. 15). The Motion has been 11 fully briefed. (Docs. 19, 22). 12 II. LEGAL STANDARD 13 To survive a Rule 12(b)(6) motion to dismiss, “a complaint must contain sufficient 14 factual matter, accepted as true, to ‘state a claim to relief that is plausible on its face.’” 15 Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. Corp. v. Twombly, 550 U.S. 16 544, 570 (2007)). A claim is facially plausible when it contains “factual content that 17 allows the court to draw the reasonable inference” that the moving party is liable. Id. 18 Factual allegations in the complaint should be assumed true, and a court should then 19 “determine whether they plausibly give rise to an entitlement to relief.” Id. at 679. Facts 20 should be viewed “in the light most favorable to the non-moving party.” Faulkner v. ADT 21 Sec. Servs., Inc., 706 F.3d 1017, 1019 (9th Cir. 2013). 22 III. DISCUSSION 23 Defendants move to dismiss Count IV of the Complaint, tortious interference with 24 business expectancy. To state a claim for tortious interference, a plaintiff must allege 25 facts showing: 26 (1) the existence of valid contractual relationship or business expectancy; (2) knowledge of the relationship or expectancy 27 on the part of the interferor; (3) intentional interference 28 inducing or causing a breach or termination of the relationship or expectancy; and (4) resultant damage to the 1 party whose relationship or expectancy has been disrupted. 2 Antwerp Diamond Exch. of Am., Inc. v. Better Bus. Bureau of Maricopa Cnty., Inc., 637 3 P.2d 733, 740 (Ariz. 1981). Defendants contest all four elements, which the Court 4 addresses in turn. 5 a. Business Expectancy 6 A business expectancy is “a prospective business relation with another.” Dube v. 7 C. Desai, Inc., No. 2 CA-CV 2007-0142, 2008 WL 4638924, at *1 (Ariz. Ct. App. Apr. 8 4, 2008) (internal quotation marks omitted). “To state a claim for tortious interference 9 upon which relief may be granted, there must be a colorable economic relationship 10 between the plaintiff and a third party with the potential to develop into a full contractual 11 relationship.” Dube v. Likins, 167 P.3d 93, 101 (Ariz. Ct. App. 2007) (internal quotation 12 marks omitted). A plaintiff may allege a business expectancy with a group, such as 13 customers, but that group must be “specifically identifiable.” Id. (citing cases where 14 allegations of interference with a relationship with a company’s “enrollees,” “patients,” 15 and “identifiable customers” were held sufficient). 16 When a plaintiff alleges that a defendant made false or misleading statements 17 about the plaintiff specifically directed to the plaintiff’s prospective customers, the 18 plaintiff has alleged a valid business expectancy. In MiCamp Solutions LLC v. National 19 Processing LLC, the parties entered into a receivables sales agreement by which MiCamp 20 purchased a portfolio of assets, including National Processing’s database of potential 21 customers. No. CV-19-05468-PHX-MTL, 2020 WL 3893570, at *1 (D. Ariz. July 10, 22 2020). National Processing alleged tortious interference with a business expectancy 23 against MiCamp. Id. at *3. Specifically, National Processing alleged that it continued to 24 offer services to businesses not included in the portfolio sold to MiCamp, and that 25 MiCamp was making false representations to those prospective customers that it was 26 National Processing’s parent company and could offer lower rates. Id. The court held that 27 National Processing had sufficiently alleged a business expectancy because even though 28 1 National Processing’s counterclaim did “not specifically identify the other businesses 2 with whom [it] allegedly had a valid business expectancy, . . . interference with the 3 opportunity to obtain customers is sufficient.” Id. (citing Edwards v. Anaconda Co., 565 4 P.2d 190, 192–93 (Ariz. Ct. App. 1977)). 5 Here, Plaintiff alleges that Defendants represented to customers who wanted to 6 buy Life Saver pool fences that Defendants could sell them such products, when 7 Defendants were in fact selling competing pool fences under the Life Saver name. Much 8 like the circumstances in MiCamp, then, Defendants allegedly interfered with Plaintiff’s 9 opportunity to obtain customers for their Life Saver fences. Even though the Complaint 10 does not identify prospective customers by name, it does include text messages between 11 Defendant and certain customers inquiring about Life Saver fences. As Plaintiff has 12 alleged that Defendant misled Plaintiff’s prospective customers with respect to Plaintiff’s 13 products, Plaintiff has sufficiently pled a business expectancy. 14 b. Knowledge of Expectancy 15 A defendant need not have knowledge of a specific expectancy so long as the 16 defendant knows that the plaintiff is continually doing business; a defendant’s “intent to 17 keep away all who might otherwise deal with the plaintiff” suffices. Edwards, 565 P.2d at 18 192. Again, this case is analogous to MiCamp, where the Court found that “[t]he fact that 19 MiCamp mentioned undercutting National Processing’s rates, if true, suggests that 20 MiCamp had knowledge of National Processing’s legitimate business expectancy in those 21 business relationships.” MiCamp Sols. LLC, 2020 WL 3893570, at *3.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Watters v. Wachovia Bank, N. A.
550 U.S. 1 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
John Faulkner v. Adt Security Services, Inc.
706 F.3d 1017 (Ninth Circuit, 2013)
Dube v. Likins
167 P.3d 93 (Court of Appeals of Arizona, 2007)
Metropolitan C. Ins. Co. v. Indus. Acc. Com.
4 P.2d 190 (California Court of Appeal, 1931)

Cite This Page — Counsel Stack

Bluebook (online)
Life Saver Pool Fence Systems Incorporated v. Howard, Counsel Stack Legal Research, https://law.counselstack.com/opinion/life-saver-pool-fence-systems-incorporated-v-howard-azd-2023.