Mytax Farm, Bourbles Lane, Preesall (sand and gravel quarry)

appeal 6002168·Lancashire County Council·26 August 2026dismissed
Decision
dismissed, 26 August 2026
Decided by
Planning Inspector: Stephen Normington
Authority
Lancashire County Council (North West)
Appeal reference
6002168
Application reference
LCC/2023/0030
Procedure
inquiry
Development
Extraction and processing of c.500,000 t of sand and gravel over about 5 years (about 100,000 tpa) on 20.7 ha, with washing plant, new access road and restoration using c.220,000 m3 imported inert fill (EIA development)
Site context
open countryside, rural lane
Green Belt
No
Framework applied
August 2026 NPPF
Determinative policies
TR6(4), M3(1)
Development plan policies
Joint Lancashire Minerals and Waste Core Strategy 2009 CS3, CS4, CS8, Joint Lancashire Minerals and Waste Local Plan Part 1 2013 M1, DM2, WM1, Wyre Local Plan 2019 CDMP1, CDMP4, CDMP6
Main issues
need / landbank; highway safety; noise; dust and air quality

Summary

A 20.7 ha sand and gravel quarry near Preesall (Wyre), refused by Lancashire County Council and appealed to an 8-day inquiry. The inspector accepted a "critical" county landbank shortfall and found noise, dust and air quality acceptable with conditions. But the required access visibility splay depended on a hedge owned by an objector, and the narrow B-road could not take two-way HGV traffic safely. That was an unacceptable highway-safety impact, and TR6(4) says such proposals "should be refused". Appeal dismissed.

Issues and findings

Planning balance

"Policy M3(1) of the Framework sets out that … substantial weight should be given to the benefits of mineral extraction … I have therefore attached significant weight to these benefits" (DL ¶188). Against that, the TR6(4) failure: "Notwithstanding the weight that I have attached to the benefits … these would be significantly and demonstrably outweighed by the unacceptable highway safety risk" (DL ¶191).

What made the difference

The access. The landbank case was about as strong as it gets (under one year excluding one dormant site), and amenity passed. But a visibility splay over hedges the appellant did not control, owned by an objector, could not be secured by condition or obligation. And the B-road's width made HGV passing unsafe. With control of the splay land, or a wider haul route, need would very probably have won.

Transferable points

Policy findings

Policy codes are those of the National Planning Policy Framework (August 2026) unless a development plan is named.

PolicyFindingWeightNote
M1(2)(d)benefitnearly all of the landbank sits in one inactive site (Runshaw), which is itself contrary to the principle of M1(2)(d) (DL ¶30)
M2neutral7-year sand and gravel landbank benchmark (cited as "M2(a)"); county landbank only 0.45-0.69 years excluding Runshaw (DL ¶25, ¶31)
M3(1)benefitsignificantM3(1) says "substantial weight" but the inspector attached "significant weight" to meeting the critical landbank shortfall (DL ¶51, ¶188)
TR6(4)failrequired 2.4 x 52 m visibility splays cross hedges on third-party land (owner objects); no Grampian prospect; narrow B-road with no footways means HGV passing and reversing conflicts, a "severe impact from a safety perspective" (DL ¶72-79, ¶85-105)
M4(1)(b)passnoise within the PPG limit (background plus 10 dB, max 55 dB) with bunds and a Noise Management Plan; dust slight adverse at worst, controlled by a DMP; LP DM2 consistent with M4(1)(b) and P3 and given full weight (DL ¶106-156)
P3passair quality and RCS risk negligible; perception of health harm given limited weight (DL ¶166-172)
N6not-engagedSPA/SAC/Ramsar 1.5 km away; Natural England did not engage with the shadow HRA; appropriate assessment unnecessary because the appeal fails anyway (DL ¶173-182)
CS3 / CS4 / M1 (Lancashire M&W plans)neutrallimitedout-of-date restrictions on new mineral permissions given little weight (DL ¶23, ¶38)

Key facts

Sources

This note is one of the decisions behind the NPPF 2026 Navigator, which shows how each Framework test has been applied across all the decisions in the database. Also available as Markdown.