Skip to main content
Official casework recordDismissedCurrent release

Appeal 3367651

Public case and site metadata stored from the official casework database, including fields that were empty in the source release.

A clearer next step

See how Inspectors approached issues like yours

Bring your planning decision into a private workspace. We separate the disputed points, then match them with source-located Inspector reasoning from similar appeals.

  • See which issues the decision appears to turn on
  • Compare the facts and open the full appeal records

One private comparison

How the refusal review works

One-off service · No subscription

Similar appeals are evidence to inspect, not a prediction of your outcome.

Official decision document

The decision, section by section

6 sections

Read the development description and the Inspector’s text from the official decision PDF in source order. Source headings are retained where available. Personal and contact details are removed by an automated privacy filter; this is source material, not Rules for You analysis.

Section 01

Development description

a single storey side extension, conversion of garage into habitable room, and single storey rear extension with a raised rear patio.

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    Preliminary Matters

    The application form description of development cites “the conversion of garage and single storey side and rear extension.” The decision notice description provides more clarity including reference to the raised rear patio, so I have used that as the description in the banner above.

  3. Section 04

    Main Issue

    The main issue is the effect of the proposed development on flood risk.

  4. Section 05

    Reasons

    The appeal proposal is for single storey extensions and raised rear patio to the semi-detached dwelling at [site address] . There are no interested party objections, and the Council has raised no issue with the proposal’s visual appearance. Given its modest size and scale overall in comparison to its host, and the lack of any terracing effect, I see no reason to conclude differently.

    Residential buildings are categorised as a ‘more vulnerable’ use. The site lies within flood zones 2 and 3, with a 1 in 100 +17% climate change fluvial flood risk, and a medium to low risk of surface water flooding. The proposal’s total proposed impermeable area would be 32.6sqm, such that the Council’s Sustainable Drainage Proforma identifies a target attenuation of 4.17 cubic metres, and a minimum required attenuation of 1.47 cubic metres.

    The National Planning Policy Framework ('the Framework') (2024) paragraph 170 requires development which is necessary in areas at highest risk of flooding to be made safe for its lifetime without increasing flood risk elsewhere. Paragraph 181 states that applications should ensure that flood risk is not increased elsewhere, and includes the criteria (c) that development should only be allowed in areas at risk of flooding where it can be demonstrated that it incorporates sustainable drainage systems, unless there is clear evidence that this would be inappropriate. Paragraph 182 also reiterates the need to incorporate proportionate sustainable drainage systems to control flow rates and reduce runoff volumes.

    Policies DMD59 and DMD60 of the Enfield Development Management Document (DMD) similarly require new development to avoid and reduce the risk of flooding, not increase the risks elsewhere, and provide a sustainable drainage strategy and management of surface water. Policy DMD61 requires all developments to follow the drainage hierarchy in the London Plan, and demonstrate how proposed measures manage surface water as close to its source as possible. The appeal development must maximise the use of [name] (SuDS), including at least one 'at source' SuDS measure resulting in a net improvement in water quantity or quality discharging to sewers, with clear ownership, management, and maintenance arrangements. The Enfield Core Strategy 2010- 2025 (CS) Policies CP21 and CP28, and the London Plan policies SI12 and SI13 incorporate similar water management requirements.

    The appellant’s [name] Assessment1 (FRA) identifies that in order to not increase flood risk, the site’s surface runoff would be improved by implementing SuDS measures of 4 water butts to harvest a total of 4 cubic metres of rainwater. The landowners would be responsible for their maintenance and repair throughout the development’s lifetime.

    However, water butts are only intended to temporarily store rainwater. Despite reference to throttle attenuation, the proposal does not address where that water would then be directed. There is a distinct possibility that it would end in the mains drainage, including if the butts were subject to overflow such as if the occupiers were away for a period of time. There is no appropriate or reasonable control I could impose via planning conditions to guarantee how the site’s occupiers should use the water.

    As such, water butts would not therefore provide appropriate long-term flood risk attenuation in line with the above policy requirements for SuDS provision, unless connected to an overflow system leading to further SuDS features. The FRA identifies that the underlying soil conditions of clay and fine silt has very low permeability, but this does not outweigh the need to consider other options in detail. The proposal has identified no other elements of at source measures across the site, such as permeable paving, cellular crate systems, rain gardens, and/or green roofs. For these reasons, I therefore find that the proposed water butts would not provide sufficient runoff attenuation.

    The Council also objects because the development has not ensured safety from flooding, including equivalent retention or compensation of flood storage on site. Although capacity would remain under the proposed new decking, overall there would be less capacity than at present resulting from the additional massing of the new extensions. Flood storage has therefore not been sufficiently demonstrated.

    The Council also refers that the finished floor level must be at least 300mm above the 1 in 100 year (plus climate change) fluvial flood depth. However, the FRA highlights that the finished floor level complies with Environment Agency Standing Advice, whereby it can be set at existing levels if flood proofing has been incorporated. The proposal would incorporate various flood resistance and 1 [name] ref QFRA 2618 V1.0, 03/01/2025 resilience measures in its construction and finishes, including for water exclusion and entry. As an extension to an existing dwelling, I find this would be appropriate.

    The FRA also provides detailed information and a Flood Evacuation Plan for how the site’s occupants would be made aware of the flood risk, and flood warning and evacuation during an extreme event. The access route to a safe area is the same as at present, and the first floor of the existing dwelling would provide a safe haven if necessary if the evacuation route is under water.. Overall, I find these measures acceptable.

    Nonetheless, the development would not appropriately manage the risk of flooding, due to insufficient use of SuDS in not following the drainage hierarchy, and insufficient flood storage compensation. It would thus conflict with numerous development plan policies as outlined above; SI12 and SI13 of the London Plan; CP21 and CP28 of the CS; and DMD59, DMD60, and DMD61 of the DMD.

  5. Section 06

    Conclusion

    In conclusion, the proposed development would conflict with the development plan as a whole. With no other material considerations outweighing this conflict, for the reasons given above I conclude that the appeal is dismissed.

Planning inspector and document dates

The official casework attribution is grouped under a one-way keyed hash and shown only by its local identifier. Decision-letter dates and page references are extracted by fixed first-page rules and checked against that authoritative record.

  • Appeal Decision

    Extracted inspector · page 1
    Inspector attribution ID 5628No official casework-database value to compare
    Extracted decision date · page 1
    15 October 2025Matches the official casework database
    Extracted site visit dates
    15 September 2025 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3367651
Application reference
25/00347/HOU
Lead case reference
Not recorded
Planning authority
London Borough of Enfield
Planning authority code
E09000010

Casework details

The casework, procedure, development and linking details supplied by the official record.

Casework type
Householder (HAS)
Procedure
Written Representations
Development type
Householder developments
Appeal type reason
1. Refused planning permission
Appeal reason
Refusal
Type detail
Planning Appeals - Full
Jurisdiction
Transferred
Link status
Not Linked

Site and development

Published appeal-site measurements and planning designations, without the withheld precise location fields.

Site area
Not recorded
Floor space
Not recorded
Number of residences
0
Site in Green Belt
No
Agricultural holding
Not recorded
Affects setting of a listed building
Not recorded
Historic building grant made
Not recorded
Relates to a conservation area
Not recorded
Flooding is an issue
Not recorded
Site within an AONB
Not recorded
Site within an SSSI
Not recorded

Decision and dates

The published outcome and every imported case date.

Official decision
Dismissed
Decision category
Dismissed
Received date
14 June 2025
Valid date
25 June 2025
Start date
25 June 2025
Planning authority decision date
26 March 2025
Appeal decision date
15 October 2025

Case administration

Published recovery, call-in, costs and enforcement information for this case.

Redetermined
No
Bespoke
No
Date recovered
Not recorded
Date not recovered or derecovered
Not recorded
Call-in date
Not recorded
Costs applied for
Not recorded
Enforcement grounds count
Not recorded
Enforcement grounds
Not recorded

Source and catalogue history

When this record appeared in the rolling official release and when the catalogue stored it.

Source
Planning Inspectorate casework database
Source data system
Horizon
Dataset status
Current release
Catalogue record ID
77997
First seen
20 August 2026 at 14:25
Last seen
20 August 2026 at 16:29
Removed from release
Not recorded
Record created
20 August 2026 at 14:25
Record updated
24 August 2026 at 16:21