Skip to main content
Official casework recordDismissedCurrent release

Appeal 3306831

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

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

  1. Section 02

    Decision

    The appeal is dismissed.

  2. Section 03

    Procedural Matter

    The description of development in the heading above has been taken from the planning application form. [name] of the appeal form a different wording has been entered, but as the parties have not provided written confirmation that a revised description of development has been agreed I have used the one given on the original application form.

  3. Section 04

    Main Issue

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

  4. Section 05

    Reasons

    The appeal property is located on [address], which the Council advises is a busy transport route through the borough. In its consultation response, Essex County Council as highway authority advises that [address] is classified as a [name] road, the function of which is to carry traffic safely and efficiently between substantial rural populations and on through built-up areas. The site is located within reasonably close proximity to a junction with [name], a lower category of road in the County Council’s Development Management Route Hierarchy, albeit I note the appellant’s view that this is as busy as [address]; the Council also refers to the junction as busy. Opposite the site there is a parade of shops, access to a garage block, and many properties within the vicinity have direct vehicular access onto [address].

    The frontage of the appeal property is paved but parking is located at the rear of the site, accessed from a track off [name]. This is a narrow unmade track serving four properties, and leads to a garage and carport at the appeal dwelling. However, the appellant advises that only one parking space is available, with the garage being dilapidated too small for modern vehicles.

    At the midweek, mid-morning appeal site visit there was a steady flow of traffic along [address], and slowing of vehicles to access the parade of shops, [name] and other accesses. In its consultation response, the highway authority advised that one of the measures to protect the function of [name] roads is to ensure that where there are overriding safety concerns and access is available to a lower category of road, that such access is used.

    The proposal would introduce a further access point that would lead to the slowing of vehicles around a bend in [address], and a potential point of conflict with pedestrians and road users. I appreciate that other accesses in the vicinity also cause slowing vehicles and congestion, and would block the pavement whilst waiting to emerge onto [address]. However, the introduction of another access onto this stretch of road, close to a road junction and opposite access to a parade of shops and a garage block, would be an extra and unnecessary point of potential conflict. Although there are other accesses in the vicinity, minimising the number of points onto the road would reduce the opportunities for traffic conflict and therefore safety risks.

    I am not persuaded that good visibility from the site gateway would avoid the need for vehicles to obstruct the footway, which is deep at this point in [address]. The appellant accepts that it may be necessary to wait for a gap in the traffic, but implying that vehicles could wait on site. In my view, vehicles are likely to wait closer to the road to ensure quick use of a gap in the traffic flow, thereby occupying the footway and with potentially less awareness of pedestrians at the rear of the vehicle. Whilst there may be other accesses in the vicinity that could pose similar risks to safety, this would not justify creating a secondary access point that would introduce its own risks.

    In view of the additional slowing movements that use of the proposed access would create, it would have the potential to interfere with the flow of traffic and the efficiency and functioning of this main road. As this results in a policy objection from the highway authority, the proposal conflicts with Policy T2 of the Castle Point Borough Council Local Plan 1998 (LP).

    The appellant has experienced problems accessing the rear parking spaces as a result of obstruction by other vehicles. However, traffic enforcement measures could address obstruction of the highway, and as a track serving only four properties it seems feasible that the communal area could be managed to avoid inconvenience for all users. As the existing garage is substandard, it is not known if the appellant has explored alterations to create a second usable parking space to meet the needs of residents. I appreciate that the existing arrangements may not be as convenient as frontage parking off [address], but as there is access to alternative parking I do not find that the benefits of the proposal would outweigh the potential risks associated with an additional unnecessary crossover on this stretch of road.

    Attention has been drawn to other accesses in the vicinity, including that at [address], which the appellant advises also has access via the rear track. However, it is not known if these examples are historic as no details of any planning permissions granted and the reasoning behind those decisions has been supplied. As such, I have no information on the planning policies, highway standards and traffic conditions which were in force at the time of their installation.

    The appellant has identified a planning permission granted for a dropped kerb at [address] in 2021, and an appeal allowed at [address] (APP/M1520/D/17/3168818). However, no details have been supplied, and viewing the premises on the ground the site constraints and characteristics do not appear to be the same as in this case. On the basis of the available information, they offer only limited support for the proposal.

    I therefore conclude that the introduction of an additional secondary access point would detract from highway safety and functioning, in conflict with LP Policy T2, and with LP Policy EC2 and RDG12 of the SPD , which together seek to ensure that access to all forms of development, and by all modes of movement, are made safe and convenient. These are consistent with paragraph 110 of the National Planning Policy Framework, which advises that in considering development proposals, safe and suitable access should be achieved for all users.

    For the above reasons, I conclude that this 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 867No official casework-database value to compare
    Extracted decision date · page 1
    28 March 2023Matches the official casework database
    Extracted site visit dates
    7 March 2023 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3306831
Application reference
22/0210/FUL
Lead case reference
Not recorded
Planning authority
Castle Point Borough Council
Planning authority code
E07000069

Casework details

The casework, procedure, development and linking details supplied by the official record.

Casework type
Householder (HAS)
Procedure
Written Representations
Development type
Other minor 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
0 m²
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
12 September 2022
Valid date
17 November 2022
Start date
24 January 2023
Planning authority decision date
22 June 2022
Appeal decision date
28 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
30375
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