FDA Reports Recall of 37,250 Vials of Xylocaine Injection Over Hair Found in Products
An FDA enforcement report dated July 29, 2026 lists a nationwide Class II recall by Fresenius Kabi USA, LLC of one lot of lidocaine HCl injection.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22D-0729-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://dailymed.nlm.nih.gov/dailymed/lookup.cfm?setid=c1735498-0721-687c-e053-2a95a90a47f4
- https://dailymed.nlm.nih.gov/dailymed/fda/fdaDrugXsl.cfm?setid=07a2b40b-0386-40d4-b0c4-e69e13610cd9
- https://www.federalregister.gov/documents/2002/02/01/02-2548/amendment-of-regulations-regarding-certain-label-statements-on-prescription-drugs
Revision history
- Version 67 Aug 2026, 13:48current
No new facts; added headline and dek and confirmed all figures against the FDA enforcement report.
- Version 57 Aug 2026, 11:54
Added headline and dek; corrected the chemical designation and pH/excipient description to match the DailyMed labeling and removed the unsourced sodium chloride reference.
- Version 47 Aug 2026, 07:01
Removed unsupported reference to veterinary practices, added the drug's chemical designation and sodium chloride/0.1% methylparaben composition from the DailyMed labeling, and added the source URLs the story is written from.
- Version 37 Aug 2026, 02:15
Removed the uncited "0.1%" methylparaben figure and the unsupported stopper-puncture detail, clarified the distribution chain per the DailyMed background, and added the source URLs.
- Version 26 Aug 2026, 21:21
Corrected the product-background paragraph to match the DailyMed labeling (0.1% methylparaben; pH adjusted with sodium hydroxide and/or hydrochloric acid), removed unsourced details on sodium chloride, pH value, dental practices and label inspection instructions, and attributed the description to DailyMed.
- Version 16 Aug 2026, 17:19
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.