Appeal 3310861
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
7 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
creation of new vehicular access to existing residential property and installation of a gate.
Section 02
Decision
The appeal is dismissed.
Section 03
[name]
The original description of the development was amended during the course of the application to include the installation of the gate.
The appellant submitted an Arboricultural Appeal Statement (the AAS). Although the appeal is being considered under the Part 1 procedure (as a Householder Appeal) in this case, in the interests of fairness and as provided for in the Regulations1, the Council was given the opportunity to comment. I have seen no response.
Section 04
Main Issue
The main issue is the effect of the proposal on the character and appearance of the area taking particular account of the effect on a lime tree and hedgerow.
Section 05
Reasons
The appeal property is a dwelling set back from [address]. Its access onto [address] is shared with [address] Farm. There is a ninety degrees offshoot from the shared access leading into the shingle surfaced parking area of [name]. This is retained by low timber sleeper walls and separated from the remainder of the access to [address] Farm by a beech hedge within a slightly raised bed. The bell mouth of the shared access is hard surfaced and the remainder is shingle.
The protected lime tree2, stands on the edge of the shared access between the offshoot and the carriageway. It is a mature and attractive individual specimen, one of several similar trees along [address]. As is typical for lime trees it has 1 Regulation 8 of the Town and Country Planning (Appeals) (Written Representations Procedure) (England) Regulations 2009 ([name] 2009/452) as amended 2 Tree Preservation Order TPO/1385 extensive shoots on the lower trunk. These have been trimmed back. The trunk bifurcates into two principal stems at around 3m; the condition of the main fork appears generally sound. The upper crown has re-established after previous reduction. Some deadwood is present but this is not untypical and the form and structure of the tree appear typical for the age and species.
The canopy of the lime tree extends over the [address] carriageway; the shared access; the shingled parking area; and the offshoot. Aside from a very restricted area around the base of the stem the only unsurfaced area beneath the canopy appears to be the grass verge.
The proposal would create an independent access across the grass verge at the front of the appeal site close to the lime tree. A gate would be set back 6m to allow vehicles to wait off the live carriageway. The Design and [name] identifies that the access would serve a 14 foot (4.3m) wide gate and the submitted gate detail also shows a short section of fence to either side. The submitted layout plan contains few stated dimensions but shows that most of the access would be as wide as/wider than the proposed gate/fences.
Paragraph 1.3.3 of the AAS states the proposed access would be around 3.5m wide. There would also be a 5m radii on the east corner. No detailed plans accompanied the AAS: reference is made to site notes, sketch plan and photographs but these do not appear to have been submitted with the appeal. Given the above apparent inconsistencies I cannot be confident that the extent of works in the root protection area (RPA), or the compaction effect that might occur from vehicle use, has been fully explored.
The intention is that the access would be constructed, as far as possible, above existing ground level using a Cellweb system to maintain the appearance of the existing grass verge, and to minimise excavations within the root RPA of the lime tree. However, no site specific cross sections showing the level of detail that might be expected when proposing works close to a protected tree have been provided. Moreover, the accuracy of the plan in relation to the tree was queried by the Highway Authority.
[name] cannot be confident that tree roots would not be compromised, whether or not kerb stones would be required, particularly given that I observed a substantial, partially exposed, tree root in the verge. In addition the proposed access would be in very close proximity to the stem of the tree in a part of the RPA likely to be most sensitive to works. Nor have I seen proposals for compensatory contiguous RPA or mitigation measures to improve the soil environment as envisaged by BS 5837.20123.
Most of the frontage of [name] has a post and rail fence on the verge side of which is a row of small beech hedge plants which appear to have been planted at the request of the Council. This adjoins a more established hedge on one side and the lime tree on the other. The proposals would require the removal of some hedgerow but the plans do not clearly show the extent of removal that would be required.
Although the hedge is of no special historic value it adds to the verdant character and appearance of the area. Its loss would open up views of the parking area which would be harmful to the local leafy rural character and 3 BS 5837:2012 Trees in relation to design, demolition and construction – Recommendations appearance. This could potentially be ameliorated to some extent by a replacement hedge. However, the plans do not show how this could be successfully accommodated.
On the basis of the evidence before me I cannot confidently conclude that the effect on the protected lime tree and the hedgerow, and consequently on the character and appearance of the area, would not be harmful. Accordingly the proposal would not amount to high quality design. There would be conflict with those principles of Policies 25, 32 and 33 of the Horsham District Planning Framework 2015 (the HDPF) and the National Planning Policy Framework that seek high quality design that protects and enhances local landscapes and natural features such as trees and hedges. Although not mentioned in the reasons for refusal there would also be conflict with the similar Policy 15 in the Storrington, Sullington & Washington Neighbourhood Plan 2019 (the NP).
Section 06
Other Matters
The Council refused permission for a similar access DC/09/0128 on highway safety grounds only. However, at that time it seems there were alternative access arrangements and there appears not to have been the existing offshoot. Accordingly the effect on the tree RPA of that access is likely to have been less than would be the case of the proposal before me. Moreover, the tree is now older and may respond less successfully to changes in conditions.
The proposed access would be more convenient for drivers than the existing awkward offshoot which, it appears, cannot be improved. It would minimise the waiting of vehicles turning into the shared drive when another vehicle was exiting. On the other hand, the proposed access would be in close proximity to the existing, which could cause some confusion for other users of the highway. These matters balance each other out. Despite concerns raised by third parties, the highway authority raises no objections on highway safety grounds. I find no compelling evidence that would lead me to a different conclusion.
[address] Farm is a Grade II Listed Building. There is intervisibility between the appeal site and [address] Farm, so the former is within the setting of the Listed Building. However, the proposed access and gate would be some distance from the Listed Building and the proposal would have a neutral effect on the setting in which its historic architectural merit is appreciated.
The proposed access in itself would not alter the water requirements of the appeal site and there is no compelling indication that it would lead to a more intensive occupation of the dwelling necessitating an increased consumption of water. In any event given my conclusion on the main issue I do not need to further consider the effect on the Arun Valley Special Area of Conservation, Special Protection Area and Ramsar sites.
Section 07
Conclusion
The default position of BS 5837.[address] outside RPAs although it is recognised that, where there is an overriding justification for construction within the RPA, technical solutions might be available that prevent damage to the tree. For the reasons set out above I cannot be confident that the technical solution proposed would prevent damage to the tree. Moreover, I conclude that the benefits of more convenient access for the appellant would not constitute an overriding justification for works in the affected part of the RPA.
I conclude the benefits of an independent access would not outweigh the harm to the tree and to the character and appearance of the area. In failing to fully comply with Policies 25, 32 and 33 of the HDPF and Policy 15 of the NP the proposal cannot be said to comply with the development plan as a whole. I find insufficient material considerations to justify a decision other than in accordance with the development plan. 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 508No official casework-database value to compare
- Extracted decision date · page 1
- 21 March 2023Matches the official casework database
- Extracted site visit dates
- 27 February 2023 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3310861
- Application reference
- DC/22/0519
- Lead case reference
- Not recorded
- Planning authority
- Horsham District Council
- Planning authority code
- E07000227
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
- 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
- 10 November 2022
- Valid date
- 10 November 2022
- Start date
- 26 January 2023
- Planning authority decision date
- 31 August 2022
- Appeal decision date
- 21 March 2023
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
- 29996
- 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