Ministry of Defence safeguarding and radar interference

Development inside a Ministry of Defence safeguarding zone triggers a consultation you cannot design your way around after the event. The MOD is consulted on tall structures, external lighting, wind turbines and solar arrays near its aerodromes, technical sites and explosives storage areas, and an objection at that stage is usually about physics rather than about massing or materials. MOD safeguarding planning constraints also sit alongside civil aviation safeguarding, so a site can be well clear of the nearest commercial airport and still fall squarely inside a defence zone.

The consultation itself is handled by the Defence Infrastructure Organisation on behalf of the department. For a land promoter scoping an evidence base, the point to grasp early is that defence safeguarding is a binary technical question about interference, not a planning balance where public benefits can be weighed against harm.

What defence safeguarding protects

Safeguarding exists to keep military operations working: aircraft taking off and landing, radar seeing what it is meant to see, radio links staying clear, and explosives stores keeping their separation distances from people.

Four broad categories cover most of it. Operational aerodromes and relief landing grounds, where obstacle clearance and birdstrike risk matter. Technical sites, which include air defence and air traffic radar, meteorological radar, communications and navigation aids. Explosives storage areas around ordnance depots and some barracks. And ranges, danger areas and low flying areas, which affect structures and lighting more than they affect land use.

The asset being protected determines the question asked. Around an aerodrome the concern is a physical obstacle or something that attracts birds. Around a radar head the concern is a returned signal that clutters the display. Around an explosives store the concern is people, so the sensitive proposal is housing rather than height.

Statutory and non-statutory safeguarding

Statutory safeguarding works through a direction to local planning authorities requiring consultation on defined categories of development within mapped zones. Every safeguarded site has its own set of maps held by the local planning authority, and those maps set out which applications must be referred and at what height. The authority has to consult; it cannot waive the referral because the scheme looks harmless.

Outside the statutory zones the MOD still asks to be consulted informally on wind and solar schemes, tall masts and anything near a low flying route. Non-statutory consultation carries no procedural bite, but a late objection from the department is a material consideration and case officers take it seriously. Treating the informal route as optional is a false economy.

The mechanics of the referral sit in the Development Management Procedure Order 2015, which sets the consultee framework, the 21-day period and the duty to give substantive responses. That order is also where you find the wider list of bodies a council must consult, which is worth reading alongside hazardous substances consultation zones if your site sits near an industrial installation as well.

Height and lighting triggers

Safeguarding maps use graduated height thresholds that step up with distance from the aerodrome. Close in, a two-storey building can breach the threshold. Further out, only structures of real height do. The figures differ between sites, so read the map for the specific aerodrome rather than carrying a rule of thumb between projects.

Two things catch developers repeatedly. The first is cranes. Tower cranes are frequently taller than the permanent building and need a separate crane operating procedure agreed with the aerodrome, which is a construction-phase matter but should be flagged in the application so it does not arrive as a surprise condition.

The second is lighting. Aviation obstruction lighting requirements under the Air Navigation Order 2016 bite on en-route obstacles at and above 150 metres above ground level, and aerodrome safeguarding brings in a separate concern about lighting that could be confused with runway or approach lighting. Long straight lines of white or amber lighting near an approach path attract comment. So do unshielded upward-directed floodlights.

Radar and telecommunications interference

Radar interference wind turbine objections are the single most common reason a defence consultation stops a renewable scheme. Rotating blades produce Doppler returns that primary surveillance radar can read as moving aircraft, and the effect extends a long way, well beyond any visual zone of influence. Distance from the radar head, blade tip height and the number of turbines all matter, and so does whether the site sits in radar line of sight.

Solar arrays raise a different set of issues. Large arrays can affect meteorological radar and, more often, they raise the glare question dealt with below.

Technical site safeguarding around communications installations is narrower in extent but less forgiving. A building placed across a microwave link path blocks it, and the mitigation is relocation rather than attenuation. Masts and tall plant on roofs can do the same thing, which is why a tall building scheme near a defence communications site needs its coordinates tested before the massing is fixed rather than after.

Solar glare near airfields

Reflected light from panels, glazed facades and metal roofs is assessed against the view from the control tower and from aircraft on approach. The usual method models the sun's position through the year, calculates when a reflection would reach the receptor, and reports duration and intensity.

Mitigation is generally straightforward once the geometry is understood. Changing panel tilt or azimuth, using anti-reflective coatings, adding screening or moving an array a short distance can remove the receptor from the reflection path. What does not work is arguing that the effect is brief. Even short daily windows at a busy approach attract an objection.

Consultation procedure and timescales

The referral happens after validation, in parallel with other statutory consultations, and the standard period is 21 days. In practice defence responses on ordinary building schemes come back quickly, because most are cleared against the maps without further work. Wind, solar and tall structure cases take longer, and a radar assessment can add months if it has to be commissioned.

Pre-application engagement is the sensible route for anything likely to be contentious. The MOD will comment on a described scheme before an application exists, and a written position at that stage is worth far more than an objection to a submitted application. Fold it into the same programme as your other constraint checks: it sits naturally with the work described in mine entries and coalfield planning conditions, which is another desk-based enquiry best done before the layout hardens.

Mitigation that resolves an objection

Defence objections are resolved in three ways, in roughly this order of likelihood.

1. Redesign the offending element: lower the ridge, move the mast, reorient the array, relocate the attenuation basin away from the approach.
2. Accept a technical mitigation scheme, which for radar cases means infill radar, blanking or a negotiated operating restriction, secured by planning obligation or condition and paid for by the applicant.
3. Withdraw the element entirely, which is what happens to a good number of turbine proposals inside air defence radar coverage.

Conditions attached to a permission tend to cover crane procedures, lighting specifications with a maximum upward light output, bird hazard management plans for schemes involving new water bodies, and a requirement to notify the aerodrome before works start.

Checking the position before design

Do this as a desk exercise at the point you are testing site capacity, not after the architect has produced a scheme.

• Ask the local planning authority for the safeguarding maps covering the site and the categories of development they capture.
• Establish the height thresholds that apply at your distance, and check them against both the permanent structures and the likely crane heights.
• For any renewable element, get the coordinates and blade tip or panel heights into the hands of the Defence Infrastructure Organisation early.
• Record the outcome in your constraints plan alongside flood, heritage and ecology, so the whole picture is visible when you scope the evidence base.
• Where the site is also within a landscape designation, read the safeguarding position together with the duty described in National Landscapes and the duty on decision makers, because obstruction lighting and landscape policy pull in different directions.

The honest uncertainty here is scope. Safeguarding maps are updated as the defence estate changes, and a site that was outside a zone three years ago may not be today. Always work from the current maps held by the authority.

If you are putting the constraint schedule together for a major application, the full list of report types by category will show you which of the technical documents a defence-constrained site typically needs, and you can enter the postcode on PlanScope to see which ones the site flags against.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.