FirstAlerts

Accord Healthcare Recalls Levothyroxine Sodium Tablets, 100 mcg, Over Subpotency

The FDA's enforcement report lists a Class II recall of specific lots of the prescription thyroid drug, distributed nationwide, for a subpotent drug.

By AI ReporterWritten Sep 9, 2026, 9:38 p.m. ET
of , North Carolina, is recalling Levothyroxine Sodium Tablets, USP, 100 mcg (0.1 mg) because the drug is subpotent, according to the FDA's enforcement report for recall number . The recall was initiated on August 6, 2026, and reported on September 2, 2026, and its status is . The affected product is packaged in 90-count bottles (NDC 16729-451-15) and 1000-count bottles (NDC 16729-451-17), and is labeled Rx Only. It was manufactured for , , NC 27617, by Intas Pharmaceuticals Limited, Camp Road, Selaqui, Dehradun-248 197, India. The FDA's enforcement report lists the following lots and expiration dates: Lot D2402186, Exp. Date 09/30/2026; Lot D2402019, Exp. Date 08/31/2026; Lot D2402094, Exp. Date 09/30/2026; and Lots D2500022, D2500023, D2500021, Exp. Date 12/31/2026. The recall is classified as , which the FDA defines as the category used where the product may cause temporary or medically reversible harm, and where the chance of serious harm is remote. Distribution was . Levothyroxine Sodium Tablets, USP, 100 mcg is an oral solid finished drug product made from synthetically manufactured levothyroxine sodium blended with inactive pharmaceutical excipients, packaged as standard solid tablets in plastic bottles and distributed to consumers through pharmacies, according to the National Institutes of Health. It is normally sold as a prescription-only pharmaceutical. The FDA's enforcement database records no other enforcement action by this firm. That history is context only and says nothing about fault in this action.

Was this report accurate and useful?

Sources

Revision history

  1. Version 110 Sept 2026, 01:38current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.