Appeal 3364759
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
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
the installation of a dropped kerb.
Section 02
Decision
The appeal is dismissed.
Section 03
Main Issue
The main issue is the effect of the proposed dropped kerb on highway safety along [address].
Section 04
Reasons
No 176 is a semi-detached house situated on the eastern side of [address], just south of its junction with [address]. The house has a frontage of around 6 metres in width and the front elevation is set some 3 metres back from the rear of the pavement with no front boundary. The house is the end property of a row of dwellings and the northern boundary of the property is a wall and fence separating the appeal site from the bungalow on the corner plot at the junction. There is a bus stop on [address] close to No 176. The road markings delineating the bus stop are now largely erased, but it would appear that they extended from the junction with [address] to a point a part way along the front of the appeal property.
The proposed development would involve the creation of a dropped kerb at the front of No 176 to enable a vehicle to be parked on the forecourt of the property. I have no information before me to indicate the extent of the dropped kerb.
From my site visit, it would appear that, with the exception of Nos 176, 178 and [address], all of the other properties along this side of the road have a low wall to demarcate the front boundary of the property at the rear of the pavement. There is a dropped kerb, which appears as a recent construction, outside of No 180, and a small length of dropped kerb also exists at the front of No 178. I have no details as to whether these lengths of dropped kerb have been authorised. There remains a kerb outside No 176 and part of No 178. From the drawings submitted with the application, there would not appear to be any intention for the dropped kerb to extend beyond the frontage of No 176.
Policy T1 of the Council’s Unitary Development Plan (UDP) indicates that development schemes must be designed, amongst other things, to improve safety for all road users. Policy RD7 of the Council’s Residential Design Supplementary Planning Document (SPD) indicates that parking provision should not dominate front garden areas, the street or impede pedestrians.
At the time of my visit there was a car parked on the forecourt of No 178, with another car parked partly on the road and partly on the pavement outside of the house. There was a vehicle parked, partly on the road and partly on the pavement outside of No 176, very close to the bus stop sign.
Given the limited amount of space at the front of the appeal property, for a car to be able to parallel park on the forecourt at No 176, it would be necessary for that vehicle to reverse from the road across the pavement. I do not have any swept path information before me, but it would seem very unlikely that any vehicle attempting this manoeuvre, would be able to park without an incursion, albeit small, onto the forecourt of No 178, and it would almost certainly need to cross over part of the remaining raised kerb outside of No 178. In any event, the manoeuvre would be dangerous for road and pavement users alike, particularly if there happened to be a bus at the nearby stop picking up or discharging passengers. Moreover, if a car were to be parked on the forecourt, there would be issues of getting in and out of the car without impinging on the pavement, and there would also be an issue of lack of visibility of pedestrians and/or vehicles, due to the presence of the northern boundary wall/fence potentially impeding sight lines.
There have been letters of support for the proposal, and the appellant has also contended that by parking a vehicle on the forecourt at the appeal property, it would prevent vehicles parking on the road at this point, making it safer for buses and passengers. However, I note that even with a car parked outside No 178, at the time of my visit there was also another vehicle parked on the road outside. I do not consider that the proposed drop kerb would necessarily result in no parking at all on the road near the bus stop. Even if there was some deterrent to on-road parking, the issues of danger to pedestrians and other highway users resulting from the difficult manoeuvres into and out of the parking space would remain, and would outweigh any potential benefits.
Section 05
[name]
The appellant states that his family includes a 3-month-old baby, and the ability to park directly outside the house is crucial for family well-being. I sympathise with the appellant on this matter, but it is not reason to allow a development that would be harmful to wider highway safety.
Section 06
Conclusion
In the light of the above, I find that the proposal would be harmful to the safety of highway users, would be likely to impede pedestrians, and would dominate the front garden area of the appeal property. It would, therefore, conflict with Policy T1 of the UDP and with Policy RD7 of the SPD. Accordingly, I dismiss the appeal.
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 239No official casework-database value to compare
- Extracted decision date · page 1
- 27 June 2025Matches the official casework database
- Extracted site visit dates
- 16 June 2025 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3364759
- Application reference
- 25/00188/FUL
- Lead case reference
- Not recorded
- Planning authority
- Tameside Metropolitan Borough Council
- Planning authority code
- E08000008
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
- Unknown
- 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
- 28 April 2025
- Valid date
- 6 May 2025
- Start date
- 6 May 2025
- Planning authority decision date
- 25 April 2025
- Appeal decision date
- 27 June 2025
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
- 71984
- First seen
- 20 August 2026 at 14:25
- Last seen
- 20 August 2026 at 16:28
- Removed from release
- Not recorded
- Record created
- 20 August 2026 at 14:25
- Record updated
- 24 August 2026 at 16:21