Appeal 3297109
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
a dropped kerb.
Section 02
Decision
The appeal is dismissed.
Section 03
Procedural Matter
Since the date of the decision the Council has adopted the Brent Local Plan 2019-2014 (LP) in February 2022. Policies of the Development Management Policies 2016 that have been referred to in the Council’s decision are no longer part of the development plan and are superseded. The Council has forwarded copies of the relevant policies of the new LP, which were referred to as emerging policies at the time of their decision, and the appellant has clearly considered these new policies in their appeal submissions. I have considered the appeal having regard to the up-to-date development plan.
Section 04
[name]
The main issues are the effect of the proposal on highway safety, amenity, and drainage.
Section 05
Reasons
The appeal property is a mid-terraced dwelling located on the southern side of [address], a fairly busy London distributor road and bus route. The houses to this side of the road are set below the level of the adjoining footpath and carriageway due to the topography of the area. The frontages to the properties in this particular terrace at Nos 33-47 (odd) are fairly short and shorter than adjoining terraces to each side which are set on a slightly more recessed forward building line. The proposal is to lower the kerb at the roadside to create a pavement crossing for a car to park on the frontage of the premises at right angles to the road. This would involve breaking through a continuous parking bay to this side of the road in front of Nos 35-39 and creating a vehicle crossing over an existing grass verge and pavement.
The Council point to their Domestic Vehicle Footway Crossover Policy V4 March 2021 (DVFCP). The loss of a parking bay in front of No 39 to accommodate the proposed dropped kerb would directly conflict with the DVFCP where it states that the Council’s policy, when considering the construction of crossovers, is that a major consideration will be the maintenance of on-street parking. It explicitly states that total capacity and the street scene should not be compromised. During my daytime visit I saw that the roadside parking spaces were heavily used. The level of parking stress in the area is also recognised by the appellant in their submissions. [name] recognise that a private parking space within the curtilage of No 39 would be of direct benefit to the appellant, the loss of a kerbside space would reduce parking capacity on the highway as a whole. This would have the potential to add to on-street parking demand or otherwise harm existing on-street parking conditions by creating a shortfall of public parking. As well as contravening the DVFCP this would also be directly contrary to criteria a) and c) of LP Policy BT2.
Turning to the off-street parking space. My attention has been drawn to an earlier proposal for a similar use which was refused planning permission in October 2019 (Ref 19/2467). I have been provided with a copy of the plans that were submitted at that time. [name]/0204/LS gives a dimension for the depth of the front garden between the back edge of a 100mm thick front boundary wall and the front face of the dwelling’s bay window as 4585mm with a proposed driveway length of 4.1m. This was considered to be unacceptably short of the minimum requirement of 4.8m, which is specified within the DVFCP. The appellant has asserted that the proposal has been revised with significant changes to the design. I recognise that the originally proposed gates have been removed and that at least 30% of the front garden would be soft landscaped, which the Council considers would be acceptable in this instance. Nevertheless, the current plan [name]-39-01 [name], shows a dimension for the proposed hardstanding to be 4800mm but without showing the property’s front bay window, with an illustration in the appellant’s grounds of appeal showing a total depth for the frontage, including from the front of the bay window to be 4.9m.
There is no substantive explanation for the difference between the dimensions given on the 2019 application plans and those on the current appeal plans. Revisions to the layout cannot explain the change from a forecourt depth that was shown to be below the minimum required to one that is now apparently larger in order to accommodate a full-size parking space. In the absence of an accurately measured survey for the property’s frontage, based on the information before me I cannot be confident that a parked vehicle would not overhang the footway. This would be prejudicial to pedestrian safety and in this regard the proposal would fail to be safe having regard to the Council’s crossover guidance. It would therefore fail to satisfy one of the criteria listed within the Council’s Residential Extensions & Alterations Supplementary Planning Document 2 (SPD) where it deals at section 2.[address] and would conflict with part a) of LP Policy BT4.
I have further concerns over safety in relation to the gradient of the proposed driveway. There is an obvious and significant levels difference between the threshold of the dwelling and the back edge of the highway. There is a difference of opinion between the Council and the appellant over what precisely the gradient of the parking space would be. I recognise that there is no Council guidance on what is, or is not, an acceptable gradient for a parking space or driveway. However, I have no doubt that a steep gradient would make a reversing hill-start onto a busy distributor road a difficult manoeuvre and one that would be potentially dangerous on the highway with the risk of conflict between converging vehicles, including cyclists. From the information available to me and as shown on the Proposed Side Section on [name]-39-02 [name], combined with my own observations of the levels’ differences during my site visit, I am not satisfied that the ultimate gradient of the pavement crossover and hardstand can be readily understood. Safe access for vehicles entering/egressing the site has not been adequately demonstrated. This would be further contrary to the primary considerations of the DVFCP and Policy BT4.
The Council is additionally concerned that the proposal would unacceptably remove an extent of grass verge. However, the verges to both sides of [address] are regularly punctuated with concrete crossings. A crossing to the front of No 39 would not be alien or harmful to the visual amenity of the area. Additionally, the depth of the verge at this point is clearly less than 3m and as such its loss would not conflict with the DVFCP in this regard.
Regarding drainage, due to the gradient of the land, water run-off from the hard surface would be contained within the property’s boundary. Moreover, a permeable surface is proposed and could have been secured by condition in the event of the appeal succeeding, along with other drainage details if necessary. In these circumstances I am satisfied that there would be no unacceptable risk from flooding.
The Council has questioned whether suitable pedestrian visibility splays would be provided due to a hedge that is proposed in order to limit the width of the opening on the site’s frontage. This is a further matter that could have been controlled by condition had I been minded to allow the appeal.
Section 06
Other Matters
I appreciate that there are many pavement crossovers in the immediate locality, however I am not persuaded that the circumstances elsewhere along this stretch of [address] are directly comparable with those at No [address] of which it forms part. Neither does the [name] submitted by the appellant, which indicates just two slight incidents in the area over the last ten years, the absence of any objections to the proposal, or a letter of support, indicate to me that the proposal at No 39 would be inherently safe.
I have carefully considered the appellant’s circumstances and I understand that a private parking space within the curtilage of the property would be of significant personal benefit. However, when weighed in the balance, the personal gains do not outweigh the harms that I have identified regarding the loss of on-street parking in an area of parking stress and highway safety.
I appreciate that a single parking space at No 39 would satisfy the car parking allowances permitted for residential use as set out in The London Plan 2021. However, it is not unusual for policy and guidance to pull in different directions. In this instance I have found clear conflict with the DVFCP, the SPD and development plan policy. For this reason, the proposal would not amount to a sustainable form of development for the purposes of the National Planning Policy Framework.
Section 07
Conclusion
For the reasons given, I have found direct conflict with [name] BT2 and BT4. Notwithstanding my findings with regard to amenity and drainage, the failure to show satisfactory access and parking which is safe would also conflict with parts b) and f) of LP Policy DMP1. Accordingly, and having regard to all other matters raised, the appeal is 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 286No official casework-database value to compare
- Extracted decision date · page 1
- 22 September 2022Matches the official casework database
- Extracted site visit dates
- 22 August 2022 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3297109
- Application reference
- 21/4617
- Lead case reference
- Not recorded
- Planning authority
- London Borough of Brent
- Planning authority code
- E09000005
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
- 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
- 15 April 2022
- Valid date
- 15 April 2022
- Start date
- 27 April 2022
- Planning authority decision date
- 11 February 2022
- Appeal decision date
- 22 September 2022
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
- 20889
- 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