Appeal 3298020
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
demolition of existing store/garage and provision of new garage.
Section 02
Decision
The appeal is dismissed.
Section 03
Main Issue
The main issue is whether the proposed garage would cause highway safety issues to users of the adjacent public highway and the light railway.
Section 04
Reasons
The appeal property comprises a detached bungalow located on the corner of [site address] at its junction with [address]. It has a vehicular access and driveway on its western side and at the rear of this and set at right angles to the access is an existing store/garage. In front of that is a car port. Immediately to the west of the property is the [name] and Dymchurch District Railway line (RHDR) and there is a controlled automated barrier across [site address] . The RHDR runs in a north south direction and there are further barrier crossings across roads elsewhere in the estate. On the opposite side of the road and to either side of the railway are further bungalows.
The appellant argues that the previous visibility splay requirements are now redundant since the introduction of the automated safety barriers where the fail safe component is in the lowered position. Consequently, the engine driver would be able to proceed safely as the barriers would be lowered. Furthermore, rail has priority over road and therefore pedestrians and vehicles should refrain from crossing beyond the barriers.
However, rail has always had priority at crossing points when barriers were lowered but history has shown elsewhere on railway crossings in rural areas that road users often ignored warning lights and sought to cross until the last possible moment with the inevitable consequence of accidents. The automated barriers have been introduced here and elsewhere to reduce the level of risk and to my mind, the key safety issue is therefore what happens if they should fail? [name] note the appellant’s assertion that any failure should result in them being lowered, that does not seem to be corroborated by a response from the RHDR who specifically comment in an email exchange with the Council dated 22 December 2021, that ‘ the whole purpose is so that drivers of trains when approaching the crossing if the crossing does not operate automatically, allows them to see adequately up and down the road before they move off’.
That does not suggest that the possibility of the barriers malfunctioning in a raised position can be ruled out. In that scenario, maintaining visibility would allow intervisibility between trains and crossing users so that there was mutual awareness in the event of a train crossing the road and the barriers were not lowered. Based on the evidence before me I consider that although the risk may be low, it cannot be ruled out altogether and therefore any worsening of existing visibility could result in potentially serious safety issues. In this context I noted the convenience store adjacent to the western side of the railway which generated a significant degree of traffic using the crossing at the time of my site visit. Although suggested otherwise by the appellant, I do not consider the relatively small cabinets installed to operate the barriers, would preclude some visibility.
I accept that there are other properties nearby, including one of the bungalows opposite and also elsewhere in the estate, where fences have been put up which also contravene the visibility requirements. However, there is no evidence before me to indicate as to whether they have been lawfully erected or not, or as to how long they have been there, and consequently they have not influenced my finding above. I also note the appellant’s suggestion that other development could be put up without the need for permission which would also impede visibility. That may or may not be the case but it is not an issue which is currently before me to determine. Finally, whilst I note the desirability to provide electrical charging for vehicles, it seems to me that a garage in the proposed location would not be the only solution or location to provide such charging.
I acknowledge the desirability of providing some form of garage which is accessible to vehicles using the driveway whereas the current store/garage is not. There may be an alternative solution which might not reduce the visibility requirements to such an extent as the current proposal. However, that would have to be a matter for further discussion and agreement between the various parties involved.
The Council raises no objections to the design of the proposed garage, nor for any amenity reasons and having considered those issues I see no reason to disagree.
Notwithstanding the above, on the basis of the proposal and evidence before me, the siting of the proposed garage could result in an increased risk between trains and users of the crossing. It would therefore be contrary to Policies HB1 and T1 of the Folkestone & Hythe District Place & Policies Local Plan 2020 in that it would not be safe for all street users.
Accordingly, the appeal should be dismissed. [planning inspector] INSPECTOR
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 1737No official casework-database value to compare
- Extracted decision date · page 1
- 12 December 2022Matches the official casework database
- Extracted site visit dates
- 22 November 2022 (page 1)
Reference and authority
Official identifiers and the planning authority recorded against this case.
- Case reference
- 3298020
- Application reference
- 21/0548/FH
- Lead case reference
- Not recorded
- Planning authority
- Folkestone and Hythe District Council
- Planning authority code
- E07000112
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
- 24 m²
- 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
- 2 May 2022
- Valid date
- 2 May 2022
- Start date
- 12 May 2022
- Planning authority decision date
- 11 March 2022
- Appeal decision date
- 12 December 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
- 24983
- 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