FirstAlerts

FDA Expands Recall of Medtronic Bravo CF Capsule Delivery Devices

The FDA has expanded its ongoing recall of Medtronic Bravo CF capsule delivery devices, adding new lot codes and urging users to quarantine and return affected devices.

4 reports on this incident · first at Aug 28, 2026, 7:01 a.m. ET

By AI ReporterFirst reported Aug 28, 2026, 6:10 a.m. ETWritten Aug 28, 2026, 7:15 a.m. ET
The U.S. Food and Drug Administration (FDA) has expanded its recall of Bravo CF capsule delivery devices, according to a report from Medical Daily. The recall, initiated on August 6, 2026, now includes additional lot codes: FGS-0635 and FGS-0636. The devices are sold in one-pack and five-pack configurations. The recall was expanded because the capsule may fail to attach to the esophageal wall or to detach from the delivery device as intended, posing risks of aspiration or inhalation of the capsule, perforation of the esophagus, airway obstruction, bleeding, laceration of the esophagus, delayed diagnosis, and foreign bodies remaining in the patient. As of August 10, 2026, there have been 184 serious injuries and no deaths, according to Medical Daily. The FDA advises users to . The recall is .

Earlier reports

  1. Aug 28, 2026, 7:11 a.m. ET

    FDA Reports 184 Injuries in Ongoing Medtronic Bravo CF Capsule Recall

    The U.S. Food and Drug Administration (FDA) has reported 184 serious injuries and no deaths associated with the use of Medtronic's Bravo CF capsule delivery devices, as of August 10, 2026, according to Medical Daily.

    The FDA initiated an ongoing recall on August 6, 2026, for the Bravo CF capsule delivery devices, available in one-pack and five-pack configurations, with identifying codes FGS-0635 and FGS-0636. The agency states the capsule may fail to attach to the esophageal wall or to detach from the delivery device as intended, posing hazards including aspiration or inhalation of the capsule, perforation of the esophagus, obstruction of the airway, bleeding, laceration of the esophagus, delayed diagnosis, and foreign bodies remaining in the patient.

    The FDA advises identifying and quarantining all unused affected devices and returning them for replacement.

  2. Aug 28, 2026, 7:07 a.m. ET

    FDA Closes Recall of Medtronic Bravo CF Capsule Delivery Devices

    The U.S. Food and Drug Administration has closed the recall of Medtronic Bravo CF capsule delivery devices, according to a report from Medical Daily. The closure means the agency considers the recall carried out. The devices, sold in one-pack and five-pack configurations, carry identifying codes FGS-0635 and FGS-0636.

    The recall was initiated on August 6, 2026, because the capsule may fail to attach to the esophageal wall or to detach from the delivery device as intended. The FDA reported 184 serious injuries and no deaths as of August 10, 2026. The hazard includes aspiration or inhalation of the capsule, perforation of the esophagus, obstruction of the airway, bleeding, laceration of the esophagus, delayed diagnosis, and foreign bodies remaining in the patient.

    The remedy instructed users to identify and quarantine all unused affected devices and return them for replacement. The status of the recall is ongoing.

  3. Aug 28, 2026, 7:01 a.m. ETFirst report

    FDA Issues Early Alert for Medtronic Bravo CF Capsule Delivery Devices

    The U.S. Food and Drug Administration (FDA) has issued an early alert concerning Medtronic Bravo CF capsule delivery devices, according to a report from Medical Daily. The alert, initiated on August 6, 2026, covers devices in one-pack and five-pack configurations, identified by model codes FGS-0635 and FGS-0636.

    The FDA reported that the capsule may fail to attach to the esophageal wall or detach from the delivery device as intended, potentially leading to aspiration or inhalation of the capsule, perforation of the esophagus, airway obstruction, bleeding, laceration of the esophagus, delayed diagnosis, or foreign bodies remaining in the patient. As of August 10, 2026, there have been 184 serious injuries and no deaths reported, according to Medical Daily.

    The FDA advises identifying and quarantining all unused affected devices and returning them for replacement. The status of the alert is ongoing.

Was this report accurate and useful?

Sources

Revision history

  1. Version 128 Aug 2026, 11:15current

    First published.

  2. Version 128 Aug 2026, 11:01current

    First published.

  3. Version 128 Aug 2026, 11:11current

    First published.

  4. Version 128 Aug 2026, 11:07current

    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.