Sewerby Hall plans security fence after breach and unpaid access
Summarised from 2 outlets · Updated 31 Oct, 12:03 · Archive
Sewerby Hall and Gardens near Bridlington is planning to install metal palisade fencing after existing wire mesh was cut and removed.
East Riding of Yorkshire Council is planning to install metal palisade fencing at Sewerby Hall and Gardens near Bridlington after existing wire mesh was cut and removed from a site access road. The council said the works are necessary to address ongoing security concerns regarding unauthorised access to the hall. Infill panels will also be added to a gate linking the estate to nearby Bridlington Links Golf Course.
The Grade I-listed country house with 50 acres of parkland, award-winning gardens, zoo and clifftop views attracts more than 150,000 visitors a year. The site is popular with dog walkers and offers scenic views along the East Yorkshire coast. According to planning documents, gates on the access road were initially installed in response to an increase in visitors accessing the attraction without paying for admission, together with people being on the road without permission, particularly in the evenings.
How it is being reported
- 'Security breach' prompts plans for more 'robust deterrent' at Yorkshire attractionGrade I Sewerby Hall and Gardens could see improved security in part of the estate which has seen a recent 'security breach', according to planning documents.Gazette & Herald (Malton) · 31 Oct, 11:00
- Fence removal and 'security breach' prompt new security plan at Yorkshire attractionGrade I Sewerby Hall and Gardens could see improved security in part of the estate which has seen a recent 'security breach', according to planning documents.The Press (York) · 31 Oct, 07:45
In this story: Sewerby Hall and Gardens · Bridlington · East Riding of Yorkshire Council · Bridlington Links Golf Course
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)