Arnuity Ellipta Powder
FDA Recall NDC 0173-0876
FDA Enforcement Report: View Recall Date, Reasons, and Safety Status
Active & Historical Enforcement Reports
The FDA has identified 1 recorded enforcement report(s) associated with Arnuity Ellipta (NDC 0173-0876). A significant event, classified as Class II, was initiated on Mar 15, 2021 by Glaxosmithkline Llc. The reported reason for this action was: "CGMP Deviations: Intermittent exposure to temperature excursion during storage."
This specific recall has a current status of TERMINATED, indicating that the FDA considers the recall process finished or the product successfully recovered.
This specific recall has a current status of TERMINATED, indicating that the FDA considers the recall process finished or the product successfully recovered.
Reported Recall Events
Class II Terminated
CGMP Deviations: Intermittent exposure to temperature excursion during storage.
Mar 15, 2021
Jun 02, 2021
353 inhalers
Recall Profile & Regulatory Data
Event ID
87512
Classification
Class II
Enforcement Status
Terminated
Recalling Firm
Cardinal Health Inc.
Voluntary / Mandated
Voluntary: Firm initiated
Distribution Pattern
FL, GA, SC
Termination Date
Jun 17, 2024
Product Description
Arnuity Ellipta (fluticasone furoate inhalation powder) 200 mcg 1 Ellipta Inhaler containing 1 Foil Strip of 30 Blisters Rx Only NDC 0173-0876-10 GlaxoSmithKline Research Triangle Park, NC 27709
Batch or Lot Expiration Information
Lot# 5U3D
Affected Packages Involved in this Recall
0173-0888-10Product
0173-0874-10Product
0173-0874-14Product
0173-0876-10Product
0173-0876-14Product
About FDA Recall Enforcement Reports
FDA recall data documents classified recall actions associated with a product. Most recalls are limited to specific lots, batches, or package configurations rather than every unit of a drug.
If a recall is listed for an NDC, review the affected lot information and package details carefully. Patients and healthcare professionals should confirm whether a specific product in hand matches the lot or package information before assuming it is affected.
