Released as Clean, Yet Residue Remained: A Simple Finding With a Bigger System Lesson

What happened

On 7 April 2026, the US Food and Drug Administration issued Warning Letter 320-26-60 (MARCS-CMS 721592) to Chemco Corporation, an over-the-counter, non-sterile topical drug manufacturer at 4920 NW 165th St., Miami Lakes, Florida (FEI 1042599). It followed an inspection conducted from 11 to 22 August 2025 by the Florida District Office and was signed out of the Center for Drug Evaluation and Research (CDER).

The Warning Letter identifies a straightforward observation among its CGMP findings. During the inspection, the investigator observed white residue in a piece of manufacturing equipment — Tank #68 — that the firm's quality unit had verified as clean according to the tank cleaning logbook. The tank had previously been used to manufacture a topical drug product containing a redacted active ingredient.

Two related failures sit underneath that single observation. First, the firm stated during the inspection that it had not conducted cleaning validation studies for its non-dedicated equipment. Because actives were manufactured on shared equipment, the firm could not demonstrate that its cleaning process was effective in preventing cross-contamination between products. Second, the letter cites the absence of written cleaning and maintenance procedures — the equipment-cleaning requirements of 21 CFR 211.67(a) and 211.67(b).

The proposed remedy was an analytical method to verify cleaning effectiveness. FDA judged that response inadequate: no evidence was provided that the cleaning methods actually removed drug product residues, cleaning and sanitising agents, and objectionable organisms, and no impact assessment was made for drug products already on the market and within expiry.

The agency's expectations were set out explicitly: a comprehensive, independent retrospective assessment of cleaning effectiveness — naming the residues, other equipment that may have been improperly cleaned, and whether cross-contaminated product may have been released — plus a CAPA plan, worst-case identification (higher-toxicity drugs, higher-potency drugs, lower-solubility drugs, drugs that are difficult to clean, swabbing locations for areas hardest to clean, and maximum hold times before cleaning), change-management steps before new equipment or products, and updated SOPs covering verification and validation of cleaning procedures.

The same letter also cites 21 CFR 211.84(d)(1)/(d)(2) for missing identity testing of components and 21 CFR 211.22 for quality unit oversight, alongside unapproved-new-drug and misbranding findings for several OTC products. Those sit outside this article's scope but frame the environment in which the cleaning failure occurred.

Why it matters

The observation is almost boring: a residue visible to the naked eye, on equipment already signed off. That is exactly why it matters.

A cleaning release decision is a claim that equipment is fit for the next product. Here the claim was made and recorded — the logbook said clean — and the physical state of the equipment contradicted it. When visual inspection misses an obvious residue, the failure is not primarily an analytical gap. It is a release-state gap: the process that decided "clean" was not capable of detecting "not clean".

That has two consequences. The historical record of release decisions becomes untrustworthy, which is precisely why FDA asked for the scope of improperly cleaned equipment and an assessment of already-distributed product. And a retroactive analytical method cannot repair a defective decision: testing the outcome does not validate the process that produced it.

What is particularly interesting

Visual inspection was the control that failed, and it was the only control. With no cleaning validation for non-dedicated equipment, there was no acceptance criterion, no worst-case basis, no swab or rinse sampling strategy and no demonstrated MACO logic. The tank logbook carried the entire cross-contamination argument on the strength of a visual check with no defined limits or lighting conditions. Visual inspection is a legitimate and often primary control — but only when qualified, bounded by acceptance criteria and supported by validated analytical evidence where risk demands it.

FDA linked cleaning to hold times. Among the worst-case elements demanded is maximum hold time before cleaning: the hold-time dimension most often left implicit. Dirty hold time is a cleaning-programme variable, not a scheduling convenience. If a tank waits, residues dry, adhere and change character — and the procedure that worked on day one may not work on day five.

The response narrowed the problem. A single analytical method was offered as the fix for a system lacking procedures, validation, criteria and impact assessment. FDA's reply reads as a checklist: retrospective scope, residue identity, affected product, CAPA with timelines, worst-case coverage, change management, SOP updates.

How such a gap can realistically develop

Rarely by a deliberate decision. Typically by drift. A firm begins with a small portfolio on shared equipment, where carryover looks low-risk. Cleaning is done conscientiously and checked visually — and it works, because the actives are forgiving and batches infrequent. The logbook becomes the record of that working practice.

Then the portfolio grows. Potencies rise, solubility falls, some actives become harder to remove, changeover frequency increases. None of this forces a validation exercise under a change-management system that was never designed to watch cleaning. Practice that was adequate at the start is now inadequate, but equipment still gets released because the ritual — clean, look, sign — still completes. A visible residue is the moment the ritual is caught being a ritual.

Questions for our programme

• For every non-dedicated equipment item, can we produce the cleaning validation study — acceptance criteria, recovery data, worst-case justification — rather than only a cleaning record?
• Who is authorised to release equipment as clean, against what written acceptance criteria, under what lighting and viewing conditions?
• Have we defined maximum hold times before cleaning for each product/equipment pair, with data showing the procedure works at end of hold?
• If a residue were found tomorrow on equipment we had released, could we name the residues, identify all potentially affected equipment, and state whether affected product was distributed?
• Does change management require a cleaning assessment when a new product, potency or equipment item enters shared equipment?
• Would our response be a test result, or a retrospective assessment of the whole cleaning programme?

Wider context

Equipment released as clean while residue remains is a recurring FDA theme, not a Chemco curiosity. Recent warning letters have cited visible product residue and oxidised metal surfaces on both shared and dedicated equipment that quality assurance had already approved. FDA's position is consistent: a fix limited to better visual inspection — enhanced lighting plus training — is insufficient on its own, because it neither demonstrates that cleaning procedures are suitable and effective nor assesses impact on product currently on the market within expiry.

The durable message: cleaning validation is a lifecycle commitment — procedures, validation with a worst-case basis, routine verification of execution, and change management that notices when the portfolio makes yesterday's cleaning obsolete. The residue in Tank #68 was the symptom. The absent validation was the disease.

Sources

• FDA Warning Letter 320-26-60, Chemco Corporation, MARCS-CMS 721592, 7 April 2026 (primary source)
• Assyro regulatory intelligence record, Warning Letter Chemco Corporation (7 April 2026)
• KeyPedia warning letter and Form 483 records, Chemco Corporation (inspection 11–22 August 2025)