Skip to main content
Official casework recordAllowedCurrent release

Appeal 3321886

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

described on the planning application form as: “I would like to apply for a vehicle cross over / drop kerb application and I understand I need a planning permission completed first.”

  1. Section 02

    Decision

    The appeal is allowed and planning permission is granted for development described as “I would like to apply for a vehicle cross over / drop kerb application and I understand I need a planning permission completed first”, at [site address] , Enfield, Southgate [postcode] , in accordance with the terms of the application, Ref 23/00357/HOU, dated 4 February 2023, subject to the following conditions:

    The development hereby permitted shall begin not later than three years from the date of this decision.

    The development hereby permitted shall be carried out in accordance with the following approved plans: Location Plan – [site address] [postcode] Proposed Front Garden Plan (Ref: [name])

  2. Section 03

    [name]

    The main issues are the effect of the proposal on highway safety and the availability of public on-street car parking.

  3. Section 04

    Reasons

    The appeal site is a semi-detached property fronting on to [address], which forms part of a reasonably busy ‘A’ road linking Southgate to the northwest with the A406 [address] to the southeast. [address] is flanked mainly by residential properties in the vicinity of the site comprising detached, semi-detached and terraced houses and flats. The road is lined on both sides by grass verges, with footways adjacent to the front boundaries of the residential properties. The verges contain irregular tree planting and are interrupted at varying intervals by the hard-surfaced vehicular access points that serve many of the neighbouring properties.

    The Council’s officer report refers specifically to Policy DMD 46 of the Enfield Development Management Document – [name] 2014 (the DMD), which states that vehicle crossovers and dropped kerbs that allow for off-street parking and access onto roads will only be permitted where they meet 8 criteria (A to H). The Council considers the proposal would fail to meet criteria C, D, E and [name] will address each criterion in turn.

    [name] seeks to resist proposals that would increase on-street parking pressures in areas already experiencing high on-street parking demand. Paragraph 9.2.4 of the DMP, forming part of the supporting text to Policy DMD 46, states that permission will not be granted if surveys demonstrate that on-street parking occupancy is high.

    At my site visit I noted that vehicles were parked on both sides of [address] in the vicinity of the property. Road markings and the presence of access points indicated suitable locations for on-street parking, and there were numerous spaces available to park on both sides of the road without causing obstructions or parking illegally. [name] acknowledge this observation to be a snapshot in time, I am provided with no surveys or any other compelling evidence to demonstrate any particularly high-level of on-street parking demand or occupancy. As such, based on my observations and the available evidence, the proposal would not conflict with criterion C.

    [name] seeks to resist proposals that have an adverse impact on road safety. The Council cites specific concerns including the proximity to the junction with Hillfield Park and the presence of a mature tree which impedes visibility.

    [name] acknowledge that some vehicular crossovers on [address] may have been constructed unlawfully, it is nevertheless the case that such access points are an intrinsic characteristic of the area, and I am provided with no evidence of the Council taking enforcement action against any unlawful development. Vehicle movements on and off driveways in both forward and reverse gear are therefore commonplace in the area.

    The vehicular access would be adjacent to the eastbound lane of [address]. The road is reasonably straight giving relatively clear sightlines to eastbound traffic approaching the proposed access point. The presence of existing vehicular access points at the neighbouring properties to the west limit the number of vehicles parked on the street, which assists in this regard. There would also be acceptable visibility to westbound traffic.

    A detached property lies between the appeal site and the junction with Hillfield Park, providing a reasonable separation from the junction. The proposed arrangement would be similar to that found at several other properties in the vicinity, and I am provided with no specific evidence that these examples contribute to highway safety concerns.

    The Council has included an image of the appeal site in its officer report that does not reflect my observations on site, with the photograph showing a mature tree outside of Nos 34 and [address] that has since been removed. At the time of my visit two young trees had been planted in the verge close to the proposed point of access. There is also a mature tree closer to the junction with Hillfield Park. However, there are numerous examples of trees close to access points in the area and they form an intrinsic characteristic of the street with limited effects on sightlines. I am therefore not persuaded that the proposed access point would be unsafe due to the presence of the trees, either in their current state or as they mature. For the reasons above, I do not find the proposal to conflict with criterion D.

    [name] seeks for there to be no adverse impact on the free flow and safety of traffic on the adjoining highway and in particular on the effective movement of bus services. As previously noted, the prevalence of similar access points throughout the immediate area means vehicle movements on and off driveways are already commonplace. I am provided with no specific evidence that the creation of this additional access point would tangibly affect the free flow or safety of traffic or bus services. As such, the proposal would not conflict with criterion E.

    [name] seeks for proposals to show that there are no alternative opportunities for safe access to the property (for example to the rear or side). The proposal seeks to provide parking for an individual with mobility issues. [name] acknowledge there is an existing parking space to the rear of the property, accessed from Hillfield Park, the route from this space to the house would involve either navigating the rear garden or the footway around the corner of the Hillfield Park / [address] junction. The Council’s officer report notes that the application included evidence of a blue badge, but I am provided with limited such evidence within the appeal submission. Nevertheless, I do not dispute that the proposal would significantly improve access to the property for those with mobility needs. Furthermore, given my findings on the other criteria, the proposed access point would be safe. I therefore find the proposal would not conflict with criterion G.

    The Enfield Council Revised Technical Standards for [name] (excluding Heavy Duty Crossovers) – April 2013 (the RTS) provides standards for crossover developments with the aim of ensuring proposals provide safe access and egress and do not adversely affect the passage of vehicular traffic in highways. Although the RTS is a material consideration, I attach it limited weight on the basis it does not form part of the development plan. In any event, I am not persuaded that there would be any specific conflict with the RTS.

    I note the Council’s reference to the history of refusals at the adjacent property of No [address]. [name] am provided with limited substantive details of these proposals, the neighbouring property is closer to the junction with Hillfield Park and I am not persuaded that the relevant considerations would be comparable. As such, I give limited weight to this matter.

    For the reasons given above, the proposed development would not have a harmful effect on highway safety or the availability of public on-street car parking. It would therefore accord with Policy DMD 46 of the DMD, Policies 24, 25 and 30 of The Enfield Plan Core Strategy 2010-2025 and the provisions of the National Planning Policy Framework, which together seek, among other objectives, to permit vehicle crossovers and dropped kerbs in certain circumstances; to deliver improvements to the road network; to provide safe, convenient, and accessible routes for pedestrians, cyclists and other non-motorised modes; to promote attractive, safe, accessible, inclusive and sustainable neighbourhoods; and for development to only be prevented or refused on highways grounds if there would be an unacceptable impact on highway safety, or the residual cumulative impacts on the road network would be severe. It would also generally accord with the RTS, which has similar aims.

  4. Section 05

    Conditions

    Conditions relating to the statutory time limit and a list of approved plans are necessary in the interests of certainty.

  5. Section 06

    Conclusion

    For the reasons given above, I conclude that the appeal should be allowed subject to the conditions listed in my formal decision.

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 4240No official casework-database value to compare
    Extracted decision date · page 1
    21 December 2023Matches the official casework database
    Extracted site visit dates
    19 October 2023 (page 1)

Reference and authority

Official identifiers and the planning authority recorded against this case.

Case reference
3321886
Application reference
23/00357/HOU
Lead case reference
Not recorded
Planning authority
London Borough of Enfield
Planning authority code
E09000010

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
Allowed
Decision category
Allowed
Received date
10 May 2023
Valid date
10 May 2023
Start date
9 August 2023
Planning authority decision date
12 April 2023
Appeal decision date
21 December 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
44092
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