Contents
The Third Circuit vacated a Navy engineer’s procurement integrity conviction on January 14, 2026 because the guilty plea failed to connect an old bid’s information to a pending submarine propeller machine procurement. The court’s opinion explained the gap: calling the machines virtually identical did not establish that the bids contained the same information in substance.
The criminal appeal concerned a mechanical engineer who led Navy purchases at the Naval Foundry and Propeller Center in Philadelphia. The center designs, manufactures and repairs submarine propellers, and the engineer led projects supporting Columbia Class and Virginia Class submarines. The machines at issue were vertical turning centers, large specialized equipment used to manufacture those propellers.
In the opinion’s account, the engineer became project lead for the SU22 procurement in 2017. Four companies bid, submitting confidential cost, pricing and manufacturing information. The engineer favored the bidder the court calls Company 1 and used its proposal in drafting the technical specifications. The other three bids failed those specifications, and Company 1 won the contract.
That is a consequential place for an engineer to sit: the technical description helps determine which suppliers can compete for the government’s order. Here, the criminal opinion connects the favored company’s proposal to the specifications against which the competing bids were judged. The losing bidders were competing on requirements shaped with their rival’s proposal in hand.
In 2019, the Navy began another purchase, SU25, with the same engineer as project lead. The engineer asked for a sole-source contract for Company 1, which would have given it the work without competing bids. The Navy instead accepted other bids while indicating that it tentatively planned to select Company 1 again. Company 2 returned with a technical and pricing proposal for the new machine.
According to the criminal opinion, the engineer sent Company 2’s confidential SU22 bid information to an employee at Company 1 through WhatsApp during the SU25 competition. The attached proposal came from the earlier purchase. The opinion also recounts the engineer’s threat to ruin Company 2 if it interfered with the award. The accompanying message made the engineer’s preference unmistakable:
[l]oyalty is important to me. [Company 1] has mine. And Company 2 pissed me off with this situation.
Third Circuit opinion, January 14, 2026, quoting the project lead’s WhatsApp message
The plea memorandum, reproduced in the opinion, described approximately 31 pages of confidential information. The documents carried source-selection, official-use-only and proprietary markings, and contained cost and pricing data, manufacturing processes and techniques, and bid prices. These were a rival supplier’s commercial details, sent by the government employee leading the purchase.
Company 1 submitted its SU25 bid after receiving the information and won the contract. The opinion says Company 2’s price was higher, so the Navy dropped its bid from consideration. The Justice Department’s earlier account of the criminal case puts the April 2020 award to Company 1 at $15,254,608.
The Defense Criminal Investigative Service and the Naval Criminal Investigative Service’s Economic Crimes Field Office investigated the engineer’s conduct. The later court ruling turned on what the plea actually established about the disclosed information and the pending purchase.
Under the court’s reading of the Procurement Integrity Act, the old bid information had to be the same in substance as information submitted for the new purchase. The wording could differ, but the plea needed facts connecting the contents of the two bids.
The majority’s reasoning would be familiar to someone who prepares technical bids. Different suppliers can propose different ways to produce the same product. A supplier that loses one competition may change its engineering approach or price before bidding again, even when the buyer wants similar equipment.
The two losing bids illustrated the problem. Company 2’s SU22 proposal had been rejected as technically unacceptable, while its SU25 proposal was rejected as too expensive. The court said that difference suggested the technical components had changed. The prices gave it another reason to question the comparison:
In addition, the price of the awarded SU25 contract was over forty percent greater than that of the SU22 contract, suggesting that Company 2’s SU22 cost and pricing data were outdated, if not irrelevant, by the time of the SU25 procurement.
We see a government buyer treating a public purchase as a promise to a favored supplier. The loyalty pledge came with a rival’s confidential proposal attached, yet the conviction fell because the plea never connected those documents to the new bid. The message exposed the preference; it could not supply the missing comparison.
The court also kept the alleged competitive advantage separate from the information’s connection to the pending purchase. Prosecutors argued that the engineer would have disclosed the old proposal only if it could help Company 1. The majority said that inference lacked factual support and could not supply the missing comparison. A claim that the recipient gained an advantage did not answer what information about the pending procurement had been disclosed.
With old bid information, we work with you to connect the evidence to the purchase it could affect. In this case, that meant understanding the cost, pricing and technical information in the earlier proposal and its relationship to the later submission. A machine description alone could not explain those connections.
An engineer may understand whether a proposed manufacturing process changed between bids. Someone in pricing may recognize which costs were carried forward and which were revised. A person who saw the message or attachment may know when the information reached the competing bidder. Those are different parts of the same comparison, and we work through them with the person who knows the business.
The distinction matters when we assess a defense contractor whistleblower case. We connect what you saw to the supplier’s proposal, the government decision and the money at stake. The Navy opinion shows how much can turn on a connection that a broad account of favoritism leaves unexplained.
Boeing agreed to a $565 million civil settlement covering contracting decisions and launch competitions, including allegations involving a competitor’s confidential material. In its civil settlement announcement, the government alleged that Boeing obtained Lockheed Martin competition documents, gained an unfair advantage in the Evolved Expendable Launch Vehicle competition and used that position to obtain NASA sole-source awards. That account tied the alleged advantage to identified purchasing decisions.
The Navy engineer’s case was a criminal prosecution. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. Our whistleblower experts assess how the information you saw connects to government business and whether it can support a civil case.
If you saw a rival’s confidential proposal reach the bidding team, speak to one of our Whistleblower Experts about the bid information you saw. We build the case with you around the details an outsider would miss and bring in defense procurement whistleblower lawyers who understand how bids become government contracts. We stay beside you as that inside knowledge becomes a case for recovering government money.