Frigidaire LAD 504TDL

SaferProducts.gov consumer incident report 20150812-98201-2147429417. Severity: Unspecified. Matched catalog product: Frigidaire LAD 504TDL. Source model text: LAD504TDL. Incident: The frigidaire dehumidifier tripped the GFI. When I attempted to reset and plug it back in the GFI tripped again and I could smell the dehumidifier burning.

SaferProducts.gov consumer incident report 20190725-91D88-2147379684. Severity: Incident, No Injury. Matched catalog product: Frigidaire LAD 504TDL. Source model text: LAD504TDL. Incident: We are a municipal fire department. We encountered a structure fire (private home) this past month that our fire investigators have determined was caused by a defective dehumidifier. The unit became completely involved in fire and spread to other items in the structure. The unit in question was a Frigidaire. model # LAD504TDL. Ser. # KN95304808.

SaferProducts.gov consumer incident report 20220321-68E49-3637579. Severity: Incident, No Injury. Product: Frigidaire LAD 504TDL (dehumidifier). Incident: 3/20/2022: The dehumidifier was in use (length of time unknown), when the consumer noticed the unit was on fire internally and emitting smoke. She consumer quickly unplugged it and took it outside. Once outside, the flames died out on their own. There is no visible exterior damage to the outside of the dehumidifier itself and there was no property damage to the consumer�s home. The consumer did not use the water bucket for the dehumidifier. It had tubing, which allowed water to go from the dehumidifier to a pipe in her basement. So that is where the water from the dehumidifier drained directly into. The dehumidifier model matched one of the recalled numbers (CPSC Release #[REDACTED]), but the serial number did not appear to be included. Model # LAD504TDL Serial #KN01801706 The consumer said she contacted a company and they asked for pictures, but she hadn�t submitted them at the time she filed a report with CPSC. The dehumidifier caught on fire 18MAR22. Calls were made regarding the incident 19MAR22.