Contents
In the Williams International settlement, the engine supplier agreed to pay $2.1 million to resolve False Claims Act allegations that it manufactured and delivered nonconforming engines for target drones sold to the Navy. The case connected an engine assembled at a supplier’s plant to the performance of the aircraft the government bought. If you know what an engine was required to do and what its quality records actually showed, that connection matters even when another company’s name appears on the Navy contract.
The Justice Department announced the Williams settlement on August 22, 2003. It identified Williams International Co., LLC as a Michigan-based company and placed assembly of the engines at its Ogden, Utah facility.
The target drones gave the Navy a realistic aerial target for gunnery and missile training, simulating enemy threats. They could launch from a ship, from shore or from military aircraft.
The government alleged that Williams manufactured and delivered engines that did not meet requirements and caused those engines, inside target drones, to be sold to the Navy. That is the supplier side of nonconforming defense products: a component made at one plant becomes part of the equipment delivered under another company’s contract. If you built the engine, the Navy was still the customer at the end of the chain.
Northrop Grumman, the Navy’s prime target-drone contractor, separately agreed to a $20 million settlement to resolve allegations about its delivery of nonconforming targets. The Williams announcement said Northrop’s settlement provided credit for the amount paid by Williams. Under those terms, money paid by the supplier would count toward the prime’s resolution.
Williams assembled the engines and Northrop supplied the target drones. The supplier’s work reached the Navy through the prime contractor, putting the engine’s quality inside Northrop’s promise about the finished aircraft.
The Northrop settlement announcement concerned eight Navy contracts from the late 1980s and early 1990s. The government alleged defective parts, inadequate quality assurance and failures to meet reliability requirements. Those allegations explain why the engine supplier belonged in the same story: the Navy’s purchase depended on the quality of components inside the drone, as well as the prime’s work on the finished product.
The purchase order connects the supplier to the prime. The delivered component connects the supplier’s work to the aircraft. We follow those connections to understand how a quality problem reached the government’s purchase and what each company represented along the way.
The Justice Department said its investigation confirmed that defective engines caused at least 65 target drones to experience operational failures at Navy firing ranges from 1993 through 1998. The consequence reached the equipment in use, where the Navy was conducting weapons training. We see the absurdity in buying a target to test weapons and having its own engine defeat it.
The Naval Criminal Investigative Service’s office in Upland, California, and the Defense Criminal Investigative Service’s office in Ogden, Utah, jointly investigated Williams. The Justice Department said their investigation connected the engines to operational failures. The civil settlement resolved allegations about manufacturing and delivering nonconforming engines.
For a concern about nonconforming engines, the useful evidence connects the requirement, the engine’s identity and condition, what the customer was told, and the government payment. We examine the original quality records alongside the delivery and payment records to understand that connection. An engineer’s knowledge of what a test measured and a purchasing employee’s knowledge of what was ordered illuminate different parts of the same transaction.
An engine’s test result belongs with the particular engine delivered, not just a product description on an order. Product identification and traceability connect the inspected component to the finished aircraft. We work through those records with the insider who understands them, including who knew about a discrepancy and what they told the customer afterward. That keeps the inquiry tied to the government’s money and the product it was promised.
Third Way’s 2026 memo Pentagon Procurement: Big Spending, Bigger Vulnerabilities identifies defective parts among the consequences of procurement failures. It makes the case for looking beyond the accounts:
A clean audit is a worthwhile goal, but the government must also do more to deter fraud in the defense industry.
Pentagon Procurement: Big Spending, Bigger Vulnerabilities, Third Way, 2026
That distinction matters to an engine inspector whose knowledge concerns the product behind the bill. We connect what the inspection showed to what the buyer was told, so the case carries the technical evidence as well as the payment trail.
Bradken’s naval-steel case shows how a supplier’s test results can reach the government’s bill through another contractor. Under its deferred prosecution agreement in the criminal case, Bradken admitted the government’s allegations that falsified tests concealed steel that did not meet Navy strength and toughness specifications. The civil allegations concerned shipbuilders billing the Navy as though the steel complied.
The useful parallel is the path from a supplier’s quality information to the government’s purchase. For an engine engineer or a steel-testing employee, the original result describes something the final invoice cannot: whether the component met the requirement the buyer relied on. We examine that gap with the person who understands the product and what the customer was told.
A Northrop employee started the related case, a qui tam case under the False Claims Act. After a Naval Criminal Investigative Service investigation, the government joined the case. An employee’s knowledge inside the prime contractor helped bring the quality of the Navy’s target drones into a government case.
A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers. If your knowledge sits inside an engine supplier, we connect it to the finished equipment and the government’s purchase. The technical detail you understand explains why a delivery record and the product behind it tell different stories.
If you saw an engine approved despite quality records showing it fell short, speak to one of our Whistleblower Experts about how that engine was approved. We build your strongest defense contractor whistleblower case around what happened at the supplier and how it reached the government’s bill, bringing in defense contractor whistleblower lawyers who understand manufacturing and product-quality disputes. You bring the knowledge of the engine; we bring the experience to pursue the case and stay beside you throughout it.