Tumble dryer left running overnight sparked house fire
Summarised from 2 outlets · Updated 18 Nov, 13:32 · Archive
A tumble dryer left running overnight caused a house fire in Ashington, south of Horsham, on 28 October.
A house fire in Ashington, south of Horsham, was caused by a tumble dryer left running overnight. The blaze broke out in the early hours of 28 October at a property in The Sands, where a washing machine and tumble dryer had both been left on. Five fire engines tackled the fire at its height, and all occupants were evacuated safely.
Nathan Cross, head of prevention at West Sussex Fire & Rescue Service, warned against running household appliances overnight or when nobody is at home. 'If a fire starts while you are asleep or away from the property, you have less time to react and get out safely,' he said.
The fire service advised regular maintenance and cleaning of appliances, particularly tumble dryer lint filters. It also recommended registering appliances on the Register My Appliance website to stay informed about product safety recalls, avoiding overloaded sockets, using surge-protected extension leads, and ensuring working smoke alarms are fitted and tested regularly. For appliances kept in outbuildings, the service suggested installing linked smoke alarm systems to provide quick alerts if a fire occurs.

How it is being reported
- Tumble dryer caused fire at home in West Sussex villageA tumble dyer, left running overnight, caused a significant house fire in Ashington.Chichester Observer · 18 Nov, 12:45
- House fire sparked by tumble dryer left running overnightThe blaze, which broke out at a property in Ashington, south of Horsham, in the early hours of October 28, was tackled by five fire engines at its height.The Argus · 18 Nov, 11:33
In this story: Ashington · Horsham · West Sussex Fire & Rescue Service · Nathan Cross · The Sands
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)