Skip to main content
Official casework recordDismissedCurrent release

Appeal 3339121

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

formation of vehicular access following removal of garden wall.

  1. Section 02

    Decision

    The appeal is dismissed.

  2. 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.

  3. Section 04

    [name]

    The main issues raised by this appeal are the effect of the proposed development on pedestrian and highway safety.

  4. Section 05

    Reasons

    The Council advises that Kent County Council Highways Safety Guidelines ([name]: Interim Guidance Note 3 – [name] (IGN3)) sets out standards for off street parking. The parking area should be at least 4.8m long between the back of the pavement or property boundary and the front of the building. Alternatively, at least 6m length is required where a parking area is in front of a garage or door where adequate means of escape needs to be provided, like a front or back door. To my mind this sets out appropriate criteria to ensure parking meets acceptable highway safety standards and that driveways have enough room for users to park a vehicle completely on the property.

    The Council have calculated the length of the parking space to be approximately 4.79m between the back of the pavement and the front building line of the dwelling, although I note the calculation provided by the appellant indicates this to be approximately 4.88m. The dwelling hosts a projecting entrance porch, therefore, the latter requirement of 6m of the above criteria should be applied. Taking into consideration both the Council’s and appellant’s measurement calculations the length of the parking space would not meet the required standard to ensure a safe means of escape from the dwelling’s entrance porch front door.

    To allow for access to and from the entrance porch a vehicle parked within the frontage would be extremely likely to overhang the pedestrian highway thus creating an obstacle for passing pedestrians. Consequently, the proposal would create a hazard for pedestrians using the public footway. The appellant contends that any encroachment of the pedestrian highway would be subject to potential enforcement action under separate highway legislation. However, it would not be appropriate to rely on other legislation beyond the scope of the planning system to make an unacceptable development acceptable.

    Further to the above, the plan that supports the proposal does not illustrate that a vehicle would be able to turn within the parking area. As such, a vehicle leaving the site would be required to reverse across the pedestrian footpath or alternatively undertake this manoeuvre in reverse.

    [address] is a busy arterial road. The proposal would require vehicles to either reverse onto the highway or stop on the carriageway to reverse into the driveway. As such, there would be an increased risk of accidents to pedestrians and increased danger to road users from the proposed development even with reasonable visibility of the highway.

    The appellant contends that the IGN3 does not specifically advocate dimension requirements for individual parking spaces or require on site turning. Nonetheless, Policy TP06 expects developments to make satisfactory provision for the parking of vehicles. In this case the proposal would not achieve this.

    I have been provided a photographic list of other examples of accesses onto [address]. However, most of these are not within the immediate environs of the appeal site and those that are the Council indicates to be historic. The proposal should be considered on its own merits taking into account the current development plan policy context.

    The existing occupiers have an electric vehicle that requires charging close to the meter box that is situated at the front of the dwelling. The creation of the driveway could facilitate electric charging for the cars. Whilst this would provide a benefit in reducing vehicle CO2 emissions, this does not overcome the harm that I have identified in regard of highway safety.

    The proposal would bring about benefits for existing and future occupiers by providing easy access to a vehicle and this would also benefit various family members personal well-being issues. However, the harm that I have identified would give rise to highway safety issues and this safety concern is not outweighed by the appellant’s particular circumstances.

    For these reasons, I conclude that the proposed development would be harmful to pedestrian and highway safety. The proposal would, therefore, conflict with Policy TP06 and the provisions of the Framework. That policy seeks, amongst other matters, development to make satisfactory provision for the parking of vehicles.

  5. 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
3339121
Application reference
FH/TH/23/1241
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
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
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
20 February 2024
Valid date
2 March 2024
Start date
13 March 2024
Planning authority decision date
11 December 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
53464
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