R2 Solutions LLC v. Allegiant Travel Company

CourtDistrict Court, E.D. Texas
DecidedApril 24, 2023
Docket4:22-cv-00537
StatusUnknown

This text of R2 Solutions LLC v. Allegiant Travel Company (R2 Solutions LLC v. Allegiant Travel Company) is published on Counsel Stack Legal Research, covering District Court, E.D. Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
R2 Solutions LLC v. Allegiant Travel Company, (E.D. Tex. 2023).

Opinion

United States District Court EASTERN DISTRICT OF TEXAS SHERMAN DIVISION

R2 SOLUTIONS LLC, § § Plaintiff, § § Civil Action No. 4:22-CV-00537 v. § Judge Mazzant § ALLEGIANT TRAVEL COMPANY, § § Defendant. § §

MEMORANDUM OPINION AND ORDER

Pending before the Court is Defendant Allegiant Travel Company’s Motion to Dismiss Plaintiff R2 Solutions LLC’s Complaint (Dkt. #10). Having considered the motion, the response, and the relevant pleadings, the Court finds that the motion should be DENIED.1 BACKGROUND This contractual dispute arises from patent licensing negotiations gone awry. Plaintiff R2 Solutions LLC (“R2”) is a Texas limited liability company with its principal place of business in Frisco, Texas (Dkt. #2 ¶ 3). Defendant Allegiant Travel Company (“Allegiant”) is a Nevada corporation with its principal place of business in Las Vegas, Nevada (Dkt. #2 ¶ 4). I. Licensing Negotiations R2 first contacted Allegiant regarding licensing opportunities in June 2021 (Dkt. #2 ¶ 10). After four months with no response, R2 sent a pair of follow-up emails to Allegiant in October 2021 (Dkt. #2 ¶ 10). Allegiant then responded through its general counsel, and the parties engaged in protracted licensing discussions (Dkt. #10 at p. 10).

1 This Order addresses Allegiant’s arguments concerning the lack of personal jurisdiction and improper venue. The Court will address Allegiant’s argument concerning the first-to-file rule in a separate order. As a part of those discussions, R2 and Allegiant negotiated a confidentiality agreement (the “Agreement”) (Dkt. #2 ¶ 1). After executing the Agreement, R2 sent more detailed communications to Allegiant, which included specific patents from R2’s portfolio that it considered relevant to Allegiant’s operations and claim charts mapping the disclosed patents to

specific Allegiant products and services (Dkt. #2 ¶ 14). R2 also referred to several pending cases in which it has asserted the same patents that it disclosed to Allegiant (Dkt. #10 at p. 11). II. The Nevada Action Following several months of fruitless licensing discussions, Allegiant sought a declaratory judgment of non-infringement in the United States District Court for the District of Nevada on May 24, 2022. Allegiant Travel Co. v. R2 Solutions LLC, 2:22-CV-00828 (D. Nev. May 24, 2022) (the “Nevada Action”).2 R2 responded on July 14, 2022, moving to dismiss the Nevada Action on three separate grounds (No. 2:22-CV-00828, Dkt. #26). First, R2 contends that the Nevada court lacks subject-matter jurisdiction over Allegiant’s request for declaratory relief because Allegiant’s complaint is improperly based on information that is confidential under the Agreement

(No. 2:22-CV-00828, Dkt. #26 at pp. 12–13). Second, R2 contends that the Nevada court should exercise its discretion under the Declaratory Judgment Act and dismiss the case as an improper anticipatory filing, arguing that Allegiant brought the case solely to gain a tactical advantage in licensing negotiations (No. 2:22-CV-00828, Dkt. #26 at pp. 19–21). And finally, R2 argues that it is not subject to personal jurisdiction in Nevada (No. 2:22-CV-00828, Dkt. #26 at pp. 21–26). R2’s motion to dismiss in the Nevada Action remains pending.

2 The Court takes judicial notice of the docket entries and judicial documents filed in the Nevada Action. See Polnac v. City of Sulphur Springs, 555 F. Supp. 3d 309, 327 (E.D. Tex. 2021) (“Documents in judicial actions and cases’ dockets are public records of which any court can take judicial notice.”) (internal citations omitted); see also FED. R. EVID. 201. The Court will refer to any filings in the Nevada Action by its case number (No. 2:22-CV-00828) and the appropriate docket entry. III. Procedural History In addition to its motion to dismiss in the Nevada Action, R2 responded to Allegiant’s complaint for declaratory relief by filing the current case on June 28, 2022 (Dkt. #2). R2 asserts a single cause of action for breach of contract, alleging that Allegiant breached the Agreement when

it filed the Nevada Action because Allegiant’s complaint discloses R2’s confidential information (Dkt. #2 ¶¶ 18–26). On August 19, 2022, Allegiant moved to dismiss this case for lack of personal jurisdiction and improper venue, or, alternatively, to transfer it to the District of Nevada under the first-to-file rule (Dkt. #10). R2 responded on September 16, 2022 (Dkt. #19). Allegiant filed a reply on September 30, 2022, and R2 filed its sur-reply one week later (Dkt. #24; Dkt. #31). On April 18, 2023, the Court held a status conference with the parties concerning the parties’ pending motions. Consistent with the Court’s statements in that status conference, this Order addresses the portions of Allegiant’s motion to dismiss involving personal jurisdiction and improper venue (Dkt. #10). The Court will address Allegiant’s arguments regarding the first-to- file rule in a separate order.

LEGAL STANDARD I. Personal Jurisdiction Federal Rule of Civil Procedure 12(b)(2) requires a court to dismiss a claim if the court does not have personal jurisdiction over the defendant. FED. R. CIV. P. 12(b)(2). After a non-resident defendant files a motion to dismiss for lack of personal jurisdiction, it is the plaintiff’s burden to establish that in personam jurisdiction exists. See, e.g., Luv N’ Care, Ltd. v. Insta-Mix, Inc., 438 F.3d 465, 469 (5th Cir. 2006). To satisfy that burden, the party seeking to invoke the Court’s jurisdiction must “present sufficient facts as to make out only a prima facie case supporting jurisdiction,” if a court rules on a motion without an evidentiary hearing. Alpine View Co. v. Atlas Copco AB, 205 F.3d 208, 215 (5th Cir. 2000). When considering the motion to dismiss, courts take allegations in a plaintiff’s complaint as true except to the extent that they are contradicted by defendant’s affidavits. Int’l Truck & Engine Corp. v. Quintana, 259 F. Supp. 2d 553, 557 (N.D. Tex. 2003) (citing Wyatt v. Kaplan, 686 F.2d 276, 282–83 n.13 (5th Cir. 1982)).3 That is, courts accept a plaintiff’s non-

conclusory, uncontroverted allegations as true, and resolve factual conflicts contained in the parties’ affidavits in the plaintiff’s favor. See, e.g., Panda Brandywine Corp. v. Potomac Elec. Power Co., 253 F.3d 865, 868 (5th Cir. 2001). II. Improper Venue A party may challenge venue by asserting that venue is improper in a responsive pleading or by filing a motion. FED. R. CIV. P. 12(b)(3). The Fifth Circuit has yet to indicate which party bears the burden on a Rule 12(b)(3) motion, but “most district courts within this circuit have imposed the burden of proving that venue is proper on the plaintiff once a defendant has objected to the plaintiff’s chosen forum.” Galderma Labs., L.P. v. Teva Pharm. USA, Inc., 290 F. Supp. 3d

599, 605 (N.D. Tex. 2017) (collecting cases); see also Provitas, LLC v. Quality Ingredients Corp., No. 4:21-CV-00196, 2021 WL 5907790, at *7 (E.D. Tex. Dec. 14, 2021) (“Once a defendant raises improper venue by motion, the burden of sustaining venue will be on the plaintiff”) (cleaned up). A plaintiff may satisfy this burden by showing facts that, if taken as true, establish that venue is proper. Provitas, 2021 WL 5907790, at *7. The Court “must accept as true all allegations in the complaint and resolve all conflicts in favor of the plaintiff.” Mayfield v. Sallyport Glob. Holdings,

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

Related

Latshaw v. Johnston
167 F.3d 208 (Fifth Circuit, 1999)
Alpine View Co Ltd v. Atlas Copco AB
205 F.3d 208 (Fifth Circuit, 2000)
Central Freight Lines Inc. v. APA Transport Corp.
322 F.3d 376 (Fifth Circuit, 2003)
Religious Technology Center v. Liebreich
339 F.3d 369 (Fifth Circuit, 2003)
Freudensprung v. Offshore Technical Services, Inc.
379 F.3d 327 (Fifth Circuit, 2004)
Luv N' Care, Ltd. v. Insta-Mix, Inc.
438 F.3d 465 (Fifth Circuit, 2006)
Seiferth v. Helicopteros Atuneros, Inc.
472 F.3d 266 (Fifth Circuit, 2006)
Ambraco, Inc. v. Bossclip B.V.
570 F.3d 233 (Fifth Circuit, 2009)
McFadin v. Gerber
587 F.3d 753 (Fifth Circuit, 2009)
International Shoe Co. v. Washington
326 U.S. 310 (Supreme Court, 1945)
Burger King Corp. v. Rudzewicz
471 U.S. 462 (Supreme Court, 1985)
Clemens v. McNamee
615 F.3d 374 (Fifth Circuit, 2010)
Goodyear Dunlop Tires Operations, S. A. v. Brown
131 S. Ct. 2846 (Supreme Court, 2011)
Oscar Wyatt, Jr. v. Jerome Kaplan
686 F.2d 276 (Fifth Circuit, 1982)
Carol Bullion v. Larrian Gillespie, M.D.
895 F.2d 213 (Fifth Circuit, 1990)
The Akro Corporation v. Ken Luker
45 F.3d 1541 (Federal Circuit, 1995)

Cite This Page — Counsel Stack

Bluebook (online)
R2 Solutions LLC v. Allegiant Travel Company, Counsel Stack Legal Research, https://law.counselstack.com/opinion/r2-solutions-llc-v-allegiant-travel-company-txed-2023.