FDA Publishes October 2026 Impella Controller Recall: 900 Devices to Be Corrected While Remaining in Use, Distributed to 31 Countries and Regions

FDA Publishes October 2026 Impella Controller Recall: 900 Devices to Be Corrected While Remaining in Use, Distributed to 31 Countries and Regions

Published 2 November 2026, 19:57 | Recall and Safety Notices

Recall Scope: Controllers, Not the Catheter Pump

On 18 September 2026, Abiomed issued an “Urgent Medical Device Recall (Removal)” letter to customers. On 28 October 2026, the U.S. Food and Drug Administration (FDA) entered the event into its Device Recall database and published three recall numbers: Z-0208-2027, Z-0209-2027 and Z-0210-2027, all under event number 99778.

The devices subject to return are not intracorporeal catheters but three types of external controllers: the Automated Impella Controller (428 units), the Impella Optical Controller (179 units) and the Impella Connect Optical AIC (293 units), totalling 900 units. FDA records show that all three products share product code OZD, are linked to premarket approval numbers P140003 and P170011, and fall within device class III. In other words, this is a field correction action directed at the “brain” of the cardiac support system; the catheter pump itself is not within the scope of this recall.

Four Defect Categories Identified Through a Retrospective Review

The recall reason given in the official records originates from a retrospective review of service records conducted by the company. No single adverse event served as the starting point. The review found that certain controllers required hardware, firmware or software updates, falling into four categories.

• Radio-frequency identification (RFID) firmware issue: the controller may fail to recognise the purge cassette during start-up set-up or when a cassette consumable is replaced, potentially delaying a procedure or treatment.
• Rotary push-button sticking and unreliable actuation: the operator may be unable to select or confirm menu items, effectively losing control of the console.
• Controller instability: the controller may fail to start or may be unable to drive the pump, in which case the console must be replaced.
• Software defect caused by a computational process crash: negative central venous pressure values may appear in the calculated pulmonary artery pressure result.

The first three categories directly interrupt circulatory support, while the fourth affects the reliability of haemodynamic readings. The company records the root cause as “under company investigation” and does not state a conclusion in the published record.

Continued Use Pending Correction Is a Distinguishing Feature of This Action

The handling instructions in the recall letter merit attention: while awaiting Abiomed service, affected devices may remain in use on the grounds of maintaining continuity of therapy. The company requires customers first to inventory the handheld devices in use; Abiomed then contacts each customer individually to coordinate collection, upgrade and return. Customers must complete and return a business reply form and may also submit it via a designated email address or fax. If a device has been transferred to another organisation, the original holder is obliged to notify the receiving party.

This arrangement shows that the correction is not achieved by taking devices out of service but by repairing them one unit at a time. For users, the critical points are whether serial numbers are accurately identified and whether the repair schedule can be tracked. If the affected-unit list is wrong, notifications will not reach the right parties.

Distribution Covers 31 Countries and Regions

The distribution scope recorded by the FDA covers the entire United States plus multiple overseas markets, listing Belgium, Brazil, Canada, Colombia, Croatia, the Czech Republic, Finland, France, Germany, Hong Kong (China), India, Ireland, Italy, Kuwait, Luxembourg, Malaysia, Mexico, the Netherlands, Norway, Pakistan, Panama, Poland, Saudi Arabia, Singapore, Slovenia, South Korea, Spain, Sweden, Switzerland, the United Arab Emirates and the United Kingdom — 31 countries and regions in total. Mainland China and Japan do not appear on the list.

For companies operating across multiple markets, the practical significance of this list is that the same controllers may have changed hands several times, been transferred across borders or entered rental pools; screening solely against purchase records will often leave gaps.

How This Recall Differs From a Single-Fault Recall

Conventional device recalls are triggered by a specific malfunction or adverse event, with clear boundaries and a countable scope. This action is closer to a consolidated remediation following a review: the company identified multiple pending update items across devices of the same model in its service records, included all serial numbers requiring upgrade in a single field action, and is resolving them through repair rather than deactivation.

This type of recall places higher demands on the quality management system. It requires the company to reconstruct, by serial number, each device’s location of use, service history and transfer path, and requires its field service network to perform hardware replacement and firmware and software upgrades at customer sites. Without these two capabilities, corrective action tends to stop at the level of “notification issued”.

Sources and Scope of Application

Source: U.S. Food and Drug Administration (FDA) — Device Recall database, event number 99778, recall numbers Z-0208-2027, Z-0209-2027 and Z-0210-2027, publication date 28 October 2026, recall initiation date 18 September 2026; record address https://api.fda.gov/device/recall.json?search=res_event_number:99778. The same entry can also be viewed on the FDA recall database search page at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfRes/res.cfm?id=99778.

Verification scope and access date: Three product records under the above event number were verified for this article, with item-by-item comparison of recall reason, corrective action, product quantity, distribution scope and product code; the access date was 2 November 2026. The recall classification was not provided in the record fields readable at the time of verification, and therefore no classification determination is made in this article.

Scope of application: This article is an interpretation of publicly available regulatory information and does not constitute a conclusion or commitment regarding any specific product, company or registration application. The recall scope, quantities and handling requirements are governed by the official original text, and the information may change with subsequent official updates. Handling of specific devices should be carried out directly in accordance with the manufacturer’s notice and the requirements of the competent authorities.

AIMEILI Regulatory Interpretation

Field correction rather than market withdrawal

Although the action is recorded as a “removal”, its substance is a field correction: devices remain in clinical use while hardware, firmware or software updates are completed. For regulatory affairs teams, the key point is that the scope of the action is defined by device serial number and configuration rather than by product family alone. Any distributor, rental provider or servicing organisation holding affected controllers should reconcile its inventory against the manufacturer’s affected-unit list and confirm that end users have received the customer letter and the business reply form.

Multiple defect modes under a single event number

Four distinct defect categories — RFID firmware, mechanical button actuation, start-up and pump-drive failure, and a calculation software fault — are consolidated under one event number and three recall numbers. This pattern is typical of remediation driven by a service-record review rather than by a single adverse event. From a regulatory standpoint, it means that a single health hazard evaluation may cover hardware, firmware and software corrections simultaneously, and that the corresponding corrective and preventive action records must trace each defect mode separately while linking them to a common field action.

Root cause still open

The root cause is recorded as under company investigation. Where a recall notification is issued before root cause conclusion, regulators generally expect the manufacturer to maintain an open investigation record, to define interim risk controls, and to update the field action if the investigation later expands or narrows the affected population.

Business Impact

For manufacturers

• Serial-number traceability is the operational bottleneck. Field actions of this kind depend on the ability to reconstruct each unit’s current location, service history and transfer path. Gaps in distribution records translate directly into missed notifications.
• Service network capability determines execution speed. Completing hardware replacement and firmware or software upgrades on site requires trained field service engineers and controlled update procedures; without this capacity, correction stalls after notification.
• Regulatory reporting across 31 markets. A U.S. recall database entry does not in itself satisfy notification obligations in other jurisdictions. Manufacturers should assess whether parallel vigilance reports, field safety notices or competent authority notifications are required in each listed market, and align timing and content.
• Documentation consistency. Health hazard evaluations, risk management files, CAPA records and the customer letter should present the same defect descriptions, affected quantities and corrective actions.

For distributors and healthcare providers

• Inventory reconciliation by serial number should be completed promptly, including devices in rental pools, loaner fleets or transferred to other institutions; the transferring party must notify the receiving party.
• Business reply forms should be returned through the designated channels so that service scheduling can be coordinated.
• Clinical awareness of the four failure modes supports timely recognition of console start-up failure, unresponsive buttons or implausible haemodynamic values, and escalation under existing procedures.

For regulatory affairs and CRO teams supporting cross-border portfolios

• Treat the distribution list as a market-by-market notification checklist rather than a single U.S. event.
• Confirm whether the device configuration marketed in each jurisdiction corresponds to the affected models and software versions.
• Monitor subsequent FDA record updates, including any classification or root cause conclusion, and reflect them in vigilance files and periodic safety reporting.

Information Source

U.S. Food and Drug Administration (FDA) — Device Recall database, event 99778, 28 October 2026.

U.S. Food and Drug Administration (FDA) — Class Device Recall detail.