Out-Law / Your Daily Need-To-Know

Out-Law News 1 min. read

Lend Lease submits first phase of £1.5bn Elephant and Castle scheme


Developer Lend Lease has submitted a detailed planning application to Southwark Council for 360 homes as the first phase of its major regeneration of the Heygate Estate in London's Elephant and Castle.

Southwark Council approved the Heygate masterplan, which sets out plans for 2,500 to be built over the next 15 years, earlier this year. The first phase of the scheme proposes the construction of 360 homes along the south eastern part of the estate, including a 16-storey tower.

Lend Lease's project director for Elephant and Castle Pascal Mittermaier said in a statement that the application was "another major step" in the ongoing transformation of the area. “The homes that replace the Heygate Estate will be some of the most sustainable and energy efficient places to live in Britain and we look forward to working in partnership with Southwark council to deliver them,” he said.

Lend Lease has already launched two other housing schemes in Elephant and Castle where work has started on the sites. These include One The Elephant, a 37-storey tower to comprise 284 new homes, and Trafalgar Place, a 235-home development.

"The pace of change at the Elephant is remarkable," said the Council's cabinet member for regeneration Fiona Colley. "As new homes at Trafalgar Place and One the Elephant rapidly come out of the earth and the Leisure Centre begins to take shape, I am delighted that a planning application for the next phase has already been submitted. The 360 new homes, if granted permission, will include 25 per cent affordable housing and be a mix of attractive town houses and flats that will complete Wansey Street and complement the existing homes."

The Council is expected to make a decision on the application early next year and construction on the new homes is expected to start in the autumn next year.

We are processing your request. \n Thank you for your patience. An error occurred. This could be due to inactivity on the page - please try again.