← Drone Mapping Job Calculator

How much should you charge for drone mapping?

The honest answer is that price per acre is not a price, and the reason is specific rather than philosophical: the term that moves a mapping job most does not appear in a per-acre quote at all. That term is overlap. This page prices one real job all the way through so you can see where the money actually goes, and then changes exactly one input to show the problem.

Price your own job →

The job

100 acres of a construction site, flown on a DJI Mavic 3E at 120 m AGL, 75% front and 70% side overlap, 10 m/s, five ground control points, an hour of round-trip travel and 45 miles of it. Field rate $125/hr, processing $95/hr, mileage $0.70, target margin 40%. Every figure below comes out of the calculator on this site with those inputs.

1. Resolution first, because it sets everything else

Start at the deliverable, not the parcel. The client's required ground sample distance decides your altitude, and altitude decides the footprint, the line count, the image count and the processing bill. The formula is:

GSD (cm/px) = sensor width (mm) × altitude (m) × 100
              ────────────────────────────────────────
              focal length (mm) × image width (px)

The Mavic 3E has a 17.3 mm wide sensor, a true focal length of 12.29 mm, and a 5280 px wide frame. At 120 m that is 3.20 cm/px. Use the “35 mm equivalent” focal length here with the real sensor width and you get a plausible-looking number and a flight that comes back at the wrong resolution — it is the most common error in a hand-rolled mapping spreadsheet, and it fails silently.

2. Footprint becomes flight lines

At 3.20 cm/px a 5280 × 3956 frame covers 169 × 127 m of ground. Overlap is what is left over:

• Side overlap 70% → lines are 50.7 m apart (169 × 0.30)
• Front overlap 75% → an exposure every 31.6 m (127 × 0.25)

100 acres is 404,686 m², so a square site is 636 m on a side. That gives 13 flight lines of 22 exposures each — 286 images over 8.9 km of path.

A note on the square: acreage alone does not determine a flight, and a square is the shape with the least perimeter for a given area. So this is the optimistic end of the range. Real parcels run longer, never shorter. For a corridor — a pipeline, a road, a transmission line — price from length and swath width instead, because the square model will be badly wrong.

3. Airtime is a small part of the day

8.9 km at 10 m/s is 14.8 minutes, plus 8 seconds of turn overhead on each of 12 turns: 16.4 minutes in the air. One sortie, no battery swap.

And here is the first thing worth noticing about mapping economics:

Airtime is 12% of the field time. A pilot who prices “the flight” has priced an eighth of the job, and a pilot who discounts because “it is only a twenty-minute flight” has discounted against a number that was never the cost.

4. Processing follows the image count

286 images at 9 seconds each of attended time is 43 minutes. Set that rate from your own machine and your own workflow — it is the input people guess at most, and it is worth timing once against a job you have already delivered.

This is the line that a per-acre quote cannot see, which is the whole problem, and section 6 is where it bites.

5. The quote

That is $6.39 per acre, and $255.72 of margin.

Margin is not markup. A 40% margin means price = cost ÷ 0.6. Adding 40% to cost gives cost × 1.4 = $537.02, which is a 28.6% margin, not 40%. On a job with $1,000 of cost the two answers are $1,666.67 and $1,400.00 — a $267 difference on one sortie, repeated on every job you ever quote. This is the single most common arithmetic error in trade pricing and it always runs in the same direction.

6. Now change one number

The client asks for “a bit more overlap — say 80/80”. Same site, same aircraft, same altitude, same rates:

2.19× the images. 1.44× the airtime. $135.30 more to quote — 21.9% on a job whose acreage did not change by a single square foot.

Why the two ratios differ is the mechanism worth internalising:

• Image count goes as 1 / ((1−front) × (1−side)). At 70/70 you keep 30% of each: 1 / (0.3 × 0.3) = 11.1. At 80/80 you keep 20%: 1 / (0.2 × 0.2) = 25.0. That ratio is 2.25 — a quadratic, not a linear, response to a number people discuss in linear terms.
• Airtime goes only as 1 / (1−side), because only side overlap adds flight lines. Front overlap just triggers the shutter more often along a line you were flying anyway. 3.33 → 5.0, about 1.5×.

So the flight looks nearly the same and the processing more than doubles. If you quoted per acre, you absorbed all of it.

7. The one the regulation decides

Resolution does not run upward without limit. 14 CFR 107.51(b) caps a small unmanned aircraft at 400 ft AGL — 121.92 m — unless you are within 400 ft of a structure or hold a waiver. If a coarse target GSD would need more altitude than that, you cannot simply climb: you fly at the ceiling, deliver a finer GSD than was asked for, and cover less ground per pass, so the job takes longer than an unrestricted plan implies. The calculator flags that case rather than quietly planning an altitude you cannot legally fly.

What to do with this

1. Quote the specification, not the acreage. Put GSD and overlap on the quote as named terms. A change to either is a change order.
2. Time your own processing once. Seconds-per-image is the input most often guessed and it scales with the term that moves most.
3. Bill travel and ground control explicitly. They were 66% of the field time here and they are invisible in a per-acre number.
4. Check the battery count against the sortie count before you commit to a date. A short day is a second mobilisation.

Open the calculator →