Skip to main content
Official casework recordDismissedCurrent release

Appeal 3342098

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

a dropped kerb to provide access from [address], and hard standing to facilitate off street parking (Resubmission of planning ref: 23/00481/FUL).

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    Preliminary matter

    In the interests of accuracy and brevity I have adopted the description of the proposed development used in the Council’s decision letter rather than that used in the original application form.

  3. Section 04

    Main issue

    The main issue is the effect of the proposal on highway and pedestrian safety.

  4. Section 05

    Reasons

    The appeal property is a detached dwelling. It stands at the junction of [address] and [address], the latter being a cu-de-sac comprised of about 10 dwellings. The appeal property has a small front garden, which the appellant proposes to use for parking, with access being provided at the junction.

    I saw that several properties fronting [address] used their former front gardens as parking areas, but those that I saw had no alternative means of providing off-street parking since no rear access was available. That is not the case with the appeal property; it has a lengthy, fenced return frontage onto [address], and as I saw, a set of gates, although there was no apparent sign that parking was taking place within the rear garden.

    The proposed access would be sited at the apex of a bend at the most potentially dangerous spot possible both in respect of vehicles entering and leaving the cul-de-sac, particularly if cars were to leave the proposed space in reverse gear. Forward and lateral visibilities would be curtailed for drivers creating unnecessary risks of accidents/collisions. Similar considerations would apply to pedestrians crossing the mouth of the cul-de-sac. I acknowledge that the level of traffic using the cul-de-sac would not be high, but it is important that those drivers that use it should be able to do so safely.

    The appellant would prefer not to use his rear garden for parking since space is limited, and it is considered impractical particularly taking into account the presence of young children. To my mind, however, having regard to what I saw, there seems no convincing reason why a safe parking space could not be designed and accommodated at the rear of the dwelling.

    I conclude that the proposed car parking space, if built, would unnecessarily increase the risk of accidents at this location thus proving harmful to highway and pedestrian safety. Accordingly, I find a clear conflict with that provision of policy INF1 of the Gloucester, Cheltenham and [name] (JCS) requiring developers to provide safe connections to the transport network.

  5. Section 06

    Other matters

    I have taken account of all other matters raised in the representations, including the appellant’s point that he considers himself to have been treated unfairly, particularly having regard to the presence of similar junction arrangements seen locally. I have noted the examples provided, but I have not been made aware of their provenance in planning terms. Notwithstanding this, their presence does not justify the creation of another potentially dangerous access point.

    No other matter raised is of such strength or significance as to outweigh the considerations that led me to my conclusions.

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 2949No official casework-database value to compare
    Extracted decision date · page 1
    18 June 2024Matches the official casework database
    Extracted site visit dates
    30 May 2024 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3342098
Application reference
23/02056/FUL
Lead case reference
Not recorded
Planning authority
Cheltenham Borough Council
Planning authority code
E07000078

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
1
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
7 April 2024
Valid date
7 April 2024
Start date
11 April 2024
Planning authority decision date
26 January 2024
Appeal decision date
18 June 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
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
Horizon
Dataset status
Current release
Catalogue record ID
52705
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