The Complete Guide to Planning a Drone Waypoint Mission in AirPlot

Automated waypoint missions are how drones do real work — consistent altitude, consistent overlap, the same flight repeatable next month. Traditionally that meant desktop planning software and a laptop in the truck. This guide covers the whole job from a phone, start to finish, and doubles as the reference for every control in AirPlot.

Step 1 — Pick the Mission Type

The mission type sets sensible defaults for everything downstream — altitude, overlap, flight pattern, and gimbal behaviour. Four types cover most professional work:

• 3D Visual — detailed models and mesh reconstruction. Higher overlap, oblique camera angles, orbital passes around the subject.
• Elevation Map — terrain and topographic surveys (DSM/DEM). Straight nadir camera, efficient grid coverage.
• Urban / Stealth — tight environments. Low and slow, flight path stays inside your boundary markers, facade passes.
• Object Scan — a single structure captured from all angles. Low altitude, tight orbits, mixed nadir and oblique.

You can change any parameter afterwards — the mission type is a starting point, not a cage.

Step 2 — Define the Area

There are two ways to define a mission area, and both work on the same map.

Walking the property (GPS). Stand at your takeoff spot and tap Capture Home. Then walk the property line and tap Capture Boundary Point at each corner. The map draws your boundary as you go, and the readout at the top shows GPS accuracy so you know when to trust a tap. Three points make a mission; more points trace complex parcels.

Planning remotely (crosshair). Pan and zoom the map to anywhere on earth, put the crosshair where you want a point, and tap +Pt. Same accuracy, no walking required — useful for quoting a job before you visit, or planning a site you can't access on foot.

The POI (optional). A Point of Interest is the thing your mission is about — a tower, a building, a stockpile. Capture one with the ⊕POI button on the map (crosshair) or Capture POI at GPS (standing at it), then set its height in metres above ground. A POI does two things: it becomes the aim point for orbital passes, and it unlocks the Focus POI heading mode described below. Leave it blank and orbits simply aim at the centre of your boundary at ground level.

As soon as your home point is set, AirPlot queries the FAA's UAS Facility Map grids for that location and shows a green, amber or red indication beneath the capture buttons. Tap it for the full readout.

Read that result carefully: it is an advisory lookup, not permission to fly. A green result means no LAANC grid was found at that point — it does not mean the airspace is clear, and it does not authorize a flight. The FAA grid data covers controlled-airspace ceilings around airports; it does not include temporary flight restrictions, stadium and security no-fly zones, national parks, wildlife refuges, state and local ordinances, private property restrictions, NOTAMs, or anything that changed after the data was published. Verify independently in B4UFLY or an equivalent official source, obtain LAANC or DroneZone authorization where required, and treat AirPlot's indication as a first look rather than a final answer.

Step 3 — Tune the Parameters

This is where a mission becomes a specific plan. Every control has a sensible default per mission type; these are the ones worth understanding.

Flight Pattern

• Single Grid — a lawnmower pass, nadir camera. Fastest coverage; the standard for elevation and orthomosaic work.
• Double Grid — crosshatch: two perpendicular passes. Substantially better 3D reconstruction on varied terrain, roughly double the flight time.
• Perimeter — orbit rings around the area. Facades and structures rather than ground coverage.
• Enhanced 3D — grid plus crosshatch plus orbital passes. The most complete capture, and the most expensive in time and battery.
• Corridor — a linear strip. Roads, fencelines, pipelines, riverbanks.
• Star / Radial — radial arms across a single structure for maximum angular coverage.

Altitude, Overlap and Speed

Altitude drives ground resolution and coverage rate. Overlap — front and side — determines whether photogrammetry software can reconstruct your subject: 75–80% front and 70–75% side is the working standard for mapping, and higher for 3D. Speed affects how much ground passes under the camera between shutter releases; slower is safer for detail.

Line Spacing and Buffers

Line Spacing sets the distance between adjacent grid lines — tighter spacing means more lines, more waypoints, more flight time, and more detail. It can go as tight as 1 metre for close urban and object work.

Grid Boundary expands or contracts the flown area relative to the boundary you captured. Positive values fly wider than your markers (useful because photogrammetry models degrade at their edges); negative values keep the aircraft inside them, which is what Urban missions default to.

Orbit Buffer sets how far orbital rings sit outside the subject. On a tight object scan this is the difference between a usable orbit and one that collides with the structure.

AirPlot refuses to generate a plan smaller than 3×3 metres, and tells you which control to change — rather than silently substituting a different mission than the one you asked for.

Grid Heading — Where the Nose Points

This is one of the most consequential settings and the least understood. It controls which way the aircraft faces while flying the grid — which determines what the camera sees.

• Fixed — the nose holds a single angle for the whole grid, crabbing sideways and backwards along the serpentine. Fastest option, no turnaround rotation. Correct for straight-down nadir mapping, where heading doesn't affect the image.
• Follow Path — the nose tracks the direction of travel, turning to face each new waypoint. This is what you want for oblique capture, facade passes and 3D work, where the camera angle relative to travel matters. Note the trade-off: on a serpentine grid the aircraft yaws 180° at the end of every line, which adds flight time.
• Focus POI — the nose stays locked on your captured POI for the entire grid, however the aircraft is moving. Ideal for scanning a single structure: every photo looks at the subject from a different position. Requires a POI — AirPlot will prompt you if you select this without one.

Orbital passes always face the subject regardless of this setting: they aim at your POI if you captured one, or the centre of your boundary if you didn't.

Intended Photo Interval

Set this to whatever you'll dial into the camera's timed-shot mode before takeoff — 1, 2, 3 or 5 seconds. AirPlot uses it to estimate your photo count, and more usefully, it checks the interval against your speed and overlap: green means the interval achieves your target overlap, amber tells you the exact speed to slow to. This one check prevents the most common mapping failure — gaps in the model because the camera couldn't keep up with the aircraft.

Step 4 — Generate and Review

Before you commit, read the estimates: photo count, flight time, batteries required, coverage area, and the waypoint budget. The path preview draws the full route over satellite imagery with a scale bar, so you can see exactly what will be flown and how big it is.

Two numbers deserve attention. Batteries: any mission over one battery pack means a mid-mission swap, and AirPlot warns you — usually the better answer is to split the area, raise altitude, or widen spacing. Waypoint budget: controllers cap the number of waypoints per mission, so a plan that exceeds it needs simplifying before it will load.

When it reads right, tap Download Mission. AirPlot builds a flight-ready .kmz waypoint file in the industry-standard WPML format, generated server-side with a structure verified on real flights.

Loading the KMZ Onto Your Controller

Consumer flight apps don't have an import button — the technique is to replace the file of an existing mission. Five minutes, once:

• 1. Create a placeholder mission on your controller. In your flight app's waypoint mode, tap out any few points near your location and save it. This creates the folder structure your mission will live in.
• 2. Connect the controller to your computer with USB-C and choose File Transfer when prompted.
• 3. Find the waypoint folder. Browse the controller's storage to the flight app's waypoint directory — you'll see a folder named with a long ID for the placeholder you just made, containing a .kmz file.
• 4. Replace the file. Delete the placeholder's .kmz and copy your AirPlot download in, renamed to exactly the filename you deleted. The name must match; the contents are now your mission.
• 5. Restart and fly. Disconnect, power the controller off and on, open waypoint mode — the placeholder now shows your AirPlot route over your property. Review it on the map, check your surroundings and airspace, and launch.

The Mission Doesn't Fire the Shutter

A waypoint mission file controls where the drone flies and where the gimbal points — it does not command the camera to take photos. Photos come from your camera's own timed-interval shooting mode, set on the controller before takeoff (photo mode → timed shot / interval).

The two work together: the mission flies at a steady speed, the interval timer fires at a steady rhythm, and photo spacing comes out even. Set the interval you chose in Step 3, start interval shooting as you launch, and stop it after landing.

If you fly a mission and come home with an empty SD card — this is why. It's the single most common first-mission mistake, and it costs a re-flight.

Saving, Reloading and Reusing Missions

Save a mission and everything comes back with it — boundary points, home point, POI, and every parameter including heading mode and photo interval. Reload it next season and fly the identical route for a true change-comparison, or use last month's plan as the starting point for a similar property.

Pre-Flight, Every Time

A generated mission is a plan, not a clearance. Before every flight:

• Verify airspace with an official source. AirPlot's FAA tab queries the FAA UAS Facility Map grids as a convenience; it is advisory data, may be incomplete or out of date, and is never an authorization. Confirm in B4UFLY or your usual official tool, and file for LAANC or DroneZone authorization where controlled airspace requires it.
• Check for TFRs and local restrictions — temporary flight restrictions, events, emergency operations, parks, and state or municipal rules sit outside the facility-map data entirely.
• Fly under the right certification for the operation (Part 107 for commercial work in the United States) and within its limits.
• Confirm the route on your controller's map matches what you planned, keep obstacle avoidance enabled, and maintain visual line of sight.

The automation flies the pattern. You are the pilot in command — responsible for the legality and safety of the flight, regardless of what any planning tool displays.