DEPLOYDatabase

Incident · Recall

Stryker recalls Mako RIO over loss of system power mid-procedure

Stryker recalled the Mako RIO robotic-arm interactive orthopedic system because the system could lose power during a procedure. 20 units. Source: FDA Class 2 device recall Z-2741-2017, accessdata.fda.gov / openFDA enforcement.

Occurred 2017-06-07 · Stryker

Machine-readable surfaces

Common questions

What happened in Stryker recalls Mako RIO over loss of system power mid-procedure?
Stryker recalled the Mako RIO robotic-arm interactive orthopedic system because the system could lose power during a procedure. 20 units. Source: FDA Class 2 device recall Z-2741-2017, accessdata.fda.gov / openFDA enforcement.
When did this incident occur?
The incident is recorded as occurring on June 7, 2017 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in Stryker recalls Mako RIO over loss of system power mid-procedure?
The incident is recorded as involving Stryker on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to Stryker recalls Mako RIO over loss of system power mid-procedure?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of Stryker recalls Mako RIO over loss of system power mid-procedure?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · no sources on file · last reviewed 2026-06-27

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-06-27

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for Stryker recalls Mako RIO over loss of system power mid-procedure.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.


Canonical ID 2c82347d-22ca-46f1-8cd8-c0a88d1db4fc