Appeal 6000290
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 worksOne-off service · No subscription
Similar appeals are evidence to inspect, not a prediction of your outcome.
Official decision document
The decision, section by section
11 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
dropped kerb with minor front boundary details.
Section 02
Decision
The appeal is dismissed.
Section 03
Appeal Procedure
The site visit was undertaken by a representative of the Inspector whose recommendation is set out below and to which the Inspector has had regard before deciding the appeal.
Section 04
Preliminary Matters
Prior to the consideration of this appeal, the Council adopted the Richmond Upon Thames Local Plan 2024-2039 (2025) (LP). The main parties were aware of the emerging policies at the time of the Council's decision, and they have not materially changed to the adopted versions. The LP has replaced the London Borough of Richmond Upon Thames Local Plan (2018), and I have considered the appeal having regards to the most up to date development plan.
Section 05
Main Issue
The main issue if the effect of the proposed development on trees and highway-safety.
Section 06
Reasons for the Recommendation
The appeal site is a semi-detached dwelling located on a residential street. It is set back from the highway beyond a shallow drive, which is bound on one side by hedging and to the other by shrubbery and trees. The verdant nature of the appeal site compliments the surrounding street scene, as low level shrubbery and hedging is a typical example of boundary treatment and there are a number of trees of varying size and maturity both in gardens and lining the highway.
[address] is a classified road with a 20mph speed limit; this has been reduced from 30mph between the Council’s decision and my site. There are traffic calming measures in place along the road including speed bumps and chicanes, both of which can be found in the immediate vicinity of the appeal site. [address] is also within a [name] (CPZ), with a CPZ space located outside the property boundary.
Section 07
[name]
The forecourt of the appeal dwelling is not large enough to support a turning area of 8.0mx10.0m as required by the guidance within the Richmond Borough Council Transport Supplementary Planning Document (2020) (SPD) meaning that there is insufficient space for a vehicle to both enter and exit the parking area in a forward gear. The proposed development would require the vehicle to either enter or exit the appeal site in a reverse gear, thereby increasing the risk of creating a road safety hazard.
This risk would be exacerbated by the presence of an on-street parking space outside the appeal site and abutting the edge of the proposed dropped kerb. There are further on-street parking spaces lining both sides of [address] and at the time of my site visit I observed that many of them were in use. Whilst the road is straight and free of significant bends, the parking space immediately adjacent to the proposed dropped kerb already affects the visibility of pedestrians using the footway and crossing the road, together with vehicles using [address]. Because a vehicle entering No 39 using the proposed dropped kerb would need to reverse in or out, those movements would take place with limited visibility and add to the existing situation.
Furthermore, visibility splays have not been provided as part of this proposal and therefore I cannot determine whether the proposal satisfies this requirement within the SPD for visibility splays of 2.1mx2.4m for off-street parking. These dimensions are required to ensure that residents can control the height of any vegetation and ensure that pedestrians, especially small children, can been approaching on the footway. [name] note that there is a school nearby, and with a lack of evidence to the contrary, I consider that this would exacerbate the harmful effect I have already found.
There are a number of dropped kerbs already on [address]. However, I do not have the benefit of any details to understand the material circumstances under which these examples were installed, and thus I do not know whether or not these existing examples benefit from the visibility splays of 2.1mx2.4m as required by the SPD.
The appellant has stated that there is no record of safety incidents arising from the existing dropped kerbs. However, the absence of safety incidents to date does not automatically remove the risk to highway safety. This does not therefore override the harm I have found above.
The Council have raised concerns regarding the choice of material for the proposal; it is proposed to use concrete rather than pavement slabs which would complement the existing footpath. I am satisfied that if the proposal were to be found otherwise acceptable, that this could be conditioned satisfactorily and thus be found to have an acceptable effect on the appearance of the street scene.
Overall, the proposed development would have an unacceptable effect on highway safety contrary to Policy 48 of the LP which require all development to maintain the quality and safety of Richmond’s footways for pedestrians and vulnerable road users. It would further lack compliance with the SPD regarding entering and exiting the highway.
Section 08
Trees
The proposed development would introduce a low boundary wall to the right-hand side of the existing driveway abutting the highway. Policy 42 of the LP requires the protection of all existing trees, and not just those which have Tree Preservation Orders (TPO’s). Furthermore, the policy resists the removal of any tree that is not dead, dying, dangerous or that it is causing significant damage to adjacent structures; whilst I do not have the benefit of an arboricultural assessment, there is no evidence before me to suggest that this is the case. The extant tree currently contributes positively to the pleasant verdant character of the area and therefore its retention would be a desirable outcome.
The proposed works would take place within the Root Protection Area (RPA) of the extant tree and therefore they would have the potential to harm the trees long-term health and longevity. However, a suitable worded condition requiring the work to be undertaken by hand digging within the RPA and bridging over roots if they are encountered could satisfactorily alleviate this concern and mitigate any harmful effect on the street scene.
Therefore, the proposed development would not have a harmful effect on trees and would thus comply with Policy 28 and 42 of the LP, which requires all development to minimise impacts on existing trees and other significant vegetation, and to integrate new existing natural features.
Section 09
Other Matters
The appellant has suggested that the proposed development would facilitate the installation of an electric vehicle charging point. However, this proposed installation does not form a part of the scheme before me.
Section 10
Conclusion and Recommendation
[name] have found that the proposed development would not have a harmful effect on the tree within the appeal site, this does not outweigh the harm that I have found to highway safety. As such, the proposal conflicts with the development plan and the material considerations do not indicate that the appeal should be decided other than in accordance with it.
For the reasons given above and having had regard to all other matters raised, I recommend that the appeal should be dismissed.
Section 11
Inspector’s Decision
I have considered all the submitted evidence and my representative’s report and on that basis 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 245No official casework-database value to compare
- Extracted decision date · page 1
- 12 January 2026Matches the official casework database
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 6000290
- Application reference
- 24/3115/HOT
- Lead case reference
- Not recorded
- Planning authority
- Richmond Upon Thames London Borough Council
- Planning authority code
- E09000027
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
- Not recorded
- Appeal reason
- refused
- Type detail
- Householder
- Jurisdiction
- No Jurisdiction Associated
- Link status
- Not recorded
Site and development
Published appeal-site measurements and planning designations, without the withheld precise location fields.
- Site area
- 0 hectares
- Floor space
- 326 m²
- Number of residences
- Not recorded
- Site in Green Belt
- No
- Agricultural holding
- Not recorded
- Affects setting of a listed building
- Yes
- 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
- 27 May 2025
- Valid date
- 27 May 2025
- Start date
- 28 May 2025
- Planning authority decision date
- 14 March 2025
- Appeal decision date
- 12 January 2026
Case administration
Published recovery, call-in, costs and enforcement information for this case.
- Redetermined
- Not recorded
- Bespoke
- Not recorded
- Date recovered
- Not recorded
- Date not recovered or derecovered
- Not recorded
- Call-in date
- Not recorded
- Costs applied for
- No
- 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
- Back Office
- Dataset status
- Current release
- Catalogue record ID
- 82631
- 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