Scan-Tech Security, L.P. v. United States

46 Fed. Cl. 326, 2000 U.S. Claims LEXIS 44, 2000 WL 291202
CourtUnited States Court of Federal Claims
DecidedMarch 20, 2000
DocketNo. 97-601C
StatusPublished
Cited by29 cases

This text of 46 Fed. Cl. 326 (Scan-Tech Security, L.P. v. United States) is published on Counsel Stack Legal Research, covering United States Court of Federal Claims primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Scan-Tech Security, L.P. v. United States, 46 Fed. Cl. 326, 2000 U.S. Claims LEXIS 44, 2000 WL 291202 (uscfc 2000).

Opinion

OPINION

BUSH, Judge.

This matter is before the court on the defendant’s motion to dismiss plaintiffs contract-based counts for lack of subject matter jurisdiction and plaintiffs takings count for failure to state a claim upon which relief can be granted. The issues to be decided are (1) whether plaintiff properly submitted a claim to the contracting officer for final decision in compliance with the requirements of the Contract Disputes Act (CDA), 41 U.S.C. §§ 601-13 (1994) and (2) whether defendant has properly demonstrated that the parties’ contractual relationship precludes plaintiffs takings claim from proceeding. Because plaintiff has completely failed to certify its claim in accordance with the CDA, the court dismisses plaintiffs contract-based counts. However, because defendant has failed to demonstrate that the parties’ contract prevents plaintiff from asserting its takings claim, the court denies defendant’s motion to dismiss as it relates to plaintiffs takings count.

FACTS

The Federal Aviation Administration (FAA) and Scan-Tech Security L.P. (Scan-Tech) entered into Contract No. DTFA0389-C-00044 on September 26, 1989. This cost-reimbursement contract required Scan-Tech to perform research as well as full-scale engineering and development of a non-nuclear, non-vapor detection system to be used to inspect airline luggage in airline terminals. The contract contemplated two work phases. Phase II required the construction of an x-ray scattering explosive detection device prototype. During performance, the parties entered into various formal contract modifications increasing the funding of these phases and adjusting their completion dates.

[329]*329On July 1, 1993, the FAA ordered Scan-Tech to stop work so that Scan-Tech could perform a demonstration of the prototype. Leading up to this, Scan-Tech had met with the FAA on several occasions in early 1993 to discuss the continuation of the project and the further funding of it. As a result of these meetings, Scan-Tech submitted proposals, allegedly at the FAA’s request, and in return received encouragement to proceed with work. On August 20, 1993, the parties entered modification number 12, which authorized the demonstration of the prototype and provided $150,000 in funding for the demonstration. Modification 13 definitized the $150,000 funding amount. Scan-Tech performed the “as is” demonstration of the prototype in September 1993, and at some unspecified point, delivered the prototype to the FAA at its own expense. On January 27, 1994, the FAA default terminated the contract.

Beginning in 1993, Scan-Tech submitted invoices to the FAA seeking reimbursement for cost overruns and expenses incurred in performing the contract. According to Hasbrouck Miller, the Vice-President of Control Screening Corporation (which was a general partner in the Scan-Tech Security limited partnership), Scan-Tech filed a “claim” with the Contracting Officer on or about June 21, 1994. Based on Scan-Tech’s submissions to this court, this “claim” included Standard Form 1411 (SF 1411), the Contract Pricing Proposal Cover Sheet. SF 1411 listed a cost overrun on Phase II of the project as the type of contract action, and a Scan-Tech representative signed this standard form.

More than two years later, on September 17, 1996, Mr. Miller sent a letter to the FAA’s contracting officer (CO), listing nine outstanding invoices. The invoice dates ranged from May 28, 1993 to September 16, 1996, and totaled $808,043, nearly the same amount of relief requested in Scan-Tech’s present complaint. The subject of the September 17,1996 letter was “Outstanding Billings for DTFA03-89-C-00044.” In it, Mr. Miller stated that “[fjurther to ongoing correspondence and various conversations, please find the enclosed invoices and backup documentation for what I believe to be all the outstanding invoices for payments due to Scan-Tech for work performed for DTFA0389-C-00044.” Mr. Miller noted that he had “spent considerable time accumulating and checking the various invoices” and related his belief “that this is as complete an assembly as possible.” In conclusion, Mr. Miller expressed that Scan-Tech was “anxious to put this matter to rest” and offered to “follow up with you in the next couple of days to discuss how we need to proceed.”

By letter dated November 8, 1996, the FAA’s CO, Michael King, responded to Scan-Tech’s submission. In his responding letter, Mr. King authorized payment in the amount of $52,201.57 for the work that modification 12 ordered; much less than the $808,043 that Scan-Tech had requested. Def.’s App. 5. Mr. King reasoned that the “ceiling” price established by Modification 12 was $150,000 and since the FAA formerly had already approved payment in the amount of 97,798.43, Sean-Tech was only entitled to the remaining $52,201.57. In conclusion, Mr. King requested that Scan-Tech submit an invoice for $52,201.57, and identify that invoice as “final.”

On August 28,1997, Scan-Tech filed suit in this court, asserting five counts. In counts I to IV, Scan-Tech alleges that the Government failed to pay it for extra work the Government requested and approved in 1993. In addition, Sean-Tech asserts that the Government breached the contract by accepting work, including that associated with the delivery of the prototype, without paying Scan-Tech. In count V, Scan-Tech asserts that the acceptance of the prototype without payment constitutes a taking without just compensation.

DISCUSSION

I. Motion to Dismiss for Lack of Jurisdiction — RCFC 12(b)(1)

The Government has moved to dismiss counts I to IV for lack of subject matter jurisdiction pursuant to RCFC 12(b)(1). The focus of the Government’s argument is that Scan-Tech failed to certify its written submission to the CO. However, because compliance with the CDA affects this court’s [330]*330jurisdiction, the court will analyze Scan-Tech’s submissions to insure that they meet all of the CDA’s requirements, not simply the certification provision.

Jurisdiction may be challenged by the parties or by the court on its own motion at any time, and if jurisdiction is found to be lacking, this court must dismiss the action. RCFC 12(h)(3). When considering a motion to dismiss, this court must assume all undisputed factual allegations to be true and draw all reasonable inferences in favor of the pleader. Scheuer v. Rhodes, 416 U.S. 232, 236-37, 94 S.Ct. 1683, 40 L.Ed.2d 90 (1974); Reynolds v. Army & Air Force Exch. Serv., 846 F.2d 746, 747 (Fed.Cir.1988). When a party challenges jurisdiction, the non-moving party bears the burden of proving disputed jurisdictional facts by a preponderance of the evidence. Reynolds, 846 F.2d at 748. Although a decision on a motion to dismiss pursuant to RCFC 12(b)(1) is not a judgment on the merits, Mark Smith Constr. Co. v. United States, 10 Cl.Ct. 540, 541 (1986), the court may make any factual findings necessary to adjudicate this motion, Reynolds, 846 F.2d at 747, including findings on matters not raised in the pleadings. Indium Corp. of America, Inc. v. Semi-Alloys, Inc., 781 F.2d 879, 884 (Fed.Cir.1985), cert. denied, 479 U.S. 820,107 S.Ct.

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

Related

Baha v. United States
Federal Claims, 2018
Magnus Pacific Corporation v. United States
133 Fed. Cl. 640 (Federal Claims, 2017)
Estes Express Lines v. United States
123 Fed. Cl. 538 (Federal Claims, 2015)
Csx Transportation, Inc. v. United States
123 Fed. Cl. 244 (Federal Claims, 2015)
Williams v. United States
118 Fed. Cl. 533 (Federal Claims, 2014)
Delaware Cornerstone Builders, Inc. v. United States
117 Fed. Cl. 539 (Federal Claims, 2014)
Kellogg Brown & Root Services, Inc. v. United States
115 Fed. Cl. 168 (Federal Claims, 2014)
PARSONS GLOBAL EX REL. ODELL INTERN. v. McHugh
677 F.3d 1166 (Federal Circuit, 2012)
NCLN20, Inc. v. United States
82 Fed. Cl. 103 (Federal Claims, 2008)
County of Ventura v. Channel Islands Marina, Inc.
71 Cal. Rptr. 3d 762 (California Court of Appeal, 2008)
Roxco, Ltd. v. United States
77 Fed. Cl. 138 (Federal Claims, 2007)
Omaha Public Power District v. United States
69 Fed. Cl. 237 (Federal Claims, 2005)
Franconia Associates v. United States
61 Fed. Cl. 718 (Federal Claims, 2004)
Engineered Demolition, Inc. v. United States
60 Fed. Cl. 822 (Federal Claims, 2004)
Detroit Edison Co. v. United States
56 Fed. Cl. 299 (Federal Claims, 2003)
Pi Electronics Corp. v. United States
55 Fed. Cl. 279 (Federal Claims, 2003)

Cite This Page — Counsel Stack

Bluebook (online)
46 Fed. Cl. 326, 2000 U.S. Claims LEXIS 44, 2000 WL 291202, Counsel Stack Legal Research, https://law.counselstack.com/opinion/scan-tech-security-lp-v-united-states-uscfc-2000.