Products · VTOL Fixed-Wing

VTOL Configuration for Large-Area Terrain Survey

Large-area survey is a production problem: overlap, ground control, and how many sorties the schedule allows. Aircraft choice follows from those three.

2 of 10Method note

Overview

Fix ground sample distance and forward/side overlap first; they determine altitude, and altitude determines sortie count.
Decide the ground control strategy (GCP, PPK or RTK) before the first flight — it cannot be added afterwards.
Terrain relief changes effective overlap. Plan for the highest terrain in the block, not the mean.
Agree the deliverable coordinate reference system and vertical datum in writing before mobilisation.

Coverage per day is the requirement, not coverage per flight

Large-area terrain survey is the mission a VTOL fixed-wing is built for, and it is also the mission where a badly framed requirement produces the most expensive mistakes. The instinct is to specify endurance. The correct specification is area per working day, because that is what the programme is actually contracted to deliver and it is the only number that accounts for turnaround, transit and weather losses alongside raw flight capability.

Start from the deliverable and work backwards. How many square kilometres, at what ground sampling distance, with what overlap, within what calendar window. That chain of numbers determines the sensor, the flight altitude, the line spacing, the number of sorties, and therefore the battery or fuel logistics and the crew size. Teams that start from the aircraft instead of the deliverable consistently end up with a platform that flies well and a programme that runs late.

Then separate the two kinds of time. Airborne time is the part people optimise; ground time is the part that usually dominates. Between recovery and the next launch sit battery or refuelling, data offload and verification, sensor check, flight plan load, and the walk to and from the launch point. On a large site the walk alone can exceed the flight. Measure it before you buy, because it is cheaper to change a ground routine than a fleet.

Choosing the sensor and the altitude together

Ground sampling distance is not a sensor property; it is the ratio of sensor resolution to flight altitude. That means altitude is a free variable you can trade against coverage: fly higher and each line covers more ground, but resolution drops and the deliverable may no longer meet spec. Fix the required ground sampling distance first, then compute the altitude that delivers it for the candidate sensor, then compute the number of lines that altitude implies for your area. Everything downstream follows from those three numbers.

A mapping camera is the default for terrain work and the right choice where the deliverable is an orthophoto or a surface model. Where the terrain is vegetated and the deliverable is a ground surface rather than a canopy surface, a LiDAR payload becomes relevant — but it brings mass, power, and a calibration and georeferencing workload that a camera does not. Decide this on the deliverable, not on the novelty of the sensor.

Overlap is the other variable that quietly doubles or halves a programme. Front and side overlap determine both the quality of the reconstructed surface and the number of lines required. Specify the minimum overlap that meets the accuracy requirement and no more; excess overlap is paid for in flight time on every single sortie, and over a large area that is the difference between finishing in a week and finishing in two.

Wind, altitude and the planning assumptions that break

Wind is the largest single source of schedule loss in fixed-wing survey. It affects ground speed asymmetrically along and across lines, which changes both coverage rate and image spacing; it increases the turn radius at line ends, which lengthens every line change; and beyond a threshold it grounds the aircraft entirely. Plan against a realistic distribution rather than an average, and build the plan so that a day lost to wind can be recovered by additional sorties rather than by compressing quality.

Altitude and terrain relief interact in a way that surprises teams on their first large site. Flying a constant altitude above take-off point over rising ground means falling clearance and rising ground sampling distance variation across the strip. Terrain-following flight plans solve this but require a reliable elevation model to plan against, and they add planning time. On a site with significant relief, decide early whether you have that model and who produces it.

Airspace is the other planning assumption that breaks late. Large survey areas frequently cross controlled airspace, temporary restrictions, or corridors with prior users. File early, and treat the clearance lead time as part of the programme schedule rather than an administrative footnote. A platform that can fly tomorrow is worth nothing if tomorrow's clearance arrives next week.

Data volume, georeferencing and the ground workflow

A large-area camera survey produces data at a rate that outruns unprepared workflows. Estimate it before you fly: images per sortie times sorties per day times bytes per image, then ask where that lands overnight and how long the processing takes. If processing takes longer than acquisition, the backlog grows every day and the first sign of trouble is a disk, not a flight log.

Georeferencing strategy should be fixed before the first sortie, because it determines both the hardware and the ground work. Direct georeferencing with a survey-grade GNSS and an inertial solution reduces ground control but adds cost and calibration. Ground control points cost field time and people but anchor accuracy in a way that is easy to verify. Most programmes land on a hybrid, and the right mix depends on the accuracy spec and the terrain's accessibility.

Finally, decide who owns verification. Someone must check each sortie's coverage and image quality on the day it is flown, not at the end of the block. Re-flying a missed strip costs one sortie; discovering a systematic problem at the end costs the block. This is a role, not a task, and it should be named in the plan with the authority to stop and re-fly.

Where to confirm the plan before committing

The single most valuable thing you can do before committing to a large-area programme is fly a representative subset with the actual sensor and the actual crew. Not a demonstration — a measured trial on terrain that resembles the target area, using the flight plan you intend to use, with coverage per sortie and turnaround time recorded. That trial converts every assumption above into a number.

Where the configuration deviates from a standard offering — an unusual sensor, a non-standard mount, a specific data format — treat it as engineering scope and have it documented before the order. Our custom survey data acquisition work exists precisely for configurations where the standard bay, mount or interface does not match the requirement.

Send the area, ground sampling distance, overlap requirement, terrain relief and expected wind envelope to our engineering team. We will respond with a coverage estimate, a sortie count and the configuration we would propose, including where a standard airframe is sufficient and where it is not. For the step-by-step mapping setup, the orthophoto acquisition configuration note covers the camera-side detail.