JET SYSTEMS, LLC v. UNITED STATES OF AMERICA

CourtDistrict Court, D. Maryland
DecidedNovember 19, 2025
Docket8:25-cv-01218
StatusUnknown

This text of JET SYSTEMS, LLC v. UNITED STATES OF AMERICA (JET SYSTEMS, LLC v. UNITED STATES OF AMERICA) is published on Counsel Stack Legal Research, covering District Court, D. Maryland primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
JET SYSTEMS, LLC v. UNITED STATES OF AMERICA, (D. Md. 2025).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF MARYLAND

: JET SYSTEMS, LLC :

v. : Civil Action No. DKC 25-1218

: UNITED STATES OF AMERICA :

MEMORANDUM OPINION Presently pending and ready for resolution in this conversion case is the motion to dismiss for failure to state a claim filed by the United States of America (“Defendant”). (ECF No. 13). The issues have been briefed, and the court now rules, no hearing being deemed necessary. Local Rule 105.6. For the following reasons, the motion to dismiss will be granted. I. Background A. Factual Background1 This dispute arises from the U.S. Navy’s treatment of Plaintiff JET Systems, LLC’s (“Plaintiff” or “JET”) software and the CD on which it was provided. Plaintiff is a government contractor that provides software services to government agencies, including branches of the military. (ECF No. 12 ¶ 4). In general, Plaintiff “develops, maintains, and innovates systems for specific

1 The facts herein are undisputed unless otherwise noted. and common mission capabilities, combat aides, and surveillance systems.” (Id.). Plaintiff “provides solutions through cost- effective, tailored strategies to meet mission requirements to

include both new software generation and certified software re- use.” (Id.). The Government uses Plaintiff’s services “to provide ongoing support activity or to prepare the customer to be a lead systems integrator.” (Id.). Additionally, Plaintiff “has developed its proprietary Adaptive Layer Framework (‘ALF’) software products and documentation.” (Id.). Plaintiff “has registered its copyright” in its proprietary ALF software. (Id. ¶ 42). ALF is known by the United States Navy (“Navy,” “Government,” or “Defendant”) and “throughout the industry to refer to Plaintiff’s products.” (Id. ¶ 10). Plaintiff alleges that the Navy “ha[s] a continuing interest” in Plaintiff’s ALF products. (Id.). As an example of this

interest, the Navy “even wrote ALF into its Core Avionics Master Plan 2020 (‘CAMP’).” (Id.). Plaintiff alleges that “[t]he inclusion of Plaintiff’s ALF in the [Navy’s] CAMP 2020 as the primary software framework solution and the fact that money was obligated demonstrated a long-term intent for the [Navy] to use Plaintiff’s products.” (Id. ¶ 12). J.F. Taylor, Inc. (“JFTI”) had a contract with the Navy “to design, develop, build, and test prototype computers for the NAVAIR 2 PMA-209 Air Combat Electronics Program Office (‘PMA-209’) Mission Computer Adjunct Processor (‘MCAP’) Program.” (Id. ¶ 18). In April 2022, “[c]onsistent with [its] interest in Plaintiff’s

Adaptive Layer Framework products, the Government began negotiating directly with JET regarding the use of ALF in the MCAP program, along with [JFTI].” (Id. ¶ 13). In an August 1, 2022, email, Scott Jaster of JET told Matt Campbell of JFTI that the Navy was “expecting product delivery [of the Baseline ATF software] and additional training and interaction, which is fine. However, this [quoted price] is a product purchase only.” (Id. ¶ 17). The Navy “asked JFTI to issue a purchase order to JET for JET’s proprietary Baseline ALF software products and documentation.” (Id. ¶ 18). On August 5, 2022, JFTI issued to JET the Request for Quote, (Id. ¶ 19), which instructed that “[t]he Government requests physical delivery of software and documentation via CD or via DoD SAFE,” (Id. ¶ 20 (quoting ECF No. 1-12)). JET responded with a quote, which JFTI accepted. (Id. ¶¶

21–22). JFTI then issue the purchase order, which included clauses summarizing the Government’s rights in the software and documentation, (Id. ¶¶ 23–26), and “required delivery of the software and documentation on or before September 11, 2022,” (Id. ¶ 27).

3 Plaintiff alleges that the Government “was sufficiently aware of JET Systems’ interest in protecting its proprietary intellectual property from unauthorized copying and distribution,

especially by JFTI, that [it] accepted delivery of ALF software directly from JET, instead of from the Prime contractor JFTI.” (Id. ¶ 29; see also id. ¶¶ 31–32). Around September 9, 2022, “JET delivered a CD containing a copy of its Baseline ALF source code and documentation directly to the Government.” (Id. ¶ 33). After notifying JET that certain items were not included in the original order, Mr. Campbell “relay[ed] to JET a request from the Government to amend [the purchase order] to include delivery of products and services not [originally] included . . . in exchange for a ‘50% payment for what [was] delivered so far.’” (Id. ¶ 35). Plaintiff alleges that because it had already met its obligations under the purchase order fully, it “did not accept the coercive offer from JFTI and the Government.” (Id.).

Plaintiff alleges that as a result, on November 20, 2022, the Government “sent a Letter of Concern to JFTI falsely claiming that the delivered software was incomplete and requesting a response by close of business on November 18, 2022, as to how JFTI intended to remedy the content of the deliverable.” (Id. ¶ 38). Given the Letter of Concern, JFTI deemed JET to be in breach, which JET denied. (Id. ¶¶ 39–40). On December 9, 2022, JFTI informed JET 4 that the purchase order was “terminated for cause.” (Id. ¶ 40). JFTI and the Government did not make any payments to JET pursuant to the purchase order. (Id. ¶ 41). JET alleges that the purchase order was terminated wrongfully. (Id.). JET further alleges that

as of December 9, 2022, any rights the Government may have had in the software and documentation terminated along with the purchase order. (See id. ¶ 26). Sometime before February 27, 2023, the Government delivered the CD containing the ALF software to JFTI, and JFTI then returned the CD to Plaintiff around February 27, 2023. (Id. ¶ 43, 44). Plaintiff alleges upon information and belief that “JFTI and the Government made unauthorized copies” of Plaintiff’s copyrighted ALF software before returning the CD to JET. (Id. ¶ 43). In support, Plaintiff points to a December 5, 2022, conference call, where it alleges that “JFTI personnel admitted that they evaluated

the ALF software that JET had delivered not to JFTI, but to the Government.” (Id. ¶ 46). Furthermore, Plaintiff alleges upon information and belief that “JFTI copied ALF software at the [Navy’s] direction” pursuant to language in JFTI’s Prime contract that JFTI “shall integrate ALF into the MCAP software environment.” (Id. ¶ 47). Finally, Plaintiff alleges that the Government “made the [ALF] software and its documentation available to other

5 parties,” as evidenced by a contract award “to a contractor having ‘[d]emonstrated experience with [ALF].’” (Id. ¶ 48). B. Procedural Background

On April 11, 2025, Plaintiff filed a complaint against Defendant, asserting a single count of conversion under the Federal Tort Claims Act (“FTCA”).2 (ECF No. 1). Defendant moved to dismiss the complaint for failure to state a claim on August 8, 2025. (ECF No. 11). Plaintiff then filed an amended complaint on August 22, 2025. (ECF No. 12). Defendant moved to dismiss the amended complaint on September 5, 2025, (ECF No. 13), and several days later, the court denied Defendant’s first motion to dismiss as moot, (ECF No. 15). On September 18, 2025, Plaintiff filed its opposition to Defendant’s motion to dismiss. (ECF No. 16). Defendant filed its reply on September 30, 2025. (ECF No. 17).

2 There are three additional proceedings related to this case, one in this court and two in the United States Court of Federal Claims. In the other proceeding in this court, Plaintiff sued JFTI for copyright infringement, misappropriation of trade secrets, conversion, and breach of contract. JET Systems, LLC v. J.F. Taylor, Inc., No. 24-cv-1628.

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

Related

Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Durst v. Durst
169 A.2d 755 (Court of Appeals of Maryland, 1961)
Diamond v. T. Rowe Price Associates, Inc.
852 F. Supp. 372 (D. Maryland, 1994)
Zachair, Ltd. v. Driggs
762 A.2d 991 (Court of Special Appeals of Maryland, 2000)
Yost v. Early
589 A.2d 1291 (Court of Special Appeals of Maryland, 1991)
Postelle v. McWhite
694 A.2d 529 (Court of Special Appeals of Maryland, 1997)
Allied Investment Corp. v. Jasen
731 A.2d 957 (Court of Appeals of Maryland, 1999)
Lawson v. Commonwealth Land Title Insurance
518 A.2d 174 (Court of Special Appeals of Maryland, 1987)
K & K Management, Inc. v. Chul Woo Lee
557 A.2d 965 (Court of Appeals of Maryland, 1989)
SecureInfo Corp. v. Telos Corp.
387 F. Supp. 2d 593 (E.D. Virginia, 2005)
Thomas v. Artino
723 F. Supp. 2d 822 (D. Maryland, 2010)
OpenRisk, LLC v. MicroStrategy Services Corp.
876 F.3d 518 (Fourth Circuit, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
JET SYSTEMS, LLC v. UNITED STATES OF AMERICA, Counsel Stack Legal Research, https://law.counselstack.com/opinion/jet-systems-llc-v-united-states-of-america-mdd-2025.