Drone site survey: how to assess a job site before anyone flies

A drone site survey is the assessment a crew makes of a job site before the first aircraft leaves the ground, and it is the difference between a flight that goes to plan and one that meets a surprise at fifty feet. Every site brings its own airspace, its own obstacles, and its own people and property to keep clear of, and a survey is how a program learns all of that before it matters. Done well, it is not a formality but the step that turns an unfamiliar site into a known quantity, with the hazards mapped, the access sorted, and the emergency options identified in advance.

This article covers why the survey is a regulatory requirement and not just good practice, the desktop review that starts before anyone drives out, the on-site walk that fills in what a map cannot show, and how a program keeps each survey tied to the job it belongs to. The aim is a repeatable routine that a crew runs the same way on every site, so nothing important depends on a pilot happening to remember it.

Why the survey is required, not optional

The site survey is written into the rules. Before every flight, section 107.49 requires the remote pilot to assess the operating environment, and it names what that assessment must include: local weather, local airspace and any flight restrictions, the location of people and property on the surface, and other ground hazards. The same rule requires the pilot to brief everyone taking part on the conditions, the emergency and contingency procedures, their roles, and the hazards. A survey is how those requirements get met in practice rather than on paper.

Reading that list closely tells you a survey is broader than a look at the sky. Airspace is only one piece, and the rule gives equal weight to who and what is on the ground, because a drone that comes down does so onto that ground. The survey is also where the operation gets sized up honestly, since it is the point at which a pilot decides whether a site can be flown safely, or whether it needs a different plan, a waiver, or better weather.

The desktop survey before you drive out

A good survey starts at a desk, well before the crew loads the truck. The first question is airspace: what class covers the site, whether an authorization is needed to fly there, and whether any temporary flight restriction is in effect. Tools like the FAA's B4UFLY service and the airspace maps behind the authorization system answer most of that, and a program can request access before travel rather than discovering a problem on arrival. Alongside airspace, a look at satellite imagery reveals the obvious obstacles: towers, power lines, tall structures, and the open areas that could serve as takeoff, landing, and emergency zones.

The desktop review also settles the questions that have nothing to do with flying: who owns the site and whether anyone has permission to be there, where the crew will park, and what the weather is expected to do. Whatever the desktop survey turns up should be written down and carried to the site, because a plan that lives only in the lead pilot's head is one the rest of the crew cannot follow.

The on-site walk

A map cannot show everything, so the survey finishes on foot. Walking the site reveals obstacles that imagery misses, from a guy-wire on a tower to a fresh construction crane, and it confirms the takeoff, landing, and emergency zones are where the desktop review assumed. It is also where the crew checks for people and property that will be in the area, sets the boundaries the aircraft will stay within, and confirms the launch point has a clear line of sight. On a program running many sites with several pilots, software that can tie each pilot to only the jobs they were assigned keeps a survey attached to the right job, so the pilot flying a site is working from the assessment made for it.

The walk is also the moment to brief the crew, which the rule requires anyway. Everyone taking part should know the plan, the boundaries, the hazards, and what to do if something goes wrong. A survey that ends without that briefing has gathered information the crew never received, so the point of walking the site is not only to see it but to align everyone on it.

Keeping the survey with the job

For a single flight, a site survey can be a mental checklist. For a program, it becomes a record that has to survive past the day it was made, because sites recur, crews change, and a survey done in spring may need revisiting in winter. A survey that is filed loosely, or not at all, forces the next crew to start over, and it leaves the program unable to show what it assessed if a client or an investigator asks after an incident.

That is where tying the survey to the job pays off. When the assessment, the airspace determination, the identified hazards, and the map boundaries all attach to the specific job and site, the next flight there starts from what was already learned rather than from scratch. The same record answers the question that follows an incident, showing the conditions the crew planned for and the hazards it identified. A survey is most valuable not as a one-time exercise but as a durable part of the job's record that the operation can return to and build on.

Common mistakes in drone site surveys

Treating the survey as an airspace check only. The rule gives equal weight to people, property, and ground hazards, because a drone comes down onto the surface. A survey that confirms the airspace but skips the obstacles and the emergency zones has covered the easy half and left the risky half unexamined.

Skipping the desktop review and improvising on arrival. Discovering an airspace restriction or a missing authorization after driving out wastes the trip and tempts a crew to fly anyway. Settling airspace, access, and obstacles from the office turns the on-site visit into confirmation rather than discovery.

Relying on imagery and never walking the site. Satellite views miss guy-wires, new construction, and temporary hazards. Walking the site confirms the takeoff and emergency zones and catches the obstacles a map cannot show, which is exactly where a surprise at altitude comes from.

Not briefing the crew after the survey. The rule requires briefing everyone on conditions, emergency procedures, roles, and hazards. A survey whose findings stay with the lead pilot leaves the rest of the crew flying blind, so the briefing is the step that turns a survey into shared awareness.

Letting the survey vanish after the flight. A survey kept only in memory forces the next crew to repeat it and leaves nothing to show after an incident. Attaching it to the job preserves what was learned and gives the program a record of what it assessed.

FAQ

Is a drone site survey legally required?

In substance, yes. Section 107.49 requires the remote pilot to assess the operating environment before every flight, including weather, airspace, people and property on the surface, and ground hazards. A site survey is how a program meets that requirement, so skipping it puts the flight offside.

What should a desktop site survey cover?

The airspace class and whether an authorization or a check for restrictions is needed, plus obstacles, takeoff and landing zones, site access, permissions, and the expected weather. Settling these from the office keeps the on-site visit focused on confirming rather than discovering.

Why walk the site if I have satellite imagery?

Imagery misses guy-wires, new construction cranes, and temporary hazards, and it cannot confirm a clear line of sight from the launch point. Walking the site verifies the emergency zones and catches the obstacles that cause surprises once the aircraft is in the air.

How does a site survey help after an incident?

A survey tied to the job records the conditions the crew planned for and the hazards it identified. If a flight goes wrong, that record shows what was assessed and briefed, which supports the program's account and helps it improve the next survey.

Closing thought

A drone site survey is the moment a program replaces assumptions with facts: the airspace it can fly in, the obstacles it must avoid, the people and property to keep clear of, and the emergency options if a flight goes wrong. It starts at a desk, finishes on foot, and ends with a crew that shares one picture of the site. The survey is not the part of the job to rush, because it is the part that makes the rest of the job safe.

If you are surveying sites across a crew of pilots, FlybyOps was built for the operational record problem at the center of regulated drone work. A project and job hierarchy with map-based scoping, a risk register, role-based access control, and an append-only audit log are all part of how the platform keeps each site survey attached to the job and the map area it covers.