The UK drone delivery sector is spending huge amounts of time talking about airspace, detect-and-avoid, BVLOS, CAA approvals, operational authorisations, SORA, ground risk, air risk and technical safety cases. All of that matters. But there is another problem sitting quietly in the background that many drone companies appear to be overlooking: local planning law.

The CAA may regulate the airspace, but local authorities regulate land use. That distinction could become one of the biggest bottlenecks for drone delivery, drone-in-a-box operations and any fixed or repeated commercial drone launch site in the UK.

At the moment, many operators seem to believe that if they have the CAA approval and the landowner’s permission, they are good to go. That may be true for a one-off flight, a survey job, a short trial, or occasional commercial drone use from a private site. But it is not necessarily true once the same land is being used repeatedly as a commercial drone operating base.

The CAA position is relatively simple: if you are standing on private land, taking off from it, landing on it, accessing it, or recovering a drone from it, you need the landowner’s permission. That is a civil land-access issue. It does not mean the local planning authority has approved the use of that land as a drone delivery hub, launch site, drone port, drone-in-a-box station, logistics node, or recurring commercial aviation site.

That is where the problem starts.

In the UK, temporary use of land is generally allowed for a limited period without a full planning application. The well-known planning “28-day rule” allows land to be used temporarily for certain purposes for up to 28 days in a calendar year, subject to conditions, limitations and local variations. But once a site is being used commercially for more than that, or where the use becomes regular, permanent, noisy, disruptive, or materially different from the existing lawful use of the land, planning permission may be required.

This is a major issue for drone delivery.

A drone delivery company cannot build a viable network on occasional launch days. It needs repeat operations. It needs the same depot, roof, yard, car park, industrial estate, hospital site, supermarket site, warehouse site, or village hub to be used again and again. It needs charging.

It needs storage. It needs staff access. It may need fencing, landing pads, telemetry equipment, weather stations, cameras, ground control equipment, battery handling areas and safety zones. It may generate noise, complaints, traffic, privacy concerns and visual impact.

That is no longer just “a drone flight”. That starts to look like a commercial change of use.

The same issue applies to drone-in-a-box systems. A drone-in-a-box unit might look small and harmless on paper, but in planning terms it could still raise questions. Is it a piece of operational infrastructure? Is it permanently installed? Is it fixed to a roof, mast, pole, compound, container or hardstanding? Is it being used every day for security patrols, site inspections, delivery, emergency response or surveillance? Does it change the character of the site? Does it create additional activity, noise, lighting, privacy concerns or public complaints?

If the answer to those questions is yes, then simply saying “we have landowner permission” may not be enough.

This is the part of the drone industry that many companies are currently sleepwalking into.

They are focused on the CAA because the CAA is the obvious regulator. But the CAA does not give planning permission. The CAA can say whether an aviation operation is acceptable from an airspace and safety perspective. It cannot say that a warehouse yard, farm field, supermarket car park, hospital roof or industrial estate has the correct planning use for a repeated commercial drone operation.

That decision sits with the local planning authority.

This could seriously slow down drone delivery in the UK. Every delivery hub may need to be considered site by site. Every local authority may take a different view. One council may see it as an innovative logistics use. Another may see it as an unacceptable noise source near homes. Another may ask for acoustic reports, privacy assessments, ecology reports, transport statements, operating hours, complaint handling procedures, community consultation and evidence of cumulative impact.

That is not a quick route to national scale.

The planning system also gives local residents a voice. That matters politically. Drone delivery may be technically possible, but local communities may still object to noise, privacy, nuisance, wildlife impact, visual intrusion, perceived safety risk, or the feeling that drones are being imposed on them from above. Once planning is triggered, those objections become part of the process.

This is why the drone delivery sector should be careful about claiming that regulation is almost solved. Aviation regulation may be moving, slowly, towards routine BVLOS. But BVLOS approval does not solve local planning. A perfect CAA safety case does not stop a neighbour objecting to drones taking off every few minutes from a nearby site. A landowner agreement does not override planning control. A drone-in-a-box unit on private land does not automatically become lawful just because the landowner bought it.

There is also a commercial risk. If a company installs drone infrastructure and begins operating without checking planning, it may later face enforcement action, complaints, retrospective applications, operating restrictions or forced relocation. That is not just a legal issue. It is a customer issue, an investor issue and a reputational issue.

The irony is that the industry keeps being told that drones will transform logistics, medical delivery, inspection, security and emergency response. Yet the practical reality is that every regular launch site may need local approval before it can operate at scale. A delivery network is only as strong as the land permissions and planning status underneath it.

This does not mean drone delivery should stop. It means the sector needs to grow up about the non-aviation side of regulation.

If the UK wants drone delivery, medical logistics and autonomous drone-in-a-box operations to become normal, the Government needs to recognise that CAA approvals are only one part of the puzzle. Local planning authorities need clear guidance. Drone operators need to be told early that landowner permission is not the same as planning permission. Planning policy needs to catch up with aviation policy.

At the very least, any serious drone operator should be asking these questions before using the same site repeatedly:

Is the current lawful use of the land compatible with repeated commercial drone operations?

Will the site be used for more than 28 days in a calendar year?

Are any launch pads, boxes, masts, cabinets, charging stations or control systems being installed?

Could the operation create noise, privacy, lighting, traffic, ecology or amenity issues?

Has the local planning authority been consulted?

Is there a risk that the operation could be considered a material change of use?

Those questions should be part of every drone delivery business plan. They should also be part of every drone-in-a-box sales process. Selling a box to a customer without warning them about planning risk is storing up problems.

The danger for the UK drone sector is not just that the CAA moves too slowly. It is that companies finally get through the aviation approval process, only to discover that the land they intend to operate from has a completely separate regulatory hurdle.

Drone delivery will not be slowed only by airspace integration. It may be slowed by planning departments, local objections, land-use rules and a 28-day limit that many in the industry have not even considered.

The CAA can approve the flight.

The landowner can approve the take-off.

But the local planning authority may still decide whether the site can actually be used as a drone operation at all.

That is the hidden bottleneck the drone industry needs to face now, not after the enforcement letters start arriving.