FAA Part 107 CertifiedDrone Photography · Video · Photogrammetry$2M Liability InsuredCalifornia · Metro Atlanta · South FloridaNDAA-Compliant LiDAR on Request for Federal WorkCheckpoint Report With Every LiDAR JobAI-Planned Flights · Pilot in Command
← Back to Blog

What drives the cost of a drone survey, and how to write an RFQ that gets comparable quotes

March 28, 2026

Illustrative image: What drives the cost of a drone survey, and how to write an RFQ that gets comparable quotes

Two drone survey quotes for the same site can differ by a wide margin, and the gap is rarely about pilot skill. It usually comes from two vendors pricing two different jobs.

This guide skips price tables on purpose. A number without a written scope behind it does not compare to anything. Instead, it covers what moves the cost of a drone survey, which public rules set minimums you cannot negotiate, and what to put in a request for quotation (RFQ) so every bid answers the same question.

It is written for civil engineers, contractors, landfill, mine and basin owners, and agencies in Southern California and Metro Atlanta.

Start with the decision the data supports

Cost follows the use of the data. A planning-level earthwork estimate, a progress map and a permit-grade topographic surface are different products. They need different control, different checks and different signatures.

Before you ask anyone for a quote, write one sentence: "This data will be used to ___." Everything below flows from that sentence.

Acreage and terrain

Area matters, but not in a straight line. Mobilization, setup, control placement and processing setup are largely fixed per site. So doubling the acreage rarely doubles the effort. This is a general pattern, not a measured figure.

Shape and relief matter as much as size.

  • Compact parcels fly efficiently. A long corridor such as a road, channel or pipeline needs more launch points and control spread along its whole length.
  • Several small parcels act like several mobilizations, even if the total acreage is modest.
  • Steep or terraced ground calls for terrain-following flight plans so the ground resolution stays consistent. A landfill face or a pit wall is slower to plan and to check than a graded pad.
  • Hard surfaces such as standing water, fresh pavement and uniform sand can be difficult for image matching and can add processing review.

Give every bidder the same boundary file (KML, shapefile or DWG), and say whether access roads, laydown yards and offsite tie-ins are inside it.

Vegetation: LiDAR or photogrammetry

Vegetation is the biggest technical fork in the road. Photogrammetry measures what the camera sees. Over grass, brush or crops, that is the top of the plants, not the ground. LiDAR sends laser pulses, and some reach the ground through gaps, so it can produce a bare-earth surface where photogrammetry cannot.

LiDAR is not magic, and public numbers show why you should ask for accuracy by land cover. Figure 1 puts four reported values side by side.

Horizontal bar chart of reported vertical RMSE: 2 to 3 centimeters over bare ground, 4 centimeters for a vendor system specification, 7 centimeters on an open road and 21 centimeters under dense canopy.
Figure 1. Reported vertical RMSE for drone LiDAR in four settings. Sources: Chen, Geyman and Lamb, Landslides 2026; DJI Zenmuse L2 specifications; Tamimi and Toth, ISPRS Archives 2024. Built from the post's data folder, 2026-10-17.

The values come from different studies, sensors and methods, so read them as a range, not a ranking.

  • Chen, Geyman and Lamb report 2 to 3 cm RMSE over bare ground surfaces in the Eaton fire area.
  • DJI's Zenmuse L2 page states 4 cm vertical at 150 m, measured in a DJI laboratory environment. That is a vendor figure for one sensor, named here only as an example.
  • Tamimi and Toth tested an L2 and reported 0.07 m on an open road and 0.21 m for forest checkpoints.

What that means for cost: vegetated ground takes more field checks, more manual review of ground classification, and sometimes a second pass or a different season. A bare, graded site needs less of all three. If your site has brush or trees, the quote should say how bare-earth accuracy will be tested under them. A reasonable inference, not a rule: the more of the site is covered, the more of the budget goes to review and checking instead of flying.

Many projects use both sensors. LiDAR carries the terrain, and photos carry the orthomosaic.

Deliverable and accuracy spec

This is the driver most often left vague. "Survey-grade" is not a specification. An accuracy class and a test method are.

The ASPRS Positional Accuracy Standards, Edition 2 express accuracy as RMSE and raise the minimum number of checkpoints for a fully compliant accuracy assessment from 20 to 30. The standard also says that vertical accuracy in vegetated areas should be evaluated and reported, not treated as a pass or fail criterion, and that checkpoints should be at least twice as accurate as the product being tested.

Every added product adds processing and review time. Spell them out:

  • Classified point cloud, with classes named.
  • Bare-earth DTM, with cell size.
  • Orthomosaic, with ground sample distance.
  • Contours, with interval, and whether breaklines are included.
  • Surface files such as LandXML, or a CAD drawing, in the layer standard your team uses.
  • Volumes, with the base surface defined.
  • An accuracy report with the checkpoint count and RMSE by land cover.

State the coordinate system, vertical datum, geoid model and units. Converting data after delivery is rework for everyone, and a datum mismatch between two surveys can look like earthwork.

Ground control and checkpoints

Ground control points tie the data to your datum. Checkpoints are different: they are measured on the ground, kept out of processing, and used only to test the result. Both take field time, and field time is a major part of what separates a thin quote from a complete one.

Public rules set floors. Figure 2 shows the minimum number of positional checks Georgia's land surveying rules require for UAS-collected topography, next to the ASPRS minimum of 30.

Bar chart of Georgia's minimum positional checks for UAS surveys by project size: 4 for 1 to 10 acres, 8 for 10 to 25, 12 for 25 to 100, 24 for 100 to 200, no stated figure for 200 to 300, and 36 for 300 acres or more, with a dashed line at the ASPRS minimum of 30.
Figure 2. Minimum positional checks for UAS topographic surveys under Ga. Comp. R. & Regs. 180-7-.04, with the ASPRS Edition 2 minimum of 30 checkpoints for comparison. Sources: Georgia Rule 180-7-.04 (read 2026-10-17) and ASPRS Edition 2. Built from the post's data folder.

Three things stand out.

  1. Georgia's floor grows with site size. The rule calls for a minimum of 12 checks for 25 to 100 acres and 24 for 100 to 200 acres. At 300 acres or more it is 36.
  2. The two standards do different jobs. Georgia's rule is a legal minimum for surveys it governs. ASPRS is an accuracy-testing standard you choose to invoke. A small site can meet Georgia's floor with fewer checks than ASPRS wants for a full report.
  3. The rule has a gap. It prints bands for 1 to 10, 10 to 25, 25 to 100 and 100 to 200 acres, then 300 acres or more. It lists nothing for 200 to 300. A surveyor has to resolve that, so ask how.

The same rule asks for ground control "along the flight lines" and says the surveyor must perform positional checks "along the perimeter of and within the surveyed area." In California, the board's Bulletin 50 says the licensed land surveyor must use field auditing to verify that the ground control and software mapping are accurate within the project's tolerances.

Control and checkpoints also depend on access. A site with locked gates, active haul roads or a daily-changing working face is slower and sometimes needs a second visit.

Licensed review and stamp

If the data will support a design, a permit submittal or a volume of record, a licensee has to be in responsible charge. This is a cost line, and it should appear in the quote.

  • California. Business and Professions Code 8726 covers anyone who "determines the configuration or contour of the earth's surface" by mathematics or photogrammetry. Bulletin 50 says flight planning, piloting and capturing images are not themselves regulated, but creating a topographic map for a client is. The licensee is a PLS or a civil engineer legally authorized to practice land surveying.
  • Georgia. The rule states that producing contour maps and elevation data "to typical survey precision" is the practice of land surveying and "must be performed by properly licensed individuals and authorized firms." The licensee is a PLS.

Twinn Digital captures and processes the data and does not stamp it. A licensee reviews and stamps what goes into a permit or design set. The RFQ should say who that licensee is, whether the licensee reviews the control and checkpoints or only the final surface, and what the stamped sheet will say. Compare bidders on this line. A quote with no licensed review may be cheaper because it delivers a different product.

Airspace authorizations

Many sites sit under controlled airspace. Part 107 requires prior air traffic control authorization to fly in Class B, C or D airspace, or within the surface area of Class E airspace designated for an airport.

  • LAANC. The FAA's UAS Data Exchange offers near real-time authorization for flights below the altitude ceiling on its facility maps. A pilot can apply up to 90 days in advance. Higher requests go through a further-coordination process.
  • Waivers and manual authorizations. Operations outside Part 107 limits need an FAA waiver. The FAA's waiver page says it aims to review requests within 90 days. Processing varies with complexity.
  • Temporary flight restrictions. These can move a schedule with little notice.

Near a busy airport, such as many Southern California and Metro Atlanta sites, a provider that checks airspace before bidding is pricing the real job. Ask whether authorization is already in hand, who requests it and what happens if it is denied.

NDAA-compliant equipment on federally funded work

Equipment rules can change who may bid. The American Security Drone Act (Pub. L. 118-31, secs. 1821-1833) bars federal procurement and operation of drones from covered foreign entities, and bars federal funds from being used for them. The funds and operation provisions began two years after enactment on December 22, 2023, and the sections cease to have effect five years after enactment.

A covered foreign entity is one on a list maintained by the Federal Acquisition Security Council and published in SAM. Do not assume any manufacturer is on it or off it. Check SAM.gov at the time of bid.

Separately, the FCC's December 22, 2025 action added foreign-made UAS and critical components to its Covered List. The FCC says this blocks new equipment authorizations and does not affect drones people already own.

For cost, the point is simple. If any federal money is in the project, say so in the RFQ. Twinn rents equipment per job and is not tied to one brand, which lets it match the sensor to the funding source. NDAA-compliant sensors are available on request for agency-facing work. Equipment availability for that class can differ from the standard commercial supply.

Travel and mobilization

Sites far from a provider's base add travel, lodging and equipment transport. These costs do not change how hard the data is to process, but they should be visible. Ask for them as a separate line.

Batching helps. Several sites in one metro area, such as a basin program or a set of landfill cells, can share one mobilization. Say so in the RFQ if you have more than one location.

Repeat surveys

Monthly stockpile inventories, weekly grading checks and annual capacity surveys all repeat. The second flight is usually cheaper in setup than the first, because the flight plan, control and processing workflow already exist. But repeat work adds its own requirements:

  • Control that survives between visits.
  • The same datum and the same base surface every time.
  • A defined cutoff date, so material placed after the flight lands in the next period.
  • A change log, if you will compare epochs.

Scope a recurring program once, as a series, with a stated cadence. A string of one-off bids gives up the benefit of repetition.

Processing

Processing covers alignment, ground classification, surface building, contouring, QA and the accuracy report. It is often the least visible line and the one where scope grows.

Ask which steps are automated and which a person reviews. Dense vegetation, steep faces and water usually need review. Ask also what happens when the first result misses the spec: whether re-processing is included, and whether a re-flight is.

Twinn's flights are planned with software agents under human supervision and flown by an FAA Part 107 remote pilot, and the company carries $2M in insurance. Those are facts you can check against the credentials every bidder must show.

A checklist for your RFQ

Put these in writing so each bidder prices the same job.

Project

  • [ ] The decision the data supports, in one sentence.
  • [ ] Site boundary file, plus access roads, laydown yards and offsite tie-ins.
  • [ ] Single site or several, and whether the work repeats.
  • [ ] Any federal funding, and the agency, so equipment rules can be applied.

Capture

  • [ ] Method required, or the performance needed, so bidders can propose LiDAR, photogrammetry or both.
  • [ ] Vegetation and ground cover, with the areas that matter most.
  • [ ] Airspace: who requests authorization, and what is already in hand.
  • [ ] Site access, badging, safety training and working hours.

Accuracy

  • [ ] Accuracy standard and class (for example ASPRS Edition 2), with RMSE by land cover.
  • [ ] Number of independent checkpoints, at least 30 if ASPRS is invoked, and who surveys them.
  • [ ] Ground control: who sets it, how many points, and the monument types.
  • [ ] Any state minimums that apply, such as Georgia Rule 180-7-.04.

Deliverables

  • [ ] Every file named, with format, cell size or interval.
  • [ ] Horizontal and vertical datum, geoid model, units and any site calibration.
  • [ ] Volume method and base surface definition.
  • [ ] Accuracy report contents.

Review and terms

  • [ ] Licensed reviewer and stamp: name, state and scope of review.
  • [ ] Pilot credentials (FAA Part 107) and insurance limits required by your contract.
  • [ ] Re-flight and re-processing terms if the result misses the spec.
  • [ ] Travel and mobilization shown as their own line.
  • [ ] Delivery dates stated by the bidder, not assumed by you.

Ask every bidder to answer in the same order. A bid that skips a line has priced something else.

Red flags when comparing bids

  • A price before anyone looks at the site. Vegetation, access and airspace change the work.
  • Accuracy with no test. A sensor datasheet is not an accuracy report.
  • Vague deliverables. "A 3D model" is not a list.
  • No licensed reviewer for design or permit data. The bid may be for a different product.
  • The narrowest scope. A bid that omits checkpoints or your datum can cost more in rework than it saves.

Check free public data first

If the site is stable and a planning-level surface is enough, public lidar may already exist. Programs such as the USGS 3D Elevation Program publish lidar for much of the country. Georgia's rule even includes language for surveys that incorporate public data, requiring the source to be stated and noting it is not certified by the surveyor. Public data tells you what the ground looked like when it was flown. It does not tell you what it looks like today.

One practical next step

Before you request quotes, write the one-sentence use of the data, pick the accuracy standard, and draft the deliverable list with datum and units. Then send the same RFQ to every bidder.

To scope a project with licensed review and the right sensor for your funding source, see Twinn Digital for surveyors and engineers.

Ready to See Your Terrain?

Get a quote built around your project

Whether you manage farmland, watersheds, municipal infrastructure, or development sites — tell us about your site and we'll prepare a scope and estimate around the required outputs and schedule.

Get a quote

Prefer texting? Text (424) 577-5461

(424) 577-5461Get a quote