FDA Records Class I Recall of Abiomed Impella CP Pump Sets Over Introducer Leak Risk
An FDA enforcement report covering 87,277 units cites potential introducer sheath leakage that the record says is not visually detectable by users.
Was this report accurate and useful?
Sources
- https://api.fda.gov/food/enforcement.json?search=recall_number:%22Z-2682-2026%22
- https://www.fda.gov/safety/industry-guidance-recalls/recalls-background-and-definitions
- https://www.fda.gov/media/140763/download
- https://www.ncbi.nlm.nih.gov/books/NBK572322/bin/fdacovideuas_140767.pdf
- https://cce.upmc.com/sites/default/files/Impella%20CP%20Step-by-Step%20Insertion%20Guide%20Handheld%20(2).pdf
- https://eurointervention.pcronline.com/article/tools-and-techniques-clinical-percutaneous-catheter-based-left-ventricular-support-using-the-impella-cp
Revision history
- Version 67 Aug 2026, 14:49current
No new facts; headline and dek added, body unchanged.
- Version 57 Aug 2026, 13:38
Expanded the device-description paragraph with FDA and clinical-documentation detail on the pump set's contents (purge cassette, guidewires, dilators, peel-away sheath) and added the corresponding source URLs.
- Version 47 Aug 2026, 08:43
Replaced the device description previously attributed to FDA premarket approval documents (including the Danvers, Massachusetts manufacturer address) with the sourced EuroIntervention description, and noted that available sources do not state materials or place of manufacture.
- Version 37 Aug 2026, 03:53
Added a paragraph describing what the device is and who uses it, sourced to FDA premarket approval documents, with the manufacturer location in Danvers, Massachusetts.
- Version 26 Aug 2026, 23:52
Removed the device-description paragraph sourced outside the fact set and listed the recall's distribution countries in full as given in the enforcement record.
- Version 16 Aug 2026, 18:49
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.