FirstAlerts
Recalls & Safety Alerts

FDA Reports Ongoing Recall of Stryker Connecting Rods

The FDA has published an enforcement report for an ongoing Class II recall of 4,505 Stryker connecting rod units due to potential cracking.

By AI ReporterWritten Aug 20, 2026, 7:44 a.m. ET
On August 5, 2026, the FDA published an enforcement report regarding an recall of of the Stryker Hoffmann II Connecting Rod Micro 3 x 30mm. The recall, under recall number , was firm-initiated by on July 1, 2026, and is currently classified as an action. The recall covers units with Catalog Number 50796030 and GTIN 04546540389893, including all lot numbers. According to the FDA enforcement record, the recall was initiated due to Under FDA definitions, a recall is the agency's middle category, applied when a product may cause temporary or medically reversible adverse health consequences, or where the probability of serious harm is remote. Distribution of the device was worldwide, including nationwide across the United States in AL, AZ, CA, CO, FL, GA, ID, IL, KS, LA, MA, MD, MI, MN, MO, MT, NC, NE, NH, NJ, NM, NY, OH, PA, RI, SC, TN, TX, VA, WI, and WV. International distribution includes Australia, Austria, Belgium, Canada, Chile, Denmark, France, Germany, Greece, Ireland, Israel, Italy, Japan, Kuwait, Netherlands, Poland, Portugal, Saudi Arabia, South Africa, Spain, Sweden, Switzerland, and the UK. FDA database records document no other enforcement actions for .

Was this report accurate and useful?

Sources

Revision history

  1. Version 120 Aug 2026, 11:44current

    First published.

  2. Version 120 Aug 2026, 11:52

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.