MULTI-million-pound housing plans have been unveiled for a former pub site in York city centre.
Northminster Ltd intends to to build eight homes - two of three or four bedrooms in the building in Walmgate that once housed the Lord Nelson Inn, and six on unused land behind it.
The firm says its plans could be a “catalyst for regeneration” in the area. A planning application is due to be submitted to City of York Council in the coming weeks.
The plan being drawn up by the owners of Northminster Business Park includes a private courtyard for the houses.
Northminster is currently finalising the proposals after acquiring the third-of-an-acre site last autumn, when it was put up for sale with an asking price of £1 million.
The houses will have panoramic views over the city centre and will include roof-mounted solar-thermal heating, private parking and gardens.
Each of the new homes, designed for the developer by COG Architecture, will meet the latest sustainability requirements and the top energy performance certificate rating.
Northminster Ltd’s development surveyor, Alastair Gill, said: “This is a run-down site which will benefit from an attractive, high-quality housing scheme at a time when the region needs more homes.
“As well as being sustainable from a design and construction perspective, the homes will be close to city centre amenities, reducing dependence on transport.
“The scheme is designed to appeal to families who want to live and work in the city centre or people downsizing from nearby villages who want to embrace city living.”
Robin Parker, of COG Architecture, said: “The new homes are intended to be adaptable, multi-use family houses providing generous accommodation in a tight urban location and we hope that, if approved, they will act as a catalyst for the regeneration of this area.”
If City of York planners back the scheme, construction work should start in the summer and the homes will be ready by spring next year.
This article initially said ten homes were planned, however the correct total is eight. The error was contained in the information provided on behalf of the developer, however we are happy to now clarify this matter.