Judd Wire Inc., a wire and cable manufacturer in Turners Falls, Massachusetts, has agreed to pay $1,014,000 to resolve False Claims Act allegations that it failed to perform tests required by 29 separate specifications covering wire and cable products used by the U.S. Navy, the Justice Department announced.
Background
Judd Wire supplies wire and cable for defense applications, including products built to military specifications the Navy relies on to certify that shipboard and aircraft wiring will hold up under heat, vibration, moisture, and the other stresses of naval service. Those specifications typically require manufacturers to run a defined battery of tests on production lots before the material ships, generating records that downstream buyers and the government use to confirm the product meets its rated performance.
According to the Justice Department, Judd Wire produced wire and cable that was used by the United States but did not perform all of the tests required under each of the 29 specifications covered by the settlement. The conduct at issue ran from September 2011 through August 30, 2021, a span of roughly a decade during which the company allegedly shipped product without completing the full testing regimen the specifications called for. Submitting invoices for goods represented as meeting contract specifications, when required testing was not actually performed, can trigger liability under the False Claims Act, the civil statute the government uses to recover money obtained through false statements on federal contracts.
Wire and cable manufacturers occupy a lower tier of the defense supply chain that rarely draws public attention, but the parts they produce are embedded throughout Navy ships and aircraft, often in locations where replacement after installation is expensive or impractical. Specifications covering this category of product typically require dielectric, tensile, flammability, and environmental testing to confirm that a given production lot performs to its rated standard over the life of the platform. When a manufacturer skips steps in that testing sequence, the government has no independent way of knowing whether the material it received meets the standard it paid for, which is why the False Claims Act treats an unsubstantiated certification of compliance as a basis for civil liability.
Key Details
Under the settlement, Judd Wire will pay the United States $1,014,000, of which $676,000 is designated as restitution. The remainder reflects damages and penalties tied to the underlying False Claims Act allegations. The settlement agreement, posted by the Justice Department, states that the resolution "is neither an admission of False Claims Act liability by Judd Wire nor a concession by the United States that its claims are not well-founded" — meaning the company did not admit wrongdoing as part of the deal.
A central factor in how the case was resolved was Judd Wire's own conduct after discovering the testing gaps. The company voluntarily disclosed the lapses to the government, cooperated with the ensuing investigation, and implemented remedial measures, including bringing its testing processes into full compliance with the applicable specifications. The Justice Department credited that self-disclosure and cooperation under its False Claims Act guidelines, found in Justice Manual §4-4.112, which sets out how much credit a company can earn by coming forward on its own rather than waiting to be caught.
The case was handled jointly by the Justice Department's Civil Division, Commercial Litigation Branch, Fraud Section, and the Navy Office of General Counsel's Acquisition Integrity Office. Navy General Counsel David W. Denton Jr. tied the resolution to the Acquisition Integrity Office's expanding partnership with the Task Force to Eliminate Fraud, a government-wide initiative the Administration launched this year, not a Navy-specific program. The settlement preserves several avenues for further action: it does not release Judd Wire or any individual from potential criminal liability, release any employee from civil liability, or affect the government's suspension and debarment authority. The civil payment closes out the False Claims Act allegations but leaves the door open for criminal, individual, or debarment measures.
What It Means for Contractors
The Judd Wire settlement is a reminder that testing and certification requirements built into military specifications are not paperwork formalities — they are conditions of payment, and failing to complete them can expose a manufacturer to False Claims Act liability even without an allegation that the product actually failed in service. Contractors that supply components under detailed technical specifications, particularly wire, cable, connectors, fasteners, and other items tested lot by lot, should treat this case as a prompt to audit whether their quality and test records actually match what the specifications require, not just what internal procedures assume is happening on the floor.
The case also illustrates how self-disclosure can shape the outcome once a testing gap surfaces. Judd Wire's decision to come forward, cooperate with investigators, and fix its testing processes before the government came looking is cited as the reason it received cooperation credit under DOJ's guidelines. Contractors that discover their own compliance gaps face a real choice: disclose promptly and negotiate from a position of cooperation, or risk an investigation that carries none of that credit. The Acquisition Integrity Office's continued partnership with the Task Force to Eliminate Fraud signals that procurement fraud enforcement in this space is an ongoing institutional priority, not a one-off case.
Finally, the decade-long span of the alleged conduct — from 2011 to 2021 — underscores how long testing gaps can persist undetected in a supply chain built on trust in a supplier's certifications. Prime contractors and government buyers relying on subcontractor test data have limited visibility into whether that data reflects tests that were actually run. Contractors on both sides of that relationship should expect continued scrutiny of testing documentation as part of routine contract administration, not just in response to a specific complaint.
For compliance officers, the practical takeaway is to reconcile test logs against the specific specification revisions cited in each contract, rather than assuming a general testing program covers every requirement a specification imposes. Specifications are updated over time, and a procedure that satisfied an earlier revision may not satisfy the version incorporated into a current order. Building that reconciliation into internal audits before an investigator does it first is the difference between a corrective action plan and a False Claims Act settlement.
