Fresenius Kabi Recalls 93,250 Vials of Xylocaine Injection After Hair Found in Product
An FDA enforcement report lists a Class II, nationwide recall of one lot of 1% lidocaine HCl injection initiated on July 16, 2026.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22D-0728-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=24e7b8b6-2de2-466d-ae2e-5eba8b2bc754
- https://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=3b2dd84e-cee8-4e58-d494-395a65a353a0
- https://dailymed.nlm.nih.gov/dailymed/fda/fdaDrugXsl.cfm?setid=07a2b40b-0386-40d4-b0c4-e69e13610cd9
- https://dailymed.nlm.nih.gov/dailymed/lookup.cfm?setid=cddb2b22-fce3-8967-6e54-dca3df5ac4b3
Revision history
- Version 67 Aug 2026, 15:29current
No new facts in the record; added headline and dek and retained the enforcement report, classification definition, product description and firm recall history unchanged.
- Version 57 Aug 2026, 10:49
Corrected formulation details to match the DailyMed labelling records: methylparaben stated as 0.1%, pH range roughly 5.0–7.0, and the chemical designation given without the monohydrate wording; clarified packaging and storage description.
- Version 47 Aug 2026, 06:09
Removed the historical origin claims about the compound's discovery and their unlisted sources; restored label details (nonpyrogenic, methylparaben 1 mg per mL) and distribution description to the DailyMed records.
- Version 37 Aug 2026, 01:21
Removed composition figures not present in the source record (molecular weight, 0.1% preservative concentration), added the pH detail and the compound's 1940s origin, and split the closing paragraph.
- Version 26 Aug 2026, 20:59
Corrected the product description to match DailyMed labelling (removed sodium chloride and the pre-use inspection line, added chemical designation and pH adjustment) and added the source URLs.
- Version 16 Aug 2026, 16:24
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.