Z-0474-2011

Medtronic Sprint Quattro Secure S, model 6935. Steroid eluting, tripolar, screw-in, ventricular lead with RV...

Name: Z-0474-2011 Medtronic Sprint Quattro Secure S, model 6935. Steroid eluting, tripolar, screw-in, ventricular lead with RV...
Creator: Medtronic Inc. Cardiac Rhythm Disease Managment
Published: 2010-10-25
License: https://open.fda.gov/license/

Medtronic, Inc. / initiated 2010-10-25 / Terminated / root cause: design

FDA source

Medtronic Inc. Cardiac Rhythm Disease Managment began a recall of Medtronic Sprint Quattro Secure S, model 6935. Steroid eluting, tripolar, screw-in, ventricular lead with RV defibrillation coil electrode. Contents Sterile... on 2010-10-25. The reason FDA records is "Over--retraction of the helix during initial implant or subsequent repositioning may result in the inability to extend the helix. This does not impact acute or chronic performance of successfully implanted leads". As of 2026-09-10, the recall status on record is Terminated, and MDM tags the root cause as design.

Recall record

Recall number: Z-0474-2011
Status: Terminated
Initiated: 2010-10-25
Posted: 2010-11-26
Terminated: 2012-02-04
Recalling firm: Medtronic, Inc.
Product: Medtronic Sprint Quattro Secure S, model 6935. Steroid eluting, tripolar, screw-in, ventricular lead with RV defibrillation coil electrode. Contents Sterile. Manufactured in: Villalba, Puerto Rico, USA. Medtronic, Inc., Minneapolis, MN 55432 U.S.A.
Product code: LWS Implantable Cardioverter Defibrillator (Non-Crt)
Reason for recall: Over--retraction of the helix during initial implant or subsequent repositioning may result in the inability to extend the helix. This does not impact acute or chronic performance of successfully implanted leads.
Root cause tag: design
FDA root cause: Device Design
Action: Medtronic issued an Important Medical Device Correction letter, dated October 2010, to doctors. The letter contains a Performance Note. The letter describes the issue and the performance note provides information on how to mitigate the issue through replacement with a new lead. Customers can contact Medtronic Technical Services at 800 723-4636
Quantity in commerce: 154,000 total
Distribution: Worldwide Distribution: Throughout the US, including Guam, Puerto Rico, and US Virgin Islands, and to the countries of: Algeria, Argentina, Armenia, Australia, Austria, Bahamas, Bangladesh, Barbados, Belgium, Bolivia, Bosnia And Herzegovina, Brazil, Brunei Darussalam, Bulgaria, Canada, Chile, China, Colombia, Costa Rica, Croatia, Cyprus, Czech Republic, Denmark, Dominican Republic, Ecuador, El Salvador, Finland, France, Georgia, Germany, Greece, Guatemala, Honduras, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kazakhstan, Kenya, Korea, Kuwait, Latvia, Lebanon, Libya, Lithuania, Luxembourg, Malaysia, Malta, Martinique, Mexico, Morocco, Netherlands, New Zealand, Norway, Oman, Pakistan, Panama, Paraguay, Peru, Philippines, Poland, Portugal, Qatar, Romania, Saint Lucia, Saudi Arabia, Serbia, Singapore, Slovakia, Slovenia, South Africa, Spain, Sri Lanka, Sweden, Switzerland, Syria, Taiwan, Thailand, Trinidad and Tobago, Tunisia, Turkey, Ukraine, United Arab Emirates, United Kingdom, Uruguay, Venezuela, and Viet Nam.
Product codes and lots: all devices are affected, however, it is an issue that can present itself only at the time of the surgical procedure (acute issue) and it doesn't affect teh chronic performance of a successfully implanted lead.

Product code LWS

The FDA recall record names no cleared device, and no clearance has been matched to it.

MDM coverage of this record lists here, newest first.

About this record

Sourced from the FDA device recall database and the FDA enforcement reports, both ingested from openFDA. The recall record supplies the product, the reason and the product code; the enforcement report supplies the classification. The two datasets are exported by FDA on different days, and the date above is the older of the two, so nothing on this page is newer than it says.

MDM adds the root cause tag, derived from FDA’s own root cause text, and the cross-links to the product code, the clearances named on the record and MDM coverage. Where a recall has not been joined to an enforcement report, no classification is shown.

Data as of 2026-10-07, the FDA export date for this dataset. Page last changed 2026-09-05. View this recall on fda.gov (opens on fda.gov)