Appeal 3338046
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
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 new vehicular access and hardstanding to front to provide 2 off-street parking spaces.
Section 02
Decision
The appeal is dismissed.
Section 03
[name]
A revised version of the National Planning Policy Framework (the Framework) has been published since the planning application was determined by the Council. Both main parties have had the opportunity to comment on the relevant implications for the appeal. I have had regard to the revised Framework in reaching my decision.
The width of the drop kerb has been reduced during the course of the Council’s consideration of the planning application. In the interests of clarity, I have considered the proposal as amended.
Section 04
[name]
The main issues raised by this appeal are the effect of the proposed development upon the existing mature highway Ash tree and highway safety.
Section 05
Reasons
The proposal would be in close proximity to an existing mature highway Ash tree. Highway trees are an important local asset. This tree is an attractive feature within the street scene and is of high visual amenity value for this reason. This makes it all the more important to protect the Ash tree from harm to ensure its longevity is not undermined. The premature loss of this tree would have a negative and significant visual impact to the street scene.
To create the vehicular cross-over excavation would be required within the root protection area (RPA) of the Ash tree with a consequent risk of root damage. The Council’s Tree Officer indicates that this would be so despite the vehicle cross-over having been reduced in width. The appellant comments that the [name] indicates that with careful excavation works the tree root can be protected. However, from the information before me there is no clear indication that the Council’s Highway and Tree advisers have seen sight of this report. Therefore, this assertion holds little weight in favour of the proposal.
Given the size of the tree and the proximity of the proposed cross-over to it, there is a risk of direct harm to the tree roots from any digging required within the RPA. Due to the siting of the tree, it would be unlikely to survive the disturbance of construction. As such, its long-term protection would not be sufficiently secured. The proposed development, therefore, has a significant potential to negatively impact upon the tree and have a detrimental impact on its wellbeing in the long-term that could lead to pressure to remove the tree in the future.
Subsequent to the determination of the planning application the Council have placed a tree preservation order (TPO) upon the Ash tree. The TPO affords this tree protection. This makes it all the more important to protect the Ash tree from harm to ensure its longevity is not undermined. Loss of this tree would be an erosion of the statutory protection placed upon the tree by the serving of the TPO. As a consequence, the proposal should be resisted.
The trunk of the tree, given its proximity to the proposed cross-over, would be extremely likely to obstruct sight lines when vehicles exit the vehicular access. The applicant has stated that the Ash tree has been pruned recently and that there is no issue with visibility. However, I saw that the trunk of the tree is of some size and as such would obscure visibility of on-coming traffic. Therefore, safe visibility would not be guaranteed. As such, there would be an increased risk of accidents and increased danger to road users.
I have been provided a plan that shows potential sight lines from both the back of the pedestrian highway and the edge of the pedestrian kerb. It is suggested that the sight line from the kerb would achieve an acceptable level of visibility. However, the tree is sited within the pavement at the edge of the kerb. Visibility of on-coming traffic would be obstructed by the tree when traversing the pedestrian footway. The annotated sight lines do not overcome my highway safety concerns or justify the proposed development.
For these reasons, I conclude that the proposed development would have a harmful impact upon the existing mature highway Ash tree and highway safety. The proposal would, therefore conflict with Policy QD02 of the Thanet Local Plan and the provisions of the Framework. That policy seeks, amongst other matters, development to retain and protect existing features, including trees that positively contribute to the quality and character of an area and to provide safe and satisfactory access. The Framework states that trees make an important contribution to the character and quality of urban environments, and can also help mitigate and adapt to climate change and requires planning decisions to ensure places are safe, inclusive and accessible.
Section 06
Conclusion
Having regard to the above findings, the appeal should be 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 309No official casework-database value to compare
- Extracted decision date · page 1
- 4 July 2024Matches the official casework database
- Extracted site visit dates
- 21 June 2024 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3338046
- Application reference
- FH/TH/23/0706
- Lead case reference
- Not recorded
- Planning authority
- Thanet District Council
- Planning authority code
- E07000114
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
- Unknown
- 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
- 2 February 2024
- Valid date
- 2 February 2024
- Start date
- 18 March 2024
- Planning authority decision date
- 13 November 2023
- Appeal decision date
- 4 July 2024
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
- 53460
- First seen
- 20 August 2026 at 14:24
- Last seen
- 20 August 2026 at 16:27
- Removed from release
- Not recorded
- Record created
- 20 August 2026 at 14:24
- Record updated
- 24 August 2026 at 16:21