Skip to main content
Official casework recordDismissedCurrent release

Appeal 3300118

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

5 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

the excavation and construction of new basement level.

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    [name]

    The main issue in this case is the effect of the proposal on the appearance and life expectancy of protected trees within and adjacent to the site.

  3. Section 04

    Reasons

    The proposed substantial extension and sunken courtyard area would extend beyond the existing footprint of the house to within the Root Protection Area (RPA) of 2 trees protected by a TPO, which are identified in the submitted Arboricultural Impact Assessment (AIA) as T9 (cedar) and T10 (oak). These two trees, as recognised by their TPO status, contribute significantly to the verdant character of the area.

    The AIA and plans illustrate that the development would only slightly extend into the RPA of T9, a [name] tree sited near the rear boundary of the property. Whilst the reason for refusal only refers to T10, the Council raise concern that the development would also impact T9, however given the limited incursion into the RPA of this tree, the majority of which the appellant’s appeal statement sets out would be external paving with planters, I am satisfied that the impact upon this tree would be acceptable.

    However, the AIA sets out that 18% of the RPA of T10, a substantial oak tree located on the neighbouring side of the side boundary, will be affected by the basement development. The plans show that there are existing pile foundations within the RPA of this tree.

    Given the topography of the site, this tree is sited on a lower level than the ground floor level of the appeal property. Nevertheless, the AIA identifies that the proposal requires an excavation to a maximum depth of 826mm, with the deeper swimming pool area sited centrally within the plot some distance away from the tree. The majority of roots are in the top 600mm of soil and therefore this is an area of concern with regard to potential damage caused by cutting of these roots, particularly given that a precautionary approach should normally be adopted in such circumstances, in accordance with the advice contained within BS5837:2012.

    The AIA suggests that this would be mitigated by constructing on piles with a beam supporting the ground floor above the existing ground level within the trees RPA, with the above ground work implemented under the supervision of an Arboricultural specialist. There is a disagreement between the parties regarding the effectiveness of these measures. [name] note that BS5837 indicates it is acceptable to undertake certain work within an RPA, such as hand digging, thrust boring, pile foundations and radial trenching, it sets out that the default position should be that such works should be avoided wherever possible and generally require overriding justification.

    I share the Council’s concern that, given the amount of RPA affected and the excavation depth, there is no overriding justification for these works, which would provide a small area of the overall substantial basement space. Given the proximity of the development to this tree, and the existing works within its RPA, I am also aware of potential future pressure, with potential damage being sustained through root spread.

    Given these reservations and on the basis of the evidence before me I consider that the proposed excavations would be likely to significantly damage the roots of T10 and seriously compromise its long-term health. [name] accept that the works may not directly result in the loss of the tree, harm to its health will undoubtedly detract from its amenity value.

    Whilst there is a further disagreement regarding the consistency of the drawings, I consider that the plans are sufficiently clear to have based my decision on the plans in front of me and my site visit.

    I therefore conclude that the proposal would be contrary to Policy DM10 of the [name] (2012), which expects new development to ensure that trees that are important to the character of the area or covered by Tree Preservation Orders (TPOs) are not adversely affected, and Policy G7 of the London Plan (2021) which states that development proposals should ensure that, wherever possible, existing trees of value are retained.

  4. Section 05

    Conclusion

    For the reasons given above, having regard to the development plan as a whole and all other material considerations, 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 3478No official casework-database value to compare
    Extracted decision date · page 1
    30 November 2022Matches the official casework database
    Extracted site visit dates
    31 October 2022 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3300118
Application reference
21/04104/HOU
Lead case reference
Not recorded
Planning authority
Royal Borough of Kingston Upon Thames
Planning authority code
E09000021

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
411 m²
Number of residences
0
Site in Green Belt
No
Agricultural holding
No
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
30 May 2022
Valid date
22 June 2022
Start date
28 June 2022
Planning authority decision date
22 April 2022
Appeal decision date
30 November 2022

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
24346
First seen
20 August 2026 at 14:24
Last seen
20 August 2026 at 16:26
Removed from release
Not recorded
Record created
20 August 2026 at 14:24
Record updated
24 August 2026 at 16:21