Key takeaways
- Permission to fly and permission to be looked at are two different questions. Airspace is federal and a neighbour does not control it; how you handle imagery of their property is where the real exposure sits.
- Most neighbour problems on commercial sites are not legal problems. They are surprise problems, and a note beforehand removes almost all of them.
- Keep the capture scoped to your site. Incidental edges are normal on any survey; a camera pointed at the property next door is not.
- HEADS UP: this is general information about how we plan flights, not legal advice. Anything sensitive should go past your own counsel.
It comes up on almost every job with a fence line, which in practice is almost every job. A client wants a survey of their own yard, plant, pit, roof or field, and somewhere in the planning someone asks whether the neighbours have to agree to it.
The question feels like one question. It is actually three, and they have different answers, which is why the conversation usually goes in circles.
Three separate questions
- Can the aircraft legally be in that airspace? This is aviation regulation, and it is federal.
- Can the aircraft take off from, land on or be operated over that ground? This is property access and site control.
- What may be recorded, kept and shared? This is privacy, and it is where nearly all of the real risk lives.
Mixing them together produces both of the wrong answers. One is "it is public airspace so nothing else matters", which ignores privacy entirely. The other is "we need signed consent from everyone within sight", which stops routine work that nobody objects to.
The airspace question
Airspace in Canada is regulated federally by Transport Canada. A neighbouring landowner is not the authority over the air above their parcel and cannot grant or withhold an airspace permission, because it was never theirs to give. What governs the flight is the RPAS rules: the pilot certification held, the aircraft registration, and the distances the rules require from people who are not involved in the operation.
That last point is the one that actually constrains flights near a fence line, and it is a rule about people rather than about property. Where controlled airspace or a nearby aerodrome is involved there is a separate approval process, which we covered in airspace near Alberta airports and aerodromes. The current regulatory picture is set out in our 2026 Alberta RPAS compliance guide.
So on the narrow question: no, a neighbour's permission is not what makes a flight legal. That is also not the end of it.
The ground question
Property rights apply to the ground, and they are straightforward. Taking off from, landing on, driving across or placing ground control points on land you do not control needs the permission of whoever does. This is ordinary access permission and has nothing to do with aviation.
It comes up more often than people expect. The best launch point for a difficult corner is frequently just outside the fence, in a road allowance, on a right of way, or on the adjacent lot. If a flight plan needs that, it needs permission, and the person asking should be the one who wants the survey rather than the pilot improvising on the day.
The privacy question, which is the real one
This is where the actual exposure sits, and it is not answered by aviation rules at all.
Canada has a layered privacy framework. Federal private-sector privacy law applies to commercial activity, and Alberta has its own provincial private-sector legislation as well. The Office of the Privacy Commissioner of Canada has published guidance specifically on drones. The Criminal Code separately addresses surreptitious observation and recording in circumstances where a person has a reasonable expectation of privacy, and that is a serious matter entirely separate from any drone rule. There are also provincial privacy torts and trespass considerations that vary and are outside what an operator should be opining on.
What this means in practice is simpler than the list suggests. The question is not whether the aircraft passed over a boundary. It is whether you captured, kept or published imagery of people or private property that was not part of the job.
The working principle we apply, and the one we would suggest to any buyer: capture the site you were hired to capture, and treat anything beyond it as incidental rather than as content.
Incidental versus deliberate
Aerial survey of a bounded site always picks up some ground beyond the boundary. A nadir grid flown to cover a yard to the fence line will include a strip past it, because overlap and turn geometry require it. That is incidental, it is unavoidable, and it is well understood.
Deliberate capture is different in kind. Flying a corridor over the neighbouring property, pointing an oblique camera across a fence at a dwelling, or flying a thermal pass over a house next door is not incidental, and no amount of "it was public airspace" makes it look like anything other than what it is.
The line between them is usually obvious to everyone involved, which is why it is a workable line.
What we do about it
- Plan the flight around the site boundary rather than around the convenient grid.
- Prefer nadir capture over obliques where a neighbouring dwelling is close, because a nadir camera looking straight down is a very different thing from an angled camera looking across.
- Crop deliverables to the scope. If the orthomosaic extends well past the fence, trim it before it goes out.
- Treat thermal with extra care near residential property. A radiometric pass over a house is the flight most likely to generate a complaint, regardless of intent.
- Do not publish site imagery containing identifiable neighbouring property or people without the client having thought about it, which is part of the data ownership and confidentiality conversation we have at the start of a job.
Notification, which solves most of it
Here is the part that gets skipped. The overwhelming majority of neighbour problems with drone work are not legal problems. They are surprise problems. Somebody hears an aircraft they cannot immediately account for, sees it near their property, and does not know who is flying it or why. By the time anyone explains, they have already called someone.
A short note beforehand almost entirely removes this. It does not need to be a formal instrument. It needs to say who is flying, when, what the survey is for, that the capture is scoped to the client's own property, and who to call with a question. Sent a couple of days ahead, that converts an unexplained aircraft into an expected one.
Where it is worth doing:
- Sites with residential property immediately adjacent, especially acreages and rural parcels.
- Repeat programmes, where a monthly flight is going to be seen many times.
- Anything with existing friction at the boundary, such as a drainage dispute or a development objection.
- Small-town and village sites, where a drone is genuinely unusual and gets noticed.
Where it is usually unnecessary: a fenced industrial site with industrial neighbours, a pit or quarry away from dwellings, or a field in the middle of a quarter section. Use judgement rather than a rule.
If a neighbour asks you to stop
Being told to stop is not the same as being required to stop, but treating it as a fight is almost always the wrong move on a commercial job.
What works: land or move off, talk to the person, explain what the survey is for and what is being captured, and say plainly what will happen to imagery that includes their property. Most of the time that ends it. If it does not, the flight can usually be re-planned around the concern, by shifting the pattern, dropping the obliques on that side, or moving the launch point.
What does not work: continuing while somebody films you from their driveway. Whatever the regulatory position, that becomes a complaint, and a complaint about a client's site lands on the client.
If you are the one buying the survey
- Tell the operator where your boundary actually is, including any easement or right of way that affects it.
- Say up front whether any neighbouring property is sensitive, and why.
- Ask what will be captured beyond your line and what happens to it.
- Ask whether deliverables are cropped to your scope before issue.
- Decide before the flight whether the imagery will be published, and whether that changes anything.
- Send the note to the neighbours yourself where it is warranted. It carries more weight from the landowner than from a contractor.
The short version
A neighbour does not control the airspace above their land and cannot veto a properly conducted flight. A neighbour does control their ground, so any use of it needs permission. And a neighbour has a real interest in what gets recorded of their property and what is done with it, which is where a careful operator spends their attention.
The flights that cause trouble are not the ones that crossed a line on a map. They are the ones nobody explained. If you have a site where the boundary is tight and you want to talk through how a flight would be planned around it, get in touch and we will walk through it before anything is scheduled.
This article is general information about how we plan and scope flights. It is not legal advice, and anything genuinely contentious should go past your own counsel.