Riverside café owner seeks retrospective planning permission
Summarised from 2 outlets · Updated 19 Oct, 18:32 · Archive
The owner of a popular riverside café near Richmond has applied for retrospective planning permission after North Yorkshire Council ruled it was needed.
Nic Perks, who runs The Easby Loop Cafe close to Easby Abbey near Richmond, has submitted an application to North Yorkshire Council for retrospective planning permission after being told the café requires it. The café opened in June 2025 and has become a popular stopping point for walkers and visitors using the scenic route between Richmond and Easby Abbey.
The application has received support from local organisations. Richmondshire Ramblers' footpath officer Mike Richardson said the café is popular with public footpath users and that the application is supported. Richmond Civic Society also backed the proposals, though expressed disappointment that permission was not sought before opening. The society stated the café is extremely popular with locals and does not negatively impact the environment of Easby Abbey as it is discreetly placed.
The application seeks permission for a transportable metal trailer measuring 3.9 metres long, which serves hot and cold drinks and food.
How it is being reported
- Popular riverside café told it needs planning permissionEasby Loop Cafe close to Easby Abbey, near Richmond, has been told to apply for retrospective planning permission by North Yorkshire Council.Darlington & Stockton Times · 19 Oct, 18:00
- Popular riverside café backed by groups after being told it needs planning permissionA popular riverside café has received backing from local organisations after its owner was told to apply for retrospective planning permission.The Northern Echo · 19 Oct, 17:30
In this story: Nic Perks · North Yorkshire Council · Richmondshire Ramblers · Richmond Civic Society · Easby Abbey · Richmond
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
Comments (0)