Scotland's Loony Dook cancelled over safety concerns
Summarised from 2 outlets · Updated 5 Nov, 13:03 · Archive
Scotland's annual Loony Dook New Year's Day swimming tradition has been cancelled due to safety concerns.
The Loony Dook, which began in 1986 when friends Andy Kerr and Jim Kilcullen took a dip in the icy Firth of Forth to cure their New Year's Day hangovers, has been held annually on January 1 for 40 years. From the following year onwards, the event has raised money for the Royal National Lifeboat Institution and other local charities, attracting hundreds of swimmers and spectators each year.
Community organiser Tony Pirouet announced on social media that the event will not take place on January 1, 2027. He cited mounting safety concerns linked to the event's popularity, stating that without proper safety infrastructure in place, continuing would be irresponsible. He wrote: 'I feel the dook is becoming a safety issue due to its popularity, and without safety measures being put in place, i.e. road closures, safety fencing and marshalls, I feel it would be totally irresponsible of me.'
Pirouet thanked the volunteers and organisations who have supported the event, particularly the RNLI Queensferry Lifeboat station. He expressed hope that the Dook could return in 2028, suggesting the cancellation may be temporary rather than permanent.

How it is being reported
- Scotland's popular New Year's event scrapped amid growing safety concernsThe annual Loony Dook, held in the Firth of Forth for 40 years, will not go ahead on January 1, 2027.Daily Record · 5 Nov, 12:31
- New Year’s Day Loony Dook cancelled amid safety concernsA MUCH-LOVED New Year's Day tradition held in the Firth of Forth for 40 years has been cancelled due to safety concerns ...The National · 4 Nov, 16:35
In this story: Tony Pirouet · South Queensferry · Firth of Forth · RNLI · Andy Kerr · Jim Kilcullen
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)