Appeal 3277724
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
4 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 over the pavement on a classified road.
Section 02
Decision
The appeal is allowed and planning permission is granted for a dropped kerb over the pavement on a classified road at [site address] in accordance with the terms of the application, Ref. DC/21/00477/FULL6, dated 31 January 2021and subject to the following conditions:
The development to which this permission relates shall be begun not later than the expiration of three years beginning with the date of this Decision;
The development hereby permitted shall be carried out in accordance with the following approved plans: OS based Site Location plan; OS based Block Plan; dimensioned sketch of proposed dropped kerb.
Section 03
Main Issue
The main issue is the effect of the proposed dropped kerb on highway and pedestrian safety.
Section 04
Reasons
I saw on my visit that the great majority of properties on this section of [address] have parking on their frontages and dropped kerbs to facilitate highway access and egress. The main difference in this case is that the proximity of the access to the Pelican crossing is considered by the Council to create an unacceptable hazard to pedestrians and drivers, although reference is also made to inadequate on-site turning space.
On the first point, I consider that the presence of the nearby Pelican crossing has a traffic calming effect, as its existence invariably reduces speeds and increases driver alertness. When it is actually in use by pedestrians, the effect of halting traffic flow will be one of creating even safer opportunities for access and egress to No. 176. Furthermore, these interruptions in traffic flow by the Pelican also regulate the movement of vehicles that turn out of both [address] and [address] into [address], some of which turn southeast and accelerate from the junction past No. 176. Without this constraint the Council and the Highway Authority would be able to argue that there would be an increased hazard as regards the potential for collisions with vehicles entering or leaving No. 176.
Furthermore, the road is straight and roadside parking is precluded, thereby enabling good visibility for the drivers of passing vehicles and for the appellant when driving into or out of the parking area. And with the proposed crossing’s distance of 5 metres from the Pelican, I do not envisage any additional danger to pedestrians. I also note that the adjoining dwelling at No. 174 and the house directly opposite on the other side of the road both have dropped kerbs within the zig zag markings of the Pelican.
On the second point of the turning space, the appellant is already using the front curtilage for parking on a basis that in all probability cannot reasonably be prevented by the Highway Authority, and the dropped kerb will not in itself lead to more use of the access. Moreover, crossing the existing raised kerb inevitably results in a slower manoeuvre which is more likely to disrupt the flow of traffic and increase the chance of collision.
I am additionally satisfied that there is enough room for an average sized vehicle to turn on the site to enable entering and leaving the site in a forward gear. This would not be possible if the area is used by two vehicles, bit this is no different to the circumstances of the many other frontages in this part of [address].
Overall, in the circumstances of this case, including the proximity of the Pelican crossing, I conclude that the proposed dropped kerb will have no adverse effect on highway and pedestrian safety. There would therefore be no conflict with Policies 32 & 34 of the Bromley Local Plan 2019 or with paragraph 111 of the National Planning Policy Framework 2021 which says that development should only be prevented or refused on highway grounds if there would be an unacceptable impact on highway safety. This is clearly not the case here.
I shall therefore allow the appeal and grant permission. A condition requiring the development to be carried out in accordance with the approved plans is needed for the avoidance of doubt and is in the interests of proper planning. In addition, the appellant will need to ensure that the construction method and materials needed for the dropped kerb will be subject to the regulations administered by the Local Highway Authority to ensure that the appropriate standard is met in carrying out the proposed installation of the crossing.
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 204No official casework-database value to compare
- Extracted decision date · page 1
- 13 September 2021Matches the official casework database
- Extracted site visit dates
- 24 August 2021 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3277724
- Application reference
- DC/21/00477/FULL6
- Lead case reference
- Not recorded
- Planning authority
- London Borough of Bromley
- Planning authority code
- E09000006
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
- 24 June 2021
- Valid date
- 24 June 2021
- Start date
- 14 July 2021
- Planning authority decision date
- 10 May 2021
- Appeal decision date
- 13 September 2021
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
- 3105
- First seen
- 20 August 2026 at 14:24
- Last seen
- 20 August 2026 at 16:25
- Removed from release
- Not recorded
- Record created
- 20 August 2026 at 14:24
- Record updated
- 24 August 2026 at 16:21