When a Recall Is Not Reported to Customers: 21 CFR 806 and the Luna G3 Class I Recall

It is rare for a regulator to write down, in its own words, that a manufacturer fixed a device and did not tell the people using it. In the Luna G3 Class I recall, the United States Food and Drug Administration did exactly that. The recall notice states that the corrective action was not reported to customers, and that up to 196 units may never have received the fix at all. For anyone who runs a medical device quality system, this is not just another recall. It is a clean case study in what 21 CFR Part 806 requires, and what happens when a field correction is neither reported nor completed.

This article walks through the case, explains the correction and removal reporting duty under 21 CFR 806, and then draws the line every Canadian device firm should care about: the parallel duty under the Medical Devices Regulations, SOR/98-282. One important caution up front. The Luna G3 devices were distributed in the United States only, and there is no Health Canada recall tied to them. We use the case as a teaching example, not as a claim of Canadian market exposure.

Executive Summary

The FDA classified a recall of 20,160 Luna G3 APAP devices as Class I on 19 August 2026, after a firmware defect could cause the device to display an error and shut down, stopping therapy. The manufacturer upgraded the firmware at the United States importer's warehouse in late 2024, but later found that up to 196 units may still carry the defective firmware, and the FDA notice states the corrective action was not reported to customers. Under 21 CFR 806, a correction or removal made to reduce a risk to health must be reported to the FDA within 10 working days of being initiated. The case exposes two failures every quality system should test for: a field action that did not close, and a correction that was not communicated. Canadian firms carry a mirror duty under SOR/98-282, with a 24-hour reporting clock for recalls.

What Is 21 CFR 806?

What it is: 21 CFR Part 806 is the FDA rule on reports of corrections and removals for medical devices. Under section 806.10, a device manufacturer or importer must submit a written report to the FDA of any correction or removal it initiates to reduce a risk to health posed by the device, or to remedy a violation of the law that may present a risk to health. That report is due within 10 working days of initiating the action. The clock starts when you initiate the correction or removal, not when you finish investigating. The rule is published in the electronic Code of Federal Regulations.

Why it matters: not every correction or removal has to be reported, but the ones tied to a risk to health do, and they have to be reported quickly. Corrections and removals that are not reportable still have to be documented and kept under section 806.20. Firms get into trouble in two ways: they misjudge whether an action is reportable, or they treat a report as optional once the fix is under way. The Luna G3 case shows the second failure in plain language.

The Luna G3 Recall: What Happened

In short: the Luna G3 APAP is a home sleep-therapy device. A firmware defect meant that when the device ran under high pressure, a high respiratory rate and a high peak flow at the same time, it could display an error and shut down, so it stopped delivering therapy. The manufacturer upgraded the firmware, but the correction did not reach every device, and it was not communicated to customers. The FDA published the recall details on its recalls and safety alerts page. The verified facts are below.

A Class I recall is the most serious category, used when there is a reasonable probability that the product will cause serious injury or death. For a device that some patients rely on to breathe during sleep, an unannounced shutdown is exactly the kind of hazard that classification is meant to capture.

Correction or Removal? Why the Distinction Matters

What it is: under 21 CFR 806, a correction is a repair, modification, adjustment, relabelling, destruction or inspection of a device, including patient monitoring, without physically removing it from where it is used or sold. A removal is the physical removal of a device from where it is used or sold to some other location for one of those same purposes. A firmware upgrade is a correction. The reporting duty, and the 10-working-day clock, attach to both.

Why it matters: the label you put on the action does not change the duty. Some firms convince themselves that a quiet firmware push is a routine service update rather than a correction, and so decide it does not need to be reported. If the action was initiated to reduce a risk to health, it is reportable, whatever you call it internally. The safest posture is to decide reportability against the risk-to-health test, document the reasoning either way, and keep the record under 806.20 when you conclude an action is not reportable.

The Two Failures the FDA Documented

The first failure is a field action that did not close. The manufacturer upgraded the firmware at the importer's warehouse, but up to 196 of 20,160 units may never have received it. In quality-system terms, that is an effectiveness-check failure. A corrective action is not complete when the fix is designed. It is complete when you can show that the fix reached every affected unit, or that you accounted for the ones it did not. A firmware campaign that leaves 196 devices unverified has not been closed, and a well-run CAPA process is built to catch exactly that gap. We cover this pattern in our guide to why CAPA keeps failing.

The second failure is communication. The FDA notice states plainly that the corrective action was not reported to customers. A correction that is never communicated cannot be verified in the field, and it deprives clinicians and patients of the information they need to protect themselves while the fix is rolled out. Reporting to the regulator and communicating to customers are separate obligations, and both were in question here. This is the single most inspectable failure mode in a device quality system, because it is visible in the records without any need to reconstruct intent.

Your Canadian Duty: Recalls Under SOR/98-282

What it is: in Canada, medical device recalls are governed by the Medical Devices Regulations, SOR/98-282. A recall covers any action to deal with a device that may be hazardous to health, whether by correcting it or removing it from the market. The Canadian regime is not identical to 21 CFR 806, but it targets the same failure modes, and it moves faster in one respect: the holder must inform Health Canada of a recall within a tight window, with an initial 24-hour reporting expectation. Our full explainer sets out what counts as a device recall in Canada and the 24-hour clock.

Why it matters: if the Luna G3 scenario played out with a device on the Canadian market, the holder would need to notify Health Canada quickly, run the recall through to an effectiveness check, and keep records that show both the correction and the communication happened. The lesson travels across the border even though the recall did not. For how Canada grades severity, see our guide to recall classification types I, II and III.

Field Correction and Recall Readiness Checklist

• A written procedure decides reportability against the risk-to-health test, for both corrections and removals.
• The 10-working-day clock under 21 CFR 806 starts at initiation, and your process can meet it.
• Non-reportable corrections and removals are still documented and retained under section 806.20.
• Firmware and software updates are assessed as potential corrections, not waved through as routine service.
• Every field action has an effectiveness check that confirms the fix reached all affected units, with the exceptions accounted for.
• Customer and patient communication is a required, documented step, separate from the regulator report.
• For Canadian-market devices, the SOR/98-282 recall reporting duty and its 24-hour expectation are built into the SOP.
• A mock recall has been run in the last 12 months, and it tested traceability to the individual unit.

Common Mistakes

• Calling a risk-reducing firmware push a service update so it does not have to be reported. The risk-to-health test governs, not the label.
• Closing a field action when the fix is designed rather than when it is verified in the field. That is how 196 units stay uncorrected.
• Treating the regulator report as the whole duty and skipping customer communication. They are separate obligations.
• Starting the 10-day clock when the investigation ends. It starts when the correction or removal is initiated.
• Keeping no record of an action you judged non-reportable. Section 806.20 still requires the file.

Frequently Asked Questions

Do I have to report a firmware update to the FDA?

If the firmware update is a correction initiated to reduce a risk to health, or to remedy a violation that may present a risk to health, then yes, it must be reported to the FDA under 21 CFR 806 within 10 working days of being initiated. A firmware update made purely to add features and not tied to a risk to health is generally not reportable, but you should still document why you reached that conclusion and keep the record under section 806.20.

What is the difference between a correction and a removal under 21 CFR 806?

A correction fixes the device where it is, without physically moving it, for example by repairing, adjusting, relabelling or inspecting it, including patient monitoring. A removal physically takes the device from where it is used or sold to another location for one of those purposes. Both can trigger the reporting duty when they are done to reduce a risk to health.

If a field correction was never communicated to customers, is the recall complete?

No. A correction that is not communicated cannot be verified in the field and leaves users unaware of the hazard while the fix is rolled out. A recall is complete only when the action has reached the affected devices, the effectiveness of the action has been checked, and the required communications and reports have been made. In the Luna G3 case, the FDA specifically noted that the correction was not reported to customers.

Does a software configuration change count as a device modification that needs reporting?

It can. A software or configuration change that is made to reduce a risk to health is a correction for the purposes of 21 CFR 806, and the reporting duty applies. The test is whether the change addresses a risk to health, not whether it involves hardware. Assess each software change against that test and record your decision.

How fast must I report a device recall in Canada?

Under the Medical Devices Regulations, SOR/98-282, the duty holder must inform Health Canada of a recall promptly, with an initial reporting expectation of 24 hours, followed by the required recall information and an effectiveness check. The Canadian clock is tighter than the 10-working-day window in 21 CFR 806, so a firm selling in both markets needs procedures that satisfy the faster one.

Were any Canadian patients affected by the Luna G3 recall?

The recall notice states that the affected devices were distributed in the United States only, and there is no Health Canada recall tied to them. We present the case as a teaching example of correction and removal reporting, not as a claim of Canadian market exposure. Canadian device firms should still use it to test their own procedures.

How MFLRC Can Help

MFLRC helps device manufacturers, importers and MDEL holders build field-action and recall programmes that hold up under scrutiny. We design correction and removal procedures for both 21 CFR 806 and SOR/98-282, review your CAPA and effectiveness-check process, run mock recalls that test traceability to the individual unit, and support computer system validation and software change control so a firmware change is assessed correctly the first time. See our audit services, our medical devices practice, and our guide to running a recall simulation.

If your last field action left any unit unverified, that is the gap to close before an inspector finds it. Book a recall-programme review and we will pressure-test your corrections, removals and communications against both frameworks.

Conclusion

The Luna G3 recall is a short, clear lesson. A firmware fix that does not reach every device is not a closed corrective action, and a correction that is not communicated is not a completed recall. 21 CFR 806 sets out when you must report, how fast, and what to keep. SOR/98-282 sets the Canadian mirror, with a faster clock. The manufacturers who stay out of these notices are the ones who decide reportability against the risk-to-health test, verify their field actions to the last unit, and treat communication as a duty rather than a courtesy. Read your own procedures against this case, and fix the gap while it is still yours to fix.

Sources and References

• eCFR: 21 CFR 806.10, Reports of corrections and removals
• FDA: BMC Medical Co., Ltd. Recalls Luna G3 APAP (Model LG3600) Due to Firmware Defect
• Justice Laws Website: Medical Devices Regulations (SOR/98-282)