Some quotes include a pre-capture site visit line. It looks like operator-side overhead — a day where nothing flies and nothing gets delivered. The value is invisible because it lives entirely in the day that *does* fly: the launch point that wasn't actually clear, the control mark that's been buried under a year of vegetation, the access road that closes after the rainfall last week, the airspace clearance you didn't realise had been revoked. The site visit's whole job is to find these problems on a day where finding them costs $1,500 instead of $15,000.
If you've ever seen a pre-capture site visit line on a quote and wondered whether it's necessary overhead or genuine engineering value, you've met the reconnaissance-budget question. The buyer pays a day for nothing visible to be delivered. The operator argues that the visit prevents the much larger cost of a failed capture day. Both are partially right.
Desktop planning has come a long way — aerial imagery, DTM previews, BOM forecasts, NOTAM lookups, satellite visibility predictions — and for many projects, a careful planning session is enough. For complex sites, desktop planning consistently misses things that a two-hour walk-around would catch. The question isn't whether to do reconnaissance; it's whether to do it remotely or on site.
This article is the eleven-item checklist of what an on-site visit actually evaluates, the project-shape indicators that distinguish "site visit warranted" from "desktop planning sufficient", and the cost-vs-risk trade-off operators are weighing when they propose one.
A typical pre-capture site visit takes 4-8 hours including travel. Eleven specific things being evaluated, in roughly the order they happen:
The desktop plan identifies launch points using aerial imagery and satellite-derived terrain. The site visit confirms whether the planned points actually work. Common discoveries:
Backup launch points get identified at the same time. A project with one launch option is one no-go away from mobilisation failure; a project with three launch options has redundancy.
GNSS satellite reception varies dramatically across a site — open ground gets clean reception, cliff faces and forested terrain get partial reception, deep valleys may have very limited reception. PPK correction requires both rover (drone) and base station to have strong, consistent reception.
The site visit lets the operator stand at the planned base station location, observe sky obstructions (trees, cliffs, buildings), and confirm via field GNSS receiver that satellite geometry is workable. Several hours of capture data with weak GNSS reception produces a trajectory that fights PPK correction.
(See RTK vs PPK article for the GNSS technical background.)
If the project uses pre-existing control marks (rather than fresh survey), the marks need to actually be there and findable. Aerial imagery doesn't show whether a mark from 2019 has been buried under 1.2 m of regrowth, disturbed by farm operations, or replaced by a fence post that looks like a control mark from the air.
The site visit physically locates each mark, confirms its condition, and flags any that need re-survey before capture day. Discovering a missing mark on capture morning costs the day.
Landowner permissions, tenant notifications, public- access closures, livestock movements — all of these were confirmed in writing during planning. The site visit confirms them in person. Specific things that surface:
A 30-minute conversation on site resolves these. A phone call doesn't always.
The desktop plan identified airspace classifications and filed any required notifications. The site visit confirms what's actually happening: helicopter landing pad on adjacent property, agricultural aviation schedule for the week, military exercise underway in the area.
Some of these prompt rescheduling; some prompt operational adjustments (lower flight altitude, tighter flight envelope, additional spotter). Either way, finding out before mobilisation is cheaper than finding out on the day.
(See CASA permits article for the regulatory framework.)
Site-specific hazards that aerial planning misses:
The hazard register from site visit feeds into the operational plan. Documentation also matters for insurance and CASA reporting if anything goes wrong on the day.
The desktop plan identifies access tracks; the site visit confirms whether they're trafficable for the equipment vehicle. Common findings:
Alternative access routes get mapped during the visit in case the primary fails on the day.
Where to land, where to pack down, where to charge if the project runs long. Sometimes the optimal launch point isn't the optimal landing point (wind direction, terrain, sun angle); the site visit lets the operator plan both ends of the operation.
For sites in remote or signal-poor locations: mobile coverage check at the launch point, satellite phone test if required, two-way radio range check. Operations that can't communicate with the field crew on capture day have safety implications that prompt some operators to no-go even with otherwise-favourable conditions.
For projects that include orthophoto, oblique imagery or multispectral capture alongside LiDAR, the site visit assesses lighting conditions at the planned capture time. Terrain shadowing, building shadows, canopy gap patterns — all affect image quality and should inform the capture plan.
(See hybrid workflows article for when this matters.)
The most subtle but most valuable item. The operator mentally walks through the planned capture day from arrival through demobilisation, identifying anything that doesn't work in practice. Timing of flight blocks relative to sun angle. Crew positioning during operations. Battery swap logistics. Data download checkpoints.
The desktop plan looks fine in software; the operational walk-through surfaces logistics issues that wouldn't have shown up until the day.
Project shape indicators that suggest a site visit will pay back:
Complex airspace. Controlled airspace boundaries within project area, BVLOS approvals required, proximity to controlled aerodromes.
Difficult or unknown access. Remote sites, gated private land, sites only accessible via complex permission arrangements, sites where access routes haven't been used recently.
Multiple stakeholders. Multi-property projects, sites with multiple tenants or land users, sites with local community sensitivity.
Existing infrastructure to avoid. Active rail corridors, operational mine sites, powerline corridors needing close-quarters work.
Engineering-grade accuracy spec. Projects requiring ±20 mm accuracy where the control mark network has to be perfect on capture day — the site visit confirms the network exists and is workable.
First-of-programme captures. Year 1 of a long- running programme deserves the visit; subsequent years can typically skip it.
Sites with limited launch options. Heavily-treed sites, tight urban environments, sites with restricted clearance.
A simple paddock 30 km from the operator's base for planning-grade DTM does not usually warrant a site visit. A complex mine site or BVLOS corridor on first capture almost always does.
A site visit typically costs $1,200-3,000 depending on travel and crew. The cost-of-failure being avoided:
The trade-off favours site visit any time the probability of capture-day failure is above about 15-25%, and complex sites can easily exceed that without reconnaissance.
(See mobilisation costs article for the underlying mobilisation cost structure that makes failed days expensive.)
The site visit isn't always warranted. Five project shapes where desktop planning is genuinely enough:
Simple area capture on well-mapped open ground. Australian farm paddocks with sealed road access, no airspace complexity, no stakeholder complexity.
Annual repeat capture on previously-flown sites. Year 2+ of a programme — the operator already knows the site.
Captures within an operator's regular service area. Sites the operator has flown nearby before; local knowledge substitutes for site visit.
Planning-grade or feasibility work. Where the accuracy target is loose enough that minor capture- day adjustments don't compromise the deliverable.
Projects with extremely tight budgets. Where the buyer accepts higher capture-day risk in exchange for the cost saving. Worth being explicit about the trade-off.
If you're paying for a site visit, the deliverable should include:
The report converts the site visit from a "we went and looked" line item into a documentation artefact you can audit.
When site visits don't deliver value, it's usually one of three patterns:
Visit too early. Site visit 4 weeks before capture finds things that change before capture (vegetation grows, access changes, gates lock). Visit within 1-2 weeks of capture day is the sweet spot.
Visit by junior staff without authority. Field person who identifies issues but isn't empowered to adjust the capture plan. The visit identifies problems; the plan doesn't change to address them. Operations manager or pilot-in-command should be on the visit.
Visit with no documentation. Operator visits site, forms mental model, doesn't document what was checked. Two weeks later, the operational plan doesn't reflect what was learned because nobody wrote it down.
The pre-capture site visit is operator-side reconnaissance that costs $1,200-3,000 and prevents capture-day failures costing $3,000-25,000. Eleven specific items get checked: launch points, GNSS sky visibility, control mark verification, in-person stakeholder confirmation, airspace operational verification, hazard identification, vehicle access, demobilisation options, communications coverage, lighting for hybrid captures, and operational rehearsal of the capture plan.
Site visit warranted when: complex airspace, difficult or unknown access, multiple stakeholders, infrastructure to avoid, engineering-grade accuracy spec, first-of- programme captures, limited launch options.
Desktop planning sufficient when: simple open ground, repeat captures, regular service area, planning-grade deliverables, extremely tight budget with explicit risk trade-off.
The visit should produce documented deliverables — report, updated plan, hazard register, stakeholder log, photo log — not just operator confidence. Three common failure modes: visit too early, visit by under-authorised staff, visit without documentation.
For complex sites, the question isn't whether to reconnoitre. It's whether to do it remotely (cheaper, misses things) or on site (more expensive, catches things). The trade-off favours on-site reconnaissance any time capture-day failure probability exceeds about 15-25%.
If you're scoping a project where any of the seven 'site visit warranted' indicators apply, we'll include the visit in the quote with a documented deliverable so the cost converts to an auditable artefact. If your project genuinely doesn't need one, we'll say so — the visit is the wrong line item to over-include just to fill the budget.
The cost structure that makes failed capture days expensive — and that makes site visit reconnaissance pay back when it prevents one.
The other half of pre-capture risk management — what's checked on the morning of the flight vs what gets checked weeks before during the site visit.