Device type · NCF
Aberrometer, Ophthalmic
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
NCF
Ophthalmic
Device class
Class I
FDA decisions since 2015
0
510(k), De Novo and PMA
Adverse event reports
46
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Aberrometer, Ophthalmic
- Product code
- NCF
- Device class
- Class I
- Review panel
- Ophthalmic
- Regulation
- 21 CFR 886.1760
- Specialty
- Ophthalmology
- FDA record
- Classification database entry for NCF
Latest FDA decisions
No 510(k), De Novo or PMA decisions for this product code since 2015.
Reports received
46
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
24
52% of reports
Injury reports
22
48% of reports
Death reports
0
0.0% of reports
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 2 | 1 | 0 | 0 |
| Jan 24 | 4 | 0 | 0 | 0 |
| Feb 24 | 2 | 1 | 0 | 0 |
| Mar 24 | 1 | 2 | 0 | 0 |
| Apr 24 | 0 | 1 | 0 | 0 |
| May 24 | 2 | 2 | 0 | 0 |
| Jun 24 | 4 | 1 | 0 | 0 |
| Jul 24 | 0 | 3 | 0 | 0 |
| Aug 24 | 0 | 1 | 0 | 0 |
| Sep 24 | 1 | 0 | 0 | 0 |
| Oct 24 | 0 | 2 | 0 | 0 |
| Nov 24 | 2 | 4 | 0 | 0 |
| Dec 24 | 1 | 0 | 0 | 0 |
| Jan 25 | 0 | 2 | 0 | 0 |
| Feb 25 | 0 | 4 | 0 | 0 |
| Mar 25 | 2 | 3 | 0 | 0 |
| Apr 25 | 2 | 2 | 0 | 0 |
| May 25 | 2 | 2 | 0 | 0 |
| Jun 25 | 1 | 7 | 0 | 0 |
| Jul 25 | 0 | 2 | 0 | 0 |
| Aug 25 | 0 | 0 | 0 | 0 |
| Sep 25 | 2 | 1 | 0 | 0 |
| Oct 25 | 0 | 0 | 0 | 0 |
| Nov 25 | 3 | 3 | 0 | 0 |
| Dec 25 | 0 | 1 | 0 | 0 |
| Jan 26 | 2 | 1 | 0 | 0 |
| Feb 26 | 6 | 1 | 0 | 0 |
| Mar 26 | 1 | 0 | 0 | 0 |
| Apr 26 | 0 | 0 | 0 | 0 |
| May 26 | 1 | 4 | 0 | 0 |
| Jun 26 | 3 | 4 | 0 | 0 |
| Jul 26 | 4 | 6 | 0 | 0 |
| Aug 26 | 1 | 2 | 0 | 0 |
| Sep 26 | 1 | 0 | 0 | 0 |
| Oct 26 | 2 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Incorrect, Inadequate or Imprecise Result or Readings41
- Defective Component2
- Failure to Align2
- Component Incompatible1
- Component or Accessory Incompatibility1
- Nonstandard Device1
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Insufficient Information18
- Visual Impairment16
- Blurred Vision9
- Appropriate Clinical Signs, Symptoms and Conditions Term/Code Not Available6
- No Clinical Signs, Symptoms or Conditions4
- Corneal Edema1
- Diplopia/Double Vision1
- Dry Eye(s)1
- Eye Irritation1
- Eye Pain1
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
- ORA System with VerifEye+ Cart, Catalog Number 8065998307 For use during intraocular lens surgeryTerminated
Z-3049-2017 · Started Jun 30, 2017
Reason given: Some ORA Carts have the potential to return an incorrect IOL power measurement during cataract surgery. This issue appears to have been caused by a software coding error that results in the lens coefficients for an IOL model being downloaded from the Alcon server in an incorrect order.
Cause as FDA categorized it: Software design
- ORA System with VerifEye, Catalog Number 8065998300 For use during intraocular lens surgeryTerminated
Z-3050-2017 · Started Jun 30, 2017
Reason given: Some ORA Carts have the potential to return an incorrect IOL power measurement during cataract surgery. This issue appears to have been caused by a software coding error that results in the lens coefficients for an IOL model being downloaded from the Alcon server in an incorrect order.
Cause as FDA categorized it: Software design
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.