Visible residue on equipment labelled 'clean.' API contamination persisting 20 months after last use. Cleaning validation studies that never sampled the hardest-to-clean surfaces. The Fareva 483 exposes the gap between validation on paper and validation in practice.
On September 16, 2025, FDA investigators at Fareva Amboise’s manufacturing facility in Poce Sur Cisse, France issued a 483 observation that cut to the core of cleaning validation: “Equipment and utensils are not cleaned, maintained and sanitized at appropriate intervals to prevent contamination.”
The details were worse than the headline. Non-dedicated equipment used for US market products had visible residue on surfaces that had been cleaned and labelled as ready for use. On September 10, 2025, investigators found residues on the gasket and inside surfaces around the product drum of Equipment Id 005. Analytical testing confirmed API contamination from a product last manufactured on that equipment in January 2024 — yet the equipment had been used for multiple subsequent batches, including batches destined for the US market. The cleaning validation studies for this equipment had never identified these areas as hardest-to-clean. No sampling points existed around the drum.
That wasn’t all. Filling and capping equipment showed apparent corrosion, fraying, and gouges — physical damage that compromises both cleanability and product integrity. Particles had been found in two batches, but the investigation never evaluated the equipment as a potential contamination source. Preventative maintenance records showed maintenance had been performed only just before the inspection. The picture was comprehensive: a cleaning validation programme that existed on paper but failed to reflect what was actually happening on equipment surfaces.
The equipment was labelled “clean.” The analytical data said otherwise. When your cleaning validation studies don’t sample the places where contamination actually accumulates, the validation certificate is fiction.
21 CFR 211.67 requires that equipment and utensils be cleaned, maintained, and sanitised at appropriate intervals to prevent contamination that would alter the safety, identity, strength, quality, or purity of the drug product. 21 CFR 211.65 requires that equipment be constructed so that surfaces in contact with drug products are not reactive, additive, or absorptive — and that equipment be maintained to prevent malfunctions or contamination.
The Fareva finding exposed failures against both regulations simultaneously. Equipment Id 005 carried analytically confirmed API residue from a product last manufactured in January 2024 — twenty months prior. In those twenty months, the equipment had been cleaned, released, and used for other production batches, including US market products. Each of those cleaning cycles had been executed against a validated protocol. Each had passed. And each had missed the contamination sitting on the gasket and inside surfaces around the product drum, because the validation study had never identified those locations as sampling points.
The equipment condition issues compounded the cleaning failure. Corroded, frayed, and gouged surfaces on filling and capping equipment create harbourage sites — micro-environments where residues accumulate and resist cleaning. Two batches had shown particle contamination, but the resulting investigation never evaluated the damaged equipment as a source. The maintenance performed immediately before the inspection suggested awareness of the problem, but not a system for preventing it.
20 months
API contamination from January 2024 was analytically confirmed on 'clean' equipment in September 2025 — surviving every cleaning cycle in between because the validation never sampled the affected surfaces.
0
The cleaning validation study for Equipment Id 005 included no sampling points around the product drum — the exact location where FDA investigators found visible residue and confirmed API contamination.
47%
FDA Tracker analysis shows that equipment cleaning and maintenance deficiencies account for a significant proportion of manufacturing-related 483 observations, making it one of the most persistent compliance gaps in the industry.
The root cause isn’t lazy cleaning operators or inadequate detergents. It’s a validation architecture that treats worst-case identification as a one-time paper exercise, validation studies as static documents, and equipment condition as someone else’s problem. When those assumptions meet real manufacturing — with complex geometries, degrading surfaces, and products that leave tenacious residues — the validation programme produces certificates while contamination persists.
Most cleaning validation programmes select sampling points based on accessibility and historical practice, not on rigorous analysis of equipment geometry, flow patterns, and residue behaviour. The Fareva study never identified the gasket and drum interior as hardest-to-clean areas — precisely the locations where contamination accumulated. When worst-case selection is a desk exercise disconnected from actual equipment behaviour, the validation misses the places that matter most.
A cleaning validation study is a snapshot. Equipment degrades. New products are introduced. Cleaning agents change efficacy over time. But the validation protocol remains frozen at the point of approval. Fareva's equipment had been validated, but the validation reflected conditions that no longer existed — corroded surfaces, worn gaskets, and twenty months of additional production cycles that the original study never anticipated.
Validation establishes that a process can work. Ongoing verification confirms that it still does. Most facilities lack systematic ongoing verification of cleaning outcomes — visual inspection is subjective, and routine swab testing often targets the same convenient locations as the original validation. The contamination on Equipment Id 005 survived because no verification programme was checking the surfaces where it actually lived.
Corroded, frayed, and gouged surfaces are not just equipment maintenance issues — they are cleaning validation issues. Damaged surfaces create harbourage sites that resist standard cleaning procedures. Yet in most facilities, equipment maintenance and cleaning validation exist as separate programmes with separate owners. Fareva's particle contamination investigation never evaluated the equipment as a source, because the system didn't connect these domains.
The question isn’t whether your cleaning procedures are adequate. It’s whether your validation programme can identify where contamination actually accumulates — and whether it updates when equipment and processes change.
In each comparison below, the issue is the same: static, disconnected processes create gaps that persist until an inspector or a contamination event exposes them. Systematic approaches eliminate these gaps by design, not by additional manual effort.
Worst-case products and sampling points are selected based on solubility data and analyst judgment, typically during a single desktop assessment. Equipment geometry, flow dead-legs, gasket interfaces, and residue adhesion characteristics are rarely evaluated systematically. The result: validation studies that sample accessible surfaces while contamination accumulates in unsampled areas — exactly the Fareva pattern.
Result: Sampling misses actual contamination sites
HBEL-driven worst-case matrix generation evaluates every product-equipment combination against toxicological limits, cleaning difficulty scores, and equipment-specific geometry data. Sampling points are mapped to hardest-to-clean areas identified through equipment design analysis and cleaning mechanism modelling — not just the surfaces easiest to reach with a swab.
Result: Validation targets where contamination actually occurs
After initial validation, cleaning effectiveness is assumed until the next revalidation cycle — often years later. Routine visual inspection is subjective and inconsistent. Any monitoring swabs target the same locations as the original study, leaving the same blind spots. Equipment Id 005's contamination persisted for twenty months because nothing in the programme was designed to detect it.
Result: Contamination persists between revalidation cycles
Continuous monitoring programmes track cleaning outcomes against validated limits, with trend analysis that detects drift before it becomes a failure. Changes in product mix, equipment condition, or cleaning parameters automatically trigger reassessment of worst-case assumptions. The system adapts because it's designed to — not because someone remembered to update a spreadsheet.
Result: Drift detected and addressed proactively
Equipment maintenance and cleaning validation are managed as separate programmes by separate teams. Corroded or damaged surfaces are a maintenance issue until they cause a contamination event — at which point they become everyone's issue. Fareva's damaged filling and capping equipment was a known condition that never triggered a cleaning validation reassessment, and particle investigations never traced back to equipment condition.
Result: Equipment damage creates hidden cleaning risk
Equipment condition data feeds directly into cleaning validation risk assessments. Surface degradation, maintenance events, and equipment age are tracked as variables that affect cleaning effectiveness. When equipment condition changes, the system flags affected cleaning validations for reassessment — connecting the maintenance and validation domains that should never have been separated.
Result: Equipment changes trigger validation updates
The capabilities below directly address the gaps exposed in the Fareva observation — not by adding more manual assessments, but by building scientific rigour into the cleaning validation lifecycle itself.
Automated calculation of health-based exposure limits across every product-equipment combination, with worst-case matrix generation that accounts for toxicological data, cleaning difficulty, equipment geometry, and residue characteristics. Sampling point selection is driven by scientific analysis of where contamination actually persists — not by where swabs are easiest to take.
Cleaning validation treated as a living programme, not a static document. Changes in product portfolio, equipment condition, or cleaning parameters automatically trigger reassessment of affected validations. Trend analysis on cleaning outcomes identifies drift before it crosses limits — replacing the assumption that a twenty-month-old validation still reflects reality.
Equipment condition, maintenance history, and surface integrity data are linked directly to cleaning validation risk assessments. Corrosion, wear, or damage events trigger automatic flags on affected cleaning validations. Investigations for particle contamination or cleaning failures include equipment condition as a standard evaluation parameter — closing the gap that left Fareva's damaged equipment unconnected to its particle findings.
7+
CLEEN deployed across 7+ facilities at Zydus, delivering standardised HBEL-driven cleaning validation with automated worst-case matrix generation across the entire manufacturing network.
80%
Reduction in cleaning validation cycle time at Zydus — from weeks of manual worst-case calculations and protocol generation to automated, scientifically rigorous validation programmes.
100%
Complete elimination of manual calculation errors in HBEL computations and worst-case matrix generation — removing the human error factor from the most scientifically critical step in cleaning validation.
The goal isn’t more validation protocols. It’s a fundamentally different relationship between cleaning validation, equipment management, and ongoing verification — where gaps like the Fareva finding are structurally impossible, not just unlikely.
Map your current cleaning validation sampling points against actual equipment geometry — gaskets, dead-legs, drum interiors, transfer lines, and every surface that is difficult to access, inspect, or clean. Compare your worst-case product matrix against current HBEL calculations, not just solubility rankings. Most facilities discover that their 'worst case' was selected for convenience, not scientific rigour, and that entire categories of hard-to-clean surfaces have never been sampled.
Establish a systematic link between equipment maintenance records and cleaning validation status. Any change in equipment surface condition — corrosion, wear, damage, gasket replacement — should trigger a reassessment of the affected cleaning validation. Build investigation protocols that include equipment condition as a standard evaluation parameter for particle events and cleaning failures. The Fareva pattern — particles found but equipment never evaluated — should be structurally impossible.
Deploy a continuous monitoring programme that tracks cleaning outcomes against validated limits over time, with statistical trend analysis that detects drift before limits are breached. Verification sampling must include the hardest-to-clean locations identified in Phase 1, not just the original validation sampling points. Within two to three revalidation cycles, the data will show whether your cleaning programme controls contamination or merely documents the assumption that it does.
Fareva Amboise’s cleaning validation studies passed every time. The contamination persisted every time. When validation doesn’t sample the surfaces where residue actually accumulates, passing the study and controlling contamination are two entirely different things.
The Fareva Amboise 483 is not a story about a cleaning failure. It is a story about a validation failure — a programme that certified equipment as clean without ever checking the surfaces where contamination persisted. The API residue survived twenty months and multiple cleaning cycles not because the cleaning was inadequate, but because the validation never looked where the contamination lived.
This pattern — worst-case assumptions that aren’t worst-case, validation studies that don’t adapt, equipment damage that nobody connects to cleaning risk — is not unique to Fareva. For teams rebuilding from this failure mode, how to structure a cleaning validation protocol that ties worst-case selection to actual equipment geometry is the place to start. It is the structural outcome of cleaning validation programmes built on static documents, manual calculations, and the assumption that initial validation remains valid indefinitely. Every facility running that model carries the same exposure.
Modern cleaning validation eliminates this risk by treating validation as a living system: HBEL-driven worst-case analysis that targets actual hard-to-clean surfaces, equipment condition data that feeds directly into validation risk assessments, and ongoing verification that confirms cleaning effectiveness rather than assuming it. The validation programme becomes a contamination control tool, not a regulatory filing. This is the architecture behind how Zydus automated worst-case product selection across 7+ facilities with CLEEN, cutting cleaning validation cycle time by 80% while eliminating manual HBEL calculation errors. And when the inspector arrives, the evidence of cleaning effectiveness isn’t a certificate from three years ago — it is current, comprehensive, and grounded in the surfaces that actually matter. Purpose-built cleaning validation software is what makes this living-system model practical across a multi-product site — automating worst-case selection, residue-limit calculations, and ongoing verification so the validated state stays current.