Sunbeam 053891134019Recalls & reported problems
Jarden Consumer Solutions · Heating Pad · Class 2
Data updated Oct 18, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 5
- Deaths reported
- 0
- Injuries reported
- 4
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 5 adverse event reports that list this exact device (DI 00053891134019), received between Mar 1, 2023 and May 29, 2026 — classified as 4 injuries, 1 malfunction.
The most frequently reported specific device problem is “Labelling, Instructions for Use or Training Problem” (5 reports).
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.
Reports received per month
Most reported problems
Device problems
- Labelling, Instructions for Use or Training Problem5
Patient problems
- Burn(s)4
- No Clinical Signs, Symptoms or Conditions1
Recent adverse event reports
The 5 most recent of 5 reports, in the reporter's own words as published by the FDA.
InjuryMay 29, 2026Labelling, Instructions for Use or Training Problem
AN ATTORNEY'S OFFICE IS FILING A LETTER NOTICE ALLEGING THAT A HEATING PAD WAS THE CAUSE OF A BURN TO ITS CLIENT'S RIGHT ABDOMEN. THERE WAS NOT A REPORT OF PROPERTY DAMAGE(S) WITH THIS INCIDENT.
Patient problems: Burn(s)
MAUDE report 25331362 ↗InjuryJan 19, 2024Labelling, Instructions for Use or Training Problem; Labelling, Instructions for Use or Training Problem
AN ATTORNEY'S OFFICE IS FILING A COURT SUMMONS NOTICE UNDER CASE REFERENCE NUMBER (B)(4)ALLEGING THAT A HEATING PAD WAS THE CAUSE OF A BURN TO ITS CLIENT'S BODY. THERE WAS NOT A REPORT OF PROPERTY DAMAGE(S) WITH THIS INCIDENT.
Patient problems: Burn(s)
MAUDE report 18541983 ↗InjuryMay 25, 2023Labelling, Instructions for Use or Training Problem; Labelling, Instructions for Use or Training Problem
CONSUMER ALLEGES SHE WAS USING HER HEATING PAD AND RECEIVED BURNS ON HER BUTTOCKS. THERE WAS NOT A REPORT OF PROPERTY DAMAGE WITH THIS INCIDENT.
Patient problems: Burn(s)
MAUDE report 17002331 ↗MalfunctionMar 28, 2023Labelling, Instructions for Use or Training Problem; Labelling, Instructions for Use or Training Problem
CONSUMER ALLEGES HER HEATING PAD CAUGHT ON FIRE WHILE USING ON HER COUCH AND CAUSED DAMAGE TO HER COUCH. THERE WAS NOT A REPORT OF PERSONAL INJURY WITH THIS INCIDENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 16626846 ↗InjuryMar 1, 2023Labelling, Instructions for Use or Training Problem; Labelling, Instructions for Use or Training Problem
CONSUMER ALLEGES SHE FELL ASLEEP USING THE HEATING PAD THEN AWOKE TO A BURN ON HER LEG. THERE WAS NOT A REPORT OF PROPERTY DAMAGE WITH THIS INCIDENT.
Patient problems: Burn(s)
MAUDE report 16460586 ↗
Other Pad, Heating, Powered devices
- HANDY SOLUTIONS HEATING PAD WRAP SHOULDER AND NECK 25607Navajo Manufacturing Company · Pad, Heating, Powered1 recall25 reports
- TearCare(TM) (2.2) System Kit FG 06041Sight Sciences, Inc. · Pad, Heating, Powered1 recall0 reports
- CHATTANOOGA 1032Djo, LLC · PAD, HEATING, POWERED6 reports
- DMI 619-5133-1900D-M-S Holdings, Inc. · Pad, Heating, Powered5 reports
- Sunbeam 053891133784Jarden Consumer Solutions · Pad, Heating, Powered5 reports
- Sunbeam 053891174015Jarden Consumer Solutions · Pad, Heating, Powered4 reports
- CONAIR HP15XFConair Corporation · Pad, Heating, Powered3 reports
- CHATTANOOGA 1033Djo, LLC · PAD, HEATING, POWERED3 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 18, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page