FDA 483 OBSERVATION · #104 OF 1,945 MOST-CITED

Investigation of device failures

FDA cited this observation 290 times across 271 firms in recent inspections. Below: how it breaks down by program area and fiscal year, and real examples of how FDA worded it on Form FDA 483.

BY PROGRAM AREA
Devices290
BY FISCAL YEAR
FY20266
FY202515
FY202412
FY202329
FY202223
FY202117
FY202013
FY201932
FY201848
FY201745
FY201650

What this observation means, and how to comply

SPEQ's practitioner reading of this finding. The regulatory basis is a cited fact; the interpretation, compliance steps, and root causes are SPEQ synthesis — not an FDA classification of the citation.

21 CFR 820.198 · 820.100

21 CFR 820.198 (Complaint files) is a Quality System Regulation section; since QMSR took effect on 2 February 2026 FDA inspects this as “Complaint Handling”: 21 CFR 820.10(b)(3)–(4) and 820.35, and ISO 13485 clauses 8.2.2 and 8.2.3 (CP 7382.850 Attachment A).

The device manufacturer did not adequately investigate device failures surfaced through complaints (or other sources), so the causes of failures — and whether they were reportable — were not properly determined.

Why FDA writes it — Device failures are signals of a quality or safety problem. Failing to investigate them means recurring failures go uncorrected and reportable events go unreported, defeating both CAPA and the FDA’s market-wide safety surveillance.

HOW TO COMPLY
  • Investigate complaints involving possible failure of a device to meet its specifications, unless a similar failure was already investigated.
  • Determine the cause where practicable, and feed systemic causes into CAPA.
  • Screen each failure for MDR reportability and report reportable events on time.
  • Document the investigation, its conclusions, and any corrective action.
WHY FIRMS GET CITED
  • Device failures closed without investigation or root cause.
  • No screen for MDR reportability within the failure investigation.
PROFESSIONAL · REMEDIATION PLAYBOOK · SPEQ SYNTHESIS

How to close this finding — and stop it recurring

CHECKING ACCESS

Checking your access…

What this observation is associated with

Firms cited for this observation also appear in FDA compliance actions — warning letters, injunctions, or seizures — at 1.4× the rate of the average FDA-cited firm (10.7% vs 7.8%), across 271 FEI-matched firms.

This is an association, not causation, and reflects co-occurrence in FDA's records — not a claim that the observation caused or preceded the action.

CHECKING ACCESS

Checking your access…

How FDA worded it — real examples

Complaints involving the possible failure of a device to meet any of its specifications were not investigated where necessary.

Nuclein LLC · Austin, Texas · Devices · 2026-01-13

Complaints involving the possible failure of a device to meet any of its specifications were not where necessary.

Shirakawa Olympus Co., Ltd. · Nishishirakawa-Gun · Devices · 2025-11-14

Complaints involving the possible failure of a device to meet any of its specifications were not investigated where necessary.

PNEO, LLC · Denton, Texas · Devices · 2025-11-05

Complaints involving the possible failure of a device to meet any of its specifications were not reviewed, evaluated and investigated where necessary.

Hologic, Inc · Marlborough, Massachusetts · Devices · 2025-11-04

Complaints involving the possible failure of a device to meet any of its specifications were not investigated where necessary.

Vesalio, Inc. · San Diego, California · Devices · 2025-10-30

Complaints involving the possible failure of a device to meet any of its specifications were not reviewed, evaluated and investigated where necessary.

McLaren Flint · Flint, Michigan · Devices · 2025-10-20

Related SPEQ references

Where to read the requirements behind this observation area on SPEQ. These are SPEQ's topic and audience pages — not an FDA classification of the citation.

Quality risk management →Medical device quality →Medical devices →

Examples are a representative sample of FDA's published inspection observations. Open the 483 observation explorer →