Core Refusal Reason
The proposed development is considered out of scale, proportion, and character with the existing built form on Montpelier Lane, leading to significant overbearance and overlooking that would seriously injure the residential and visual amenities of the area and the Monkstown Architectural Conservation Area.
Decision Maker's Conclusion
- The proposed mews dwelling's scale and form are inconsistent with the established and recently permitted pattern of development on Montpelier Lane.
- The design changes at the Further Information stage resulted in an unacceptable increase in the structure's overall bulk and massing, causing significant overbearance on the adjacent property at No. 13 Shandon Park.
- The proposal fails to comply with Policy Objective PHP22, which requires mews housing to be measured, proportionate, and respectful of the existing built form and heritage of the area.
Cited Policies (CDP)
Section 12.3.7.9 (Mews Lane Development)Section 4.3.1.5 (Policy Objective PHP22: Mews Lane Housing)Section 12.8.3.3 (Private Open Space)Section 11.4.2.1 (Policy Objective HER13: Architectural Conservation Areas)Section 11.4.2.2 (Policy Objective HER14: Demolition within an ACA)Section 4.3.1.3 (Policy Objective PHP20: Protection of Existing Residential Amenity)Section 12.4.8.4 (ACAs/Protected Structures)
Decision Document Summary
This report pertains to a first-party appeal against the refusal of permission for a 3-storey mews dwelling (87.9 sq.m) at Montpelier Lane, Blackrock, a gated laneway within the Monkstown ACA. The proposal involves demolishing a 30 sq.m single-storey home office to facilitate the new structure. While the Inspector noted that the principle of 3-storey dwellings is increasingly established on the lane due to recent planning precedents, this specific proposal was found to be problematic. The Inspec...SOURCE PDFOpen Original
Note: If code appears below, the council site is blocking the preview. Please open the original file.
PDF Document Missing
The original decision document for this case could not be linked. This often happens for older cases or those with restricted documentation.
Search for case on ABP