Devices › Orthopedic stereotaxic instrument
Device brand name · Orthopedic stereotaxic instrument
Navio Surgical System Us: medical device reports filed with FDA
334 reports name it, 2019–2025. Manufacturer given most often on reports: Blue Belt Technologies. Product code OLO.
- 334
- device reports naming the brand
- 0% of all MAUDE reports · about 48 a year
- 0
- reports, 12 months to August 2026
- 3 in the 12 months before
- 40.1%
- classified as malfunction
- 81.6% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
334 medical device reports received by FDA name the brand "Navio Surgical System Us" (orthopedic stereotaxic instrument); the manufacturer given most often on reports is Blue Belt Technologies; received from July 2019 to March 2025. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
0 reports arrived in the 12 months to August 2026, against 3 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are injury (59.9%) and malfunction (40.1%); across all orthopedic stereotaxic instrument reports (product code OLO) death is recorded in 0.1% and malfunction in 81.6%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are computer software problem (20.1%), application program problem (16.2%) and application program problem: parameter calculation error (12.6%). The patient problems coded most often are injury, no patient involvement and fibrosis. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 20,634 reports carrying product code OLO. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| Computer software problema software problem | 67 | 20.1% | 2.7% |
| Application program problem | 54 | 16.2% | 0.9% |
| Application program problem: parameter calculation error | 42 | 12.6% | 2.9% |
| Display or visual feedback problem | 19 | 5.7% | 0.6% |
| Unintended application program shut down | 14 | 4.2% | 2.4% |
| Insufficient device problem information | 12 | 3.6% | 4.4% |
| Mechanical problema mechanical problem | 12 | 3.6% | 9.2% |
| Circuit failure | 9 | 2.7% | 0.3% |
| Application program freezes or fails to launch | 7 | 2.1% | 0.5% |
| Mechanics altered | 7 | 2.1% | 0.6% |
| Image orientation incorrect | 6 | 1.8% | 0.1% |
| No display/image | 6 | 1.8% | 0.1% |
| Battery problema problem with the battery | 5 | 1.5% | 0.1% |
| Computer operating system problem | 5 | 1.5% | 0.3% |
| Connection problema connection problem | 5 | 1.5% | 2.4% |
| Calibration problem | 4 | 1.2% | 0.2% |
| Failure to cut | 4 | 1.2% | 0.3% |
| Intermittent communication failure | 4 | 1.2% | 0.3% |
| Failure to calibrate | 3 | 0.9% | 0.7% |
| Failure to power up | 3 | 0.9% | 0.2% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Injurya physical injury | 92 | 27.5% |
| No patient involvement | 19 | 5.7% |
| Fibrosis | 4 | 1.2% |
| Failure of implant | 2 | 0.6% |
| Missing value reason | 2 | 0.6% |
| Painpain, site not specified | 2 | 0.6% |
| Test result | 2 | 0.6% |
| Bone fracture(s) | 1 | 0.3% |
| Deformity/ disfigurement | 1 | 0.3% |
| Falla fall | 1 | 0.3% |
| Loss of range of motion | 1 | 0.3% |
| Nerve damage | 1 | 0.3% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Navio Surgical System Us | Product code OLO | All MAUDE reports |
|---|---|---|---|
| Reports | 334 | 20,634 | 26,136,888 |
| Share of that pool | — | 1.6% | 0% |
| Classified as death, per 1,000 reports | 0 | 1 | 9 |
| Classified as injury | 59.9% | 18.2% | 36.2% |
| Classified as malfunction | 40.1% | 81.6% | 62.3% |
| Filed by the manufacturer | 100% | 99.1% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code OLO
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Mazor X System | 1,009 | 238 | 0.6% |
| Real Intelligence Cori | 983 | 97 | 0% |
| 3 0 Rio Robotic Arm - Mics | 847 | 2 | 0% |
| Handpiece MICS | 812 | 183 | 0% |
| Reamer Handle Offset | 758 | 345 | 0% |
| Velys Saw Interface Right | 611 | 124 | 0% |
| Velys Saw Interface Left | 597 | 125 | 0% |
| Excelsius Gps | 597 | 128 | 0.3% |
| Real Intelligence Robotic Drill | 585 | 81 | 0% |
| Navio Handpiece | 489 | 0 | 0% |
| NavLock | 464 | 90 | 0% |
| Velys Satellite Station | 353 | 94 | 0% |
| Mako Robotic Arm 3 1 | 317 | 65 | 0% |
| Velys Saw Handpiece | 269 | 82 | 0% |
| Velys | 257 | 257 | 0% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Navio Surgical System Us reports
How many FDA reports name Navio Surgical System Us?
334 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
injury (59.9%) and malfunction (40.1%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
computer software problem (20.1%), application program problem (16.2%), application program problem: parameter calculation error (12.6%), display or visual feedback problem (5.7%) and unintended application program shut down (4.2%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Navio Surgical System Us was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.